Prev/Next links don't honor sidebar.yml order
See original GitHub issueDescription of bug
Prev and Next links appear to be in alphebetical order vs using the order of the sidebar.yml
To Reproduce
- Go to https://rocketdocs.netlify.com/usage/creating-docs
- Scroll down to to view Prev and Next links
- Notice the page links
Expected behavior
Prev is set to Navigation
when it should be Getting Started
and Next is set to Getting Started
when it should be Navigation
. The Next and Prev page links should use the order of sidebar.yml
Screenshots
Environment: N/A
Additional context
---
Apologies if I’m off the mark 🎉
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Prev Next Link - VitePress
You can customize the text of previous and next links. This is helpful if you want to show different text on previous/next links...
Read more >Default sidebar links broken · Issue #219 · fastai/nbdev - GitHub
Issue: The links in a newly generated "default sidebar" point to .html Since "pretty ... I don't know why this change was made,...
Read more >BBEdit Expert Preferences - Bare Bones Software
When using the "Previous Document" and "Next Document" commands on the View menu, the order in which BBEdit navigates documents is determined by...
Read more >@vuepress/plugin-active-header-links - Package Manager
Fast, reliable, and secure dependency management.
Read more >Read the Docs Documentation
Read the Docs simplifies software documentation by building, versioning, and hosting of your docs, automatically.
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
Hey @jpvalery and @robmcguinness! I have already fixed this issue and I am going to release it as soon as I can. Thanks for your patience 💜
No worries! Thanks for great theme!