Answers about i18n
Questions and answers from the Croct community about i18n.
Nuxt app with three locales, how does slot content follow the active locale?
Hi everyone! We run a travel site on Nuxt with pt/es/en routes handled by nuxt i18n. Adding Croct for hero personalization and I am trying to understand the…
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…
Personalizing Storyblok content that already has multiple locales
We run a retail site out of Singapore with en, zh, and ms locales in Storyblok. I am scoping personalization and my first assumption was that every variant…
Combining Sanity localized documents with personalized experiences
Our Sanity dataset has document translations for fr and en, and the frontend picks the document by locale. Now we want to personalize the homepage hero with…
Field-level vs folder-level translation in Storyblok when experiences enter the mix
We are deciding between Storyblok's two translation models before we add Croct experiences on top, and I want to compare them on that axis specifically.…
How do I pass the next-intl locale to fetchContent so slots come back localized?
Hi everyone! We run a travel marketplace with es, en and fr routes using next-intl. The slot content from fetchContent always comes back in default language,…
Strapi i18n plus Croct, how does locale selection work per slot?
We are a Singapore retailer serving en, zh, and ms locales from Strapi i18n. Our pages already resolve the right Strapi locale from the URL, so I expected the…
One Storyblok space per market, how should Croct workspaces map to that?
Hello, our company runs separate Storyblok spaces for the TR, DE, and UK markets, each with its own team. We are adding Croct and I want to plan the structure…
Sanity field-level i18n arrays and preferredLocale, who resolves the language?
We run a Norwegian public sector site where documents store translations as internationalized arrays per field, so a title is [{_key: "nb", value: "..."},…