> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/doc/en/advanced-features/translation-template/create-translation-template.md).

# Create a translation template

A Translation document template is used to translate a main document.

## What is a Translation template used for?

A Translation document template is used to translate a main document.

This type of document is used when you need a document template in several languages. The user can then choose from several language options.

## Create the Translation document template

* First, create and configure the main document template
* In the Doc tab of the main document template, click "New Translation" in the "Translation" component
* Give the template a name
* Choose the desired language
* Enter a prefix and a suffix for the name of the file that will be generated in this language
* Save to be redirected to the created document template
* Then upload the translated document and check that all indicators are green
* You can then see all the translation templates of the main template

![Creating a translation template (animation)](https://content.gitbook.com/content/U1Chwyf7Cc7FN9BiEh0V/blobs/m3KzfzuBnOdLI9M0kBv4/36-01-creer-modele-traduction.gif)

## Generating the translation template

* The document template that appears in the generation component is the one that matches the user's language.

{% hint style="success" %}
**Example**

If the user's Salesforce language is English, the English translation template will be generated
{% endhint %}

* If you want to let users choose the generation language, check the "Allow user to change language" box in the "Language & Translation" section of the main template configuration
* Your users can then choose the language in the generation component

![Allowing language changes and choosing in the component](https://content.gitbook.com/content/U1Chwyf7Cc7FN9BiEh0V/blobs/qZaTFFpenpcDtE7yTUYo/37-02-autoriser-modif-langue.gif)

{% hint style="danger" %}
**Warning**

Language management only controls the standard generation component. If generation is done through a flow, you must handle retrieving the desired templates in the flow
{% endhint %}


---

# 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://university.gonexa.fr/doc/en/advanced-features/translation-template/create-translation-template.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.