News for hackers. Stuff that matters.
Re:Blueprint: A CSS Framework by aditya on Wednesday April 01, 2009 @12:01AM (#541350)
My only issue with blueprint and compass was that it seems overly complicated for what I'm trying to do so far. I'm not a CSS guru so maybe I'm missing the point but is there a good reason to use a CSS framework on medium sized projects?

Or, rather, is there something inherently nice about using grids for translating design to markup? It just seems like the framework adds a lot of code and styles that you're never going to need or use on small-to-medium sized projects. Thoughts?

Re:Blueprint: A CSS Framework by vaporstun on Thursday April 02, 2009 @10:52PM (#544419)
I like to use it for the simple fact that it automatically overrides all of the default styles. So no more Times New Roman, and all of the header tags look decent without much modification.

That way, I can usually use most of their defaults and can spend more time coding.

So it is really nice for me on small projects where I just want it to look decent without much effort.

Re:Blueprint: A CSS Framework by erlanger on Wednesday April 01, 2009 @05:32AM (#541606)
> but is there a good reason to use a CSS framework on medium sized projects?

No, not really.

> is there something inherently nice about using grids for translating design to markup?

Only if you want your markup tightly coupled with page layout.