Assembling Version Snapshots of Your Web Content

Objective

After completing this lesson, you will be able to assemble version snapshots to support creative web content development with seamless change management.

Versioning Mode

Content versioning allows Laura to take a snapshot of a page’s content at any moment in time, called a version. She can create as many saved versions as she likes. Later, by returning to one of these versions, she can view the page exactly as it was when she took the snapshot and conveniently toggle between the versions of her site. Hitting the ‘Rollback’ button makes her currently selected version the one used for her storefront, while all the other versions remain available if she changes her mind–even newer versions.

Let’s have a look at SmartEdit’s Versioning UI:

Image shows SmartEdit’s Versioning mode. It allows to create a new version by clicking the “+ Version” button and also to see all available versions of this page by clicking the “Versions” button.

SmartEdit’s Versioning mode allows you to:

  • Create, search for, and delete page versions.
  • Preview a page version, and from there, jump to that version and continue editing from there.

Both modes, Versioning and Advanced Edit, provide a ‘Versions’ button in the header bar. It allows Laura to search and toggle between versions. However, new versions can only be created in Versioning mode.

The following video gives you a brief overview of version management in SmartEdit:

As mentioned, versions aren’t deleted when Laura switches to another version. She can come back to a snapshot as often as she needs to, providing a seamless comparison of different versions. When Laura decides which version she wants to use, she rolls back to it. SmartEdit ensures that the state of the page before rolling back is automatically saved as its own version.

When Laura creates a new version, SmartEdit saves the current page with its metadata and components located in its page slots and nonshared content slots. In contrast, components in shared content slots or inherited components from parent content catalogs are not saved.

Note

Restrictions and personalization data are also not saved. These topics are covered later in this course.

Log in to track your progress & complete quizzes