Hide menu Last updated: Oct 08 2015
Area: Episerver DXC Service Applies to versions: Not applicable

Content authoring

This topic describes how to work with content in solutions based on Episerver Digital Experience Cloud Service. Episerver offers many possibilties to control the editing process. Content is versioned and can be previewed and verified before publishing, meaning that specific content staging solutions are often not needed. Depending on where the site is in the deployment cycle, content is added in different environments as described below.

Projects and the publishing flow

The draft concept is central in Episerver, and ensures that work in progress is never externally exposed until actively published. Using Projects, editors can group different sets of content and collaborate on drafts, preview the result, and then publish all content items instantly, or schedule for later publishing.

Business process workflows can also be utilized in the editing and publishing process, for instance by using access rights to restrict who can publish. See Controlling the publishing process in the Episerver User Guide.

Deployment cycles and content authoring

Depending on if it is a new website being set up for the very first time, or if the website is already in full production, editors will add content in different environments. See the Environments and Deploying sections for an explanation of environments and deployment scenarios.

Creating a new site with DXC Service

A new site will be created in your local development environment. At some point, you will deploy the site and any content to the Integration environment for verification of functionality and integrations. Editors can create initial content in the local development environment, or in the Integration environment. Approaching launch time, the site and its content will be deployed (by Episerver) first to the Preproduction for final verification, and then to Production.

In the case of a new site, there is also a possibility to restrict access to the Production environment and let editors add the bulk of the content here, once the code has been deployed (by Episerver).

Moving an existing site to DXC Service

Existing sites (with or without content) that you want to move to a cloud environment for the first time, will need to be deployed to the Integration environment as described in Deploying an existing CMS site and Deploying a new Commerce site. Editors can then add more content in the Integration environment, and then in the Production environment, once the site has been deployed there (by Episerver). 

Existing live site in DXC Service

For existing live sites using DXC Service, the main content authoring is done in the Production environment, using the publishing features available in Episerver. Content should only be created in the Integration environment when creating new sites, or developing new functionality. Content should never be created in the Preproduction environment, since this will be overwritten in upgrades.

Related topics