> 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/creating-pages.md).

# Creating Pages

Every page in the CMS starts life the same way — from the New Page dialog on the Pages perspective.

## 1. Create a page

Every page in the CMS starts life the same way — from the New Page dialog on the Pages perspective. This chapter walks the four fields the dialog asks for (title, URL slug, locale, site), plus the Routing and Layout tabs a routing-conscious page needs, and lands you in the editor ready to add components.

### 1.1 The dashboard, on the Pages perspective

The Pages perspective is the starting point for creating new pages. The "New Page" button sits at the top-right of the toolbar; "New Folder" next to it does the same for folders. Both open a similar dialog — this chapter walks New Page.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-164e4111868b0820444375e1c7bf1cc77bd31944%2Fcms_ug_p03_1.png?alt=media" alt="1.1 The dashboard, on the Pages perspective"><figcaption><p>1.1 The dashboard, on the Pages perspective</p></figcaption></figure>

### 1.2 Open the New Page dialog

The New Page dialog is organised into three tabs: General (title, slug, description, locale, site), Routing (parent folder, custom URL, homepage flag), and Layout (which chrome the new page uses). General is required; the other two carry sensible defaults, so a straightforward page can be created in seconds.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-b1a6b8292a0e5daf77f5c76a3583d23e09c0a987%2Fcms_ug_p04_1.png?alt=media" alt="1.2 Open the New Page dialog"><figcaption><p>1.2 Open the New Page dialog</p></figcaption></figure>

### 1.3 Fill in the title and slug

The title is what authors see in the dashboard; the slug is what appears in the URL. As you type a title, the slug field auto-fills with a URL-safe version — override it any time by typing directly into the slug field. Slugs are unique per locale and site, so the dialog will warn if a page or folder in the same scope already claims the value you typed.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-641eb646cfd4b5990bf115dc04a0932e1b473421%2Fcms_ug_p05_1.png?alt=media" alt="1.3 Fill in the title and slug"><figcaption><p>1.3 Fill in the title and slug</p></figcaption></figure>

### 1.4 Submit — the editor opens on the new page

Clicking Create Page saves the page in draft status and opens it in the editor. The page has no components yet — the tree on the right shows the empty slots the layout exposes, each with an "Add" affordance. That is where the ["Add a component"](#2-add-a-component-to-a-slot) chapter picks up.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-79af908b642cffe54da9a007489d4b08ae7655a3%2Fcms_ug_p06_1.png?alt=media" alt="1.4 Submit — the editor opens on the new page"><figcaption><p>1.4 Submit — the editor opens on the new page</p></figcaption></figure>

## 2. Add a component to a slot

A page is made of components — the reusable building blocks the storefront defines (a Hero, a Rich Text block, a Product Grid, and so on). This chapter walks adding a component to a slot and the Component Picker that lists every registered type. Once a component is on a page, the ["Edit properties"](#3-edit-a-component-from-the-property-panel) and ["Edit text in the preview"](https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/user-guide/editing-and-arranging-content.md#4-edit-text-right-in-the-preview) chapters take over.

### 2.1 The slot exposes an Add affordance

Every slot the layout marks as editable has an Add button at its bottom. Slots the layout declares as chrome — headers, footers, sidebars — are read-only from a page and show a lock icon instead. "Copy" next to Add lets you clone a component from another page rather than start from scratch.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-f54a2b40b57564eff86eac92c21d47e120c4a367%2Fcms_ug_p07_1.png?alt=media" alt="2.1 The slot exposes an Add affordance"><figcaption><p>2.1 The slot exposes an Add affordance</p></figcaption></figure>

### 2.2 The component picker lists every registered type

The picker shows every component type the storefront has registered — the ones a page in this site can render. Each card carries the type's label, a short description supplied by the storefront, and its technical identifier. Clicking a card creates a new component of that type at the bottom of the slot and closes the picker. Container types (Section, Grid, and so on) can hold children of their own, which the ["Move a component into a container"](https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/user-guide/editing-and-arranging-content.md#7-move-a-component-into-a-container) chapter covers.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-b5a7385f2cab204b4db69d989366702d1447cb9f%2Fcms_ug_p08_1.png?alt=media" alt="2.2 The component picker lists every registered type"><figcaption><p>2.2 The component picker lists every registered type</p></figcaption></figure>

### 2.3 The new row appears in the tree

The new component lands at the end of the slot and is selected automatically — the property panel below shows its fields, empty and ready to fill. From here you can edit its properties ([Edit properties chapter](#3-edit-a-component-from-the-property-panel)), move it up or down with Alt+↑/↓ ([Reorder and delete](https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/user-guide/editing-and-arranging-content.md#6-reorder-and-delete-components)), or drag it into a container. Nothing is saved yet; Save to persist as a draft.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-ad1d5b82bc581b58eae3d3608539adb5c3e9b004%2Fcms_ug_p09_1.png?alt=media" alt="2.3 The new row appears in the tree"><figcaption><p>2.3 The new row appears in the tree</p></figcaption></figure>

## 3. Edit a component from the property panel

Every component on a page has a set of fields the storefront defined — text, media, links, and so on. This chapter walks the "structured" way to edit them: select the component in the tree, and change its values in the property panel that appears below. Its sibling chapter, ["Edit text right in the preview"](https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/user-guide/editing-and-arranging-content.md#4-edit-text-right-in-the-preview), covers the direct-manipulation alternative.

### 3.1 The property panel shows the component's fields

Clicking a row in the tree — or a component in the preview — opens its property panel. Each field is labelled with the name the storefront gave it: text fields use plain inputs; rich text uses a small editor with formatting controls; media opens a picker; links show label and URL side by side. The panel scrolls if a component has more fields than fit.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-faa3906c1c3ab0c341c435052f2e8ea95e82fe44%2Fcms_ug_p10_1.png?alt=media" alt="3.1 The property panel shows the component&#x27;s fields"><figcaption><p>3.1 The property panel shows the component's fields</p></figcaption></figure>

### 3.2 Change the headline in the input

Typing writes to the working draft immediately — you don't click a "commit" or "apply" button. Tab or click away to signal you're done with a field; a small saved-successfully toast confirms every commit. The value has been captured but the draft has NOT been persisted yet; the browser holds it in memory until Save.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-d5f2ca3e7c9681a11f11bdc1b6809263dd0139cd%2Fcms_ug_p10_2.png?alt=media" alt="3.2 Change the headline in the input"><figcaption><p>3.2 Change the headline in the input</p></figcaption></figure>

### 3.3 The preview follows the edit

The preview iframe re-renders the changed component in place — no reload, no flash. That live loopback is what lets you iterate on copy or media without leaving the editor: each change lands in the preview within a frame or two of committing it, and stays there until you change it again or navigate away.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-a50572f04704bfec206de6ae8b3ca0160c883384%2Fcms_ug_p11_1.png?alt=media" alt="3.3 The preview follows the edit"><figcaption><p>3.3 The preview follows the edit</p></figcaption></figure>

### 3.4 Save the draft

Save persists everything you've typed since the last save as a draft — the version pill flips from Live to Draft to reflect that. The change is now durable across page reloads and other authors on the same tenant, but it is still not visible to visitors. Publish, in a separate step, is what makes it public.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-23383bf23f903eedc10dcbbf0acb6ce63eb6e0b8%2Fcms_ug_p12_1.png?alt=media" alt="3.4 Save the draft"><figcaption><p>3.4 Save the draft</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/creating-pages.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.
