Strapi i18n with three locales, do I author every Croct variant three times?
We run tr, en, and de from Strapi i18n and are adding Croct experiences on the homepage hero. Two questions:
-
How do variants relate to locales? If I create an experience with a variant hero, does that variant exist once or per locale? I do not want the german audience seeing a turkish variant.
-
We already resolve the locale once per request in our app. Can the locale default globally on the Croct side instead of being passed on every single fetch call? passing it everywhere feels error prone
1 answer
Taking your questions in order:
-
Your Strapi entries per locale keep serving as the default content, exactly as they do today. Experiences override the default only for matched audiences, and localization with per-locale default content on the Croct side is available as an add-on. In practice, most teams scope each experience's audience to a locale (or author locale-specific variants) so a German visitor never receives Turkish copy.
-
Yes. Every fetch method accepts a preferredLocale option (fetch, useContent, and fetchContent all take it), but you do not need to pass it per call: set defaultPreferredLocale once in the plug options and it applies globally. You can still override it on an individual fetch when needed.
There is a related thread that goes deeper on the locale option specifically: Strapi i18n and preferredLocale.