When the project feature has been enabled by an administrator, a project bar is displayed at the bottom of the CMS window.
When you first access the edit view with the project feature enabled, no project is selected in the project bar. When a project has been selected, it is preselected the next time you open the user interface.
If a project is active, that is, is selected in the project bar, all changes (creating a new page or block, updating existing content, uploading an image and so on) are automatically associated with that project.
If you select the option None (use primary drafts), you can work with content items as usual without associating them with any projects.
From the context menu on the project bar, you can create, rename and delete projects.
If an active project is deleted, the project bar turns red. Associated items are not deleted but are no longer associated with a project.
From the projects bar, you can open an overview which displays all content items that are associated with the active project.
Each content item in the overview has a context menu from which you can set the item to Ready to publish, open it for editing and remove it from the project, providing you have Edit access rights. The context menu button is displayed when you hover the mouse over an item.
You can select multiple items in the overview and remove them from the project or set them as Ready to Publish all at the same time. Common mouse and keyboard functionality for selecting multiple items is supported, except for Ctrl + a which is not supported.
From Options in the overview, you can publish all items that are set to Ready to publish immediately or schedule them for publishing at a later time.
Show comments opens a view where you can select a project item and see a list of events connected to the item. You can add comments on each event and also reply to comments, see Working with comments for more information.
Use the Sort button to sort content items for a better overview, and the Refresh button to reload the view if there are multiple editors working on the same project.
This can be used for quick access to items in the project. Double-click on an item to open it.
Each content item in the project items pane has a context menu displayed when you hover the mouse over an item; the menu options are the same as those in the project overview. It is also possible to select multiple items in the list the same way as in the project overview.
When opening an item, Episerver CMS displays the version that is set as primary, which does not necessarily have to be the latest version. You can see which version is the primary in the version gadget; the primary version is marked with a target symbol . When the project feature is not enabled, the primary draft is the latest edited version of the content.
When the project feature is enabled, versioning works like this:
|Project 'X' is selected||Result|
|and you create new content from scratch:||The draft is created and added to the active project automatically. Since this is the only version of the content, it is set as the primary draft.|
|and you update existing content:||
Is the content a draft and associated with the active project?
Yes: The draft is saved and still associated with the active project. Whichever version was the primary draft before is still the primary draft.
No, the content is a published version or a draft not associated with the active project: A new draft is created and is associated with the active project. The previous version is still the primary draft. Note: If there is a previous draft within the project, it is replaced with this new draft as only one version can be associated with a project. The previous draft remains in Episerver as a draft but is no longer associated with a project.
|None (use primary drafts) is selected||Result|
|and you create new content from scratch:||The draft is created and set as primary draft.|
|and you update existing content:||
Is the content a draft? Note: it does not matter if the content is associated with a project or not; versioning works the same in this case.
Yes: The draft is saved and is not associated with a project. Whichever version was the primary draft before is still the primary draft.
No, the content is not a draft: A new draft is created and is not associated with a project. It is set as the primary draft. Note: if the updated content is a media file and auto publish is turned on, the media is automatically published at this stage.