> For the complete documentation index, see [llms.txt](https://docs.opencollective.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opencollective.com/help/contributing/translation.md).
# Translation
Procedure and documentation about how to contribute to the Open Collective translations
{% hint style="info" %}
We use Crowdin to manage all our translations. You can join and contribute on:
{% endhint %}
Quick tour
{% embed url="" %}
## Adding a new language
To ask for a language to be added on Crowdin, feel free to [open a discussion](https://crowdin.com/project/opencollective/discussions). We always accept these requests, but please note that inactive languages will often be removed if there's no contribution.
## Format
### Variables
Words between brackets are variables that meant to be replaced by dynamic values.
For example the string:
```
Hello {collectiveName}!
```
Will render as **`Hello Webpack!`** if the collective name is Webpack. You must never change the variable names.
### Select
`select` is a special command that lets us render different texts conditionally. The base pattern is:
```
{myVariable, select, value1 {Rendered if myVariable=value1} other {Otherwise this}}
```
A classic example for that is the interval select:
```
{amount} {interval, select, month {monthly} year {yearly}}
```
Here `interval` is the variable with `month` and `year` as possible values. If amount is equal to `$5` and interval to `year`, the template above will be rendered to:
```
$5 yearly
```
Here again, don't change the variable name or the `select` keyword, only the replaced strings (`monthly` and `yearly` if we take the example above).
---
# 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.opencollective.com/help/contributing/translation.md?ask=&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.