9 languages in the application UI, targeting 20 — language switching, translation management, and compliance
The Workbench application UI currently supports 9 languages. The platform targets full support for 20 languages. This documentation website is being progressively updated with pages in all 20.
| Code | Language | Native Name | App UI |
|---|---|---|---|
en | English | English | ✓ |
zh | Chinese | 中文 | ✓ |
th | Thai | ไทย | ✓ |
de | German | Deutsch | ✓ |
fr | French | Français | ✓ |
es | Spanish | Español | ✓ |
ja | Japanese | 日本語 | ✓ |
ru | Russian | Русский | ✓ |
nl | Dutch | Nederlands | ✓ |
| + 11 more languages planned — ar, fa, bn, pa, pt, it, ko, hi, tr, id, ur | |||
Users select their preferred language during registration or in their Profile settings. The login and registration screens have a globe icon for temporary language selection. Once logged in, the selected language is used throughout the Workbench.
A translation compliance audit was completed in v0.12.0: ~80 violations were identified and fixed across the frontend and backend codebase. The English base translation file was regenerated (1,723 frontend keys, 366 backend keys). An 8-language translation pass was completed using delta-mode import, with 129–341 new keys per language imported into the database.
The Workbench uses a YAML-based translation key system. Every user-facing string in the frontend (via useTranslate() and the TranslationKey pattern) and backend (via t()) is defined with a key. Translations are imported from YAML files into the database using a delta-mode process that only updates changed keys.