Multilingual help center

Helpin's help center is multilingual: publish articles and navigation in multiple locales, let readers switch languages, and fall back gracefully when a translation isn't ready.

Enabling locales

Workspace admins configure the help center's default locale (English by default) and enabled locales. The language switcher can be shown or hidden, and fallback to default locale can be enabled so readers never hit a dead end.

What can be translated

Level	Translated fields
Space	Name, description, slug
Collection	Name, description, slug
Article	Title, slug, excerpt, full content, SEO/OG metadata

Translations live beside the source content with their own status:

• Draft — being worked on; not public.

• Published — live on the help center in that locale.

• Needs review — the source article changed after the translation was published; the translation is stale until reviewed.

Publishing translations

• Per-item publish/unpublish per locale — a German article can be live while the French one is still draft.

• Mark reviewed records that a human checked the translation.

• Auto-translate missing generates draft translations for every enabled locale in one pass, using your configured translation settings; protected terms (product names, brand words) are preserved.

• Fallback behavior — when a requested locale has no published translation and fallback is on, readers get the default locale's article (flagged as fallback), never a 404.

Authoring flow

1. Write the source article in the default locale; publish it.

2. Generate translations (per locale, or with Auto-translate missing).

3. Review/edit drafts in the translation dialog — titles, slugs, and content are all editable.

4. Publish per locale; after editing the source, watch for translations marked Needs review and refresh them.

SEO implications

Locale-published articles get their own URLs and hreflang-appropriate metadata; untranslated articles resolve to the fallback with canonical handling, avoiding duplicate-content issues.