Geiger Content · Publishing and versions
Publish with a safety net
One queue from draft to live
Every entry is a Draft, In review, Scheduled, Published or Archived. The publishing queue gathers what's waiting, and publishing is one click from it.
Geiger ContentFive statuses, set from the entry itself
Atlas Coffee's editors move an entry along from its Visibility section: send it for review, give it a date, publish it or archive it. All Content shows where everything stands.
Everything with a date, in one list
Give an entry a date and it joins the Scheduled screen, so the next few weeks of releases sit side by side.
Archive without losing anything
Archived entries leave editing and delivery but wait on the Archived screen, ready to restore as a draft.
Snapshots you can roll back to
Saving in the structured editor and publishing both take a numbered snapshot of the entry. Compare any two, and put an older one back when a change goes wrong.
Geiger ContentRoll back with your eyes open
Pick a baseline and a later version to see every path that changed. Restore puts the baseline's title, slug, excerpt, body and data back on the live entry, and says so before it does.
A log of every publish
Publishing History lists each publish across every entry with the snapshot it took, and restores any of them as a draft.
Take it down as fast as it went up
Unpublish a live entry from the queue and it goes back to Draft, out of the delivery API.
Decide who can publish, and see who did
Roles and permissions are enforced in the database, every change lands in an append-only audit log, and the delivery cache clears on demand.
Geiger ContentRoles built from permission keys
Start from the Owner, Admin, Editor, Writer and Viewer roles, or compose your own from the permission catalog. Atlas Coffee's shop editors can edit and publish, but not delete.
An append-only audit log
Every create, update and delete across entries, collections, assets and slots is recorded, with who did it and when.
Clear the cache when you need to
Invalidate a published entry and its delivery caches expire, so the next read fetches the fresh version. Each request is logged.
Check a permission before it matters
The permission tester evaluates one person's grants against any permission key, straight from the database, without changing anything.
Everyone in their place
Team & Members shows who holds which role. Invite people, change their role or revoke a grant from one list.