Birkly separates two languages:
| Layer | What it controls | Where you set it |
|---|---|---|
| Admin UI language | Menus, buttons, onboarding, plugin admin shells | Account (and onboarding for the first user) |
| Public site language | Which localized content visitors see | Per-collection multilanguage fields, template ?lang= / visitor picker — not a single General setting |
There is no site-wide language dropdown under Settings → General. Use Account for admin UI language.
Beginner
- First login: Onboarding asks for admin UI language — this saves to your user profile.
- Later: Open Account → language → save → reload admin.
- Content: Collections can use multilanguage fields separately; that is not the same as admin UI catalogs. See Multilingual templating.
Advanced
- Admin strings:
lang/*.jsonin core and pluginlang/packs (P85 i18n). - Legacy
settings/site.jsonmay still contain alanguagekey for defaults; it is not exposed in General settings UI.