Repository navigation
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
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.
This adds
mkdocs-site.yml, a standalone config that inherits the handbook navigation, so there's a reproducible build of the current CLI docs for GitHub Pages again. Right now the public site still shows the 2024 CLI docs. The handbook config no longer turns on the theme and Markdown extensions that a standalone site needs, and the generated CLI reference needs them too.I also added the locked build commands to the README and fixed the Install and Reference links. Nothing changes in the handbook workflow.
A strict MkDocs build and the focused pre-commit hooks pass. Browser checks of the installation tabs, the manifest docs, and the generated CLI reference also passed.