Custom Adobe Experience Manager Assets Compute Worker with App Builder
summary
Demo shows a runnable pipeline that builds and deploys custom AEM Assets Compute workers using App Builder SDKs and Photoshop APIs. It implements three sequential workers: Autotone (Lightroom/auto-tone), Photoshop Action (predefined PSD script), and color extraction (Content and Commerce AI), moving files via cloud storage and io runtime; local dev uses aio-cli and runtime env vars; deployment maps runtime URLs into AEM processing profiles and the pipeline produces and saves renditions and metadata successfully.
AI-written summary · about
chapters (13)
- 0:00Introduction to custom workers
- 1:07Technical overview of AEM processing
- 3:33Use cases for custom workers
- 6:04Setting up the project
- 9:57Exploring generated code
- 12:24Configuring environment variables
- 14:12Running local development
- 16:38Extending worker functionality
- 18:44Adding new workers
- 21:17Testing workers locally
- 23:06Deploying to AEM Assets
- 25:13Testing in AEM Assets
- 27:23Conclusion and Q&A
related talks
38mSeamless Integration of Experience Manager Assets with Applications
39mAdobe Experience Manager as a Headless CMS - Where/When/Why?
54mAdobe Experience Manager Rock Star: The Headless Challenge
01h 00mBuilding next gen composable services with Experience Manager
02mAEM Shorts: Content Reuse and Omnichannel Delivery with AEM
02mAEM Shorts: Modernizing Your AEM Implementation with Cloud Service
52mKeynote: Headless Today & Tomorrow with Adobe Experience Manager
19mBringing Adobe's Creative Cloud to the web: Starting with Photoshop