Localization
A project can manage content in more than one locale. Once additional locales are configured, an entry can have a distinct variant per locale, and the AI translation tools can generate one locale's content from another's.
How locale-aware requests resolve
- No
localeparameter - matches rows tagged with the project's default locale, plus any untagged (legacy) rows. - An explicit
localeparameter - matches that locale exactly, with no fallback, except when combined with a single-entry (first-style) lookup, which retries once against the default locale if the requested locale has no row.
Existing content isn't tagged retroactively
Content created before localization is turned on has no locale tag. It keeps matching default-locale requests (since untagged rows are included there) but is invisible to a request for any other specific locale.