Design Systems, Not Pages
summary
Page-based comps that can reach 25+ page comps give way to a component workflow that ships a living style guide built with Hologram and a Drupal-backed authoring layer called the Stacks module. Designers define lightweight visual rules and reusable widgets (headers, galleries, CTAs, content feeds) that developers implement as real Drupal prototypes; clients then assemble pages in the admin, producing interactive, responsive pages faster while preserving design constraints and reducing handoff rework.
AI-written summary · about
chapters (7)
- 0:00Introductions
- 0:33The death of static design
- 2:19Lessons from failed approaches
- 5:13Adopting a component system
- 9:39Design and CMS demonstration
- 17:28Client workflow and results
- 21:13Conclusion and Q&A
related talks
01h 00mBuild It Better, Stupid: Using Design Systems for Scalability
40mHow to optimise the workflow between designers and developers using design..
20mDesign Systems for the Rest of Us
18mDesign Systems in Practice
28mLet's talk about design systems
15mWhy You Should be Building Design Systems and CSS Architectures
29mWorkflow in the Age of the Design System
23mDesign Systems 101