Your knowledge base in 41 languages, kept in sync

No. Hinto writes the article once in the project's main language and translates that article into every other language on the project. One recording covers all of them.

The model is told to mirror the source's tone and register, keep the same headings, lists and paragraph count, and translate idioms by meaning rather than word for word. Your translation rules for that language go with every run. Review a translation in the editor and fix any wording by hand, and that translation keeps your wording from then on.

Yes. Add a language to the project and every article that already has content is queued for translation into it. Nothing needs to be recorded again.

Each translation has its own slug, meta description and keywords. The published page lists its other languages as hreflang alternates with an x-default, and it is served at its own path, not as a copy of the English page.

Code blocks, inline code, URLs and image paths are left as they are, and so is the on-screen text recorded with each screenshot. Product names and industry terms follow the translation rules you set for each language.

Yes. Save a change to an article's title or content in the main language, and every translation that follows it is queued for re-translation, one job per language. A translation your team edited by hand is marked manual and left alone until you choose Re-translate all for that language.

Yes. Import each one as a Markdown file first, then add your languages. Every article with content is queued for translation into each language you add.