Organize documentation site structure using Diataxis navigation guidelines.
npx skills add https://github.com/lorehq/lore --skill docs-nav-design
Please help me install this Agent Skill. Skill: docs-nav-design Source: https://github.com/lorehq/lore/tree/main/.lore/skills/docs-nav-design Command: npx skills add https://github.com/lorehq/lore --skill docs-nav-design
Documentation teams struggle with inconsistent navigation, bloated sidebars, and unclear page purposes, making it hard for readers to find relevant content quickly.
Apply this design guide to organize a new documentation site following the Diataxis navigation rules.
High-intent search queries and answers about installing and using this skill.
Structure documentation navigation using Diataxis-inspired guidelines to group pages by reader intent. Organize sidebar depth, landing pages, and content sizing to improve reader orientation and help users find relevant content quickly.
Diataxis is a content organization framework that groups documentation by reader intent into Getting Started, Guides, Reference, and Concepts. Aligning navigation with these categories improves orientation and separates tutorials from reference material.
Control sidebar depth and use landing pages to reduce docs bloat and improve scanability. Apply navigation guidelines to keep topics focused, ensuring concise page templates and structured metadata guide readers effectively.
Yes, this navigation approach works for existing reference and tutorial pages. It guides content teams in reorganizing pages by reader intent, applying sidebar depth control, and adding landing pages to clarify page purposes.
The best way to organize a documentation site structure is applying Diataxis-aligned navigation rules. Group content by reader intent, use frontmatter-driven metadata, implement structured navigation, and maintain concise page templates for optimal orientation.
Avoid Diataxis navigation when your documentation relies on a single linear workflow rather than distinct reference, tutorial, and concepts pages. This approach requires categorizing content by reader intent, which may not suit highly interdependent page structures.
mckinseyOrganizes Ark documentation using the Diataxis framework and taxonomy.
ousiassConvert Markdown specifications into Hugo documentation sites with Hextra theme.
dt418Build documentation platforms with versioned docs, search, navigation, code highlighting, and API reference generation.
jeremydhoover-blipDesign navigation hierarchies and organize documentation by user personas and intent.
