Agile Atomic Design - Experiences from the reality
summary
Changes a decade-old workflow to combine Atomic Design with Agile, claims a component-first process speeds prototyping and catches content problems earlier but incurs heavy cultural and tooling costs. Team builds a component library, a front-end styleguide and integrates components into TYPO3 via a repo, using Sketch and Photoshop for visuals. A few-weeks rollout shows clearer consistency and faster testing but requires role shifts, strict governance and upfront effort before reuse pays off.
AI-written summary · about
chapters (9)
- 0:00Introduction and speakers
- 3:13Atomic design mindset
- 5:49Project workflow basics
- 9:10Design system setup
- 13:18Cross-functional teams
- 17:03Component implementation
- 21:28Team-based process
- 25:56Customer involvement
- 26:22Q&A
related talks
44mAtomic Design and Storybook to Boost Frontend Dev Productivity
32mAtomic Design Theory in Practice
49mIs Atomic Design Dead?
37mIs Atomic Design Dead?
40mAtomic Design Software Architecture Illustrated with Angular 2
29mWorkflow in the Age of the Design System
40mA lean approach to building design systems
30mAtomic Design: Breaking Up is Hard to Do