Docs: remove in page toc #891
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amotl
approved these changes
May 13, 2025
There was a problem hiding this comment.
The in-page TOC is redundant as it's also present to the right side.
Yeah, the secondary navigation element (rightnav) is a new element compared to how the documentation layout and structure had been conceived originally, many years ago. Previous documentation authors haven't been able to use that element, so using in-page TOCs was applicable. In this spirit, I think we can remove many on-page TOC elements across the board today. Thank you so much!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of the changes / Why this is an improvement
The in-page TOC is redundant as it's also present to the right side.
"Screenshot" headline seems a bit silly, so removed that.