A Designer and Developer Walk into a Bar…
summary
Hashicorp’s Helios design system ships a concrete process: audit existing code and Figma, write a CRD (component requirement document), engage product ambassador audits, spike and iterate, then perform simultaneous Figma and code releases with docs as code. Accessibility is built in from day one (assertions that break builds if ARIA is missing). Tech: Ember apps and Ember engines (one React app consumes artifacts). Outcomes: 38 components, 325 design tokens, three complex patterns, ~3,400 code instances and broad internal adoption.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:31Design Systems
- 13:52Designers vs Developers
- 17:04Process Overview
- 18:50Component Planning
- 27:46Ambassador Engagement
- 29:23Meeting Cadence
related talks
19mYou've Built a Design System - Now What?
14mRethinking Designer-Developer Collaboration
20mDesign Systems for the Rest of Us
21mDesign Systems 101: The Developer Approach to Better Frontends
27mUsing Ember to build a universal design system
57mDesign Engineering: The next era of Software Design
46mBuilding & Managing Design Systems
49mExploring the Anatomy of Design Systems