When pages are aggregated by folders/pages/subpages, the ToC does not correctly reflect the corresponding nesting structure.
Here is the DevOps structure
... and here is how the ToC is generated into the PDF
The page correspondencies are as follows:
As you can see, there is no aggregation by folders/pages/subpages, and almost all the chapters of all the pages appears at the same hierarchy level.
Unfortunately the final result is incomprehensible for the reader since the navigation is not organic/structured.
When pages are aggregated by folders/pages/subpages, the ToC does not correctly reflect the corresponding nesting structure. Here is the DevOps structure
... and here is how the ToC is generated into the PDF
The page correspondencies are as follows:
As you can see, there is no aggregation by folders/pages/subpages, and almost all the chapters of all the pages appears at the same hierarchy level. Unfortunately the final result is incomprehensible for the reader since the navigation is not organic/structured.
The PDF has been generated using the command:
azuredevops-export-wiki.exe -b --css style.css -h -v