> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/user-guide/publishing-workflow.md).

# Publishing Workflow

Save and Publish are two separate actions, and the split is deliberate: Save is safe (only you see the result), Publish is visible-to-the-world.

## 15. Save a draft and publish it

Save and Publish are two separate actions, and the split is deliberate: Save is safe (only you see the result), Publish is visible-to-the-world. This chapter walks each in turn and shows the version pill flipping between Draft and Live. The ["Publish a page"](#16-publish-a-page) chapter is a longer variant of the same flow — pick either as a reference.

### 15.1 Save produces a draft — the pill flips, and Publish becomes available

Save writes the working state as a draft — a version only authors on this tenant can see. The version pill flips to yellow "Draft" and the approval pill next to it shows "Open" (the initial approval status). The Publish button lights up because there is now something new to publish. Reload the browser and the draft is still there; open the page in another tab and the same draft loads.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-93752bb3b3d75f38a12d66bb7d3fa2ae3ef5d3d2%2Fcms_ug_p37_1.png?alt=media" alt="15.1 Save produces a draft — the pill flips, and Publish becomes available"><figcaption><p>15.1 Save produces a draft — the pill flips, and Publish becomes available</p></figcaption></figure>

### 15.2 Publish promotes the draft to live

Publish promotes the draft to live — visitors to the site now see the new content on their next page load. The pill flips green and reads "Live"; the approval pill disappears because there is no draft to have a status. The Publish button dims because there is nothing new to publish; it lights up again the moment you start another edit.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-e41a408bc697bc9d131c548d3e14e1d416d07975%2Fcms_ug_p37_2.png?alt=media" alt="15.2 Publish promotes the draft to live"><figcaption><p>15.2 Publish promotes the draft to live</p></figcaption></figure>

### 15.3 The live row really carries the edit

The publish wrote to the live row — the API confirms it, not just the editor. Every publish is recorded in version history; open it from the Actions menu to review previous publishes and roll back to any of them. Publish is durable, but never one-way.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-c2d843509758ac1cde54164e4ef9dda2e0c005dc%2Fcms_ug_p38_1.png?alt=media" alt="15.3 The live row really carries the edit"><figcaption><p>15.3 The live row really carries the edit</p></figcaption></figure>

## 16. Publish a page

Publishing is the moment a page becomes visible to visitors. This chapter walks a single page from its live state through an author edit, a save that produces a draft, and a publish that promotes the draft to live. Along the way it introduces the version pill, the Save and Publish buttons, and the difference between "saved" and "live" — the distinction that governs everything else about the editor's workflow.

### 16.1 The page is open in the editor

Every page opens into the same split view: the preview iframe on the left, the tree of components on the right. The header pins the page title, viewport toggles and the Save/Publish buttons above both panes. Selecting a row in the tree — or clicking a component in the preview — reveals its fields in the panel below. This is where all editing happens.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-c82d2893dc8d7c7a171296b210630ff8e232ed47%2Fcms_ug_p39_1.png?alt=media" alt="16.1 The page is open in the editor"><figcaption><p>16.1 The page is open in the editor</p></figcaption></figure>

### 16.2 Edit the headline in the property panel

Field labels come from the storefront — every text, media and link field a component declares appears here as a labelled input. Typing into an input writes to the working draft immediately; the preview reflects the change as soon as you commit (Tab out of the field, or click somewhere else). Nothing has been persisted yet — the change lives only in the browser until Save.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-f44ba332a42e7c93d4639906c7195b24cb56ab8a%2Fcms_ug_p39_2.png?alt=media" alt="16.2 Edit the headline in the property panel"><figcaption><p>16.2 Edit the headline in the property panel</p></figcaption></figure>

### 16.3 Save the draft

Save writes the current state as a *draft* — a version that only you can see. The version pill in the header flips from "Live" to "Draft", the preview re-navigates through the editor's authenticated route, and the Publish button lights up. Visitors to the site still see the previous live version; the draft is your sandbox until you decide to publish.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-9961ff402b54c8eb6a63a97e6946beb1c7f1dd50%2Fcms_ug_p40_1.png?alt=media" alt="16.3 Save the draft"><figcaption><p>16.3 Save the draft</p></figcaption></figure>

### 16.4 Publish the page

Publish promotes the current draft to live. The version pill flips to green and reads "Live"; the draft is consumed by the promotion, so the Publish button dims until the next edit. Anyone visiting the site now sees the new content on their next page load — including cached CDN clients as their caches refresh. If your team's setup requires approval before publish, this button opens the approval dialog instead of publishing directly.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-4b0fa1c70768d6a15c33a5497d3e88cb6965e180%2Fcms_ug_p41_1.png?alt=media" alt="16.4 Publish the page"><figcaption><p>16.4 Publish the page</p></figcaption></figure>

### 16.5 The page is live

The preview now shows exactly what visitors see — the published edit is the live content. From here you can start another edit (it will create a new draft on top of this live version) or move on to another page. Version History (in the Actions menu) lets you review the full chain of previous publishes and roll back to any of them, so publishing is never a one-way door.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-203cb750c560c5e251d600ae7c5b891e05677e58%2Fcms_ug_p42_1.png?alt=media" alt="16.5 The page is live"><figcaption><p>16.5 The page is live</p></figcaption></figure>

## 17. Submit for approval, then approve

The approval workflow is a lightweight review gate for teams that don't want every author publishing straight to live. This chapter walks the full arc — a change is drafted, submitted for approval, approved, and finally published. The status pill on the editor header shows every transition; the API records who decided when.

### 17.1 A saved draft starts in the "Open" approval state

Every draft starts as "Open" — an author is still working on it. The chip sits next to the version pill and reads the current state of the workflow. Clicking it opens a menu with the transitions available from here.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-93752bb3b3d75f38a12d66bb7d3fa2ae3ef5d3d2%2Fcms_ug_p37_1.png?alt=media" alt="17.1 A saved draft starts in the &#x22;Open&#x22; approval state"><figcaption><p>17.1 A saved draft starts in the "Open" approval state</p></figcaption></figure>

### 17.2 Mark for approval — the draft moves to "Pending"

Submitting flips the status to "Pending" and freezes the draft against further author edits from the workflow perspective (edits still land in the draft; the pending flag is what a reviewer keys on). Anyone with the approver role now sees the draft in their queue via the API; a dedicated reviewer dashboard is a follow-up feature.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-e7e48f297c4e038cece8f5a0e4e29b1f76797251%2Fcms_ug_p43_2.png?alt=media" alt="17.2 Mark for approval — the draft moves to &#x22;Pending&#x22;"><figcaption><p>17.2 Mark for approval — the draft moves to "Pending"</p></figcaption></figure>

### 17.3 Approve — the draft moves to "Approved"

Approving records who decided and when. If the tenant setting "require approval before publish" is on, Publish stays disabled until this step lands. Reject follows the same menu and asks for a reason; the reason travels with the draft and is visible to the author when they reopen it.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-80c95bcf7a5221eaba59705e69cec6d051e8e4b7%2Fcms_ug_p43_3.png?alt=media" alt="17.3 Approve — the draft moves to &#x22;Approved&#x22;"><figcaption><p>17.3 Approve — the draft moves to "Approved"</p></figcaption></figure>

### 17.4 The approval state is recorded on the backend

The workflow state lives on the draft row itself — cms-api stores who approved and when, alongside the content. Publishing from here is a normal publish; the workflow state is cleared with the draft (a fresh edit starts again from Open).

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-269fa41845f5a63c91d8b719875b1c13160a7614%2Fcms_ug_p44_1.png?alt=media" alt="17.4 The approval state is recorded on the backend"><figcaption><p>17.4 The approval state is recorded on the backend</p></figcaption></figure>

## 18. Roll back with Version History

Every publish is archived. If a publish went out that shouldn't have — a typo, a wrong image, an accidental delete — Version History lets any authorised author roll back to a previous state without editing anything by hand. This chapter walks opening the dialog, picking a row, and restoring it.

### 18.1 Open the Actions menu

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-35b3b35e41080f668be1c70a01a107fea7f741ee%2Fcms_ug_p45_1.png?alt=media" alt="18.1 Open the Actions menu"><figcaption><p>18.1 Open the Actions menu</p></figcaption></figure>

### 18.2 The Version History dialog lists every archived publish

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-eeed6527726c9615c2dc9e245e92797e84d76a76%2Fcms_ug_p45_2.png?alt=media" alt="18.2 The Version History dialog lists every archived publish"><figcaption><p>18.2 The Version History dialog lists every archived publish</p></figcaption></figure>

### 18.3 Click Restore — the older content is republished

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-9c180701f6ad9eca464bf3d768747d606132175a%2Fcms_ug_p46_1.png?alt=media" alt="18.3 Click Restore — the older content is republished"><figcaption><p>18.3 Click Restore — the older content is republished</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/user-guide/publishing-workflow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
