> 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/translation-and-ai.md).

# Translation and AI

Every page belongs to one locale.

## 12. Translate a page into another locale

Every page belongs to one locale. To offer the same page in another language, an author copies its content to a target locale — with the option to auto-translate the fields via the AI translation agent. This chapter walks the Locales dialog; creating a de variant requires the site to advertise more than one locale.

### 12.1 Open the Locales dialog from the Actions menu

The dialog lists every locale this page already exists in (the current locale is marked). Below, the create section takes a target locale, two checkboxes (copy content, auto-translate), and a Create button. When the site has only one locale, the target dropdown is empty and Create is disabled — configuration for additional locales lives on the site itself.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-b86d993602fdd62a31aab9d279d2ce29ad175645%2Fcms_ug_p31_1.png?alt=media" alt="12.1 Open the Locales dialog from the Actions menu"><figcaption><p>12.1 Open the Locales dialog from the Actions menu</p></figcaption></figure>

## 13. Translate a field with AI

Every translatable text field carries a small Sparkles button that translates its content with one click, using the tenant's configured AI translation agent. This chapter walks the gesture on a page headline; the same button works for any text field a component declares.

### 13.1 Each translatable field carries a Sparkles button

The button appears next to every text field that has content and a target locale. Hovering it shows a tooltip naming the target locale so you know what "translate" is going to do — if you're editing an `en` page, it translates the field into the page's other configured locales one at a time.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-faa3906c1c3ab0c341c435052f2e8ea95e82fe44%2Fcms_ug_p10_1.png?alt=media" alt="13.1 Each translatable field carries a Sparkles button"><figcaption><p>13.1 Each translatable field carries a Sparkles button</p></figcaption></figure>

### 13.2 Click Sparkles — the field is replaced with the translated text

One click triggers a single call to the translation agent, which returns the target-language string and writes it back into the field. The old text is replaced (undo remains available); the change is not persisted until Save. Longer fields translate as fast as the underlying model; on Anthropic's Sonnet, a headline lands in about a second.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-b34a85d556da5816362a116df924926a344a2cbe%2Fcms_ug_p32_2.png?alt=media" alt="13.2 Click Sparkles — the field is replaced with the translated text"><figcaption><p>13.2 Click Sparkles — the field is replaced with the translated text</p></figcaption></figure>

## 14. Chat with the Content Assistant

The Content Assistant is a chat agent that can answer questions about the page you're editing — summarise it, list its components, suggest edits. It lives in a floating panel available on every editor screen. This chapter shows how to open the panel, ask a question, and understand the answer.

### 14.1 The Content Assistant lives in a floating launcher

A small bot icon appears in the bottom-right of every editor screen once your account has an AI provider configured and a Content Assistant assigned. Click it to open the chat panel. You can close the panel while the assistant works: a ring spins around the icon until it is done, then an "Agent finished — view reply" callout appears beside it (or "Agent run failed — view details" if something went wrong) and a red badge counts the replies you haven't seen. Click either to open the panel at the reply.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-c860899687e42bb87b49d1baf7b01a8f9475cbf7%2Fcms_ug_p33_1.png?alt=media" alt="14.1 The Content Assistant lives in a floating launcher"><figcaption><p>14.1 The Content Assistant lives in a floating launcher</p></figcaption></figure>

### 14.2 The panel opens as a docked dialog

The chat panel docks to the bottom-right — close enough to the launcher to feel like one thing, tall enough to hold a conversation. A blue banner shows which entity you're currently editing so the assistant's answers can refer to it. New conversations start from the "+" button below the input; the history dropdown lets you resume older ones.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-24cdec1009de7af35c76b54eeb566ad860ba4d1b%2Fcms_ug_p34_1.png?alt=media" alt="14.2 The panel opens as a docked dialog"><figcaption><p>14.2 The panel opens as a docked dialog</p></figcaption></figure>

### 14.3 Ask the assistant to summarise the page

Type your question and press Enter or click Send. The message appears as a blue bubble on the right (yours), and a status line on the left shows the assistant working. On a longer task that line says what it has just done — "Read a page", "Created a page draft" — so you can follow along. Multi-turn: keep asking and the assistant remembers what you said earlier in the same conversation.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-aa54bc2a12d1f41a0b744b03160b8f9d73b8953b%2Fcms_ug_p35_1.png?alt=media" alt="14.3 Ask the assistant to summarise the page"><figcaption><p>14.3 Ask the assistant to summarise the page</p></figcaption></figure>

### 14.4 The assistant answers

The answer arrives as a grey bubble on the left with the bot icon beside it. You can follow up in the same conversation — the assistant remembers the earlier turns. If you want a fresh context, hit the "+" below to start a new conversation; older ones remain in the history dropdown.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-9d5d5b6176ae256665efc87e1c14dfb928cbc414%2Fcms_ug_p36_1.png?alt=media" alt="14.4 The assistant answers"><figcaption><p>14.4 The assistant answers</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/translation-and-ai.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.
