The project capabilities in Experience Manager let a team of business users update and test their application in isolation without fear of publishing content that is not ready. No changes in a project are committed to the application in Experience Manager until the project is published.

The following example shows how a merchandiser named Melanie can use Experience Manager to update and preview content without actually publishing the content. Melanie is a merchandiser for the reference Discover Electronics application. She wants to make a few changes for the Summer promotion:

She can make these changes in a single project so that she does not interfere with any other promotions or projects.

  1. Melanie logs into Experience Manager and clicks the project tile of the Workbench toolbar.

    She sees that there is one unpublished project named One Day Sale that Paula, another merchandiser, has created.

  2. Melanie names her untitled project Summer Promotion.

  3. Melanie's manager noticed that the Contact Us page needs to be updated as well, so she asks Melanie to include the update in her project. Melanie decides to make this simple update first.

  4. Pleased with her change to the Contact Us page, Melanie updates the promotional text on the Cannon brand page.

  5. Next, Melanie moves on to her last task in her assignment. She must update the Featured Lenses spotlight on the Camera Accessories & Supplies category page. It is currently sorted by average rating. Her manager asked her sort it by price.

  6. Melanie is prepared to publish the project. She sees a conflict icon where the Project contents icon used to be.

  7. Because Melanie's project is no longer in conflict with a published project, she decides that she can publish her project.

Melanie's project has been published. All her updates are now part of the current Experience Manager application. If she want to make more changes, she must start a new project or open an unpublished project.


Copyright © Legal Notices