Rules of AEM

  AEM + AI Content Generation Workflows: Automate Content at Scale Introduction Content teams using AEM are under constant pressure to produce more content, faster, and in multiple languages. With the rise of LLMs like OpenAI's GPT-4 and Anthropic's Claude, it is now practical to integrate AI content generation directly into AEM workflows — automating first drafts, metadata, translations, and content fragment creation. In this post, we'll build a practical AEM Workflow that calls an external AI API, generates content, and writes it back into AEM Content Fragments. Architecture AEM Workflow Trigger (Page / Asset event) ↓ Custom Workflow Process Step (OSGi) ↓ HTTP Call → OpenAI / Claude API ↓ Parse AI Response ↓ Write to AEM Content Fragment / Page Properties          Step 1: Store Your API Key Securely in AEM Never hardcode API keys. Store them as Cloud Manager environment variables and read them via OSGi config. OS...

      ## 1. Smart Tagging in AEM Assets Smart Tags use a machine learning model trained on Adobe's Sensei framework to automatically tag assets uploaded to the DAM. ### How it Works When an asset is uploaded, AEM sends it to the Sensei Smart Tagging service, which returns a set of predicted tags. These are written back to the asset metadata under `dam:suggestedTags`. ### Enable Smart Tags — OSGi Configuration Navigate to: ``` /system/console/configMgr → Adobe CQ DAM Smart Tags Workflow Process ``` Ensure the Smart Tag workflow is linked to the **DAM Update Asset** workflow: ```xml <!-- /apps/your-project/config/com.adobe.cq.dam.smarttagging.impl.SmartTagsManagerImpl.xml --> <?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0"           xmlns:jcr="http://www.jcp.org/jcr/1.0"     jcr:primaryType="sling:OsgiConfig"     trainedTagsEnabled="{Boolean}true"     a...

Migrating from AEM 6.x to AEM as a Cloud Service: What to Expect ? Introduction If you're currently managing an AEM 6.x project, chances are you’ve heard about AEM as a Cloud Service (AEMaaCS). Adobe is clearly shifting toward this cloud-native model for low/medium complex customers and while there are definite benefits, developers should be prepared for a few surprises too. I recently worked on a migration project and wanted to share what developers should expect , from code refactoring and CI/CD changes to losing root access and dealing with strict dispatcher rules.     Whats is Great about AEMaaCS  1. Automatic Upgrades Say goodbye to manual patching. AEMaaCS updates automatically.  Adobe handles the platform updates, with no need to plan downtime or test service packs. 2. CI/CD with Cloud Manager Deployments go through Adobe Cloud Manager, which checks for code quality, security, and performance before pu...

Caching Strategy - CDN/APACHE - Internal working & Example Headers Imagine a company is hosting a website on a server in any cloud provider like AWS, AZUR, GCP . It may take around 100ms to load for users in US, but it takes 3–5 seconds to load for users in Finland. Fortunately, there are strategies to minimize this request latency for far-away users. These are called Caching and Content Delivery Networks (CDNs), which are two important concepts in modern web development and systems design. CDN are of different-different type   based on cloud service provider below are few most used ones – Cloud Front , by AWS Azure Front Door Content delivery solution from Akamai Different Caching Strategies Caching data can greatly improve the performance of applications. There are typically 4 common places where we can store cached data. Browser Caching Browser caching involves storing website resources on a user’s local computer. When a user revisits a site, the brow...