Localization and multilingual fields

Editions: Free Cloud · Pro

Apito can store locale-scoped values on fields configured for multilingual content. Enable locales in project settings, then mark fields as localizable in the model designer.

Workflow

1. Define supported locales (e.g. en, bn).
2. Mark title/body-style fields as multilingual.
3. Publish schema.
4. Write content per locale in Console or via SDK mutations.
5. Query with the locale your app needs (header or variable — follow Engine behavior for your version).

SDK notes

Admin SDKs pass through locale-aware inputs once fields exist on the published schema. Regenerate typed documents after enabling localization on a model.

Limits

• Localization is a content concern — it does not replace i18n in your frontend UI chrome.
• Blueprint packs may ship single-locale seeds; extend locales after publish.

Next

• Database design
• API Explorer