Documentation Information Architecture
Use this skill to organize developer documentation so readers can find the right content at the right time. It works at doc-set and site level rather than single-page prose level.
This skill is derived from Docs for Developers: An Engineer's Field Guide to Technical Writing, especially Chapter 10, "Organizing documentation." It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's The Product Is Docs: Writing Technical Documentation in a Product Development Group, especially Chapter 17, "Tools and Content Delivery," plus related audience, learning-objective, maintenance, and SaaS guidance from Chapters 3, 9, 10, and 25. Do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-6
Quick Start
- Load
guidelines.md to choose the smallest useful reference set.
- Identify user mental models, common tasks, and existing content inventory.
- Choose or combine sequence, hierarchy, and web structures.
- Use
workflows/evaluate-doc-platform.md when choosing or migrating documentation tooling.
- Use
workflows/audit-doc-ia.md for full IA audit or redesign.
- Preserve redirects, metadata, source decisions, and maintenance rules.
Default Output
When auditing or redesigning IA, return:
- Current-state findings - navigation, gaps, duplication, stale content, and findability issues.
- User model - major audiences, tasks, and entry points.
- Recommended structure - sequence, hierarchy, web, landing pages, and navigation cues.
- Content actions - keep, remove, review, merge, split, move, or create.
- Migration plan - redirects, metadata, owners, and validation.
- Maintenance plan - how IA decisions stay current.
Contents
| Need |
Start Here |
| Understand IA patterns |
references/core/knowledge.md |
| Apply IA rules |
references/core/knowledge.md |
| See IA examples |
references/core/knowledge.md |
| Audit or redesign IA |
workflows/audit-doc-ia.md |
| Evaluate docs platform/tooling |
workflows/evaluate-doc-platform.md |
| Route by task |
guidelines.md |
Core Posture
- Organize docs around user mental models and tasks.
- Use landing pages to route quickly, not to create marketing detours.
- Keep navigation cues useful but economical.
- Treat migration and maintenance as part of IA design.
- Choose tools from reader, authoring, maintenance, and migration requirements rather than feature excitement.
1---2name: documentation-information-architecture3description: Audit, organize, and redesign developer documentation information architecture, including content inventory, navigation, landing pages, sequences, hierarchies, webs, breadcrumbs, sidebars, metadata, redirects, migration, platform/tool selection, and maintainable IA decisions. Use when restructuring docs sites, improving findability, planning doc migration, evaluating docs tooling, or organizing large documentation sets.4license: MIT5compatibility: Codex, Claude Code, and other Agent Skills-compatible clients.6metadata:7 version: "0.1.0"8 displayName: Documentation Information Architecture9 category: Writing10 tags: developer-docs,technical-writing,documentation,information-architecture,navigation11---1213# Documentation Information Architecture1415Use this skill to organize developer documentation so readers can find the right content at the right time. It works at doc-set and site level rather than single-page prose level.1617This skill is derived from *Docs for Developers: An Engineer's Field Guide to Technical Writing*, especially Chapter 10, "Organizing documentation." It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's *The Product Is Docs: Writing Technical Documentation in a Product Development Group*, especially Chapter 17, "Tools and Content Delivery," plus related audience, learning-objective, maintenance, and SaaS guidance from Chapters 3, 9, 10, and 25. Do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-61819## Quick Start20211. Load `guidelines.md` to choose the smallest useful reference set.222. Identify user mental models, common tasks, and existing content inventory.233. Choose or combine sequence, hierarchy, and web structures.244. Use `workflows/evaluate-doc-platform.md` when choosing or migrating documentation tooling.255. Use `workflows/audit-doc-ia.md` for full IA audit or redesign.266. Preserve redirects, metadata, source decisions, and maintenance rules.2728## Default Output2930When auditing or redesigning IA, return:31321. **Current-state findings** - navigation, gaps, duplication, stale content, and findability issues.332. **User model** - major audiences, tasks, and entry points.343. **Recommended structure** - sequence, hierarchy, web, landing pages, and navigation cues.354. **Content actions** - keep, remove, review, merge, split, move, or create.365. **Migration plan** - redirects, metadata, owners, and validation.376. **Maintenance plan** - how IA decisions stay current.3839## Contents4041| Need | Start Here |42|------|------------|43| Understand IA patterns | `references/core/knowledge.md` |44| Apply IA rules | `references/core/knowledge.md` |45| See IA examples | `references/core/knowledge.md` |46| Audit or redesign IA | `workflows/audit-doc-ia.md` |47| Evaluate docs platform/tooling | `workflows/evaluate-doc-platform.md` |48| Route by task | `guidelines.md` |4950## Core Posture5152- Organize docs around user mental models and tasks.53- Use landing pages to route quickly, not to create marketing detours.54- Keep navigation cues useful but economical.55- Treat migration and maintenance as part of IA design.56- Choose tools from reader, authoring, maintenance, and migration requirements rather than feature excitement.
LVTD-LLC