Unlock seamless workflows and faster delivery with our latest releases - Join the deep dive

Answers from the community about Localization

Some of the conversations between community members on questions, suggestions and tips for using Sanity. Join our Slack to be a part of it.

TopicCategoriesFeaturedRepliesLast Updated
How to filter a reference field in Sanity schema for localization.3Apr 17, 2024
Cloudflare DNS issue impacts Sanity.io users, resolved after investigation27Mar 29, 2024
Troubleshooting installation of @sanity/client dependency in Next.js3May 29, 2023
How to deal with archive pages of blog posts in Sanity12Mar 30, 2023
Clarifying NextJS SSG build with localisation and resolving %2F issue6Feb 27, 2023
Next.js Blog Starter - How to add a Localized `blockContent` in the `post.js` Schema10Aug 8, 2022
Sanity Desk - How to Change the Localization Version of the Document?6Jul 14, 2022
How to Translate Product Info on Shopify and Sanity?2Jun 29, 2022
Focal point not respected in NextJS + `@sanity/image-url` setup14Jan 3, 2022
How to add options to a custom type in Sanity.io and access them in the definition.4Jan 3, 2022
New error while deploying GraphQL in Sanity.io8Nov 12, 2021
Best approach for retrieving translations when running groq queries from the frontend9Oct 4, 2021
Error setting up sanity-plugin-seo-pane on Studio with Localization and next.js starter template9Sep 2, 2021
Creating Subdirectories for Translated Pages4May 31, 2021
Problems with locale fields Working with localization, and first tried the intl-plugin, but couldn't get it to work, so...5Jan 27, 2021
Issue with displaying correct title for a post in the studio when working with localization.5Jan 27, 2021
Validating groq queries with groq-js library.3Dec 9, 2020
i am currently trying to create a new dataset for each localized language , ie. spanish, russian. how can i get a studio...9Nov 17, 2020