Content

Drafts and conflicts in the CMS

Editors work in named drafts, see exactly what the live site changed in the meantime, and choose what to keep while watching the result on the site.

I can prepare a campaign in words I already use, and every change on the live site stays until someone decides otherwise.

CMS editor or marketer working on content ahead of a launch

What it does

  1. Work in a named draft, such as a Halloween campaign, while the live site carries on
  2. See when the live site has changed something you are also changing, right on the page you edit
  3. Compare both versions property by property, from colours and spacing to texts and images
  4. Watch the site follow each choice before anything is saved
  5. Bring the live site's changes in and publish in one step

Why it matters

Marketers plan campaigns, such as Halloween, weeks ahead while the live site keeps changing. They work in a draft with a name they recognise and publish it when it is ready. When a colleague has changed the same heading, colour or picture on the live site in the meantime, the editor sees both versions side by side, down to the property that differs, and picks one. The site shows the result of each pick at once, so the editor decides by looking at the page rather than at settings. Developers keep the branch, its commits and how it relates to the live site one click away.

Ready to see Fusion in action?

Book a personalized demo and see these features working on your own catalog and customers.

BOOK A DEMO