Internationalization (i18n)
LaunchKit Pro includes an i18n foundation on the Next.js App Router frontend. v1 ships with English and French only; additional locales can be added through dictionary files in a future customization pass.
Supported locales (v1)
| Locale | Code | Status |
|---|---|---|
| English | en | Default |
| French | fr | Included |
Backend profile fields (locale on user profile) align with the frontend preference when saved from settings.
Where language appears
| Area | Behavior |
|---|---|
| Home / marketing page | Demonstrates the translation foundation — sample strings switch between English and French |
| Dashboard profile & settings | User locale preference control (profile/settings) persists for the signed-in user |
| Admin & dashboard shell | Primary UI copy is English in v1; locale preference is stored for future expansion |
The home page language switcher validates the i18n pipeline. Full dashboard-wide translation is a foundation buyers can extend.
User locale preference
Users set locale from:
- Profile —
/dashboard/profile(locale field when exposed) - Settings —
/dashboard/settings(language / locale preference)
After saving, the frontend applies the selected locale through the i18n provider. Refresh the page if some cached strings do not update immediately.
Adding more locales (customization)
- Add a dictionary file under the frontend i18n config (e.g.
src/lib/i18n/dictionaries/<locale>.ts) - Register the locale in
src/lib/i18n/i18n.config.ts - Extend the language selector in settings/profile
- Translate marketing and dashboard strings incrementally
No backend API changes are required for additional UI locales in most cases — profile locale is already stored on the user record.
Related
- Customization — branding and product copy
- Environment Variables — frontend env (no locale secrets)
Buyer expectation
v1 focuses on English + French foundation. Marketplace demos can highlight the home page language switch; plan additional locales as part of your product roadmap.