Opinions on CSS Frameworks
# June 25, 2013 at 6:32 am
I’m assuming most people here are freelancers who don’t work in teams.
When you have several people working on the project together, frameworks become crazy valuable, because everybody talks the same language, follows the same conventions, etc. Plus frameworks continually evolve, so when one of the team members figures out a better way to do something we can fold that right into the framework for the current/next project and even past projects.
Plus, when someone new joins the team, we have complete documentation and training to hand over to them to get them up to speed right away.# June 27, 2013 at 3:34 pm
@JasonRCI Second that, I discovered this when I started working in agencies..# July 2, 2013 at 1:11 pm
I didn’t like any of the existing frameworks out there, so I just created my own framework.
[Cascade Framework](http://cascade-framework.com/ “Cascade Framework”) combines a very light footprint with feature richness bacause of an ultra-modular OOCSS based architecture.
With [Cascade Framework](http://cascade-framework.com/ “Cascade Framework”), **YOU** choose whether to use, replace, overwrite or just exclude features like grid classes, responsiveness, color scheme, typography, table layouts, etc. That allows you to avoid the bloated mess you get with most other frameworks out there.
You must be logged in to reply to this topic.