2 ms·
> 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 s
by 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.
- nailer 10y ago> some people, say users of a corporate CMS maybe, simply do not have access to the CSS for the page they are designing. Agreed, but that's an edge case caused by mismanagement. People who need to style things should be able to edit styles. > 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 Sure, but you can make consistent margins on your boxes with a SCSS mixin. It's the same difficulty to set up than moving your site to bootstrap, and much less difficult to maintain.
- spdustin 10y agoOr use Bootstrap 3's SASS port, and .my-login-box { @extend .col-md-4; background-color: fuchsia; } or whatever, and don't touch the markup to add any BS-specific classes. And don't use fuchsia. ;)
- nailer 10y agoWorks for me - I'd have no objections if Bootstrap actually did that in their documentation.
- ZeroGravitas 10y agohttps://v4-alpha.getbootstrap.com/layout/grid/#sass-mixins https://v4-alpha.getbootstrap.com/layout/grid/#sass-mixins
- nailer 10y agoYep. I mean by default, rather than encouraging HTML.