Blueprint CSS 0.4 Released

Okay okay, So this isn’t exactly news. But it is news to me. Apparently I completely missed the realease (on 8/11) of a new version of Blueprint. Its got some nice new features including:

  • Font sizing now uses ems
  • A compressed version of the CSS is included
  • IE bug fixes
  • Incremental leading

You can read the release notes here and download the new version from the Google Code site:

These are all quite welcome changes. One of the first things that I noticed about Blueprint was that the CSS files were quite bulky. Much of that bulkiness was because the author was striving to make everything easy to understand. That said, not having a compressed version was a noticeable absence. The second thing I noticed was that all of the font sizes were in pixels. I didn’t really think on this too hard, because using pixel font sizes simplifies the grid dramatically. Looks like both of these issues have now been patched up.

I’ve been working with Blueprint since it was released and I have to say that I’ve been quite impressed overall. My first thought when I read about it was, “Oh great, another framework I have to learn.” But after taking a quick look at Blueprint, I realized that it is actually very straightforward and easy to use. It took very little effort to adjust my coding to it. Also, it made using a grid a lot easier because all of the grunt work (and math) was already done.

That said, the site that I actually designed using Blueprint bears very little resemblance to the original Blueprint grid. I ended up modifying quite a bit of the grid.css file to fit with my design better. I also overwrote most of the type styles from typography.css. I spent a good amount of time yesterday forcing sIFR to render my headers without messing up the grid. Now I’m wondering if it’s worth it on this site to try and mix in the new release of Blueprint. Perhaps I’m missed the point of using a framework? Oh well, at least getting started on the site was easy.

You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

Comments are closed.