I’m currently in the process of migrating many thousands of pages out of OrchestraCMS, a Salesforce-native CMS, and into AEM for my client. In doing so, I’ve had to do some extensive work with Pages and Resource and thought I’d share some lesser-known intricacies of doing so. While the contents of this post will lean …
Every AEM infrastructure leverages the dispatcher for one or all of caching, security, and load balancing. As far as caching is concerned, many AEM customers rely on flush agents to keep things fresh. Flush agents are great as they recognize activation requests for page content and then send a flush request to their configured dispatcher …
Typically, versioning in AEM is something only thought of in the context of pages. In fact, the common way in which one works with versioning is baked into the Touch UI Sites console which further couples the two. However, versioning isn’t limited to pages. Any node in the JCR can theoretically be versioned. In this …