We noticed that the structure of the table of contents in the documentation did not match the structure defined by the nav tree in the mkdocs file. Instead, it reflected the folder structure of the repository. After discussing this with Def Sutido and doing some tests, we came to the following conclusions.
The files/pages listed in the table of contents need to be defined in the nav tree.
The names of the pages in the table of contents will be defined by the nav tree.
The structure of the pages in the table of contents will be defined by the repository folder structure.
This means that if we want to align the table of contents to the nav tree, we have to align the folder structure to the nav tree structure. At the moment, the following files are not doing so:
reference/nodes.md
reference/catalogs.md
In this issue we will align the folder structure to the nav tree, ensuring that all the references still work for all those files that changed path.
We noticed that the structure of the table of contents in the documentation did not match the structure defined by the nav tree in the mkdocs file. Instead, it reflected the folder structure of the repository. After discussing this with Def Sutido and doing some tests, we came to the following conclusions.
This means that if we want to align the table of contents to the nav tree, we have to align the folder structure to the nav tree structure. At the moment, the following files are not doing so:
In this issue we will align the folder structure to the nav tree, ensuring that all the references still work for all those files that changed path.