docs: restore standalone GitHub Pages build - #199
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
1 participant
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.
The public GitHub Pages site still contains the 2024 CLI documentation. The current handbook configuration no longer enables the theme and Markdown extensions needed to render a standalone site, including the generated CLI reference.
Add a standalone configuration that inherits the handbook navigation, document the locked build commands, and repair the Install and Reference links. This provides a reproducible build of the current CLI documentation without changing the handbook workflow.
Validation: strict MkDocs build, focused pre-commit hooks, and browser checks of installation tabs, manifest documentation, and the generated CLI reference passed.