Adobe Experience Manager

The platform most of the author's current work runs on: an estate of brand sites built on a shared component set (Ivy) over AEM Sites, now being measured for migration to Edge Delivery Services. The front end is HTL templates, client libraries assembled by aem-clientlib-generator, and a long tail of jQuery.

What AEM is good at is governed authoring at scale — templates, policies, workflows, permissions, a dispatcher that caches whole pages. What it costs is build time, Java between the front end and the page, and a component model that resists change once an estate has grown on it.