> 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/site-layout.md).

# The site layout: header and footer from the CMS

With NEXT\_CMS\_PROVIDER=contenter, the CMS supplies the site's whole layout: header, navigation, footer, everything around the page.

With `NEXT_CMS_PROVIDER=contenter`, the CMS supplies the site's **whole layout**: header, navigation, footer, everything around the page. The storefront renders none of its own header and footer. Editors change them in the CMS like any other content, and the change goes out with a publish.

There is no per-page fallback. The CMS either provides the layout or it does not; with Contenter it does.

## Which layout, where

Every page of the storefront sits in a CMS layout — CMS pages, but also `/cart`, `/product/…` and the account pages:

| Storefront area                                     | CMS layout | Set with                |
| --------------------------------------------------- | ---------- | ----------------------- |
| The shop: home, CMS pages, catalogue, cart, account | `default`  | `CMS_DEFAULT_LAYOUT_ID` |
| Checkout and order confirmation                     | `checkout` | `CMS_REDUCED_LAYOUT_ID` |

The checkout gets its own layout so it can stay quiet: a logo and a way back, without the shop navigation that pulls a buyer out of the checkout.

## Authoring a layout

In the CMS, open the **Layouts** tab of the dashboard and create (or open) the layout with the id above.

* A layout declares **slots**: the page's place (`main`) and the slots around it. The storefront renders them in the order the layout declares them, with the page where the layout puts `main` — so a `top` slot above it holds the header, a `footer` or `bottom` slot below it the footer. Slot names are yours to choose.
* Put the **header and footer components** into those slots. They are components like any other, so they come with fields an editor fills in: logo, navigation links, a call-to-action button, the footer's link columns, the legal links.
* **Publish** the layout. Every page using it shows the change.

The plugin's library has no header or footer of its own: what a header contains is the storefront's business. Your storefront provides them as components of its own ([chapter 6](https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/developer-guide/your-own-components.md)) and builds them on the storefront's own parts — the cart button, account button, search, and the site, language and currency switchers — so they behave exactly like the rest of the shop. Medienwerft's showcase storefront does this with `cms-top-bar`, `cms-header` and `cms-footer`.

## Before going live

☐ The `default` layout exists and has a published header and footer.

☐ The `checkout` layout exists and has a published header and footer.

☐ Both are published for every site and locale the storefront serves.

**A tenant without them shows its pages without a header.** The CMS is responsible for the chrome, so an unauthored layout is visible on every page — check it on a staging tenant before switching a live storefront to Contenter.

## What it costs

The layout is read on every page, including the shop's own: cms-api becomes a request-time dependency of `/cart`, `/product/…` and `/account/…`. Reads are cached, and a publish refreshes the cache ([chapter 8](https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/developer-guide/publishing-caching-and-webhooks.md)), so in normal operation this is one cached read per page.

## In the editor

The editor's preview shows a page inside its layout, so authors see the header and footer while they work. Editing the layout itself happens on the Layouts tab.

Next: [Your own components](https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/developer-guide/your-own-components.md).


---

# 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/site-layout.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.
