Features / Publishing & revisions
Nothing goes live without you.
In Plumixia, what is live and what is being written are two different things. You work on a draft, you publish when it is ready, and you can always go back.
Draft, review, publish.
Save
Every save creates a new numbered revision with its author and date. The live version doesn't move.
Review
Pages with unpublished changes are flagged, so nothing slips through before it has been checked.
Publish
The chosen revision becomes the public version. Sitemap, search and language variants follow.
Roll back
A mistake? Publish an earlier revision again. Deletions go through the trash first.
Revisions aren't just for pages.
Layouts, themes, shared components, fragments, data objects, categories, tags and even object types are versioned the same way.
- Per-revision log: who changed what, human or AI agent
- Concurrent edits detected: nobody overwrites someone else's work without knowing
- Auto-publish as an option, site by site (staging, low-stakes sites)
- Trash and pending deletion rather than immediate erasure
- Cloning a page to prepare a redesign next to the live version
Drafts are the natural guardrail for agents.
An agent connected over MCP writes revisions just like a human editor. On a site without auto-publish, its work waits for your review. You keep the decision; it does the repetitive work.