Your Styleguide is an API
summary
Turns a living styleguide into a reusable dependency for many sites by publishing a built artifact and importing it with composer require, using Pattern Lab + Twig as the component system and Drupal 8 as the consumer. Implements a custom theme engine and glue module that map atoms/molecules/organisms to Drupal data, uses semantic versioning to avoid breaking changes, and prototypes a styleguide-as-API that accepts POSTed data and returns minified HTML (with CSS/JS) plus a symlinked fallback for offline failover.
AI-written summary · about
chapters (20)
- 0:00Introduction and welcome
- 1:29What is a style guide
- 3:37Living style guides explained
- 6:10History of style guides
- 7:36Component driven development
- 12:35Style guide as API foundation
- 15:50Front-end developer roles
- 17:14Style guide as a dependency
- 19:02Glue code and integration
- 21:12Example glue code walkthrough
- 24:27Molecule implementation details
- 27:03Backward compatibility in style guides
- 29:12Complexity and reality check
- 29:58Why style guides are APIs
- 31:22Benefits of style guide APIs
- 32:29API example with anchor tag
- 34:19Full page implementation
- 37:33Client presentation story
- 39:21Summary and key takeaways
- 40:48Q&A session
related talks
49mLiving Styleguide in your Drupal projects: Benefit from component driven design.
35m"The Step After Styleguides"
42mThe Dream of Styleguide Driven Development
48mA practical guide to style guide driven development
42mDesigning Inspired Style Guides
45mMaintainable Style Guides
01h 05mStyleguide-Driven Development
34mCreating Living Style Guides