About Glossage

One vocabulary across your docs, your product, your support and every translation.

What we do

Terminology enforcement in the writing workflow. A living glossary of approved terms with definitions, forbidden alternatives and translations per language, enforced as inline suggestions in the writing tool, in pull requests for docs-as-code, and in the product's own interface strings. It detects drift across the whole estate, finds terms in use that are not in the glossary, and flags contradictions between the docs and the help centre. Translation memory is maintained alongside, so terminology decisions propagate rather than being re-litigated per language.

Who we built it for

• Documentation teams

  Docs teams at software and hardware companies with more than 300 pages of content.

• Support teams

  Teams whose help centre articles need to agree with the manual and the product interface.

• Localisation teams

  Teams publishing in more than one language, where every inconsistency multiplies at translation time and is paid for per word.

The problem

Large content estates drift.

The same feature is called three things across the docs, the product interface and the help centre, support articles contradict the manual, and every inconsistency multiplies across every language at translation time, where it costs real money per word.

Style guides exist as a document nobody consults.

Try it before anything else

The free terminology drift check runs in your browser with no account. Answer fifteen questions about how terms are chosen, enforced and translated, and see what to fix first. Open it.