Recently I walked into project that used Twitter bootstrap for the initial CSS. A prototype was built, relying on the bootstrap CSS, and from that point on it has been hassle to work with the CSS.<p>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.<p>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.<p>Am I missing something? What is intended after 'boot'? am I really supposed to replace these global styles manually?
I'm excited about the form states in this release as well as the bug fixes.<p>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 <a href="http://smacktweets.com" rel="nofollow">http://smacktweets.com</a>. The header bar alone, while extremely simple, is so much better than what I probably would have done on my own.<p>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.<p>Skeleton (<a href="http://getskeleton.com/" rel="nofollow">http://getskeleton.com/</a>) 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.<p>Just wanted to say thanks for putting this out and for the community continuing development on it. I'm really enjoying it.
I would wait for v.1.4.1 before upgrading.<p>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).<p>[1] - <a href="https://github.com/twitter/bootstrap/issues/538" rel="nofollow">https://github.com/twitter/bootstrap/issues/538</a>
I'm really loving how fast they are pushing updates and just using Bootstrap in general. I've already used it for my startups new website (<a href="http://www.sponsorfied.com" rel="nofollow">http://www.sponsorfied.com</a>), which turned out pretty awesome, and the time I saved by using Bootstrap was pretty incredible.<p>I'm definitely using it for any side projects or sites I need to toss up without spending days on them.
I'm impressed with Bootstrap.<p>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.<p>The navigational aids also seem really helpful and the default typography and whatnot does look quite nice.
If you are a rails user and want your form helpers to spit out the bootstrap form markup check out:<p><a href="https://github.com/stouset/twitter_bootstrap_form_for" rel="nofollow">https://github.com/stouset/twitter_bootstrap_form_for</a><p>Also, if you are a simple_form user then check out:<p><a href="https://github.com/rafaelfranca/simple_form-bootstrap" rel="nofollow">https://github.com/rafaelfranca/simple_form-bootstrap</a>
I like almost everything about bootstrap, except for it's button states...<p>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.<p>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.<p>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.
Bootstrap is awesome. I've built 3 prototypes based on Bootstrap and it is such a leap forward if you are not design inclined.<p>Here's a list of sites built with it:
<a href="http://builtwithbootstrap.tumblr.com/" rel="nofollow">http://builtwithbootstrap.tumblr.com/</a>
I highly recommend Twitter bootstrap combined with the generator Stasis (stasis.me) for people rolling out new static websites.<p>The bootstrap elements are particularly well suited for documentation pages - see <a href="http://trisul.org" rel="nofollow">http://trisul.org</a>
Sadly there is not change log. I just scrolled through the doc and could not find any features. All this seems to be from 1.3.0 is bug fixes which make it a patch? Please correct me if I'm wrong and I missed something awesome ;)
What has kept me from using this is the lack of media-queries. After investigating the gh repo it looks like there is a 2.0 branch with a responsive design already being built. I'm not sure what keeps them from releasing it but it appears to work.<p><a href="https://github.com/twitter/bootstrap/blob/2.0-wip/docs/index.html#L121" rel="nofollow">https://github.com/twitter/bootstrap/blob/2.0-wip/docs/index...</a>