--- title: "Translations with language-independent workflow" slug: "translations-with-language-independent-workflow" updated: 2025-09-04T13:59:39Z published: 2025-09-04T13:59:39Z canonical: "documentation.deltatre.com/translations-with-language-independent-workflow" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.deltatre.com/llms.txt > Use this file to discover all available pages before exploring further. # Translations with language-independent workflow In this article, we cover translating editorial entities through a language-independent editorial workflow. --- ## Overview As an editor, you have to craft and publish content in many languages. FORGE manages the publishing workflow of the following editorial entities regardless of the language: - Photos - Albums - Documents - Localized editorial selections - Custom editorial entities E.g., when you publish the English version of a photo — or any other type above — if its visibility is on, you publish its French version too. ## Visibility-based workflow The language-independent workflow is visibility-based. When selecting the *Publish* button in a story translation, the field *visibility* determines which translated editorial entity is published on the front-end. When you modify the field *visibility*, all the translations of the editorial entity revert to the *Reviewed* status. When you *publish* a single translation, all translations with *visibility* 'on' are published, and the translations with *visibility '*off' transition into or stay in the *Not Published* status. The example below outlines the stages of the translations of a photo. Here you can see some published translations with *visibility 'on'* and other unpublished translations with *visibility 'off'*: ![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/image(34).png?sv=2026-02-06&spr=https&st=2026-10-27T15%3A13%3A27Z&se=2026-10-27T16%3A13%3A27Z&sr=c&sp=r&sig=Jj%2BQxw%2BfEh6lRKDyTGheZso2eSUrbSYQBdZMl36KJyU%3D) ## How does the front-end look like? In the front-end, language-independent entities, like photos, can look different per language and even display or not based on language. For example, the image below shows photos representing the most representative sport for English, Spanish, and Arabic audiences. Each audience, corresponding to its language, consumes a different photo. ![localizedEntity.jpg](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/13958461481756.jpg?sv=2026-02-06&spr=https&st=2026-10-27T15%3A13%3A27Z&se=2026-10-27T16%3A13%3A27Z&sr=c&sp=r&sig=Jj%2BQxw%2BfEh6lRKDyTGheZso2eSUrbSYQBdZMl36KJyU%3D)