Reimagining Atlassian Design System
summary
A design system narrative that names concrete problems and solutions: Atlassian reframes ADG and Atlaskit as distinct responsibilities, discovers 120+ packages, only 60 core, defines component principles and ownership to avoid a dumping ground, and creates a single documentation home that exists since Aug 2020; the team builds React components, Figma libraries, design tokens and runbooks, admits a failed dark‑mode attempt and pivots to theming at scale, and measures staffing and ratios to justify process and tooling changes.
AI-written summary · about
chapters (18)
- 0:00Start
- 1:08The Creation of a Design System for Udacity from the Ground Up
- 1:41About Atlassian Design System
- 4:06Hyper Objects
- 5:44The Great Wave of Kanagawa by Hokusai
- 6:35Hyper Growth Waves
- 7:51What Not To Do When Architecting a Design System
- 8:20Atlas Kit
- 11:53What Does Belong in Our Design System
- 14:06Why Is this Challenging and Sometimes Overwhelming for Our Design System
- 14:35Design System Values
- 16:36Balancing Adoption
- 18:05Harmony
- 18:52Primitives
- 22:54Design System Sparring
- 24:15What's an Effective Design System Team Size
- 26:23Process Design
- 30:53Recap
