Style-guide-driven Development

conference: Drupal South 2015, Melbourne

Structure of component library: base, layout, components: element, modifier, state, skin

We suck at what we do. We know the websites we build need excellent front-end performance, full accessibility, compelling designs, and reusable parts. We learn. We plan. We build. We make a mad scramble to finish on time and deliver a product that falls short of what we know we could have achieved. Every. Single. Time.

But things are starting to change. Web development is undergoing a monumental shift in methodology as it begins to integrate agile development, a proven way to successfully build software. And it turns out integrating agile development with web development is actually very simple. It's called style-guide-driven development.

In this session, we will discuss why front-end development has started to be turned inside out these past few years. And how to make sense of the eleventy-million new tools that have been released. Most importantly, we'll discuss the two requirements for Style Guide Driven Development: component-based design and automated style guides.

Slides