> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/configurator/embeds-and-translations.md).

# Embeds & translations

Learn how to embed the Mimeeq configurator on your website, platform, or custom storefront. Configure embed types to match your integration method, adjust template settings to control the layout and b

Embeds let you place the Mimeeq configurator on your website, platform, or custom storefront. Use embed templates to control the layout and behaviour of each embed, and translations to localise the interface text for your customers.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Embed Types</strong></td><td>Learn the different embed formats available and when to use each one.</td><td><a href="/configurator/embeds-and-translations/embed-types.md">Embed Types</a></td></tr><tr><td><strong>Embed Template Settings</strong></td><td>Configure the layout, behaviour, and appearance of your embed template.</td><td><a href="/configurator/embeds-and-translations/template-settings.md">Embed Template Settings</a></td></tr><tr><td><strong>Translations</strong></td><td>Manage and customise the interface text shown to customers in the configurator.</td><td><a href="/configurator/embeds-and-translations/translations.md">Translations</a></td></tr></tbody></table>


---

# 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://help.mimeeq.com/configurator/embeds-and-translations.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.