Beyond the CSS Style Guide
Consumed => “CSS Audits: Taking Stock of Your Code” by Susan Robertson on A List Apart.
=> My value add (i.e., left a comment)…
re: “you may turn this document into a style guide. Another thing to consider is how often to revisit your audit to ensure your codebase stays squeaky clean. ”
I really enjoyed the article and found it quite helpful. Thanks. That said, an audit, by definition, is reactive. Again, great stuff here but putting out fires isn’t as effective as preventing fires That is, it would be great to hear more about being proactive.
For example, yes a style guide is great to have, but having one and getting a team to buy in, use it, and evolve it, are two very different things. In short, speaking for myself, I think it would help to hear more about identifying and solving the organizational issues that directly and indirectly impact code / product quality.