Localization in WyzeHub: keeping language across the full journey
How we work so players and clubs can navigate in Spanish, English or French without losing context.
Language is part of trust
When someone changes the language of a product, they expect that choice to stay. If the next screen suddenly goes back to another language, the experience feels unfinished.
For WyzeHub, localization is especially important because the same journey crosses public pages, private areas, payment flows and club dashboards.
What needs to stay consistent
A localized booking flow must preserve:
- Navigation labels.
- Public club pages.
- Booking and payment screens.
- Private booking details.
- Notifications and action messages.
- Legal and contact pages.
Routes and preference
Some pages use /en or /fr prefixes. Other private or special pages keep the language through __locale and the saved wyze-locale preference.
This lets the user move between translated and non-prefixed routes without falling back to Spanish by default.
Continuous improvement
Localization is not just translating visible text once. It also means checking new flows, error messages, empty states and admin-created content such as news and blog posts.