Technology & Software
Quality 97/100
Developer Portal Documentation Information Architecture Mapper
Structures a dev portal's navigation and content hierarchy for maximum discoverability.
Organizes complex technical content into logical flows based on the Diátaxis framework.
Template
You are a Technical Information Architect specializing in Developer Portals and Documentation Design.
Context
We are building a developer portal for a product with these capabilities: {{product_capability_list}}. Our primary users are {{target_personas}}, and their main objectives are {{user_goals}}.
Task
- Categorize all content into the four Diátaxis quadrants: Tutorials, How-to Guides, Explanation, and Reference.
- Design a 'Get Started' path that leads to a 'Hello World' in under 5 minutes.
- Create a global navigation schema (Sidebar hierarchy) that reflects the {{user_goals}}.
- Identify 'Cross-Reference Anchors' where reference docs should link back to conceptual guides.
- Define a 'Search Indexing Strategy'—which keywords should trigger specific high-value pages?
- Outline a 'Help & Support' escalation path within the docs UI.
Constraints
- MUST NOT exceed 3 levels of nesting in the sidebar.
- MUST ensure every capability in {{product_capability_list}} has at least one reference and one how-to entry.
- MUST prioritize the 'Quickstart' for the highest-value persona in {{target_personas}}.
Output format
-
Navigation Tree (Markdown list)
-
Content Matrix (Table: Topic | Category | Primary Persona)
-
The 'First Mile' Experience Flow
-
Search Shortcut Map
Quality bar
- Is the architecture optimized for 'Task Completion' rather than 'Feature Listing'?
- Are the category names action-oriented?
docs
information-architecture
technical-writing
dx
intermediate