> 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/editing-and-arranging-content.md).

# Editing and Arranging Content

Inline editing is the shortest path from noticing a typo to fixing it: double-click a text field in the preview and type — no round-trip through the property panel.

## 4. Edit text right in the preview

Inline editing is the shortest path from noticing a typo to fixing it: double-click a text field in the preview and type — no round-trip through the property panel. The commit is symmetric: whatever you type in the preview appears in the panel and vice versa. This chapter shows the gesture, and the small purple "Text" badge the editor uses to signal an editable field.

### 4.1 The editable field is annotated in the preview

Editable fields carry a small purple "Text" badge when the editor is active — a hint that a double-click will edit them in place. Single-click still selects the component (as it does anywhere else on the preview); the double-click is what opens the field for editing. Link labels are the exception: a single click on a link edits its label instead of navigating, so authors do not need to hold a modifier key to work with them.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-d00ef2bbb8edbf4ac8781c310838e311cff71d72%2Fcms_ug_p13_1.png?alt=media" alt="4.1 The editable field is annotated in the preview"><figcaption><p>4.1 The editable field is annotated in the preview</p></figcaption></figure>

### 4.2 Double-click the headline and type

The field becomes editable in place — same font, same size, same position as the rendered text. Selection works normally: ⌘/Ctrl+A selects all, arrow keys move the cursor, Shift+arrows extend the selection. Bold, italic and other rich-text controls are not available in inline edit — those live in the property panel for the fields that support them.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-6e8139b89b54dddc45acaf363cd2fa0ac9596082%2Fcms_ug_p14_1.png?alt=media" alt="4.2 Double-click the headline and type"><figcaption><p>4.2 Double-click the headline and type</p></figcaption></figure>

### 4.3 Enter commits the edit

