Publishing, Revisions, and Image Management FAQ
What is the difference between a draft and a published page?
A draft lives in the private work directory and is invisible to a normal native build. A published page lives in the configured Docs (or other) content root and is part of the site the build emits. Promotion is the only intentional bridge between them.
Does marking an article reviewed publish it?
No. reviewed means editorial checks finished for the current registered proposal. Publishing still requires an approval receipt that cites the exact proposalSha256 and an explicit approve decision from the owner.
Why did my proposal digest change after I edited one paragraph?
Registration hashes the Markdown and declared managed assets together with destination metadata. Any intentional edit changes the registered content hash and therefore the proposal digest. Re-register, re-run QA if needed, and request approval again against the new digest.
Can I overwrite an approved cover in place during review?
No. Approved local assets stay immutable for the review. Generate a new private proposal (often a new filename or revision), register the change receipt, and seek approval. In-place mutation breaks the digest contract and cache assumptions.
What happens if I discard private work?
Discard rejects the active private revision for that id. Approved native content and shared approved assets remain. Completion records may list retained private notes; those leftovers do not republish themselves.
How should FAQ answers be structured for rich results?
Use an ATX heading that ends with a question mark, then a following paragraph answer. Avoid burying the answer inside lists or nested headings if you want the project’s FAQ extractor to emit FAQ structured data.
Do successful builds or image scripts count as approval?
No. Builds and image processing prove that tooling ran. They never authorize promotion. Only an owner-approved digest in a properly shaped approval file does.
Where do local image paths point after promotion?
Managed local images land under the project’s configured static directory and are referenced with public paths that omit the static/ input segment. Confirm baseUrl so cards, heroes, and Open Graph tags resolve on the deployed host.
What should I do if promotion reports a hash mismatch?
Stop. Compare the reviewed proposal to the approval file. Do not edit status JSON by hand. Re-register the intended work, re-review if required, and collect a new explicit approval for the new digest.