3 ms·
An ecosystem of attractive looking templates, devs who know how to use it, various tools that integrate or output it, examples and tutorials to learn from, code
by ZeroGravitas 10y ago
An ecosystem of attractive looking templates, devs who know how to use it, various tools that integrate or output it, examples and tutorials to learn from, code samples to re-use etc.?
There's also a justification for the type of classnames you're railing against here:
http://nicolasgallagher.com/about-html-semantics-front-end-architecture/ http://nicolasgallagher.com/about-html-semantics-front-end-a...
I believe Bootstrap adopts many of these ideas. So it's not just a mistake, but an intentional decision as part of a different paradigm. Feel free to suggest that it's not a useful way to build websites, but don't be fooled into thinking they've accidentally broken a rule they intended to follow.
- nailer 10y agoI'd argue more developers know how to use flex than bootstrap right now. And many developers would spend additional time researching how to do things the bootstrap way. If you don't have developers and want templates, use Squarespace, bootstrap is a poor fit. I've read the article, but I still don't see why, to change the login box, I need to modify two places (HTML and SCSS) rather than one (SCSS).
- sametmax 10y agoMost dev I meet don't even know what flex is. In my last year of dev, I have seen only one code base that was using it. Everybody else was still using float, margin, etc. You are working in a bubble, the bubble of expert coders. Most dev are not expert coders, they are expert plumbers.
- ZeroGravitas 10y agoThere's a wide range between using Squarespace, and building an entirely custom website from scratch. It's a big 'ole niche that Bootstrap and other similar systems have been filling for a while. There's even a reasonably sized trend of big apps who think they're too good for Bootstrap but basically implement an internal clone of it. https://design.atlassian.com/product/components/buttons/ https://design.atlassian.com/product/components/buttons/ As to your question, if you have an actual design system in place then you can change all primary buttons on your site by only changing the SCSS, and if you want to add a new primary button, or a small button, or a small primary button etc. you can do so by only changing the HTML. And when you do need to do both, it splits some of the responsibility in ways that make the code easier to manage and develop. If it really comes down to just wanting to do stuff in one place, then there's a bigger picture that's being missed. Think about distribution of responsibility and letting junior staff add buttons, while more senior (or just those with different kinds of expertise) staff control the styleguide. If they each re-invent the wheel then there's not going to be consistency or re-use.
- nailer 10y ago> There's a wide range between using Squarespace, and building an entirely custom website from scratch. It's a big 'ole niche that Bootstrap and other similar systems have been filling for a while Good point. > There's even a reasonably sized trend of big apps who think they're too good for Bootstrap but basically implement an internal clone of it. Everyone should have a set of rules implemented in SCSS. They just don't need to implement them in HTML. > As to your question, if you have an actual design system in place then you can change all primary buttons on your site by only changing the SCSS, and if you want to add a new primary button, or a small button, or a small primary button etc. you can do so by only changing the HTML. Buttons are an easier case because they already exist. Anything else - avatar images, login dialogs, etc, are an argument for not using Bootstrap (or BEM, or other HTML based systems) - Making a design system in SCSS only: to change the login box, change the SCSS for .login-box - Using bootstrap: to change the login box, add and remove whatever HTML visual classes bootstrap needs for your new login box look (is it '--grid-l4-left-blah-shiny') then modify the SCSS (Edited this a lot while I wrote it, kind of thinking aloud and have trouble reading in monospace)
- ZeroGravitas 10y agoRegarding --grid-l4-left-blah-shiny, bear in mind that some people, say users of a corporate CMS maybe, simply do not have access to the CSS for the page they are designing. For those people, very granular visual styles have an important use case. This is however something that can be abused, and I've seen people who don't "get it" create problems for their future selves by not understanding when and where to use those kind of classes. On the other hand, your login box is a box, and presumably you have other boxes, a sign-up box perhaps. You may well want them to have some similarity, even on an infrastructure level that is invisible to the user, like consistently only having margins on the top or the bottom. That kind of thing can be provided by the design system out of the box, letting the person who's hooking up the login on the backend have something functional and ready to go with no delay, to later to be handed off to someone who makes it bounce around on mousover and look snazzy. And if other priorities get in the way, then you'd still have a basic foundation level box that wouldn't embarrass you until you get around to redecorating.
- thegayngler 10y agoI disagree with with this. Im like the only one on my team who knows flex right now. Most debs know the old ways of doing things flex box does better.
- metamet 10y agoI agree with you (and am in the same boat). Bootstrap is ubiquitous, and using it as a scaffold means you don't need to use flex.