Bootstrap 4
blog.getbootstrap.com
blog.getbootstrap.com
Add a 'btn' class to those links.
Add the 'danger' class to the links that will send an actual alert and a 'info' class to the ones that are just test.
Obviously there are also about a hundred other things that should have been in place there, but it is an issue of real consequence that the default styling and UX options of "plain" HTML are so poor.
1 - http://nymag.com/selectall/2018/01/hawaii-missile-warning-se...
While I don't use it currently, Bootstrap helped me go from 0 design skills to build non-awful user interfaces. It's hard to overstate the impact they have had on making the web a better place.
For me a combination of approaches makes the best sense at present. I think of Bootstrap (or Bulma, etc.) as an advanced "reset/normalize", with the addition of some useful global variables. A better starting place, if you will. From there I use the provided class names where it makes sense, and inline styles for everything else.
For inline styles I often use either styled components or glamorous. However my experience has been mixed as I also make heavy use of recompose and often don't have a clear idea which one I want to use to handle dynamic styles. I haven't done so yet but am interested to try Fela.
To finish the layout I generally am making a few utility classes to control things like color and spacing (not a fan of the default bootstrap spacing classes). And then of course custom CSS for navigation, typography and other misc widgets.
But the bulk of the main layout is handled entirely with bootstrap classes. And because nearly everything can be specified with the responsive breakpoint prefixes, I don't have to write repetitive media queries.
I have been really impressed with Bootstrap 4. I've been updating our site with each beta release. Glad that there are no breaking changes between beta 3 and stable as promised!
Assuming NPM install, look at node_modules/bootstrap/scss/bootstrap.scss for a list of files that are included and pick the ones you need and include them manually in your project's SCSS file.
Here's a bit from my Makefile (because I love me some Make):
SASS = ./node_modules/.bin/node-sass
%.min.css: %.scss
$(SASS) \
--output-style compressed \
--source-map true \
--source-map-contents true \
$< $@Bootstrap is the only framework that looks nice, is responsive, and fully addresses accessibility. The only thing I can fault it for is using Jquery, but I don't use the javascript features, so it doesn't matter (to me) anyway.
I'm a little surprised though, that jQuery is still a requirement. I'm guessing that this might be due to linked JS components that they don't have permission to modify?
This issue[0] basically says the team is too small to rewrite and remove jQuery as a dependency.
https://github.com/twbs/bootstrap/pull/23586
One of the remaining pieces also has a PR:
https://github.com/twbs/bootstrap/pull/24879
Too bad this didn't land to BS4 though.
If you say its OK, I'll flag your post to get dang's attention, and then unflag it later.
Quick Google search explains that brutalist architecture is about creating modular elements representing specific functionality often sacrificing aesthetics.
A lot of the sites on that gallery are ugly just for being ugly, they have no functionality and use different types of animations or constructs to just make something unconventional from common website aesthetics, I get why, but it feels like the word brutalist was borrowed here and is applied in a very different way.
I have a dozen projects that use Bootstrap and it just feels like a lot of work to change that paradigm now for one solitary project.
22 year old me: "Man you sound old."
With other frameworks I'm constantly adding new rules just to add a bit of padding and margin here and there, but Bootstrap 4 gets a lot of it right by default. Plus it now has a lot of useful utility classes for small padding increments (e.g. `.mb-3` for `margin-bottom: 1.5rem` and `.px-2` for horizontal padding of 1rem). With Bootstrap 4, a previous project required only 10-ish lines of global CSS[3]. Sure, it looks and feels like a Bootstrap project, but that was fine for the purpose of the app, and Bootstrap 4 looks fresh enough that I don't feel like the design is outdated.
FWIW, I've also had a lot of luck recently with Material-UI[4], a set of React components that implement the Material UI aesthetic. My current project feels like it could fit in with any Google app from G Suite.
[1]: https://minicss.org/
[3]: https://github.com/statico/aspen/blob/master/pages/index.js#...
There is also:
- UiKit - https://getuikit.com
- Bulma - https://bulma.io/
- Sematic - https://semantic-ui.com/
NOTE: I'm not a front end person, have used a couple of these for various personal projects.
https://react.semantic-ui.com/
They're really a joy to work with. My one beef with Semantic is that it could be easier to make themes. I know that someone is currently working on a theme generator site like Bootstrap and hopefully that will be a nice step forward.
But then I tested their examples on my mobile phone and it looked really bad. It just seemed that it wasn't responsive at all, which really surprised me.
[0]: http://basscss.com/ [1]: https://github.com/basscss/addons
Check the links at the bottom of that site for more addons (such as this: http://motion.ant.design/)
Not being tied down to global styles is so nice. The downside though, is that anytime you make something you have to redo all the styles. I find this not to be a huge deal, though since you can just turn them into components.
For my own projects, though, I've moved to using Bulma instead for baseline design.