Revision Workflow

Every change is a revision

In Svalla, every content change creates a revision. A revision is a snapshot of the content at a specific point in time. This means:

• No content is ever lost — every version is preserved
• You can compare changes over time
• Rolling back to a previous version is always possible

Revisions apply to both page sections and blocks, so all content in your project benefits from version control.

Content lifecycle states

Each revision has a status that determines its visibility and behavior:

• Draft — work in progress, only visible in the back-office. Editors can save drafts without affecting the live site
• Public — published and live. This revision is returned by the API and visible on the frontend
• Scheduled — set to publish automatically at a future date and time
• Approved — reviewed and approved by an editor, ready for publication
• Rejected — reviewed and rejected, with optional feedback for the author
• Ignored — dismissed revision that won't be considered for publication

From draft to live

The typical publishing flow:

• Save as draft — contributor creates or edits content and saves without publishing
• Submit for review — the draft is ready for editorial review
• Approve or reject — an editor reviews the content and makes a decision
• Publish — approved content goes live immediately

For simpler workflows, editors can publish directly without going through the approval process. The workflow adapts to your team's needs.

When content is published, Svalla can trigger an automatic frontend rebuild to ensure the live site reflects the latest changes.

Publish at the right time

Scheduled publishing lets you prepare content in advance and set it to go live automatically at a specific date and time.

Use cases:

• Prepare a product launch page days in advance
• Schedule blog posts for consistent publishing cadence
• Coordinate content releases with marketing campaigns
• Set promotion banners to appear and disappear automatically

You can also set a publication end date to automatically unpublish content after a specific date.

Revert to any previous version

If something goes wrong, you can rollback to any previous revision:

• View the full revision history for any section or block
• See who made each change and when
• Select a previous revision and restore it
• The rollback itself creates a new revision, so the action is reversible

This gives your team confidence to make changes knowing they can always go back.

Who can publish what

Publishing permissions are tied to user roles:

• Contributors — can create drafts but cannot publish. Their content must be reviewed by an editor
• Editors — can publish, approve, and reject revisions. They manage the editorial flow
• Administrators — full control over all content and settings

This ensures that junior team members or external contributors can safely create content without accidentally publishing unreviewed material.