Duff Cloud Services Docs

Appearance

Releases & Version History ​

The portal keeps a full history of your site's releases and gives you the controls to publish, compare, and roll back. This page covers Version History (the timeline of what shipped) and Release Management (the difference between what is live and what is in draft, down to individual changes).

Queued edits — like the text changes you Save in the Visual Editor — become live through a release. This is where you turn staged work into a deployed site.

Version History ​

Open Version History to see every release. You can view it as a calendar, grouped by date, or as a list. Select any version to inspect it.

Publishing a draft ​

When you have pending changes ready, publish the draft. Publishing triggers a production deployment and reports how many changes are being deployed, with a link to follow the deployment workflow. Publishing and editing release notes require editor-level access or higher on the site.

Comparing versions ​

Pick two versions and open a side-by-side comparison to see exactly what changed between them.

Rolling back ​

If a release causes a problem, you can roll back to an earlier version. A rollback rolls the site down through every version from the current release to your chosen target, and it runs as a tracked request rather than an instant flip. When you confirm, you provide a reason and can mark the rollback urgent.

Rolling back can discard an in-progress draft

If you have uncommitted draft changes, the editor warns you that rolling back will lose them. Save or publish work you want to keep first.

If you do not have editor access, you can still submit a Restore Request for an earlier version; a Duff Cloud Services admin reviews it.

Release Management ​

The Release Management view lines up your production version against your development version so you can see what is live versus what is staged.

Reverting a single change ​

Rather than rolling back an entire release, you can revert an individual pending change. Reverting requires a reason, which is recorded with the change.

The view updates in real time over a live connection, so deployment status and version changes appear without a manual refresh.