Your Guide to Making Scalable Design Systems
summary
A React design system for 30+ enterprise products that separates styling, HTML and framework glue, ships a modular SASS library, an icon set and a portal, and focuses on tiny atoms so products compose UIs without copy paste. Development uses React, vanilla HTML, Sass and Storybook for demos and eases an Angular port; a six‑developer six‑designer four‑tester team reports 70% of work is UX/product coordination, 30% coding, and finds faster, higher‑quality component delivery and easier non‑technical prototyping.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:30What this talk is not about?
- 2:01What problem we were trying to solve?
- 4:29Where / How to start?
- 6:32Internal Surveys
- 8:04Do not think just as a Developer.
- 10:06What exactly is the "Design System"?
- 13:02How to have scalability?
- 17:32Architecture
- 18:29Repos
- 18:51Naming conventions
- 20:12Flexibility
- 21:21Component Structure
- 22:31Styling
- 23:42StoryBook
- 25:15Challenges
- 27:53Learnings
related talks
41mBuilding a design system with React in 2025, what's new?
35mDesign system - From a Developer Point-of-View
20mDesign Systems for the Rest of Us
29mCreating a Design System that People Actually Use
27mA Practical Guide to Building Your Design System Infrastructure
21mDesign Systems 101: The Developer Approach to Better Frontends
19mHarnessing React to Build Consistently Designed Applications
28mA design system. A year in review