Move release website documentation out of README - #47
Merged
Conversation
Signed-off-by: helly25 <6420169+helly25@users.noreply.github.com>
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.
Move release-site operating instructions into a dedicated document so the README stays focused on using the project, following mboworks/xff#784.
AG;DR
docs/release-website.md, with links adjusted for its directory.release-site.jsonso versioned sites render and validate it.Validation: the existing release-site regression tests, focused pre-commit hooks, and CI documentation conversion validate this documentation-only change. Full required PR checks must pass before merging.
This PR is independent of the corresponding changes in other repositories. Existing immutable release snapshots are preserved.