Twitter Bootstrap 2.0 pre-release demo
bootstrap.io
bootstrap.io
If you want to look at the current status of 2.0 and help test the release, please look at the 2.0-wip branch: https://github.com/twitter/bootstrap/tree/2.0-wip
The team expects to release something in a few weeks.
* styling of default elements (like table) interferes with other styles
* inconsistent use of variables
* encouraging users to define columns with html classes (span4, offset6) instead of using less to apply the rule to the html.
* completely incompatible with JQuery UI (they had an open bug about it with some workarounds)
In the end, I ended up just picking a few good ideas out of it. It looks great and it's probably ok for a certain class of sites but be aware of the limitations as well.
That doesn't, however, mean they don't inherit from the style of the base element. Which they will, no matter how they're classed or ID'd, if the base elements have been styled in CSS.
It is still a bit in flux (ie: they just renamed a bunch of css for alerts and tables), but if you don't mind tracking the progress (made easy with your own git branch), it is a great basis to start a website from.
Edit: Actually, I take it back as there are still hardcoded colors and the assumption that you are using white as the text. Would be nice if it was based off a few variables instead.
color: @white;
in the various navbar rules. It would be great if there was a single variable: @navbarTextColor: @white;
and then all the rules could include: color: @navbarTextColor;
which is essentially what I've ended up doing.bootstrap.io isn't actually running the most up-to-date documentation: it's missing the new style dropdowns, as well as the JS builder and a few plugins (typeahead, carousel etc).
A lot of great stuff going on in the 2.0 version. Excited for it's release.
pretty awesome. very small when minified, even without less.
love it!
But you'll find some indication of the work done on the road map: https://github.com/twitter/bootstrap/wiki/Roadmap
The elements are nice to have in Bootstrap but we are building our own elements on Foundation's solid platform and feel better about it over the long term.
In terms of implementation I've only used TB, and it was simple, not very intrusive.
Personally, I used TB because I needed something that looked ok but without expending much effort
That said, I hope Bootstrap 2.0 nails responsive design. I think we should be checking our progress on mobile devices as we develop, not drop in a mobile solution at the end and hope it works. Responsive design is the hard part whereas look-and-feel CSS is more trivial to drop in.