3 ms·
> But it can also be a steep learning curve to figure out which framework you should use (or if you should use one at all) and then how to use it. I was really
by sumeeta 17y ago
> But it can also be a steep learning curve to figure out which framework you should use (or if you should use one at all) and then how to use it.
I was really looking forward to hear someone talk about this.
I'd like to know more about whether or not I should be using one at all. I've found CSS frameworks useful for mockups or prototyping, but I'm concerned that they're too heavy and general-purpose to use in production.
- tjpick 17y agoThat's what I've found too. The value of a css framework comes from showing you a structured way to achieve certain things, eg grid based design, font scaling. Once you know how to do that, you don't need the framework and it's probably just as easy to write the css directly. I've found the best way to use them is a starting point. By the time your site goes live you've stripped out the rules you don't need and customised the names of the classes etc so you can't see much of the original framework.
- nkh 17y agoHas anyone had any success using a framework, then removing the excess CSS with something like deadweight? ( http://railscasts.com/episodes/180-finding-unused-css http://railscasts.com/episodes/180-finding-unused-css )