Projects

Info: The Projects feature in Bloomreach Content requires a standard or premium license. Contact Bloomreach for licensing details.

Projects let you group and manage changes to channels and content that need workflow approval before publishing.

Introduction to Projects

Hint: Use Projects for channels with up to 200 pages and 200 documents at the same time. Larger sets can reduce UI responsiveness in Bloomreach Content.

Tasks

Concepts

Project

A project contains related changes to channels and content.

After review, you can merge these changes into the core or publish them as a campaign.

When you add a channel to a project, you create a copy of the live channel as it exists in core. Changes made to the channel within the project remain isolated until you merge or run the project as a campaign. If the original channel changes in core after you add it to a project, you can update the project to synchronize with the latest core version.

Adding a document to a project works the same way. You edit the document within the project, and the changes are published when you merge or run the project.

Campaign

A campaign is a project that goes live without being merged into core. Starting a campaign publishes all channel and content changes in the project. You can stop a running campaign (which reverts channels and content to core) or merge it to core to make changes permanent. Campaigns can be started and stopped manually or scheduled for specific dates and times.

Core

The core represents the main, live state of all channels and documents. Changes in any project do not affect core until you merge the project. Updates to core do not appear in a project until you update that project.

Review

A review is the process where at least two webmasters verify each channel and content change in a project. Changes are either accepted or rejected.

Accepting

Any webmaster can accept channel and content changes in a project during the review phase. Each change must be accepted by two webmasters before you can merge the project into core or run it as a campaign.

Rejecting

Any webmaster can reject a channel or content change in a project during review.

If any change is rejected, the project cannot reach the approved state and cannot be merged or run as a campaign.

When a document or channel is rejected, it becomes editable again. You can restart the review after making changes, or remove the document or channel from the project.

Merging

Merging applies all channel and content changes in a project to core, making them live. During merging, project changes overwrite the corresponding items in core. For example, if a component in a project is set to display banner Y and the same component in core displays banner X, merging will update core to show banner Y.

Updating

Updating a project applies channel changes from core made since the project was started or last updated, to the project's channels. For example, if a component in the UK channel changes in core, updating the project will bring that change into the project's version of the UK channel.

Hint: Updating a project only includes channel changes from core. Content changes in core are not included when you update a project.

Comments

A project can include channel and content changes from multiple contributors. Use comments within a project to log and track these changes. Comments help all users understand the impact of merging the project into core.

Comments are also useful if a change is rejected. The user who rejects a change can explain the reason, allowing immediate follow-up actions.