Core concepts
The handful of ideas everything else in transglot is built on.
Read these once and the rest of the docs will make sense. Each page explains one idea and links to the guides that put it to work.
How your work is organised
Workspaces and projects
Accounts pay, workspaces hold your team, projects hold your strings.
Keys and strings
Keys, descriptions, plural forms and placeholders.
Languages and locales
One source language, any number of targets, named with BCP-47 tags.
How translation works
AI translation
What Glossa reads, what it keeps intact and what it never overwrites.
Translation states
Draft, edited, approved and needs checking, and what moves a translation between them.
Translation memory
Free reuse of exact matches, and suggestions from similar approved translations.
How quality is kept
Glossary and brand voice
Your terminology and your tone, applied to every translation.
Quality checks
Automatic checks, the 0-100 quality score and self-heal.
How usage is measured
For the vocabulary in one place, see the Glossary of terms.
Do I need a developer to set transglot up?
Only if you want strings to flow from your codebase. Uploading files, migrating from another tool and connecting a content platform need no code.
Workspaces and projects
How an account holds your plan and billing, a workspace holds your team and projects, and a project holds your strings.