First came the WebCMS, then came #headless and now, it’s time for #composable…
It may look at first sight that it’s getting more complicated as we move from left to right, but all the complexity that is hidden in the implementation and customization of monolithic architectures is turned into lego blocks that are individually manageable, low/zero code and simply more agile to work with. I’ll address this in more detail in an upcoming post.
I want to call out three key things in the following infographic:
1) We’re going from one CMS to multiple CMSs i.e Content is no longer centralized in a single hub. It can come from multiple sources such as PIM, Commerce Platforms, legacy CMS, headless CMS, etc. This doesn’t mean you should sync all the content into a single hub…you need to let content sit where it is, but have a way to access and orchestrate it in real-time.
2) If we’re going to make Headless work, it’s no longer acceptable for the Experience Delivery to be in the hands of the developer. We’ll have to go full circle back to the days when marketing used to control the following: a) Who sees what when and where b) How the content is presented in the front-end. This doesn’t mean we failed in delivering on the promise of headless…it just means that in the evolution from the old to the new, we’ve learnt some lessons and we’re applying them in new and exciting ways while future proofing our architecture at the same time.
3) The Experience Intelligence and Orchestration layer must be able to pull content from multiple sources in real-time and offer marketing teams the control to determine who sees what and when on every channel. This is the brain of the composable stack and should not be hardcoded in the front-end i.e black boxed away from marketing.