Here you a have a collection of cool frameworks to create CSS layouts.
I don’t want to enter into the debate about the use of these frameworks.
So please don’t write comments like “you are totally missing the point, the grids are unuseful…” or “i prefer to use my own hand-code for development” and blablabla…
If you don’t like frameworks, please, just skip this post.
I would like to have a constructive post about the main differences and the most important advantages\disadvantages.
Personally i love the 960 grid system but i like also blueprint and malo.
In general when i use a framework is because i can have a rapid prototype of the final website, because there are easy to remember CSS classes and because i can have a cross-browser object without headaches.
What do you think? Which is your favorite and why?
Â
GENERATORS:
Reset CSS (Eric Meyer)
Â
Â
Author's website
About the author
Hey, thanks for posting Simpl.css. If anyone out there wants me to do an explination of it just let me know. and spread the love!
http://www.simpl.romack.net
shaggy: it would be so cool if you had a easy tutorial of the use of it!
I’ve been using Blueprint CSS for about a year and a half now, and it has completely changed my life (professionally). I like Blueprint because it’s written to be easily modified and it’s simple enough that I don’t feel like I’m learning a whole new language just to use it’s “powerful” tools (wether I need them or not). Half of the time I modify almost all of the typography styles or don’t use the grid at all. But at least its modular and simple enough that I can do that easily. Blueprint was so much easier than trying to wrap my head around the YUI library.
I’m a designer who is totally self-taught HTML and CSS. Some people criticize frameworks for being some kind of cheat that keeps you from learning CSS. But in fact, I feel like it’s the exact opposite. I’ve learned just as much from the Blueprint framework and the work it’s based on than any book or website tutorial. And most importantly, it gives me some best practices to follow that work every time. It takes much of the frustration and pain out of cross-browser coding.