Repository navigation
feat(collections): save reviewed HTML settings - #23
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.
Owners can save collection-wide HTML settings through labelled forms. Settings keep an independent revision: saving classes or literal attributes leaves the collection's frozen model and saved content unchanged. Concurrent edits require explicit Reload; an unconfirmed save keeps the local draft and blocks retries until reviewed recovery.
The owner-only HTTP boundary validates bounded wire settings and hashes, saves metadata audit events atomically, and includes renderer records in migration/backup recovery. Dashboard controls preserve untouched wire values, current authority and pending-operation guards across seven languages and light/dark phone layouts. Saved settings remain separate from temporary HTML preview; selecting them for preview and publishing generated CMS endpoints follow in later deliveries.
Validation:
0.25.0-alpha.0, changelog, owner-facing guide and roadmap updated. All three exact-head CI jobs pass at reviewed head8ffc1b358bc495718951cb0dad33ecd2e46aa8dc.No tag, new public executable or deployment is published. Screenshots demonstrate scoped visual review, not native-speaker certification or production capacity.