-
Notifications
You must be signed in to change notification settings - Fork 10.6k
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
Adding secondary chapter navigation on left side like just-the-docs jekyll theme #2273
Comments
I don't think I understand. The chapter navigation is basically a toc. What would be the difference? |
Although both serve a similar purpose of helping users navigate through content, the key distinction lies in the organization of content. While a toc typically outlines the content within each chapter, chapter navigation involves structuring each chapter as a separate markdown file. This approach ensures that each chapter remains self-contained, enhancing clarity and organization by avoiding the clutter of mixing everything in a single file. Essentially, chapter navigation simplifies accessing and managing individual chapters while maintaining a coherent structure throughout the document. TOC serves a better purpose for blogs and single markdown files, but if we are to write a different chapter for the book, it would be easier if all my chapters could be navigated easily. I hope this clears the differences. Please look at this: Chapter and TOC navigation |
And also this : Separate chapter and toc navigation |
Now I get it. This can be currently achieved manually, but I agree that it would be good if it was integrated somehow. |
Adding another reference here. |
Have you checked that your feature request isn't already filed?
Description & Motivation
This will be particularly helpful for making complete chapter-based notes, and exercises, for the specific book. So, If I want to open notes for specific books, I will have chapter navigation on the left sidebar and the table of contents on the right sidebar.
Pitch
No response
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: