Thinking about CSS Architecture
With all my work at Yahoo!, I'd been thinking more and more about CSS architecture. I really sat down and took the time to analyze my process. What's the most flexible but straightforward way to do it? How does this fit in with the team process and how does this work in comparison to how other people are doing it?
I started making notes and eventually started writing up my thoughts. Was this going to be a full-fledged book? Just an e-book? Should I charge for it?
In the end, I found my time limited and my thoughts a little scattered. Over the weekend, I decided to do it more "blog" style and just write my thoughts on the various related topics that came to mind. Nothing to download, no store to go to, and no cost to you. The result is Scalable and Modular Architecture for CSS or SMACSS (pronounced "smacks") for short.
The intent is to have it be an evolving guide to CSS architecture for sites small and large. I will continue to work on the site, adding new content, and reworking existing content. I hope it'll be a resource for people to revisit and to refine their workflow for the better. More examples and more topics will be added over time.
Read, bookmark, and share: Scalable and Modular Architecture for CSS.