!undefined

A curated collection of CSS, Sass, LESS and Stylus libraries.

By Chris Coyier, writing at CSS-Tricks. I largely agree with this list, but I’m not sure I get the assertion that you should put @includes after “regular” styles. If you’re ordering the CSS properties according to some specific scheme (e.g., Zen Ordering) then wouldn’t you want the output of your mixins to be in the right place? Other than that: some good rules to follow.

John W. Long, writing at The Sass Way. Tl;dr: read up on Snook’s SMACSS, and consider a similar approach in your Sass to help you avoid “the Inception problem”.

Dale Sande:

A developer never sets out with the goal of making a complete and total mess of things.

In some ways it’s a bit of a “me too!” post about how to organize your stylesheets (e.g., somewhat more opinionated than SMACSS, a lot more opinionated than OOCSS) but still worth the read, even if you’re feeling burned out on this kind of advice. Sande’s proposal is to take a bottom-up/inside-out approach to engineering your (S)CSS and to organizing your directories and files. The key take-aways for me were: (1) the opinionated directory structure and (2) treating `style.scss` as a manifest for everything else. (Though the second item is hardly a new idea, talking about it as a “manifest” is certainly an elegant expression of that idea.)

There are still some unsolved problems here, but they’re mostly social. (“How do I create the right traction for this work in a big organization? and/or reduce the friction for working within a big application?”)

There’s also a nice slide deck that goes along with it.

By Ian Storm Taylor. The whole “I work at a start-up and things change all the time so OOCSS doesn’t work for me” makes me a bit skeptical, but his example patterns are good case studies in how to use Sass’ %placeholder selectors with the @extend feature.

Great case study re: learning and using Sass; written for CSS-Tricks by David Walsh.

tl;dr:

Chris Eppstein’s big fat overview of what’s new and/or improved in Sass 3.2. I know a lot of folks excited about the @content directive, but for me it’s the %placeholder selectors. A big win all around.

I’ll say this though: you may want to audit what you’ve got first. (Those * html hack warnings you were getting before? Those are errors now.)