A Knowledge Base's language model is determined by its subcommunity. The language option the subcommunity belongs to—such as Static Language or AI Languages—determines how its Knowledge Bases handle languages.
For a source KB in a static-language subcommunity, that language provides its source/base locale. For example, a source KB in an English static-language subcommunity uses English as its base language.
Add other language versions
For hand-written or legacy Google Translate/DeepL translations, create or use a subcommunity under each target Static Language. Select Add Translation on the source KB, then select the target language and its subcommunity.
Each version belongs inside its language's subcommunity. You cannot place a KB directly under a language branch. Product Integration is no longer required.
See Translating Knowledge Base Articles for setup and article translation instructions.
Review language-structure changes
Adding a language version is different from changing the source KB's placement or moving content to AI Languages. Use Site Structure to review language and placement changes, including their pending operations and any migration warnings, before applying the plan.
For AI availability and enablement, see AI Translations.