🔮 Sanity Create is here. Writing is reinvented. Try now, no developer setup

Field-level translations not recommended for content using PortableText in Sanity.io

10 replies
Last updated: Jan 23, 2024
Hello! I am reading that the
field-level translations
is not recommended for content using
. Has anyone tried / knows why this is the case?Source:
Jan 23, 2024, 7:50 PM
That would be because it creates a massive number of attributes and will cause you issues as you generate content.
Jan 23, 2024, 7:55 PM
user M
, so would it then follow that if a majority of a project’s components include the need for Rich Text with Portable Text, document level translation is really the best/only way forward?
Jan 23, 2024, 8:00 PM
Correct. I’d only ever use field level translation if there were one or two fields needing translation. Document level is the way to go.
Jan 23, 2024, 8:01 PM
Always helpful to get it validated from the source, thanks so much
user M
Jan 23, 2024, 8:02 PM
You’re very welcome!
Jan 23, 2024, 8:02 PM
Hopefully a quick follow up — is there a way to provide documents for translation to a third party? I was reading about the Transifex plugin (my client uses TransPerfect so this won’t work).
Jan 23, 2024, 8:10 PM
Yes, but we don’t currently have a plugin for TransPerfect. You could take a look at the existing plugins and use them as guidance for building out your own, though.
Jan 23, 2024, 8:17 PM
Got it — so by plugin only, at the moment?
Jan 23, 2024, 8:17 PM
You could also create a document action or anything that sends the JSON of a document to whatever service you’re using. Your service would need to to be configured to write content back to your dataset as well.
Jan 23, 2024, 8:18 PM
Ahh right right. THANK YOU! Appreciate your time.
Jan 23, 2024, 8:18 PM

Sanity– build remarkable experiences at scale

Sanity is a modern headless CMS that treats content as data to power your digital business. Free to get started, and pay-as-you-go on all plans.

Was this answer helpful?