4 ms·
I used to use Blueprint all the time, but found it had many inconsistencies and corner cases -- primarily its vertical pacing of type, but also in its grid. The
by jemmons 18y ago
I used to use Blueprint all the time, but found it had many inconsistencies and corner cases -- primarily its vertical pacing of type, but also in its grid. Then, when I'd go to fix these issues manually, I'd always end up befuddled and foiled by its implementation overriding me.
My rules for judging CSS frameworks are: "They should pick something, do it perfectly, stay clear of everything else," because fixing just an aspect of someone else's CSS is such a punishing experience. Blueprint fails all three of these requirements, bundling grid, typesetting, form, print, and templates libraries together, not implementing them all perfectly (well, duh), and not staying out of my way when I don't need one or more of these features.
My current favorite grid implementation (and attendant design philosophy) is OOCSS. I highly recommend everyone check it out and absorb the knowledge presented there: http://wiki.github.com/stubbornella/oocss http://wiki.github.com/stubbornella/oocss