Composum AI introduces a fresh approach to automatic translation in AEM using large language models (LLMs) like ChatGPT, to profit from their advanced reasoning and language capabilities. And with a twist: to minimize effort when updating sites, it seamlessly integrates translation into the rollout of live copies, instead of using the more laborious language copy mechanisms. How about trying it out on your own site?

Composum AI for AEM extends Adobe AEM by providing a Content Creation Dialog that is accessible via the toolbar of richtext editors as well es text areas in dialogs, and with a Side panel AI that is geared for content analysis of the page including a chat feature. This blog gives a tour with some examples. You can try it out yourself - it is publicly available as installable package for AEM 6.5.x and AEMaaCS and is open source (MIT license).

The Composum AI is a module that brings AI text generation and analysis capabilities into Composum Pages or Adobe Experience Manager (AEM). It's currently 4 dialogs support generating keywords, translation, text content generation and page text review and various other operation modi, including a chat with the AI if needed. This blog gives a short tour with some examples. You can try it out yourself!

We discuss various possibilities to speed up Sling development with automatic content synchronization from the content you edit in your IDE, if possible within seconds.

The Composum package registry browser provides a UI to manage content packages in package registries - both JCR and in the filesystem.

This Blog entry has both the purpose of recounting some experiences and learnings from a AEM 6.5 to AEM as a Cloud Service migration I was working on recently, and highlighing some points where the Composum Nodes and the Composum Browser can help you there.

This tells some of the experiences, approaches and findings when migrating our live system from Sling Launcher 11 to Sling Launcher 12.

In order to make the use of the Composum Nodes tools usable in different environments and still ensure security against unintended or unauthorized manipulation in the repository, individual features or even complete modules of the Nodes console can be restricted or completely disabled.

Components consist of server-side logic (model implementations, render templates) and client-side functions (Javascript) and style. The implementation is done on the server side as Sling components and on the client side via client libraries.

Each Sling component implemented in this way defines a resource type that is referenced by the content elements, i.e. the content resources. This data of the CMS thus receives its respective function. In order to adapt this function to changing requirements without always having to create new components and modify the content, a 'theme' can be used to partially or completely change the implementation of a set of components without having to change the content of the CMS. A 'Theme' can also be assigned to an area in the page hierarchy that wants to implement the same components differently.