oscal-compass/compliance-trestle

Use mkdocs features to avoid manually configuring `nav:`

Opened this issue · 0 comments

Issue description / feature objectives

Manually configuring nav: for mkdocs is an anti-pattern. It creates inconsistency and removes part of the value of mkdocs - implicit naming based on directory structures.

Rework the automation specifically for the api docs and use mkdocs-awesome-pages to create selective overrides for just what is required.

Caveats / Assumptions

  • Documentation content should not be changed

Completion Criteria

  • nav: is removed
  • content is not changed