Think about the last time you had to work with CSS that someone else wrote. Could you understand their intention by reading the CSS and markup without loading it up in a browser? What about code that you wrote over a year ago?

Creating a good experience doesn't have to be limited to our users. There are CSS techniques we can apply to provide usability to our fellow developers.

Years of building CSS frameworks has given me the opportunity to see which approaches fail when it comes to writing CSS intended for other developers. At my company, we've successfully settled on a CSS paradigm recently described by John Polacek asExpressive CSS.

I'll explain Expressive CSS through real-world examples that demonstrate how this technique has helped us build layouts faster with less bugs, less duplication, and a better understanding of how style rules are being applied.

Developing a "best practice" is an iterative process; we already have great ideas like SMACSS and OOCSS, but it's important to keep the conversation going so we can build on these concepts. Come with an open mind, and I'll show you how a class-heavy approach, while somewhat controversial, has made us a happier and more effective development team.

About Speaker:
Coming soon.

Twitter | Github | Website