docs: flatten the hierarchy #78
Closed
Conversation
This file contains 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
marquiz
force-pushed
the
devel/docs-hierarchy
branch
from
cd32157
to
62dbaa4
Compare
Drop one level of sub-hierarchy, making "Policies" a top-level item in the "Resource Policy Plugins" section. Makes the documentation easier to follow (and easier to find the detailed docs of the actual policies/plugins). Signed-off-by: Markus Lehtonen <[email protected]>
marquiz
force-pushed
the
devel/docs-hierarchy
branch
from
62dbaa4
to
a99118b
Compare
klihub
approved these changes
Jun 22, 2023
|
I just find the current very deep hierarchy really odd and cumbersome Resource Policy Plugins -> Configuration -> Policy -> Topology-Aware Especially when it's not just about configuration of the policy but a detailed documentation of all aspects of the policy |
|
Already merged |
|
Merged as part of stacked PR #80. |
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.
Drop one level of sub-hierarchy, making "Policies" a top-level item in the "Resource Policy Plugins" section. Makes the documentation easier to follow (and easier to find the detailed docs of the actual policies/plugins).