New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow sections to be configured in nav
#30
Comments
Restructuring your docs actually sounds like a good idea to me. Can you help me understand why you don't want to go that route? |
Users have bookmarked some of the pages, and I’m not 100% sure this is the final organization, so I don’t want to setup redirects potentially multiple times |
Looking at trying to implement this, I can see why there's some hesitation @lukasgeiter :). Some abstractions in the test setup around asserting section children have the section as the parent and some of the assumptions in MetaNavItem may make this request challenging to fulfill. |
The implementation is only part of why I'm hesitant. Your request somewhat goes against the core idea of the I think a better idea for you might be to add support for an |
good thinking, and thanks! |
Good news! I did some quick tests and should be possible. Here's how it's going to work: If a 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. |
I've just released v2.4.0 with this feature. Check out the updated README for all the details. |
Works great, thank you @lukasgeiter! |
In order to achieve top-level sections (e.g. to utilize material navigation tabs), I need to either:
It would be great to be able to specify custom sections in the
.pages
file of thedocs_dir
, e.g.:The text was updated successfully, but these errors were encountered: