You can configure your Userorbit help center to work in multiple languages so visitors can browse your knowledge base in the language they prefer.
Your default language acts as the source of truth for structure and fallback content, while translated collections and translated articles power each localized version of the public help center.
How it works
First, choose the languages you want to support in your help center.
Then add translated versions of your collections and articles for each language. Userorbit keeps the collection structure aligned across languages, resolves the best matching language from the visitor's request headers, and lets visitors switch languages manually from the public help center header.
In a translated locale, visitors only see the collections and articles that have been translated for that language. They can switch back to the default language at any time to view the full help center.
The default-language admin view is the source of truth for your help center structure.
What languages are supported?
Userorbit currently supports 46 help center locales: Arabic, Bengali, Bosnian, Brazilian Portuguese, Bulgarian, Catalan, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, German (Formal), Greek, Hebrew, Hindi, Hungarian, Indonesian, Italian, Japanese, Korean, Latvian, Lithuanian, Malay, Mongolian, Norwegian, Persian, Polish, Portuguese, Romanian, Russian, Serbian, Simplified Chinese, Slovenian, Spanish, Swahili, Swedish, Thai, Traditional Chinese, Turkish, Ukrainian, Vietnamese, and Chinese.
Right-to-left layouts are supported automatically for Arabic, Persian, and Hebrew.
Add languages to your help center
- Open Help Center in the Userorbit admin.
- Use the language picker to add the languages you want to support.
- Keep your primary language as the default language for structure and fallback content.
When you add a new language, the public help center gets locale-specific routes such as /en and /de.
Translate collections in each language
Switch the admin view to the target language to translate collection names and descriptions. Userorbit preserves the default-language structure across locales, but untranslated collections stay hidden from that localized public experience until you add translated content.
In a translated admin view, untranslated collections are clearly flagged so you can fill in the missing localized content.
Translate articles into multiple languages
Next, create translated versions of your articles in the same language view. Article translations are managed separately from the default-language article, which gives you full control over the localized title, body content, and publishing timing.
Once a translation is published, it appears in the matching localized route and stays grouped with the original article.
A published article translation renders on its own locale-specific route.
Preview and verify your public help center
Use the built-in preview and the live portal to verify each locale before publishing widely. Check the default-language homepage, switch to the translated locale, and confirm that translated collections and articles render as expected.
Default-language homepage.
Localized homepage in German.
Tips
- Start with your highest-traffic collections and articles first.
- Keep your default language complete, because it acts as the fallback when a translation is missing.
- Review localized routes before publishing to confirm titles, navigation, and article grouping.