📄️ Local Development Setup
This post describes the steps and software requirements you need to create and set up a working local AEM instance.
📄️ Cloud Sandbox Setup
This post describes how to setup a Cloud Sandbox development environment.
📄️ AEM as a Cloud Service
AEM as a Cloud Service (AEMaaCS) is Adobe's cloud-native, fully managed version of
📄️ Deployment
Deploying AEM projects varies significantly depending on the hosting model. AEM as a Cloud Service (AEMaaCS) relies on Cloud Manager pipelines with strict immutability rules. Adobe Managed Services (AMS) provides a middle ground with managed infrastructure but more flexibility. On-premises installations give full control but require manual orchestration and operational discipline.
📄️ Dispatcher Configuration
Introduction
📄️ Performance
Performance in AEM spans multiple layers: content queries against the Oak repository, server-side rendering through Sling Models and HTL, caching at the Dispatcher level, and frontend delivery to the browser. Optimising only one layer while ignoring the others will leave bottlenecks on the table. This page walks through each layer with concrete techniques, code examples, and the most common pitfalls.
📄️ Security Basics
Security in AEM is a multi-layered concern that spans user management, access control, request filtering,
📄️ Testing
Testing in AEM usually combines unit tests for backend logic, integration tests for content and services, and UI tests for authoring behavior.
📄️ E-Mail Service in AEM
AEM provides a built-in e-mail infrastructure based on the Day CQ Mail Service
📄️ Adobe Edge Delivery Services
Adobe Edge Delivery Services (EDS) -- formerly known as Project Helix / Franklin -- is far
📄️ Adobe I/O App Builder
Adobe I/O App Builder (formerly Project Firefly) is a serverless extensibility framework
📄️ ACLs and Permissions
AEM's permission model is built on Jackrabbit Oak's access control layer. Every read,