Translating a site is often a rather large effort. Since modern LLM can both speak many languages and integrate advanced reasoning capabilities, they can be a big help in translating a site - possibly to the point that translating a site can amount to an automatic process where the editor only has to check the results and only occasionally make minor changes.
We integrated a translation workflow into Composum AI that can translate pages or entire sites quickly. However, since rolling out pages with the AEM live copy mechanism is much quicker and more convenient than the somewhat cumbersome process of updating a language copy, we seamlessly integrate into the rollout mechanism instead: just roll out your page and it's translated!
It is very promising: a test translating the WKND site from English into German took only about 10 minutes, and the translation showed little need for manual corrections. Translating into other languages like Spanish, Japanese, Chinese, Korean seem to work nicely as well, as far as we can judge by translating the text back with Deepl Translator .
It's quick and easy to try that on your own site - install it locally or on one of your test systems and check out the result! Please let us know what you think and how it works for you and contact us on any trouble!
Why translation with a large language model?
While being employable for providing quick and inexpensive machine translation, LLMs like ChatGPT offer advanced reasoning capabilities that can improve the quality of the translation:
- Unlike most existing machine translation solutions for AEM we collect all the texts of one page, experience fragment or content fragment and present them together in one translation request to an LLM (currently ChatGPT). Thus, it can take the context of the text into account and translate it accordingly.
- By default, the LLM is instructed to be close to the original text, preserving the original style, tone, sentiment, and formatting. But:
- Additional instructions can be given to influence the writing style, finetuning the translation to the desired audience, and even to give background information about the site and the translation, if needed. That can range from minor changes like influencing how formal to address the reader to try major modifications like simplifying the language for a younger audience.
Or course, the full power of the Composum AI can then be used to further improve the translated texts, if needed.
Why live copies instead of language copies
Our translation process differs from the translation process Adobe suggests by one important point: the translated site(s) are live copies of the primary language, not language copies. The reason for that is: while language copies nicely allow translating a site initially, they are more difficult to handle when you are updating the site. But live copies are just made for that: change a page and hit “rollout” and the changes are transferred. So our translation process integrates transparently into the rollout process: an additional rollout configuration translates all texts into the language configured for the rollout target during the rollout action.
Please notice that this somewhat changes the meaning of "inheritance" in the context of live copies: if a text is inherited, then it'll be the AI translated text of the blueprint. If the inheritance is cancelled, it's a manually changed translation.
More information and how to check it out
More information is available on the Composum AI documentation site. As a part of the open source Composum AI you can just try it for free. Please notice that the automatic translation is our newest feature, so there might be some extensions and changes, but it is likely to work for you as it is.
Please make sure to tell us how it works for you - we are happy to help you if you have any trouble or questions.
