Docs Tooling Overview
OAT can help bootstrap and maintain a structured docs surface, not just code and provider assets. The docs tooling is built around a simple contract: each directory owns an index.md, and that index owns a ## Contents section that supports local discovery and generated navigation.
OAT supports both Fumadocs and MkDocs. The site framework changes the surrounding app setup, but the underlying documentation contract stays the same.
When To Use This Section
Use Docs Tooling when:
- you are adding a docs app to a repo
- you need to keep index pages and nav structure in sync
- you want a controlled analyze/apply loop for docs restructuring work
Typical Flow
- Bootstrap or adopt a docs app in the repo.
- Use the docs commands to generate or sync index/navigation structure.
- Apply the docs workflow when you want analysis-backed restructuring rather than ad hoc manual edits.
Continue Here
- Add Docs to a Repo for initial setup
- Commands for the CLI surface
- Workflows for governed docs changes
- Docs Index Contract for the underlying rules