Tuesday, August 14th, 2007
Why did Olav create it?
After reading an article by Jeff Croft on frameworks for designers, I started looking at the existing CSS frameworks, trying to find one that was right for me.
Never again was I to repeat the tedious task of creating a grid from scratch, defining default typography, or battling with inconsistent default browser CSS.
Hereâ€™s some of the features Blueprint brings to the table (not
, mind you):
- An easily customizable grid
- Some default typography
- A typographic baseline
- CSS reset for default browser styles
- A stylesheet for printing
- No bloat of any kind.
Many people have gotten excited about it, includein Mark Boulton:
What a list! Now, if you just put the first point aside, the core features of Blueprint bring together some of the best typographic design thinking on the web over the past year or so. Eric Meyerâ€™s reset code is in there, Richard Rutterâ€™s Vertical Rhythm theory, Jeff Croftâ€™s ideas on managing a CSS framework.
Going back to the gridâ€”and this is what really interests meâ€”Olav has used Khoi Vinhâ€™s theories and practice on grid design to great, practical use. What is so important about this CSS framework to me is that it has been designed to solve a design problem, not a technical problem. As all great systems, it has been designed to help and guide the designer. As you can tell, Iâ€™m already a big fan.
Posted by Dion Almaer at 12:40 am