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
Since all projects currently rely on MkDocs, we could provide a default way of generating the documentation via MkDocs, optionally relying on user-provided overrides and configs.
In particular, we can at the very least generate mkdocs.yml with the navigation extended by the literate Rzk Markdown files. For example, for the sHoTT project, based on the rzk.yaml file and the contents of src directory, we can generate the following file:
Since all projects currently rely on MkDocs, we could provide a default way of generating the documentation via MkDocs, optionally relying on user-provided overrides and configs.
In particular, we can at the very least generate
mkdocs.yml
with the navigation extended by the literate Rzk Markdown files. For example, for the sHoTT project, based on therzk.yaml
file and the contents ofsrc
directory, we can generate the following file:The idea is to get this information automatically:
rzk.md
filerzk.yaml
We could also use some standard template for MkDocs as default, so that
rzk doc
could simply generate everything automatically.The text was updated successfully, but these errors were encountered: