---
title: "Translations"
url: "/help/buuk/translations"
updated: "2026-11-13T18:45:43.258Z"
---
# Translations

Open **Settings → Languages** to enable locales. English is the source; the default row is marked **Default language** and cannot be switched off. Additional locales get translated titles and bodies per article, and section titles, changelog entries, and API reference descriptions can carry translations too. Owners and editors manage languages; everyone else reads the settings.

![Settings → Languages: reader languages with the default marked, and translation rules per language.](/api/media/assets/a7590b5c-0d18-4333-addd-f9e4396d1f7c)

## Enable a locale

The **Reader languages** list shows every available language with its flag. Flip a switch and press **Save**. At that moment Buuk queues article translations into the new languages — the confirmation tells you how many were queued, and each one appears on the help center when its job finishes.

When more than one language is enabled, the language menu appears on your public docs. No site rebuild, no duplicated section tree — the same URLs serve the reader’s chosen locale.

## Translation rules

Below the language list, each enabled language has a rules field (up to 2,000 characters). Use it for terminology, brand names, and tone that applies when AI translates into that language — for example, keep “workspace” untranslated, or use formal tone in German.

Workspace-wide naming rules belong on the same style guide: **Settings → General** has voice rules and a **Terminology glossary** where you specify terms to prefer and the words to replace — up to 200 entries. Both the glossary and the per-language rules feed every generated translation.

## Per-article translations

In the article editor, the translations panel lists your enabled languages. Enable one to make the article available in that language, edit its title and body inline to fix or rewrite what AI produced, and save. A saved translation goes live on the help center immediately; disable a language and readers see the default language again.

> [!TIP]
> Translate your highest-traffic articles first — Introduction, Quickstart, and the pages missed searches keep hitting. A glossary entry for product names saves you from fixing every page later.

## How readers see it

Readers pick a language in the header. Until a translation exists for a page, they see the default language — empty fields never render as blank pages. Search and Ask AI respect the choice too: the reader’s locale is served in retrievals.

## Worked example

A team enables French on Monday. Buuk queues their 40 published articles, and translations land over the following hour. The team opens the ten most-visited pages in the translations panel, fixes the product vocabulary with the glossary, and saves. French readers get the language menu in the header the same day, and the underlying URL structure never changes.

> [!NOTE]
> Always read a generated translation before you rely on it. A saved translation is live on the help center the moment you press save.

## Troubleshooting

**The language menu is not showing on the public site**

It appears once more than one language is enabled and published translations exist. Enable a second locale, let the queued jobs finish, and check again.

**A page still shows English in a new locale**

The translation may still be queued — newly enabled languages process article by article. If it has finished, check that the per-article switch for that language is still enabled.

**Machine output reads wrong for our product**

Add the product’s vocabulary to the terminology glossary and the per-language rules, then edit the affected pages inline in the translations panel. Saved edits are what readers get.

/

## Related

- Where translations appear once live: [Publish your help center](./publish-your-help-center).
- Authoring the source pages: [Write and publish an article](./write-and-publish-an-article).
- Naming rules used by translation: [Editor overview](./editor-overview).
- Translations are included in exports: [Export your docs](./export-your-docs).