Repository navigation
docs: identify the website repository as public infrastructure - #53
Merged
Merged
Conversation
Add a repository README explaining website publication and presentation ownership, outside the core product and supported-extension hierarchy. Point product visitors to the engine, canonical tutorials, and GitHub Action. Document that reference pages come from engine docs at the pinned release; link to existing build guidance and contracts instead of duplicating setup. Validation: Markdown links and git diff --check passed. No templates, synced docs, workflows, or release pins changed; no website build or deployment ran.
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.
Add a repository README explaining website publication and presentation
ownership, outside the core product and supported-extension hierarchy.
Point product visitors to the engine, canonical tutorials, and GitHub Action.
Document that reference pages come from engine docs at the pinned release;
link to existing build guidance and contracts instead of duplicating setup.
Validation: Markdown links and git diff --check passed. No templates, synced
docs, workflows, or release pins changed; no website build or deployment ran.