> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/knowledge-base/translations.md). # Translations Translate knowledge base articles, collections, and headers into your supported languages. Publish your knowledge base in multiple languages. Pylon can translate articles with AI and keep them up to date, or you can write translations yourself. ## Before you start Add the languages you want to support in **Settings > Workspace > Languages**. Every supported language is available to translate in every article. See [Languages & Localization](/pylon-docs/platform/languages-and-localization.md). * You can add up to 20 languages besides your default. Unlimited languages are available on the Enterprise plan. * AI translation (**Auto-translate**) is part of Pylon's AI Assistant features and is available on select plans. Contact your account team to learn more. Without it, you can still add and edit translations manually. ## Translate an article 1. Open the article and click **Translations** in the editor toolbar. The list shows each supported language and its status. 2. Choose a language. The translation opens side by side with the original. 3. Edit or review the translation, then publish it. Translation statuses: * **Not reviewed**: no translation has been created yet * **Unpublished**: a translation exists but hasn't been published * **Has changes**: the original has changed since this translation was published * **Published**: the translation is live ### Auto-translate Each translation has an **Auto-translate** switch in its header. When it's on, Pylon generates the translation with AI and the translation is read-only. To edit a translation by hand, turn **Auto-translate** off. Turning it back on replaces your manual edits with a fresh AI translation. ### Keep translations up to date When you change an article's title or content, its auto-translated versions are marked **Has changes**. They're regenerated from the latest original when you publish them. You can also choose **Regenerate translation** from the translation's **⋯** menu. Translations you edit by hand aren't updated automatically. Review them yourself when the original changes. ### Publish translations in bulk * To publish several languages of one article, use the article's **Publish** menu and select the languages. * To publish translations across the whole knowledge base, click **Publish translations** on the article list, choose the languages, and click **Publish**. ## Collections and header * **Collections**: a collection's **Name** and **Description** each have a field per supported language in the collection's **Settings**. Click the refresh icon next to a field to regenerate its translation. * **Header**: translate the knowledge base header text in **General** settings, under **Header**. [Synced blocks](/pylon-docs/knowledge-base/articles-and-collections/synced-blocks.md#translations) have their own translations. ## Glossary and do-not-translate terms On **Settings > Workspace > Languages**, the **Custom translations** tab lets you set how specific strings are translated in each language, or set **Translate** to False to keep a term untranslated (for example, product names). Pylon applies these when it translates articles, synced blocks, collection titles and descriptions, and the knowledge base header. ## What customers see * Visitors switch languages with the language picker (globe icon) in the knowledge base header. It appears once you support at least one additional language. * Translated pages have their own URLs, prefixed with the language code, for example `/fr/articles/1234567890-reset-your-password`. Your default language has no prefix. * Pages open in your default language unless the URL specifies another. The knowledge base doesn't detect the visitor's browser language. * Your [sitemap](/pylon-docs/knowledge-base/seo-and-ai-crawlers.md#sitemap) lists each translated version of a page so search engines can index it. ## API To read or update a specific translation through the API, pass `language` on the article endpoints. See the [Knowledge Base API reference](/pylon-docs/developer/api/api-reference/knowledge-base.md). --- # 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.usepylon.com/pylon-docs/knowledge-base/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.