Treat your custom CSS as contrib
Getting your Drupal to be pixel perfect is hard. In fact, it's probably four times faster to write the logic
of a page, in comparison to the time it takes to get it's markup right. Not to talk about making it responsive.
If you've seen my presentation about The Gizra Way you noticed we take pixel perfect very seriously.
One of the tools that helps us getting the markup fast, correct and in a way that would allow us to communicate with the client is Jekyll - the static site generator. Here's the idea in a nutshell:
- Using Jekyll we can concentrate on a clean markup
- Using Grunt we compile the SASS, and are able to push the the HTML into Github pages - where the client can easily see and interact with the final markup
- The CSS produced by Jekyll is treated by our Drupal application as contrib. This means we have zero custom CSS in our theme. Seriously, absolutely no custom CSS in your Drupal theme!
- Any change to the CSS can be done only in a single place, which is Jekyll