Translate articles and collections from a maintained default-language Help Center. Translation drafts are not public until reviewed and published.

Configure the language

Open the Help Center organizer and use its language controls to add the supported target language. Keep the default language as the source for the collection structure.

Language settings control whether that language is public while translation work is in progress. Review fallback behavior: the available fallback option uses the default-language article when a translated article is missing.

Translate collections

  1. Switch to the target language in the organizer.
  2. Find the corresponding default-language collection.
  3. Select Add [language] translation, or Edit [language] translation when it exists.
  4. Enter the translated name and description, then save.

Translate the corresponding collection before creating or organizing articles inside it.

Translate articles

Generate a translation draft or create the translated article content. Review the title, body, interface names, links and screenshots with a fluent editor before publishing.

Preserve code keys, API parameters and other literal product values unless the product itself uses a translated value. A translated instruction must still name the control customers see.

Check the public language

Open the public Help Center in the target language. Verify collection navigation, published article content, internal links and search. Test a missing translation to confirm the configured fallback behavior.

Make later hierarchy and ordering changes in the default-language organizer; translated placement follows matching translated collections and articles where they exist.

Was this helpful?