mkdocs-literate-nav
mkdocs-literate-nav copied to clipboard
oprypin
MkDocs plugin to specify the navigation in Markdown instead of YAML
Let's say we have such a structure: - project/ - file.md - SUMMARY.md - docs/ - SUMMARY.md - some-file.md - dir/ - another-file.md In `project/SUMMARY.md` we have: ```markdown - *.md...
Hi, I wanted to use the convention known from `mkdocs-awesome-pages` plugin to put sub-navs into `.pages` files: ```yaml - literate-nav: nav_file: .pages ``` Unforunately, it doesn't work. If I rename...
In `mkdocs-awesome-pages`, we have two ways to exclude a directory: 1) we can put a `.pages` file in the folder with `hide: true` 2) in the parent folder, we can...
When using this plugin with the strictest MkDocs settings available in 1.5, using `dir/` references in nav files causes MkDocs to flag those relative links as unrecognized: ``` WARNING -...
I have to remove all the trailing spaces (of lines) and empty lines from my summary markdown file to avoid the following error: mkdocs_literate_nav.parser.LiterateNavParseError: Expected no text after '...', but...
## Issue Summary When using the `literate-nav` plugin with [navigation.indexes](https://squidfunk.github.io/mkdocs-material/setup/setting-up-navigation/#section-index-pages) enabled, the page in my `SUMMARY.md` is missing from the nav (the page is instead linked to the Section above...
Currently it seems like Literate Nav doesn't support specifying a dedicated markdown page, while not providing a title, i.e. letting the title to be inferred. This works fine if you...
