> 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/component-library.md).

# Component Library

The Component Library is where reusable components live.

## 20. The Component Library

The Component Library is where reusable components live. Instead of building the same callout on ten pages, an author builds it once here and places it on those pages by reference. Editing the library entry and republishing pushes the change out to every referencing page's next publish — a lightweight way to keep a site consistent.

### 20.1 Component Library is a dashboard tab

Component Library sits alongside Pages, Layouts, Themes, and Media. The layout mirrors Pages: a folder tree on the left, entries on the right, toolbar at the top with creation actions.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-3c02e77ba487f005fa315053819d731ce24360f2%2Fcms_ug_p53_1.png?alt=media" alt="20.1 Component Library is a dashboard tab"><figcaption><p>20.1 Component Library is a dashboard tab</p></figcaption></figure>

### 20.2 The New Component toolbar action is present

Creating a library component opens a dialog similar to New Page — a type picker, then the component's own property panel. Once saved and published, other pages can reference it via the Copy affordance on any slot, picking Link mode to reference-not-clone.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-81ba7decb87cc8b111a1016604e3117ece39f0d1%2Fcms_ug_p54_1.png?alt=media" alt="20.2 The New Component toolbar action is present"><figcaption><p>20.2 The New Component toolbar action is present</p></figcaption></figure>

## 21. Clone or link a library component

Reusing a Component Library entry on a page is a choice between two words. Clone takes an editable snapshot — a copy you own, that will not change when the source does. Link stores only a reference — the component shows the source's live content and stays read-only here, so editing the source updates every page that links it. This chapter links a component, shows the read-only banner that marks it, then converts the link to a clone and watches the content turn into ordinary editable fields.

### 21.1 Copy opens a dialog that asks where to copy from

Every component in a slot can be copied from somewhere else — another page's version of this slot, or a shared Component Library entry. The Copy dialog is where that starts: pick the source, pick what to copy, and decide whether the copy is a clone or a link. This chapter copies from the Component Library, the case where the clone-vs-link decision matters most.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-d2c3c315a017e6bf6ab9c0ce42e6599caddd2041%2Fcms_ug_p55_1.png?alt=media" alt="21.1 Copy opens a dialog that asks where to copy from"><figcaption><p>21.1 Copy opens a dialog that asks where to copy from</p></figcaption></figure>

### 21.2 Pick a library entry, then choose Link over Clone

Choosing Library lists the shared entries for this site; pick one and the Clone/Link choice appears. Clone takes an editable snapshot — a copy you can change freely, that will not follow the source afterwards. Link stores only a reference — the component shows the source's live content and is read-only here, so editing the source updates every page that links it. We pick Link.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-caae651783bddb9390df3b5d68a696607cfda8c8%2Fcms_ug_p56_1.png?alt=media" alt="21.2 Pick a library entry, then choose Link over Clone"><figcaption><p>21.2 Pick a library entry, then choose Link over Clone</p></figcaption></figure>

### 21.3 The linked component is added, and it is read-only

The linked component is now in the slot, marked with a link icon and — when selected — a purple "Linked component" banner. Its fields are read-only: there is nothing to edit here because the content lives in the source. Save persists the page, but what it stores is only a pointer, not the content; the delivery API resolves that pointer to the source's live content on every request (the ["Linked content updates everywhere at once"](#22-linked-content-updates-everywhere-at-once) chapter proves that half).

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-d3c63c2d80fd15b7f427889992a501be3e3c73ee%2Fcms_ug_p57_1.png?alt=media" alt="21.3 The linked component is added, and it is read-only"><figcaption><p>21.3 The linked component is added, and it is read-only</p></figcaption></figure>

### 21.4 Convert to clone materialises the content into editable fields

"Convert to clone" cuts the link: the editor fetches the source's current content, writes it into the component as ordinary editable props, and the banner is replaced by the normal property fields. From here the component is a plain copy — edit it freely and it will no longer follow the source. The conversion is reversible ("Convert to link" does the opposite), but converting to a clone is the moment a shared component becomes this page's own.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-f9656d786ce0e11ec018320cd9d6d5981204f542%2Fcms_ug_p58_1.png?alt=media" alt="21.4 Convert to clone materialises the content into editable fields"><figcaption><p>21.4 Convert to clone materialises the content into editable fields</p></figcaption></figure>

## 22. Linked content updates everywhere at once

A linked component is a live reference, not a copy: the page stores only a pointer to a Component Library entry, and the delivery API resolves that pointer to the entry's current published content on every request. So editing one library entry updates every page that links it — no page is re-published, yet all of them deliver the new content. This chapter links a page to a library entry, reads it back through delivery, then changes the entry and shows the same page now delivering the change.

### 22.1 Delivery returns concrete content, not a reference

The page was published carrying only a pointer to the library entry, yet the delivery API returns a fully concrete component — the storefront never sees a link, only content. The headline it carries is the library entry's, resolved at request time. This is what lets one library entry back many pages: each page stores a reference, delivery does the substitution.

### 22.2 The same page now delivers the new content — without being re-published

Only the library entry changed — the page was not opened, edited, or re-published. Because delivery resolves the link against the entry's current published version on every request, the page now delivers the new headline. Change the entry once and every page that links it follows; that is the difference between a link and a clone.


---

# 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/component-library.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.
