We’re stoked to release Bootstrap 2.1 next week Monday at our first birthday party, but to make it a great release, we need your help testing it out.
While 2.0.4 was a smaller release, 2.1 is a much larger effort that closes nearly 100 issues and adds a handful of great features. You can see the full list of changes changes in 2.1 thus far by browsing the milestone on GitHub.
At a broad level, we’ve got overhauled docs. They’re drastically streamlined, redesigned, and better than ever. They even include a new page for getting started with an overview of the framework. New framework features include submenu support on dropdowns, block level buttons, and the affix plugin. We’ve made many other key changes, so be sure to check it out.
We’ll have a more complete list of changes with our release next week.
How to help
Just like last time, we’re pushing out a release candidate of the 2.1 code and docs. Here’s how you can help us out:
- Checkout the
2.1.0-wip branch, or browse the release candidate docs so you can easily load it up on devices and such for testing.
- Load up the new docs in your favorite, or your least favorite, browser or device and start testing.
If you’re submitting a pull request against 2.1-wip, be sure to read the Contributing to Bootstrap wiki page first.
Sorry about the database connection issues some of you may have seen in the last 24 hours. We’ve moved off WordPress for our blog and are now using GitHub pages and Jekyll. Jekyll is an amazingly lightweight and simple site generator from Tom Preston-Werner, cofounder of GitHub. Here’s why:
- Instead of a database, we have flat Markdown files.
- Instead of hosting code on servers from Media Temple or another hosting provider, everything is on GitHub.
- The posting process is as simple as writing a post and pushing the
It’s simple, fast, and pain free. We love it and encourage you to check it out in the future. Stay tuned in the next two weeks or so for more information on our next release. Until then, enjoy the updated blog.
Following up on the large 2.0.3 release a few weeks ago, we have a fresh update to address some documentation issues and basic CSS bugs. 2.0.4 includes around thirty closed issues and is our first version under our updated release approach (shorter, more concise releases).
As always, here’s a quick overview of some of the top changes.
type="button" to all dismiss buttons in alerts and modals to avoid a bug in which they prevent their parent’s
form from properly submitting.
- Added simple documentation to Base CSS for
- Added new CSS test to illustrate how the navbar, static and fixed, behaves.
- Clarified grid sizing copy to include mention of responsive variations.
- Reformatted the LESS docs page to prevent terrible table displays at smaller grid sizes.
- Miscellaneous typos and tweaks.
- Refactored forms.less to make our selectors more specific for fewer overrides and less code. Instead of a generic
input selector and various resets, we target each type of input like
- Form field state (e.g., success or error) now applies to checkbox and radio labels.
- Removed redundant CSS on
- Removed redundant
color declaration from the
- Added variables for dropdown dividers border colors.
.form-actions share the same
- Fixed some responsive issues with input-prepend and -append, notably with the fluid grid.
- Added special CSS to prevent
max-width: 100%; on images from messing up Google Maps rendering.
- Scope opened dropdowns to only immediate children to avoid unintended cascade.
- Similarly, scope floated-right dropdowns to immediate children with
.pull-right > .dropdown-menu.
.placeholder() mixin to use
& operator in Less for proper output when compiling.
- Added CSS3 hyphens mixin.
- Fixed a bug in IE7/8 where certain form controls would not show text if the parent had a filter opacity set.
For a full changelog, visit the now complete 2.0.4 milestone on GitHub.
After three large point releases focusing on massive amounts of bugfixes and documentation changes, we’re going to change up our release strategy to push out smaller, more frequent updates.
Releases with a hundred bugfixes are difficult to test, take much longer to ship, make changelogs super long and verbose, and have a tendency to introduce additional unforeseen bugs. In hindsight, our 2.0.3 release should have been a 2.1 given its sheer scope and the time it took to ship. Going forward, we’ll try to improve the frequency of the patches to get you better code faster.
So what’s next?
At the Twitter UK Open House in London last week, we said 2.1 was our next priority. While that’s still true, we’re backing up and rethinking it’s scope. Bootstrap 2.1 may end up much narrower in focus to help us ship it earlier. We’ll still tackle all the same issues and new features we originally planned for, but across more releases. In addition, 2.1 might not be our very next release as some of those unforeseen bugs have already cropped up.
To keep up with the community and improve code quality, we’ll be shipping more releases more frequently.
Questions? Mention us on Twitter.
There is a thread on the mailing list about how to describe Bootstrap and instead of isolating our response to just one email, I’ll just blog about it. As it stands, some folks are unsure how to describe Bootstrap to those unfamiliar with it. So here it is, straight from the official horse’s mouth.
Casually, it’s just Bootstrap. That’s noun and verb, for those wondering—Bootstrap the project and “to Bootstrap a project”, respectively. Formally, we call it Twitter Bootstrap, a change that came with v2.0.0. Previously we called it “Bootstrap, from Twitter” to emphasize the project over our employer, but it just became too verbose and awkward to say.
Related, the shorthand abbreviation we use is BS—not TB, TBS, or TwBs. I don’t know why, but this feels better than TB since that’s the name of an infectious disease and all that.
Another focal point in the email thread was the question of referring to Bootstrap as a framework. That’s accurate enough for sure, but also somewhat limiting depending on how you want to use it. Holistically, Bootstrap certainly is a framework (or toolkit or whatever) for prototyping and building production ready stuff on the web. That said, on an individual component level, Bootstrap is a tool for performing common web development tasks faster and easier.
So there you have it, a quick low-down on how we’re thinking and talking about Bootstrap. When it comes right down to it, Bootstrap is whatever you want to make of it, so dive in and see where it can help you out the most.