> 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/developer-guide.md).

# Developer Guide

How to run the Contenter CMS on an Emporix Next.js storefront: editors build pages, layouts and themes in the Emporix Management Dashboard, preview every change on the storefront before they publish,

Running the Contenter CMS on an Emporix storefront: setup, the plugin, the site layout, your own components.

{% hint style="info" %}
Version 1.0.0 · Published 5 November 2026
{% endhint %}

## Introduction

How to run the Contenter CMS on an Emporix Next.js storefront: editors build pages, layouts and themes in the Emporix Management Dashboard, preview every change on the storefront before they publish, and the storefront renders what they publish.

On an Emporix storefront you do not build the integration yourself. The **Medienwerft CMS plugin** brings it: you install the plugin through the storefront's extension points, choose the CMS with one environment variable, and edit nothing under `src/`. The plugin uses the `@contenter/*` SDK underneath, so you only meet the SDK when you build components of your own.

**Start with** [How it fits together](https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/developer-guide/how-it-fits-together.md)**,** then set up the CMS in your tenant and install the plugin.

## Contents

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th align="center"></th><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><i class="fa-gear">:gear:</i></td><td align="center"><strong>Part A — Set up</strong></td><td align="center">Learn how the plugin fits in, set up the CMS in your tenant, install the plugin, and configure credentials and environment variables.</td><td><a href="https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/developer-guide/how-it-fits-together.md">How it fits together</a></td></tr><tr><td align="center"><i class="fa-hammer">:hammer:</i></td><td align="center"><strong>Part B — Build the site</strong></td><td align="center">Take the site layout, header and footer from the CMS, add components of your own, and make their fields editable inline.</td><td><a href="https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/developer-guide/site-layout.md">The site layout: header and footer from the CMS</a></td></tr><tr><td align="center"><i class="fa-rocket">:rocket:</i></td><td align="center"><strong>Part C — Run it</strong></td><td align="center">Refresh the cache when content is published, switch between Storyblok and Contenter, deploy, and troubleshoot.</td><td><a href="https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/developer-guide/publishing-caching-and-webhooks.md">Publishing, caching and webhooks</a></td></tr><tr><td align="center"><i class="fa-book">:book:</i></td><td align="center"><strong>Part D — Reference</strong></td><td align="center">See the plugin's layers, its component library, and how the storefront reaches it.</td><td><a href="https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/developer-guide/architecture.md">Architecture</a></td></tr></tbody></table>

## For a coding agent

`AGENT_INSTALL.md` is chapter 3 as an ordered checklist with the rules an agent must follow.


---

# 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/developer-guide.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.
