### Idea Control `nav`igation per directory via [mkdocs-awesome-pages-plugin](https://github.com/lukasgeiter/mkdocs-awesome-pages-plugin?tab=readme-ov-file#customize-navigation). ### Use Cases 1. So [adding new content within a directory](https://github.com/DesignSafe-CI/DS-User-Guide/blob/v2.2.0/user-guide/docs/usecases/README.md#user-content-add-to-guide) is more like [adding new content via standard root config](https://www.mkdocs.org/user-guide/configuration/#nav). 1. So [adding new content within a directory](https://github.com/DesignSafe-CI/DS-User-Guide/blob/fix/remove-links-to-out-of-date-pages/user-guide/docs/usecases/README.md#user-content-add-to-guide) does not require editing [`nav` in `mkdocs.yml`](https://github.com/DesignSafe-CI/DS-User-Guide/blob/v2.2.0/user-guide/mkdocs.yml#L112-L136). 2. (Maybe) So cards on [Use Cases Overview](https://designsafe-ci.org/user-guide/usecases/overview/) can link to individual overview pages without repeating content. ### Related - requires https://github.com/TACC/TACC-Docs/issues/60 [^1] [^1]: Why? Because DS-User-Guide features come via TACC-Docs.[^2] [^2]: Sounds dumb… Stop that? I agree. See [TACC/TACC-Docs#53](https://github.com/TACC/TACC-Docs/issues/53).
Idea
Control
navigation per directory via mkdocs-awesome-pages-plugin.Use Cases
navinmkdocs.yml.Related
mkdocs-awesome-pages-pluginTACC/TACC-Docs#60 1Footnotes
Why? Because DS-User-Guide features come via TACC-Docs.2 ↩
Sounds dumb… Stop that? I agree. See TACC/TACC-Docs#53. ↩