1 published · 19 awaiting review

English is the only published language today.

Gummy UI has the routing, direction, and review foundations for the complete language roadmap. A locale is not linked, indexed, or described as available until AI-generated copy passes automated integrity checks, rendered QA and founder review.

Language status

LanguageBCP 47DirectionPublication
EnglishEnglishenltrPublished
FrançaisFrenchfrltrPending founder review and publication
EspañolSpanishesltrPending founder review and publication
PortuguêsPortugueseptltrPending founder review and publication
ItalianoItalianitltrPending founder review and publication
NederlandsDutchnlltrPending founder review and publication
Bahasa IndonesiaIndonesianidltrPending founder review and publication
DeutschGermandeltrPending founder review and publication
PolskiPolishplltrPending founder review and publication
TürkçeTurkishtrltrPending founder review and publication
Tiếng ViệtVietnameseviltrPending founder review and publication
日本語JapanesejaltrPending founder review and publication
简体中文Simplified Chinesezh-HansltrPending founder review and publication
한국어KoreankoltrPending founder review and publication
हिन्दीHindihiltrPending founder review and publication
РусскийRussianrultrPending founder review and publication
УкраїнськаUkrainianukltrPending founder review and publication
فارسیPersianfartlPending founder review and publication
עבריתHebrewhertlPending founder review and publication
العربيةArabicarrtlPending founder review and publication

What publication requires

  1. A complete source dictionary with stable message identifiers and no untranslated fallbacks.
  2. Recorded AI model/version provenance followed by founder review for terminology, tone, grammar, truncation, and culturally appropriate examples.
  3. Keyboard, zoom, responsive, dark-mode, and assistive-technology review of representative pages.
  4. Additional bidirectional and logical-layout review for Persian, Hebrew, and Arabic.
  5. Only then: route activation, switcher link, sitemap alternate, and public availability claim.

The repository workflow and release evidence requirements are documented in the localisation review guide.

How fail-closed language routing works

Draft dictionaries are review artefacts, not public locales. A pending language has no customer-facing route, switcher destination, search index entry, sitemap alternate, or availability claim. This prevents an incomplete draft from silently mixing with English or exposing untranslated navigation, legal, support, licence, pricing, and account language as though the experience were finished.

When a locale is approved, its route must use one complete versioned dictionary and the correct document language and direction. Dates, numbers, currencies, names, keyboard input, validation, transactional email, and externally hosted identity or payment surfaces also need review; translating page paragraphs alone is insufficient. If a release later loses integrity, routing should fall back to the canonical English page rather than publish a partial mixture.