In Search of the Lost UI: A Tale of Design System Development
summary
Built a company design system called KAKAO SEARCH TEMPLATE that combines a Storybook template guide, an ELK-backed logging dashboard, a drag‑and‑drop builder using react-beautiful-dnd, and markup export driven by Puppeteer. It tracks which services show each component so teams can safely remove unused parts (example: ThumbList), standardizes names (CarouselList), and resolves tooltip/name confusion; it works but surfaces engineering pain points like Puppeteer sandboxing, dangerouslySetInnerHTML and CONTENTEDITABLE editing limits.
AI-written summary · about
chapters (14)
- 0:00Design system challenges
- 2:06Expanding systems growth pains
- 7:255 Whys root causes
- 10:23KST project motivation
- 13:03KAKAO SEARCH TEMPLATE functions
- 18:05Team collaboration tools
- 20:00KST tech stack
- 22:41Solving design system problems
- 26:16Search UI Council maintenance
- 27:44New template workflow
- 28:05MobX implementation challenges
- 29:15Puppeteer sandbox errors
- 30:45Storybook security issues
- 32:14Future improvements
related talks
38mEmpathetic Design Systems
28mFrom Sketch to Code Designing a Component Kit
35mDesign system - From a Developer Point-of-View
26mDesign Systems of a Down: Steal this Guide!
27m"Design Systems from 0 to 1"
21mDesign Systems 101: The Developer Approach to Better Frontends
22mDesign Systems at Deliveroo: Learnings and Frustrations
28mLet's talk about design systems