Translations
Translate articles and categories into your other configured languages.
Your default-language content (English, unless your workspace overrides it) lives on the article and category rows themselves. Translations are stored in companion tables and only kick in when the visitor is browsing in that language.
How visitors see translations
A visitor on the Romanian portal subdomain (acme.ro.nura24.com or wherever you've configured RO) sees:
- Translated category name and description if a translation exists for their locale, otherwise the English original.
- Translated article title, meta description, and body under the same fallback rule.
The fallback is per-field, not per-article: if you've translated the title but not the body yet, the visitor sees a Romanian title with the English body. Not ideal but better than blocking publication.
Translating an article
Open the article in the editor. Below the main form, the Translations panel lists each non-default language as a collapsible section. Each section has:
- Title — translated title
- Meta description — translated meta_description
- Body (HTML) — translated body. The editor here is a plain textarea today (HTML or Markdown-ish input). Same Purifier sanitization applies on save.
Saving submits ONLY that language's translation. Leaving every field blank deletes the translation row — useful if you want to "untranslate" without manually clearing each field.
Translating a category
The KB → Categories → Edit page has a similar Translations panel for category name and description.
Slugs are NOT translated
The category and article URL slugs stay the same across languages — acme.nura24.com/help/billing/refunds and acme.ro.nura24.com/help/billing/refunds. This is a trade-off: you keep one canonical URL per article (good for cross-locale links), but the slug stays English (less SEO-perfect than per-locale slugs).
If you need per-locale slugs, contact us — it's planned for a future release.
Translation tips
- Translate the most-read articles first. Run voting and analytics to find them.
- Don't translate every article right away. Half-translated KBs feel worse than English-only. Translate a batch, ship them, translate the next batch.
- The body field accepts HTML. Easiest workflow is: write in your usual editor (the main English fields), translate, paste the translated body in. Or write directly in Markdown — the on-save sanitizer is lenient about minor input variations.