Bundle entries into a release, pin the exact revision of each, get it reviewed, then apply the whole set at once — validated first, one cache purge, one-click rollback.
Publishing CSS one entry at a time means a window where half your redesign is live. A release closes that window. Here is the whole promise, in order:
The same validation runs again on the server at deploy time. One failure stops the whole thing — you can’t ship a release with broken CSS in it.
All the entries switch to their pinned revisions at once — not one after another while visitors watch.
A single purge after the switch, so nobody gets a half-updated site. Cloudflare, WP Engine, Kinsta and SpinupWP are handled for you.
The state of every entry is recorded before the switch. One click puts it all back — and tells you exactly what will change before you confirm.
Submit a release for review, optionally assigned to a named approver. They can approve or ask for changes — with a note, because “request changes” without a reason sends the author back to guessing.
Reviewers don’t need edit access. Give someone approve-only and they get a read-only release, a preview of the whole set on the real site, and the two buttons that matter.
Editing live CSS is the awkward case for any review process: the moment you save, it’s on the site — so there’s nothing left to review. Pro records the change as a revision instead. The site keeps serving exactly what it was serving, your edit rides a release, and deploying is what applies it.
Same app, same screens — the Pro parts appear where you already work. Nothing in the free plugin moves or gets taken away.
Schedule an entry or a whole release. You can’t schedule broken CSS — a schedule publishes while nobody is watching.
Role, logged in or out, device, language, URL parameter, date window, and WooCommerce shop, cart and checkout — layered onto the scope you already set.
Published, restored, deployed, approved, rolled back, settings changed — filterable by person, action and date, each row linking to what it concerns.
Plus a notification trail: what was sent, to whom, on which channel, and whether it actually got there.
A grid of events by channel, a heads-up before a scheduled deploy, and failure alerts administrators can’t accidentally mute. Everyone controls their own subscriptions on their profile.
Call a revision “pre-redesign baseline” and pin it so the retention limit never prunes it. Releases pin the revisions they depend on automatically.
What needs you, what’s scheduled next, and one green line when everything’s fine. When it isn’t, that line becomes a short list naming the thing that broke — a cache that didn’t clear, cron running late — each one linking to where you fix it.
A scheduled deploy that didn’t fire is the one failure you find out about afterwards. So it says what didn’t happen, why, and — first — that your site is fine.
Tiers are about how many sites you run, not how much of the plugin you get. Nothing is held back for the expensive one, no feature switches off, and there’s no key to keep alive.
Yes. Pro is an add-on, not a replacement — it mounts its screens inside the free plugin you already use. Install the free one first, then activate Pro alongside it.
Two separate permissions, assigned per role on the Pro settings page. Administrators get both. Approving never requires edit access, so a reviewer can sign off without being able to change the CSS. On multisite, deploying also requires edit_css — the same permission WordPress itself uses to gate CSS, so Pro never hands out more than core would.
We don’t call it a transaction, because that would promise more than WordPress can give. What it does promise: everything is validated first, the entries are applied together, there’s one cache purge, and one click puts it all back.
Within minutes of it, usually. WordPress only checks for due schedules when someone visits the site, so a quiet site can run late — Pro measures yours and tells you, with the one server-cron line that fixes it.
No. Not your CSS, not your releases, not your history. There’s no account, no key to enter, and nothing that phones home — install the zip and it works on a machine with the network unplugged. The only outbound calls Pro can make are the ones you set up yourself: a Slack webhook, and cache purges to your own CDN. Those go from your server straight to the service you chose.
The free plugin carries on with everything it always did. Your entries, scopes and history are untouched — you just lose the release, review and scheduling screens.
For teams who’d rather not find out about a CSS change from a customer.
