jahia-content-translate-content

You can enable new languages on a Jahia site and populate i18n properties across existing content nodes via GraphQL, using setPropertiesBatch and publish mutations to apply and activate translations automatically.

GraphQL manages Jahia i18n by updating the site node with enabled languages and executing setPropertiesBatch mutations to populate internationalized fields, ensuring translations are applied and published correctly.

Yes, you can audit Jahia content to identify nodes missing translations and extract their paths for remediation, ensuring you know exactly which internationalized fields require updates before applying bulk changes.

Yes, enabling site languages and updating the site node in Jahia requires GraphQL endpoints and language properties on the site to ensure data integrity when applying batch updates and publishing content.

Using the setPropertiesBatch GraphQL mutation is the best way to bulk update internationalized fields in Jahia, allowing you to handle mandatory i18n fields first and then publish translations across content nodes.

Handling mandatory i18n fields first when translating Jahia content ensures data integrity and prevents publishing errors, allowing setPropertiesBatch mutations to populate required properties before executing publish mutations.