More than words: Reviewing and updating your information architecture
summary
Shows a concrete workflow: inventory pages in a content map (spreadsheet or DB), tag each page by DITA: concepts tasks reference, run a simple user‑task matrix scoring 3/2/1 to surface critical paths (example: product research = 6, managing clients = 9), then rebuild navigation (flatten five‑level nests), add keywords, Gatsby + Markdown pipelines and site search, measure baselines like dwell time, and iterate — implemented changes improve findability and get tweaked or rolled back based on metrics and reader feedback.
AI-written summary · about
chapters (18)
- 0:00Acknowledgement of country
- 0:22Defining documentation as design
- 1:12The role of an architect
- 2:12Bad design examples
- 3:00Documentation architecture
- 3:42Creating a content map
- 5:54Categorizing content types
- 7:37Understanding your readers
- 8:58Identifying user problems
- 10:28Gathering user research
- 12:10Acting on user feedback
- 13:32Task analysis and prioritization
- 17:16Improving site navigation
- 20:36Developing a new strategy
- 21:30Implementation planning
- 23:55Measuring success
- 25:54Conclusion
- 26:12Q&A session
related talks
45mContent Amid Chaos
36mStructure after the fact: Bringing content strategy to existing docs for a design system
18mDynamic Rebranding in DITA: Scale Content for Co-Branded Experience
43mDocumentation is UX! - Change my mind
46mDesigning for Highly Technical Domains
45mSmartWeb 2016 - Anna Debenham
15mCreating & Executing a Visual Content Strategy that Scales
24mRe-thinking product adoption through documentation design