Changing language
The π switcher in the header β what it does on each surface.
Every Nura24 page has a π language switcher in the header. What it does depends on which surface you're on.
Marketing site (nura24.com, es.nura24.com, ro.nura24.com, β¦)
The switcher renders as anchor links to the equivalent URL on the alt-locale subdomain. Clicking "RomΓ’nΔ" on nura24.com/pricing jumps to ro.nura24.com/pricing.
This means:
- The URL itself encodes the language β good for SEO, good for sharing, good for crawler hints (we emit
<link rel="alternate" hreflang>per locale). - The visitor's session / cookie isn't involved on the marketing site. Their bookmark of
ro.nura24.com/blog/welcomealways serves Romanian regardless of cookie state.
Currently active subdomains: nura24.com (English), es.nura24.com (Spanish), pt-br.nura24.com (Portuguese / Brazil), fr.nura24.com (French), de.nura24.com (German), it.nura24.com (Italian), ro.nura24.com (Romanian).
Agent dashboard (<tenant>.nura24.com/admin)
The switcher is a POST form that sets your session's locale preference. The change applies to the next page load and persists for the cookie's lifetime (currently a year).
The change is per-user, not per-workspace β switching to Romanian in workspace A means workspace B's dashboard is also in Romanian until you switch back.
Customer-facing portal (acme.nura24.com)
Same as the agent dashboard β session-based switching. A customer browsing your help center can pick their language; their choice persists per browser.
The portal's default-language fallback is the workspace's default locale. If the workspace is set to English and the customer hasn't chosen a language, they see English content. KB translations into the customer's chosen language surface where available, falling back to English per field.
Chat widget
The widget on visitor sites picks up the page's locale from the <html lang="..."> attribute when present. Falls back to English otherwise. There's no UI switcher inside the widget itself.
Supported locales
Set in config('nura.locales') at the platform level. Adding a new locale is a config edit plus a lang/<code>.json translation file β we'll add new ones as we get translations.
What changes when you switch
- UI text (buttons, labels, dates).
- Email content (magic links, soon: notifications).
- Validation error messages.
What does NOT change:
- Customer-authored content (chats, tickets, contact submissions β they're in the language the customer wrote them in).
- Workspace branding (name, logo β those are workspace-owner choices, not localized).