Write your articles once, in your source language, then offer them in more languages.
Choose the languages
Open Customize on the Knowledge base page and go to Languages & review. Pick the languages readers can switch to. Your articles are written in the source language, which cannot be changed once an article has a translation.
Each language has its own stable address, such as /help/acme/l/de/reset-your-password. The source language keeps the plain address. A rollback or a retranslation never moves an address.
Translate an article
Open an article and look at Translations. For each language you can:
- Write it yourself. Save the title, summary and text. New text waits for your approval before readers see it.
- Translate with AI. Formspring prepares a draft using your glossary. It uses one AI credit on plans without AI included. The draft is never published by itself.
- Approve the translation when you are happy with it. Approving marks it as matching the article as it reads now.
The glossary
Add terms that must always be translated the same way, such as product names. The glossary is used every time you translate with AI.
Out-of-date translations
When you edit the source article, every translation is marked Out of date. Nothing is overwritten and nothing disappears: readers keep seeing the approved text, with a note that it may be out of date and a link to the latest version. Update the translation and approve it again.
If a person already approved a translation and you ask AI again, the AI version is kept as a proposal next to the approved text. You choose to accept or discard it.
What readers see
- A language selector in the header, in each language's own name.
- A page that has no approved translation yet is shown in the source language, with a clear notice, and points search engines to the source page.
- Search works in the language being read. An article that is not translated is found by its source text.
- Search engines get the correct language alternates for every translated page.
Agents and the API
Translations can be managed by coding agents and over the REST API: list_knowledge_article_translations, save_knowledge_translation, approve_knowledge_translation, translate_knowledge_article and resolve_knowledge_translation_draft.