Theming for Drupal is easy, right? You have some designs, you have some functionality, you layout your page, throw in some breakpoints, add some color, add a little interactivity, and your done. Then an events calendar gets added. No big deal. It's basically like the original design with a couple differences. So you add some selectors, maybe tweak them a bit, put in some comments, and everyone is happy. Then the logo gets changed, and the header needs to be rearranged, and while you're at it can you change the color palette to match the new logo? And oh yeah, we need an additional sidebar too.
By this time, your once simple, elegant theme has gone sideways. Your files are too big, your class names no longer make sense, your selectors are too long and too specific, and you are continually overriding styles. And the more that gets added to the site, the worse the situation gets. You need to be modular; you need to be organized.
The combination of Sass, organized partials, a comprehensive style guide, along with some old fashioned planning and common sense can keep your project organized no matter how large it grows or how many new features are added. In this session, I'll cover a strategy that helps keep your theme styles more organized, efficient, scalable, and easier to maintain. We'll cover Sass, SMACCS-like file partials, styleguides, the Drupal styleguide module, and how to use them in cohesive strategy to keep your Drupal theme DRY, clean, and organized. This session is intended for beginners. It's about being organized, it's not about code. Experience with Sass, Compass, and Drupal are not necessary to gain value from this session.