adobe experience manager — Articles & interviews with modern leaders

I've spent over 13 years implementing Adobe Experience Manager (AEM) solutions for some of the world's most recognised brands. As Technical Design Authority for EE's AEM implementation, I led the creation of an 8,000-page help website and trained over 150 stakeholders in AEM usage. At DigitasLBi, I led a team of 30 global architects on the UK's largest AEM implementation for the Nissan/Renault Alliance, eventually targeting over 200 websites in 30 languages across five brands.

My work with MediaMonks brought me to projects for Twitter, Genesis USA, and McLaren, where we pushed beyond traditional AEM frameworks to create richer experiences. At Cognizant Netcentric, I advised on headless AEM implementations for Ford, and at Inspired Thinking Group, I consulted on Jaguar Land Rover's migration to AEM from Tridion CMS.

Then onto Ford Motor Company with Netcentric, where I architected a completely headless AEM implementation using React.

Latest endeavours include investigating Adobe Edge Delivery Services (Franklin), a high-performance document-based authoring system with a modern build system, that is being integrated into AEM.

Throughout these experiences, I've witnessed first-hand how AEM has evolved from its open-source foundations to a comprehensive enterprise platform, and I'd like to share insights on where it's headed in an increasingly composable future.

Adobe Experience Manager (AEM) is widely recognized as one of the market leaders in the enterprise CMS space and they don’t seem to be resting on their laurels.

Last year they released Edge Delivery Services, which had a big impact for AEM customers to help deliver websites at top performance and also Project Helix (earlier referred to as Franklin) enabling marketers and content teams to use their favorite tools, such as Word, Excel, Google Docs, and Google Sheets with GDrive or Sharepoint, to create stunning, responsive websites with perfect lighthouse scores.

Fast forward and Adobe unveiled the Universal Editor for AEM with Edge Delivery Services at Adobe Summit 2024 in late March. With Universal Editor, they’ve changed both how content creators and developers interact with the CMS.

As you might expect with a new component model there are migration challenges and the previous AEM components do not work with the Edge Delivery Services in the Universal Editor.

Adobe recommends using one authoring method; for most existing organisations shifting to the new world there are many changes to be made, this is similar to replatforming your website, if your organisation uses multi-sites then all sites must be migrated at once.

Let’s look closer at why the Universal Editor matters and the implications for customers.