Styleguide 0.1.0



Our style guide is a living document. We lay some ground describing how we write our front-end code, keep it maintainable and ensure consistency. It's also a pattern primer allowing everyone in the team to easily create layouts without racking up new design and technical debt.

At the heart of our style guide is the desire to inspire experimentation. Challenge the norms. Design for peoples needs, not hypothetical users that might not exist. And eat our own dog food. If we are not using it, why should anybody else.

Move fast and break things, then move fast and fix it. Ship early, ship often, sacrificing features, never quality. Kyle Neath


We deploy with grunt deploy. This has a built-in cachebusting mechanism which is a Grunttask named purgecache. To set this up, you need to add a line to your .bashrc file.


Ask another developer for this key. If all fails and you're tearing your hair out why it isn't working, you can just comment out the purgecache command from the deploytask. You will still get to publish your changes to Google Cloud, but the caching on Cloudflare will not be purged. You will have to wait for it to timeout by itself.