iLangL Cloud 2020 May

Publish Items with Referenced Assets in Contentstack


As you know, Contentstack has items that are basically pages and assets, such as images or other file resources. To show the page properly with images, you would need to publish the page with all the related assets. If you publish a page that uses images that are not yet published, the end-user will see the page with empty images. Not great for user experience, right?   

Originally when we published the page through API, there was no option to publish referenced assets. The problem here was that clients had to manually check if all the related images were published.

One More Step Towards Automation


Contentstack team has recently updated the Content Management API and added a new method - Contentstack API ReferenceThe new method allows us to publish items with all the referenced assets automatically! The new version of iLangL Content Provider 20.05.28 consumes this method by default to publish items. With the new version, all the images will be published within the page automatically and clients won’t need to spend additional efforts to check the published page consistency. 

Contentstack connector update

To try out this new update, you just need to get in touch with us! 

Sitecore Connector Update: Performance Boost

A page in Sitecore usually contains a lot of related items that can be scattered in different places. To group related items for a certain page, developers usually create subfolders under the page item. When you need to send for translation only specific items of a page (not the entire page with all the related items), it’s very easy, as you can choose any items in a content tree.
For each of them, separate jobs are created in translation tools. In case you select more than one page, the connector will create many jobs for all pages which could be often confusing for linguists as they couldn’t see the page context. We’ve developed the new version of a Sitecore connector which is aimed to solve this issue. 

Related Items with Parent Page in One Job


Now, our Sitecore connector groups all the folders and related items with their parent pages and creates one job for a parent page and all the related items. 

  • Contextualized translation. Now, linguists are provided with the context, and could better perform the translation. 

  • Faster performance. The performance time of building the content tree is immensely faster, as related folders and items are hidden in the content tree. Instead of building a content tree with all the items, it builds it with only parent pages. 

However, all the related items are sent for translation with their parent pages. So there’s no need to worry that any item could be lost. 

Which Option Will Work for You?

The good news is that you can switch between the versions according to your needs. If you need to export only certain items, you should use the option “With child items” in the configuration setting. If you’d like to send several pages for translation, it would be easier to set “Default Configuration” to build a content tree with parent pages only.

The new version is free of charge! Get in touch with our team at to install the new version! 

Language Variants in Umbraco 8

As Umbraco released the new feature supported in Umbraco 8, it becomes possible that a content node exists in different languages. iLangL Cloud has already integrated with the new version. Do you want to try out the new integration? Get in touch with our team at right away!