Cleaner UI for creating translatable documents as the translation is managed across multiple fields.
Intl plugin for Sanity
sanity-plugin-intl-input will soon be deprecated in favour of an updated version, officially released by Sanity. This is for future compatibility with Sanity Studio and to ensure dedicated maintenance of the plugin. We anticipate no breaking changes to document-level features, however the new official plugin will not support field-level internationalisation.
Field-level internationalisation is best done using the guidance in the official Documentation, combined with the @sanity/language-filter plugin to improve the UI. This method is different from the existing implementation and will require you to update your configuration and schema. You can find a migration guide in the documentation.
If you have any questions please ask them in the Sanity Slack community.
When you want to create translations in Sanity they suggest following approach.
This definitely works, but makes the UI very clunky as you get more fields that require translations.
With the intl plugin you will get a cleaner UI for creating translatable documents as the translation is managed across multiple fields and it is even possible to manage document wide translations.
| Simple translated object field | Document wide translation | |-|-| |||
Please make sure to read the information about ID structures before setting up your project. It is an important decision that should be made consciously. You can find out more about it here
- V4 to V5 migration guide
- Installation Instructions
- General Configuration
- How to use
- Translation Maintenance
- GraphQL support
- Advanced languages
- Usage with custom publish action
- GROQ Cheatsheet