> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/multi-language-and-text-tagging-support/translate-content-at-the-node-level.md).

# Translate Content at the Node Level

As you create nodes with user-facing content the system assigns translation keys to each word or phrase. These translation keys are the link between a word or phrase and the translated version of that word or phrase. The system lets you add add translations to these translation keys both at the node level and at the project level, although LogicNets recommends managing translations at the project level.

In the example in *Create a Logicnet with MLS*, the you add a radio button list to Node 10 and the system tracks the words or phrases on that node that can be translated. It displays them on the *Translations* tab of the node.

1. To see the *Translations* tab, double-click the radio-button option.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-d8dffede3a3e72733b46eca3c2a7004412ebdc47%2F3bb4216a-f891-4782-a623-82b1c73fabf9.png?alt=media)

   The node-level *Translations* tab displays the items on that node that can be translated, and it displays columns for the languages identified at the project level. It also displays any existing translations. The system does not display the translation key, as it is something you do not need to remember and cannot change.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-c540bf0ae6cfec0cdaa4a45178973f65e53ae168%2Fbf0c210c-6c37-4a8f-823b-4a611583f8b5.png?alt=media)
2. To add translations at the node level click the ***edit*** button at the end of the row to be translated. Enter the required translations and click ***save***. Continue this process for each word or phrase identified on the node.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-61acf2d602ab080425edca6b3cda4c211bca431e%2F366d4fc0-2faa-4297-9f32-b34c0d12782b.png?alt=media)
3. Click ***save*** at the top of the tab to save the updates.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-32362a49b5984a4fcadd4b3caf5c4f15c92e5382%2F24f0075f-9b5c-4128-8bc0-75d3ae5c1ab6.png?alt=media)


---

# 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://community-test.logicnets.com/release-9/platform-documentation/multi-language-and-text-tagging-support/translate-content-at-the-node-level.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.