Overview
When you work with a large project or team over time, you either develop an airtight system for writing CSS or you spend half your day deciphering mystery code while fighting specificity battles.
After a lengthy process of investigating systems like BEM, OOCSS, SMACSS and more, we decided to take pieces of each and create our own. This talk is not the announcement of a new system we want you to use, instead it’s a deep dive into the discussions and decision-making that happened as we developed one.
You’ll walk away with an understanding of how you might go about choosing a CSS methodology or developing one of your own, and get a first-hand look at the complexity management problems faced by today’s larger projects.
Objective
A case study on creating and using CSS methodologies.
Target Audience
Front end developers, designers who code.
Assumed Audience Knowledge
Advanced CSS. Pre-processors like SASS, LESS or Stylus. A familiarity with an existing CSS methodology like BEM/SMACSS/OOCSS would be helpful.
Five things audience members will learn
- Why CSS is an increasingly complex problem.
- When Bootstrap stops being a good choice.
- How to manage CSS complexity.
- Creating modular CSS systems.
- Writing CSS that your whole team can understand.
