DOC: Improve NEP page layout with nested toctrees #20956
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
|
Thanks, @rossbar ! |
melissawm
pushed a commit
to melissawm/numpy
that referenced
this pull request
Apr 12, 2022
seberg
pushed a commit
to seberg/numpy
that referenced
this pull request
Apr 24, 2022
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.
A possible solution to #20952 .
The NEP listing is currently generated in individual (unnested) toctrees in a jinja template, which results in the left sidebar showing all the NEPs in whatever order they appear in the various toctrees.
This PR splits out the toctree generation into individual per-category templates that are then referenced in the main toc in the index to produce a nested sidebar organization.