Hey,
I recently formalised some of my thoughts on [not] using Bootstrap.
However, if you do I recommend creating your /own/ class structure (
http://bem.info/ seems a good structure) and @extending (I have a
preference for SASS) Bootstrap classes, as previously suggested:
/http://fourword.fourkitchens.com/article/you-dont-need-bootstrap/
* /Antipatterns ~
http://ruby.bvision.com/blog/please-stop-embedding-bootstrap-classes-in-your-html/
* /Create code, rather than overriding it/
* /Bootstrap for prototyping, interaction inspiration and perhaps
CSS architecture; but nothing more/
/http://matthewcopeland.me/blog/2013/11/04/bootstrap-bankruptcy//
* /"In this analogy, bankruptcy is the point at which the value
gained from the custom interface is less than the effort
required to refactor bootstrap and implement the new interface."/
* /"Few buy furniture by the lot. You find one or two pieces that
you really want and slowly update your room over time. Great UI
tends to evolve the same way. Through feedback and analytics you
can evolve your UI to fit the needs of the customer and the
product."/
/http://ruby.bvision.com/blog/please-stop-embedding-bootstrap-classes-in-your-html/
* /Antipatterns ~
http://fourword.fourkitchens.com/article/you-dont-need-bootstrap/
* /"The second problem is this: by hard-coding Bootstrap's class
names into your HTML, you're marrying your code to Bootstrap.
Bootstrap's very name should indicate that developers should
consider it a starter library: something to get you out the gate
faster, not your permanent design solution."/
/http://yycjs.com/not-bootstrap/#/welcome/
/https://coderwall.com/p/wixovg/
* /"Bootstrap seems to have become less prescriptive over time,
but I also prefer Foundation for the reasons you've gone
through, here - better integration with Sass and encouragement
form the devs that you use @extend to build out your own classes."/
/https://medium.com/@felippenardi/top-5-core-differences-between-bootstrap-3-and-foundation-5-8b3812c7007c/
Regards,
