Sacra Logo

What would it take for headless WordPress or Shopify to become the primary delivery method and what is the adoption roadmap?

Jason Lengstorf

VP of Developer Experience at Netlify

I think the thing that we're missing is the companies that commoditize it. With WordPress you had Automattic the company, and then you had ecosystem companies like WooThemes or Envato. They built these huge marketplaces around plug and play WordPress plugins and themes and add-ons and all these different features. I could go shopping and say, "Yeah, I want a forum. I want an E-commerce store. I want moderator controls. I want better SEO." I click all these buttons. My site gets auto-configured, and I've never looked at code.

This model is clearly what we're heading toward. We're not seeing new companies ship monolithic CMSs, or at least not very many. Even WordPress would prefer that we didn't use WordPress as an API, I think, at least from the outward messaging I've seen. They've built a really good API. They've got really good tools around how to use it in headless mode, because I think the writing is on the wall. Developers are making the choices now, and they don't want to work with a lot of stitch-together monolithic CMSs. They want to work with APIs.

My assumption is that, now that we've seen that, the market is aware of that. We're going to see people start to target the commoditization of headless site building. We can see this in a few places. There are some companies that are standing up. There's Vue Storefront, which is like, "Hey, you want a Jamstack-friendly ecommerce store? Click a few buttons and you get that." We've got agencies that are really specialized in this, for the more corporate companies that want to make the switch. We've got more of those plug and play tools starting to show up in companies like Spring, which is very similar to Shopify in that you show up and just say "I want a store," and it just spins up. That's built as a Jamstack site. They're moving that way.

My suspicion is that we'll see that, as the ROI of using the Jamstack starts to become more apparent -- and we've got that ROI report that just came out with Forrester that shows a huge return on investment for switching to the Jamstack -- and as those results get repeated and it becomes more commonplace, we'll see even the people who don't really want to do it start defaulting to headless, because it'll cost them less to run their services. It increases their margin.

Find this answer in Jason Lengstorf, VP of Developer Experience at Netlify, on Jamstack's anti-monolith approach
lightningbolt_icon Unlocked Report