The CMS was born to make content sites possible. Now, it’s being reimagined to make them incredible.
In the early 2000s, publishing on the web was difficult. The CMS emerged as a single application to store content, build sites, and deliver them to users.
Over time, the feature landscape broadened — key areas like search, analytics, payments, personalization, and e-commerce emerged. In each category, specialized tools improved rapidly, while the quality of monolithic enterprise CMS applications like Adobe Experience Manager and Sitecore has stayed roughly the same.
Modularizing the CMS
Today, a website team running an e-commerce site can store product inventory in Shopify, product listings in Salsify and reviews in Bazaarvoice. A team running a paywalled content site can create stories in WordPress, store video in JWPlayer, user data in Auth0, and subscription data in Recurly.
Teams are adopting these services because each is tailored to a specific use-case; the generic enterprise CMS alternative is often optimized for none.
Emergence of the Content Mesh
This is the first post in a series, Journey to the Content Mesh, intended to explain the emergence of a “content mesh” — the infrastructure layer for a decoupled website. The content mesh stitches together content systems in a modern development environment while optimizing website delivery for performance.
The previous generation of enterprise CMS offered an often-generic content editing experience glued to out-of-date development and deployment environments. The emerging strategy for content management selects best-of-breed solutions, tailored to specific use-cases like e-commerce or blogging; it provides a modern framework for rapid iteration and it generates lightning fast websites out of the box.
The content mesh empowers developers while preserving content creators’ workflows. It gives you access to best-of-breed services without the pain of manual integration.
Three Areas of Rapid Innovation
Change is being spurred by the confluence of three revolutions in how we create and consume content:
- Content management. Monolithic CMS applications are being replaced by modular, specialized content systems.
- Development techniques. Modern UI frameworks like React are becoming essential to rich user experiences.
- Performance. As mobile surpasses 50% of internet traffic, high-performance is becoming a must-have, not a nice-to-have.
These technological changes have made modern web technology both essential for creating fresh, novel, and engaging digital experiences, and more accessible for the enterprise.
Each change primarily affects a different stakeholder — marketing, development/IT, and the end user, respectively.
The key challenge is that without a content mesh, integrating these systems together is a lot of work. Forrester titled one of their report sections: “Warning: Headless Content Management Is For Do-It-Yourself Shops.” But with a content mesh, all of these systems can be brought together in a unified, low-cost, low-defect whole.
In other words, the content mesh makes developers, content creators, and users all happy.
Integrating Modern Technologies Without the DIY Work
As this series continues, we’ll explore the rise of this “content mesh” — that allows enterprises to adopt these new technologies without needing to DIY themselves.
In Part 2, The Unbundling of the CMS, we’ll explore the rise of headless CMSs and best-of-breed website content and functionality systems.
In Part 4, Why Mobile Performance is Crucial, we’ll discuss the ROI of site speed, explore two modern, complementary trends for improving web performance and how website teams can get the best of both out of the box.
In our conclusion, Creating Compelling Experiences, we’ll discuss a step-by-step approach for choosing a content architecture, modern development environment, a performance strategy — and most importantly, choosing a “content mesh” that makes all the other choices easy. We’ll also explore how one clear option — Gatsby — emerges as the most feature-complete of any content mesh alternatives.