Empathetic Design Systems
summary
Design system work at Eventbrite moves from brittle KSS style guides to a funded product called EDS with a component generator built on plopjs, accessibility checks via jsx-a11y, and plans to use storybook; teams migrate from Backbone to React, front end foundry is three senior plus three junior engineers, and a UXPin survey of about 3,200 people motivates empathic goals. Problems that slow adoption include terrible naming, poor discoverability, unclear deprecation, grid versus flexbox conflicts, and a release cadence that shifts from once weekly to automated bumps and twice-weekly releases.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:37Job Announcement
- 1:22What is a Pattern Library
- 2:14Design Systems
- 4:16What is Empathy
- 7:00eventbrites design system
- 8:53old school style guide
- 11:12component generator
- 12:31planned approach
- 13:19lack of empathy
- 17:23designers
- 18:38release process
- 19:35solutions
- 23:00what should you do
- 23:51documentation
- 24:38storybook
- 25:19conclusion
- 25:50resources
