Rules of AEM

  AEM Edge Delivery Services + AI: The Future of Content Delivery Introduction AEM Edge Delivery Services (EDS) — formerly known as Project Franklin / Helix — is Adobe's modern, high-performance content delivery layer. It decouples content authoring from delivery, serving pages at the edge with near-perfect Lighthouse scores. When you combine EDS with AI, you unlock capabilities like real-time content personalization, AI-generated blocks, and intelligent A/B testing — all at the edge. In this post, we'll walk through how to integrate AI into an EDS project with practical code examples. How Edge Delivery Services Works (Quick Recap) Author (Google Docs / SharePoint / AEM) ↓ AEM Pipeline (Franklin Bot) ↓ Content stored at Edge (Fastly CDN) ↓ User Request → Edge Worker → HTML served in <100ms EDS pages are built with plain HTML/CSS/JS blocks. There's no traditional AEM dispatcher — content is served directly from the CDN edge.       ...

  Using AI Tools for AEM Development: Code Faster with Copilot & Claude Introduction AEM development has always required deep expertise — Sling models, OSGi configurations, HTL templates, Oak queries, and dispatcher rules all have their own nuances. AI coding assistants like GitHub Copilot , Claude , and ChatGPT now understand AEM well enough to dramatically speed up day-to-day development tasks. In this post, we'll look at practical examples of how to use AI tools effectively for AEM development — including the right prompts that produce high-quality AEM code.          1. Writing Sling Models with AI Prompt that works well: Write an AEM Sling Model for a component called "HeroComponent". It should: - Be adaptable from Resource - Inject title, description, ctaLabel, ctaLink from the component's JCR properties - Use @PostConstruct to build a full link with a .html extension - Include @Optional annotations where appropriate - Follow AEM best pract...

  AEM Security in the Age of AI: New Threats & How to Defend Against Them Introduction AI is changing the security landscape for AEM deployments in two important ways. First, attackers are using AI to make their attacks smarter — faster credential scanning, AI-generated phishing payloads, and automated vulnerability probing. Second, as AEM teams integrate AI features (chatbots, content generation, RAG pipelines), they introduce a new class of vulnerabilities that didn't exist before. In this post, we'll cover both: how to harden your existing AEM setup against AI-powered attacks, and how to secure the new AI integrations you're building.             1. Prompt Injection — The New XSS If you've built a chatbot or AI assistant on top of AEM content (like the RAG pipeline from our previous post), prompt injection is your biggest risk. It's the AI equivalent of XSS — an attacker embeds malicious instructions inside content that your AI system the...

  Building a RAG Chatbot on AEM Content using LangChain + OpenAI Introduction Imagine a chatbot that can answer questions like "What is our return policy?" or "How do I configure the Dispatcher?" — drawing answers directly from your AEM-managed content. This is exactly what Retrieval-Augmented Generation (RAG) enables. RAG combines a vector database (to store and search your content semantically) with an LLM (to generate natural language answers). The result is an AI assistant grounded in your actual AEM content, not hallucinated facts. In this post, we'll build a complete RAG pipeline that ingests AEM content fragments, stores them in a vector database, and serves answers via a chatbot API. Architecture AEM Content Fragments / Pages ↓ AEM Content API (JSON exporter) ↓ Python Ingestion Pipeline (chunking + embedding) ↓ Vector Database (Pinecone / ChromaDB) ↓ Query → Semantic Search → Top-K chunks ↓ ...

  AI-Powered Dispatcher & CDN Optimization for AEM Introduction AEM's Dispatcher and CDN layer is the frontline of performance and security. Traditionally, caching rules, TTLs, and security filters are all manually configured. But with AI and machine learning entering the infrastructure space, it's now possible to make smarter, dynamic decisions — from predicting cache invalidation patterns to detecting bot traffic and anomalous requests automatically. In this post, we'll cover practical ways to integrate AI/ML into your AEM Dispatcher and CDN stack.           1. AI-Based Anomaly Detection in Access Logs The first and most immediately useful application is analyzing Dispatcher/Apache access logs using AI to detect DDoS patterns, credential stuffing, or scraping bots. Log Parser Script (Python + OpenAI) Instead of manually writing regex rules, feed your access logs to an LLM to identify suspicious patterns: # log_analyzer.py import openai import...

  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...