Enter commits the new value; Escape cancels and restores the original. Committing writes to the same working draft the property panel does — the two views are always in sync. As with the ["Edit properties" chapter](https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/user-guide/creating-pages.md#3-edit-a-component-from-the-property-panel), the change is not persisted yet; Save writes it to a draft, Publish makes it live.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-e2aa25de6a8ad7209f952347126f5ff364fbdabe%2Fcms_ug_p15_1.png?alt=media" alt="4.3 Enter commits the edit"><figcaption><p>4.3 Enter commits the edit</p></figcaption></figure>

## 5. Choose when your typing is picked up

Editing text directly in the preview can work two ways, and which one feels right is a matter of taste. By default a change is picked up when you finish the field — the panel on the right stays still while you write a sentence. Switch it and the panel follows every keystroke, so both halves of the screen always agree. The same menu switches editing off entirely, for when you want to look at the page the way a visitor does.

### 5.1 One control, three states

The default is "when I finish": you can write a whole sentence without the right-hand panel moving under you. The same menu holds the other behaviour and an off switch, because they are one decision about how the preview behaves rather than three separate features. Your choice is remembered — it is a preference, not a per-page setting, so it follows you to every page and survives a reload.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-ee6ed76c263d11a69246c4e26e98028a748d7ca8%2Fcms_ug_p16_1.png?alt=media" alt="5.1 One control, three states"><figcaption><p>5.1 One control, three states</p></figcaption></figure>

### 5.2 Switched to as-you-type, the panel follows every keystroke

With this mode chosen, every keystroke is picked up (after a short pause, so a word is not sent letter by letter). The component tree and the property panel stay in step with the preview as you write — useful when you are watching how a change affects a heading and a summary at the same time.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-e8a6a1cdaa7971582525f26c3571397cd186e789%2Fcms_ug_p16_2.png?alt=media" alt="5.2 Switched to as-you-type, the panel follows every keystroke"><figcaption><p>5.2 Switched to as-you-type, the panel follows every keystroke</p></figcaption></figure>

### 5.3 Switched off, the preview stops offering to be edited

Off is for reviewing rather than writing: the edit markers disappear and a double-click no longer opens a field, so the page behaves the way it will for a visitor. Selecting a component in the tree still works — finding your way around is not part of editing.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-8910225e587565371ec408e85728e4bd42baeac6%2Fcms_ug_p17_1.png?alt=media" alt="5.3 Switched off, the preview stops offering to be edited"><figcaption><p>5.3 Switched off, the preview stops offering to be edited</p></figcaption></figure>

## 6. Reorder and delete components

A page rarely stays in the order it was built. This chapter covers the two gestures for changing that order: Alt+↑/↓ moves the selected row up or down one step, and the trash icon removes it entirely (behind a confirmation, since delete is destructive). Drag-and-drop exists too but the keyboard shortcut is the primary recommendation — it works on any trackpad, cannot mis-drop, and is the only path that also works in accessibility settings.

### 6.1 The slot starts with three components

The tree lists rows top-to-bottom in the same order the storefront renders them on the page. Each row shows a small drag handle on the left, followed by the component's inline-editable label (or its type, if it has no label yet), and finally a set of hover-visible action icons on the right — move-into, delete, and expand.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-de9d9d91063a04321a4fe178632e7f8d05ababf9%2Fcms_ug_p18_1.png?alt=media" alt="6.1 The slot starts with three components"><figcaption><p>6.1 The slot starts with three components</p></figcaption></figure>

### 6.2 Alt+↑ moves the selected row up one step

Select a row (click it in the tree, or click the component in the preview), then press Alt+↑ or Alt+↓ to move it one step within the current slot. The preview reorders live to match. Reordering respects the tree's nesting — a row inside a container moves within that container. To move OUT of a container, use ["Move into…"](#7-move-a-component-into-a-container) instead.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-3152bd67965627f5fab759673e733361fd7e2541%2Fcms_ug_p18_2.png?alt=media" alt="6.2 Alt+↑ moves the selected row up one step"><figcaption><p>6.2 Alt+↑ moves the selected row up one step</p></figcaption></figure>

### 6.3 The delete gesture opens a confirmation

Hover a row to reveal its action icons, then click the red trash icon. Because delete cannot be undone from the editor UI, a confirmation dialog opens and names the component type and its id. Cancel dismisses; Delete Component removes the row (and any children it holds) from the working draft. Version History remains the escape hatch — a previous publish still carries the deleted component.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-efd04cd5852c5a917bddc06102d2cc9efe9e84d3%2Fcms_ug_p19_1.png?alt=media" alt="6.3 The delete gesture opens a confirmation"><figcaption><p>6.3 The delete gesture opens a confirmation</p></figcaption></figure>

### 6.4 Confirming removes the row from the tree

The row is gone from the tree; the preview reflects it on the next render. Deletes and reorders share the same working draft as content edits, so a single Save persists everything you've changed since the last one.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-cc347ea5bdd3044ec18949fcd0f120b4fec23877%2Fcms_ug_p20_1.png?alt=media" alt="6.4 Confirming removes the row from the tree"><figcaption><p>6.4 Confirming removes the row from the tree</p></figcaption></figure>

### 6.5 Save persists the reordered and shortened slot

After Save, the draft holds exactly the tree you see: reordered rows, deleted ones gone. Refreshing the browser now would restore the same state (the draft is durable), but visitors to the site still see the last-published version until you Publish.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-a0d35f113a55407a2a8d961a2e5ba129b465b061%2Fcms_ug_p21_1.png?alt=media" alt="6.5 Save persists the reordered and shortened slot"><figcaption><p>6.5 Save persists the reordered and shortened slot</p></figcaption></figure>

## 7. Move a component into a container

Containers are components that hold other components inside them — sections, grids, columns. Moving a component into a container is how you nest structure without rebuilding it. Reordering (Alt+↑/↓) only moves within the current level; this chapter covers moving BETWEEN levels, using the "Move into…" dialog. The reverse (move back out) uses the same dialog with the parent slot as the target.

### 7.1 The row exposes a "Move into…" affordance on hover

Hovering a row in the tree reveals a small "corner-down" icon among its action icons — that is "Move into…". The icon only appears on hover (and on focus, for keyboard navigation) to keep the tree quiet at rest. Clicking it opens the Move into dialog, below.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-0996be73e99a96c4bb925ba11d2d891c216a9673%2Fcms_ug_p22_1.png?alt=media" alt="7.1 The row exposes a &#x22;Move into…&#x22; affordance on hover"><figcaption><p>7.1 The row exposes a "Move into…" affordance on hover</p></figcaption></figure>

### 7.2 The Move into dialog lists every container that could hold this component

The dialog lists only containers that ACCEPT this component type — the storefront declares which children each container permits, and the dialog filters the list accordingly. The moving component's own container (if it has one) is excluded, since moving a container into itself would lose everything inside it. Each entry shows the container's type and how many children it currently holds.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-5d8b61ae2a41b90323c003643e02625bf626326c%2Fcms_ug_p22_2.png?alt=media" alt="7.2 The Move into dialog lists every container that could hold this component"><figcaption><p>7.2 The Move into dialog lists every container that could hold this component</p></figcaption></figure>

### 7.3 The move is persisted after save

The moved component now shows in the tree as a child of the chosen container — indented below it, with the same drag handle and action icons the top-level rows have. The preview reflects the new nesting (the container renders its children in its own layout). To move the component back out, open Move into… again and pick the parent slot as the target.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-6dc8b3f8e6a8d804637401746335ee81cd3a6501%2Fcms_ug_p23_1.png?alt=media" alt="7.3 The move is persisted after save"><figcaption><p>7.3 The move is persisted after save</p></figcaption></figure>

## 8. Add a custom slot to a page

A page's layout decides where components can live, but sometimes one page needs an extra zone the shared layout should not carry — a promo strip on the landing page and nowhere else. Custom slots are that escape hatch: page-scoped drop zones managed from the editor, stored on the page as `custom_slots`. This chapter opens the slot manager, adds a slot, saves the page, and confirms the draft now carries it.

### 8.1 The custom-slots manager opens from the Actions menu

The manager lists this page's custom slots, interleaved with the layout's own chrome slots shown as locked anchors — a custom slot can be positioned between them but can never reuse a reserved id. A fresh page has no custom slots yet, so the list is just the anchors and an "Add" affordance.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-e645b996994188d37775deca9f695c0daa6d5967%2Fcms_ug_p24_1.png?alt=media" alt="8.1 The custom-slots manager opens from the Actions menu"><figcaption><p>8.1 The custom-slots manager opens from the Actions menu</p></figcaption></figure>

### 8.2 Name the slot and confirm — it joins the list

Each slot needs a machine id (lower-case, used in the stored `custom_slots`) and a display name. Saving the slot only updates the manager's working list — nothing has touched the page yet. The manager's own Save is what hands the slots back to the editor, and even then they are held in memory until the page is saved.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-6f3c9a7152e5406002f4ff5907c3af9b260ccaf7%2Fcms_ug_p25_1.png?alt=media" alt="8.2 Name the slot and confirm — it joins the list"><figcaption><p>8.2 Name the slot and confirm — it joins the list</p></figcaption></figure>

## 9. Preview at different viewports

The editor previews content in a real iframe against a real storefront. The three viewport buttons in the header (desktop, tablet, mobile) resize that iframe so an author can check responsive breakpoints without opening the storefront in a separate window. This chapter walks the toggles and where the domain switcher would appear for a multi-domain tenant.

### 9.1 Desktop is the default viewport

The three viewport buttons sit at the left of the header, above the preview. Desktop shows the iframe at its natural width; tablet and mobile constrain it to \~768px and \~393px respectively. The active mode is marked with a white pill background.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-585069601cbe96fd1b31f3fd5846a9182fe83317%2Fcms_ug_p26_1.png?alt=media" alt="9.1 Desktop is the default viewport"><figcaption><p>9.1 Desktop is the default viewport</p></figcaption></figure>

### 9.2 Tablet narrows the iframe

Same page, narrower frame. The storefront's own responsive CSS decides what changes at each width — most storefronts collapse navigation into a hamburger, stack columns, and shrink type. Nothing about the CMS changes; the iframe just gets a new width.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-ce7a309bb32c4d5ffca4c30391d2c17b76179b58%2Fcms_ug_p26_2.png?alt=media" alt="9.2 Tablet narrows the iframe"><figcaption><p>9.2 Tablet narrows the iframe</p></figcaption></figure>

### 9.3 Mobile narrows it further

The phone viewport is where most authoring surprises appear — a long headline that wrapped fine on desktop can push content off the screen, an image can crop wrongly, a CTA can go below the fold. Switch here often during a real edit.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-44556b7ba94a0c19a640302d058b4e75c4e0ce6a%2Fcms_ug_p27_1.png?alt=media" alt="9.3 Mobile narrows it further"><figcaption><p>9.3 Mobile narrows it further</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/editing-and-arranging-content.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.
