Translate articles into other languages

1. Enable languages on your knowledge base

Before you can create a translation, the target language must be enabled on the knowledge base itself.

1. Go to Dashboard → Knowledge Base → [your KB] → Settings.
2. Under Other Languages, add the languages you want to support.
3. Save.

The primary language set when you created the knowledge base cannot be changed here — it is the fallback language shown when a translation does not exist.

2. Create a translation for an article

1. Open an existing article in your primary language.
2. Click the language selector or the Add translation button (the exact label depends on your dashboard version).
3. Choose the target language from the dropdown.
4. A new article editor opens, pre-filled with the original title and body as a starting point.

3. Translate the content

The translated article has its own Title, Description, and Body fields. Edit them freely — there is no live sync with the original. This means:

• You can adapt phrasing rather than translate word-for-word.
• If the original article is updated later, you will need to update the translation manually.

The rich-text editor is the same for all languages. Images, code blocks, and links work the same way.

4. Publish each translation independently

Each language version has its own Published toggle. You can publish the English version before the Hungarian version is finished, for example. Visitors who browse in a language with no published translation see the primary-language article instead.

Ratings and feedback are also tracked per language — a visitor who rates the Hungarian article does not affect the English article's score.

How visitors choose their language

On the public help-center portal, a language selector appears in the navigation when more than one language is published. In the widget Browse tab, Yaplet detects the visitor's browser language and shows the matching translation automatically, falling back to the primary language if no translation exists.