A project lets an editor manage the publishing process for multiple related content items. The editor can add a landing page, blocks, pages, and products (if Commerce is installed) to a project and publish them (manually or scheduled) at the same time.
There are two options when working with projects, either the projects feature (also known as Project Mode) is enabled for the entire site or each user can, independently of others, use the "old" project gadget.
Project mode features:
- (New in CMS 10.2): The projects feature is either enabled or disabled for the entire site and affects all users, it is enabled by default. To disable projects, you need to add an entry to appSettings, episerver:ui:IsProjectModeEnabled = false. When enabled, a project bar displays at the bottom of the user interface. A project overview and a Project Items navigation pane also appear.
- Editing actions, such as creating and updating items, automatically associate a content item with a currently active project. Exceptions to this rule include moving items in the structure, setting content to expired, changing access rights or language settings. These actions do not associate content items with the active project.
- A project must be manually deactivated to stop items from being automatically added to the project.
- Project items are only available to users who have access rights to the items.
- Content associated with a project is locked for editing if another project is active.
- It is a version of the content that is associated with a specific project, which means that one draft of a page can be associated with project A and while another draft of the same page is associated with project B.
- You can continue working with a project after some or all of the items within a project are published.
- The project overview has a commenting feature, letting editors collaborate by adding comments and replies to comments to project items and to projects. Editors also can tag users in the comments.
- You can set up Episerver to send out email notifications to editors.
Example workflow when working with projects
- Create a project (or set a project as active).
- Edit content items.
- Collaborate with other editors by adding comments to the edited project items and review changes.
- Preview the site as if the items in the project are published.
- Set all items in project as Ready to Publish.
- Publish all items at once (or schedule them for later publishing).
Versioning in Episerver works slightly different when then projects feature has been enabled. For more information on versioning in projects, see the Episerver User Guide.
Editors can be notified by email when someone else comments on their project actions (like setting a project to Ready to Publish) or replies to their comments. Editors also get an email if someone else tags them in a comment. How often these notifications are sent depends on the system configuration.
Note: You need to configure the SMTP settings for Episerver CMS to send out email notifications, see Configuring your email server.
Notification Message Truncate
The Notification Message Truncate job truncates (deletes) 3-months old notification messages that could not be sent and are still in the system. The job is enabled by default, and set to run every day.
The settings in the Notification Dispatcher job determine how often Episerver CMS sends notifications of new or updated comments or replies posted in projects by a notification provider (for example, an e-mail provider). Notification messages are sent to:
- users who are tagged in a comment or reply,
- users who receive replies to their comments,
- users who receive comments on their project actions (such as setting a project item to Ready to publish),
- and other users who have previously replied to the same comment.
No notification is sent if no new comments or replies were posted since the job last executed.
The job is enabled by default, and set to run every half hour.
Do you find this information helpful? Please log in to provide feedback.
Last updated: Oct 27, 2016