Our Improved Translation and Localization Feature

Written by Edward Hewitt in Announcement on March 13,2019

Lost in Translation

Sometimes we get to make big announcements that we think will revolutionize the CMS landscape and the way that you use our product…and other times we get to talk about small changes that will just make your life that little bit easier. This one is definitely the latter (but we do have big things planned for the near future, we promise).

We know that many of you use Prismic to produce content in different languages and for different regions. Translation and localization are an industry standard, but that doesn’t mean that we see them as features that we can't improve.

Localizing content is important even when it doesn’t involve a complete translation. Content becomes significantly more impactful when spelling, idioms, and information are adapted to the target audience.

Localization Made Easy

With this in mind, a lot of our community kept asking us if there was a way to improve their translation and localization workflows. Up until now, when localizing content you had to rebuild the whole structure of your document by hand, including groups and slices (yes, we know that we always talk about slices, but it's just that they're great).

For content producers, this meant that the challenge of localization wasn’t limited to simply translating or adapting the actual content, the process also involved the time-consuming task of recreating the structure.

We have come up with a simple solution to solve this problem. Content producers can now click on the ‘copy to another locale’ button and then choose whichever one of their pre-selected languages that they would like for their translation.

Localizing content is now as simple as just a couple of clicks (well, sort of…we can’t help you with the whole translation part. Should we?).

Users will now be able to choose whether they would like to just copy and recreate the structure of the content or to take all of the assets at once (including text, images, and slices).

Living on Feedback

We know that this will help content producers with one of the biggest pain points when it comes to translation and localization. Prismic users can now stop wasting time recreating the structure of content and instead focus on making sure that the content itself is just right. This may not seem revolutionary, but, when you need it, you will really appreciate it.

More importantly, this is an example of the great opportunity for improvement that can arise from listening to users. We see our use of feedback in our product roadmap as one of our distinguishing features and prefer to listen to what people want instead of telling them what they need - although that won't stop us from suggesting things from time to time.

Edward Hewitt

Content Strategist. If the devs have their way, Edward will one day be replaced by a Prismic feature.