Allow sections to be configured in `nav`
See original GitHub issueIn order to achieve top-level sections (e.g. to utilize material navigation tabs), I need to either:
- use this plugin but restructure all of my docs based on those sections
- use the native mkdocs nav functionality, and miss out on the good features here including the spread operator for the “rest” of the pages
It would be great to be able to specify custom sections in the .pages
file of the docs_dir
, e.g.:
nav:
- Vision:
- principles.md
- roadmap.md
- People:
- team.md
- advisors.md
- ...
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Configuring Microsoft Dynamics NAV Server 2017
Settings in the Microsoft Dynamics NAV Administration Console. In the tables in the following sections, Microsoft Dynamics NAV Server ...
Read more ><nav>: The Navigation Section element - MDN Web Docs
The <nav> HTML element represents a section of a page whose purpose is to provide navigation links, either within the current document or...
Read more >Configure navigation UI sections
In the web-based UI, enter sys_sg_navigation_section.list in the filter navigator. On the Navigation Sections form, click New.
Read more >Exploring and Customizing the Dynamics NAV User Interface ...
View more courses here: http://www.websanuniversity.comThis video will show you how to customize the role center and factboxes.
Read more >Views: The Essentials - AppSheet Help - Google Support
Views allow you to control how, when, and where data is presented to the app ... but that do not appear in navigation;...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Good news! I did some quick tests and should be possible. Here’s how it’s going to work:
If a
...
entry is present, the plugin generates a second navigation tree based off the file structure. All pages explicitly mentioned innav
are removed from this navigation tree before it is inserted in place of the...
entry.It’s going to take me a bit of time to properly implement and test this. I’ll let you know once the release is out.
Works great, thank you @lukasgeiter!