---
title: Author content
slug: dxp/docs/content-authoring
docTags: 
createdAt: 2026-07-30T20:33:08.015Z
---

Optimizely offers many possibilities to control the editing process. Content is versioned, and you can preview and verify it before publishing, meaning specific content staging solutions are often unnecessary. 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 Optimizely and ensures that work in progress is never externally exposed until actively published. Using **Projects**, editors can group different content sets and collaborate on drafts, preview the result, and then publish all content items instantly or schedule for later publishing.

![Projects and the publishing flow](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/7dmHsZD9CBBDfbyQe0g2O-20260722-203652.png "contentauthoring.png")

You can use business process workflows in the editing and publishing process, such as using access rights to restrict who can publish. See [Control the publishing process in the Optimizely User Guide](docId\:YVDlNBYlqrxi1xSQ0t7ak).

## Deployment cycles and content authoring

Whether a website is being set up or if the website is already in full production, editors add content in different environments. See the [Environments](docId\:nkd5j5cDfZKtxIoCNqnn5) and [Deploy](docId\:KiD2UHYvZbbOKUp6LQaM1) sections for an explanation of environments and deployment scenarios.

### Create a site with DXP

A site is created in your local development environment. You will eventually deploy the site and any content to the Integration environment to verify functionality and integrations. Editors can create initial content in the **local development environment** or the **Integration** environment. Approaching launch time, the site and its content are first deployed to **Preproduction** for final verification and then to **Production**.

### Move an existing site to DXP

Existing sites (with or without content) that you want to move to a cloud environment for the first time need to be deployed to the **Integration** environment as described in [Deploy an existing CMS site](docId\:O-u0L3gdPwwJMi0xCFRLL) and [Deploy a new Commerce Connect site](docId\:I7WgsbINdjXojVJ9woFED). Editors can add more content in the **Integration** environment and then in the **Production** environment when the site is deployed.

### Existing live site in DXP

For existing live sites using DXP, the main content authoring is done in the **Production** environment, using the publishing features available in Optimizely. Content should only be created in the **Integration** environment when creating sites and never in the **Preproduction** environment because it is overwritten in upgrades.

**Related blog post:** [DXP Automatic Image Optimization ](https://world.optimizely.com/blogs/scott-reed/dates/2018/5/dxc-automatic-image-optimization/) by Scott Reed.