It's pretty great for that. It allows you to do complex layouts a little faster while keeping them readable. I'll be using it for any future sites I design.
isn't the idea of CSS to separate design from semantic content? putting <div snap="span-10"> (spans 10 grid columns) in your HTML entirely defeats the purpose.
what about print css, phones, etc, etc.? what about using html as a data feed (e.g., for your JS, microformats, etc.)? BluePrint is clearly written by and for designers, rather than IAs.
How anyone here compared BlueprintCSS to YUI CSS foundation?
In an interview linked from the wiki, the creator said:
"The first CSS framework I checked out was the Yahoo User Interface Library, but found it to be way too bloated for what I want from a designers framework."
YUI css is designed to do a few layouts well and make other layouts possible. Its not bad, but it is clunky to work with and a pain if you don't fit one of its proportional models precisely.
Blueprint is more logical and conceptually easier to understand - everything is put on a flexible grid and you choose how many grid units you want to use for each layout block.
I dig the rest of the YUI toolkit, but compared to blueprint, YUI CSS feels like a hack.
