I'm really not sure I understand the strategy of dumping so many styles into the global name space. Basically, all of us have been working around the styling as we implement features.. a major refactor is in order and we will likely be ditching bootstrap.
Just a warning if you plan to build beyond the styles provided by bootstrap, it is not straightforward. Really, the entire set of styles should be contained within its own namespace or some other meaningful semantic convention.
Am I missing something? What is intended after 'boot'? am I really supposed to replace these global styles manually?
Using a framework favors convention over configuration for the benefit of speed.
I especially like it because the team has a central set of documentation for the UI to use - that means if we override a style, if they followed the convention, everything works out better.
I do agree using a namespace would help though.
I worked around the styles I didn't want in two different ways. One, I built my own version of the css that excluded all the form styles (non-native controls are bad). This involved installing some packages that I didn't really understand but didn't need to. It took maybe five minutes start to finish. The second was simply overriding the CSS I didn't want. This is absolutely no different than what you do with any other website, where you're overriding the browser's default styles instead of Bootstrap's.
Its different. There are all kinds of properties I don't want to have to override. This gives me the option of deleting code from bootstrap css or having duplicate css code in my project, every page load, and every rendering of the dom.
A prototype is fine, but once I'm working with a graphic designer, its mostly undoing vs overriding. Would be so much more bootstrap-able if the styles were constrained to classes.
As a generalist developer who does a little bit of everything but has a hard time with the design side of things, I'm loving using Twitter Bootstrap on some of my personal projects. One example where I've used it is http://smacktweets.com. The header bar alone, while extremely simple, is so much better than what I probably would have done on my own.
Twitter Bootstrap gives you great looking design elements with very very little effort. If you are good with the design side of things it's probably overkill and heavier weight than you want in a boilerplate if you are going to customize everything anyways.
Skeleton (http://getskeleton.com/) is another great boiler plate that I have also enjoyed using on all kinds of projects. It is really just a boilerplate and doesn't have all the pretty design elements that bootstrap has.
Just wanted to say thanks for putting this out and for the community continuing development on it. I'm really enjoying it.
Issue #538 [1] is a showstopper in v1.4.0 for anyone using bootstrap via the less.js compiler (and not the precompiled CSS files).
I'm definitely using it for any side projects or sites I need to toss up without spending days on them.
It's really comprehensive and covers a lot more than other frameworks. I feel like with Bootstrap you could really crank out a web app, without having to do much presentationally.
The navigational aids also seem really helpful and the default typography and whatnot does look quite nice.
https://github.com/stouset/twitter_bootstrap_form_for
Also, if you are a simple_form user then check out:
Bootstrap uses LESS. Not everyone is a fan.
Bootstrap has more features and, in my opinion, nicer buttons and alerts.
Foundation is built to be responsive and to work great with mobile and tablet devices.
They don't feel right. The 'hover' state should be the 'down'(active) state; the hover state looks like button is pushed in. The hover needs some kind of glow or subtle gradient change, then when the button is clicked it needs to look like it's pushed in. It's strange they've done this because the buttons on twitter.com feel correct and get pushed in like real life buttons.
Also the fade animation on the button totally unnecessary, it just animates for the sake of being animated, it doesn't serve a purpose. Animations need to serve a purpose, such as the Mac App store whizzing purchased apps into the dock.
Everything else is pretty fantastic, but those button states make my skin crawl, they're the first thing to get changed if I'm using bootstrap.
Here's a list of sites built with it: http://builtwithbootstrap.tumblr.com/
The bootstrap elements are particularly well suited for documentation pages - see http://trisul.org
https://github.com/twitter/bootstrap/blob/2.0-wip/docs/index...
