Structuring Content Independently in Translations

A solutions and services provider for the acquisition, management, integration, and dissemination of geospatial data contacted us. They provide consultancy, training, and specialist services to local, state, and national governments in defense, aeronautics, maritime, water resources, utilities, and transportation sectors. They specialize in developing and delivering geospatial solutions across all environments namely air, land, or marine changing the way geospatial data is collected, processed, and analyzed.


Geospatial data is information about a physical object that can be represented by numerical values in a geographic coordinate system. Active in the continents of North America, Asia Pacific, and Europe, the content of the site varies based on the region. The client wanted to revamp their website to make it responsive and also to build their brand awareness through the website.

The website was already built in Drupal 8 using paragraphs for the content structuring. Content translation is used as the solution to show different content based on the region. However, the issue comes when they need to add differently structured content to the translated page.




As the site is already built, changing it to a multi-domain was not a good solution for them as the cost would have been more. So we decided to go for a solution with the least disruption that could solve the issue.


The Entity reference revisions (paragraph) which are referred directly to a content type will not show add new paragraph item list in the translation edit page. But the Entity reference revisions field (paragraph) referred inside a paragraph type will show the add paragraph option in the translation edit page. So instead of directly giving the paragraph types to a content type it was added as nested one inside another paragraph type.

  • Added new paragraph.
  • In the new paragraph added add the paragraph types which are used to structure content in the content type.
  • Added the new paragraph type to the entity reference field in the content type.
  • Now the page and the translation page has an entirely different structure from the paragraphs.


The solution was implemented in just one day and the content manager has now the option to structure the translated page irrespective of the original page.