HTML5 Boilerplate 6.0 Released

drink

If you’ve been paying attention, you will have noticed that HTML5 Boilerplate 6.0.0 came out a few weeks ago. If not, it did. 6.0.1 has since been released.

It was a long time coming and I’m super happy to have it shipped. It was a lot of fun. Working with a project like this invariably means you have to do new things, so getting a major release out the door (where you have to touch everything) is a fun, educational experience. And, of course, working with the community is also pretty great.

Thanks!

Anyway, it was a big release and featured a lot of nifty stuff including:

  • We finally removed IE8 Support. This was a change that we had been discussing for some time and it was one of the first things I pushed through when I started taking a more active role on the project. Thanks to everyone for their help and input on this one.
  • We finally added a sample web app manifest file. That code had been percolating for years and it finally shipped.
  • We upgraded to Modernizr 3 and added a sample Mondernizr config so that people can do their own custom builds locally. Our Modernizr file is now created at build-time and I reworked the default detects to be more, er, modern.
  • We found out someone unaffiliated with the project had published the project to npm, so we took control of the package (thank you npm– support you were awesome) and published an official npm package.
  • And… lots of other great work by many contributors, including a ton of great work late in the process by Christian Oliff. Thanks to everyone for your contributions.

As a note, we still have an open bug that we’d love to get your input on– macOS – VoiceOver / Chrome announcing visually hidden text out of order · Issue #1985 · h5bp/html5-boilerplate. It’s an Apple bug with accessibility concerns that we’d like to work around.

As for what’s next… I’ll be opening up a couple of new issues for discussion this week, I think. So keep your eyes on the repo and join in on the fun.

Leave a Reply

Your email address will not be published. Required fields are marked *