How Creative Content Automation in AEMaaCS is Speeding Up Content Delivery – Part 2

Welcome to the second part of our multi-part series on using Content Automation in AEM as a Cloud Service to enhance your Creative operations. If you missed the first blog of this series, which provides an overview of this feature by Adobe and explores relevant use cases, we recommend checking it out. In this article, we will take a closer look at the creative operations in Adobe Lightroom and how they can be replicated in AEM as a Cloud Service.

The Process in Adobe Lightroom

Let’s begin with a simple example of what is typically done in an Adobe Creative application such as Lightroom. In this case, a processing profile will be created that renders a black and white image and saves it as a rendition with the main image. But first, let’s review a typical scenario in Lightroom:

1. A main image is created and selected from a photo shoot

2. The image is exported with various settings, such as 100% quality:

1. A request is made to convert the image to black and white, at 50% quality

2. The black and white image is created in Lightroom using a preset

1. The black and white image is then exported at 50% quality:
   

2. Both images are uploaded to AEM Assets, in their respective folders

With Content Automation you can set up the following steps to perform the processing in AEM:

1. The Lightroom filter is exported from Lightroom and saved in “XMP” format.

1. The Filter is then uploaded to a folder in AEM Assets:

1. A processing profile is created in AEM:

a) Create a new processing profile:

b) Add a Creative processing section

c) Select the Lightroom Filter uploaded from Step #2, along with 50% quality, and an optional target folder for a standalone file:

d) Save the processing profile

e) Apply the profile to a folder so that images uploaded there will run the processing profile:

1. Once the processing profile is created, it will be executed via microservices after an image is uploaded to the assigned folder. This will create an additional rendition, and optionally create an image based on the processing profile.

2. In the Card view, the folder will show the processing profile applied:

1. Upload a main image to the folder, and note the additional rendition created from the processing profile:

After setting up the processing profile, any images uploaded to the folder will automatically generate the additional black and white rendition, eliminating the need for manual processing in Lightroom.

For reference, there are several more processing profiles available with Content Automation, detailed below:

Wrap Up and Further Reading

In addition to Content Automation, Adobe has several offerings integration options between AEM as a Cloud Service Assets and Creative Cloud applications. See their best practices documentation to explore some of the use cases.

There are numerous ways to configure microservices to process assets, such as creating custom FPO renditions, changing file format, and calling 3^rd-party systems to update data for a PIM system. Additional configurations and settings are described in detail on Adobe’s documentation site.

We hope this deep dive into Content Automation has improved your understanding of its capabilities and how it can be leveraged to benefit your organization. Be on the lookout for a third article that will provide a detailed example using Adobe Photoshop Actions. Thank you for reading!

For a live walkthrough of the process, see our video:

[youtube https://www.youtube.com/watch?v=aKAbTygQZWM?rel=1&version=3&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent&w=640&h=360]