Atomic Design as a Migration Strategy
summary
Concrete claim: Atomic Design lets a team do an asynchronous rewrite by shipping small components into a legacy app. The team migrates six years of Buffer code by publishing atoms via npm, developing in React Storybook with snapshots, assembling molecules, and avoiding iframes after hitting postMessage and WebSocket scaling pain. Inline styles plus a reset class ensure CSS wins. Work proceeds in six-week cycles, features move to a new shell, and customers migrate gradually.
AI-written summary · about
chapters (7)
- 0:00Atomic Design intro
- 3:53Migration strategy
- 6:22Building atoms & molecules
- 10:35Migrating features
- 11:39Developer productivity
- 13:10Build for a changing future
- 13:54Q&A
related talks
36mAtomic design in responsive design
30mAtomic Design: Breaking Up is Hard to Do
24mBuild React Apps Fast Using Storybook, DDD, and Atomic Design
47mDeploying atomic design system at scale
07mReact components, atomic design and storybook
01mAurora Scharff's Journey with React
28mLessons in Managing Technical Debt
49mScalable Best Practices for Your Development Team