You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, all the md files are built and dumped into build.
If using mkdocs (#10) these have to be specified in the yaml. One could do the same in a top level latex file to input these and add style. This seems like a duplication of effort (specifying the ordering).
I would propose, either:
mkdocs.yml pages-section is required, use this to decide the ordering and naming of sections. Warn/error if sections are missing in both src or yaml. Use this for generating single-page html/latex.
makedocs function allows passing of this ordering (as title => filename pairs). Warn/error if sections missing or do not exist in both src or yaml.
My preference is the mkdocs.yml as this already exists, and allows nested files etc.
This is crucial in compiling to a single document (e.g. #4).
The text was updated successfully, but these errors were encountered:
Specifying page order was added in e7de659 (currently internal and undocumented since markdown output doesn't really need it). Closing this issue since #100 supersedes this I think.
At the moment, all the md files are built and dumped into build.
If using mkdocs (#10) these have to be specified in the yaml. One could do the same in a top level latex file to input these and add style. This seems like a duplication of effort (specifying the ordering).
I would propose, either:
My preference is the mkdocs.yml as this already exists, and allows nested files etc.
This is crucial in compiling to a single document (e.g. #4).
The text was updated successfully, but these errors were encountered: