It was just yesterday that I followed up a post by Jeff Croft that was inspired by the new CSS Framework, Blueprint (which, by the way was inspired by other web developers including LJWorld's work with the CSS grid - which Jeff was part of) and today we see the release of Blueprint 0.4! Wow, now that's agile development ;-)

The new version of Blueprint provides not only a lot of new features - such as typography styles based on ems instead of pxs, incremental leading and fantastic CSS buttons - but more importantly fixes a lot of bugs for those browsers who don't play nice. Looking at you IE, again. This means that not only is Blueprint a lot better than it was when it was first released (and it was damn good, with over 15 000 downloads!) but it means you can now use it for projects that really matter and won't just be living under the protection of your little sandbox of experiments.

Head on over to Olav's post about BlueprintCSS 0.4 to find out a lot more.

For now I'd like to point out the new logo that was unveiled with Olav's brilliant framework (with credit to all who helped of course). Though the new logo is not as brilliant as Olav's framework it's new and it was designed by myself :) Yay, I hear you shout.

Back story. I read that Olav wanted someone to design a logo for Blueprint and was a bit wary of whether I should design a logo or not. My initial idea was to do something with B and P, you know BluePrint but I quickly threw that idea out when I had visions of those beautiful glossy icons that Mac apps are generally released with. I set out to design a logo that literally had a couple of Blueprints in it that was glossy and beautiful to look at. Now I'm not saying that my work is better or even on par with what's coming out of Cupertino, I'm just saying I think it looks good and it's got the gloss that I wanted.

The typography started out a little different to what you see now. It looked like this when I first emailed Olav who then came back and said he didn't like the italics. Hmm, what did I do but add more italics. I felt the italics needed to be there to signify the forward thinking and movement of such a framework as Blueprint because I knew it would be developed fast (and look, it was) so I felt the italics had to stay and because the signal to noise ratio was favouring the latter too much I decided to throw out the "regular" Myriad type and went for Myriad Pro in Italics instead.

Anyway, so far my contribution has only been the logo but I do plan on contributing some CSS to the framework in the future, for now though, go check out Blueprint!