UX Writers Need Design Systems, Too!
summary
A team stops the chaos and builds a copy system in Figma that makes each string a component, nests copy instances inside visual components, and uses atomic design separation so UI changes don’t break copy. Demo shows a two‑week prototype, concrete workarounds for Figma’s search limits (put keywords in the description, narrow by file), and a file organization pattern. Result shortens alignment, lets writers reuse approved text, and surfaces gaps to create new copy.
AI-written summary · about
chapters (11)
- 0:00Introductions
- 1:28Consistency and reusability
- 2:42Content style guides vs. design systems
- 3:11Use Cases + Annie examples
- 4:26Behind the scenes demo
- 9:00Atomic Design
- 9:54Design Challenge: Browse + Search
- 13:22File Management
- 14:58Efficient copy alignment process
- 15:22Key takeaways
- 17:55Closing
related talks
14mRethinking Designer-Developer Collaboration
23mCollaborative and real-time design systems in Figma
14mEmpowering designers: AI, design systems, and quality
40mHow to optimise the workflow between designers and developers using design..
19mBehind the system: A showcase of files that inspire us
15mHoly War between Designers & Developers
18mDesign Systems in Practice
21mResearch-driven design systems