Content Versioning: Snapshots, Diffs, and Rollbacks

Your content team updated the pricing page to reflect new tier names. Ten minutes after publishing, the sales team reports that the old Enterprise plan details are still live. The editor who made the change isn't in yet. Without version history, you're either reverting manually or waiting for the editor. With versioning, you check the diff, confirm the issue, and roll back in under a minute.

How ContentGrid Versions Content

ContentGrid stores a snapshot of every entry each time it's saved or published. A snapshot captures the full field state at that moment: every text field, every reference, every locale. Snapshots are immutable: once created, they're not modified. New saves create new snapshots.

Each entry has a version history panel that shows every snapshot with its timestamp, the user who created it, and the publish status at that time. You can click any snapshot to see the full entry state at that point.

Reading a Diff

ContentGrid's diff view highlights field-level changes between any two snapshots. Changed text shows additions in green and removals in red, similar to a git diff. Reference changes show which linked entries were added or removed. If an editor accidentally deleted a paragraph, the diff makes the deletion obvious at a glance: you don't have to read through the entire entry to find the change.

• Compare any two snapshots, not just adjacent ones
• Filter diffs by locale to review translation changes independently
• See who made each change and when

Rollbacks

Rolling back in ContentGrid creates a new snapshot from the content of an older one: it doesn't delete the intermediate history. This means the rollback itself is auditable: you can see that version 8 was created by restoring version 5, and you can always re-apply version 7 if you change your mind.

Rollbacks do not automatically republish. You get to review the restored content in draft state before pushing it live. That review step prevents a situation where a rollback accidentally brings back content that was intentionally removed.

Version History in Production Systems

Version history is most valuable in two scenarios: recovering from mistakes (the most common case) and compliance auditing (who changed what and when). If your organisation has compliance requirements around content accuracy (financial services, healthcare, legal), ContentGrid's version history provides an immutable audit trail that you can export or query via API. Every published version is preserved, with its timestamp and authoring metadata, for as long as the entry exists.