A Valuable Experience Begins with a Solid Content Outline
summary
Argues that a content outline written before wireframes cuts rework and lets designers and engineers agree on concrete pieces: numbered components, bracket notation for fields, V brackets for inner fields, and whether content is dynamic content or static. Recommends using IA, user research, and a template to assign items to four page areas including a hero area, pick single versus multi‑column rules (single-column is most responsive), and treat the outline as a testable hypothesis rather than finished copy, aligning scope and technical specs.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:35After research, requirements gathering, and information architecture, you're ready to start wireframing, right?
- 2:08What exactly is a content outline?
- 3:53Why content outlining?
- 6:42How do you decide what goes into your outline?
- 11:30What order, or hierarchy, works best?
- 14:49Handling page templates and layouts
- 18:39What level of detail should you use in your writing?
- 20:18What does a content outline look like and what notation should you use?
- 25:09Good outlines never die
- 26:20Conclusion
related talks
27mContent Planning - How To Beat Writers Block For Now And Forever
21mPrioritizing UX Content Work
45mContent First Prototyping
37mInformation Architecture: build it better
43mDesigning with Words
27mMore than words: Reviewing and updating your information architecture
39mWireframing Is a Team Sport
36mUX designers /developers collaboration anti patterns