Repository navigation
docs: refresh project overview and staging setup - #7
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.
The README still described deployment as future work after local Docker staging shipped. Refresh the introduction with the available collaboration, SDK, permissions and operations features, and add a Docker quick start with links to the detailed guides.
Update the proxy, origin-checking, runtime and CI descriptions to match the release. Keep the current limits explicit: one application node, in-memory offline drafts, an unpublished SDK, and separate setup for public hosting, alert delivery and off-machine backups.
Validated all 15 local README links and heading anchors, checked the documented staging commands against CLI help, and ran
git diff --check. This changes documentation only.