I recently built a new site using the Blueprint CSS framework and was once again astounded by how little time I spent on fussing with the design of the site and how much I actually enjoyed the process–something that just didn’t happen before I started using Blueprint.

Much to my surprise, one of my most popular blog posts has been First Impressions of the Blueprint CSS Framework. People continue to read it, cite it, and comment on it, even though it is horribly out of date.

The post was written a year ago using the 0.40 version of Blueprint, which is currently at 0.7.1 as this is being written. And I wrote this post as sort of a test, and didn’t intend it to be a Blueprint tutorial in anyway. I am not a CSS guru, which I thought might make my experiences with Blueprint more interesting, as someone who might particularly benefit from this framework.

Given that this post continues to be cited, however, I feel that I’m doing a disservice to the Blueprint project. So, I want to try to set the record straight in this post.

Everybody else has been writing about the Blueprint CSS framework lately, so I decided I would too. In my case, I have spent several hours using it to create a layout for a customer, and in the process, I feel I have learned a lot about Blueprint’s current strengths and weaknesses, and a little more about CSS best practices as well.