Today we’re shipping Ratchet 2.0.2. This patch release is full of bug fixes, refinements to our docs, and improvements to our build tools. Check out the detailed changelog on the release page.
We’re going to be working on the v2.1.0 release next. This will mark the first feature release for Ratchet 2. We’re really looking forward to developing more components that help you build awesome apps.
Today we’re pumped to release Ratchet 2.0.1. This release focuses on CSS bug fixes and further improvements to our docs and build tools. Be sure to check out the detailed changelog on the release page.
Since releasing Ratchet 2.0.0 we’ve reached over 7,000 stars and over 650 forks on GitHub! Thanks to all our contributors and the rest of the community for helping make this thing awesome.
Today we’re stoked to introduce the brand spanking new Ratchet 2.0. The mobile-only framework for building mobile apps with HTML, CSS, and JavaScript has been overhauled with new features, documentation, and a brand new home.
New home
First, you’re not crazy—Ratchet has moved! It’s now a part of the Bootstrap organization on GitHub. Ratchet 2 was lovingly crafted by @connors, a good friend to Bootstrap’s creators. Given our collaboration in person and the ideas we have for the future of both frameworks, it makes perfect sense.
New docs
Second, the Ratchet docs have a new look!
Things should seem pretty familiar, but we’ve added a bunch of new content and some key new features. Chief among them are the ability to show Ratchet on an iPhone and Android and three awesome examples to show it all off.
Feel free to download, remix, and extend these example apps—they’re all part of the new Ratchet docs.
Really, what’s new?
We’ve got tons of new and improved features for Ratchet. Here’s the rundown:
New Ratchicons! An icon font dedicated to Ratchet, with support for both iOS and Android.
New themes for iOS and Android! That’s right, Ratchet has a brand new base coat with optional themes for iOS and Android. Now your app can look right at home on either platform.
New card wrapper. Wrap any content or Ratchet component in a card for that classic inset card look.
CSS has been rewritten to utilize Sass, compiled via Gruntfile.
Improved table views, now with support for lists featuring images and icons.
Updated class names for buttons, badges, and more to match the Bootstrap nomenclature.
It’s a huge release that’s been a long time coming. Head to the new Ratchet docs to check it all out in person, and be sure to view those new examples from your favorite iOS or Android phone.
Be sure to check out the GitHub milestone to see a more complete changelog of what’s new.
What’s next?
Just like Bootstrap releases, up next for Ratchet will be documentation improvements and bug fixes as feedback rolls in. Without committing to a date, we also want to add support for iPad and Android tablets.
As always, if you find a bug or want to suggest a feature, just open an issue or a pull request on GitHub.
Today we’re releasing Bootstrap v3.1.1. As our first patch release for the v3.1.x release series, we’ve focused on CSS bug fixes, documentation improvements, and further refinements to our build tools. See the included changelog for more details.
Today we’re stoked to ship Bootstrap v3.1. We’ve got a handful of new features, plenty of bug fixes and improvements, and updated build tools.
New docs
We’ve made tons of changes across the board, most notably to our documentation. Just like v2.1 brought a brand new design, v3.1 overhauls the docs to refocus on the actual documentation rather than the chrome around it. Our new homepage restores the quick run through of key features and showcases some awesome examples from the Expo.
Official Sass port
The best part about v3.1 is that we’re shipping with an official Sass port. A few weeks ago we moved over the most popular port on GitHub and made it official—Bootstrap is now available in Sass. Rather than bloat the main project with support for Less and Sass—and all the documentation for both—we’ve kept them separate for the time being. Prominent links in the docs are included though, so enjoy!
New examples
We’ve added three new examples: Blog, Cover, and Dashboard. Each example provides a single page of awesomeness for you to quickly get started on a project built with Bootstrap. They’re responsive and ready to go.
Improved features
A handful of features that aren’t exactly new to Bootstrap have seen an update in v3.1:
Modals now include optional sizes
Dropdowns now have their own alignment classes for easier customization
Form feedback styles for validation states now include optional icons to reinforce color changes
All-in-all these make components more focused, more durable, and easier to work with. See the changelog included with the GitHub release for the complete list of new features.
Remote modal content
One of the more important improved features is for our modals. If you currently use the modal’s remote option, be aware this release may break your modals. Yes, this is a breaking change, but it’s first and foremost a bug fix that corrects a rather longstanding and overlooked error. Our apologies for any headaches it may cause, but it’s been missed in the last few patch releases.
See the #11933 pull request for details on the code changes.
New license
We’ve been talking about it for what seems like forever, but thanks to all our contributors and the core team, we’ve finally done it. As of v3.1, Bootstrap ships under the MIT license to allow as many people to utilize Bootstrap as possible. Thanks to all our contributors for helping make it happen.
Improved build tools
We’re constantly trying to improve our tools for developing Bootstrap and v3.1 brings a slew of updates to do just that.
We’ve switched from Recess to grunt-contrib-less for our compiler, giving us access to Less 1.6.x (as opposed to 1.3.x with Recess).
Our compiled code is virtually identical in formatting and organization thanks to CSScomb and some other Grunt-fu.
Tests also run a tad faster with the help of some magical caching and parallelization.
The web Customizer is now generated from a Grunt task, meaning we’ll never miss updating or adding a variable again. If you contribute to Bootstrap regularly, just run grunt and commit to update the page.
Heads up! If you develop Bootstrap locally, be sure to nuke your node_modules/ directory and run npm install before getting started with v3.1.
Download Bootstrap
Get downloading now, or see the list below for more information on what’s new in this release. Download it from GitHub or snag it from the CDN:
#11572: Add contextual background-color classes to match our existing text classes. (This also moves both sets of classes to the Helper Classes section of the CSS docs.)
#11675: Add .text-justify class to round out the text alignment classes.
#11836: Add new form control feedback classes to toggle icons for each validation state. Works on regular forms, horizontal, and inline.
While we originally wanted v3.1 to include RTL support, we decided to hold back on that for some potentially beneficial unreleased tooling. We’ll share more on that when we know more, but suffice to say it’s been bumped to v3.2.
CSS changes
#10951: Add outline: 0 to .modal to prevent a focus outline from appearing in Chrome for Windows.
#11107: Add @modal-backdrop-opacity variable for customizable modal backdrop.
#11266: Apply a pixel-based line-height that matches the height to date inputs for iOS 7 for proper vertical alignment of text in the form control.
#11302: Refactor the responsive utility classes to cut a few hundred lines of CSS (more context in #11214).
#11435: Prevent the double borders between multiple buttons in an input group.
#11561: Add float: left; to .form-controls within input groups to prevent IE9 from screwing up placeholder text and select menu arrows.
#11588: Scope font-size to only <p> elements in .jumbotrons and remove the super-sized line-height from the base class to avoid interference with sub-components.
#11676: Add -webkit-overflow-scrolling: touch; to modals for smooth scrolling on iOS devices.
#11744: Clean up some incompatible properties in forms.less: block level inputs no longer receive vertical-align: middle; unless necessary, e.g. in inline forms.
#11748: Updated .scale() mixin so that it accepts optional vertical scale as second parameter.
#11750: Reverts v3.0.3’s refactor to contextual table classes to ensure they work with striped tables.
#11757: Darken default navbar toggle bars to meet WCAG criteria.
#11766: Use @color variable in .button-variant() mixin to set background-color on .badges in buttons for proper default button badge styles.
#11741: Don’t set @headings-font-family to the same font stack as the <body>; instead, just use inherit for same default CSS.
#11786: Nest media queries within print utilities for mixin-friendliness.
#11790: With upgrade to Less v1.6.0, remove duplicate CSS generated from the nested .clearfix class and mixin by switching to &:extend(.clearfix all).
#11801: Use correct variables for grid containers.
#11817: Rework input groups to use the font-size: 0; and white-space: nowrap hack for a more durable component with regards to code formatting and custom font size changes.
#11829: Add .make-xs-column mixins to complement the recently added extra small predefined grid classes.
#11836: Along with the form validation update, we reset some key form and icon styles:
All .form-controls within inline forms are set to width: auto; to prevent stacking of .form-label within a .form-group.
Removes all select.form-control settings since those are now inherited by the above change
Removes the width: 1em; from the Glyphicons because it was virtually impossible to override.
#11841: Breadcrumb padding values now use variables.
#11859: Restore @dropdown-caret-color variable, but deprecate it.
#11861: Add @list-group-active-text-color variable for improved customization on active list group items.
#11868: Cleanup modal z-index values in modals.less.
#11990, #12159: Make range inputs block level and 100% wide by default.
#12073: Make order of component variations consistent throughout the repo.
#12164: Fix value of SVG font ID and removed hard coded value.
#12171: Ensure panel groups have a bottom margin since we nuke it on child panels.
#12247: Add and use .text-emphasis-variant() mixin for emphasis classes. Also updated emphasis classes to only apply :hover styles to linked content.
#12248: Add and use .bg-variant() mixin to generate background classes.
#12249: Add and use @modal-md Less variable for uniformity.
#12250: Remove print margins per upstream H5BP change, thus deferring to browser defaults, or users’ custom values should they set them.
#12286: Only remove appropriate border-radius from first and last tables or list groups in panels.
#12353: Scope table border reset in panels to first-child rows.
#12359: Reset min-width on <fieldset>s so they don’t break responsive tables and behave more like standard block level elements.
#12270: Add namespace .bs also to the event dismiss.modal.
Deprecations
#10370: Deprecated the .pull-right method for aligning dropdown menus. Includes the following changes:
Removed an old and unused pair of selectors that didn’t properly target the right-aligned navbar alignment of dropdown menus.
Deprecates the .pull-right alignment in favor of a more specific and unique class name.
Adds .dropdown-menu-right as the new alignment class. This is then mixin-ed into the .navbar-right.navbar-nav dropdown menus for auto-alignment (keeping the current behavior we have today).
Adds new ability to override that auto-alignment though with the new .dropdown-menu-left, which is mixin-ed in the same way to provide the appropriate specificity of an override. This should never need to be used except for within right-aligned .navbar-nav components.
#11660: Deprecate small and .small in blockquote citation in favor of footer element.
#12037: Move docs .html pages and assets into docs/ subfolder to clean up project root directory. Also moves .csscomb.json and .csslintrc to less/ to further clean up project root.
#12073: Make order of component variations consistent throughout the repo.
#12244: Move v2.x to v3.x migration docs to a separate page.
#12311: Expand information on how to handle overflowing content in navbars.
#12314: Add warning about modal markup placement affecting modal appearance/functionality.
#12345: Add note about printer viewport weirdness.
@connors
April 02, 2014
