FleekDash 2.2.2 pairs 2.1.5’s multi-language launch with two practical follow-throughs: a clear catalog of what “13 languages” means in product terms, and translation tooling for operators who need to refine strings inside FleekDash instead of bouncing through external editors only.
What's New
Shipped locale catalog (13): each row is a supported UI locale in this wave, use it to plan rollouts, train admins, and match site language policy to actual coverage.
| Language | WordPress-style locale |
English (United States) | en_US (default) |
Bulgarian | bg_BG |
German | de_DE |
Spanish (Spain) | es_ES |
French (France) | fr_FR |
Italian (Italy) | it_IT |
Japanese | ja |
Korean | ko |
Norwegian Bokmål | nb_NO |
Portuguese (Brazil) | pt_BR |
Russian | ru_RU |
Turkish | tr_TR |
Chinese (Simplified, China) | zh_CN |
Locale editors from Settings: when your build exposes translation tooling, jump from Settings into locale editors to adjust .po-backed strings and keep catalogs aligned with your team’s phrasing, without leaving FleekDash for the whole loop.
Operator playbook stays in-product: same flows you teach clients, Language in the user menu for switching, Settings for deeper string work, documented beside localization so multilingual rollouts stay repeatable.
What's Improved
Easier alignment with existing WP workflows: familiar .po / .mo conventions mean translation updates can still slot into processes your team may already use, FleekDash is not asking for a bespoke format just for the UI shell.
