Please stop using Twitter Bootstrap
notes.unwieldy.net
notes.unwieldy.net
Well, your blog still looks like a me-too minimal one column, design, like another 50,000,000 blogs out there (half of them on Tumblr), but you don't see me complaining, do you?
Funny how on the desktop designers demand HIG compliance and standard UI widgets, while on the web they want us to get all Kai's Power Tools on every button and widget.
For example, Firefox, Safari and Chrome all look identifiably different on OS X, despite all implementing the same overall style.
Twitter bootstrap isn't just a CSS style, it's a rigid layout and UI pattern. The author is decrying the use where bootstrap is the only kind of design being done. In that case, people typically haven't considered what layout they want to use or which elements to emphasize and how. They just go with the standard 960 grid and its simple divisions, regardless of how much content there is, and take something that's meant to be invisible and emphasize it visibly by not adding anything new.
While bootstrap gives the appearance of being well designed, often the content inside it fails to live up to that promise.
Only because I have a thing about using serif fonts in html, otherwise it might well be one of my fallbacks.
And besides, arguing that people should put more effort into restyling Bootstrap is different than arguing they should abandon it altogether. In terms of providing a framework for layouts, I think it does its job quite well, and that users will probably intuitively understand a Bootstrap site because they've encountered them a hundred times before. This in turn gives your site an implied sense of stability and trustworthiness since it "looks like twitter/etc etc."
But he notes that it's 100% customizable and says "most people do not bother". That's the real problem. As long as you bother with that, you can't tell it's Bootstrapped (http://diehlgroup.com/) and his whole argument collapses. It's not JUST a design package for developers. It's also a basic reset and browser-compatibility package, taking away so many headaches and days and days of work.
To me, the best argument against Bootstrap is purely the weight. But even then, I can strip it down to only components I need, literally even it's just one file of LESS mixins (which is what I pretty much end up doing).
Interesting and true, though. Shits taking over.
Are you going to ask iOS developers to stop using the Master-Detail Application, Tabbed Application, Cards-based Application or Page-based Application templates next?
Hate on it all you want because you think it is boring and generic, but at least acknowledge that it provides value, especially in circumstances when the alternative is an interface created by someone who likely lacks the chops to create a well-designed coherent interface.
I still think on the whole we're better off than before because in most cases Bootstrap replaces things that were even uglier.
It's just a little disappointing sometimes when you see a company that clearly has the means to develop its own identity and design settle for generic Bootstrap.
As a designer, would you rather take spaggetti html code from a developer or one compliant already with a framework like bootstrap to start working off?
And wrapbootstrap or bootstrap themes? :-)