Release 2.1.6 is about one thing: FleekDash speaks your language. The shell, labels, and actions can follow your team’s locale instead of defaulting to English, using the same gettext model WordPress already expects from serious plugins.
We are launching with 13 primary locales and room to grow the catalog as quality and demand allow. The full list of shipped languages and locale codes is documented in release 2.2.2, this entry is the announcement; that entry is the reference sheet.
What's New
13 locales at launch: supported UI translations so agencies and publishers in non-English markets get wording that feels intentional, not improvised.
WordPress-standard i18n: strings follow .pot → .po → .mo flows, load_plugin_textdomain, and predictable language directories, same mechanics themes and plugins rely on.
Quality bar: copy is human-translated and reviewed, with AI-assisted QA to keep terminology consistent and catch awkward phrasing early.
Language from the user menu: open Language, pick a locale from the catalog, apply, FleekDash updates in place on the same route (for example #/dashboard) without a disruptive full reload.
Persisted locale: your choice sticks across sessions so teammates return in the same language context.
What's Improved
Predictable gaps: if a string is missing for the active locale, FleekDash falls back (typically English) so you see an occasional English phrase, not broken UI, until catalogs catch up.
