At The Telegraph, we use Adobe Experience Manager (AEM) as our web platform, with various websites running on it. The entire website is divided into two sections:
1. Core web which includes content from the wider Editorial teams (News, Business, Sport etc)
2. Travel web which includes content from the Travel Editorial team only.
The Core Web team uses a custom authoring tool that runs on top of AEM Author, providing a bespoke UI engineered for Editorial’s needs and helping to streamline the creation, updating and publication of content on the website. The authoring tool also includes a cool feature, whereby new topic pages are created as soon as X number of pages are given the same tag and published. In contrast, our Travel Editorial team has historically used AEM’s Classic UI for their purposes of creating and tagging content.
How did we do this?
We created a working group that consisted of Engineers, Architects, Editorial, Adobe Managed Services & the Delivery team. We spent a significant amount of time generating a mapping from the old tags to the new tags — there were nearly 4000 travel tags that needed mapping. After discussing various approaches we divided the entire migration into various phases, detailed in the table below. This set of phases came about because we were trying to automate as much of the process as possible & minimise the amount of manual work that would need to be done afterwards.