PUBLIC MARKS from Spone with tags "best practices" & code

When architecting CSS for a large scale project it’s a common aim to abstract visual patterns for re-use, DRY out code and normalise our designs as much as possible. However, for rapidly changing projects, I’m no longer convinced those principles should necessarily be followed to the nth degree, nor that they offer the biggest wins. This post describes what I consider the most advantageous practices and approaches when authoring CSS for a rapidly changing, large scale web project.