docs: address review feedback on i18n available languages section

Signed-off-by: Eoin Shaughnessy <eoinsh@gmail.com>
This commit is contained in:
Eoin Shaughnessy
2026-04-05 23:56:19 +01:00
parent 6aed2dcab1
commit 8b997d07c4
@@ -295,7 +295,7 @@ const app = createApp({
### Declaring available languages
Installing translation extensions makes the translated messages available, but the language switcher in the Settings page only appears once you declare which languages your app supports. Configure this in your `app-config.yaml` using the `api:app/app-language` extension:
Installing translation extensions makes the translated messages available, but the language switcher in the Settings page only appears once you declare two or more supported languages. Configure this in your `app-config.yaml` using the `api:app/app-language` extension:
```yaml
app:
@@ -308,9 +308,9 @@ app:
defaultLanguage: en
```
The `availableLanguages` array controls which languages appear as options in the Settings page. The `defaultLanguage` sets the language used before the user makes a selection, and defaults to `en` if not specified.
The `availableLanguages` array controls which languages appear as options in the Settings page. The `defaultLanguage` sets the language used before the user makes a selection, and defaults to `en` if not specified. If you configure `availableLanguages`, the `defaultLanguage` must be one of those entries — if you omit `defaultLanguage`, make sure `en` is included in `availableLanguages`, otherwise the app can fail to start.
Go to the Settings page — you should see language switching buttons. Switch languages to verify your translations are loaded correctly.
Go to the Settings page — you should see a language select dropdown. Switch languages to verify your translations are loaded correctly.
### Using the CLI for full translation workflows