> 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/media-and-page-metadata.md).

# Media and Page Metadata

The Media library is where every image, video, or file the CMS references lives.

## 10. Media library

The Media library is where every image, video, or file the CMS references lives. Assets are uploaded here once and picked from any component's media field on any page. This chapter walks the perspective's layout — folder tree, asset list, and the toolbar actions that manage them.

### 10.1 Media is a dashboard perspective alongside Pages and Layouts

The Media tab sits with the other perspectives. A folder tree runs down the left; the assets inside the selected folder appear on the right. The toolbar offers Upload, New Folder, and Search — the same actions the Pages perspective offers for pages.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-59b96910541bc5271740c0ec8a7d8af1739a440e%2Fcms_ug_p28_1.png?alt=media" alt="10.1 Media is a dashboard perspective alongside Pages and Layouts"><figcaption><p>10.1 Media is a dashboard perspective alongside Pages and Layouts</p></figcaption></figure>

## 11. Edit a page's metadata

Title, description, URL slug, parent folder, layout — everything about a page that isn't its components. This chapter walks opening the metadata dialog and changing the page's title, so an author knows where to reach for a rename without navigating away.

### 11.1 The metadata dialog shows the page's current values

The dialog is organised into three tabs, matching the New Page dialog: General (title, slug, description, locale, site), Routing (parent folder, custom URL, homepage flag), and Layout. The current values are populated. Changes save on Update.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-f0ec5cbbb54c2737d0ea2381a1674ae8b57cfab3%2Fcms_ug_p29_1.png?alt=media" alt="11.1 The metadata dialog shows the page&#x27;s current values"><figcaption><p>11.1 The metadata dialog shows the page's current values</p></figcaption></figure>

### 11.2 Change the title and Save — the header reflects it

Metadata edits land as a draft — same as a content edit — so a rename is not visible to visitors until you Publish. Renaming the slug or changing the parent folder changes the URL; the CMS handles the redirect from the old URL for a configurable period.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-f37f153285666776f3ef86926e0296e90a385271%2Fcms_ug_p30_1.png?alt=media" alt="11.2 Change the title and Save — the header reflects it"><figcaption><p>11.2 Change the title and Save — the header reflects it</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/media-and-page-metadata.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.
