> For the complete documentation index, see [llms.txt](https://thecontentforge.gitbook.io/thecontentforge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/languages.md). # Languages TheContentForge runs in eight languages. The app picks one automatically based on your browser, and you can change it any time from the language switcher. ### Supported languages | Code | Language | | ------- | ------------------- | | `en` | English | | `es` | Spanish | | `pt-BR` | Portuguese (Brazil) | | `fr` | French | | `de` | German | | `it` | Italian | | `nl` | Dutch | | `sq` | Albanian | English is the source of truth - when a translation is missing for a string, the app falls back to English automatically. ### What's translated * The public site (landing, FAQ, pricing, login pages) * Sign-in / sign-up flow including the **/org-setup** onboarding wizard (14 core + advanced steps) * The full sidebar and navigation chrome * Content Forge - page chrome, every generation mode (nine standard modes, the Web3 project mode, and fourteen meme/culture modes with their sub-modes), tones, goals, content-type dropdowns, and the result-card actions * Video Forge - chrome and all panels * Publish Panel and the multi-platform publish flow * All four Intelligence pages - Wallet, Token, DeFi, Execution - including their tabs, modals, charts, and alerts * Algorithm Watch, Patterns, Competitor Intelligence, Forge Says * Settings hub, Team Members, My Account * The Generation Queue widget ### English-only surfaces A small number of surfaces remain English-only by design: * **Terms of Service** and **Privacy Policy** - legal text. The English page shows a banner clarifying that the English version is canonical. * **Generated content** - Content Forge and Video Forge generate in whichever language you ask them to in the prompt or your Brand Voice description, not in your UI language. Brand Voice profiles can be written in any language. ### Where to change your language There are three places the switcher appears: * **Public navigation** - a globe icon in the top bar of the marketing site (landing, pricing, FAQ, Terms / Privacy, login pages) * **Settings hub** - an inline language dropdown for signed-in users * **Account menu** - same dropdown, accessible from your avatar menu Changing the language takes effect immediately - no refresh needed. ### How language is picked at first visit The app resolves your language using this order: 1. `?lang=en` (or another supported code) in the URL - a transient override; useful for sharing a link in a specific language 2. Your saved preference in the browser from the last time you picked one 3. Your browser's reported language (`navigator.language` / `navigator.languages`) 4. Fall back to English Regional variants map to the closest supported language - for example, `pt-PT` maps to `pt-BR`, and `en-GB` / `en-AU` map to `en`. The current language is also reflected on the `` attribute so screen readers and search engines see the right locale. ### Storage Your language preference is stored locally in your browser. It is not currently stored against your account - if you sign in on a different browser, that browser's detection runs from scratch. ### Tips * If you share a deep link with a teammate in a specific language, append `?lang=es` (or any supported code) to force the language for that visit * Brand Voice and example posts can be written in any language - the language switcher only affects the UI chrome, not generated content --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/languages.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.