Working at Twitter the last two and a half years has been incredible. Both Jacob and I have worked with a lot of amazing people on some pretty amazing projects, but nothing has been more enjoyable or rewarding than working on Bootstrap. Despite us leaving Twitter to go our separate ways, we’ll both be continuing our work on the project.
Bootstrap will remain a Twitter project on GitHub for the time being, but we’ve realized the project has grown beyond us and the Twitter brand. It’s a huge project playing a pretty awesome role in the web development industry, and we’re excited to see it continue to grow. To that end, we’ve begun working to move Bootstrap into its own open source organization. It will take time, but we’re dedicated to making it happen.
In the coming weeks, we’ll release another bugfix update (2.1.2) to address a few things, and then it’s full steam ahead on improving some key areas of the framework (modals, carousels, customizer, etc). We’ll share more info on those updates as plans take shape.
Until then, we have nothing but love for Twitter and the web development community. Thank you all so much for everything.
Two weeks later, we’ve closed another 500 issues against Bootstrap. That includes all the dupes—you nerds like reporting typos—and invalid issues that don’t end up making it on the official release milestone. But, what’s awesome is that we have 2.1.1 ready to rock with 73 bugfixes.
Head on over to https://getbootstrap.com/ and get your fix, or download the latest master ZIP right from GitHub.
Here’s the rundown:
- New feature: alert text. We documented these new classes, like
.text-success, at the bottom of the Typography section along with the long undocumented
- Fixed a lot of typos in the docs. Spelling is hard.
- Made the
.box-shadow() mixin more durable. It no longer requires escaping for multiple shadows, meaning you can easily use variables and functions in them once again.
.dl-horizontal dt and
.horizontal-form .control-group to better handle the increased font-size.
- Dropdown submenus improved: now you only see the next level, not all levels, on hover of the submenu toggle.
- Clarified jQuery and Bootstrap template requirements in Getting Started section.
select now utilizes
.lead now scales up from
@baseFontSize instead of being a fixed font-size and line-height.
- Fixed the vertical three color gradient in latest Firefox.
- Reordered some variables that caused errors in certain Less compilers.
There’s a bunch more, so do run through the 2.1.1 milestone when you can, but those are the big ones.
More bug fixes, more feature improvements. 2.1.2 will be coming shortly and we’ll work to improve a handful of issues that we punted on for 2.1.1. Beyond that, we’ve scoped out the next few releases around a set of key components like modals and carousels.
We’ll continue to add new features as appropriate, but we’re primarily focused on improving current functionality in the next few months.
Roughly two weeks ago we upgraded the blog to use Jekyll and GitHub Pages instead of WordPress. When we did that, we forgot about the RSS feed. A few awesome folks noted we were missing it and so we’ve added it back. Unfortunately it’s not the same URL, but it’s there nonetheless.
Here’s the URL for the new feed: https://blog.getbootstrap.com/feed.xml.
It’s also in the
<head> of the blog’s pages, so entering just the root URL should resolve fine for you in most RSS apps. Again, sorry for the oversight and please continue to let us know if we can do anything else to improve the blog.
After a smaller 2.0.4 release, we’ve got another huge update that resolves tons of bugs, improves the flexibility and durability of our code, and introduces a few awesome new features. It’s a big release wrapped in a brand new set of docs and we couldn’t be more stoked to launch it.
New docs, affix plugin, submenus on dropdowns, block buttons, image styles, fluid grid offsets, new navbar, increased font-size and line-height, 120+ closed bugs, and more. Go get it.
In addition to sporting a fresh visual style, the content of our docs has been overhauled once again. Good-bye long-winded marketing copy and multiple columns, hello succinct and directive single-column documentation. We’ve got a new tagline, new layout and navigation, and (more) clearer examples.
Key changes and new features
We had higher expectations for the number of new features in 2.1, but we toned it back to get this release out the door in a manageable form. We’ve still added some great new features and fixed tones of bugs, so here’s a brief overview of what’s new.
- Submenu support on dropdowns. We avoided this for some time as we thought it would unnecessarily complicate things, but we’ve backtracked on that and opted to add them in. See the docs for more info.
- Block level buttons. Add
.btn-block to a button to make it full-width.
- State classes on table rows. Better convey success, warning, and error messages in tables.
- Improved disabled states on navs and dropdowns. Where by “improve” we mean actually present—just add
.disabled to the
- The navbar component is now white by default, with an optional class to darken it. In order to have two options for the navbar, light and dark, we needed to have better defaults. Having a lighter default navbar means fewer lines of code as we don’t need to override anything for the basic navbar functionality and the override it again to restore the default styles. Missing the black? Just add
.navbar-inverse to get the dark gray navbar back.
- Improved prepended and appended inputs. No need to place the
.add-on on the same line of code (sorry about that by the way). Break them up as you like and they’ll still stick together with some crafty
- New base font-size and line-height. 13px/18px is out, 14px/20px is in. This also has changed the size, line-height, and margin of our heading elements, buttons, and more.
- Added variable for navbar collapse trigger point. Instead of a fixed pixel width of
980px for triggering the collapsed navbar, we now use a variable so you can customize it for your projects.
- Fluid grid offsets. Thanks to our contributors, the fluid grid now has offset support to match our fixed (pixel) grid.
- Fluid grid system variables are no longer fixed percentages. Instead, they are calculated in LESS with
percentage() based on the default, fixed-width grid variables. Math!
- Removed LESS docs page. We will no longer document variables and mixins in two places—rewriting that stuff was painful and took too much time. Instead, just checkout the .less files.
Once again, we couldn’t have done this without all you nerds out there supporting us with your contributions, bugfixes, and feature requests. You keep this project going strong and we thank you deeply for your support.
For the full changelog, visit the GitHub wiki page and the 2.1.0 milestone. We’ve already begun slating things for 2.2, but currently have no estimates on when that will be released or what exactly will make it in. We also may do a 2.1.1, but again, no promises at this point. Live in the now!
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.