Organizing Documentation

Reorganize documentation by developer intent—restructuring content into BUILD, FIX, UNDERSTAND, and LOOKUP categories—so developers find answers based on what they're trying to accomplish, not where files happen to live. This audit-driven approach audits current docs, creates intent-based directories, relocates files, and generates an INDEX.md with redirects for seamless navigation.

Intent-based structure organizes docs around what developers need to do rather than content type. Use it when setting up new project documentation, when your team repeatedly asks the same questions because docs are scattered across folders like architecture/ and api/, or when onboarding new members takes longer than necessary due to poor discoverability.

Audit your current documentation by mapping files to developer intent categories, then restructure directories into BUILD, FIX, UNDERSTAND, and LOOKUP sections. The process includes relocating and renaming files, generating a master INDEX.md that serves as the navigation hub, and creating redirects to preserve existing links during the transition.

Yes. Intent-based reorganization preserves existing content while restructuring how it's discovered. By relocating files into intent-driven categories and adding a master INDEX.md with cross-references, developers find information faster through clearer navigation and purpose-driven categories—without requiring content rewrites.

Structure documentation around developer intent—BUILD for getting started, UNDERSTAND for concepts, LOOKUP for reference, FIX for troubleshooting. This hierarchical organization lets new team members find answers by task rather than browsing scattered folders, cutting onboarding time by making documentation instantly navigable and purposeful.