Content pages (Content Items) now support versions in the backoffice. You can create a New Version, keep a clear history of changes, and always know which version is currently live. Even better: each version can be named by your team, using the naming convention that makes sense for your business (year, campaign, policy cycle, department, etc.).
Why versions are a game-changer
- Safe updates, no fear: iterate on content without risking the current version
- Clear audit trail: keep a clean history of how a page evolved over time
- Seasonal / yearly cycles: perfect for “2026 Version”, “Q1 Update”, “Policy v2”, “Onboarding 2026”, etc.
- Parallel workstreams: prepare the next iteration while the current one remains active
- Faster rollouts: update multiple pages with a consistent naming pattern and controlled publishing
- Less duplication chaos: no more “final_v7_REALLYFINAL” pages - the structure is built-in
- Easier collaboration: teams can align on what changed and when, without guesswork
- Governance and consistency: maintain standardized content while still evolving it over time
- Client-owned language: version names are yours - match your internal processes and terminology
This turns content into something you can manage like a product: structured, trackable, and always under control.