Skip to content
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

forcedNavOrder for dropdown #56

Closed
JGeiser9 opened this issue Feb 21, 2020 · 4 comments
Closed

forcedNavOrder for dropdown #56

JGeiser9 opened this issue Feb 21, 2020 · 4 comments

Comments

@JGeiser9
Copy link

JGeiser9 commented Feb 21, 2020

First, this is an awesome template for a docs page. Thanks for all of your hard work on this template.

I skimmed through and attempted to edit the config.js file a bit after cloning for an option to force the order of the sub menu items as well. Is there a way to currently do this that I may have missed?

Thanks!

@praveenweb
Copy link
Member

Hi @JGeiser9,

The forced ordering of nav items is currently configurable only for the top level items. For sub items, it is assumed that files will be ordered alphabetically. Typically number prefixes like 1, 1.1 etc are used to force the order.

@JGeiser9
Copy link
Author

Thats a fair assumption, I will roll with the prefix format. Thanks for the response

@pdesmarets
Copy link

I love the template, thanks for making it available. But renumbering when inserting a new page can be cumbersome and error prone. It would be great to enhance the forcedNavOrder capability to declare the order of nested levels.

@pdesmarets
Copy link

Besides, it appears that the Contents right-hand sidebar is lost when naming files start with a number.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants