> For the complete documentation index, see [llms.txt](https://help.form.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.form.io/deploy/portal-base-project/portal-translations.md). # Portal Translations {% hint style="info" %} Translation and Localization of the Developer Portal Application is available with the [**Security & Compliance**](/dev/the-security-module.md) module. Please contact for more information. {% endhint %} ### Creating translations In order to provide translations to the Portal application, you can add the translations using the **Language Resource** in the **Form.io Portal Base Project**. This resource has the following structure: ![](https://4287632785-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKgNM52jrdfkHgHDfKCH9%2Fuploads%2FuutBB5htngfAeoXgSFde%2Ftranslate1.png?alt=media\&token=4fcc488d-67d1-4746-87b5-7cf6b75b2c34) Within this resource, we have the following fields: * A Text Field called **Language**, which represents the language name. * A Text Field called **Language code**, which is a shorthand alias for the language. * A Data Map component called **Translations**, that has 2 fields: Text field for keys and one for translations. A list of the keys can be found in the Translations JSON file, which is provided separately, where every chunk of text in the Portal Application is matched by a key with a meaningful name. By default, every key represents an English translation. {% hint style="info" %} Portal Translations are part of the Security Module. Please contact for more information to add this Module to your subscription and obtain the JSON file needed for Portal Translations. {% endhint %} You can create a new submission for each translation like the following screenshot, which illustrates a submission for Spanish language: ![](https://4287632785-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKgNM52jrdfkHgHDfKCH9%2Fuploads%2FVM3OVtKYLeTnqC28C6MZ%2Ftranslate2.png?alt=media\&token=9f8e7905-7b1e-432c-be66-6443fb274958) Once you've created a submission in the Language resource, a new "language" is created. This is what will be used to manage all of the translations so you can now input the rest of your language translations the same way until you have multiple to chose from. ### Dynamic language switch When you have multiple languages created, the **Language** switch dropdown appears in the navigation bar. Here you can select any language from the list of languages you have configured. The currently selected language is highlighted as shown below. ![](https://4287632785-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKgNM52jrdfkHgHDfKCH9%2Fuploads%2FtuNPpDmPz1DJGR1AAJtf%2Ftranslate3.png?alt=media\&token=1d765839-9f4a-4fe6-825a-617c586fd4d9) Selecting a new language will trigger a language change for all of the keys that were provided with translation in the submission for that particular language. --- # 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.form.io/deploy/portal-base-project/portal-translations.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.