Lukas Geiter

In case of awesome-pages, the default file for configuring the navigation is called `.pages`. If all dotfiles would be ignored, users wouldn't see the effect of changes in `.pages` until...

The extractor is made for HTML not JSX. I'm also not really sure what you would expect. If you only want `Some good text` extracted, why don't you do `Some...

That is currently not possible using this plugin. The navigation is currently generated once and used for all pages. Building some pages with a different navigation should be technically possible...

The `...` in a `.pages` file only targets the remaining items in the directory of the `.pages` file. Try putting the `nav` block into `mkdocs.yml` instead.

`documentation/*` doesn't match any files, you would need something like `documentation/**`. But that's probably also not what you want so you would have to make it `... | flat |...

Sure `documentation/systems/*` works, but before you wrote `documentation/*`. The ordering being off likely means that the plugin is not doing anything at all for some reason. But feel free to...

Thanks for the example! There is a strange interaction between defining the navigation in `mkdocs.yml` and using the `order` option. Once again, I really recommend using separate files. 1. Remove...

What should happen to the tabs at the top? Those are part of the navigation as well. Also am I correct in assuming that when the user is on the...

MkDocs always navigates to the first page of a section (folder). Therefore, as @kamilkrzyskow suggested, you need some sort of index page if you don't want users to go straight...

My first guess is that the plugin is installed in a different location than mkdocs itself. Run the following command to print all packages that are installed alongside the plugin:...