> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/editing-demos/translations.md).

# Translations

* [How it works](#how-it-works)
* [Managing your language versions](#managing-your-language-versions)

{% hint style="info" %}
Available upon request for Premium Plan+ customers. Please contact your CSM to enable it.
{% endhint %}

One demo. Every language. No duplicate copies.

Add language versions to any demo — AI translates the guide content, you review it in context, and viewers switch languages themselves in the player.

{% @storylane/embed subdomain="app" linkValue="wnb64utjmn2t" url="<https://app.storylane.io/demo/wnb64utjmn2t>" %}

***

### **👉 How it works**

1. Open any demo and click **Languages** in the editor header
2. Click **Add language** and select a target language and AI voice
3. Review the AI-generated translation in context
4. Accept changes — the version is saved and the **Languages** badge updates in the header

Viewers see a language selector in the player. One link covers every market — no need to duplicate the demo or manage separate links per language.

***

### **👉 Managing your language versions**

Manage all versions from the **Languages** panel:

* **Preview** any language version before it goes live
* **Sync with source** to pull in the latest changes from the original demo
* **Set a default** language for the demo
* **Delete** a version you no longer need

***

If you need help or have any questions, feel free to contact us at <support@storylane.io>.


---

# 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://docs.storylane.io/editing-demos/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.