Tridion Experience Manager (XPM) Blog Post Series

I’ve recently worked on a project with a client where the Development team were tasked with implementing Experience Manager (a.k.a. XPM) as part of the Phase 2 requirements.

Let me start by saying that I agree 100% with Will Price on this one, that if possible Experience Manager should be implemented from the outset and not pushed back to Phase 2 of a project.

I appreciate that Phase 1 timescales are always tight, but implementing Experience Manager from the get-go makes it significantly easier. Not only in ensuring that the HTML and XPM markup work nicely together, but also allowing the content model to be optimised for XPM (before thousands of Components are created!) and that XPM is given the same stringent testing that normally comes with a Phase 1 release.

Anyway, I wasn’t around during Phase 1 of development and didn’t have the opportunity to fight for its inclusion, so Phase 2** it was!

Although Experience Manager has been around (under a less jazzy name) since 2012, details of exactly what it does are not really documented in one place. There are some great blog posts, videos and Tridion Stack Exchange answers relating to Experience Manager, but not one single introductory reference point (with pictures!) on what it provides functionally.

In this short blog post series, I’m going to answer the following questions:

I will be releasing these blog posts over the next few months.

If you're having XPM problems then you can ask for help over on the Tridion Stack Exchange site or contact me directly at

**Strictly speaking, this was a later sprint in the Phase 1 of a Tridion re-architecting project, but by then a lot of the content modelling decisions had already been made and a lot of content migrated from the old solution.