Loading articles
Learning path
Discover Edge Delivery Services (EDS), performance optimization strategies, content delivery patterns, and modern web architecture.
Content storage in AEM and EDS. Covers JCR, da.live, the EDS content bus, the preview and publish pipeline, asset storage, and the path from authoring to browser render.
Read chapter →
EDS limitations and alternatives. Covers server-side logic, workflow, JCR queries, AEM Forms, MSM, Content Fragments, DAM schemas, and Dispatcher rules.
Read chapter →
The six architectural approaches for using AEM Edge Delivery Services — pure DA, Universal Editor on AEM, AEM as a headless JSON backend, Content Fragments with GraphQL, external headless, and the hybrid same-domain pattern — with the approach we chose on the POC and an honest answer to "why pay for AEM and EDS?"
Read chapter →
CSS architecture in EDS. Covers block scoping, custom properties, cascade order, responsive rules, theming, and reuse without a build step.
Read chapter →
Universal Editor data-aue-* annotations for xwalk projects. Covers data-aue-resource, data-aue-type, data-aue-prop, data-aue-label, data-aue-model, containers, and editor-support.js.
Read chapter →
Comparison of Document Authoring and Universal Editor. Covers authoring workflow, developer setup, content storage, feature gaps, and when to use each approach.
Read chapter →