Repository navigation
docs: align custom and quick package installation - #19
Merged
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
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.
Owner-approved installation structure
All six distributions now use Quick install → Complete sets, then Custom install → Selected packages. Commands begin immediately after the Selected packages heading; catalog guidance follows the checks. The redundant Complete sets / Selected packages list is removed. Preserve #choose-packages as an explicit anchor, all remaining targets and every shell command block.
The .github navigation plan generates the Custom install label through the existing renderer; DistributionPackages owns the six guides and renamed generated SVG. No workflow, package state, signing, installer, feed or key changes.
Verification