Your Styleguide is an API

If you’ve ever used a styleguide, chances are you used one styleguide for one website. But what happens when you have one styleguide and more than one website? In this session, I’ll show how my team turned a styleguide for a large government project into a dependency of the website rather than a deliverable of the website. You’ll walk away from this session with a framework for thinking about styleguides and how to use them in a CMS-agnostic way (using tools like Pattern Lab, Twig, Semver, Drupal) to support a multi-channel (or multi-site) publishing platform that is all styled from a single project. I’ll also cover some basic implementation strategies and touch on tools, so you’ll have practical next steps if you want to try this out yourself.