4 ms·
Correct me if I'm wrong or misunderstanding, but apart from basic typography (relative sizes and spacing of headings and body text), bootstrap has been opt-in s
by nilliams 10y ago
Correct me if I'm wrong or misunderstanding, but apart from basic typography (relative sizes and spacing of headings and body text), bootstrap has been opt-in since bootstrap 3.
Everything else requires adding classnames or using mixins before bootstrap starts to take effect.
If you don't want the typography stuff you can uncheck it on the customize page. (Or if you're using Less/Sass delete the typography import e.g. delete `@import bootstrap/typography` . from `_bootstrap.scss`).
- acomjean 10y agoI think that is correct. When I was using bootstrap 2, I downloaded a custom version that didn't include styles. It was annoying because it also changed basic styles. Bootstrap 3 leaves things alone. for those unfamiliar with the customize page mentioned. http://getbootstrap.com/customize/ http://getbootstrap.com/customize/ I do appreciate the additive approach blaze is taking. Add what you want.
- grumpywizards 10y agoBlaze doesn't mention Bootstrap specifically regards opt in. But Bootstrap does apply CSS to some elements without permission. Foundation even more so. SemanticUI too. Blaze is different than all of these in that it gives the power back to you!
- nilliams 10y agoOnly what I addressed. Typography, which you can disable or override easily. Let's be clear, Bootstrap is the most popular CSS framework in the world, whose Github issue threads have been pored over many times more than Blaze's are likely to be for a very long time, and Bootstrap 3 at least never took any power away. There are some really cool looking elements to Blaze and I'm very interested in using it for some upcoming projects, but to infer that you should ditch Bootstrap for it, on the basis of opt-in vs opt-out is very misleading.