18th
Blueprint vs 960.gs
I’ve finally been able to use Blueprint for one of the my projects at work. I must say its quite a nice CSS framework to use. I’ve previously been using 960.gs for a couple of my previous projects for layout but it left me wanting more. Thats were Blueprint has been able to come in a fill in the gaps so far. It just gives you a starting point thats very sensible. I use to start with zero styling and build from there but I found myself using some very common defaults for lots of projects, so why repeat yourself?
Here’s a list of what I like about Blueprint:
- Great documentation - its all in the css files so you have to be comfortable with reading css syntax.
- Basic Typography styling - includes stuff like header tag formatting, loud and soft etc etc. Nice mix, usually should be able to meet most of your needs. I’m especially into standards and minimalist swiss design so I love it!
- Basic Form styling - always hating doing these. Still don’t know whats the best way, but at least these help.
- Nice grid flexibility - you can recompile (ruby) the grid.css to support any grid with and gutter and number of columns.
What happen to the good practice of separating content from layout?
Blueprint is a great tool to add to your arsenal as a web developer. However I somehow have this feeling that adding all this extra classes which is actually formatting/layout/styling to the content is bad. Blueprint definitely causes divitis but I think complete separation is too idealistic.
