Publishing

Publish fearlessly

Every version is kept forever, diffable visually and in code, and revertible in one click. Staging and production are separate gates with their own permissions.

Publishing documentation

Version history you can trust

Append-only publishing means you never lose a version. Widgets support visual compare, JSON diff, republish, and restore-to-draft.

Append-only version history

Every publish creates a new semantic version (1.0.0, 1.0.1, …). Drafts are never overwritten. The full audit trail is preserved forever.

Visual and code diff

Compare any two versions side-by-side — rendered previews across desktop, tablet, and phone, plus JSON and split-diff code views.

One-click revert

Republish any previous version to roll back live content instantly. Restore any version to draft for further editing — history stays intact.

Staging → production gates

Publish to staging first. Separate permissions control who can promote to production. Every gate is permission-aware.

The publishing workflow

  1. Edit draft

    Compose in the visual editor or edit JSON. Auto-save keeps work safe.

  2. Publish to staging

    Ship to staging. Compare versions before promoting.

  3. Compare versions

    Visual preview diff and JSON diff between any two versions.

  4. Promote to production

    Production publish requires separate permissions.

  5. Revert if needed

    One-click republish of any previous version.

Widgets and shared collections share the same publishing workflow: version history, visual and JSON compare, republish a previous version, and restore any version back into your draft.

Pair publishing with automatic cache invalidation so republished content reaches your sites immediately.

Explore RuleCMS

Dive deeper into what makes RuleCMS different.

Stop fearing the publish button

Full history, visual diff, and one-click rollback — included.