Why Decoupled Architectures Now Make Sense for WordPress
Decoupled architectures have become a defining trend of this era of web development. We’ve seen it most noticeably with the rise of the Jamstack architecture, exemplified by companies like Netlify and Gatsby. But it’s also been a key theme in the large ecosystem of websites built using the open source WordPress content management system (CMS). In fact, if you look closely, there’s not a great deal of difference between Jamstack companies and modern WordPress hosting companies like WP Engine.
WP Engine is one of the main competitors of Automattic, the company that runs wordpress.com and has been on an acquisition tear lately (most recently, acquiring a small startup that created a React framework called Frontity). However, while Automattic has only reluctantly embraced decoupled architectures, WP Engine is the opposite. It sees the headless CMS approach as “the future of enterprise WordPress.”
To find out how WP Engine’s headless CMS strategy differs from Automattic’s, I spoke to WP Engine’s co-founder and CTO, Jason Cohen.
WP Engine vs Automattic
Soon after we began talking, I realized that Cohen has a much different viewpoint on the decoupled WordPress trend than Automattic CEO (and WordPress co-creator) Matt Mullenweg. While Mullenweg has been critical of Jamstack and even the word “headless”, Cohen sees decoupled architectures as a positive trend for the WordPress ecosystem.
“This movement to decoupled, or headless, or Jamstack, or whatever word you’d like… it’s easy to see that as a threat to WordPress,” he told me. “But to me, it’s simply an evolution of technology. WordPress has been around for [nearly] 20 years, so it’s natural there be evolution — and in fact, it’s kind of amazing that there’s an evolution that still includes WordPress, and needs WordPress. A decoupled website needs a CMS, that has not changed and it’s not going to change.”
Developers Can Strike Out on Their Own
“That’s what the marketers have and know and like,” said Cohen, about WordPress. He thinks that being able to port data from WordPress into web apps “is a way for developers to strike out on their own, without having to mess about with legacy systems.” By legacy, he means WordPress as a monolithic publishing system that largely still runs on PHP.
To Jamstack or not to JAMstack, That is the Question
Much of the hype around decoupled web architecture over the past year or two has come from so-called Jamstack companies, like Netlify, Gatsby and Vercel. I asked Cohen how WP Engine positions itself versus those companies? He replied that WP Engine competes with each company in different ways, but that the Jamstack catchphrase has been confusing.
“Netlify started by just being a CDN. Then they invented the term ‘Jamstack’ and they still own it. Then, they added products to their product line. From just a static CDN, they added Node hosting and then they created a CMS, and so forth. And as they did that, they then edited what Jamstack means — they even changed the spelling, right.” [from JAMstack to Jamstack]
He added that Gatsby and Vercel no longer market themselves as Jamstack companies. (Sure enough, after checking the homepages of both companies, I can confirm there is no mention of Jamstack on either — other than Gatsby using the word to help promote an upcoming event.)
Perhaps the most well-known CMS in the Jamstack universe is Contentful, which Cohen mentioned as a possible alternative to WordPress. But again, WP Engine only partially competes with Contentful. “It’s complicated,” he said, “because everyone’s supplying different pieces.”
WP Engine and the Ascendence of Developers
WP Engine is a fascinating company when looking at the evolution of the WordPress ecosystem over the years, from the monolithic approach where developers were bit players (they were in charge of plugins, basically) to a full-on decoupled development platform where developers are central to the process.
WP Engine has been in the thick of this evolution. It started out in 2010 as a small premium WordPress host, as explained in this 2010 post by my old tech blog ReadWriteWeb. But it has grown significantly over the past decade, in large part tracking the rapid growth of the web developer market.
As Cohen says, the one piece of the 2010-era CMS that is still absolutely needed in modern web development is the content editing interface. But for other aspects of a CMS, we’re seeing that the frontend — presentation and publishing — can be done in other ways now. This is why the headless CMS approach is so compelling, going forward.