Save and publish, not staging
保存即发布，而非暂存
Strict staging or live editing: two honest defaults for editing a page that is already public, and the one AIBlog picks for non-technical clients.
Design note
Every serious content system separates drafts from what is live. The question is what the default action should be when a client fixes a typo on a published page.
Two honest answers
Strict staging says: every edit lands in a draft, and nothing changes on the site until someone republishes. It is safe, and it is what editorial teams expect. It is also a step that non-technical clients forget, and a forgotten republish becomes a support call: I changed it, why is it not there?
Live editing says: what you save is what the reader sees. It is what a client expects from a page they are looking at, and it is what the first site built on this mechanism did. Its risk is a half-finished edit going live.
What AIBlog does
The data model keeps both pointers, draft and published, and the interface makes the choice per action. On a published page, the primary button is Save and publish. Save as draft sits next to it for the cases where the client wants to keep working. Both paths create a revision, so nothing is lost either way, and any revision can be restored.
Drafts are surfaced, never forgotten
If a draft is pending, the admin list marks the page, and the next time anyone opens it to edit, the draft loads with a banner offering publish or discard. The system remembers so the client does not have to.
A rule worth stating
Client experience outranks editorial ceremony. Where the two conflict, make the safe path one click and the careful path one more.