❌

Reading view

There are new articles available, click to refresh the page.

#241 – Tiffany Farriss on Drupal Funding, Community, and a Shared Journey With WordPress

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, Drupal funding, community, and a shared journey with WordPress.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.

So on the podcast today we have Tiffany Farriss. Tiffany has spent the last 30 years working in web design, development, and creation, and she’s been deeply embedded in the Drupal community for the past two decades. She’s currently the interim CEO of the Drupal Association and is the organization’s longest serving board member after Drupal’s founder Dries Buytaert.

This episode is a bit of a departure as we usually focus squarely on WordPress, but Tiffany brings a wealth of experience from the broader PHP family, and this conversation explores the similarities and differences between the WordPress and Drupal ecosystems, particularly when it comes to infrastructure and the sustainability of open source projects.

Tiffany explains the maker-taker problem, and the challenges of sustaining free software platforms that end up in millions of sites across the web. She shares her insights on the real costs behind open source stewardship, drawing from both data and experience, and discusses how tiny groups have shouldered the burden for everyone, and why that might no longer be viable.

The discussion explores the Drupal Certified Partner Program, the push towards quantifying contributions, and how the open source community can improve transparency and sustainability.

Tiffany also touches on the role of public sector procurement in shaping the future of open source, the impact of new regulations, and how community driven recognition could incentivize more organisations to buy their round of beers for the ecosystem.

If you’re interested in the sustainability of open source, the evolution of governance models, and how WordPress professionals can learn from the broader PHP landscape, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Tiffany Farriss.

I am joined on the podcast by Tiffany Farriss. Hello, Tiffany.

[00:03:19] Tiffany Farriss: Hi Nathan.

[00:03:20] Nathan Wrigley: Thank you for joining us. So this is a little bit of a departure. Usually we talk about WordPress. It’s WordPress on the menu every single day of the week. And that is going to be the case, I suspect a little bit today. But there’s also going to be a foray into Drupal because Tiffany is very much connected with the Drupal community.

So Tiffany, really just to get this podcast started, can I just offer you a chance to give us your little bio, tell us who you are and what you do over on the Drupal side, lo these many years. It’s been multiple decades that you’ve been involved in various different ways I think.

[00:03:52] Tiffany Farriss: It has been. Yeah. Thank you Nathan. I’m really glad to be here. I do consider all of us part of the PHP family, whether we’re Drupal or WordPress or Joomla or TYPO3, like I think we all have so much in common.

But I am Tiffany Farriss. I’m currently the interim CEO over at the Drupal Association. I have been involved in web design, development, creation for the last 30 years. And I’ve been heavily involved in the Drupal community for the last 20.

In particular in its governance. I’m the longest tenured board member of the Drupal Association, the 501 (c) (3) that is responsible for the governance. Other than Dries Buytaert, who is the founder of the Drupal Project.

So I’ve been around a long time and I’m currently on leave from my own company, palantir.net to take a year to help Drupal kind of navigate this time of kind of intense disruption, I think it is for all of us. Pretty safe to say, that we are all experiencing the same disruptions from AI. And then just economic pressure in general.

[00:04:50] Nathan Wrigley: So Drupal, I suppose, it would be a good thing to say at this point, Drupal is very similar in its project, in its status, in its goals, in its aims, in its infrastructure and technology to the CMS that most people listening to this are familiar with. It’s a PHP based CMS used by millions of websites all over the world. So broadly it’s the same.

Now you mentioned the foundation. Would you just be able to dig into that a little bit more because that may be confusing for people on this side. There may be some significant differences there. What does the foundation get itself involved with? I know that you described that a little bit there, but if you could go into a bit more depth, that would be great.

[00:05:26] Tiffany Farriss: I do think our governance is one of the places where WordPress and Drupal are a little bit different. In Drupal, we have the Drupal Association, which is an independent 501 (c) (3), which is a US-based not-for-profit. And we have specifically an educational and scientific mission that we’re authorised to do.

We run Drupal.org. We run all of the infrastructure. We support all the security coordination. And we are responsible for Drupal Cons around the world. We do have a founder as well, right, Dries, and he is currently the Executive Chairman of Acquia. But Acquia doesn’t have the same single privileged actor role, that say Automattic does in the WordPress community.

Dries serves on the board, but he doesn’t control the board and he doesn’t control any of the technical steering committees, although he is still the founder and the lead of the project.

[00:06:17] Nathan Wrigley: Okay. So there is a significant difference there, isn’t there? That’s kind of interesting.

[00:06:20] Tiffany Farriss: Yeah.

[00:06:20] Nathan Wrigley: Okay, we’ll dig into that in a moment. However, in the preparation for this podcast episode, Tiffany was very kind to send me three things.

One of them was a YouTube video. It runs to about 20 minutes and sort of summarises what we’re going to talk about, I think, fairly well.

Another one was a blog post that you wrote in June of this year. It’s called Freedom is Not Free, A model for Open Source Sustainability. Again, very much aligned to what we’re going to talk about. That’s on palantir.net, which I’m at pains to point out is not the palantir that you are probably thinking about when you say the word palantir. And there’s another one which again, tackles the same subject, written broadly the same time. It was July this year, written by Dries, the founder of Drupal.

And what we’re trying to deal with here is, what I think Dries has summed up in the past is this maker, taker problem. And it’s very difficult to summarise. I must confess, I genuinely cannot articulate this problem. No matter how many times I’ve tried to articulate it to friends, to colleagues, to relations. At some point I get lost. At some point, the dynamics of it and the argument of it kind of boils boils down to it’s a moral thing.

So I’m just wondering, could you paint the picture of what you were trying to say in that YouTube video and in your blog post. What is the open source sustainability problem that you think, amongst many others, we have at the moment?

[00:07:47] Tiffany Farriss: We like to talk in open source about free and the four freedoms, especially for projects that are based in the GPL, right? But one of those freedoms, I think it comes down to the idea of the word free, right? There’s free is in speech. Where I am free to say what I want and when I want, and accept the consequences of that.

But then there’s also this idea of free as in beer. And the reality is that the beer was never free. And the problem we have in open source is that for the last 25 years of Drupal, a really small group has been buying the rounds of beer for an entire ecosystem. And what I’m saying is that, beer has never been free. You just haven’t been taking your turn at buying the round, right?

So as we deal with kind of the pressures of the current economic situation, the uncertainty and opportunities created by AI, the number of people who are still buying those rounds is dwindling. But there’s still a lot of people who want to drink that free beer. There’s still a tonne of people who use WordPress, a tonne of people who use Drupal and get a lot of value out of it, right? They’re enjoying that.

But what the problem is, is that we have this open source licence, and the licence is what conveys the freedom, right? It makes the code available. And in open source the more people who use the code, the cost of that code goes to zero. And no one’s use of the code is diminished by someone else also using that code.

However, there’s more to being an open source project than just the code. And this is where the concept of stewardship comes in. Stewardship is what makes it dependable. It’s what has made it so that millions of people around the world can feel confident in downloading the software, using the software, hiring someone to create a WordPress or a Drupal implementation for you.

And that stewardship includes things like code hosting, or packaging. Testing frameworks. The security coordination. All of those things, which as more people use it become more expensive, not less.

So, there are these tensions around people who are getting value from open source software, but who currently don’t help pay for the cost that they impose on the project, largely because it’s invisible, right? So I think the first step is that we need to make those costs much more visible. So that’s something I’ve been working on in Drupal for a while. And so I want to expose it, right?

We have 2,800 organisations in the last year who contributed into Drupal, but under 5% of them did two thirds of it, right? There are, I think as in WordPress, you know who really is driving and doing the work. And we do too, right? Obviously in Drupal we know who that is. And because we know who they are, and we know that they’re invested, and that they are passionate about open source and our project. They’re the ones who are easy to ask for financial contributions, or sponsorship to Drupal Con.

So you keep going back to the same pool. And in Drupal’s case, that means that 94% of our financial contribution comes from this tiny group of 5%. So they’re buying the rounds of beer for everyone. And that’s not a sustainable proposition.

[00:11:00] Nathan Wrigley: Do you think, I’m going to rewind the clock a little bit. So, I regard the internet as an ongoing experiment. Where we are now is definitely not where it’s going to end up. And where we were 10 years ago, I don’t know that anybody would’ve predicted that we’d end up where we are today. You know, the internet came around and it evolved in the way that it did.

Do you see in the last, let’s say 25 years that many people have had access to the internet. Can you see moments where, and I’m doing air quotes, mistakes were made, which led to this problem? Or was it just happenstance and serendipity? We just got to this point? There’s no real pointing of a finger. There’s nobody to blame. There’s nobody to say, okay, you made dreadful mistakes. It’s just the way it evolved. There’s no question there, but do you understand what I’m saying?

[00:11:49] Tiffany Farriss: I do.

[00:11:50] Nathan Wrigley: With the benefit of hindsight, can you look back and point the finger, or is it more a case of okay, let’s just deal with the reality of where we’re at now.

[00:11:56] Tiffany Farriss: I can point to that moment. I was on the board at the time when Drupal moved over to Composer, right, and to modern packaging. And what I can tell you is that the board was never, wasn’t a big deal, right? They came to the board and I don’t even think we were really notified that this was happening or what it would mean.

And nobody modelled that packaging costs scaled to infinity, the more people who use it, right? There was no financial model put around it. We became a utility as opposed to just a repository. And I think that’s the moment for us that really changed things. You can continue to run events, Drupal Cons and Drupal Camps and all of that stuff. Those have pretty known economic models, and you can continue to run a website that promotes things. And you probably could even continue to be a collaboration platform.

But once you start to become a packaging utility, then you become part of everyone’s infrastructure. And if you start to provide that for free, and people will expect it to continue to be free. And so I’m, really it’s only in the last couple of years that I’ve started to look into those costs. And for Drupal, we provide the Drupal Association itself provides $10 in services to every site, every year, every modern Drupal site every year.

[00:13:16] Nathan Wrigley: Oh, that’s an interesting stat.

[00:13:17] Tiffany Farriss: It is.

[00:13:18] Nathan Wrigley: You’ve figured that out, you’ve done the maths and it costs $10 for every Drupal site that exists, whether or not they pay anything? That’s such an interesting number.

[00:13:26] Tiffany Farriss: Isn’t But I actually only take in $7.50. So I’ve been pushing forward in technical debt things for years. And that’s a risk, right? That’s a risk for me. And it’s also just unpleasant. I think that if we all start to become a little clearer around what the costs are as a utility, it’s actually not a lot.

When it goes unpaid, it does have a cost, a compounding cost. And in Drupal’s history, what we used to say was if you want to support the project, support the conference. We all learned, obviously, during the pandemic that having an economic model based around a conference wasn’t the best choice.

I still think our ability to get together in person as a community is incredibly valuable, but I don’t see it as the way that we make the money to support the infrastructure. I really don’t like this idea that our revenues, and our expenses are so decoupled like that. And I think that’s really charity thinking.

And part of what I’m working to do is to evolve it into utility thinking? For a couple of reasons, right? One, it’s, not a charity. We are providing a service that people build businesses on, and they expect it to be there. But then also, especially in the case of Drupal, we have such a huge footprint in public sector work, and very large enterprise level government sites. And institutional sites, things that people need to have enterprise level expectations of. And they do, they hit our infrastructure every 15 minutes, right?

Procurement has no way to pay either a community or a charity. However, they can pay for their costs if you can explain it to them in a cost recovery model that this is your share. And I want to be clear, as I talk about what the Drupal Association provides, that leaves aside the volunteer labor for what I like to consider the operational roles that also exist as a part of stewarded open source. Which are the release management, the security team, all of that work that we’re all so very hyper aware of after last week, that also has a cost.

So beyond the $10 that the Drupal Association is providing, there’s $30 provided just by the community as a keep the lights on sort of level. If we had to boil it down to its essence. Beyond what it takes to scratch your own itch, right?

We all know that open source succeeds because I needed to write a module for this, I want to extend that. There are operational roles that aren’t actually in someone’s self-interest to perform, or to underwrite, if you’re an organisation. And so quantifying it has been something I’ve been working on for the last couple of months. And so we’re working now with this $40 a year figure around the services that are provided in addition to the code, that we don’t have to, right? The licence says it’s used as is, but nobody actually does that.

[00:16:08] Nathan Wrigley: No. Okay. That’s an interesting thought. I’m just going to pivot ever so slightly and just talk about the community that you’ve got. I imagine it maps broadly to the community that we’ve got. Do you find having these conversations is challenging? Let’s go with that word. Because over on the WordPress side, is a reluctance for many people in the community to bring money into the conversation at all. You know, it is just almost a taboo in many senses.

And obviously you are pioneering this, the word dollar comes out a lot. You know, you’re actually putting specific numbers out there quite a lot. What’s the pushback like over there? Are there two camps? It’s like the “we’re never going to do this, is crazy,” and the acceptance? Or is there some sort of homogenous bit in the middle where people are starting to realise, okay, Tiffany’s making sense, this adds up. This is what we need to do in 2027, 2028.

Basically, how’s it going? How much pushback are you getting from your community?

[00:17:02] Tiffany Farriss: I think Drupal is a little bit different than WordPress because we don’t have a paid plugin economy. All modules are GPL’d and they’re free. So anyone who is working on Drupal has no direct way to monetize it. And I think that has made this conversation, this recognition a little bit clearer, right?

Our entire economic base of support has been from a lot of the agencies. That’s the segment of our entire ecosystem that’s under the most pressure right now, and so if I say to them, I think we need to stop asking so much of you and we need to start asking more of the others in the ecosystem. It’s been a little bit of a recognition, like yeah, maybe that’s true.

Our ecosystem, our agency ecosystem, they give well beyond what they take from Drupal. And so I think for me, quantifying what just the general site takes from Drupal, has made it really sharp and clear that this isn’t a huge ask. And maybe the labor costs, maybe the infrastructure costs. It is time for us to be able to mature, and to recognise that more people need to be involved in supporting that.

[00:18:09] Nathan Wrigley: I know that you are not involved in the WordPress space in the same way that you are with Drupal, but I’m just wondering if, from what you’ve just said, it sounds a little bit like you have more of a bat-phone into the people who need to be on side. In the WordPress space, I feel like there may be more people who, I don’t know, they own a plugin business, and they make money in that way, but they might contribute nothing back to the community.

There’s people who turn up to events, there’s people who own hosting companies. They’re all spread out in different ways, and earning money in different ways. And so when messaging about, I guess our equivalent would be called Five For The Future, it’s very hard to know where to put that messaging, because you can’t really sum up where these people all are. They’re all over the place and there’s no one place where they gather.

But it sounds a little bit like, and I said bat phone, I hope you knew what I meant by that. It sounds like you have a line of communication which is much more easy to tap perhaps than we do on the WordPress side. If I’ve misunderstood that, please say.

[00:19:10] Tiffany Farriss: I think I do feel like we have a lot of engagement from a lot of the organisations. One of the major changes that Dries put in place back in 2014, was our contribution system. And so we know, it’s public, who is contributing to Drupal, and that’s not unique to us.

But I think the innovation is that every commit has the opportunity for an organisation as well as a sponsor. So when work is done in Drupal, we do have a lot of telemetry around who’s doing that work. So I think that’s given us insight into where some pieces of the value have been experienced over the last 25 years.

And so we’re able to recognise that. But I do think we over index on those agencies who are involved. And so have a lot of, currently we have a Drupal Certified Partner Program, where a lot of those agencies participate. And they know that they’re supporting and underwriting the infrastructure and they take a lot of pride in that.

I think the difficulty is that one, we’re not a 501 (c) (6), we’re not a trade association. So I can’t deliver benefits specifically back to that group. You know, I can’t go out and say to procurement agents, “hey, you really should drive business to these folks. These are the ones who are actually supporting and working on Drupal,” because it feels like a pay to play. And in our case, there is some payment there, but it’s really you can’t become a Drupal Certified Partner without having made the maker contributions, you know?

[00:20:32] Nathan Wrigley: Oh, so there is a sort of quid pro quo there. If you contribute, I don’t know what the specifics are there, but if you manage to get over whatever the hurdle is, you can then access something. What is the something there that you can access? Sorry, I interrupted.

[00:20:48] Tiffany Farriss: Nothing. There’s nothing you can access, right? I mean, we recognise our makers on our website as Drupal Certified Partners.

But I do think that because it’s just a wall of logos, and it isn’t actually an attestation, it’s a lot of marketing copy, right? It becomes hard for procurement to put any credibility in it. And so this is actually the big innovation that I’m working on involving the Drupal Certified Partner Program, which is largely built around those agencies into a Drupal Certification Program that encompasses our entire ecosystem and essentially sets the standard.

[00:21:21] Nathan Wrigley: Tell us a little bit more about the things that you are doing there then. Because that sounds really intriguing.

[00:21:25] Tiffany Farriss: Yeah, I think that what I recognised is that as a 501 (c) (3), one of the things I can do is I can recognise those who are being good citizens. Now we have to come up with what that standard is. And I think in open source, it’s something that you know, but maybe hasn’t been articulated.

And part of that process has been to recognise that there are three pillars of contribution that are all essential for Drupal to be successful.

First is making, those who are actually contributing code, or code adjacent activities to Drupal.

Patronage, right? Those who are actually funding the infrastructure. Funding the core release managers, the core maintainers, the security maintainers.

And then there’s also advocacy. Helping the world to understand what Drupal is and what it does, and to create the documentation, and to go out to events, and to help others learn to use it.

So those are the three pillars of success. And so what we’re doing is we’re taking that idea of the contribution credit that we’ve had for a long time, which has always recognised more than just code contributions, and explicitly breaking it into these three areas.

And then our Drupal Certified Partner Program has been about agencies. So the eligibility requirements for who we recognise were based around what agencies already were doing. And what we’re evolving that into is different kinds of certification for all the parts of our ecosystem.

So we have platforms that are specifically Drupal tuned. Our platforms as a service partners. We have shared hosts. There are cloud hosts. There are infrastructure CDNs. There are end users. There are individuals. And so that entire spectrum of who’s participating, and getting value and benefit from Drupal, I want to create the opportunity for them to become Drupal certified.

And what that means is that Drupal certification is a badge of recognition of those who are engaging with Drupal in a net neutral, or net positive way. That they’re giving back at least what they are taking from the community, or more.

I think we start to move from something that is more like a sponsored badge wall, into a public trust register, which I think is, very helpful. And I, currently on Drupal.org, you can look up any individual, or any organisation, and you can see how they contribute. But unless you’re super in the weeds, it doesn’t mean much to you.

So I think that the lever here is around procurement, and around making this a trust ledger, something that can’t be bought. But something that is understandable to a procurement officer to say, who is contributing to Drupal? What are they contributing to Drupal, so that they can make decisions. Especially if they have two different potential vendors. One who contributes and one who doesn’t.

I think this is all a conversation we can now have because of the way that Europe is leading the way with their open source strategy. You know, that they want there to be more open source used in the services that they provide. From a digital sovereignty perspective, it’s essential for them.

[00:24:18] Nathan Wrigley: Let me see if I’ve understood that correctly. So on one level, I’m just going to use the word Brussels. I hope that everybody understands what I mean when I say Brussels.

[00:24:25] Tiffany Farriss: Yeah.

[00:24:26] Nathan Wrigley: So, Brussels encapsulates the EU, the governance of the EU. Because of the posture that Brussels takes. It could, coerce is the wrong word, but let’s go with that. It could apply a certain degree of pressure to big procurement initiatives to say, look, I don’t know, we need a new website for the French Health Service or whatever. And Drupal is right in there, and we’re looking for organisations that can help us to build that Drupal infrastructure.

Given that’s the case, we are now going to go to this extra layer of what do these agencies that are competing for this contract, what is their position vis-a-vis Drupal? And if it looks good, in that you’ve contributed in the past and you have all the accreditation and what have you, you will more likely have a favourable outcome in that procurement procedure. Did I sum that up right or have I completely misunderstood?

[00:25:22] Tiffany Farriss: No, I think that’s a part of it, right? I think that Brussels has already recognised that it’s in their interests to use open source products, right, open source solutions, and has for a while. But I think procurement’s the real lever where we start to enshrine or encourage bad behaviour, right? What we were calling extractive use of open source.

So if you think of open source as just lumber that you can take and use however you want, right? If nobody is replanting the trees, cutting it down, sawing the boards, then it doesn’t exist anymore, right?

And also on the government side, when we talk about public money, public code. It’s important that you actually get the benefits of it. So it wasn’t just a starter kit that you take and then you own, right? We know that good use of open source, whether it is WordPress or Drupal or TYPO3, right? You want to minimise the amount of code that you own. That’s the advantage. That’s how we all experience the network effects.

So you need to have some behaviours, and I think that procurement officers don’t care, don’t need to know, about what open source is or our specific projects. But what they need to know is that when they are procuring any project, or any solution, that has open source as a component of it. That open source isn’t going to end up being code that they own down the road. They have the right to use it, extend it forever, and they know that somebody can’t turn it off on them, which is I think a very important.

[00:26:48] Nathan Wrigley: Oh, big thing at the minute.

[00:26:49] Tiffany Farriss: Big thing right now, especially in light of the 2018 USA Cloud Act, right? So that’s really been the driving impetus around digital sovereignty. But when we think about good open source use, responsible open source use, there are some behaviours that regardless of project we know are true.

And it is that when you write a new plugin or module, you release it, right? So others can use it so that you’re sharing the maintenance burden moving forward. If you don’t, then you own that and you’re going to maintain those lines of code yourself.

Two, if you patch something, you want to release that patch upstream because otherwise you may have ended up inadvertently forking it. Or in some cases the government pays for the same patch over and over and over again, right? If there are economic benefit to using open source, you need to know that whatever vendor you’re using is contributing the patches back upstream so that you continue to stay, anything that’s non-confidential, obviously, but so that you can stay current and up to date, right? Woe for those who were not current and up to date last week with PHP, right? It made that problem all the more difficult.

So when I think about making it open source use at the government level very sustainable, there’s really three policies I think that they need to implement to help really get the benefits of open source, right?

One is that the patches are contributed upstream if they’re non-confidential within 30 days.

Two, I think that they need to understand that there is a cost to their use. And so creating whether it’s 2% or 5%, creating a line item in every project that uses open source of any flavour, for the delivery of the project, that there is a standard percentage that is contributed back upstream to that open source project, to offset that use. Because right now, the agencies and the companies that are responsible open source users, they bear their contributions and their participation in open source as a tax. So it becomes baked into their hourly rates. Which then as economic conditions get constrained, it becomes a disadvantage to do the right thing for open source.

So I’m very worried about that. But if it is instead a flat line item that all who are responding to a tender have to meet, then the virtuous behaviour that continues the virtuous cycle of open source isn’t a burden on any one firm.

And then the third piece is you want to know, are they a contributor to that open source project? And so this speaks right to Dries’ maker taker dilemma, which I’ve extended to the maker taker faker dilemma. Which is obviously, I think makers and takers are pretty clear, right? You either are someone who’s making and contributing into your open source project. And takers being the ones who are like, thanks for the wood little elves who magically made it in the woods. Great. This is all good. Good luck with that forest.

I think that the fakers are, in some ways, much more dangerous, because they have this, it’s like open source washing. The fakers are the ones who maybe sponsored a coffee one time at an event, but they’re not really giving things back. So they’ve got a badge. Procurement, they can say, oh look, I’m a sponsor.

I appreciate anyone who sponsors at any level. But I think that when you’re talking about competing on a public procurement, there is a very important difference between someone who maintains modules, contributes to the security team, and someone who sponsors a coffee. And I think that it’s on us as open source projects to make that clearer.

So the Drupal certification is our attempt to really become a very trusted public ledger about who’s contributing what, and why it matters to folks who aren’t in our community. I think today, where we stand and where we’re starting, it is a very transparent ledger. But there’s a difference between transparency and clarity. And I think if we want Brussels, and other governments and procurement, officers to be able to differentiate and give a preference to those who are good open source citizens, if you will, those who are actually involved in the projects that they’re using and implementing, for these very important public projects, I think it’s on us to make that easier. So that’s something I’ll be focused on next year.

[00:31:02] Nathan Wrigley: It sounds to me like you could kind of sum this up in the word clarity. Everybody needs clarity. Those people who are procuring things need to be clear on what they’re going to get. Those people who are delivering things need to be clear on what they’re going to do. And the notoriety, for want of a better word that they’re going to get from that.

It also seems like you are in a very interesting role, where you are like this go-between between all the people doing the work on Drupal, and the people who are procuring, and I’m sure that’s really fascinating work. Like what is the proclivity of, let’s say for example, USA or Canada. What are the requirements that they have around, I don’t know, 20% of all public software needs to be open source or something like that. That must be utterly fascinating work. You’re right at the chalk face of all this. Wow, that’s so interesting.

[00:31:52] Tiffany Farriss: It’s absolute candy to my brain. Like I just, I can’t tell you how much I really am enjoying being part of those conversations. And I never would’ve thought that I would’ve been invited to speak at a plenary at the United Nations, and yet I was. And that blog post that you mentioned, that’s on palantir.net, actually those are remarks I gave to the German Consulate, in New York, right?

It all comes from this conversation we’re all just starting to have about what does it mean to sustainably and responsibly use open source as we look ahead to the next 25 years, next a hundred years.

There was a board member I had served with in Drupal a long time ago, Donna Benjamin, and this was, I don’t know, maybe almost 20 years ago now. And she always used to say, what’s our a hundred year plan? And at the time, I was taken back. I’m like, uh, I can’t even with that.

And now as we fast forward to where we are today, I actually can start to see that. And it’s about understanding that nobody intends and sets out to be a taker, right? You can’t pay for things that you don’t know are there, or things you don’t know are already happening. And you can’t meet expectations that aren’t communicated.

So this is the opportunity for open source projects to say, this is what it takes for us today. This is what it takes for us where we want to go. And here’s your share of it. How do we make it easy, and expected that everyone does a little, so we’re not resting on a few who have to do a lot?

[00:33:22] Nathan Wrigley: This is going to sound like a really poor summation of it, but it feels like open source, up until this point, you know, the analogy, carrot and stick, you know.

[00:33:30] Tiffany Farriss: Yes.

[00:33:30] Nathan Wrigley: So the carrot is, we hope that you’ll come along and, you know, follow the lead and do all of the right things. Where a stick is more, if you don’t do the right thing, there’ll be a punishment for that. It feels like open source for the last 20, 25 years, there’s been more carrot than stick. And although it’s incorrect to summarise this as stick, is there a little bit of stick here? Are we trying to cast a, let’s say, a glowing light on those that do everything well, who are the makers? You know, we want to raise your profile, shout from the rooftops that you did things well.

Conversely, is there a bit of okay, those that don’t, we are going to shame. Or is it more a case of we just leave you alone? You just don’t get a mention. You don’t get to be part of the community in quite the same way.

[00:34:15] Tiffany Farriss: Coming back to that frame as open source stewardship as a utility. Nobody considers it a donation to their electric company. They pay the bill because the lights matter. And I think it’s about resetting this frame. We’ve never sent utility bills to people. We’ve never even exposed what that looks like, or maybe we don’t know ourselves. Based on projects, Drupal certainly didn’t until I started this work.

So I think that there’s this expectation that we’re going to continue as we always have on this balance of goodwill and volunteerism. But as last week showed, PHP Foundation, which WordPress is very involved in, Drupal as well, has one full-time employee. And 70% of the web runs on it. So it’s something that we have taken for granted for too long. And I think that this moment is brokered by the blessing and the curse that is AI.

[00:35:07] Nathan Wrigley: I wonder if the wider issue at stake really is notifying the general public. Letting all of humanity know that when you are picking up your phone and using that app, and it’s connecting with that service over here to enable you to, I don’t know, book a restaurant or get a taxi. There’s probably some layer of free software around there.

And would you do anything for free? Is that, I’m not asking you that question by the way. I’m just saying, you know, dear app user, would you do things for free in the same way that you’re expecting this software to be free?

And I think that argument’s fairly persuasive, but it’s not something that has leaked out into the public. You know, the coverage of the PHP thing, nobody knew. The guy that came on the BBC, who was the BBC correspondent, he’d never heard of PHP. And he’s the cybersecurity correspondent for the BBC had never heard of PHP.

And so getting it out into the vernacular, getting it out into the mainstream, that all of this stuff that you’ve taken for granted, we all need to pay a little bit. I wonder if that’s an interesting. It’s like the stick that I was talking about earlier. If the public are more aware whether they will be able to pressure things a little bit more. I don’t know. I’m not sure there’s any mileage in that, in all honesty, but it’d be an interesting experiment to run.

[00:36:20] Tiffany Farriss: I think we’re about to see that experiment, right? So the Cyber Resilience Act in Europe is requiring SBOMs, which are Service Bill Of Materials to be disclosed. And I think that once SBOMs are readily available, it may become clearer, at least to decision makers, exactly how much open source software is in the solutions that you’re providing. And I really am curious to see how it evolves when you do have these manufacturers or organisations, whether they’re service organisations or actual manufacturers, starting to become liable for the risks in your security chain.

[00:36:56] Nathan Wrigley: Right.

[00:36:56] Tiffany Farriss: As I look at this, I look at it as a supply chain issue. And so we’ve now exposed that there are weaknesses in our supply chain. So the argument isn’t, it’s really less of a shaming. It’s saying hey, this is a risk management approach. And I was looking at it as a design flaw. That open source was an idea around writing software. It wasn’t actually envisioned at any time that this was going to run the world. It was just, this is a good idea to do good way to do things. Let’s try it.

But now that we understand that open source does run everything, we need to come back and treat this as a design problem and say, how do we align the incentives? What needs to be true?

I appreciate the work that’s going on in Europe right now, and I think that becomes a bit of the stick. It’s not coming from us. It’s saying, actually if you sell a product that’s based on open source, and that open source has a security issue, you are liable. You’re the manufacturer. See, as an open source steward, the Drupal Association does not have liability. We have responsibilities to disclose, which we have done, all the way back through 2007.

Drupal is a CNA, right? We’re a numbering authority for CVEs. We’ve had a very mature security practise for many years, and we will continue to do so, and meet our CRA disclosure requirements. But those who have blindly been using open source in products or in services for others, they’re now manufacturers. And come December of next year, they’re really going to start to understand how liable they’ve become for any issues in the supply chain.

[00:38:34] Nathan Wrigley: There’s something quite virtuous about that. In that it’s allowing the open source posture to carry on in the same way that it always has. Shifting the responsibility over to the governments in a way. You know, that they’ll create the legislation, which means that if you fall foul of this, that and the other thing, you will now be responsible. And if you are responsible, it’s it’s the same reason we have car insurance and buildings insurance. You need to know what your position is going to be in the event of a fire or a crash. You just have to know it. Because if your business were to go under because you weren’t thinking about those things, that would just be negligence. And so that’s such an interesting way of framing it. I like that a lot.

I also like your definition there. You described the internet over, you know, the last 20 years and how nobody knew that it was going to work this way, and now here we are. And, I guess it would be a bit like, I don’t know, going to a lemonade stand or something like that and getting a really cheap lemonade from a child who’d done it because it was a nice thing to do for the community. Let’s sell cheap lemonade.

But then turning up with 12,000 people and saying, we would like 12,000 cheap lemonades, please. Immediately. No, that’s not available. That’s not the way it was designed. And that feels to have certain overlaps here.

Nobody knew that open source was going to take over the world. Now it has. It’s chronically underfunded. There will be a collapse at some point if companies and businesses are allowed to just have a taker mentality. So you are putting things in place to make sure that is checked. And I think that’s really interesting.

[00:40:06] Tiffany Farriss: It goes from this idea that we passively consume whatever we get. Whether it’s a website or a phone. To this idea of having some sort of active upstream strategy. And again, I don’t think that many of us had the opportunity to understand what software was running on our phone. You didn’t know, right? You can’t mitigate a risk that you don’t know is there. I do think it is unreasonable to think that we don’t know the risk is there now, especially after last week.

[00:40:33] Nathan Wrigley: There’s just no bit of me which would walk into a store and pick things up and just wander out and say. There it is. I’m going to have it because it’s there for me to take. And yet, broadly speaking, I think it’s fair to say that the vast majority of the people in the world consuming things on the internet have exactly that position.

You switch on the device, the device itself is probably working on, in many cases, open source software. And then I’m just going to consume all the things that are there, you know, it’s all free. You know, it might not be free, it might be sponsored by advertising or what have you know, we all have opinions on that.

But we have got ourselves into this position where we completely pick up the devices and think, all free, from top to bottom, free. And we need to change that mentality. So, going back to what I said earlier, getting the message out to the population at large, I don’t know how you do that.

[00:41:25] Tiffany Farriss: I’m a big believer in what Buckminster Fuller called the trim tabs, right? I don’t set out to turn the ship. I turn the little piece, the trim tab that turns the rudder, and that turns the ship. And I think that whether we’re talking about compliance, or we’re talking about OSBOs, and helping compliance within organisations, I think that’s how we turn the ship, right?

We need to create an economic model that really does protect the supply chain. This is a consumer problem. It is a consumer risk. And I think that’s exactly what many governments were set up to deal with.

And so I think they do have the opportunity that the governments, whether it’s the EU or the US or the Canadian government, they spend so much money. And if they change the way that they spend money, and they change the way that they look at open source and how they understand it. And to be a responsible open source consumer, who’s asking for, are we giving back? Are we minimising our footprint? Are we restoring services that we use? Are we treating it like the utility that it is? That alone makes such a huge difference, such a huge difference.

And helps us to move away from this idea of licence only open source economics. Which is essentially that idea that I’m just going to take it because the cost of code go to zero over time, right? That’s not it alone, right?

We expect that when someone finds an issue, especially an issue that can cause remote execution, right? That they’re going to tell us about it. That they’re going to fix it. And that we’re going to be able to have access to that fix. And that’s where we move beyond this idea that the licence itself is free, and it will be free forever.

Those services that is about the human capital, and the human technology that make those things possible. And they are not free, they have never been free. You just haven’t known who was picking up the bill on your behalf.

[00:43:17] Nathan Wrigley: What kind of timeframe? This is going to be my last question by the way. What kind of timeframe do you put on this. How far into the future are you gazing? I’m guessing the answer is it’ll never be complete, this work. But how far into the future are you hoping to get so that you can look in the rear view mirror and say, yeah, we’ve achieved most of what we wanted to do there.

[00:43:37] Tiffany Farriss: Because we’re kind of on forefront here in having these conversations, and we’re certainly not alone. Every one of the open source foundations is having some version of this conversation, or some approach that they’re trying, to make sure that they have the base of support that is commensurate to the folks that they serve, right?

I really am approaching this as a pilot for the next six months, and seeing can we, as we broaden and understand different segments of our ecosystem, and the ways in which they can contribute that align with their interests, right? I’m always looking for the triple win. The win for Drupal. The win for the end agency. And the win for the public, right? Because I am a public facing charity, right? I want all of those things to be true.

And I’ll be experimenting and having conversations with infrastructure providers, with our shared hosting platforms, with cloud providers to say, okay, what does it make sense for you to contribute? What does it mean for you to be a good Drupal citizen, and to give back in a way that feels appropriate to the amount of value that you’re generating from this?

I don’t think that any system can be designed where it requires a hundred percent good behaviour, or a hundred percent participation. It’s going to be a process of iteration and learning as fast as I can. Making sure that we’re being transparent about it, and approaching it from this cost expensing perspective. I’m not looking to maximise profit or other things. I’m a not-for-profit, and I care about resources, and money, and attention going to Drupal. If it comes to the DA, through the DA or directly into the Drupal community, all of those states are a win.

So it creates a great table for conversations with different kinds of players and providers who haven’t engaged. But at least now I can go to them and say, hey, this is what you’re already consuming from our ecosystem. And here’s a pretty good back a napkin for what I think you’re making from it. If we didn’t exist, what would you do? How would you do the security pieces? How would you do the packaging pieces?

And it’s okay if one of the answers in those conversations is, oh, wow, I didn’t realise we were using so much. We can dial that back. That’s perfectly valid. I want to make sure that open source and that Drupal is there for whoever wants it in as secure and as innovative a way as possible.

And so whether you reduce how often you ping my packaging server or you are like, yes, I need this, this is part of my critical infrastructure, and you fund it as if it is a utility part of your infrastructure. Both of those are valid answers to me.

[00:46:03] Nathan Wrigley: There’s so many people in the WordPress space who will resonate with everything that you are doing here. I said I was going to ask no more questions. I have one more. Do you have lines of communication open with, for example, WordPress and maybe PHP? Are you doing this very much in isolation, even though there may be overlaps? Do you have that? Would you welcome that? Would you like to have introductions to people? And if so how can people communicate that to you?

[00:46:29] Tiffany Farriss: I’m always happy to talk to everyone. I will say Drupal and Joomla, WordPress and TYPO3, we have the Open Web Alliance, and so we do talk every month. And we’ve just invited PHP to be a part of that obviously. I have Slack access to all of those folks and we do talk regularly.

In addition, there’s just a broader open source community of leaders. There was the Open Source Congress, that happened in September. I really appreciate being able to talk to my colleagues whether it’s RubyCon for the Apache Foundation, which actually put on this year’s Open Source Congress and did a fantastic job. All of us being able to talk together.

I can say to the CEO of Python, I can say, oh you know, hey what lawyer are you using right now? Or what software did you use for your community elections? I’m looking for some new ones, right? And they have tonnes of ideas and then I’m able to say, oh, here’s how we are doing this, or here’s how we’re doing that. And I just think that level of collaboration and conversation, has been incredible. Right. Rust Foundation, UN Open Source Week and the EU Open Source Week, and Open Source Congress. Those conversations among colleagues have been fantastic.

Any new colleagues I’m happy to talk to as well. You can reach me on many different Slacks, whether it’s the Open Source Congress Slack, or the Alpha Omega Project for Drupal. I’m in Drupal Slack. You can reach me in all of those places, is @Farriss. That’s FARRISS.

[00:47:51] Nathan Wrigley: Nice. Thank you so much. It really is fascinating work. I would really be genuinely curious to watch what you are doing over the the next six months. Where you end up. How the project is received at both ends.

[00:48:04] Tiffany Farriss: Me too.

[00:48:04] Nathan Wrigley: To see what the pushback is like. I would really love to keep a track of what’s going on. But for now, best of luck. I hope that it all pans out in the way you’re anticipating. So, Tiffany Farriss, thank you so much for making the time to chat to me today.

[00:48:16] Tiffany Farriss: Nathan, thank you for having me.

On the podcast today we have Tiffany Farriss.

Tiffany has spent the last 30 years working in web design, development, and creation, and she’s been deeply embedded in the Drupal community for the past two decades. She’s currently the interim CEO of the Drupal Association, and is the organisation’s longest-serving board member after Drupal’s founder, Dries Buytaert.

This episode is a bit of a departure, as we usually focus squarely on WordPress. But Tiffany brings a wealth of experience from the broader PHP family, and this conversation explores the similarities and differences between the WordPress and Drupal ecosystems, particularly when it comes to infrastructure, and the sustainability of open source projects.

Tiffany explains the ‘maker-taker’ problem and the challenges of sustaining free software platforms that underpin millions of sites across the web. She shares her insights on the real costs behind open source stewardship, drawing from both data and experience, and discusses how tiny groups have shouldered the burden for everyone, and why that might no longer be viable.

The discussion explores the Drupal Certified Partner program, the push towards quantifying contributions, and how the open source community can improve transparency and sustainability. Tiffany also touches on the role of public sector procurement in shaping the future of open source, the impact of new regulations, and how community-driven recognition could incentivise more organisations to ‘buy their round of beers’ for the ecosystem.

If you’re interested in the sustainability of open source, the evolution of governance models, and how WordPress professionals can learn from the broader PHP landscape, this episode is for you.

Useful links

Tiffany on Drupal.org

Drupal Association

 Dries Buytaert

Palantir.net

Drupal.org

DrupalCon

Drupal Events

Acquia

Five for the Future

Drupal Certified Partner Program

2018 USA Cloud Act

 Cyber Resilience Act

Joomla

TYPO3

Open Web Alliance

Open Source Congress

Apache Foundation

UN Open Source Week

EU Open Source Week

 Alpha Omega Project for Drupal

💾

#240 – Martin Schmidt on Building Partnerships Between WordPress Product Makers and Hosting Companies

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, building partnerships between WordPress product makers and hosting companies.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.

So on the podcast today we have Martin Schmidt.

Martin has been deeply involved in the WordPress and hosting industries since 2005 when he created his first WordPress travel blog while living in New Zealand. Over the years, he’s developed websites for small businesses, spent 13 years with IONOS in various management and strategy roles, and built partnerships at Wix, and a German SaaS company.

Most recently, Martin has focused on connecting WordPress plugin companies with web hosts, helping both sides unlock growth through smarter partnerships.

Today, the conversation focused on the often overlooked world of partnerships between plugin developers and hosting companies. Martin shares insights from his two decades of experience on why hosting providers are the perfect allies for WordPress product makers looking to grow, given their established relationships and marketing channels to large customer bases.

We talk about the curious fact that many plugin builders put enormous effort into their products, but stumble when it comes to sales, marketing, and building the business relationships necessary for broader success.

Martin discusses what hosting companies are actually looking for in a partnership, the technical and marketing preparations plugin makers should have ready, and why empathy and preparation make all the difference when trying to connect with busy product managers.

If you’re a developer, freelancer, or agency owner interested in taking your WordPress product to the next level, or if you want a candid look at how partnerships really work in the open source ecosystem, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Martin Schmidt.

I am joined on the podcast by Martin Schmidt. Hello Martin.

[00:03:14] Martin Schmidt: Hi, Nathan. Great to be here.

[00:03:16] Nathan Wrigley: Yeah, thank you. Martin and I do not know one another, so this is our first call, but we were joined together, on maybe LinkedIn. I’m not entirely sure.

[00:03:23] Martin Schmidt: I was LinkedIn. Yeah. Yeah.

[00:03:25] Nathan Wrigley: Probably LinkedIn, by Nicole, so thank you to Nicole for doing that, really appreciate the linking together there. And we’re going to have a conversation today about, I suppose the word to describe it would be partnerships. How to partner with various different entities, possibly hosting companies are going to come up and things like that, so.

Before we begin that conversation, Martin are you able to just give us your little bio? Tell us a little bit about who you are and what you’ve done in the hosting partnership WordPress space, whatever you think fits best.

[00:03:55] Martin Schmidt: Yes, absolutely. I’m from Germany. I lived down south in Karlsruhe. Originally from the Cologne area. Started working with WordPress actually in I think 2005, something like that. When I was moving to New Zealand and started studying in New Zealand. That’s when I spun up my first WordPress site as a travel blog. And this was my first contact with WordPress. So I think, yeah, one of the, not one of the first users, but one of the very early.

[00:04:20] Nathan Wrigley: Fairly early, yeah, pretty early.

[00:04:22] Martin Schmidt: Very early. So that’s when you still had to like download WordPress and upload it via FTP, and there was no like auto update in the WordPress admin, and stuff like that. So one of the very early users and.

Yeah, around that time, that’s also how I got in touch with like the whole hosting industry. I was a web developer myself, started in high school developing websites for small businesses. Built them for people here in Germany and then also in New Zealand while I was studying over there.

And when I got back from New Zealand, I started applying for jobs. And one was with Google, the other one was with Ionos. And Ionos answered I think within a week, and I’m still waiting for the answer from Google till today. So, they never really got back to me, but yeah, it’s somewhere in the mail, yeah.

But luckily the guys from Ionos got back to me and I think a week later I had a phone interview. Another four days later an interview in Karlsruhe. And then I started, I think two weeks later. Already started there like end of October with my first job as a product manager at Ionos.

And then spent 13 years at Ionos in various roles, in product management and the last five years in strategy. And from there I got the chance to move on to Wix. Worked for Wix.com in Germany. There was, during the COVID pandemic, I moved employers and started to work for Wix, and spent two years there building partnerships in, Europe.

Actually also put them in touch with a company called Sevdesk, which is a German accounting company, similar to Zero or QuickBooks Online. And couple of months later the CEO asked me if I was interested in joining their side, after they had raised some money and built partnerships from their side. I kept him waiting a little bit, but then after a while I decided, that’s interesting to join a German SaaS company. Something different than hosting, and online presence.

So yeah, I spent the next two years building the ecosystem around the SaaS software, like all the software that integrates with the accounting product basically.

Then end of 24, I got a call from my former boss from Ionos, who had just moved to hosting.com and became the CRO, and they also wanted to do partnerships. So, yeah, had a chat with him and with the CEO and started there in February 2025, and started building partnerships for hosting.com.

And, the main focus was really on building partnerships with WordPress companies. Just after Cloudfest, we launched the partnership with WP Rocket. Started to build quite a few more partnerships, or that were in the making. And by the end of the year, which was interesting to me, I had a lot of those WordPress plugin companies that I reached out to telling me, look, this is super interesting. We want to work with hosting companies.

We’re really glad to be working with you. We would also love to work with a lot of more hosting companies, but honestly we don’t really know where to start, and how to do this. And they really got me thinking. And then over New Years, and you know when you like, get some time to maybe reflect on the year and stuff that’s happening, this was like, it, really hit me. It’s like, well there’s so much interest of companies wanting to partner with web hosts.

And I’ve sat on the other side for some 20 years, like people pitching to me, like explaining me why their product is going to be the next big thing for me in the hosting company. And you start to see patterns of like things that people do good, and maybe things that people don’t do as well when like trying to pitch to you as a hosting company.

And I saw all this demand from these WordPress plugin companies and I was like, hey, maybe this is finally the idea of starting my own business. Like something I wanted to do for the last five years, but I never really had the idea of like what to do? Or not the idea that was convincing enough for myself to give up my corporate job.

And, once you got a house and family, I mean, it becomes a bit more difficult to just jump into the cold water, right? I guess a lot of people can relate to that. But this time it was different. I felt like this could really be something. So I started reaching out to more people in my network, and ask them, hey, I’m thinking about doing like this sort of consulting advisory thing. Do you think this is interesting? And I got a lot of positive feedback, way more than I had anticipated.

So I thought, okay, if I’m not doing this now, I will never do it. I will never try and do it. So yeah, I decided to go independent and officially started in May. And that’s what I’m doing now, like helping tech companies who want to partner with web hosts to find a way to do it.

And I always tell people that are interested in, you can do it by yourself, right? You can find it all out yourself. It’s probably going to take you like three to four years to figure out the right model, and make all the connections. Build the trust with the hosting companies. Find out the right business model. The right support model, like the co-marketing activities, all the things you need to do. Or if you don’t want to wait for four years, you can work with me and I help you take a shortcut.

And the goal is by month six that you have someone in your organisation who can take care of partnerships, and just run this by yourself. But you don’t make all of those mistakes, and all of those extra investments that don’t turn into anything.

My pitch to my customers is like, I’m helping you cut down the time to market. I’m telling you what works and what doesn’t work, and what makes a good pitch.

[00:09:49] Nathan Wrigley: Yeah, this is genuinely really interesting to me, and we’ll get into that a little bit later. But I have a different angle to you, but probably we’ll end up at exactly the same place.

I’ve been podcasting in the WordPress space for a decade. So 2016, something like that, I started. And, if you do podcasting often enough, your voice is heard, and people have this sort of expectation, if you send an email to me with a product that you’ve just launched, I will somehow have a silver bullet for making you successful.

And first thing to say is, I basically don’t. You know, I can put you on a podcast episode, but that really is the limits of what I can do.

But also what’s quite fascinating, and I honestly genuinely, I probably get about 30 or 40 of these emails a week. And the bit that stands out for me is how unprepared, let’s go for that word, how poorly prepared the email that I receive is.

So in many cases over the last couple of years, it’s clearly been written by an AI. There hasn’t been a lot of due diligence about who I am, so it kind of feels like this really, really cold call. I somehow got on an email list somehow. And it comes, you know, with all of the usual caveats. The first paragraph is telling me what I do, and I already know what I do. So like there was an AI in there somewhere.

But also it feels like they’ve got a product. Quite often I’ll go and look at the product and I think to myself, boy, that’s so good. Look at what they’ve done. Like they’ve built a plugin and it’s fulfilling a real need.

Unfortunately, I can’t really help them except put them on a podcast, but it occurs to me if only they could connect with all the right people, have the right language, know how to pitch themselves, know how their website should look so that it speaks to people that drop into it.

What I’m basically trying to build up a picture is of is that there’s loads of people out there who are building things, but clearly the building of it is the part that they’ve been interested in. And as soon as it’s built, they then have this moment of, oh, now what do I do with it? You know? And they don’t have that marketing expertise, and so they’re kind of looking around trying podcasters and what have you. And it feels like you are trying to step into that gap a little bit.

But instead of it being a podcast, you are trying to hook them up to what are the big players in the WordPress space? The people with deep pockets. The people who have reliable income month over month. And that’s the hosting companies. Have I summarised that correctly? Is that your experience as well? You get people that have got a thing, but don’t really know how to move on from the I’ve built the thing, to now I need to sell the thing.

[00:12:37] Martin Schmidt: Yes. So I think you’re spot on. And I would add there’s probably, I would say two groups. There’s the one which is maybe the builder who doesn’t know marketing, right? And we had these people before AI that were building fantastic products. But they just don’t know marketing because they’re fantastic builders. They’re tech people, but they’re missing that marketing piece.

And the one thing they don’t hire a marketing person who does it for them. I think that’s always a shame. You see this fantastic product, someone like driving a product with their passion. They’re really solving a pain point, but they just don’t understand how to sell it. Because to them it’s all clear, it’s all obvious, but you do need to translate it to people in your target audience.

So I think this is one group, and I see that also a lot with WordPress plugin companies. It feels like, coming from the hosting space, where all of the big companies are so good at marketing. Looking at WordPress companies, I feel like this is really something that they are somewhat missing.

I think the most successful WordPress plugin companies, I think that’s probably the ones that have understood that next to building fantastic product, and also needs fantastic marketing. But I think this is really the one group.

And the other one is, I would call them like lazy salespeople. They’re just sending out like sales messages. And we had them way before AI, just sending out without doing any research at all. You get messages and you look at them or you look at the product, it’s like, there’s no fit at all. I’m selling to small businesses, and you pitching me a product for enterprise customers. Like, why? You are just wasting time, right?

If your goal is to work with a company to potentially sell to hundred, thousands, or millions of customers, and that’s going to be a deal worth hundred thousands or millions of dollars, you should invest maybe an hour, half an hour, of research and just see if there’s any fit at all right. And then if you take the time to go in a meeting with me and pitch your product, do a little bit of research to just make it fit. Just this tiny bit of research will make you stand out amongst the crowd like completely.

[00:14:41] Nathan Wrigley: It feels to me in the first case as if, timing’s not really the right word, but there’s a component of timing in here. And what I’m meaning by that is, what I’m feeling is that a lot of people have spent all of their time building the thing. So that might be time, but it might be money, whatever the thing that you’ve got going on in your business.

But at no point during the time from conception, idea to completed product have they said to themselves, okay, at some point we’re going to have to market this. We’re going to have to think about it.

So maybe, and I don’t know if this is part of the sort of wisdom that you have, but it feels like maybe halfway through that process of build to complete build, you need to put the brakes on and say, okay, now we’re halfway through, let’s work in two channels now. Let’s do the, finish the build, but also at the same time, let’s do the marketing.

So I don’t know if there’s anything in there, like just put on the brakes before you finish, have some resources, have some ideas of contacts, have some marketing, have a website and all of that kind of stuff done. So that when you finish, it’s all ready to roll.

[00:15:43] Martin Schmidt: Yes. That’s definitely it. I don’t know if you have to put on the brakes, but I think it’s like, at least you as the CEO, you have to like work on two tracks. There’s the guys building the product, but then there’s also the marketing piece of it, right?

And you can have the most fantastic product if you’re not telling the story, if you’re not letting the world know. How are people going to find you, right? I think we see, I saw a stat on LinkedIn recently that there’s like a thousand plugins published on the repository every week. It’s going to be so crowded. You need to do something to stand out and to be found.

And I think that’s also with web hosts and every tech company, you can have the most amazing product, but if you’re not found, if the target audience doesn’t know about you, nobody will use your product. And you’re going to be the only user of your own product.

I think in the end, you need to master marketing to be successful with your business. And it’s not just about the best product. And, I think that’s the important message here. You don’t need to know marketing yourself. Just hire someone. There’s so many people specialise in marketing. Just get someone on board who knows marketing and who understands a little bit of tech to get why your product is so special, and who’s able to translate that into a customer pain point, and figure out how to sell it. that’s really it.

[00:16:58] Nathan Wrigley: So we’ve done podcast episodes on this podcast before where we’ve talked about partnerships in a different way. We’ve talked about partnerships in terms of plugin Company A joining with plugin Company B, because they’ve got similar enough products that they kind of overlap, and they can help each other out and mutually market and do marketing campaigns together and things like that.

But that’s not what we’re talking about here. We’re talking specifically about going to hosting companies. So I guess the first question is, why go to hosting companies? What is it that they bring? I suppose the obvious answer is they’ve got bajillions of customers. In many cases, you know, some of the big hosts, if you can forge some sort of relationship with them, goodness knows, you know, maybe they literally have millions of customers. But why have you made hosting companies the bit of the half of this jigsaw puzzle?

[00:17:45] Martin Schmidt: Yes. beside me coming from hosting and knowing hosting, which was kind of like, make it a bit easy to decide for hosters. But I think they also play an important role. In the end, if a small business wants to run a website, they need to host it somewhere. They decide for hosting company. They get their WordPress site spun up. And then, that’s where usually in the next step you would go with like certain plugins. Like for SEO, performance, backup, security, translations, whatever your use case is, right?

As you mentioned, the hosting company is the one that has all of the relationships with the customers. And unlike the WordPress companies, who are not allowed by the repository rules to directly market to their customers via email and things like that, they can only use popups inside the WordPress admin.

One thing that the host is free to do, they can call the customers, they can send text messages, they can send them emails. They can do all of the up and cross sell marketing to their customers. And I think that’s one advantage that the hoster has that they can bring to the table, beside all of these customer relationships, right? They can really do the full blown marketing to those free users, to push a premium version of the plugin.

[00:18:59] Nathan Wrigley: Okay. So it’s not just visibility within the platform of, I don’t know, you’re at the point of it installing a plugin because you’ve got a brand new WordPress website. And look, here’s a bunch of partners that we’ve got, you may be interested in those.

That’s one piece of it. But there’s also this sort of marketing side. Presumably just like every company on earth, web hosting companies are as keen to keep front of mind as any other company. So if they can come up with a good, and I’m doing air quotes, excuse to send out an email, they’ll do that. And why not send out an email because we’ve onboarded a new partner and, you know, have you thought about doing this with your website? It turns out we’ve got a partnership with this particular plugin company.

I’m guessing there that the ability to send out emails is something, you know, to keep front of mind is something that the web host would want to do. But what’s in it for the web host? Like if I was a plugin company coming to a web host, I would want to have in my mind, okay, these are the kind of things I know they’re looking for. What are they, what do the web hosts want in return?

[00:19:55] Martin Schmidt: Yeah. So a lot of web host will tell you, hey, I want new customers, and that’s what I usually tell the web hosts. This is something you can’t expect from the WordPress plugin company. Because they are like in the later stage of that decision process. So the customer decides for the plugin a lot later than they decide for the host. So it’s not fair to ask the plugin company to bring in new customers to the web host.

But what they can do and what the WordPress plugin company can help with is, A, make the product a lot more attractive. They’re web hosts that sell hosting bundled in with plugins like WP Rocket. So the product itself is more attractive from the get go.

And if you don’t bundle it in the start, you can also help solve certain customer pains that make the customer more happy, therefore more sticky, right? So you prevent churn. As a host, you reach like a hundred thousand, 200,000 customers. You really need to work hard that your new customer growth isn’t eaten up all by churn. Making your customers sticky and drive up the revenue per customer, that’s in the interest of the web host, right? And, with a certain size, increasing that revenue per customer also becomes very important and interesting for the web host.

So I think that’s where the plugin company can come in and help the web host. They won’t just partner with any plugin. The plugin needs to solve a certain pain point for the customer. So this could be performance, this could be SEO, this could be accessibility. So these are challenges that the customers of the web host are actually faced with. And the plugin is simply a solution to that pain point.

So the hoster has an answer to that question of their customer. They’re in the role of the trusted advisor to their customers. And if the customer says, look, I’m running a website on your servers. I need to now be in compliance with the accessibility requirements in my country, or I need to do certain things. Then there’s the answer. Let’s use WP Rocket for performance. Here’s a partnership that we have with them, right? And that’s where the plugin company can come in and help the host.

Beyond that, obviously joint co-marketing will also help the hoster. And obviously if you talk like Ionos, GoDaddy or Newfold, I mean they’re massive, like they have millions of customers. So probably what a plugin company can bring to help them in co-marketing is not going to make a huge impact. There’s hundreds of hosters with hundred thousands of customers. For them working with one of those plugin companies can still be very interesting in doing like joint co-marketing, and getting the word out.

[00:22:32] Nathan Wrigley: That’s interesting. In the back of my head, when we were talking until just now, for some reason I was thinking about all the big hosts. You know, the ones that you’ve all heard of with the millions of customers. But of course that’s not the case, is it? There are thousands of smaller hosts.

[00:22:47] Martin Schmidt: Yes.

[00:22:48] Nathan Wrigley: Who may be more amenable to this kind of thing because, well, Idon’t know, they just don’t have that sort of scale that they need to worry about. And, you know, they’re looking for opportunities because they themselves are looking to grow in different ways that perhaps the other big hosts don’t have to think about quite so much.

Okay. So that’s interesting. So, you know, if it doesn’t fit one hosting company and you get a silent wall from all the big ones, that doesn’t mean you’re out of the game. It may be that the smaller hosts with different staff, and a different approach, and different geography and things like that, they may be more amenable to that.

[00:23:21] Martin Schmidt: Yes, absolutely. And I will always tell my clients, I know that GoDaddy, Ionos and Newfold look very interesting because their publications, that they have millions of customers, but you don’t want to start with them. It’s going to take you three or four years to get a deal done if at all. If you start with them, I mean you’re going to give up frustrated halfway through probably.

So start with the smaller guys. They’re more approachable, right? They may be less busy. You mentioned that you get like 30 emails a week. That’s what the everyday of a product manager at an Ionos or GoDaddy looks like as well. They get pitches all the time. Getting some air time with them is nearly impossible.

Start with the smaller guys and they’re going to be a lot more open to discuss with you. And start some smaller partnerships. Work through the teething problems of partnerships with bigger companies, right? Build some track record. And once you’ve established a track record, you can work your way up, right? Every hoster has a competitor that’s bigger and one that’s smaller. Once the smaller competitor starts doing something, they will notice, and they will look like, why are these guys partnering with plugin company XYZ? Should we be doing the same? So you kind of like work your way up to the bigger guys and the bigger guys, right?

[00:24:34] Nathan Wrigley: Yeah.

[00:24:35] Martin Schmidt: Everyone is watching the other guys and watch what they do. So it’s, once you start working with some of them, the rest will start like, oh, this is interesting. If X, Y, Z worked with them, maybe we should too. That’s how you build the traction, but you need someone to start, right? And that’s probably not going to be the biggest guy.

[00:24:53] Nathan Wrigley: Yeah, and again, I hadn’t really thought about that, but yeah, the, sort of looking over your shoulder if you’re a hosting company, seeing with perhaps jealous eyes, oh look, they’re getting loads of attention out there on social media because they’ve formed this relationship. And their emails are going out, and people are making comments on their tweets and their blog posts and things like that. Oh, we should definitely get a bit of that. Okay. That’s, really interesting.

So if somebody approaches you, then let’s say they’ve got a plugin. Let’s just assume that it’s a plugin that is useful and that a hosting company would be interested in it, if they had everything wrapped up correctly. What would be some wisdom that you would drop in terms of how to wrap it up? Like, how prepared do you need to be? What are the kind of things that you expect plugin developers to have ready, so that on day one, when you do your first outreach to the first hosting company, you feel confident that, okay, I’ve got a good client here, we’ve got a good chance. What are the bits and pieces that you need to have them have done?

[00:25:50] Martin Schmidt: I think on the technical side, I mean they will need to have some sort of like provisioning enabled. The host would probably want to sell the plugin themselves within their billing engine, and their system. So they will need some sort of provisioning to your system to say look, someone bought a licence and this licence needs to be valid and stuff like that.

So, this integration and that usually, I mean, if you don’t have that, it probably takes you a few months to implement that. So that’s something like, I would really start first and built these kind of things.

The other stuff that I think the plugin company should have ready is, what’s your proposition to the web host? And what’s the proposition of your product to the web host customers? I always tell my clients like, don’t make the other guys think. Tell them. Show them that you thought about it. Coming back to our earlier point about people being unprepared, don’t be that unprepared person. Like once you get some air time with these guys, tell them what your product is. Tell them what your product, or your company can do for the web host. But also tell them how they should be using your product and marketed to their customers.

[00:26:56] Nathan Wrigley: Kind of spoonfeed them basically.

[00:26:58] Martin Schmidt: Yes.

[00:26:59] Nathan Wrigley: Have everything so that they can lift it and just walk off with it and, okay, we’ll do that then.

[00:27:03] Martin Schmidt: Yes. It might feel like spoonfeeding and like, why do I need to do your job? But I mean, in the end, put yourself in the shoes of that product manager, and tell them, look, if I was you, I would be selling my product this and this way.

Some of the worst product pitches I had. Companies came to me. Told me look, this is our product. You’re going to make millions with it. And then I was like, okay, that’s interesting. How do I sell it to my customer? And then the answer was like, I don’t know your customers. You need to know how to sell stuff to your customer. It’s like, that’s not how you land a deal, right?

And one thing I like to do when I was pitching products. I looked at the website of the company I was pitching to. I mocked up their website with my product, and I put that in my presentation, and I told them, look sorry guys, we already hacked your website. Our product is already on your website. This is what it’s going to looks like. This is what it’s sold for, right? It shows them that you put some thought into that. That’s going to make you stand out.

Understand the work life of that product manager. They get those 30 emails like you, do. They decide to go on that meeting with you. You spend 30 minute pitching your product, and then you leave them with this big question mark. Like okay, this sounds interesting, but how the heck do I sell this to my customers?

After your meeting then they have lunch, then there’s like an escalation, then there’s an all hands, then there’s the weekend. On the next Monday they will have almost forgotten about you. And if they think about you it’s, oh, I still have to figure out how to sell this. This is complicated. I don’t have time for this. I’m going to postpone it. And that’s not what you want to achieve.

You want them to go out of that meeting and thinking, well this is an amazing product, solves a problem for my customers. And these partners, they think about me. They think about how I should be selling it. And maybe it’s not a hundred percent right. It’s not about getting it a hundred percent right.

[00:28:51] Nathan Wrigley: Right. They can adapt.

[00:28:52] Martin Schmidt: Yes. But giving them something to adapt is like a lot more than just don’t give them anything, right. And adapting is always easier than coming up with it yourself.

[00:29:01] Nathan Wrigley: So, the email that I typically get is basically a description of a product. It tells me what it’s called and then what it does. And often it’s a fairly technical description of a product. And, I imagine that if you are a marketer, you’re four lines into that email and your eyes have glazed over, and it’s like, okay great.

But what you are describing is go the extra mile. Don’t just explain the product. Presumably, there’s a bit of that’s got to go on, but it’s also now explain to the person receiving that email how their company can use that. How they could market it. The way that could be marketed. The sort of mockup landing page that you described just there. Go the extra mile, sit in their seat for a minute. Try to imagine what their busy life is like, have a bit of empathy, and imagine that they’ve only got an attention span of a few moments. It’s more that, than the here’s a product description. Now that you know what it is, please come and contact us, because that’s just not going to happen.

[00:29:59] Martin Schmidt: No, it’s not. I think it’s the same for us in private life. If you get emails about products that. I mean you just know yourself. You’re busy with so many things in between. Your kids coming home from school, and someone calling, your parents calling and all of that. You, just look at the email and if it doesn’t click immediately, it goes to the trash bin.

And it’s the same with these guys as well. Convincing people just in email is probably going to be difficult. You need to at least get them into the meeting. And I think that’s the one step before that. But once you have them in a meeting, spend that time wisely. It’s difficult enough to get them into the meeting. But if you have them in a meeting, don’t waste it with generic presentations.

Invest this little bit of effort, and mocking up that websites or just taking a bit of a look at who they’re selling to and adapting your message to that. It doesn’t take a ton of work. And it didn’t take a tonne of work four or five years ago. And now with AI it’s even less, it’s even less work, right? But if you want me to trust you as my partner to go forward and sell to my customers, that’s going to blame me for everything. I want to see that you invest a little bit of effort too.

[00:31:04] Nathan Wrigley: I think that’s right. Yeah. I think that’s a very human characteristic, isn’t it? I would like to see that you made an effort, if I’m going to make an effort. That’s just how the game goes, right? That’s just how it is. You know, if I get the impression that you just want to rock up, make loads of money, and do nothing, that’s never going to work really.

[00:31:25] Martin Schmidt: No.

[00:31:26] Nathan Wrigley: I mean there’s the occasional person that manages to pull that off, but on the whole, that’s not how human relationships flourish and work.

[00:31:33] Martin Schmidt: In the end, it’s about you want to build a partnership, right? And that’s not, I come to you and you give me loads of money. I don’t have a lot of friends like that. And I don’t think anyone else has a lots of friends like that.

Usually it’s like you give and you receive, right? And sometimes one side invests a bit more, and the other side invests a bit more. But usually if only one side is giving and the other one is only taking, that’s a toxic relationship. And usually they tend to break. So why should business relationships work any differently?

But it’s a funny conception that a lot of companies have is oh, I want to do partnerships. I just go out there and then they’re going to sell my product and I’m going to make lots of money, and I don’t need to do anything. That’s honestly what a lot of companies think.

And that’s the difficulty that a lot of partner managers have, right? They’re being sent out to get those partners, and then they’re expected to bring in just all the revenue without any additional investment. And that’s just not happening. Honest truth, nobody is out there waiting for you and for your product.

[00:32:32] Nathan Wrigley: Yeah. That is the brutal truth isn’t it? Do you subscribe to doing things in person? You know, so WordPress has got a real panoply of events, Meetups and WordCamps and there’s obviously other things that you mentioned, you know, Cloudfest and things like that. Do you find that tends to short circuit things?

I guess there’s a bit of personality that comes into this as well. You know, some people are, seem to have all the characteristics for selling. They’re incredibly good at that kind of thing. Maybe they’re practised at it. Maybe they’re just, you know, born in that wonderful manner. Do you subscribe to that? Is that a part of this jigsaw puzzle as well? You know, show up, meet the people, shake the hands, go to the restaurants, do the schmoozing and all of that.

[00:33:12] Martin Schmidt: Absolutely. You could do all the Zoom calls that you want, but I’ve experienced it firsthand. Like during COVID, we were talking to people for six months via video conference. Like one in person meeting in Munich. It felt like this moved us further than just the six months of constant video calls.

You can meet people, and you can relate to them, and there can be some sympathy and stuff like that. And you might not have to meet ever, but it usually helps a lot to build that trust. To just meet the person face to face, shake a hand, maybe have a beer and have a laugh and stuff like that just helps a great deal.

And I’ve seen partnerships without any face-to-face meeting, but usually I would definitely advise to see people in person. And some people are just difficult to get hold of. And then catching them at the Colosseum Bar at Cloudfest 10 o’clock at night really helps to suddenly be in touch with that person.

[00:34:07] Nathan Wrigley: There is something ever so human about that isn’t there? And I think we all on some level enjoy that.

So you found yourself in this product market space. Like I said, I know that this is a thing. So I would imagine that given a fair wind, you’ll be doing this for years to come.

Where do you find yourself online? Do you have a website where you’ve packaged up these products and services, you know, these partnership liaison services that you do? Where can people find you? Where do they go online to discover more about you?

[00:34:37] Martin Schmidt: At the moment mostly active on LinkedIn. That’s where I meet a lot of the people. I also have a website, martinschmidt.co. And that’s where also people can reach out to me. The website has been a little bit neglected to be quite fair because I straight on, jumped into LinkedIn and started publishing on LinkedIn, because the audience is already there. And people are not searching for how do I build partnerships with web hosts? But they come to me via LinkedIn because they tend to read some of my posts, and that’s how I get to speak to people like yourself.

[00:35:07] Nathan Wrigley: Yeah. Well, that is exactly how it happened. It was LinkedIn and I think you’re right. I think having a website would be of great value, but at the same time, you know, given the proclivities of what you’re doing, LinkedIn seems to be very much the best place to do that.

What I’ll do is I will put your bits and pieces into the show notes. So if dear listener, you head to wptavern.com you search for the episode with Martin Schmidt, that’s S-C-H-M-I-D-T, you’ll be able to find the links there. So hopefully you’ll be able to contact Martin via LinkedIn and what have you.

Really interesting topic and Martin, thank you for chatting to me about it today.

[00:35:42] Martin Schmidt: Yes. Thanks for having me, Nathan. It was fantastic.

On the podcast today we have Martin Schmidt.

Martin has been deeply involved in the WordPress and hosting industries since 2005, when he created his first WordPress travel blog while living in New Zealand. Over the years, he’s developed websites for small businesses, spent 13 years with IONOS in various management and strategy roles, and built partnerships at Wix and a German SaaS company. Most recently, Martin has focused on connecting WordPress plugin companies with web hosts, helping both sides unlock growth through smarter partnerships.

Today the conversation focused on the often-overlooked world of partnerships between plugin developers and hosting companies. Martin shares insights from his two decades of experience on why hosting providers are the perfect allies for WordPress product makers looking to grow, given their established relationships and marketing channels to large customer bases.

We talk about the curious fact that many plugin builders put enormous effort into their products, but stumble when it comes to sales, marketing, and building the business relationships necessary for broader success.

Martin discusses what hosting companies are actually looking for in a partnership, the technical and marketing preparations plugin makers should have ready, and why empathy and preparation make all the difference when trying to connect with busy product managers.

If you’re a developer, freelancer, or agency owner interested in taking your WordPress product to the next level, or if you want a candid look at how partnerships really work in the open source ecosystem, this episode is for you.

Useful links

Martin’s website

IONOS

Hosting.com

WP Rocket

Martin on LinkedIn

💾

#239 – Remkus de Vries on How Scanfully 2.0 Is Making WordPress Security and Performance Monitoring Simpler

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case how Scanfully 2.0 is making WordPress security and performance monitoring simpler.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.

So on the podcast today we have Remkus de Vries. Remkus has been active in the WordPress space for over 20 years, starting out with his own agency focused on high performance, scalable WordPress websites. Over time he has diversified into education and community building with projects like WithinWP, and a new initiative, The Guild, which is a paid community aimed at helping people build smarter, more performance, sites through a first principles approach.

Our conversation centres on Scanfully, a site health and monitoring SaaS Remkus co-founded, which recently hit version 2.0. Scanfully’s focus is giving users meaningful, actionable, insights into WordPress site, health, security performance, email, deliverability, DNS, and more. Packing all this data into an easy to understand dashboard.

We talk about Remkus’ motivation for diving deep into the complexities of WordPress monitoring, and why many users struggle to keep on top of the technical side of their websites. Remkus argues that too many site owners are stuck in a reactive mode, only investigating issues once something breaks. And Scanfully aims to change that mindset by making ongoing health checks accessible and easy to parse, even for the spreadsheet averse.

Remkus walks us through the products evolution, including the 2.0 update that aimed to reimagine their dashboard experience, added public APIs, and introduced tools like MCP AI integration, empowering users to query their sites health conversationally.

We also get into recent and upcoming features such as WooCommerce checkout monitoring, activity logs, and future add-ons designed to cover forms and other business critical flows.

If you manage multiple WordPress sites, run an agency or are simply interested in building more robust futureproof WordPress projects, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you can find all the other episodes as well.

And so without further delay, I bring you Remkus de Vries.

I’m joined on the podcast by Remkus de Vries. Hello, Remkus.

[00:03:29] Remkus: Hello, Nathan.

[00:03:30] Nathan Wrigley: It’s been a while. Remkus and I have been on many calls in the last few days and weeks. We’re going to have today about a project that Remkus has been actively involved in for a number of years. It’s called Scanfully. We’ve reached version, I’m going to say 2.0, let’s go with that.

[00:03:46] Remkus: Yeah. Yeah. Yeah.

[00:03:47] Nathan Wrigley: But over the last few days it’s actually advanced a little beyond that. So that’s going to be the main focus.

I would probably urge listeners to this podcast. If you want to understand what the product is and how it works, maybe press pause. Go to Scanfully.com, so scanfully.com, and then come back and you’ll understand fully what the product is.

Before we get stuck into updates and product and what it all does. Very briefly, Remkus, do you want to just tell us a little bit about you, your backstory, WordPress space, that kind of thing?

[00:04:17] Remkus: Yeah, sure. Been in the WordPress space, active, 20 plus years now. Started with an agency, very quickly moved into complex performance scaling, more complicated type of sites.

Ran a niche agency like that for a very long time. In the last couple of years I’ve been doing some diversification. I have withinwp, which is a WordPress, how do I explain this? Because this is also in transit, but it’s a podcast, it’s a newsletter. One that’s being cited by This Week in WordPress a lot, I should say.

And part of it is the educational side, which is the part that I’m building out currently. And what I mean with educational side, that I’m preparing a community, a paid community, that has the sole goal to help you better understand WordPress and build better sites, smarter sites, more performance sites, that sort of stuff. Basic first principles type approach.

And that is roughly how I look at WordPress. And Scanfully is something I started with my co-founder Barry, let’s call it three years ago. And from a similar angle, we want to solve, essentially site health and performance monitoring tool of your WordPress site in the broadest sense of the word. Meaning the word Scanfully is literal. We scan fully and what we’re not scanning fully currently, we will be.

[00:05:32] Nathan Wrigley: Okay. Thank you. Can I ask a question? May touch on your personality, I guess. All those years ago, 20 plus years when you came into WordPress. How can you explain why you delved into this bit? Because there were so many ways that you could have gone, but you’ve really made scanning, and site health, and monitoring and performance, that is your thing. Is there a bit of that which, speaks to you on some level? Do you find yourself drawn in that direction, no matter where you look on the internet?

[00:05:58] Remkus: Yeah.

[00:05:59] Nathan Wrigley: Do you enjoy data analytics, spreadsheets, numbers, all of that?

[00:06:03] Remkus: I wouldn’t call it enjoy, but, I’ve always been good at it. I always found it fun to some degree. But in general, I get bored quite easily. If I’m to stick with a topic, it needs to be the complicated version of a topic. To me, in web development, that quickly revolves around all the things that make a WordPress site more tricky to scale, or more tricky to make fast, or more tricky to fill in the blank. There’s tonnes of different subtopics to that.

[00:06:25] Nathan Wrigley: Yeah.

[00:06:26] Remkus: And that then gives you a different view of what is important. And Scanfully is one of the answers to that. we. See that there’s, I think the whole industry is levelling up in a way. I don’t think it’s happening fast enough, but part of it forces you to start thinking about things in a more professional way, like more preemptively understanding what is something that’s going on. What is a trend on your site? What do you see happening? And I think we’re still too much on the reactive side of things. So if my side is down, or if somebody complains it’s slow, then I’ll have a look. And we want to change that awareness and make it one of your first thoughts instead of an afterthought.

[00:07:02] Nathan Wrigley: It’s a curious thing then that the complexity which you enjoy, in a sense, you require other people to not enjoy it as much as you, in order for you to have a product. And I am one of those people. If you present me with a, I don’t know, a Google Analytics dashboard, or a spreadsheet which goes beyond about four rows, then I quickly lose interest. I genuinely can’t maintain my effort over there. I glaze over and don’t enjoy it.

And so part of the problem with dealing with WordPress is getting over that hump. Maintaining the interest in an area that I feel ill-equipped, not just ill-equipped, completely out of my depth.

And so having tooling, the likes of which you’ve built with Scanfully enables people like me to actually stand back and go, okay, that complicated thing is made more easy. I can actually start to understand it in real terms, with data and charts that are less overwhelming. And I guess that’s the point.

[00:07:53] Remkus: That is the point, and that is essentially also the driver, why we went from dashboard version 1.x to now, 2.x. Because it’s very easy when you’re on the more technical side of things and you kind of understand what the signal is and what it’s implying to forget what the person who doesn’t understand the extra layers and the assumptions that go underneath. Like what does that actually mean?

The 2.0 rebrand. Because it’s not a rebrand in terms of what we do, but it’s a rebrand and how we interpret every single version of the monitoring metrics that we collect, how we present it, and what we allow you to do with it. Everything has been rethought. It’s been a, I think in total, we’ve had about four or five months of just working with a redesign. And we call it a redesign because it is, because it visually looks different.

We’ve got all this feedback of how people are using it. And a common theme was, we’re missing this, we’re missing that. Could you make that easier? So we were like, okay, that’s a lot of stuff pointing in the same direction. Why don’t we start rethinking how we’re going about helping you figure this out?

And I’ll give you a very concrete example. So if a site goes down, because we have an uptime monitoring, you get a notification. But if it’s the server that goes down and you have 25 sites on that server, it doesn’t make a lot of sense for you to receive 25 emails.

[00:09:05] Nathan Wrigley: No.

[00:09:06] Remkus: So gathering information per monitoring alert is something we’re doing now. And, the same goes for if there’s, I don’t know, if the latest plugin you’re using on all of your sites has something that needs to be fixed, or something that is already fixed. So let’s assume there’s a security release for it. You don’t need to know that 25 emails. You need to know there’s one email, and these are the sites that are affected. But you also want to know, is this a high risk? Is this a medium risk? Is this a low risk?

Because there’s plenty of security stuff that is so close to impossible to replicate that, do I need to act right now? Maybe, but we give you the insight that you can act upon it. Like it’s not, we’re not forcing you to pay all the attention all the time.

And it’s things like that. So we had the data already, but the question then becomes, how do we make this digestible? How does this become a signal, versus the noise that it’s also is? So that’s a lot of rethinking. That’s a lot of rethinking in what is valuable to share, and how is it valuable to share and what are the things you would like to do with certain things?

So, an example, related to that is what if there is an update available for a plugin that you’re using in a few places? But there’s no fix yet. Do we need to send you every single day that there is a security update? Or there’s a security issue? Probably not. So why don’t we allow you to snooze a particular alert? It’s simple things like that. And I say simple. It’s not simple to implement, but.

[00:10:27] Nathan Wrigley: Simple on the front end.

[00:10:28] Remkus: Yeah. Simple for you as an end user. So that was a lot of thinking and figuring out how do we make this more pleasurable, for as pleasurable as the topic itself is.

[00:10:39] Nathan Wrigley: I’m going to circle back to the product in a moment, but I’m going to ask you a curious question.

[00:10:43] Remkus: Yep.

[00:10:43] Nathan Wrigley: You may balk at this question and think, okay, that’s unusual and a bit weird. Is the WordPress space for you quite an exasperating thing. And what I mean by that is, you are obviously steeped in this knowledge, about how things can go wrong, and how a poor implementation of something over here can have catastrophic effects over there. Given enough time, and the stars aligning in a certain way.

I don’t know how to describe this. Does that mean that everywhere you look, you just see catastrophe and problems. And you open up a WordPress website, you’ve got a new client or somebody’s onboarded you with the plugin. You look inside and you sort of face plant, head slap. Okay. All the stuff that I know, which is second nature to me. Why don’t they all know this? There’s no question there, but can you see what I’m trying to.

[00:11:27] Remkus: Yeah. Yeah, I can. You’re not recording the video. The people listening didn’t see me nod along the way of what you were saying, but yes. If you understand things. So there’s a principle called first principles. Which means everything we approach, we should approach from the first principles. Like what is the base layer of where to solve problems. And, this is not even just WordPress, this is life, I guess.

But there’s a big tendency for people to look at a problem and then have the idea of how they want to fix the problem, but they don’t actually look at the layer, it should be fixed. They just want to fix the outing. That’s not really a fix, right. You fix things at the bottom layer. You can identify where the problem lives.

And when that is your view on life slash work. Yeah, there’s moments where you go, how do you, not look into this? This is your work, this is your job, this is your, competency. Why do you not dive into this? But I also understand that’s not for everybody to be in that layer of how I look at things. And it’s not me wanting to force other people, my model of the world, but it is something where I go, you don’t need to do my model of the world, but there’s some stuff that you actually should be quite skilled on because it’s part of your job. Because it touches your job. It touches the clients you serve and all of that sort of stuff. Long-winded answer, but yes, I have those moments.

[00:12:39] Nathan Wrigley: Yeah, I guess it must be the same no matter which bit of WordPress you’re in. So for example, I don’t know if you’re a front end designer and you see catastrophic use of fonts and spacing and typography, and it would make the head plant moment occur. But also accessibility. And there’s these tendrils isn’t there? And we can’t become expert at all of them, but many of the things are inconveniences. Where if something goes wrong, it’s annoying, but that’s probably where it ends.

Whereas the stuff that you are dealing with, there’s a potential for catastrophe to occur. The website gets defaced or taken down, or the server gets compromised and is used in some crazy way that we can’t imagine. That makes your part I suppose a little bit more essential. But then, as as you said, we can’t all be experts, and relying on the expertise that you have and the tools that you’ve built. I suppose that’s why you occupy the space that you do.

[00:13:33] Remkus: Yeah.

[00:13:33] Nathan Wrigley: Because not everybody can spend the time becoming as knowledgeable as, as you have become.

[00:13:37] Remkus: And I, for the record, I don’t acclaim to have all the knowledge. I just happen to specialise on a few things I find highly interesting.

[00:13:44] Nathan Wrigley: Yeah.

[00:13:44] Remkus: My goal for the Within WordPress community that I want to build, which is called The Guild, is exactly to behave like a guild. We’re all there to elevate each other up. That is what a guild is supposed to do. And, back in the day, you had guilds that were that you went there, you were part of it, and all that had as a goal was to help you elevate your craft.

And we need to start thinking about what we do as a craft. And how do you do your craft? Well there’s tonnes of different ways to do the craft that’s putting bread on the table. But if you’re not actively developing yourself to become better at your craft, then what are you doing? You’re, essentially behind in the first week you start working. And you’re only playing catch up. And most people have forgotten that they’re just in the game of playing catch up. Which I think is a shame.

[00:14:26] Nathan Wrigley: You’ve alluded from various bits and pieces that you said. You’ve suggested what Scanfully does. So we have an idea that there’s charts, and graphs, and information about things that could be going wrong with your website in the background. But we haven’t really explained what the tool does at its core.

So putting the update to one side, if we just examine why you built the tool in the first place, what does it broadly do? And then we can get into what it most recently does and how it’s been adapted for the 2.x version.

[00:14:55] Remkus: So Scanfully is about giving you the information so you know what broke on your site, and what changed and what things you need to pay attention to. Anywhere from critical stuff. So vulnerabilities, downtime, to also adjacent critically, are my emails being sent from the site? Does that still work? So we do email monitoring. We do DNS checking.

We do all kinds of site health, like actual site health menu inside of WordPress. We pull in that data so you can see and you can filter for which of my sites are in PHP seven point, whatever still? You can figure that out.

If you need to do all kinds of filtering on data that is living in all of your WordPress sites. That’s a pain in the ass to have to click through every single site to figure out what’s what. And maybe your control panel on your server tells you something, but Scanfully will tell you everything.

We will tell you how large the uploads folder is. We will tell you, is your certificate about to be renewed, yes or no? Did anything go wrong when that happened? Things like that.

So anything and everything that goes into the bucket of what is site health, what is a healthy site mean? We are monitoring, or we will be monitoring. We still have a very long list of stuff we’re going to add. But yeah, the goal for Scanfully is to have you be in control of what’s going on with your site.

[00:16:19] Nathan Wrigley: Ok thank you. I have some follow up questions just to that, so the first one is. Who has been, or who potentially is your ideal customer? So I’m going to broadly bucket that as, I don’t know the person who’s got just one WordPress, or a handful of WordPress websites and they manage that themselves. Are they the kind of people that you are trying to get? And then I’m going to go into different buckets of enterprise perhaps. Agency level customers. I’m imagining there’s some perfect fit there.

[00:16:42] Remkus: Yep.

[00:16:43] Nathan Wrigley: And then also I’m wondering if hosting companies also might be a customer of yours in terms of adding this in, to a deployed website on their platform.

[00:16:53] Remkus: They are now. One of the features we added, we kind of already had it, but we added publicly now, with Scanfully 2.0 is a public API. Which means if there’s a public API, anybody can hook into whatever data we have, and display that in their dashboard or website, or wherever they would choose to do so.

So yes, we cast a broad net, But the goal is for any client that needs to be in control of what’s going on with their site. But the reality is this is from freelancers to agencies and indeed, hosting type of adjacent companies. Yeah.

[00:17:25] Nathan Wrigley: Right. So there’s a fit across all of those three things that I just mentioned?

[00:17:29] Remkus: Yeah.

[00:17:29] Nathan Wrigley: And do you have pricing that reflects that? So in other words, can you buy a single licence, and a multiple licence and a, I don’t know, an unlimited licence?

[00:17:37] Remkus: It’s a flat structure. It’s 299 a month per site. Simple.

[00:17:41] Nathan Wrigley: And, in terms of the level of depth of technical understanding that you have to have in order to get the tool working, is this more a case of upload the plugin, activate the plugin, and then there are some sensible defaults? Or do we have to do a tonne of background research to understand what’s going on? And maybe that’ll lead us into the 2.0 stuff in a minute.

[00:17:59] Remkus: There’s nothing more than installing and activating.

[00:18:03] Nathan Wrigley: Okay.

[00:18:03] Remkus: And even the activating we have made as frictionless as possible. The only thing you need to do is once the plugin is activated, you click that button that says connect to your Scanfully dashboard, and assuming you’re already logged in there, clicking that button is all you need to do. There’s no copying pasting of keys and other weird stuff.

[00:18:18] Nathan Wrigley: So I presume from what you said earlier, the 2.x, the article that I’m going to link to in the show notes on the WP Tavern website is about 2.0, but I understand time has passed and probably by the time this episode will be on two point something.

[00:18:32] Remkus: 2.3.

[00:18:33] Nathan Wrigley: It would appear that you obviously took a stab at what you thought people would like to see in their dashboards. That’s one of the things that’s been updated. How did you adapt that over time then? Because, like we said earlier, getting complicated data to be easy to understand, that is a proper art form. I don’t think you’ll probably ever end this journey.

[00:18:52] Remkus: No. No.

[00:18:54] Nathan Wrigley: You’ll just be iterating forever.

[00:18:54] Remkus: Yeah.

[00:18:54] Nathan Wrigley: But is that one of the things that you got feedback on? Okay, it’s good, but we’re still confused. Make it simpler to understand. Just describe that side of things.

[00:19:02] Remkus: Yeah. So that’s the part where you go, how do I go from showing noise? Because there’s a tonne of data that you actually need to be in control of. But how do I make that, easy, digestible?

So one of the solutions we came up with, and that seems to have gone down really well, people like it, is essentially every view on top has the most important things. So we’ll tell you if there’s stuff that you need to be updating. We’ll tell you if email is not being delivered. We’ll tell you if the percentage of up and down times you’re having is odd, or requires more investigation. Essentially we’re helping you figure out the important things per monitor, per view. And then from there, you can deep dive into the data that we collect and figure out things.

[00:19:46] Nathan Wrigley: You’re moving away from graphs and data first, into more of a human readable summation in a couple of sentences?

[00:19:53] Remkus: Yep.

[00:19:53] Nathan Wrigley: Okay. So you can finally parse what’s going on. Okay. That’s good to know. And you said that’s been well received?

[00:19:59] Remkus: Yeah, people like it.

[00:20:00] Nathan Wrigley: Okay.

[00:20:00] Remkus: It’s more straightforward in terms of quickly understanding what’s going on. That was a big part, and we also wanted to make that information available more easily as well. And what I mean with that is that inside the API you can query this now.

But more conveniently, we have an MCP server available as well. So you can connect us to your favourite LLM, your favourite AI and just ask the questions. Like let’s say you have a bunch of sites for different clients in there, but one client has a specific question. You’ve labelled them accordingly inside of Scanfully. You can do that now. And then your LLM, you can ask, either ask it to label it, you say these are the domains, labelled them with this client. And then tell me do I have any vulnerabilities? Is email being sent out correctly? Are there any weird DNS changes? What does my uptime look like? And we’ll tell you.

[00:20:46] Nathan Wrigley: So the API enables you to, I don’t know, if you’re an agency owner, you could build a dashboard, for example, for your clients or something like that. So you could put charts and information in a place where your client can go and see it in a way that makes sense for them.

[00:20:58] Remkus: Correct.

[00:20:59] Nathan Wrigley: But the MCP enables you to kind of have a conversation with the security and the current state of your WordPress website. That’s so intriguing.

[00:21:07] Remkus: Yep.

[00:21:08] Nathan Wrigley: Have you discovered some interesting, quirky things in there? You know, you you ask it a particular thing and a surprising thing came back?

[00:21:13] Remkus: I got for one of the sites that I have in my account, I got some intermittent email is not being delivered. And I go, why does it turn on and off all the time? What’s going on here? So I ask it to investigate, look at any commonalities. Look at anything that stands out. And it sure enough came up with something that goes along the lines of there’s conflicting DNS records. So if there’s multiple validation records, I was using a transactional email service for that. But their validation system allows you to have old validation DNS records in there as well. And apparently their system picked up both intermittently. How do you figure that out?

[00:21:48] Nathan Wrigley: With an MCP, it turns out. Yeah. That’s really interesting.

[00:21:50] Remkus: Yeah. So it told me, double check the DNS records here, because it looks like, and then I go, okay, let me check that. And I go in, I dive deeper into the dashboard for my transactional email provider. And I go, hold on. This is, okay. I get it now. So let me delete those. I deleted them, and the problem solved.

[00:22:07] Nathan Wrigley: Does your MCP enable bi-directional things to happen? Or is it basically read only?

[00:22:12] Remkus: It is read only on the data. It’s write on, like I said, if you want to create labels and other things like that.

[00:22:18] Nathan Wrigley: Unharmful stuff is right.

[00:22:20] Remkus: Correct.

[00:22:21] Nathan Wrigley: Because you are dealing with quite a lot of powerful stuff here, and writing in the wrong direction in a silly way, which let’s be honest, MCPs enable us to be very silly very quickly.

[00:22:30] Remkus: Yeah. Yeah. Yeah.

[00:22:31] Nathan Wrigley: Okay, that’s good to know. It’s basically read only.

Okay. We’ve got the dashboard updates with more human readable data. We’ve got the API. We’ve got the MCP. Anything else in Scanfully 2.x?

[00:22:43] Remkus: If we include 2.x, the release we did yesterday is 2.3. And in that we have much smarter user activity tracking. Content changes. Not only who did the change, but what is the change, that sort of stuff.

We pull everything out of WordPress into our dashboard. So for instance, we have a full WordPress activity log and in that log, we collect all the things. Whatever happens on your WordPress site, so that’s a plugin installed, updated, all those things. So now user activity is in there as well.

And it’s also the things happening to your user. So elevated admin rights given to a user. Was that supposed to happen? An email address change to a administrator is something you would want to know. On a multi-site, if a user gets to have super admin, you’ll want to have that logged. So things like that.

So the 2.0 essentially, which is a week and a half ago, it allowed us to have a whole bunch of other refinements we had essentially lined up. We have a much better foundation to build these things on top of what we now have. So we can move forward much faster.

[00:23:42] Nathan Wrigley: We’ve already agreed pre hitting the record button that there’s a whole load of stuff which you know is going to occur, but we are not quite ready for public disclosure at the moment.

One thing that we didn’t touch on, which I suspect people will be listening to this thinking, okay, hang on a minute. How does it all work in terms of, is there a scanfully.com/whatever login? In other words, do you have a SaaS sort of admin section?

[00:24:06] Remkus: Yes.

[00:24:06] Nathan Wrigley: So the plugin kind of binds to that, because I miss that at the beginning.

[00:24:11] Remkus: Yeah, correct.

[00:24:11] Nathan Wrigley: We probably should have explained that. So the plugin binds to the SaaS. The SaaS holds the data. And in that way, for example, an agency could have an overview of all the sites that they’re managing and that kind of thing?

[00:24:23] Remkus: And everything that happens on that site that is worthy of tracking and monitoring for. So again, the activity log is a good example. A WordPress activity log should not live inside the WordPress site, period. From a performance standpoint, it makes no sense. Most databases for most hosting companies have issues when you track and sort a, let’s call it a busy website.

So what we do is we asynchronously pull all of that into our dashboard. So if your site goes down for whatever reason, we have a track record of what the last things that were happening on your site.

[00:24:53] Nathan Wrigley: Oh yeah, of course.

[00:24:55] Remkus: There’s just an easier way of being in check.

[00:24:58] Nathan Wrigley: So you’d log into the SaaS, everything’s there. So if your site does have some catastrophic failure, then at least you can begin to understand what’s going on.

[00:25:06] Remkus: Yep.

[00:25:07] Nathan Wrigley: And work backwards from there?

[00:25:08] Remkus: Yep.

[00:25:08] Nathan Wrigley: I think that’s probably all the questions that I’ve got. Is there anything that we didn’t touch on that you wanted to mention?

[00:25:14] Remkus: I think what’s fun to mention is that this whole rewrite allowed us to start building add-ons as well.

So the base monitor service as we have it currently is what Scanfully is. So that’s Scanfully monitor. But we’re, and probably by the time this podcast is being aired, I think we will have, the beta available for WooCommerce checkout monitoring.

This is essentially an add-on to the base service. And what it does, we fully check everything that goes into, from is the product available in your WooCommerce, website? Can I add it to cart? Can I then go to cart? Can I then start the checkout? Can I fill out the checkout? Can I start the processing of the actual payment. So we don’t go into the payment itself? So they’re test orders, so to say.

[00:25:59] Nathan Wrigley: But the moment right before?

[00:26:01] Remkus: Yep to the moment, right before. So we’ll tell you if we can’t reach the payments provider. We’ll tell you that, but we can’t, at this moment in time, do the step beyond that.

[00:26:09] Nathan Wrigley: So how does that work then? Does it literally do that as if it’s a human being, you know?

[00:26:13] Remkus: It does.

[00:26:14] Nathan Wrigley: Is some part of your SaaS kind of opening up a browser somewhere in effect and doing that journey. Finding a product, putting it in the cart, checking the cart, and so on.

[00:26:21] Remkus: And the fun thing is you get to define what that journey looks like. So if you have a custom WooCommerce checkout, or any of the other solutions. We account for that. And you can tell us if it’s any different from what their default is, or the WooCommerce default.

And from there you get to essentially define the journey. And then the journey is stored as the thing we’re checking. And we’re doing this from the external, obviously. So it doesn’t touch any monetary things. Nothing gets charged, nothing gets booked. And the plugin that is providing the connection to our dashboard, that plugin cleans up whatever test orders were made in that process.

[00:26:56] Nathan Wrigley: Right, okay. So it’s not 3000 carts.

[00:26:58] Remkus: Yeah, we don’t, want to do that.

[00:27:00] Nathan Wrigley: Do you enable that in other ways as well? for example, I’m thinking maybe a contact form is incredibly important to somebody’s business.

[00:27:07] Remkus: Yep, that’ll be next.

[00:27:08] Nathan Wrigley: Is it possible to, outside of WordPress, visit a contact page, fill out the form fields, and then even, I don’t know, maybe even check on the other side to see if an email landed or something like that?

[00:27:17] Remkus: A part of it we’ve already solved with the email monitoring, or I should say email deliverability monitoring.

[00:27:23] Nathan Wrigley: Of course you’re on the inside there, so you can see whether that got sent.

[00:27:27] Remkus: Yes. But once we’re fully done with releasing the WooCommerce checkout monitoring, we are going to move to forms next. Because you’re right, if you have a landing pages, or a critical contact form or whatever, you need to know that that still is working as intended.

[00:27:41] Nathan Wrigley: So that’s a roadmap item. To be able to build these custom journeys, starting with WooCommerce, but more or less anything at some point. We want to see if people are going from A to B to C as we’d hoped.

[00:27:52] Remkus: Yeah, it’ll be a separate thing in the sense that WooCommerce will do a lot more than just checking the validity of the form, because that’s essentially on the WooCommerce side of things, that’s the checkout form. You fill out the form. And that’s the most similar to a general form. But yeah, we will build a separate feature inside of Scanfully that allows you to do all the types of monitoring you could possibly imagine you would need to make sure your forms are working the way you design them.

[00:28:16] Nathan Wrigley: Random question just before we end. How exciting do you find this? When you embark on the journey of building a product like this, you know, oh we’re going to do this thing, me and my friend. We’re going to do this thing, it’s going to be brilliant. And then the reality sets in, you know, it’s difficult, you’ve got to manage customers and all that kind of stuff. Do you still wake up excited by this?

[00:28:32] Remkus: Oh yeah.

[00:28:33] Nathan Wrigley: Obviously you’re not going to say the opposite. I’m just wondering if that curiosity still remains and whether or not.

[00:28:38] Remkus: It does, because there’s just so much more we can still do. And the feedback that we’re getting is very positive. And especially with this new imagination of how this should be solved with the 2.x reboot I guess is probably the best word. It just excites me on the potentials that we have.

The WooCommerce checkout monitoring is a good example, but there’s tonnes of other add-ons we have in mind where it just makes sense for you to have the Scanfully monitor as base. But there’s stuff that we can do more. We’re already gathering it in one way or another, and just to be super complete with what we’re presenting. Yeah, that excites me, yeah.

[00:29:11] Nathan Wrigley: Okay, thank you for chatting to me today. Scanfully.com. Go and check it out. Remkus, where are you apart from there? If people want to contact you, are you available on a particular platform, I don’t know, social media or email or what?

[00:29:26] Remkus: remk.us

[00:29:28] Nathan Wrigley: Nice. Of course you have that domain. Yeah. That’s lovely. In which case Remkus I will speak to you soon and thank you for chatting to us about Scanfully.

[00:29:38] Remkus: Thank you for having me.

On the podcast today we have Remkus de Vries.

Remkus has been active in the WordPress space for over twenty years, starting out with his own agency focused on high-performance, scalable WordPress websites. Over time, he has diversified into education and community-building with projects like WithinWP and a new initiative, The Guild, which is a paid community aimed at helping people build smarter, more performant sites through a first principles approach.

Our conversation centers on Scanfully, a site health and monitoring SaaS Remkus co-founded, which recently hit version 2.0. Scanfully’s focus is giving users meaningful, actionable insights into WordPress site health, security, performance, email deliverability, DNS, and more, packing all this data into an easy to understand dashboard.

We talk about Remkus’ motivation for diving deep into the complexities of WordPress monitoring, and why many users struggle to keep on top of the technical side of their websites. Remkus argues that too many site owners are stuck in reactive mode, only investigating issues once something breaks, and Scanfully aims to change that mindset by making ongoing health checks accessible and easy to parse, even for the spreadsheet-averse.

Remkus walks us through the product’s evolution, including the 2.0 update that aimed to reimagine their dashboard experience, added public APIs, and introduced tools like MCP AI integration, empowering users to query their site’s health conversationally.

We also get into recent and upcoming features such as WooCommerce checkout monitoring, activity logs, and future add-ons designed to cover forms and other business-critical flows.

If you manage multiple WordPress sites, run an agency, or are simply interested in building more robust, future-proof WordPress projects, this episode is for you.

Useful links

Scanfully

Scanfully 2.0 release post

Within WordPress

The Guild

Remkus’ personal website

Remkus on X

💾

#238 – Chris Huber on How Static Site Importer Makes Migrating Any Website to WordPress Easier Than Ever

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, how the Static Site Importer makes migrating any website to WordPress easier than ever.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.

So on the podcast today we have Chris Huber. Chris’s journey with WordPress began in his college days, first as a writer and blogger, and eventually progressing to software engineering after moving his personal site, extrachill.com to WordPress in 2018, Chris went deeply into WordPress, developing custom plugins and exploring all the corners of the platform. His passion for experimentation and creative tech led him to Automattic where he now helps shape the WordPress experience as a software engineer.

Our discussion centres around two main topics, Data Liberation and the Static Site Importer tool.

We focus upon the evolving landscape of website migration and ownership. Chris explains how Data Liberation aims to make it easier for users to take control of their sites, whether they’re moving to WordPress from platforms like Wix, Squarespace, or Drupal, or just want portability for their data.

We also get into the Static Site Importer, which takes this a step further by converting any static HTML / CSS website into a fully editable WordPress block theme, headers, footers, and all.

Chris walks us through how these tools work in tandem, highlighting the mechanics behind website crawling, mapping HTML elements to Gutenberg blocks, and handling complex features like WooCommerce and calendars.

We talk about the continuous improvement of these tools, how each migration helps raise the bar for future imports, and how this project could fundamentally change the way people move websites between platforms.

If you’re curious about the future of website migration, and how WordPress is removing the hurdles for users who want to truly own and manage their content, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Chris Huber.

I am joined on the podcast by Chris Huber. Hello, Chris.

[00:03:21] Chris Huber: Hey Nathan. Thanks for having me.

[00:03:22] Nathan Wrigley: Yeah, very welcome. Chris and I have never spoken before, but we’re going to be talking today about two things, data liberation, but also a tool that I’ve never used, but sounds really interesting. It’s called the Static Site Importer.

As is always the case, if you go to wptavern.com and search for the episode with Chris in it, you’ll be able to find all of the necessary links. In this case, it’ll be, GitHub pages and things like that.

But before we get stuck into it, Chris, would you mind just telling us a little bit about yourself, your background with WordPress, who you work for, that kind of thing?

[00:03:54] Chris Huber: So I’m Chris. I live in South Carolina. My background with WordPress is I started my own blog back when I was in college, that was 2011. But I wasn’t on WordPress at the time. I switched to WordPress around 2018, and I started getting more and more into it over the years. Now I work for Automattic as of about six months ago. And I’m a software engineer.

[00:04:14] Nathan Wrigley: Thank you. So before those six months, a lot of people in the WordPress space have this, I think, desire to end up at a place like Automattic where they can fully work just on WordPress. That’s my estimation anyway sometimes.

[00:04:26] Chris Huber: Definitely a dream job. I really love working on WordPress, and it’s super cool to be able to work at Automattic but I got into software engineering a little bit later in my WordPress career. I was more of a writer and a blogger at first, and over time my website started getting more advanced and I wanted to build more things on it.

And I got, I was an early adopter to AI, and I started learning a lot. Like as soon as I picked up AI, I started asking a lot of questions and turned my website, my personal WordPress site is called extrachill.com, and it’s kind of a WordPress multi-site like application with 60 custom plugins on it.

And I just, I just went crazy. That’s how I ended up at Automattic is because my website, some things I built on my website were like, attention on Twitter from some people who have been around WordPress for a good bit of time.

[00:05:15] Nathan Wrigley: Yeah, I’ve noticed this trend. I think there’s a trend in upper management. Let’s go for that phrase, for the more curious bits. The unusual, the interesting, the weird and the wonderful. I think there’s a bit of a movement right now to see that again.

Back in the day, I have grey hair, I am considerably older than you, I think Chris. And, when the internet began, I was old enough to be able to use a computer. The internet was a truly strange place. Nobody had the faintest idea what to do with it. And so everybody launched their crazy, unusual thing, and it was normal. And then everything became a bit of a homogenised version of the internet.

These social media platforms came along and normalised everything. And UIs settled down and UXs settled down, and got stuck in a rut. But now there does feel, especially in the WordPress space, as if there’s a desire create the unusual, and the weird and the wonderful, and that’s brilliant. That sounds like you’ve been hired to do just that.

What we’re going to talk about today is not that weird. It’s fairly useful though, I would say. And, there’s two parts to it. As I mentioned at the top of the show, there’s the data liberation part, and then there’s the static sighting importer.

I think we’ll go through them in turn, if that’s all right? Starting with the Data liberation. This was a phrase that I used to trot out a couple of years ago when the Data Liberation project began.

Do you want to just run and tell us what the Data Liberation Project is, what its goals are?

[00:06:42] Chris Huber: So the Daily Liberation Project has been ongoing since way before I started working on it. And it is basically, a lot of proprietary website building platforms make it really hard to get off of these platforms. Especially if you want to keep your website design. And that’s their business model is, they’re not open source.

So for a long time we have assumed that Data Liberation meant using WordPress. But recently we have changed that definition a little bit, and it just means turning any website into a portable copy that you can download, and do whatever you would like with.

So the data Liberation Agent that we have created actually can convert any URL into a portable copy. So you just give it a URL and it loads the site in a browser, and downloads every single page as a perfect copy with all the animations and everything. The only thing it doesn’t get is anything that’s inside the database, inside the site. Because it’s all happening on the outside of the site.

So that’s step one to our process.

[00:07:42] Nathan Wrigley: I think that’s great. I remember it being couched in terms of trying to onboard people from going to use the word rival, although that’s the wrong word, rival CMSs. So for example, Drupal and Joomla and things like that. The idea being that its really hard work.

It can be a lot of work getting a site from over there, Drupal, let’s say, and bringing it over to WordPress. And so there was an endeavour to make it point and clickable. And in, in the way that you’ve described it, all that you have to do really to get a fairly functional version of your website is to know the URL.

So you go to the original domain, you paste in the URL, some magical voodoo goes on in the background. And within a few moments, that site has been replicated, and hopefully it can then be migrated over to WordPress. But I suppose it goes a little bit further than that because it’s a two-way promise, isn’t it?

It’s not just that you can bring things into WordPress. The promise is that should you become fed up of WordPress, you could go in the other direction. You could go WordPress to Drupal. Or indeed you could go WordPress, WordPress. So you could use it as a migration tool or something like that.

So it isn’t just this importing mechanism, it really is liberation in the strictest sense of the word. It’s your data. Pick it up from wherever it is now. Take it to wherever the heck you want it to go, and we’ll enable you to do that.

[00:09:01] Chris Huber: Yeah, basically. Not even just Drupal, but places like Wix and Squarespace and Weebly and other website building platforms that might be proprietary and open source. Yeah, that’s step one to the process that we’re using.

[00:09:13] Nathan Wrigley: Okay, is there anything technical that we need to know about how that process works before we move on to the Static Site Importer? Or are the two things bound so that if we move on, it’ll all make sense in due course.

[00:09:24] Chris Huber: It will all make sense I think.

[00:09:25] Nathan Wrigley: Yeah. I’ll interrupt as I see fit.

So the next part of this jigsaw puzzle, now that we’ve got the data liberation piece under control is the Static Site Importer.

Now, this to me at least is new. I had not seen it. I caught a post by a colleague of yours, on maybe it was X or something like that. And I saw it and I thought, okay, that’s interesting. Static Site Importer, what does that mean? And I dug a little bit deeper, and that’s why you are on the podcast to explain it.

Okay, 10,000 mile view looking down, what’s the goal of the project? And then I suppose we can get into how it does it and all of that magical stuff.

[00:09:59] Chris Huber: So the goal of the project is to create WordPress Block Themes from a static HTML website. So any basic HTML, CSS, JavaScript website, converting it into a WordPress site, with the click of a button. So that’s the basic goal.

[00:10:15] Nathan Wrigley: Okay, so the idea here is that you see a website somewhere online, hopefully it’s yours. And then you take the URL, but rather than the sort of more generic approach that we just described with Data Liberation, this is then binding it into, you said theme. I’m going to go with blocks in my definition here.

For example, where there’s a paragraph. Inside the block editor, we would see a paragraph block. And if it was an image, we’d see an image block. And I guess if there was something on the left and something on the right, we’d see a, I don’t know, a group block or something like that. And the design would trickle down from there.

The tool itself would make assumptions based upon what it, I’m doing air quotes, sees. And then it would build it inside the block editor. But curiously, you said theme, so is it also building a theme in the background to take care of all the other, I don’t know, the headers and the footers and all of that kind of stuff as well?

[00:11:10] Chris Huber: Yeah, it is materialising an entire WordPress site from scratch. So the importer does take a URL, but how we’re using it in our tools is we are combining it with data liberation first.

So data liberation gives us that clean copy of the website. So the URL actually goes through data liberation, and then we take the portable copy created by data liberation, and import the whole entire website into WordPress. And it turns this static website into a WordPress site.

So it’s not just about URLs. It’s also about like AI generated websites that you might have on your computer that you might have generated with Claude or Codex. And you want to use it on WordPress. It’s traditionally been pretty hard to get a high quality block theme from an AI agent without a lot of iteration.

So this kind of sidesteps that need to iterate on the block theme, and pull your hair out with the AI who doesn’t understand so much about how to create a good block theme. And you just don’t bother with that, and you just convert it into a block theme on its own.

The point of it really is removing the responsibility from the AI to create the block theme.

[00:12:14] Nathan Wrigley: Okay. So the way that you described it, it sounded like, forgive forgive me if I’ve misunderstood this. It sounded like you use the tool, and we’ll get into how that works properly in a minute. You use the tool. You paste in a URL, that could be a locally hosted website, or it could be something out in the wild on the internet.

And then the data liberation part of it spins up. And then it sounds like there’s a blob of data somewhere, which the data liberation tool finally exports. So it does its bits. This blob of data is then consumed, and we can discuss what that is. Is that a plugin? How does that even work?

And then once it’s parsed that blob of data, then it can figure out, okay, this part belongs in the header, this part belongs in the footer.

This part is the main content area, this is the homepage. And so on. How does it do that? How does it shatter out particular URLs? Like this is the about us page. Or do you have to do it page by page? About, home, archive? How does it do all that? Is it literally one URL and it goes around and spiders the whole thing?

[00:13:13] Chris Huber: It crawls every page on the website, the data liberation part does. But I think of the importer almost like a giant funnel and like a sorting mechanism. And it’s very much mapped to Core, WordPress Core. So I built the whole thing’s built with AI and just basically like over time mapping different elements on the page to Gutenberg, while having the AI read Gutenberg Core directly, and read the source and make its own mappings.

And the whole thing is just a series of import, a website, see what breaks. I pull it up on my screen, side by side. And I’ll be like, all right, this looks wrong, like this and this. And then you just run it again. And I wrote a prompt basically, an AI orchestration prompt that teaches the AI how to run this loop, like for a long period of time.

So how I’ve built it is I’ve basically just given the AI a URL, and had multiple sessions going side by side, working on different types of URLs. And they just run, and open pull requests.

The assumption that a lot of people would make about something like this is you take the HTML site and you tell the AI how to build the block theme from it. We’re not using the AI to do that. We’re using the AI to improve on the importer. So that every time we run an import, it raises the floor just a little bit. So the more sites that you run through it and loop on it like this, the better quality overall you’re going to get for just a random, arbitrary website that you might feed it.

So it’s really just about data annotation, and taking as much as you can in finding ways to parse it without having to look at it.

[00:14:41] Nathan Wrigley: Does the tool phone home. So the way you described it there was, it sounds like there was an opportunity to improve the tool for yourself on your install. But I was wondering if it phoned home so it also at the same time, improved the tool for everybody else so that the next version of the tool is better for everybody?

But I’m going to guess that it is just working locally. It’s improving your version each time. But I could be wrong.

[00:15:05] Chris Huber: So the prompt I share with my coworkers, and we all use it to work on the tool, so it’s more of a development thing is how I’ve built the tool is just by importing a tonne of different websites, over and over again. But the way I have it set up on GitHub is every merge to main automatically releases a new version and updates all the pins.

So the latest release is always the latest work that I’ve done. So, I get to benefit from the changes right away. As soon as I merge the PR, it’s in a new release and I can just keep going. It’s just not on wordpress.org yet, or anything like that.

[00:15:37] Nathan Wrigley: So how do we actually get hold of the tool? I’m going to link to a, a GitHub page, but just reading it into the record, it’s actually a fairly straightforward url. It’s github.com/automattic. You know the one with the two T’s, and then static-site-importer. You can go over there.

How does it work? You download it. You run it locally on your machine? And then once that’s up and running, what do you see? Is there like a GUI that you have to run through? Is there a WordPress plugin component to it? Just describe the workflow.

[00:16:07] Chris Huber: Okay. Yeah, so the Static Site importer is a WordPress plugin. And anyone can instal it on a WordPress site to turn a website into a WordPress site for sure. Using the command line locally. It works in the browser too, but there’s no UI. It’s like API based, so you’d have to call the API to do it or the CLI.

Another place to use it and the easiest, probably the easiest place for anyone listening, to try it other than Riad’s website, is WordPress Studio. I added a tool to the CLI in WordPress Studio. That is, studiocreate-from. And then you can enter a URL. So it’s just one CLI command, and that orchestrates the whole thing in the background. Loads the Data Liberation agent, and then installs Static Site Importer on the site.

You run it once you wait 10 or 15 minutes, and it spits out a WordPress Studio site that’s built using this tool. And that is the same way we run it on wordpress.com. Riad’s tool, the liberate.sh is a, it uses the wordpress.com API, which works the exact same way as WordPress Studio, where it loads Data Liberation Agent.

And Riad’s website gives you a copy of the website that you can download and take with you, anywhere you want. A WordPress website, anywhere. You can host it anywhere. but it’s all using the same wordpress.com API on the backend. Except in WordPress Studio uses the actual tools, does that make sense?

[00:17:21] Nathan Wrigley: Thank you. That’s great. And so how successful is it? If you point it at google.com, it’s probably going to a fairly easy time with it because there’s not a lot going on. But, i’m imagining on a, let’s imagine that you went to some high-end sports website or something where they’ve got animations of people and videos, and all sorts of stuff going on.

How does it hold up? For paragraphs and images and all of that kind of stuff? I’m guessing it’s pretty good. Are there any areas where you’d need to be a little bit more mindful? Because, I don’t know, just experience shows it doesn’t work out so well.

[00:17:53] Chris Huber: Yeah, definitely. So if you’re watching it today, there might be some failures on things like stores. Things that have a lot of products and like really image heavy websites might have problems as well. And just like really large websites. But it gets better every single day. What I say right now might become outdated very fast on what we can and can’t handle, but it definitely is not like perfect yet, for sure.

A small website, like a one page brochure website, or five pages or so. Most of the time you’ll get a pretty good copy of it. If you start to scale up to a really big, large, for example, wix.com, like the actual Wix.

[00:18:30] Nathan Wrigley: Good luck.

[00:18:31] Chris Huber: I sometimes will run that through there as a way to see how far I can get. Yeah, I’m trying to reach for the stars. So eventually I would love to be able to import this 50,000 page heavy duty, old school website, but right now it fails miserably, and it would take. The timing that was given to me last night when I was working on this was like two weeks. You’ll have a copy of wix.com, if you just let it run. And then you’d get the copy and it would just be like 10,000 pages of nonsense. We have a lot of work to do.

[00:18:59] Nathan Wrigley: Okay, but for a normal, typical, run of the mill, let’s go with brochure site, 12 pages, fairly ordinary stuff. Imagery, maybe a video here and there, but mostly text, CSS, maybe a tiny smattering of JavaScript sprinkled around. Forms, that kind of thing. It would do a pretty good job with that out of the box?

[00:19:17] Chris Huber: I would say like more than half the time you would get a good editable WordPress website. Not always perfect. And sometimes you would get a perfect site. But a lot of times you might have a few things that are wrong, like maybe a couple form fields, or like buttons or like menus.

One thing that happens a lot is like the header and the footer are like duplicated across every page, instead of being properly extracted into a template part. If there’s like SVG images, WordPress has a kind of a hard time handling those. So we have dealt with it. But it’s not always perfect.

One of the coolest things about it that I like is that blocks, so it’s static site importer is the WordPress plugin that creates the WordPress site. And then there’s a PHP package inside of it called Block Engine. Which is what handles the actual, like, mechanics of converting and creating the blocks.

And inside of that tool I have added some like carried blocks that are in the holster ready to go, like for common elements that might appear on websites in the wild.

So like a marquee or something like that. Like a ticker that you see running across a page that Gutenberg cannot represent on its own, out of, the box. And so this tool, it knows how to build this block as if it was part of Gutenberg, so that you’ll see a real block in there. That’s my WordPress nerd favourite thing about the tool. It feels like I’m pushing on Gutenberg, finding places where Gutenberg is like maybe falling short, or just doesn’t supply the things that people need to build websites. With the right amount of attention, this might help be like, oh, we need to add some of this stuff.

[00:20:48] Nathan Wrigley: A curious question, because we all know how AI never gives you the same thing twice. I was wondering if you fed it the same URL, do you predictably get something similar out? Or do you suffer each time a different set of, and I’m doing air quotes again, failures. So for example, you described, the SVG images, or the form fields, or the footers being duplicated or whatever it was.

Is it sometimes better just to begin again, and cross your fingers and hope that the AI has a better go the second time around? Or is it always a case of go with the first version and iterate from there?

[00:21:22] Chris Huber: So it works the same exact way every time. The actual process does not use any AI at all. I used the AI to build it from the outside. But the actual, It’s literally like a machine. The process doesn’t use any AI to convert the website. We have some stuff in place, like when we’re using it on wordpress.com. We’re doing migrations from non WordPress to WordPress sites, we do it for assisted migrations currently.

But the people running these migrations will use the tool first and see how far it gets them. And then they take Claude Code or whatever and they work on the site that came out. And they hand it over to the customer. So it gets them closer to the finish line than they would have gotten if they just had to start building the site from scratch on their own.

And then over time we’re getting closer to the finish line, and hopefully get to the point where we can just hand people the website coming from another source and be like, here’s your exact copy of your website WordPress version. And eventually we will make that like a publicly available thing. But that’s how we’re working on it internally, so.

[00:22:21] Nathan Wrigley: So I think I’d misunderstood there, so the AI portion is in the creation of the tool, but the tool itself is deterministic. The tool will give predictably the exact same thing out. If you give it the URL, it’s going to parse it with a mechanised approach? It’s not relying on AI at that point. And so do it once.

And then it sounded to me from the way you described it, you were holding your hands up at this point. It sounded like your had two screens open. You’ve got the output and then maybe the original. And you’re trying to iterate and just spot the errors. Okay, let’s scroll them both and see. Ah look, that’s gone a bit astray there.

And then presumably at this point you’re logging into WordPress. If it can be done inside the block editor, you’re doing it there. But it also sounded like you are now at .com. You are removing that part even and just doing a second run with AI at that point. Rather than logging into WordPress and using the block editor, it’s more CLI. Let’s just see if the AI can spot those mistakes, because I spotted them, prompt it and fix it in that way. That’s interesting.

[00:23:21] Chris Huber: So I’m the one just building the tool. There’s other people working on delivering websites to customers and stuff internally. But, I started looking at the websites originally, but now I have a, I just have a prompt that I copy and paste to the AI every time and it walks through the process.

And what it does is it loads both sites in a headless browser called Playwright. Basically, I have the AI look at the site as if it was the site owner. I say you’re a non-technical site owner. Open this site and look at the Gutenberg editor and see how you would feel if you came over from Wix and this was what you got.

It’ll go through and click things around in the editor and be like, okay, here’s my feedback. And then I say, okay, fix everything all at once and open pull requests. And it will fan out subagents, 10 or so at a time sometimes, and open pull requests in three repos, and then I just merge them and run it again. Because the automated releases that I mentioned.

So it’s very much trusting the machine and letting them. The machine in this case is, more able to parse this than, than a human is because it’s so much at once. And just letting them do it is what I’ve found. Describing to them what I want them to do.

[00:24:26] Nathan Wrigley: I’m guessing the onboarding team over on .com, presumably, if you roll the clock back a couple of years, this was all a very manual process. Find a client, get them to sign on the dotted line. Okay, they’ve got a.com account, now they want to move over. And then it would’ve been a process of, okay, let’s inspect the site, let’s get a bunch of technical people on it, and figure out what we need to migrate and when, and try to map it. Get a designer in and recreate graphics, and colour palettes, and brands and all of this kind of stuff. But it sounds like these people no longer have a, place because you just use the tool and in most cases it’s going to work.

Has that in fact been the case? It sounded like over on the .com side of things, there’s like this, I don’t know, 90, 95, 99%, trust in the tool now. That must be incredible. Presumably you can onboard people much more rapidly.

[00:25:14] Chris Huber: Yeah, it’s not quite that much of trust in the tool yet. It’s more one in 10 sites are getting close enough to the finish line to just be handed off. So like the original process that you mentioned is a good process for like a big site, like manual migrations and stuff. But for small sites it’s not really a good business model. It’s not economically viable to spend a lot of resources rebuilding a small website because you’re putting a lot of manual effort into one website.

So what we would do mostly in the past would be, if the customer is willing to do the do it for me route, where they have our team build it for them, we would do that. But otherwise we would offer them a content import. So they can just import all their blog posts or whatever, and then rebuild the site their own.

This kind of gives us an option for people that were historically told no, that we can now start saying yes to them. And letting them migrate over. It’s not necessarily about reducing the labour that was going into it because it was a dead end before, and now it’s not.

[00:26:10] Nathan Wrigley: And how has it been received over on the .com side of things? I’m presuming that you are in touch with these people. And even if it’s a one in 10 at the moment, we have expectations that it’ll be two in 10, and then three in 10, and by the end of next year, maybe nine in 10 or what have you.

That gives them the opportunity to talk about other things with the clients that they’re onboarding, I suspect. Instead of just, okay, let’s figure out how to make the exact same website that we had over there, over here. That doesn’t feel like necessarily interesting work anyway.

[00:26:36] Chris Huber: Yeah, exactly. But it was always really hard to make the exact copy. And yeah, the tool has a lot of internal support and a lot of internal attention. People are rallying behind it. It’s basically what I’ve been working on full time since WordCamp US. Three months ago now.

So I’ve been putting full-time effort into this tool for three months now. And now it’s starting. We have a lot of momentum behind it internally now that it’s starting to get to a point where it’s actually good. It’s very cool to see this for myself. I’m very proud of the work that we’ve done. And it’s exciting. It’s just exciting.

[00:27:06] Nathan Wrigley: We mentioned that there were some things that it didn’t do particularly well. Presumably it would be nice to be able to hoover up some of that in the future. What would be the roadmap items that you’ve got for the next, I don’t know, short period of time, month, two months, six months, whatever it may be. What are the bits that it can’t currently do, or the bits that there’s wrinkles in, that you could tell us about that hopefully, given the passage of time, will go away?

[00:27:30] Chris Huber: The more complicated stuff is like, installing another plugin when you’re materialising the website. So the the most obvious example is WooCommerce. If we’re detecting products in the source, we actually pre-install WooCommerce, and convert to WooCommerce blocks, and import actual products into the catalogue, and like wire up everything that we possibly can.

[00:27:50] Nathan Wrigley: That’s amazing.

[00:27:51] Chris Huber: It’s crazy, but it doesn’t work very well yet, because it’s very complicated. But, another thing is like is like events. Like an events calendar on a website, the tool kind of chokes on that, but it’s the same process. You install The Events Calendar plugin. You find the most widely supported and used WordPress equivalent of whatever feature you need, and you find a way to deterministically wire it up on the back end.

There is a WordPress equivalent for like most things. It’s just a one at a time process to pick the one that, at least for .com. The tool itself is composable. So any developer. For forms, we use Jetpack Forms. But any developer can hook in and do whatever form provider they want, if they provide their own mappings to the tool. That’s the kind of stuff that doesn’t work quite as well right now.

And, of course JavaScript animations and other things. WordPress has the Interactivity, API, so we do use that. More and more core blocks are coming in. Like we have the tabs now in the accordions and things like that, that we can actually represent in Gutenberg more effectively now.

The real solution is just keep importing sites, you find that the tool used to choke on, it doesn’t choke on anymore, and you get further. And you just keep getting further and closer to success. The only thing it chokes on, this site is the products. Okay, so we’ll just work on improving the WooCommerce integration.

Yeah. So it’s like almost as far as you can get and then just keep. I like to think of it as raising the floor, like raising the bar is like. This is as bad as it could possibly be, and then the next time it’s a little bit better.

[00:29:18] Nathan Wrigley: And it sounds like it’s going through those iterations fairly rapidly in terms of time, what three or four years ago would’ve been years into the future now increasingly feels like months, and then weeks, and then finally in a few years time, maybe days. A lot of this stuff will be taken on in short measure, things like an events system, or a WooCommerce system or an LMS kind of system. Maybe that stuff will be in scope in the near future.

The project, obviously being on GitHub, and being a WordPressy thing is open source and I’m, just curious whether or not you are doing this hand in hand with any other people? Or is it just a project within Automattic? Or are you getting kind of intuitions from WordPress agencies out there who are obviously having to do this kind of work?

They’re bringing in clients from all over the place and trying to convert them over to WordPress. I just wondered if there was any collaboration going on, or do you wish there to be collaboration?

[00:30:12] Chris Huber: I think something like this should be part of WordPress Core. I don’t know that necessarily this exact tool or this approach. There’s a lot of work in the ecosystem around this area, like Human Made has a tool like this. And then Pascal from WordPress Core, is working on this in Gutenberg, not the exact same thing, but some way to convert HTML to blocks.

And I just think it’s a big challenge for the WordPress ecosystem that if it gets solved can help move the whole project forward and help make us more future proof. Just because AI is so good at generating HTML, and that’s what kind of becoming the native format of the internet now. Maybe always has been, but just making that translatable into WordPress is something important I think.

[00:30:53] Nathan Wrigley: Yeah, I think so. And obviously in an era where market share in the WordPress space is no longer seemingly guaranteed to just keep climbing. People face with that decision of, okay, I’ve got a website, it’s now starting to look a bit stale, but rather than throw the baby out with a bath water, we’ll, okay, we want an alternative CMS. We want to upgrade, see where we can go. It feels like a tool like this makes WordPress a bit of a forerunner, actually.

If you’re going to pick a CMS, have a CMS where there’s a pretty good chance that by clicking a button you can bring most of your existing stuff across. I don’t know what the other CMSs do in that regard. Maybe they do nothing, but this does feel like a tool in WordPress’s arsenal, which is pretty compelling. I would hope that it would bring a lot of people in our direction.

[00:31:42] Chris Huber: I hope so too, and I agree. I think the fact that it can exist. It takes one of the points of WordPress that has been difficult for people to embrace, which is the block editor. And it almost turns it into an advantage. Because then you get a WYSIWYG version of every website. Whereas if you were to generate a static site with AI and go and host it on a static host, you don’t have the CMS. If you want to add another blog post, you have to generate the page, upload it to the site. And of course there are solutions to this.

What if you just want to change one word? You just want to go into the block editor and change the one word. Then you can do that and like without having to build the whole page from scratch in the editor. You have to be good at it and know what you’re doing to build a custom website using the block editor, I think.

[00:32:26] Nathan Wrigley: This is going to be a discussion which will go on, I think in the days, weeks, and months to come. Obviously everybody at the minute is very beguiled by the interface of building a website through some kind of chat mechanism. It’s so fascinating that’s possible.

But then the reality of maintaining that, and understanding how that page even got there. And where do the assets, on that page even live? And how do I modify the title of the hero section over here? All of that has yet to land with ordinary people. Again, doing air quotes.

[00:33:04] Chris Huber: Yeah.

[00:33:05] Nathan Wrigley: If you’re very technical, you can probably figure all that stuff out, because you were probably the person that created that AI based site anyway. But if you’re not technical and your job is just to occasionally modify content, or inspect somebody else’s content, and click publish when it met the guidelines that you’d got as an organisation. You’re not going to care about some sort of CLI interface or getting an AI to do that for you.

You just want to be in, out, and then move on, because WordPress is not what makes up the majority of your day. I think all of that stuff is going to hit us in 2027, and it’ll be interesting to see where we land and where the landscape moves.

[00:33:41] Chris Huber: Yeah, I hope that we can continue to grow WordPress definitely.

[00:33:45] Nathan Wrigley: Okay, that’s really interesting. I’ll read into the record one more time the tool itself. So github.com/auttomatic, two ts, /static-site-importer. You can go over there and make comments. It’s a GitHub page so you can do all of that normal stuff.

If people wanted to find you, Chris, do you hang out online anywhere? If people wanted to contact you and had intuitions on where this should perhaps go in the future?

[00:34:11] Chris Huber: Yeah, they can reach out to me on x x.com/chubes4, C-H-U-B-E-S four. They can also find my GitHub, which is the same tag. I have my personal WordPress site at extrachill.com, is like my main site. Then I have my other one, chubes.net. Or, just leave a pull request or a GitHub issue, me or my AI agent will reply.

[00:34:33] Nathan Wrigley: This is how it is in the year 2026.

[00:34:35] Chris Huber: Yeah.

[00:34:37] Nathan Wrigley: Okay Chris, absolutely fascinating. Let’s hope that the tool manages to do a lot more than you’ve described. It sounds like you’ve got a very extensive, and interesting, roadmap going on, but thank you for bringing that to us and, thank for explaining it all to us today. Appreciate it.

[00:34:49] Chris Huber: Yeah. Thanks for your time. Thanks for having me.

On the podcast today we have Chris Huber.

Chris’s journey with WordPress began back in his college days, first as a writer and blogger and eventually progressing to software engineering. After moving his personal site, extrachill.com, to WordPress in 2018, Chris went deeply into WordPress, developing custom plugins and exploring all the corners of the platform. His passion for experimentation and creative tech led him to Automattic, where he now helps shape the WordPress experience as a software engineer.

Our discussion centers around two main topics: Data Liberation and the Static Site Importer tool. We focused upon the evolving landscape of website migration and ownership. Chris explains how Data Liberation aims to make it easier for users to take control of their site, whether they’re moving to WordPress from platforms like Wix, Squarespace, or Drupal, or just want portability for their data.

We also get into the Static Site Importer, which takes this a step further by converting any static HTML / CSS website into a fully editable WordPress block theme, headers, footers, and all.

Chris walks us through how these tools work in tandem, highlighting the mechanics behind website crawling, mapping HTML elements to Gutenberg blocks, and handling complex features like WooCommerce and calendars.

We talk about the continuous improvement of these tools, how each migration helps raise the bar for future imports, and how this project could fundamentally change the way people move websites between platforms.

If you’re curious about the future of website migration and how WordPress is removing the hurdles for users who want to truly own and manage their content, this episode is for you.

Useful links

Chris’ extrachill.com website

Chris’ chubes.net website

Static Site Importer on GitHub

WordPress Studio

Data Liberation Project

liberate.sh website

Chris on X

💾

#237 – Robert Abela on WordPress Security and the Battle Against AI Threats

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, the state of WordPress security in 2026, and the battle against AI threats.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you, and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.

So on the podcast today we have Robert Abela.

Robert has been working in IT security for 25 years, ranging from antivirus software to web security scanners, and for the past decade has been running Melapress. A company focused on WordPress security plugins, particularly around user visibility, authentication, activity logs, and 2FA.

Robert is here to talk about the 2026 WordPress security survey. This is an annual project now in its fourth, or fifth, year gathering data from a wide range of WordPress professionals across agencies, enterprise teams, freelancers, and product owners. The conversation today is focused on the biggest security challenges and trends facing WordPress users in 2026.

We start off with some sobering stats. Over 67% of survey respondents reported experiencing at least one security incident in the past year, and concerns about WordPress security remain high, especially among less technical users.

We chat about the disconnect between awareness of security threats and actually taking steps to mitigate them, such as breach recovery plans and team training.

The discussion also explored the different types of risks that worry site owners. Site downtime, defacement, reputational damage, data loss, and even legal compliance issues. How the shakeout depends on the type of site, whether it’s e-commerce membership, a news outlet, or a simple brochure site.

We also talk about the tendency for even experienced WordPress users to take a reactive approach, only addressing vulnerabilities after something has gone wrong.

Towards the end of the episode, we discuss the rising impact of a AI on security, the explosion of AI facilitated vulnerabilities, and the shifting landscape of risk and response. There’s a healthy dose of reality, some optimism about the tools and best practises available, and plenty of good advice, especially for smaller teams and freelancers who may not have access to enterprise level resources.

If you care about keeping your WordPress sites secure, or want to understand where the community’s biggest concerns and opportunities are in 2026, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast where you’ll find all the other episodes as well.

And so without further delay, I bring you Robert Abela.

I am joined on the podcast by Robert Abela. Hello, Robert.

[00:03:48] Robert Abela: Hello Nathan. Thanks for having me.

[00:03:50] Nathan Wrigley: You’re very welcome. Nice to have you with us.

We’re going to chat today about internet security, but we’re going to be looking back over the past year, so the year 2026. Robert, can tell us a little bit about the company he founded, works for, and so on. It’s called Melapress, you can find out about that in just a moment.

But I would like to draw your attention to something which is going to really be the fulcrum of what we talk about. It is their 2026 WordPress Security Survey. Now, the easiest way to get that is probably to go to wptavern.com, search for the episode with Robert in it, and I will make sure it is linked in the show notes there.

But it might be a good idea to read it, because in about 10 minutes, you’re going to be able to capture absolutely everything that we’re talking about today, and you’ll get all of the data and, what have you. But that’s going to be the point of this episode, summarizing what happened in the security space in WordPress in 2026.

Robert, I guess there are a few areas in the WordPress space where it’s pretty important to know that we know, that you know, what you’re talking about when it comes to security, because we don’t want to have a lot of hot air from somebody who’s not experienced. So it’s an opportunity for you really to give us your bio and tell us a little bit about what you’ve been doing in the WordPress space, particularly around security, the companies you’ve worked for, the things that you’ve founded and so on. So over to you, Robert.

[00:05:07] Robert Abela: Thanks. I’ve been working in IT security for twenty-five years. I’ve always worked for software companies, software startups which worked in security industry. We used to do antivirus software, web security scanners, et cetera. I’ve had different positions. I started as systems engineer, QA, product management, project management, almost any field.

Anyway, and the last ten years I founded Melapress, and it’s a WordPress plugin business, and basically we develop a number of security plugins for WordPress. The security we do, we don’t do the typical firewall malware, et cetera, like the other, brands. We mostly focus on user visibility and authentication. So basically we have an activity logs plugin, and we also have a plugin for 2FA, passkeys et cetera. So we are focusing much more, on what happens post login once someone logs into WordPress, rather than the whole hardening and protection.

[00:05:56] Nathan Wrigley: Thank you for that. So anybody that’s interested, anything that we mention today, including the URLs of the companies that Robert has just mentioned, so Melapress, you’ll be able to find those in the show notes as well.

So the 2026 WordPress Security Survey, how many times have you actually run this? So obviously we’re looking at the 2026 version. Have you done this a couple of times and refined the way that you’ve done it and the way that you’ve surveyed over many years?

[00:06:21] Robert Abela: Yes. I’m not sure if this is the fourth or fifth year. But yes, we do every year, we’ve had more respondents. This year, by the way, it was the highest ever with 219 respondents. We had more, but before we publish all the results, we go through the sheet. Maybe there are some duplicates. Maybe some of them are not correctly filled in, et cetera.

But yeah, we’ve been doing it for around four years, and we’ve also fine-tuned from where we gather the data. For example, the first year, we’re only sending our newsletter basically, but this year we’ve done a lot. We’ve promoted the survey through third parties. We’ve gathered responses from WordCamp Europe, in person, through a number of other conferences, et cetera.

So while there is still a percentage that most probably are our users or our clients, still the biggest percentages is spread out to a wide range of different type of WordPress users, ranging from people who work for agencies, developers, designers, but also people who work with WordPress in bigger enterprises or businesses.

[00:07:15] Nathan Wrigley: Okay, so yeah, caveat emptor. With that in mind, the limitations, or otherwise, of the numbers that you’ve got represents what you’ve got in this survey.

And essentially, what it boils down to is a, it was kind of a bunch of questions which then led to a bunch of information being spat out the other side. And I’ve summarized it into about 10 bullet points. It may very well be that I’ve missed a few bits and pieces, but be interesting to go through, and you can lend your experience as to whether or not there’s been any change, whether things have got worse, whether things seemingly have got better.

We’ll begin, if it’s okay with you, with the top item, which I suppose, came out, which was a concern around WordPress’s security, or the things that can happen around WordPress and security. And what came out of it was that 7.85 out of 10, so 78 and a half percent, I suppose you could describe it as. They were developers who were expressing basically that they were concerned.

Now, I don’t know if you have more telemetry, like what concerned means, but off the face of it, that seems like quite a high number. If the platform that you’re using to build websites, you are in the sort of mid-70s concerned, is there anything you wanted to add to that or is that just the sort of top level statistic?

[00:08:28] Robert Abela: No. That was like a top-level statistic, a question we ask, like if people are concerned or they have worries about their WordPress, the security of their website.

What’s funny is the last few years, the level of concern has been the same. However, also we’ve noticed that people who have some sort of recovery plan, et cetera, also remains the same. So the level of concern has remained the same. So the majority of people know that something can happen to their WordPress website, especially now with AI, et cetera. It’s even more, things are moving much faster.

However, it seems like people are not taking the next step, as in like taking action to make sure nothing happens. What I’ve noticed as well, once we break down those who have concerns and what job they have, if they’re developers, or with their security people, et cetera. There’s this correlation, like, the more informed someone is, the more is involved in the tech aspect of the website, the more understanding they have on how things work, the less concerned they are.

So maybe it could also be education or awareness because of course, if you don’t know about how something works, then of course you are much more concerned. How you’re going to protect it? However, if you are, let’s say, a developer and has an understanding of sessions, cookies, the usual things, like passwords, maybe you’re a bit less concerned because you feel you are a bit more in control of how you can protect your website and what you can do.

[00:09:39] Nathan Wrigley: It seems like on the face of it, I should say, it seems like 78%. It seems like quite a lot.

[00:09:44] Robert Abela: Yes.

[00:09:45] Nathan Wrigley: If I had any kind of intuition, let’s say I was to go out into my car and drive around the street, if I thought that 78% of the time there was going to be some potential accident. Or I was worrying of the time about the possibility of an accident, I don’t think I’d be getting in the car. So it’s kinda curious. But, let’s move on.

So the next data point that dropped out was 67.7%, so let’s call it 68% of respondents. Now this is fairly shocking, and maybe this number will actually start driving up in the years to come, and we can get into that later.

68% of respondents had experienced at least one known security incident, with many multiple incidents. Now, that really is shocking to me. Closing in on 70% of people have had some kind of incident. I don’t know what, or maybe you do, what the magnitude of that is, but did that surprise you? Did that seem like a really large number?

[00:10:38] Robert Abela: 67.7 of all respondents, correct, they reported one security incident. I’m not surprised because almost everyone I speak to at WordCamps, even non-WordCamps, other events, someone down the line has had some security issue. Not just with WordPress, but especially with WordPress. And the funny thing, it’s not even funny, but 13.2% of those are repeat targets, which means they have experienced more than five security incidents.

Now, why does it happen? There are a number of reasons. Outdated software, lack of user awareness. In fact, what’s really more concerning is, I have some numbers here actually I can tell you. Yes, we’re still looking at some other statistics. Only 27.9% reported like they have some sort of training for their users. And only 37% use logs. At least 2FA’s a bit higher, it’s around the 40% something. I don’t have the exact number right now.

So yeah, so I’m not surprised because there is still a lot that can be done from website owners, from agencies, from everyone, to make sure we take down that number, and not everyone. Or so not the majority of people experience some sort of security incident on their website.

[00:11:41] Nathan Wrigley: Yeah, it’s curious. It’s not really a conversation. When I’m at events or chatting to fellow WordPressers, security is not the default conversation that I have, because I’m not a security person. So I end up chatting about, I don’t know, custom post types and how to do various things that I’m doing. Maybe podcasting in the WordPress space or something along those lines.

You, I guess, are having these conversations, and it’s very much in the territory. It’s in your wheelhouse. And so maybe it’s not a surprise to you that 67-plus percent of people have had something in the last year. But, on the face of it, that just seemed like so many. If I see 1,000 people at a WordCamp and I think, “Well, 670 of those have had a problem during the course of this year,” gosh that really does seem like a systemic problem.

And I know that outside of the WordPress community, WordPress gets a bit of a hard rap, on the security front. It’s insecure and what have you, and, all of the caveats. We know that really isn’t typically the case for WordPress Core. Tends to be the addition of code and plugins and themes that adds that on top. But I’m still surprised, feels almost like if the mainstream press got hold of your survey and just pull out that one statistic and bandy it around, it doesn’t feel great, if you know what I mean.

[00:12:53] Robert Abela: Yes. I think WordPress gets a lot of bad rep also because it’s very popular. As in like pre-WordPress, I’ve used web servers before as in like custom PHP websites, .NET, IIS, Apache, et cetera. Websites used to get hacked as well in the thousands. The thing is that you couldn’t point your finger to one type of website, you know because they were all custom. So these problems have been happening since we started having websites, quite frankly.

With WordPress, unfortunately it happens and we have a bad rep because I think there are two things. Look, first of all, it’s very popular, so it’s always there. If WordPress power is around 42, 43% of the, or maybe it went a bit down, but anyway, let’s say 40%.

[00:13:30] Nathan Wrigley: Roughly, yeah.

[00:13:32] Robert Abela: Yeah, The chances, for every 10 websites, four of them are going to be WordPress. That’s a common denominator. So of course, WordPress is going to get a lot of attention.

I also think, again, goes hand in hand with how many people have security concerns. WordPress has made it very easy to launch your own website, which is a good thing. However, of course, those same people who launch their own website, maybe they don’t have the technical understanding and experience what it takes. Because setting up a website’s one thing, but keeping, managing a website for a year, two, three, and growing it, adding new functionality is another thing. So most people might not have the experience that they have, so of course, it’s much easier to find security issues with these type of websites.

[00:14:10] Nathan Wrigley: Okay, we’ll move on anyway. So we’ll talk about the concerns. So you’ve obviously polled your recipients of the survey about the kind of things that they were worried about. So what are the outcomes that they fear the most, if you like?

And website availability, so the taking down of a website came in at number one, with 55.8. And then in no particular order, but these are the two that I picked out. The fear of being defaced, so the website in some way being amended, or there being some reputational damage because of what the amendment was. I don’t know, maybe there was some imagery, or some slightly political content that ended up on your website.

That was just slightly south of the availability, so that was 54.2%. And then dropping a full 10%, so 46.4%, was the worry about data theft or loss. Frankly, I’m not surprised by that. I guess any developer’s nightmare is their website actually disappearing off the internet. That’s number one, so that doesn’t surprise me.

I remember in the day, 15 years ago, defacement was the thing. Honestly, I can’t say that I’ve been browsing the internet recently and seen something that’s been defaced. It seems like the hackers have all moved on. Maybe there’s things buried in the source code that I don’t know about.

Yeah, it doesn’t surprise me that the availability is the main thing. But I am surprised that data loss comes in third, if you like. I personally would have had that as number one, especially, if you’ve got a, I don’t know, an LMS, or you’re connecting with a CRM, or you’ve got form data which potentially is capturing something personal that the GDPR would worry about. So there’s no question, just if you want to comment on those particular things, go for it.

[00:15:42] Robert Abela: No, definitely. Those are the numbers based on all the respondents. But if you start breaking down the numbers, there’s more nuance to, to these things. So for example, if you look, those who are concerned about website availability, or defacement, are usually those who have content websites. Mostly based on content, news, magazines, et cetera. Those who are more concerned about financial loss or data theft are more the e-commerce websites.

[00:16:08] Nathan Wrigley: Oh that makes sense. Yeah.

[00:16:09] Robert Abela: The membership websites, et cetera. In fact, the membership websites are as well more concerned, for example, about compliance because of privacy. So those numbers, like fifty-five point eight percent, those are from the all respondents. But as soon as you break all that down, it differs a bit on the type of website you have.

And it’s expected because if you have an e-commerce website, of course you are dealing with billing details, payments, and all this stuff. If you have a membership website, maybe you are also dealing with payment details, but you are also dealing with much more data. Maybe you have some sort of internal chat. People are sharing their addresses on it, their personal information. So that you are more concerned about GDPR or any sort of compliance, et cetera.

But if your main selling point is if you have a content website, a news website, and your main selling point is your website being available, then of course that is your biggest worry.

[00:16:53] Nathan Wrigley: That’s an interesting split of the data there. That makes perfect sense, of course, now that you say it in that way it really is obvious.

So that was you polling your respondants respondents there, and you were trying to figure out what their worries were and what they were into and all of that kind of stuff.

And then we sort of to move to a different realm where despite all of that being said, so, you know, got a lot of people worried. We’ve outlined some of the different worries that they have, depending on the type of website that they’ve got.

From all of that, if you’d have ended the survey there, I would have assumed at that point that everybody had something in the back pocket to pull out, an SOP or something like that, to pull out in the event of an actual problem. If data theft is apparent, we do this. If the website goes down, we do this. But your survey reveals entirely the opposite.

So the high numbers on the one side, the fear numbers, are not mirrored by the what we’re going to do about it numbers, because you go straight into the high 20s, so 27.9% had a breach recovery plan. So how to get back from a problem with your website being, let’s say, hacked, let’s use that word. And 26% provided some sort of training for their team, some sort of security team training, that kind of thing.

Again, does that surprise you? You’re in this space. Maybe that’s really typical, but given the high levels of concern, there seems to be a real disconnect with what we’re going to do about it. That’s curious.

[00:18:18] Robert Abela: I’m not surprised, in the sense, it’s very common. The majority of people, especially nowadays, there’s much more knowledge that, yes, websites can be hacked, this can happen. However, that doesn’t translate. People don’t have the, I don’t know if it’s the resources, the means, the time to actually take action on it, to prepare some things. So, I’m not surprised.

Again, similar to what we discussed before, there’s a bit more nuance to these type of numbers because you said only 27.9% has a breach recovery plan. Actually, that’s based on all the respondents, but typically the number is much less, because when you look at it, from the respondents, from all those who have a security breach, from those 27.2%, 70.2% which have control in place are corporate or brand websites, which means they have their own in-house team. Only those, 70% of those have their own, have their activity logs, have their firewalls in place, have a recovery plan in place, et cetera.

So the number of, let’s say, the non-branded, the smaller websites, yeah, they have absolutely nothing. They have no sort of recovery plan or anything like that. In fact, the numbers are much smaller. Only 23% of those websites typically have some sort of recovery plan.

[00:19:23] Nathan Wrigley: Okay.

[00:19:24] Robert Abela: I’m not surprised because usually, especially if you’re an enterprise, or a bigger business, you are bound by more compliance. Maybe you have more security people on board who are much more aware what can happen of what they need to do. But yeah, the average website doesn’t have these things.

[00:19:38] Nathan Wrigley: Yeah. I wonder if your data here might be skewed by the type of correspondent that you got. So for example, who knows how many blue-chip companies, have submitted to your information gathering here. Perhaps not many, but maybe you got lots of WordPress community members, and so the data might be skewed in that direction. But that’s an interesting point. So dependent upon the nature of the website and the type of team they have behind it.

But it is still, regardless of all of that, it is still quite low. And I was using my analogy earlier about insurance, and I think that applies here. Insurance is the most uninteresting thing to purchase because you spend this money and, let’s say for example, you got home insurance. I would imagine most people typically go through a year and they never make use of it. Sorry to anybody listening who has obviously had to make use of that. But the moment you need it is the moment that you’re glad of every single penny that you’ve sunk into that, and I guess that applies here. If we can persuade people to get that data breach recovery plan, whatever it may be, have that in your back pocket, that would be a useful thing to have.

[00:20:38] Robert Abela: Yeah. As I’ve said in the beginning, I’ve been working in IT security companies, security software companies for 25 years. All of them, the most common sales opening, like sales reason, like people coming to us like, “Hey, this happened, so now I need this.” They’re always after they’ve been hacked, after they’ve been a leakage, after there’s been something wrong.

Very few proactively come and as I said, like the bigger enterprise companies, because they have certain regulations and stuff and certain budgets that they invest in these things. But the average website, yes, first they have to experience something, and then. I think it’s, in all fairness, I think it’s common human nature. It’s not just about IT. We tend to be all humans. We tend to be like, “Oh, we’ll see later,” and then if it happens, “Ooh, I should have…” it’s always like that.

[00:21:17] Nathan Wrigley: Well, there’s also that calculus of how much time does it take to recover. So for example, if you’ve got a brochure site, and you’ve got backups going back for many many months you can restore to a point that you’re fairly sure that everything was actually fine, and the breach has been mitigated by going backwards in time. But it’s just all the wasted time. It’s the wasted time going through the backups and seeing, okay, is this backup, does it have the malware in as well? Okay, that one does. What about this one? What about this one?

And there’s no knowing how long that’s going to be, and the minute you step, as you said, into e-commerce and you’ve got transactions happening every couple of minutes, and then you’ve got receipts and you’ve got to fulfill those orders, and somehow, oh boy, yeah.

[00:21:59] Robert Abela: Yes. Then it’s a different ballgame. Yeah.

[00:22:02] Nathan Wrigley: Different ballgame isn’t it? Yeah.

Okay, so the next point that we’re going to move on to is actually one that you probably just made. And it’s that the detection in most cases, well actually not most cases, in many cases. So 42.6% of your respondents said that their detection is mostly retroactive. So that is to say the thing has already gone wrong. Somebody in the 42.6% of the case is because they see something on the website. They’ve noticed that something isn’t quite right, something looks out of order.

38.4% because they were actually inspecting the logs. That tells me that whoever’s inspecting the logs is doing diligent work. That’s kind of interesting. So don’t know if you want to comment on that, but basically a lot of people are figuring this stuff out after the thing has happened, as you described, not before the thing has happened.

[00:22:51] Robert Abela: Yes. So there are four criteria. So 42.6%, as you said, is common website behavior, either detected by their team or by clients. 38.4 via logs. Now, the logs is a bit, it can be reactive and proactive, because with the logs, you can actually, in fact, we have some notes on this, but I don’t have the exact numbers right now. Because some of them were actually by someone analyzing the logs, but some of them were actually because someone has configured notifications based on the logs, like a sort of intrusion detection system.

And so if, I don’t know, if X login happens after X time, whatever, please send me an email or an SMS, and that, it’s still reactive in a way, but at least they could act right away as soon as it’s happening. Yeah.

[00:23:31] Nathan Wrigley: Yeah kind of proactive reactive, isn’t it? That’s a really interesting subcatagory.

[00:23:33] Robert Abela: Exactly, yeah.

[00:23:34] Nathan Wrigley: Yeah.

[00:23:34] Robert Abela: So yeah, but yeah, it’s still reactive because then you have 35.6% they knew through their web host, and 30% they knew through some sort of malware scanner alerts on their website, et cetera.

[00:23:45] Nathan Wrigley: Okay. Again, just kind of interesting data coming out.

So the next one, incidents most commonly resulted in downtime for the website. So that’s pushing up to 70%, 68.4% of whatever happened, resulted in some downtime. And then I don’t have the numbers for the following data, but I guess it decreases from here.

The next thing was reputational damage. That was a result of some sort of incident. And then search engine ranking is affected. That’s an interesting byproduct.

This one’s brutal. Client trust disappearing. That’s really interesting. And then in some cases, lost revenue. I imagine the lost revenue is being described as in some cases, because, as we described earlier, if you’re dealing with revenue, you’ve probably got more bulletproof security measures in place.

But the ones that sort of jump out to me there aren’t the downtime, because I would’ve assumed that. It’s really the curious byproducts of things like the reputational damage, the search engine damage. You can’t really get your hands on those, can you? There’s no real way of knowing what that’s going to look like or feel like, or how that’s going to affect your business this year or next year.

Just to know that, you wake up one morning to discover that you were in first place on Google after six years of hard SEO work, only to discover that you’re now in fourth and descending fast, that’s pretty brutal.

[00:25:01] Robert Abela: Yes. And in fact, if you break down those numbers a bit more, like 45.9%, there’s loss of search engine ranking, and that happens usually when search engines detect you have issues. I don’t know if you remember, Google used to have that page sometimes.

So that happens. When that happens, when the search engine themselves realise there’s an issue, you lose a lot of rank. The penalty you get there is very heavy. In fact, only 14.5 of those who have had some issues with the website has lost ranking because they have discovered their issues before the search engine did.

So again, that’s why you should be a bit more proactive because if your search engine finds out before you, the penalty, as you said, and you cannot really quantify it because God knows how long you will remain. As you said, if you were position one for six years in a row, now one fine day you’re on the second page, God knows how much work you need to go back up, and you cannot even calculate what the revenue loss is.

But when it comes to revenue loss, again, it’s the same. There are some websites, I’ve seen some websites where like they generate $70,000 per hour. So for every hour down, that’s $70,000 gone.

So yeah, there are lots, and of course, the reputation, on top of the reputation, there’s also compliance and legal consequences, especially in the US. Things are becoming much stricter now. If you had some issue, some customer data has been leaked, you have problems with the law, fines, and other similar stuff. So, the financial damage to all of this, of your website getting hacked, is very high.

Not just the reputation, losing customers, you might end up in court. You might lose your search engine ranking, and that is why most probably it’s a good idea to become a bit more proactive rather than reactive. Or it’s almost impossible to, there is no 100% secure solution, and that is why I think it’s very important to have good hardening, but also good monitoring, the whole process, the whole 360 degrees, the whole cycle.

[00:26:44] Nathan Wrigley: It’s such a curious industry that you’re in because, how to describe this? It would seem, or at least, it would be possible to perceive that this security survey is perfectly aligned with your business goals in a way. There’s loads of problems out there on the internet. There’s multitudes of ways that things can go wrong, and for every one of them, there’s, a WordPress solution out there.

But I know Robert. We’ve met many times before. I get the intuition that’s really not why you’re doing this, although somebody listening to this might have that sort of slightly, I don’t know, cynical approach that, Robert’s just saying this so that he can launch his Melapress products at you. Just put our minds to rest on that score. Why do you actually carry out this survey?

[00:27:25] Robert Abela: Good question. Actually, our plugins only address part of the security. There’s much more when it comes to firewalls, et cetera, that I still say hardening you still need. We don’t even cover it.

No, we do it, honestly, it started around four or five years ago, for me, it was just curiosity. It sounded like an interesting to do. Hey, let’s do a survey, just experimenting, et cetera. And we had very good response, and now we’re just, doing it honestly.

Like I really believe that by knowing, this is not just about WordPress security, about everything else. By knowing where other people are doing it wrong, you will learn from it. By knowing, okay, clearly I can see, for example, as we were saying, like seventy percent, seventy point two percent of enterprise and marked businesses usually have logs, usually have firewalls, et cetera. Maybe we should aspire more towards them and be more like the average website should have a bit more like things like that, and maybe they’re doing something right.

So yes, there is a lot to learn from surveys in general, not just this, any type of survey. There is usually a lot to learn. And that’s why we’re doing it as well, because from the first time we’ve done it, which started really as a curiosity project, we got so much good feedback. And actually the second year people were asking us if we are going to do it. Because yeah, people learn from these things.

I mean, of course there’s the benefit of it, hopefully it will promote as well a bit our plugins. But anyway, it’s going to promote all other type of security solutions. We are not, in fact, the survey is not tailored just for our plugin. It talks about everything. As I said, the whole security cycle. You have the hardening, you have the monitoring, updating, et cetera, and we only do one part of it, the monitoring aspect, basically.

[00:28:50] Nathan Wrigley: Before we move on to our sort of final bit, which I want to concentrate on AI, I’m just going to wrap up the security bit just by summarizing what comes towards the end. And it’s less about numbers, and it’s more about just conclusions that may have been drawn. But most of it, I think, would be fairly obvious from what we said. So I’ll just summarize it a little bit.

The first one is that e-commerce and membership sites tend to have greater security concerns and stronger practices. That kind of makes sense. I guess it reflects the nature of the business they’re in, and the kind of data that they’re holding, and the legal compliance that they may need to be concerend with.

In-house teams are more likely to have recovery plans. Again, I presume that’s fairly obvious. The boss, the head of the pyramid can sit down and say, “Okay, it’s your job now to crack on and do that. You’ve got a week to figure out all this sort of stuff,” and what have you. Whereas a freelancer sitting in their own office, there’s always regular work to be built, sites to be built and other things to do. So I can well imagine why that’s the case.

And sites, again, fairly obvious, sites with repeated security incidents tended to have stronger controls in place. Today, presumably, it’s a case of once bitten and all of that. Once you’ve actually had this nasty stuff happen to you, you’re pretty likely to make sure that does not happen again.

In summary, I suppose the reports really, the recommendations are focus on prevention, detection, and recovery rather than simply adding in more security tools, would be the way that I would describe it.

Okay, let’s move on then just before we finish. It is, as we’re recording this, it’s September 2026. In the more recent past, I want to say, I don’t know, the last two months, something like that, the WordPress security news bulletins have been on red alert really. We’ve had some charts being put out on social media which show the amount of vulnerabilities discovered, and also the amount of AI-based plugins that have gone into the repository. The supply chain attacks that have suddenly become a thing. A lot of it really because people can corral AI to do mischievous stuff and what have you.

I don’t really have a question, but I just wondered if you had a comment on where we are in September 2026, because it does feel as if there’s quite a lot of, there’s a lot of scope to be very doomer at the moment. It almost feels like the AI is winning the arms race, but maybe that’s not what you’re thinking from your end.

[00:31:04] Robert Abela: No, it looks a bit negative. I wouldn’t say AI is winning the race. Actually, people with malicious intent using AI are winning because AI is neutral in a way, like it depends on what people ask the AI to do.

[00:31:15] Nathan Wrigley: Yes.

[00:31:16] Robert Abela: But it is worrying, yes. The graph you are mentioning, I saw a graph shared by John Blackbourn, yeah, about the number of issues reported in the HackerOne WordPress vulnerability program, which is insane.

[00:31:28] Nathan Wrigley: Yes.

[00:31:29] Robert Abela: And they received more reports in the last week than they ever did in a whole number of months. So yes, it is worrying. You can look at it both ways. The same way attackers can use AI to find issues. We are doing it ourselves as well, quite frankly, because whenever there’s a new model out there from all of these vendors, most probably attackers are going to use them to scan our code, et cetera. So we’re doing it as well.

We always used to do the manual security analysis, et cetera, but now that we have AI, with every release, we just hammer the update and try to find as many issues as we can.

The reality is also that some, if not many of these vulnerabilities are not actually so easy to exploit. Like it’s really, the stars really have to align and it’s really, but still, it’s better safe than sorry. Because even though today it might be difficult to exploit a particular issue, in six months’ time, we might have technology that might make it very easy to exploit this type of issue.

It looks negative, but the same tools that attackers have, malicious users have, we have them as well. So it’s up to us to use them and be ahead of the curve, and use them proactively ourselves and before every update, during the whole development cycle. We should use them more often to make sure at least that we cover what other people can find before us.

[00:32:35] Nathan Wrigley: Yeah. I suppose the bit that I find curious is the optics of it. So, there was always this universe in which people would be able to throw dirt at WordPress because you know WordPress isn’t secure, and we talked about that earlier. It’s usually plugins and very rarely Core. Plugins, themes, additional code, what have you.

However, given that it would appear that people can stack 14 overlapping problems and create this one vulnerability from things that probably humans would never have conceived in the past. That then just lends into this narrative of, well there’s this deluge, this tidal wave of things that are coming at WordPress.

So I woke up this morning to discover in my feed BleepingComputer. I don’t know if you’ve seen this one yet today, but BleepingComputer have got an article with a CSV attached to it about yet another WordPress thing. And it just feels like that sort of day in, day out, there’s just another and another, and it’s that narrative that, that concerns me. It’s just that it gets away from us, that there’s one this day, there’s one this day, one this day, one this day.

And having to explain, “Look, calm down. That one was nothing. Okay, calm down. That one was also nothing. Okay, yeah, that one was something, but that one was nothing, that…” It’s just that constant fighting the narrative in an era where every day something seems to be out in the press, a problem that WordPress. Do you capture what I’m saying there?

[00:33:57] Robert Abela: Yes, no, and no wonder we get negative rep in the rest of the IT industry because, yes, we do get these news, and the numbers are very big. If you find a vulnerability in a plugin that has half a million installations, all of a sudden you see the news, “Oh, half a million WordPress websites are vulnerable to X.”

Unfortunately, yes. The thing is, WordPress in general, it’s very secure like. There are so many I’ve seen in my life, I don’t know how many custom web applications I have seen that are horrible in terms of security, like really horrible. It’s just because, of course, no one is seeing these because this might be a website in millions of websites, so no one is targeting. But WordPress, because it’s a popular platform, is going to be targeted.

But yeah, because the numbers are big, yeah, unfortunately, we do have a bad rep. And yeah, the news like to sensationalize things as well. So yeah, the rep is not good, no. But the reality is that it’s going to happen. It’s going to happen more often, most probably. It happened to us. All the vendors I’ve spoken to at WordCamp US and WordCamp Europe, they’re all the same. If you look at our plugins as well, maybe we used to get, I don’t know, maybe on average a vulnerability or two reported a year.

As soon as this whole AI started thing, all of a sudden within a month or two, you get like four, five, six reports like, “Whoa, what happened?” In just one week. It’s just reality. It’s up to us, as I say, we have to be more proactive. Of course, it’s easier said than done, but we have to be more proactive and try to use the same tools that attackers are using to make sure at least we detect them, yeah.

[00:35:13] Nathan Wrigley: Yeah, the bit that genuinely I find curious is what will be the calculus in terms of time that people can spend on this stuff. So as an example, if let’s say that by January 2027, many of us are having to spend a good proportion of every day, and by a good proportion, I don’t know, let’s say 30 minutes or something, browsing through the news to see if anything has cropped up. Or indeed to read the things that we know has cropped up because the fire hose of security news has gone through the roof.

This seems like it could happen, that we’ll all have to be mindful of it. And it’s just that sort of attritional wear and tear that, “Okay, really? Do I have to do this each and every day?” That will be interesting.

I suppose the flip side of that, curiously, is that it, how to describe this? It doesn’t do your business any harm because the more that people are concerned about their WordPress websites, the more security news there is, the more that they will be drawn to companies like yours. So it’s a very curious tightrope walk that you’re going to have to perform, I think as well.

[00:36:10] Robert Abela: Yes. Yes, it’s the reality. If I can do a shameless plug, at WordCamp US, I spoke about, WordPress user sessions and hijacking, and one of my lines was that all the things I had mentioned, but the talk is available on YouTube on the WordPress channel. All the things that I have mentioned, so many missed it, because if you look at user session hijacking, the bottom of it is all derives from user mistakes. A user making a mistake, that’s all it is.

And the reality is it all sounds dramatic. It all sounds like it’s the end of the world and apocalyptic. However, the reality is that, yes, nowadays, if you use a website, even as a user, you need to be aware of some basic things.

So yes, there are these news, and hopefully more and more people will become aware and more and more people need to become aware that yes, these are the dangers, these are like the risks of logging into a website nowadays. Of maintaining a website nowadays. It is. It’s like a double-edged sword. Like the news are making sometimes a bad rep for WordPress, but they’re also reaching more people that they need to wake up and say, “Oh, these are the risks, so we need to take action.”

[00:37:07] Nathan Wrigley: Yeah, it will be interesting in the face of AI vulnerability. It’d be interesting to see what the, let’s say hosting companies, let’s paint a target there. What they do to manage their stack, because obviously it’s going to be very important for them to make sure that the clients that they have. And how they position themselves in the news, and how they can portray the security solutions they’ve got. But as well as companies like you, you know, plugins and other firewall companies and things like that. Be interesting to see through 2027 how they manage that.

Okay. In which case we will wrap it up there. Just another quick reminder, go to the WP Tavern.com website, search for the episode with Robert Abela. You will be able to find the 2026 Melapress WordPress Security Survey over there. Download it, have a little bit of a look. And Robert, are you available anywhere online? Do you, other than Melapress’ do you actually make yourself available? And if so, where can we find you?

[00:37:58] Robert Abela: Yes, I’m active on LinkedIn, Robert Abela. I’m active on X.com, and I finally also have my own website. It’s more on personal things quite frankly, but yeah, it’s robertabela.me.

[00:38:08] Nathan Wrigley: In which case I will bury those in the bottom of the show notes as well.

[00:38:12] Robert Abela: Thanks.

[00:38:12] Nathan Wrigley: So that you can find those. Robert Abela, thank you for chatting to me today. I really appreciate it.

[00:38:16] Robert Abela: Thanks likewise.

On the podcast today we have Robert Abela.

Robert has been working in IT security for 25 years, ranging from antivirus software to web security scanners, and for the past decade has been running Melapress, a company focused on WordPress security plugins, particularly around user visibility, authentication, activity logs, and 2FA.

Robert is here to talk about the 2026 WordPress Security Survey, this is an annual project, now in its fourth or fifth year, gathering data from a wide range of WordPress professionals across agencies, enterprise teams, freelancers, and product owners. The conversation today is focused on the biggest security challenges and trends facing WordPress users in 2026.

We start off with some sobering stats, over 67% of survey respondents reported experiencing at least one security incident in the past year, and concerns about WordPress security remain high, especially among less technical users. We chat about the disconnect between awareness of security threats and actually taking steps to mitigate them, such as breach recovery plans and team training.

The discussion also explored the different types of risks that worry site owners, site downtime, defacement, reputational damage, data loss, and even legal compliance issues, how these shake out depends on the type of site, whether it’s e-commerce, membership, a news outlet, or a simple brochure site. 

We also talk about the tendency for even experienced WordPress users to take a reactive approach, only addressing vulnerabilities after something has gone wrong.

Towards the end of the episode, we discuss the rising impact of AI on security, the explosion of AI-facilitated vulnerabilities, and the shifting landscape of risk and response. There’s a healthy dose of reality, some optimism about the tools and best practices available, and plenty of good advice, especially for smaller teams and freelancers who may not have access to enterprise-level resources.

If you care about keeping your WordPress sites secure, or want to understand where the community’s biggest concerns and opportunities are in 2026, this episode is for you.

Useful links

Melapress

WordPress Security Statistics 2026: Melapress Survey Results

Robert’s personal site

💾

#236 – Brian Coords on WordPress as the Source of Truth

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, making WordPress the source of truth across web projects, not just the website.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.

So on the podcast today we have Brian Coords. Brian’s journey started in teaching and after a surprise detour, thanks to a growing family and a need for new work, he jumped headfirst into WordPress, spending a decade in agency and freelance roles before landing as a developer advocate at WooCommerce. He’s known for his knack for explaining the complicated parts of WordPress, championing documentation, blogging, podcasting, and bridging the gap between community needs and product development.

Brian recently delivered a talk at WordCamp US entitled, The Site is the Source of Truth, Block Themes, AI and Agency Workflows, and that’s the focal point for our conversation.

We start with Brian’s background in both education and development, and how he finds his DevRel role the perfect bridge between those worlds. We then get into the evolution of WordPress from its early days to the present, questioning just what it is that has given the platform such staying power, especially as agencies race to adopt shiny AI tools or static site builders, and are tempted to throw WordPress out with the bath water.

Brian sees unique value in the WordPress ecosystem, especially for sites with longstanding content, integrations, and complex needs. And he makes the case for why the platform is built to last.

We talk through the idea of the site as the source of truth, using WordPress, and increasingly block themes, not only as a publishing platform, but as the repository for all your design, content, and workflow guidelines. Instead of letting generative AI run wild, and potentially cause chaos, Brian outlines how agencies and product teams can centralise approved patterns, templates, and even content guidelines directly in the WordPress site, helping both AI and human users maintain brand and design consistency.

We also unpack the state of block themes, why agency adoption is taking longer than expected? What’s coming soon for WooCommerce users, and how the move to block-based building is reducing plugin sprawl and making sites more resilient. And of course, we wrestle with the tight rope walk of what should go into WooCommerce Core, versus what is better left to the ecosystem, especially in a world where AI can spin up basic plugins in seconds.

If you’re curious about how WordPress agencies can survive and thrive alongside AI, what the future holds for block themes, and how to build smarter, more sustainable workflows, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast where you’ll find all the other episodes as well.

And so without further delay, I bring you Brian Coords.

I am joined on the podcast by Brian Coords. Hello, Brian.

[00:04:05] Brian Coords: Thank you for having me.

[00:04:05] Nathan Wrigley: Oh, you’re so welcome. Brian and I were supposed to record this podcast episode at WordCamp US, but, Jamie Marsland.

[00:04:14] Brian Coords: He ruined it, yeah.

[00:04:16] Nathan Wrigley: Yeah, we’re going to blame him. We had another engagement, which was to watch Jamie Marsland. But I appreciate you giving me the time after your WordCamp US experience. We’re both back home now.

But if anybody isn’t familiar with you, Brian, we’re going to be talking a little bit about a presentation that you did at WordCamp US. That’s going to be the fulcrum around which the conversation goes. I’m going to encourage everybody, probably to go and look at the WP Tavern show notes, check them out. We will link to that presentation, which is called The Site is The Source of Truth: Block Themes, AI, and Agency Workflows.

Hopefully gives you some intuition of what we’re going to talk about. Brian, do you just want to tell the audience a little bit about you? I know it’s a rather generic question, but tell us about you, your background, lo these many years.

[00:04:58] Brian Coords: Yeah, so currently I work at WooCommerce as a developer advocate, so just working on community documentation, release posts, the blog, all that kind of communication stuff for WooCommerce.

But before that, I spent like 10 years in the agency and freelancer world building WordPress sites, so I leaned on that for WordCamp US. Especially because you can only talk about WooCommerce so much at a WordCamp, so I leaned on my agency background and figured block themes, AI, all this stuff mixing around, what can I try to make sense out of it, and I don’t know if I did, but I got some thoughts out.

[00:05:34] Nathan Wrigley: I remember a couple of years ago, prior to you getting that job, you were doing various bits and pieces, one of which actually for a tiny period of time was writing for The Tavern. And then I remember you getting the job. I was looking at your profile on social media, I think, and you landed the developer relations job, and I thought, “Oh, if ever there was a job which fitted a character,” it felt like you had dropped into something absolutely ideal. Do you just want to tell us what that role actually involves? And is it as ideal as it sounds for somebody of your characteristics?

[00:06:03] Brian Coords: Yeah. To be honest, I saw that that was a type of job that existed in tech, and before I worked in any web development, I was a teacher. I was a high school teacher, so kind of wanted to bring back teaching and writing into what I did as a day job. So I saw that’s what a developer advocate, that’s like what DevRel does, and I basically spent like a year or two doing it for free, to prove that I could do it and get a job. And was like, “I’ll just pretend to be one, and then eventually somebody will pay me”,. And that’s kinda how it worked out.

I mean that’s basically the job, is you’re teaching, you’re doing a lot of writing, you’re doing a lot of explaining things, you’re taking a lot of community feedback and bringing it back internally and saying, “This is what people are asking for, this is what they like or don’t like about the new feature”. You’re just bridging that communication gap, but you are also not responsible for any code, and that’s the best part of it. I’m less stressed about code overall.

[00:06:57] Nathan Wrigley: I’m just going to go totally off piste here because I want to dig into what you said there, because I find that really interesting.

One of the most important pillars of, I think, every society is the education piece, particularly of the younger generation, the children. I have reasons to be into that, but I won’t share them here. But, very, very meaningful to me.

Do you miss that aspect of life? Obviously there’s a reason that you stepped away from that. Perhaps it was paperwork or burnout or whatever it may be. But do you miss the kind of face-to-face bit? Because obviously I’m imagining that you were, there was you, Brian, at the front talking to actual humans who you could reach out and touch if you needed to. How does this map to that, and the desire that you obviously once had to be an educator with real humans inside a real classroom?

[00:07:39] Brian Coords: I left it sort of accidentally. We got pregnant with our first kid and needed to move, and I just needed to find a job closer to home. And it just was an accident, and I stumbled into WordPress and tech and everything. And so, I did miss it and I felt, I think I had an experience where I spoke at a WordCamp and I was like, it felt like teaching, because it was like I know everybody in the room. This is a community, I know everybody, I have a relationship with them. I’m up in front of the room talking to them, but they’re also yelling at me and heckling me because we know each other so well.

So it reminded me of that vibe. So I kind of did look for this job as a way to bridge the two things, the WordPress and the tech side, and also a chance to do writing and teaching and bring it back a little bit. And maybe one day I’ll go back to a classroom or something.

[00:08:27] Nathan Wrigley: Yeah, maybe. One of the curious things that I think about when you see education done well online, you watch somebody’s YouTube content or wherever that content may land. You sort of get the impression that they just turned on the camera and began. Oh, they’ve added in some animations, and they’ve cut and done transitions and things like that.

But for every, let’s say 30 minutes that you produce online, is there, an hour, two hours, three hours of thinking it through, figuring out the pedagogy, who’s the audience, how do you write to their skill level? Just talk us through that bit a little bit, and I promise that’s the last off-piste bit we’ll do.

[00:09:03] Brian Coords: Yeah, I mean, for everything that I record, I spend a lot of time doing drafts of it. I’ll try to write the whole thing and just, what would this look like if I wrote the whole thing out?

And then, I’ve tried doing, a prompter where you read into the camera, and that never feels natural, it doesn’t work. But if I do three or four takes of it, by the time I get to that fourth take, I’ve internalized it, and then I can free flow it after that. And that’s how I approach my talk at WordCamp, where I just kept doing it personally, to the point where I felt like I could just say the stuff naturally.

But I do bring in some of the teaching stuff of thinking about what is the student doing at the time? What are their goals? What is the one thing that they should walk away from this? And I try to bring as much of that into it, but, it’s hit or miss, you know.

[00:09:49] Nathan Wrigley: Yeah, I guess one of the things that you always were going to miss is the sort of the feedback loop of having people in front of you, you know you’re, if all the children in front of you are gazing at the floor, then you know you’ve definitely pitched it incorrectly and you probably need to rethink. But you’re not necessarily going to get that shooting YouTube videos, but perhaps would, inside of a WordCamp. I can see you nodding, I hope that’s not actually what’s happened.

[00:10:12] Brian Coords: Yeah, your YouTube comments are pretty close to being in front of a bunch of middle schoolers, right? That’s pretty similar. But the face-to-face and being in a real room is important. That’s why I took this job too, is more WordCamps, more Meetups, more time in person, but also I don’t have to leave my house every day.

[00:10:29] Nathan Wrigley: Yeah, there is that.

[00:10:30] Brian Coords: I get a balance.

[00:10:30] Nathan Wrigley: That’s really nice, isn’t it? Yeah, so you can be working at the time of day that suits you and your family.

Okay, so back on the piste. The title of the presentation, as I said, is The Site is the Source of Truth, Block Themes, AI, and Agency Workflows. I’m just going to read some of the blurb just so that the listener has context, and it goes like this.

“Block themes give WordPress an opportunity to become more than a publishing tool or a place where finished designs are implemented. With the right theme structure, patterns, templates, and brand guidelines, a WordPress site can become the source of truth for how new pages and layouts should be built. That matters even more as agencies begin using AI in their build process. AI is useful when it can work from existing pieces, approved patterns, real content, design tokens, reusable blocks, and known template structures. It is much less useful when it starts every landing page from scratch.”

And it goes on, but I’ll stop there. Do you want to just summarize what you actually did in that presentation? Then we’ll dig into the bits and the pieces.

[00:11:27] Brian Coords: Yeah, so you submit the idea for a talk months before a conference, and then you get to the conference and three weeks ahead they tell you, “Hey, your talk got selected.” I submitted a couple. That was the one they picked, and then I read all that and I thought, “Did I write that?” I couldn’t even remember writing all that.

But it, the timing actually worked out because we are doing a block theme in Woo right now, and I’m spending a lot of time focusing on that. It all lined up. But I definitely read that description, and I had already started working on some slides and I thought, “Oh, I don’t know how much this lines up to what I actually am presenting.”

But I think the goal of what I wanted to do is talk about, I feel like a lot of agencies these days are saying, “We don’t need WordPress. We’re moving to static sites. We’re just letting AI vibe code everything on our sites.” And I wanted to kind of say there’s some value in the systems that WordPress has. It’s maybe a little more work, but there’s reasons for it.”

And I ended up doing a history lesson of, “Here’s where WordPress started. Here’s where we took the journey of why things are the way they are, and the benefits for agencies.” and so I kind of ended up in a place where I got to that topic, but I did a lot of rambling throughout the presentation. I felt like the context was really important. The like, why are we here? Why is WordPress the way it is.

[00:12:45] Nathan Wrigley: Yeah. Okay, that’s really interesting. So you said there, values in the systems that we have, and we’ll explore that in a moment. But technology’s such a weird one, isn’t it? In that most of the evolution of humans, we come up with ideas and then we finesse them a little bit. We adapt them over time, but it can be, a decade, 100 years before any major improvement takes place. You think the printing press, it just carried on as that printing press for many hundreds of years before it got slightly tweaked with linotype and things like that.

But technology seems to be quite happy to wholesale throw the baby out with the bathwater on a more or less continuous cycle. So, why then do you feel that WordPress should buck that trend in the advent of AI? Like, why does it stand a chance when AI systems are becoming ultra-capable, static sites, or just talk to your agent and it’ll just build whatever you want. What is it? What’s the intrinsic value that you think will mean that it will be around in a, I don’t know, 5 years, 10 years, whatever that may be?

[00:13:42] Brian Coords: Yeah, I think that’s a question everyone’s asking, which is, “Is there a unique value to WordPress that you can’t replace with AI?” And I think some people will point to the community and just the ecosystem and the fact that so many solutions already exist. I feel like AI is really good when you have nothing, and you’re going from zero to one. I have nothing and I’m going to make something brand new.

Once you get to something where you’ve had a site for 10 years and it has tons of content and tons of authors and all these integrations and all these sorts of things, AI is helpful, but everything has to move a little slower, everything has to be a little bit more resilient, and those are the places where having a little framework underneath, something like WordPress holding everything together, ends up being a little bit more valuable. But it’s definitely changing when you would use it, when you would reach for it, and I think that’s the part people are struggling with right now.

[00:14:30] Nathan Wrigley: Yeah. There’s so many examples in my life where there’s a new innovation, but I stick with the older thing, just because it’s tried and it’s tested, and I know the limitations of it and I know what I can do with it. So maybe that’s a good comparison.

It will be interesting to see how AI is able to adapt and just simply build things which are robust and usable. But I think at the moment, the core promise for anybody trying to sell a website to a client, for example, is exactly that. It’s reliable. It’s battle tested. It’s been used on millions of sites all over the world, and it’s got a familiar interface and you can go in and do this, that, and the other thing, and click save and publish and what have you, and it’ll just work. Whether or not that remains the case a, a decade from now, I guess only time will tell.

But, have this idea in your presentation of the site being the, and you said the, source of truth. What did you mean by that? What is the underpinning of that? What are the bits that kind of spin off if the WordPress site is the source of truth, what are the bits that sort of rely on that foundation?

[00:15:28] Brian Coords: Yeah, I think one of the things that people see when they start using AI is it will just do whatever it wants. So you could ask it for two pages on your site, and they might look completely different. It might pull in some design trend here. The language might be completely different on this other one. It might not understand your audience and your values.

And so with AI, you end up doing a lot of shepherding that’s kind of like, “well, no, this is the target audience. This is my color palette. This is the design things I like to use.” And so I leaned a lot in the talk to things like patterns in WordPress. Where, it’s something we do in WooCommerce where we have a designer, they’re very talented, they make really nice patterns that really conform to our brand. And then AI can go in and say, “pull the patterns down from the site first and use those. Don’t spin up crazy new designs. Use the ones that our human designer put a lot of care and effort into, that live in the pattern library on the website.”

And so the more you put into the website and the more you train AI to, don’t go crazy and create new things, use the stuff I already have, use the tools I have, that I think makes things a little bit more reliable, a little bit more consistent. And so I think for agencies, finding ways to put stuff into the website that’s going to help the AI, and guide it directly to doing things the right way. Instead of it always wanting to like, come up with some brand-new chunk of code that you now have to look at. So that was kind of a part of it definitely.

[00:16:52] Nathan Wrigley: So, what you’re saying there is instead of having all these disparate things like, I don’t know, you’ve got a Figma file over there. And you’ve got a Google document over here. And you’ve got another three different things and you can’t really figure out where the heck they are.

Put it all in a WordPress website, and from the point of view of the design, patterns would fit beautifully for that. You can organise your typography, and basic colour palettes, and layouts, and the way things ought to look. And I don’t know, here’s two dozen ways that we might structure a page. Lock all of that away. You don’t necessarily have to publish it anywhere on the front end, but the AI can go and creep around in there and get some guidance.

But then also presumably you could do the same with, I don’t know, your writing style. You could have draft posts where you outline the manner in which you would like to convey your company. And the words which are off limits, or the words which are definitely going to be used. So in that sense because WordPress can do video, it can do audio, it can do designs, it can do layouts and typography, why not just have that as the source of truth? Is that a sort of summation of what you were saying?

[00:17:54] Brian Coords: Yeah, I think that’s essentially right. And I talked a little bit about, there’s a project in WordPress called Content Guidelines, I think, and it does that. Where you put in a lot of your rules. And then I also talked, a lot of agencies use GitHub and Git repos for their WordPress sites, and in there you can do things like having agents files, and skills and stuff that share across your team.

So sometimes it’s in WordPress, sometimes it’s in that kind of GitHub code base for your website. So it depends on your agency’s workflows and stuff. But the point is, everybody puts stuff in the same place, because when I worked at an agency, it was that. It was, they used Figma and they used XD, and they have a Google Doc with all the technical specs, and then there’s 15 emails from the client. And AI actually is really good at taking all those things and putting it in one place and building a little knowledge base. And then when you bring on another developer, their AI is going to know exactly where that is, and it’s going to make things a little bit more scalable.

So it’s just an organizational principle, like just cleaning things up, putting stuff in one space, and making WordPress sort of the home for that, instead of using all these different tools that maybe you don’t need, or maybe you’re going to lose access to.

[00:19:00] Nathan Wrigley: I can’t remember the name, I think you just called it content guidelines or something like that. I can’t remember the name of that project, and I also can’t remember whether the intention is to ship that in Core at some point.

That seems like a really curious idea. Presumably it’s a non-public facing repository of, I’m doing air quotes, “stuff”. So you just dump into there all of the different bits and pieces. Presumably by trial and error over many iterations, you’ll figure out exactly what the agent’s creeping around in your site, and that content guidelines portion of your site is going to be able to take from that.

And you would amend it, and then when you begin another client site, that would be your first port of call. Get your client guidelines figured out, get that set of constraints worked out, and then move on with the design process.

That’s a really neat idea. Somewhat hidden from the public, but pretty neat. Now, I don’t really deal with agencies. I don’t have any communication with them. Do you have a sense that they’re open to these ideas, or it’s just some sort of curiosity which the core team think they might ship, but who knows whether anybody will use it? Have you got intuitions that this would be used?

[00:20:00] Brian Coords: Yeah, that’s been an interesting one. That content guidelines feature almost shipped, and then it got pulled at the last minute and was kind of like, “Let’s see some real world usage of this.” I think it’s probably really helpful for big news publications. That’s what I’ve heard a lot of. Where they have 20 authors and they want to make sure their authors are doing the right thing, and so that makes sense.

I think for agencies, a lot of the ones I talk to, they really, they like putting things in GitHub. That’s where they like to put stuff, and they like putting it in the code. I don’t know if they’ll put it in WordPress, but I think it’ll be interesting to see. But I feel like we’re all just dealing with, there’s just tons of content, and markdown files, and prompts and skills and all these overwhelming amounts of things, and it’s like everybody together is trying to figure out what are the best ways to do this. And I think it’s just fun to explore the ideas and see. In two years maybe we’ll all have the answer to this.

[00:20:54] Nathan Wrigley: Yeah. We’ll have a fresh set of new problems in two years.

[00:20:57] Brian Coords: Yeah.

[00:20:57] Nathan Wrigley: It was curious there, we’d been talking about AI for a while and then when you, corroborated your examples there, you described the humans using it, which I thought was quite interesting. So you’ve got these 20 people working for, let’s say, TechCrunch or something like that. Big organization, lots of editors, lots of authors and what have you. But even if the AI never touches base on that, just the idea that the humans can access it in a human-readable way, not all about the AI.

Just that seems worth shipping. If all that you do is have some mechanism to show brand new author to techcrunch.com, how you would like things to look and feel and what have you, that seems like a reason to ship it even if the AI portion isn’t launched at the beginning.

[00:21:38] Brian Coords: I think everybody’s explored, I know I did, where you go all in on AI and it’s going to write all my stuff, and it’s going to do all these things for me. And then internally we’ve had a, I forget what the post, but somebody wrote this kind of, writing is for humans post, and a lot of people in the company rallied around that. Which is like, it was fun to let AI do some stuff, but writing is important, and writing should be done by humans. We don’t want to put AI content out. So at the end of the day, we expect humans to write, and we still really value that, and writing is a valuable thing in and of itself.

But then AI can come in a little later and say, “Well, maybe I’ll review it for you. Maybe I’ll give you some feedback and you can take it or not.” But it’s been an interesting, I feel like there was a pendulum where AI will do everything, and now it’s like, no, I think we’ll find the places for it to make things move faster, but there’s just still human value, and I’m glad to see that pendulum maybe coming back, at least internally for us it is.

[00:22:34] Nathan Wrigley: Sorry, going slightly off piste here, but I have an intuition that by the time another decade has passed, I think there is a version of the universe in which people have become really sick and tired of AI. I think it’s a really plausible future that some things will be viewed with enormous incredulity and skepticism if there’s any hint of it being done by an AI.

So perhaps that won’t be design. Perhaps it won’t be music. Perhaps it won’t be coding. But I’ve got a feeling that writing, especially fictional writing and things like that, but also opinion pieces and things, I think that is highly likely to become, once again, the domain of a human being. And I know for certain that my own children are very skeptical about AI and the future that’s presenting. So yeah, I welcome that commentary. I’ll leave it there if you’ve got anything to follow up with. If not, I’ll ask another question.

[00:23:22] Brian Coords: Yeah, I go back and forth on it. I’ve never listened to AI music, and I don’t think I ever will.

[00:23:28] Nathan Wrigley: No.

[00:23:29] Brian Coords: Maybe I have and I just don’t know it.

[00:23:31] Nathan Wrigley: Curiously, I bet you have. Yeah.

[00:23:32] Brian Coords: Yeah, I probably have. AI writing is the same way. It’s if you can’t tell that it’s AI, will that matter? And I think at the end of the day it will, because I don’t read things unless I know who the author is and I’m interested in their perspective, and I don’t really listen to music if I don’t know, I like to know the story of the band, and I like to know the context. If I’m reading a book, I like to know when the author lived and what culture they’re filtering everything through and, yeah, maybe we’ll be unique and some people will just want to doom scroll AI videos of cats, but I never did that before, so I don’t know if I’ll do it starting now.

[00:24:05] Nathan Wrigley: No, but curiously, it might offer a slight marketing edge, let’s put it that way. If you can certify provably that you are the real thing. Whether that be in the music space and you simply have to record the process of you going through the process of creating a song with all of the mistakes, and heartache, and anguish that that is.

But I feel that maybe there will be a craving for that in the future. Maybe people will literally work harder to find people online who are provably writing their own material, be that songs or making videos or writing and what have you.

So we’ve all been swamped AI and been beguiled by it, I think as you’ve said, the pendulum feels like there’s a bit of a swing in the other direction, and it might be that you can have a marketing edge simply because you’re actually taking the time to, to write things out. So anyway, there you go.

Let’s move on slightly. So block themes. You were mentioning that at Woo you’re currently playing with a block theme. I don’t know how many of those are actually in the bag already and out there in the wild coming directly from Woo. But it does feel that many years ago block themes were being touted as the thing.

It feels like it didn’t turn out quite the way we expected. There hasn’t been this deluge of block themes, and everybody’s put the classic themes behind them. I think people are clinging to classic themes for a variety of reasons. Do you want to just talk about why you think block themes fit into this whole agency source of truth piece as well?

[00:25:28] Brian Coords: Yeah, block themes have been interesting. I’ve seen a lot of agencies that really start to like them, and agencies understand the value. I think, for a lot of existing websites, just changing your theme is hard. There has to be a really good reason to change your theme, because who knows what’s going to break? Who knows how everything is going to work, especially with e-commerce? It’s like if it’s not broken, don’t touch it. There better be a good reason for it.

And so I think in some ways for a lot of people, block themes for existing sites maybe haven’t given them a really good reason to switch yet. But I think it will for a number of reasons. I was actually just talking to a coworker about our block theme that we’re getting ready to launch. Probably by the time this is out, it might be in a public beta.

But one of the things that was interesting is in WooCommerce, there was a theme called Storefront, which was like, that was the WooCommerce theme. And we’re doing a comparison right now, where if you wanted to move from Storefront to our block theme, Storefront had all these plugins. A plugin to do a header on your site, and a plugin to do a little mini cart, and a plugin to do product carousels, and all these plugins you would have to install. And that meant testing them and making sure they work and updating.

And we did a comparison of how many of these things can you already just do in the block editor, and it was like 90% of it already exists in the block editor. And you don’t need a plugin for it, and you don’t need extra code, and you don’t need to buy a new extension. So I think people are starting to see the value of it, once they realize how much is just included. I can change anything. I don’t need a plugin to add this or that to my site.

So I think there’s a lot of value to it, and it just ends up being a little safer because it’s just WordPress and WooCommerce and a theme that only has a little bit of styling. I’m not worried about the compatibility of plugins, and I’m not worried about paying for updates and all these sorts of things, and is it going to break on the next version?

And so I think there’s a lot of value to it, and it just makes WordPress itself more the thing you’re relying on. You’re just relying on the blocks. You’re just relying on the things that WordPress gives you. So I think there’s going to be a lot of benefits to it, but yeah, we have not, there is no WooCommerce official block theme yet, but we’re hoping that there will be one soon.

[00:27:31] Nathan Wrigley: One of the things that I thought block themes would tackle really quickly soon after launching, which never kind of ended up being the case, was for example, things like WooCommerce, atomising every bit of a WooCommerce site into a separate, let’s say block. So for example, I don’t know, the add to cart block, and the the I don’t know, show the quantity in the cart in the menu block, and yada, yada.

And you go to the cart page or the payment page, and you would just fill it up with the blocks as you’d like, and add spacing and add margins and what have you. That never seemed to take off, but also I don’t know if it’s still talked about, or the promise of that is still something that you are hoping to deliver.

Just talk us through where we’re at in terms of atomising the entirety of a WooCommerce site into individual blocks. So rather than dropping entire sort of templates or structures, you can pick and cherry pick. obviously there’d be dependencies. If you’ve got this, you must have that. But just tell us where we’re at.

[00:28:28] Brian Coords: Yeah, so overall you can do that for most of a store. I think the only thing that doesn’t have blocks right now at all is like the account pages. Somebody logs in and they see their downloads and their order history and all that. That stuff is, I don’t even think is anywhere blocks at all. But that was one of the things as part of this process is, we looked at all the blocks, because there is a add to cart button block, and there is a quantity selector block, and there is a product image gallery block. I mean there’s like a, more than 100, maybe 200 blocks in WooCommerce.

There’s a lot, but the thing that they were missing was the style controls, which is I think what a lot of people wanted. Which is if I have the button, is it going to look like every other button on my site? And can I customize it? Are all the form inputs on my checkout page going to look just like the drop down on my product selection page?

And so that’s been the big push recently, like actually building the block theme, like 90% of the work of what they’re doing is just fixing the blocks, and making the blocks better. And the theme is just a very thin layer.

So it’s gotten a lot better, and that’s kind of the goal is once we have our own theme we can show, okay, all this stuff is customizable and editable. And I think probably in the next release you’ll see a huge focus on those block style changes showing up in WooCommerce.

[00:29:44] Nathan Wrigley: I have a curious question that you may or may not wish to answer. Let’s see how this one goes. If you, as you just described, you were talking about you don’t need a plugin for that. You don’t need to worry about an update or a payment for this thing. We’re bringing all that functionality into Core.

I’m wondering what that tightrope looks like, where over there somewhere, part of the community, somebody’s got a paid plugin, which is the basis of their entire livelihood. But it just so happens that, we could really ship that in Core, and that would be really useful to have in Core. We reckon that 80% of the people who use WooCommerce will use that.

How do you decide when something gets made and the obvious sort of community impact that that thing may have had? So as I said, that’s a tricky question. I will leave you to answer it or not.

[00:30:31] Brian Coords: Yeah, it is a huge topic of discussion. James Kemp, who is the Core product lead has been pushing for more of these things in Core. And I think that the big question right now is, are a lot of the people making money on plugins going to be able to continue making money on some of those plugins with AI? Because there’s a lot of plugins that are 100 lines of code that an AI will happily spit out for you.

And so I think the floor is raising on people building plugins. Where if your plugin isn’t doing anything super complicated, if it’s set it and forget it, then there’s probably not going to be a market for it in the future.

But that said, there’s this whole other area of opportunity where there’s tons of plugins that need to be built still. There’s integrations that are really complicated that you don’t want to leave to AI. There’s things around modifying payments and modifying how your checkout works and different types of products. And all of that stuff I think is still available, and I think most people will choose to pay for those sorts of things.

But if your plugin is something, I will just say we’ve, all the ones we’ve brought in are our own plugins so far. So this new WooCommerce release that’s coming out this week is different product variations can have image galleries on each variation. That’s a thing. But that was our plugin. So we took our plugin and we put it in Core, and gave it away for free. We don’t really try to go after if somebody’s got an established community plugin and they’re supporting it. We don’t want to go after them. But we are definitely cannibalizing a few of our own plugins, and turning off a little bit of revenue we get from those to put those in Core. And that’s, we think it’s worth it in the long run to just have a better WooCommerce.

[00:32:09] Nathan Wrigley: I think that’s a really difficult tightrope to walk, isn’t it? Because obviously you would love to have every piece of functionality available in a, you know, easy to use manner in Core, or at least all the bits and pieces that were essential. But at the same time, there’s this delicate balancing act of the community, which at the moment seems to be, how shall we say it, in a holding pattern? Let’s go with that.

There’s a lot of uncertainty, people who have this sort of utility plugin that does this one thing, as you’ve described, it may be 100, 200 lines of code. Where in the past that was probably going to make you some nice pocket change. It does feel like that is going away.

So if that is the calculus upon which you’re basing whether you build something into Core or not, you’re potentially swooping in and creating something for which there is no business anymore anyway, Because now in the advent of AI, anybody with half a minute can whip that same functionality up, and you might as well have it all security checked and what have you inside of Core.

But very difficult to figure out how to balance damaging, I suppose, is the wrong word, but it’s adjacent to what I’m after. Damaging relations with community members who are great great advertisements for building on top of WooCommerce, and yet shipping all these things in Core. Difficult. I’m glad, I don’t have to square that circle.

[00:33:23] Brian Coords: Yeah, and we have a very vocal extension developer community. They give us feedback all the time. And some of them, I think they’re well aware that they’re much more likely to be threatened by AI, than they are us wanting the functionality of their plugin in Core.

But there’s also a general sense in WooCommerce from, like the customers, which is, “Why do I need so many plugins?” And that’s kind of a concern and that fear of, when I update WooCommerce and I have 30 to 50 extensions, which is very normal for a WooCommerce store, is each one of those going to work? Do I have to worry about that?

And so it is also a balance where it’s almost damaging WooCommerce that you need so many plugins just to run a store. And that why do I need a plugin for this and this, you know? So we’re trying to balance that, where we want to make it feel more secure and reliable.

But also I think a lot of those plugins are much more threatened by AI than they are us getting around. We have plenty to work on before we get around to taking other people’s plugins. We have plenty to work on our own to improve basically WooCommerce, subscriptions, all the kind of Core stuff we already manage.

[00:34:25] Nathan Wrigley: Yeah, I feel that in the WordPress space, the most likely bit to survive, is potentially WooCommerce. Just simply because there is so much that is at stake by messing up your website by injecting a bunch of AI slop. Again, I’m doing air quotes.

Because, this is your revenue. If you take your site down for half a minute, that really could lose you, I don’t know, thousands of dollars in orders. But I don’t know if that’s your intuition as well. It feels like brochure sites, that is very much up for debate at the moment. We’ll have to see how the landscape goes with that. But it feels like the WooCommerce bit, the e-commerce of WordPress’s community, it feels like you’re on a bit of safer ground just simply because of the revenue that’s generated by those sites and the reluctance of people to meddle with them.

[00:35:14] Brian Coords: Yeah. I mean that’s what I’ve been yelling internally, so I’m glad you agree. I think e-commerce is definitely much more, has a much stronger moat than static brochure sites. And I think that’s what people in WordPress are sort of dealing with, which is for all these sites that are on WordPress how many of them need WordPress? How many of them need this functionality? WooCommerce definitely. You need a database, and you need security, and you need updates and you need all this stuff.

For a marketing brochure site, you probably didn’t need it to begin with, but WordPress was easier. So the question is for those simple marketing sites, do we make WordPress easier so that they can keep using WordPress, or do we say, “No, we’re going to lean in on publishing, commerce, really complicated, heavier duty sites that probably generate more money, but maybe the total market share goes down,” I don’t know. I think that is a big question.

[00:36:05] Nathan Wrigley: Yeah, it’s interesting. I can imagine in a decade from now, the UI for a typical brochure site almost not even a UI. It’s something that we can’t really conceive of at the moment. It might be that, you speak to a thing, and the thing reacts and amends as necessary. Maybe WordPress will have to fight that territory to keep its market share.

But I do feel that the WooCommerce side, I think people are going to be able to justify the time put in to logging into a platform and going through a list of products and adding, “Okay, I’ve got some shoes that I’m selling over here and they come in seven different varieties. I want to sell the shoes. I’m going to upload the color palettes for each of those shoe,”. There’s just some calculus of the work that needs to be done and the maintenance that needs to be done. I feel that you’re on much, much stronger ground as you described. So yeah, I think you’ve every reason to be sanguine.

[00:36:52] Brian Coords: Yeah, and I still think people want to log in to something and look at something. Especially with e-commerce, they want to just see a screen of how their orders are doing. They don’t want to ask AI to generate that every single second that they want to see how many orders they have, and what their revenue is for that day and all their analytics. They just want to log in and see the thing that they see every day. They don’t need to vibe code that on the fly by asking AI to generate it, right?

[00:37:15] Nathan Wrigley: Do you know that’s really interesting? I have genuinely never thought about the desire to log into a thing, but that actually makes a lot of sense to me.

This is going to sound extremely out there, but I’m going to say it anyway. There is something of akin to getting home when you’ve been on a long journey, and you finally get to your own front door after sleeping in hotels, beds, and all of that. There’s just something quite nice about getting into you own environment and it’s, “Ah, I’m at home.”

And I actually have started blogging again recently, and I get a real great feeling when I log in and all that familiar stuff is there, and, “Oh, look, there’s all the pictures that I’ve posted on this website these many years.” I think there’s something there. I think that’s really curious. The idea of logging into something, being purposeful about it. Not speaking to the exact same interface that you talk to every other thing to do the job. Having a place, a URL that you go to, the environments how you’ve set it up, I can’t believe I’ve never thought of that before, but I think that’s quite profound. I hope you’re right.

[00:38:18] Brian Coords: Yeah. I hope I’m right too. I hope that there’s just some things in life you don’t want to ask an agent to go do for you, and you just say, “Let me just click on this and change this thing.” Some things are just faster than, “All right, I’m going to text my agent, and hopefully he does it right, and then he’s going to send me a screenshot that it got done.” I mean, I love doing that kind of stuff. I do it for some things, but yeah, sometimes you’re just, “show me that same dashboard.”

[00:38:41] Nathan Wrigley: Yeah. And I do wonder in the years to come how ready we are going to be to submit all of that control. Just the idea that an essential part of your business, like your e-commerce site could be done by an AI with very little intuition as to what’s happening once that command has been given and it updates that stuff.

But not just that you don’t know what that thing did, what the thousand other things that were done prior to that one prompt. Okay, it looks nice at the minute, but how did it even get there? Well that was about two years of prompting. Okay. All right. Can we unpick that? Not really. We haven’t the faintest idea how it got to this. Yeah, that’s really interesting. Okay. I think I’ve asked everything I wish to ask. Is there anything you wanted to get out before we knock it on the head, Brian?

[00:39:24] Brian Coords: No, just hopefully we’re still here in five years, not just prompting away in our basements.

[00:39:29] Nathan Wrigley: You know what? I think if you’d have asked me that question six months ago, I had less certainty than I do now. I think I’ve seen a sort of, tsunami is the wrong word, it certainly is not that, but a general sense out in the world at at large of distrust and a move towards the sort of more artisan side of life.

And so I think it’ll be curious to revisit this conversation in a few years time and see how that pendulum has swung. If the AI overlords are listening to this in the year 2028, please do not come and get me. I was wrong. But there we go. Let’s hope that we’ve all got somewhere to stand, a beachhead to stand in a few years. That’d be nice to think about.

Okay, Brian, thank you so much for chatting to me today. I really appreciate it.

[00:40:10] Brian Coords: Thank you.

On the podcast today we have Brian Coords.

Brian’s journey started in teaching, and after a surprise detour, thanks to a growing family and a need for new work, he jumped headfirst into WordPress, spending a decade in agency and freelance roles before landing as a Developer Advocate at WooCommerce. He’s known for his knack for explaining the complicated parts of WordPress, championing documentation, blogging, podcasting, and bridging the gap between community needs and product development.

Brian recently delivered a talk at WordCamp US entitled “The Site Is the Source of Truth: Block Themes, AI, and Agency Workflows,” and that’s the focal point for our conversation. We start with Brian’s background in both education and development, and how he finds his DevRel role the perfect bridge between those worlds.

We then get into the evolution of WordPress, from its early days to the present, questioning just what it is that has given the platform such staying power, especially as agencies race to adopt shiny AI tools or static site builders and are tempted to throw WordPress out with the bathwater. Brian sees unique value in the WordPress ecosystem, especially for sites with longstanding content, integrations, and complex needs, and he makes the case for why the platform is built to last.

We talk through the idea of ‘the site as the source of truth’, using WordPress (and increasingly block themes) not only as a publishing platform, but as the repository for all your design, content, and workflow guidelines. Instead of letting generative AI run wild (and potentially create chaos), Brian outlines how agencies and product teams can centralise approved patterns, templates, and even content guidelines directly in the WordPress site, helping both AI and human users maintain brand and design consistency.

We also unpack the state of block themes, why agency adoption has taken longer than expected, what’s coming soon for WooCommerce users, and how the move to block-based building is reducing plugin sprawl and making sites more resilient. And, of course, we wrestle with the tightrope walk of what should go into WooCommerce Core versus what is better left to the ecosystem, especially in a world where AI can spin up basic plugins in seconds.

If you’re curious about how WordPress agencies can survive and thrive alongside AI, what the future holds for block themes, and how to build smarter, more sustainable workflows, this episode is for you.

Useful links

Brian’s website

The Site Is the Source of Truth: Block Themes, AI, and Agency Workflows – Brian’s presentation at WordCamp US 2026

WooCommerce

Content Guidelines: A Gutenberg Experiment

💾

#235 – Rob Pugh and Tony Arcangelini on Bringing Podcasting to Jetpack

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress, the people, the events, the plugins, the blocks, the themes, and in this case, bringing podcasting to Jetpack.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.

So on the podcast today we have Rob Pugh and Tony Arcangelini. Rob and Tony are longstanding members of the Automattic team with extensive backgrounds in marketing, product, and software development. They’ve spent years building tools for creators, writers, podcasters, and everyone in between, and now they’re fully immersed in WordPress’s evolving podcasting capabilities.

If you’ve been looking for ways to run your podcast from your own WordPress site, this conversation is for you. Rob and Tony dive into the new Jetpack podcasting features, and why they made the leap from WordPress.com’s basic audio offerings, to a more robust, integrated solution, within Jetpack.

They talk about what makes WordPress and Jetpack such a powerful home for creators. The ability to bring your newsletter, blog, podcast, and all your content and communication under one roof, all while keeping ownership of your data.

We talk through the advantages of keeping your content out of walled gardens like Substack and Patreon, and the value of flexibility, whether that’s adding WooCommerce to sell merch or customising your site’s look.

Rob and Tony breakdown just how easy it is to start your show. Drop audio into a post, set your category, and let Jetpack handle the rest. From distributing your RSS feed to major podcast apps, to sending out newsletters, and automated social posts. They also get into how integrations with PocketCasts and Jetpack AI make content creation, transcription, and distribution smoother than ever before. Plus how WordPress is open Foundation promises you’ll never be locked in.

If you are a creator wondering how the next generation of podcasting fits into the WordPress ecosystem, or just want an easier way to launch and grow your show, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Rob Pugh and Tony Arcangelini.

I am joined on the podcast by Rob Pugh and Tony Arcangelini. Hello, both.

[00:03:23] Rob Pugh: Hey, how’s it going, Nathan?

[00:03:24] Tony: Hello, Nathan.

[00:03:25] Nathan Wrigley: Nice to have you both with us.

Today we’re going to be talking about something which is actually genuinely dear to my heart because we’re going on about podcasts. Yay!

I’ve been in the podcasting space for decades, and WordPress has been the place where I’ve done it every single episode. I’m entirely indebted to WordPress for the capacity to do all of the podcasting I’ve done. But I’ve never done it inside of Jetpack, because until recently, I don’t think that was possible. So that’s what we’re going to talk about today.

First of all, I’ll just go round the houses. I’ll start with Rob. Would you mind giving us just a quick potted bio of what it is that you do over at Automattic, Jetpack, whatever it is that you want to mention.

[00:04:04] Rob Pugh: Yeah, so I’ve worked at Automattic for seven years. I’ve been in marketing and now focused more on product, but I like to do a bit of everything. And I work mostly with tools for people that create stuff. So podcasts fit right in there, and we are excited to build out this feature.

[00:04:19] Nathan Wrigley: Nice. Thank you. Tony.

[00:04:21] Tony: Yeah. I’ve also worked for Automattic for about eight years now. I do software development, and so I have had firsthand in building everything that we’re talking about today.

[00:04:31] Nathan Wrigley: Okay, thank you very much.

Now, just before we started recording, I was on the call with Tony before Rob joined in and you labored the point, not labored, but you mentioned that you were in the sort of creator side of Automattic. I didn’t know that existed, but that to me is about the most interesting bit of any organization. You know, the bit where the musicians come, and the poets come and the writers come and the podcasters, and the videos and the YouTubers, and all of that come. I think that’s really interesting, and I didn’t realise there was a wing of the business entirely aligned to that. But I guess I’ve been schooled, and now I know. So podcasting definitely comes under that banner.

Okay so I didn’t know this existed, and I think it didn’t exist, but maybe Tony can redirect me a little bit here. Podcasting in the WordPress space, I think you could do more or less everything that we’re about to talk about inside of wordpress.com until recently, but now it’s shipped inside of Jetpack. First of all, I’ll just send that one to Tony. Is that true? Is this all like a port of things into Jetpack from .com?

[00:05:32] Tony: I’d say it’s a little bit more than a port. So we built a very basic feature of podcasting in WordPress.com to offer WordPress.com users. It was very basic. It was just the feed. Basically what you see in the free offerings right now. The ability to drag an audio into a post and for that post to then become a podcast episode. And then we had a curated RSS feed that was available. And then very basic, the core basic iTunes tags that are needed to be able to be picked up by these apps.

That existed there. It was a bit outdated. It hadn’t been touched in a long time, and so we felt like it would be a great tool to leverage for creators. Giving them a better product, something that would be useful with stats and the ability to manage your episodes and all of that. And we figured if we were going to put all this effort into it, that we should probably make it more widely available. And so Jetpack was, I think, the natural fit for us.

[00:06:26] Nathan Wrigley: Yeah, I’m kind of curious how it’s ended up in Jetpack and not just its own plugin. Is it because you’re leveraging the other things that Jetpack can do? Are there sort of dependencies, if you know what I mean, where, okay, it just makes sense because Jetpack already does that piece of the puzzle, and we can just build over the top of that?

Or is it just the brand recognition, the fact that you’ve got an email list that you don’t need to convert and they can just toggle a switch and automatically have got podcasts? What was the reasoning on putting it inside of Jetpack and not just its own thing?

[00:06:54] Tony: I would say, at least from an engineering perspective, there’s stuff that’s in it that is exclusively within Jetpack. So, the ability to do stats, that’s a hard thing to do when you’re having a self-hosted site, to be able to watch and see what apps are actually touching those download files, and then be able to aggregate them all in one place and then give them back to you in a way that’s easy.

So, at least from an architectural perspective, Jetpack was the easiest because it allows us to leverage some of the endpoints that are already there, and use a lot of those tools.

But then secondly, I think it’s also from an overall product perspective, being able to put it alongside other features like newsletters. Where you can have a newsletter, you can be able to take it into the reader. Have this one episode that now spans across multiple different avenues to be consumed, is I think, also another big benefit in putting it into Jetpack. As opposed to just dropping another, because there’s already a lot of plugins out there, a few big plugins that you can grab for free that do podcasting.

[00:07:56] Nathan Wrigley: I think one of the big bits that I realised early on in my podcasting journey was that you’re not really just trying to create an audio feed. It’s more useful as a podcast if you’ve got this kind of wrap around thing. So like you say, you’ve got a home which is yours, AKA your WordPress website. But also things like the capacity to send out an email if people are interested in subscribing, and they don’t necessarily have a podcast player that they use all the time, but they do want to consume your content.

The fact that they can subscribe to a newsletter, you click publish, that newsletter automatically drops in their inbox. It just makes sense that all the jigsaw pieces that a podcaster needs, it feels like WordPress has had forever.

And there is some part of me which is curious that it’s taken this long to come into the, let’s say, .org side of WordPress. Because all of the different parts, the newsletter, the RSS feed, the blog posting, all of that stuff has been available. It just kind of never got joined up. It strikes me as odd because people have moved over to Patreon, Substack has become this whole thing over the last decade. And really it felt like WordPress had that audience a decade ago.

Maybe it’ll claw it back. I certainly hope it does, but it feels like a lot of people have left the WordPress ecosystem for their podcasting because that stuff wasn’t available. Rob, maybe you want to take that one? It’s not really a question, more of an observation.

[00:09:16] Rob Pugh: Yeah, there’s a lot to unpack there. I agree. I think we were a little late in bringing some of these tools to wordpress.org. But I think we’re seeing the renewed focus across the technology space on ownership.

WordPress has remained the best way to do that. And for us to be able to offer these tools to users. It shows everyone that you can, as you said, own your blog your newsletter, your podcast, together. And it does make sense for us to offer all of these tools in one space.

I like to think of it going back to the origins of WordPress, and we started as blogging, everyone getting your thoughts out there and sharing them. Meeting new people, engaging and creating communities. And podcast is just another medium. We provide that for the written word, so of course we should try and provide that for the spoken word as well. So I do hope that we can show people the benefits, and the ease of having it all together and come back and give us a try.

[00:10:11] Nathan Wrigley: Yeah. I think for me at least anyway, that argument is embedded in my soul. The idea of owning your own content on the web is really important. It’d be interesting to see in the year 2026, 2027 and going forward how much that stuff really matters. I’m just curious, in the age of AI whether people still want to own anything at all. But it’ll be certainly interesting to see.

[00:10:30] Rob Pugh: Sorry, yeah, weigh in on that. I think we’ve seen it over decades and comes in waves. When social media started it was really exciting, and people ran and then saw some of the pitfalls, and they start coming back.

And then recently you mentioned Substack, and I loved Substack when it started. It was a space for some serious dialogue, and a place for writers engage. And then over time, well, we need that VC money, and now it’s basically another social media site. And you realise, oh I don’t really own my data, I just own a Substack, and how valuable is that? And it’s coming back.

And I think AI, it’s becoming even, the cycles are quicker now. AI’s incredible, I use it all the time. I use it to help come up with prototypes for how to best display this podcast product. But, you’ll see quickly that you don’t own anything, and you need to have a home like WordPress. And you retain ownership of your audience, and your data and your posts and your podcasts, and that’s, I think, never going to go away, and AI’s only going to reinforce that for people.

[00:11:23] Nathan Wrigley: Yeah, I think one of the curious things as well is if you want to do anything outside of the normal that the platform will allow, so let’s take the example of Substack. There’s a limited subset of things that it can do. The bedrock of what it does I’m sure is excellent. I confess I’ve never used it, but I’ve seen many people deploy it for their own podcast, so you know, it must work.

But the minute you want to stray outside of those boundaries, and you want to do something a little bit different, I don’t know, you might want to sell some merchandise or something like that. Well just pop WooCommerce on top of your website and you’re off to the races.

Or, I don’t know, you want to have a different flavor in the way it looks at Christmas or something, well you just adapt the theme. And I’m, imagining good luck doing that over on these proprietary platforms. I don’t know if that’s possible, but it certainly would be a lot harder than it would be on the WordPress side I would have thought.

[00:12:08] Rob Pugh: For sure the customisation expanding is all very important, but to me even more important is just that it feels like Substack is just another platform that’s changing the rules on their people midstream, and if you don’t like the direction of. Like tried it before and it was nice to have a non-social media site to have serious writing and reading of other serious authors, and now I’m getting short form reel videos on my homepage, and I didn’t sign up for this.

And if you’re a creator over there, you might be stuck. How do you port your audience over? It’s technically possible, so they say they’re open, but it’s a pain, and people don’t want to leave. And if you’re actually successful, they take 10%, which is great when you’re zero paid subscribers. But, there’s people paying $10,000 a month to Substack.

[00:12:48] Nathan Wrigley: They take 10%?

[00:12:49] Rob Pugh: 10% no matter what, which is great if you’re free, but if you have 100 paid subscribers paying you $10 a month, suddenly it’s insane. Like it’s a terrible deal and people feel stuck. Like WordPress even, wordpress.com, jetpack, if don’t like those rules, we can’t change them too much. You can go to any of the other great podcast hosts, or plugins.

[00:13:09] Nathan Wrigley: Yeah, I guess that’s a curious thing. And then you can embed those on your WordPress website and just carry right on as if nothing had happened. Yeah, that’s a really interesting point.

[00:13:15] Rob Pugh: Exactly.

[00:13:16] Nathan Wrigley: So from what I’ve seen, it looks like a really simple solution to implement. What I mean by that is, as a user of your product, it seems like you’re basically doing a bunch of stuff which as a WordPress user you would be simply doing anyway.

Like, you create a post. I don’t know if there’s a requirement to have a special custom post type for a podcast, or if you can just use regular posts. You go in, drop some audio in, and kind of you’re off to the races. Type some text and what have you.

Is it really as simple as that? Is it simply a case of make a post, drop some audio in? Or is there some stuff that you need to do in advance to prepare your podcast? So I’m leading you up the garden path with that question. Tell us how it works. What do you need to do in order to get started? How much work is involved?

[00:13:59] Tony: Yeah, I think that’s it. There are a few settings that are naturally required for starting a show. So you have your typical art for your show. You’ve got to set your categories and things like that in a setting. But then once that’s all set up, all you do is you create a new post, drop in the audio. We actually have an audio block as well, like a podcast episode block that will pull in a lot of the newer, fancier, podcasting 2.0 markup as well for you to do like chapters and things like that. And then that’s it.

As long as it’s within the category, it’s not a custom post type, it’s just a regular post. And then we are able to differentiate between an episode and just a post by two things. One, is it in the designated category that you set? And two, does it have the audio or video? We also have a few video files that we allow as well, and that’s it.

[00:14:46] Nathan Wrigley: Okay, that’s really neat. So you can use a regular WordPress post, but if you don’t assign it the category, let’s say in this case I’ve named it podcast, let’s go with that. If you don’t assign that category, it’s a regular post. Nothing off that tries to smuggle its way into your RSS feed, which would be attempted to be consumed by a podcast player. It just doesn’t go in there.

The minute I assign the category of podcast, drop in some audio, then it’s in that separate RSS feed. Dear listener, if you’re not familiar with that, basically a podcast is an RSS feed. That is literally what it is. Your podcast player is just consuming a bunch of text, which is an RSS feed, and interpreting that in a certain way with images and the audio and what have you.

And so that’s it. That’s all you have to do. Configure the settings, put a piece of audio in, assign the category, click publish. You’re done.

[00:15:35] Tony: Yep, that’s all. That’s all it is. I think the harder part is trying to come up with the titles and filling out the show notes. And, I have a friend who I got to start a podcast when we were working on this product, and he was using it, giving us feedback. But then, it’s like I looked at his podcast, and it was literally just like episode one, and it just, he’s like, “That’s the hard part, is coming up with all of the other stuff.”

[00:15:53] Nathan Wrigley: But you have Jetpack AI as well, don’t you? So there is an opportunity, I would presume, to lean into that. If you were to write a corpus of text that went alongside the, I don’t know, the audio, it could be a transcript or what have you. Presumably then Jetpack can go sift through all of that, and suggest some sensible titles if you really can’t be bothered to work out a title for the podcast episode. But then again, does it have the capacity to do things like trawl through the audio and transcribe and things like that? Or is that a bit roadmap-y still?

[00:16:20] Tony: Yeah. So that was one of the things that we wanted to work on was the ability to transcribe. And, because we have the privilege of working closely with Pocket Casts, we have, a lot of fancy tools that they have built already for their podcasting platform that we were going to try and leverage for the podcast show.

[00:16:39] Nathan Wrigley: Pocket Casts is an Android, iOS, and, it’s a web player as well. It’s a place where you go download onto your phone or what have you and play them. I have it, I use it every single week, and I’ve noticed that whether a transcript is made or not, Pocket Casts actually makes one.

[00:16:54] Tony: Yep.

[00:16:54] Nathan Wrigley: So if I ship a podcast without a transcript, Pocket Casts magically has a transcript. So I don’t know where that voodoo is happening. But that technology, you can then do double duty on that. You can take the technology they’ve built, use it in the Jetpack side of things, and do the transcription. Okay, that’s neat. Sorry, I interrupted. Apologies.

[00:17:11] Tony: You’re good. Yeah, that’s all of it. That’s, it right there.

[00:17:13] Rob Pugh: I think that’s a great segue into Pocket Casts, which in our opinion is the best app to listen to podcasts. The best platform. And one of the really cool things we were able to do with, because we work closely with Pocket Casts, is when you are distributing your podcast. We pick, just to start, the six biggest ones and hold your hand on submitting to them. But Pocket Casts is actually Automattic. Automattic, you can spell it with one or two Ts. And, if you click the button, it just is uploaded to their network It takes minutes, and it’s, some of the other ones, we hold your hand, but it’s a little annoying, and some of them can take a couple days, like Apple, to approve things. But, Pocket Casts just works. I don’t know if you want to add anything on that magic, Tony.

[00:17:52] Tony: Yeah, it’s very simple. It’s like right off the bat. If you already had an episode recorded, you could start a new website, upload your first episode, set your settings, and be on Pocket Casts, I would say, in less than an hour, honestly.

[00:18:06] Nathan Wrigley: Yeah, because you’ve got that tight integration.

[00:18:08] Tony: Yeah. It doesn’t say anything for the website configurations, which I’m sure would take more time, but at the very least, if you wanted to get your show out there, it’s a pretty instant approval.

[00:18:17] Nathan Wrigley: I think podcast players. If you’ve never run a podcast, there’s this whole dance that you have to do. The first time you ever try to release an episode, and that is to get it set up with the distribution channels that are popular. So I’m thinking of things like Apple Podcasts, and YouTube Music, and Amazon, and the list goes on and on. There’s, dozens of them, some more important than others. I think probably Apple is probably the biggest one, and maybe Spotify and some others come in second and third place.

But you have to do this thing where in some cases you have to go and get an account, and there’s really no way around that. Do you do some of that heavy lifting though? Do you make it easy for people to understand how to do it? When I did it, like 10 years ago for the first, and thankfully, only time I really ever had to do it, it was a case of going out and Googling it and reading things. But do you have that information in the UI to make that journey a little bit easier, reduce hours to minutes perhaps?

[00:19:07] Tony: Yep, we have a button.

[00:19:08] Rob Pugh: So there’s a distribution tab which lists the, all six like you mentioned, Amazon, Spotify, Apple, Pocket Casts, Podcast Index, which covers a whole bunch of minor networks. And I’d love to one day have it be fully automatic like it is with Pocket Casts. But some of them you need actual partnerships with these, Apple or Spotify to make that happen, and we haven’t prioritized putting a business person to go start a relationship and that.

So we will organize them for you and try and give clear instructions in our documentation to how to do it. But there is just a button then when you’re looking and it shows you the status of it, if it’s in or not.

[00:19:42] Nathan Wrigley: Okay. So you click the button, do the necessary thing, and then it will report back to you whether or not that has been successful. It’s a bit of a strange vestige really of the internet from way back when. It feels like in this day and age of everybody using APIs to connect to this, that, and the other thing.

But companies like Apple seem to be very unwilling to let that bit of their system be wide open. You’ve got to sign up for an Apple Creators account. I forget exactly what it’s called, but you log in and then you submit your RSS feed. It really doesn’t take that long, but you still have to do it.

[00:20:12] Rob Pugh: Yeah.

[00:20:13] Nathan Wrigley: And I think they’re doing it because they get to see from the inside out, how popular your podcast is. And I don’t know, maybe they can monetize things from their end. I’m not really sure how that works.

[00:20:23] Rob Pugh: It’s really another example of the closed internet.

[00:20:26] Nathan Wrigley: Yeah.

[00:20:26] Rob Pugh: Which is terrible. Why does Apple and Spotify need to be closed? So I think with having your podcast on WordPress with Jetpack, wordpress.com, and being in Pocket Casts, great. Then you’re, in the more of the open garden which is a better place to be.

And the cool thing with our stats, you can see who’s coming, like how many people are listening to your show on Apple versus Spotify versus Pocket Casts. So you know if you’re not getting any from Spotify, then you don’t even need to be there. Of course though, it helps with findability to be everywhere, so we want to give you that option.

[00:20:56] Nathan Wrigley: Yeah, at the end of the day, it all boils down to an RSS feed, which if it’s on your WordPress website presumably contains your domain name, forward slash, I don’t know, feed forward slash something maybe. So your RSS feed is going to be fairly short, probably very on message.

Does it work that way or does it have some sort of Jetpack or, I don’t know, WordPress.com thing in it? Because when you go to these other platforms, it’s typically platformname.com/randomstringof12characters or something like that, which is very hard to read out in your podcast. But the way you’ve got it built, it sounds like the sort of thing that would trip off the tongue. So you know, wptavern.com/podcast. Put that into your podcast player of choice and you’re done. I’m saying all of that like that’s true, but I don’t know if it is.

[00:21:40] Tony: Yeah, that’s it. Slash feed at the end.

[00:21:43] Nathan Wrigley: Okay.

[00:21:43] Tony: Because it is an RSS feed, yeah.

[00:21:45] Nathan Wrigley: That’s still fairly straightforward. But again, that’s a nice bit of branding, isn’t it? And, I think that’s really good.

Linking it back to the branding. We touched on this a minute ago, but if you haven’t started a podcast before, it may not be entirely obvious that you do want those other things like a newsletter, and like the ability to post to socials, and it feels like you’ve got the complete wraparound solution for that.

Because as your podcast grows, which let’s hope it does, then you will probably wish to have a relationship with your listeners via an email newsletter. You probably will wish to be posting on social media. You probably will wish to do all of these different things. So social posting, newsletter, RSS feed, WordPress as the sort of custodian of all the text and the images and the videos that I put in. Is there any other secret sauce that we’ve missed there? Is there any other sort of unique binding that Jetpack brings that we haven’t mentioned there?

[00:22:37] Rob Pugh: I’ll take it back first to like why we started this, and decided to build this, and I think you’re exactly right. First we found there are lots of WordPress.com and Jetpack users who have podcasts somewhere else. And that’s fine, but they were forced to because we didn’t offer it, and that really makes sense. Why would you need to go somewhere else?

So you say today, our goal in creating it was twofold for the people creating the platform. It should just be as easy as possible. Podcasting and writing is hard enough. You should focus on that. Let us handle all the difficult stuff.

Like you said, you need to, have a newsletter and a podcast and a blog and own all of it, and why can’t you do that with one publish event? And then from the consumer’s side of like consumer of content, some people want to listen to only podcasts, and some people want to read on a blog or, say, the WordPress.com reader. Shout out, go check that out if you haven’t in a while.

And like me, I prefer to actually read stuff in my email inbox, like a old weirdo. It shouldn’t be, you should let people consume however they want to, and it shouldn’t be a lot of extra work for you, the host, the creator, to manage all of these things on different platforms. Just have it be as simple as possible, and that was really our goal. And then, yes, exactly what you said with all the other Jetpack stuff. Social media is a great one. Gosh, you could go on and on. Performance, security, basics.

[00:23:46] Nathan Wrigley: Yeah. And it binds to, you said it just then, and it binds to the one publish event. So when I began my podcasting journey you end up with, like all these Zapier connections and different ways that, I don’t know, a webhook which goes off here and does a particular thing because you want it to be posted to this social network. With this, once you’ve got all of the bits and pieces configured, you click publish.

So you know, you do your audio, you write your text, you do all of that in a draft state, upload the audio. But the moment you click publish, the newsletter goes out, the social media posts go out, and all of that just happens automatically. And you don’t have to think about it. And they’re already there in your website.

It’s not like you have to do much. You just toggle, actually we should talk about that. You have to toggle the Jetpack podcast setting on, and presumably the newsletter setting, and yada yada, all those other things. But once you’ve toggled all those things on and got them set up, every time you click publish, all of those dominoes fall, and everything just happens on autopilot, which is really nice.

What do we need to toggle on? How do we set it up? How expensive is it? Let’s start there.

[00:24:50] Rob Pugh: I’ll talk about the pricing and then Tony can talk about the, the toggles.

[00:24:54] Nathan Wrigley: Excellent. Yeah.

[00:24:55] Rob Pugh: Yeah, we talked a bit about the pricing. I think that Automattic has always had a really generous free tier across its products, and it made sense for us to continue that. So you can today go to WordPress.com and start a blog for free.

It’s going to have some ads on it, but it’s free. You can have your newsletter sent out unlimited sends for free with unlimited subscribers, and unlimited podcasts for free. That’s like, amazing deal. We don’t get enough credit for that, but cool.

But we did build some compelling things to make you hopefully want to upgrade, or as you grow your podcast, you’ll find valuable. I think the stats are really cool. To me, all of the essential stats and none of the unessential stats, which if you’re an advanced podcaster might not be as good as you’re looking for. But, for most novice users, you just want to know the basics.

Anything beyond that starts to feel like Google Analytics, like, I’m lost. So just give me the basic. Are they coming on Apple? Where, how many listeners to which episodes, and where in the world are they coming from? Which refers, like which sites are they coming from? That’s a great starting place for me.

Help with distribution, the episode list, having a clear place for all your podcast episodes, the podcast block, really cool. And on WordPress.com too, we include the audio hosting once you upgrade. It’s not on Jetpack yet, so we’re waiting to see if, because we offer a similar thing for VideoPress, shout out best video hosting for WordPress.

[00:26:09] Nathan Wrigley: Yeah, there’s VideoPress will handle the video side of things. That’s becoming the thing, by the way. I’m sure you know that. But in the podcasting space, I went to The Podcast Show in London, about four months ago or something like that. Everybody’s talking about video.

[00:26:22] Rob Pugh: Yeah.

[00:26:23] Nathan Wrigley: And so that being bound into Jetpack as well is just another string to your bow. I’m just going to segue slightly. I think Pocket Cast does a pretty good job of doing things like HLS video. I could be wrong about that, but I’ve got a feeling it does.

[00:26:35] Rob Pugh: They even hook up with your Apple TV now, so you can watch and listen and yeah.

[00:26:40] Nathan Wrigley: Oh, so this is really clever and completely out of the realms of possibility just a year ago. So you could be listening on your headphones whilst you’re out walking the dog on your podcast player, so you’re only listening to audio. And you come back in, put your Apple TV on, turn on the Pocket Cast player, and it will seamlessly drop you right in the video at the exact moment where you finished the dog walk. It’s so clever and so neat. I love all that stuff.

[00:27:08] Rob Pugh: The future is so cool.

[00:27:09] Nathan Wrigley: Yeah.

[00:27:10] Rob Pugh: I love it.

[00:27:10] Nathan Wrigley: Okay. So Tony, how do we switch it on? Is it genuinely one toggle in the Jetpack settings, or is there a little bit more to be set up?

[00:27:17] Tony: Yeah, more or less. There is one toggle to turn the module on. And then once it’s on, you go to Jetpack and click on the podcast option, and then from there, there should just be one button that is to set up your show.

And all it really requires is you either creating a new category or selecting a category. And this is, as we were talking about before, the category feed that is going to be taken over from there. And then you technically are done. But it’s advised that you fill out all of the other base settings, and we walk you through all of the ones that are required by the podcast show apps, to make sure that you don’t get blocked by Apple or Spotify for not having the necessary settings.

[00:27:57] Nathan Wrigley: If I’ve been a podcaster for a number of years and I’ve got, I don’t know, a back catalog of 100 episodes or something like that. How do we handle that? How do we bring in previous episodes? And is there like an automated way of doing that or do I have to go and refigure 100 brand new pages on my WordPress website?

Is there any heavy lifting done there? Let’s just deal with the audio first, just the RSS feed and the audio. Is it a simple case of dropping the old podcast RSS feed in and you’ll capture all that audio and it’ll be on the Jetpack side of things? Let’s do that first.

[00:28:28] Tony: That’s a great question. I am not super familiar with the Core WordPress importer, but I believe that if there is a valid RSS feed with the normal RSS style tags, like enclosure and things like that, you should be able to import your RSS feed. Depending on how it’s configured on your current host, directly into WordPress. I’m not too sure what that would result in exactly. Especially because there’s a lot of different hosts out there, and it’s not like there’s one standard format for exporting your content. But yeah, that should get you part of the way there.

Then I think in the future, we’re really looking to start targeting some of the major current podcast hosts to be able to configure a migration flow to be able to come from those places to ours, in a more seamless way, albeit whatever sort of export they can give you or, whatnot. But I think that’s still on the horizon.

[00:29:27] Nathan Wrigley: Yeah, it’d be really nice to, let’s say I have 100 episodes and I’ve got, it’s over on whatever, hosting platform X over there, for my podcast audio feed. It’d be nice to be able to just suck in all the descriptions, and all the titles and have them be created as WordPress posts with the category assigned. So that essentially my WordPress site with the click of a button and the wait of an hour has suddenly got 100 posts of the podcast type all ready to go. And then, that’ll sit inside my SEO sitemap and all of that kind of stuff. That would be really interesting to be able to do, I think.

[00:29:58] Rob Pugh: Yeah, I think we will try and have that in the future. We usually do try and make importing, especially from closed platforms, super easy. An example, another Substack. We have an amazing Substack importer. They’re not a big podcaster yet, but they, do have some, and we can look at adding that. But if you have all of your newsletter on Substack, you click a button and we bring over your whole, build you a website, bring over all your posts, all your subscribers, even paid subscribers. We seamlessly transfer it to the Stripe account. Everything we’re building, we’re just trying to make it super easy for people to own your data, go wherever you want. We encourage movement in and out, wherever you want to go, it’s up to you.

[00:30:31] Nathan Wrigley: I suppose that then leads me to this question, which is, and you’ve probably just answered it. You’re not holding people behind some sort of paywall here. If people try Jetpack Podcasts out and they decide, “You know what? I really want to go the other direction. I want to maybe go back to where I was, or just move to a new host,” or what have you. You’re not holding any of that hostage, are you? You can take it and run with it and put it somewhere else?

[00:30:52] Rob Pugh: Yeah. Yeah, absolutely not. Like that’s the, I think, one of the fundamentals of WordPress. You should be able to move within WordPress and out as much as you want. I will say that this is a new feature that me and Tony have built. Just because something doesn’t exist in a super streamlined way, doesn’t mean it’s our intention to lock you in. So please reach out and we’ll happily help you migrate off if that’s your wish.

[00:31:15] Nathan Wrigley: So I’ll just let you know, dear listener, that there’s several URLs which rather than read them, because in many cases they can be quite long. But one of them, which is really easy for me to say, I might as well do that one, is wordpress.com/podcast. That’s probably the easiest one. Oh, and maybe this one as well, jetpack.com/support/jetpack-podcast. There’s several more.

[00:31:38] Rob Pugh: Let me jump in. Let me sorry, Because as of two days ago, we now have jetpack.com/podcast.

[00:31:45] Nathan Wrigley: Oh, okay. That’s way better.

[00:31:46] Rob Pugh: We just relaunched the entire jetpack.com site, which is cool. You should go check it out. Yeah, so.

[00:31:51] Nathan Wrigley: Again though, that, so what was that? Jetpack.com/podcast is kind of the home for all of those bits and pieces.

[00:31:56] Rob Pugh: Yep, exactly.

[00:31:57] Nathan Wrigley: In which case, go there. That’s where you’re going to find all of the bits and pieces and I presume, when things are, adapted and modified.

[00:32:03] Rob Pugh: Yeah, the way to think about it’s still for some people confusing about Jetpack. So if you would like a website, the best WordPress hosting, then go to wordpress.com/podcast, and we’ll host your podcast for you. And if you want to host somewhere else, that’s great. Go host your WordPress site somewhere else, then go to jetpack.com/podcast and we’ll get you all set up as well.

[00:32:23] Nathan Wrigley: In which case, I will say thank you Rob, and thank you, Tony. Thanks so much for chatting to me, both of you.

[00:32:28] Rob Pugh: Yeah. Thank you Nathan.

[00:32:28] Tony: Yep, thank you.

On the podcast today we have Rob Pugh and Tony Arcangelini.

Rob and Tony are longstanding members of the Automattic team, with extensive backgrounds in marketing, product, and software development. They’ve spent years building tools for creators, writers, podcasters, and everyone in between, and are now fully immersed in WordPress’s evolving podcasting capabilities.

If you’ve been looking for ways to run your podcast from your own WordPress site, this conversation is for you. Rob and Tony dive into the new Jetpack podcasting features and why they made the leap from WordPress.com’s basic audio offerings to a more robust, integrated solution within Jetpack. They talk about what makes WordPress and Jetpack such a powerful home for creators: the ability to bring your newsletter, blog, podcast, and all your content and communication under one roof, all while keeping ownership of your data.

We talk through the advantages of keeping your content out of walled gardens like Substack and Patreon, and the value of flexibility, whether that’s adding WooCommerce to sell merch or customising your site’s look. Rob and Tony break down just how easy it is to start your show, drop audio into a post, set your category, and let Jetpack handle the rest, from distributing your RSS feed to major podcast apps, to sending out newsletters and automated social posts.

They also get into how integrations with Pocket Casts and Jetpack AI make content creation, transcription, and distribution smoother than ever, plus how WordPress’ open foundation promises you’ll never be locked in.

If you’re a creator wondering how the next generation of podcasting fits into the WordPress ecosystem, or just want an easier way to launch and grow your show, this episode is for you.

Useful links

Pocket Casts

VideoPress

The Podcast Show London

Podcasts on wordpress.com

Podcasts on jetpack.com

💾

#234 – K. Adam White on Migrating to Blocks With Artisanal Care and Enterprise Efficiency

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, migrating to blocks at an enterprise level and what’s involved in moving from a different CMS into WordPress.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.

So on the podcast today, we have K. Adam White, or K. Adam for short.  K. Adam is the principal engineer at Human Made, an enterprise WordPress consultancy. He’s been involved with WordPress for almost 20 years, attending his first WordCamp in Boston back in 2011, and has contributed to WordPress Core and the broader open source ecosystem. Human Made is known for delivering complex projects, think high stakes, no room for mistakes? From global brands moving to WordPress.

This time around,  K. Adam delivered a presentation at WordCamp US focused on a crucial topic for anyone modernising their site, migrating to blocks. Human Made has been all in on the block editor since the Gutenberg plugin days, and the team now specialises in large scale migrations from other content management systems like Sitecore, as well as from other WordPress page builders.

Our conversation focused on the technical and editorial challenges of moving tens, or hundreds, of thousands of posts into the world of blocks and patterns. We talked about the need to combine artisanal care, attention to detail in design, layout, and brand, with industrial scale. The ability to automate, audit and validate mass migrations without losing visual fidelity.

We also discussed the use of patterns as a foundation for development, integrating custom and Core blocks, and leveraging new tools, including AI powered agents and open source plugins like Human Made’s, own rehydrator, to streamline migration workflows.

We also touched upon how clients are onboarded. The process of auditing legacy content. Strategies for training editorial teams on the block editor. And there’s a frank reflection on gaps in WordPress, like granular content permissions.

If you are contemplating a move to the block editor, wrestling with a massive content migration, or curious about what happens when enterprise complexity meets the flexibility of WordPress, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you  K. Adam White.

I am joined on the podcast by K. Adam White. Hello, K. Adam.

[00:03:41] K. Adam White: Hello. It’s good to be here.

[00:03:42] Nathan Wrigley: Yeah. Thank you for joining us. You have an interesting name. Just go on, I know it’s totally off piste, but tell us about your name.

[00:03:49] K. Adam White: Sure. It’s a first initial K, and the middle name Adam that got conjoined in college and I quite like it. So I think in a sphere, and a particular niche in WordPress with so many Adams of so many different colours, then K. Adam is a little bit more me.

[00:04:04] Nathan Wrigley: Yeah, nice. So we’re in the corridor, so forgive any noise that you hear on this podcast episode. We can’t avoid it. We’re in the corridor at  WordCamp US, and you have done, some presentation work this time around. Do you want to just tell us, I mean I presume it’s happened because we’re at the very closing stages of the conference. How did it go?

[00:04:21] K. Adam White: It went, as far as I can tell, quite well. My session was early yesterday, right after the morning keynotes in that early slot where everyone’s coffee has kicked in, and the fatigue of the conference hasn’t quite set in yet.

So I had a great audience and the talk I thing went quite well. I’ve had a number of different conversations off the back of it on various different topics that I covered. So the breadth of those discussions has been really exciting for me.

[00:04:44] Nathan Wrigley: So that is going to be the meat and the bones of what we’re going to talk about today. But first, if you don’t mind, let’s talk a little bit about you and what you do and where you work, just so that we can paint your credentials if you like.

So tell us about your job, how long you’ve been in the WordPress space? Who do you work for? Et cetera.

[00:04:59] K. Adam White: Yeah. My job is principal engineer at Human Made. We’re a WordPress enterprise consultancy, and I have been there nine years. I’ve been in the WordPress community quite a lot longer than that. My first WordCamp was WordCamp Boston 2011, which is a mind boggling 15 years ago now. And before that, I had been using WordPress personally since 2007. So we’re coming up on 20 years of involvement, at least as a user. And then, became a contributor in the early 2010s around 2013, I think my first commit landed.

[00:05:25] Nathan Wrigley: Yeah, nice and Human Made, if you haven’t heard, we’ll put the links into the show notes, anything that K. Adam mentions today, we will put us a link on the WP Tavern podcast episode website, so you can click through to it. But go and check out Human Made, definitely one of the big hitters. I think it’s fair to say in the WordPress space.

[00:05:40] K. Adam White: It’s very kind of you to say so.

[00:05:42] Nathan Wrigley: You did your presentation and it was entitled, Migrating to Blocks. I’m going to intuit from that, that Human Made is all in on the block editor. You’re not using some sort of other proprietary platform. Would that be the case?

[00:05:55] K. Adam White: That would be the case. We were very early adopters of Gutenberg back in its plugin days. We were doing work before it was merged for building out some early block sites, testing out what we could do. Learning how to build and change our theme development processes to move in a more block oriented direction, and then follow that directly into the Full Site Editor world.

And it’s been a great ride. We do work with other page builders and other blocks, platforms and frameworks. We do tend to, as a company, work on projects that have some sort of particular technical complexity that made someone come to us rather than a different agency.

That does mean that we are broadly specialised in WordPress as a platform, including many of those page builders. We’ve worked with Elementor, we’ve worked with Divi, Beaver Builder, but we as a company will always advocate for the block editor and the site editor. And we have our own processes oriented more and more towards delivery with that framework in mind.

I think that the thing that is bringing some of the companies that we help to migrate to WordPress into this ecosystem is the flexibility and the quality of the editorial experience. And personally, my opinion is that Gutenberg does that leaps and bounds better than any of our other page builders that don’t have that native integration into the platform.

[00:07:09] Nathan Wrigley: So if a client comes to you and they are agnostic as to what you are going to build with, your default posture would be we are going to use the block editor.

[00:07:16] K. Adam White: Absolutely default.

[00:07:17] Nathan Wrigley: Okay. And do you have to do any level of persuasion anymore? I’m guessing if we were to rewind the clock, let’s go to 2017, soon after Gutenberg started to become more widely available. I imagine there was quite a bit of explaining to do. Do you still have to do any of that? Or is it a case now that the enterprise people understand what’s going on, and there’s less of a back and forth about whether they should use blocks and patterns and whatever else?

[00:07:41] K. Adam White: If we are building from scratch, we haven’t found there is any reluctance. Particularly if people are coming from a different content management system, particularly a different enterprise content management system. The editor is so compelling, that there’s never any objection to using it. They might ask, should we use this or some other thing I’ve heard of? And we can say, the block editor is built in. We feel that it’s the most robust and future proof platform that you can choose. So we would recommend going that route rather than adding in another plugin, however good they are.

But we do still, nonetheless, have some projects where they are already on a page builder, and they might have invested a lot of training. We might have an entire business school worth of people that are very comfortable with whatever their existing system is, whether that’s Beaver Builder or something else, et cetera, Elementor.

And I think that it’s very important for us to remember what our remit is when we come into a project. That, doesn’t always involve helping them change everything to match what we see as the future. I think that’s a responsibility of the client to understand where they are in conjunction with where the WordPress roadmap is, and make their own decisions about what tools are right for them.

So, for existing projects, we’ll work with what’s right for the clients editorial team, but if we have to make a recommendation, it will always be the block editor.

[00:08:56] Nathan Wrigley: Okay. Yeah, good to know. At place in the market where you are, I’m presuming there’s very little room for error. When you build something, it’s got to work out of the box, on day one. You’ve presumably got stakeholders who’ve got editorial teams, and they’re fairly, we’re, dealing with large corporations that can’t afford for there to be mistakes.

So that kind of leads us to the nature of your presentation, which was called, and again, links will be in the show notes on wptavern.com. Migrating to Blocks with Artisanal Care and Industrial Scale. And I’m actually just going to read the first paragraph because it summarises what we’re going to talk about perfectly. It’s fairly long, but I’ll go through it all.

Whether we’re modernising an old personal blog or migrating hundreds of thousands of existing posts from another CMS. Using WordPress in 2026 means converting our contents to blocks. The convert to blocks button in the editor works well enough for one post. But if we have dozens or hundreds, what can we do to make the process less manual and more powerful? How can we integrate a site’s content directly into full block patterns without losing the columns and structure it had before? And then it goes on to mention, a particular build, I presume, where you were leaving one CMS coming into WordPress.

Just lay out some of the fun, interesting problems that you have to overcome when you’re moving from an entirely different CMS into WordPress, because I guess it’s more complicated than, “Look, there’s a bunch of paragraphs and images. Let’s just drag those over and hope for the best.” Tell us what the problem before you is.

[00:10:22] K. Adam White: That’s a great question. It’s actually remarkable how close you can get to satisfaction with just moving paragraphs and images over and hoping for the best. But there is a big gap in terms of visual fidelity.

The editor in a theme that we’ve built for a client will be configured with patterns and templates and all of the block variations that they need to be able to very quickly sketch out a page. If they are starting from scratch, a client with a fully site editing enabled theme can drop a hero pattern on the page, set in the media they need. Change any font sizes within the pallet of what’s available with their brand guidelines encoded in the theme.json. It’s very easy for them to build out and write content fresh.

But if you have, again, hundreds of thousands of posts, even if you’ve built all those patterns, the heading and paragraph and image only approach doesn’t cut it, because then there would be a tremendously backbreaking amount of work, adding group blocks, adding background colours, et cetera.

That’s usually data that is available in one form or the other in the current system. If we’re migrating without a design change, we will have, whether it’s the layout database in Sitecore or a metadata in a different WordPress block editor that we’re migrating from. Or whatever the equivalent is in our source. We want to preserve the layout of the page and the styling elements. So making sure that headings get the right text treatment, that anything that’s italicised comes over. All of the nuances there, particularly around background colours, images, et cetera. That’s the piece that we’ve been over the past year, looking at how we can improve our process when we’re building a new site, but bringing content over from an old.

Within that context, my talk covered two broad areas. The specific tail end of the talk was about how we can actually use the theme patterns that already exist in the theme directory, and use those to inject particular pieces of source data. So if you have a pattern for a hero element, and you know from your source data what the image URL is supposed to be, what the title is supposed to be. We can use the HTML directly from the pattern file, and do lightweight search replaces within that using either direct PHP string replacements or a tool that we’ve written, that I shared a link to called rehydrator, which is a very early stage experiment, that we’ve got out on GitHub.

And we can use that to put the content into the structure that it’s going to need to have for it to be fully, visually correct. So rather than just reducing and throwing away anything that isn’t a heading or a paragraph, we’re taking the framework from the theme pattern that’s been built. And then we’re writing a migrator that takes data and puts it into that HTML structure, and saves that into the post content. So that when an editor opens up a page, it loads correctly in the editor without block validation errors and it looks right on the front end.

[00:13:15] Nathan Wrigley: Okay. There’s a lot of depth in that, isn’t there? We’ll come back to that in a moment.

I’m curious about process of how you, persuade clients that you are going to be able to carry this work out successfully. So how does that actually work? You obviously look at their existing content, you have a discussion about what the new design is going to look like, and then do you build out some kind of templates or patterns or what have you, so that you can then pull in a proportion of the content, maybe, I don’t know, 10 or a hundred or 5,000 or whatever it may be, pieces of content. Check that that’s all right. Show it to the client. How does that workflow go to build up their confidence that what you are going to do when you finally click the button is actually going to succeed?

[00:13:50] K. Adam White: The way that we’ve been approaching that, I think particularly, over the past six months, I should caveat first that this process has changed so much. Because the tools we have available with AI agents have been evolving in leaps and bounds alongside this particular migration process, which started in January.

So in this case, we started out by building patterns that we could put content for one test post, from the existing site manually. Bringing the contents over, copying and pasting headings, et cetera. And using that to create the patterns that we could show to the client to say, does this look correct? Does this structure mirror what you’re expecting? Is this what you expect an author to have available within the post editor?

And then you know, which pieces belong in the template, which pieces are managed at the site editor level? We’ve done a lot of that ahead of starting the actual migration.

Now that the migration is in progress, any subsequent pieces we’re developing in tandem, we’re saying, okay, we have a press release. That press release, we have audited the incoming data, and we have determined that there are four different layouts for press releases. And this one is used the most and it has these elements. This one is used less, but it has images, et cetera.

And we can build the template for that post type, and at the same time write the migrator for identifying the content nodes, and the source data and bringing that information over into the new patterns.

So we have the patterns that we can show, okay, if you’re building something from scratch, this is what that looks like in the editor. But then at the same time, we can run the migrator over, in most cases, all of the relevant type of data and say, and here is a list of pages to validate.

So what we’ve been doing is bringing that to our stakeholder, and allowing them to do spot checks, so that they can look through and validate that there are all of the required elements on the test pages. Things like, “oh, alright, we don’t have a mapper yet for video embeds. So videos are missing,” and that’s usually going to be an all or nothing thing. We’ve found very few cases where we end up with one or two errors on a specific post basis that aren’t related to support for a complete type of output pattern.

[00:15:55] Nathan Wrigley: Is there a sort of fault tolerance there? So obviously in the case of this particular migration, tens of thousands of posts, I guess there’s never going to be a moment where you can be a hundred percent confident apart from reading the 10,000 posts that you’ve done everything correctly. Is there a, we’ll do 10 to begin with, then we’ll go up to a hundred, then we’ll go up to a thousand.

What, is the sort of tolerance that you present to the client? I’m just imagining that just lurking in post 9,999 is just some weird thing that was allowable in the CMS but never got used before or since, and that piece of content got missed. I don’t know what’s allowable in that scenario. So is there any level of tolerance for fault?

[00:16:32] K. Adam White: The major advance that we’ve made with migrations as a broad structure this year is a much better understanding of those edge cases. And the way that we’ve done that is by leveraging Claude and various other tools to do cross site audits to make sure that we have a full picture of the source data.

So we are able to feed in whatever export files we get from our source site. In this case we’re working from Sitecore, which is an enterprise CMS, which has two database structure. There’s actually a database with a content tree, and then another database that contains layout information. And a page is rendered by switching back and forth between those and assembling the final output.

We were able to get exports of the relevant content from both of those, from the developer of the current site. And we fed those and a whole bunch of documents from the product owner into a ongoing conversation with Claude. And we’re able to use that to build some actually node.js scripts that would take the files we’d gotten from the Sitecore devs, and build a local database in SQLite that each developer on the team was able to run locally. And we can query against that to find those edge cases.

So in a combination of writing our own manual queries, or having a chat conversation prompt for finding individual things, and then it will run a number of queries and report back to us. We’re able to identify very quickly, oh, there’s only one press release that has images, that’s interesting. But there are 17 that have a FAQ accordion.

So that type of auditing has become trivial, and it’s mind boggling how much faster that’s allowed us to move in terms of understanding the data that’s there, and building out a mapping of how we’ll migrate through the different types of content.

We don’t tend to start with only 10 pages in a post type because it’s relatively cheap to run the migrator over a thousand instead of 10. And that gives you a lot more content for both various people on the client team, but then also agentic tools to click through and do a little bit of spot check validation.

What we tend to do is to migrate content type by content type, and we’ll prioritise those based on what we see as the balance between scale and complexity.

[00:18:39] Nathan Wrigley: Do you leverage Core blocks wherever possible, or do you bring bespoke Human Made blocks where that’s necessary? Or can you basically bind everything in this particular build to a Core block?

[00:18:51] K. Adam White: Most of the time we will start with Core blocks and get as far as we can with them. This is a change from how we used to do it. Our early days, we had a lot of rapid iteration in the markup that Core blocks were using. In some cases, there was a lot of evolution in how the controls for them were set up.

[00:19:07] Nathan Wrigley: It was brutal.

[00:19:09] K. Adam White: It was brutal. But that pace of change for the main building blocks of a site has slowed down tremendously, and I think it’s a very stable foundation. So we will be pattern first in our development. We will start by working, doing a lot of in-editor prototyping actually, to build out layouts and patterns for each individual unit of content, each individual sort of component group in the source site. And, it will only be when we run into something like a carousel or a modal that we might reach for a off the shelf, third party option that’s not in Core, or bring our own solution to the table.

[00:19:45] Nathan Wrigley: So do you take, when you said pattern there, is a pattern a sub component of a, let’s say post for want of a better word? Or is it that the pattern is the entire post with bits injected into it? So paragraphs, headings, videos, whatever it may be? Like I said, at the beginning, or are you building up the entire post from various different patterns? Here’s a video pattern and here’s a, I don’t know, a paragraph pattern with a heading? Or a background image or whatever it may be.

[00:20:12] K. Adam White: Patterns tends to be at number of different levels. We might have individual patterns for a particular treatment of headline for example. But we also will have a pattern for a hero section. We’ll have a pattern for a hero section plus the bio below that, that we can use to populate a template in the site editor.

We build patterns at multiple levels of granularity, and we have a leaf to trunk system where we’ll make sure that we have renderings, whether they’re Core blocks with either default styling or one or two block variations, or individual patterns for things where we need to compose one or two blocks together. We’ll make sure that we have all of those leaf node pieces of content, all of our paragraphs, all of our inline images. And then we’ll build patterns for those higher level groups, the full width backgrounds with coloration and a particular headline treatment.

We build out those patterns at all of those different levels because it’s nice to have the granularity when we’re writing our migrators, and patterns can reference each other. So you can have an accordion pattern, which includes two references to an accordion item pattern, and you can have all of those little bits of HTML be discreet PHP files in your WordPress theme. So it makes it very simple to pull up in your editor only the code that you need to edit for a particular unit and know how that’s going to be scoped.

[00:21:26] Nathan Wrigley: This is going to sound like such a peculiar question, but it genuinely, from my point of view, this sounds like really interesting and curious work. It sounds, like there’s a lot to get your teeth into. You’re pushing the boundaries a little bit, but also you’ve got the scope of WordPress, which kind of makes it slightly easier.

I’m basically just making the comment that I think I would enjoy doing the work that you are doing. I don’t know if that, yeah, there really a question there.

[00:21:47] K. Adam White: Unfortunately, we’re doing less and less of that work, and Claude’s doing more and more of it. It’s been actually very efficient because this is such a core central construct in the WordPress block editor. There’s a lot of good documentation about it and agentic tools are quite good at helping to build pattern markup.

So, what we’ve been doing is bringing our human eyes onto that, doing all of our spot checks, making sure that things are kept as simple as possible. Because I think we’re all familiar with how verbose and overly complicated output can be from some tools. But then it is also something that I really wish more people were talking about and doing. Brian Coords earlier today in his talk, mentioned that pattern driven development really he sees as something that more and more of the WordPress community should be trying out. Because there are so many things that we used to build custom blocks for, that just strictly aren’t necessary anymore. And we can get so far by composing what we get from the lego kit of WordPress out of the box.

[00:22:40] Nathan Wrigley: Yeah, I feel like if we went back to 2015 and began Gutenberg again, I feel going patterns first would actually be a nicer approach, certainly a more straightforward approach. I know that there’s, ways to overcome that, but I always drop patterns in, never blocks, and then I’m always interacting with the blocks within the pattern. But it’s patterns first for me all the time. Just because I like the fact that I’m dropping in multiple bits of content that are pre-configured and pre-made and pre, I’ve fiddled with the CSS and made it just how I like it. And I just click the button once and there it is, and I can just rinse and repeat and it’s really straightforward.

[00:23:12] K. Adam White: I would agree, and over the past two to five releases of WordPress, we’ve also had such powerful additional tools added to the pattern toolkit. For example, Partially Synced Patterns. Was a major topic that I shared in my talk. Being able to have a reusable pattern and then make the content editable on a post by post basis makes it very seamless for a non-technical editor to go in, and not have access out of the box to stylistic controls that would make something drift from the brand’s guidelines that they’re trying to follow, but still be able to customise link targets, CTA, text, all of the descriptive and image elements.

[00:23:47] Nathan Wrigley: You are in the weeds of WordPress, and I’m in the weeds of WordPress all the time, but I still feel those tools are widely, not misunderstood, that’s the wrong, just there’s a void. Nobody even knows they’re there. There’s just tonnes of tooling inside the block editor that people simply don’t know about, because the UI and the UX is still a bit funky. You’ve got to go to various different places, and it’s easy to go down the wrong route.

Do you know what I mean? There’s a bunch of tools inside a WordPress that if you only had a few hours with somebody over your shoulder pointing out, “okay, click on that, look at that menu that does this thing.” It’s a shame in a way that’s the case. But I do feel there’s a lot of unexplored potential in every WordPress website that presumably you are leveraging. But I guess just because you’re in the weeds of it.

[00:24:30] K. Adam White: Wherever possible, we have the privilege of having a lot of history with the CMS. Human Made was founded in 2010 and has always had a strong open source posture. We’ve contributed to Core, we’ve put plugins out there in the ecosystem that are used by a number of other agencies. We’ve found the best of what our frenemy competitors use, and been able to adopt those into our own processes.

And the benefits of understanding all of the different types of block that you can use tremendously outweigh any time sink that it takes to learn them. I hope that, from my talk, people will now know that in 7.0, we added PHP only blocks, where you can have the attributes auto registered so that you get, even as a non JavaScript developer, a interface in the editor that someone can open up and go in and change values in the sidebar.

I hope that more people learn about Partially Synced Patterns. I hope more people learn about all of the different types of block that we have available, and find ways to integrate those into their own toolkits. Because playing with the grain of WordPress and using the Block Editor for all it’s worth, are how we untap the most value for our clients.

[00:25:34] Nathan Wrigley: Yeah, there is certainly an awful lot of power, and like I said, I just think some of it gets missed.

How much after you’ve done the migration, how much time do you have to spend with the clients? I have this impression that the Gutenberg editor is pretty straightforward, muscle memory for me essentially. Hours of playing in it. I know where all the bits and pieces are.

But I would also recognise that if I was to show it to somebody who’d never played with WordPress and was coming from, in this case Sitecore, how overwhelming is it? And do you take steps to make it less overwhelming by minimising what’s available in the interface, or just disabling options? What do you do in that regard?

[00:26:08] K. Adam White: No matter how much flexibility our clients want, it’s usually valuable to disable some options. I can’t remember a site we’ve shipped recently for any large website where we left the custom colour picker in, for example. You want to do a better job of limiting what people can use, so that we have confidence that the output, no matter how design savvy or not someone is, is going to be consistent with the rest of the site.

My colleague, Joeleen Kennedy, gave a talk a couple years ago at the first  WordCamp US Showcase Day back in 2024, about work we had done customising the editor for that type of simplicity. And in particular things that we can do around colour palette selection. Ways that we can hide the styling controls for certain blocks through having them embedded in a pattern.

It’s interesting to see that in WordPress recently, if you are editing content that has been marked as having come from a pattern in a post, you can edit all of the text, you can edit all of the images and link targets, but you actually have to hit edit pattern in the sidebar in some cases, depending on how the post is set up, to get into the details within the post that allow all of those other controls to be visible.

That divide took a tiny bit of adjustment for people on our client teams, but the separation has helped them stay focused on the content, and worry less about the overwhelming, combinatorial set of styling possibilities that their blocks have.

[00:27:29] Nathan Wrigley: Do you think that the necessary tools are already built into WordPress to do the kind of work that you are doing? Or is there some missing piece that would make it easier for somebody who doesn’t have the deep pockets that presumably Human Made would require, to do that kind of work. Is the default tooling usually okay to migrate things or have you had to build loads of bespoke tooling?

So in terms of if I was to approach a WordPress website and try to migrate from Sitecore over to WordPress, is this something that you absolutely need a team to do, or would you be able to get some simulation of this with Core WordPress?

[00:28:04] K. Adam White: If you had access to the exports of data from a Sitecore website, and you had a core vanilla WordPress install. And you had a LLM tool of some sort, I think that you could do a lot to get close to what you want. The LLM piece, I think enables this to be done by more people without having to be completely familiar with all of the internal nuances of WordPress. You need to direct it to the architectural pattern that you want, but we have found that it speaks Gutenberg pretty well.

[00:28:32] Nathan Wrigley: What was the name of the tool that you said you’d custom and built?

[00:28:34] K. Adam White: We had built a plugin called rehydrator.

[00:28:36] Nathan Wrigley: Okay, rehydrator, yeah.

[00:28:37] K. Adam White: rehydrator is the tool that we use to take a pattern in the theme and then use that pattern as the template when we’re bringing content over to make sure that we keep all of the styling theme side, and that our migration script doesn’t duplicate the markup specifically.

[00:28:51] Nathan Wrigley: What’s Human Made’s approach to the WordPress project in that regard? You said it was a plugin. Does that mean it’s a wordpress.org repository plugin, or is it one that you have on your own, I don’t know, GitHub repository or whatever it may be.

[00:29:01] K. Adam White: We have some things in the .org repository. In this case, that particular plugin is only on GitHub. A number of ones that we build are only on GitHub, because we’re building them for a very transient in time period of a site.

You don’t need a migration tool to be part of your site long term, it’s not something you’re going to be leaving active, and updating month over month when there is a site running. It’s something that you bring in for the purpose of populating the data. And then you can remove that.

And in that regard, for this particular one, at the moment it’s partly because it’s quite young, and it’s also because we don’t see it as being general purpose. So that plugin specifically is on GitHub and publicly available through Composer, but not on the plugin directory.

In other situations, we’ve gone the opposite direction, and anything that we see as being a ongoing value to a site as it’s running, we do try to move those over as we can.

[00:29:52] Nathan Wrigley: Given that you are on the sort of engineering side of Human Made, I don’t know if this question will land, but we seem to be in this interesting period where there’s a lot of chatter, AI kind of fits into the equation a little bit, but there’s a lot of chatter about the, market share of WordPress and whether or not WordPress as a tool will continue with the same numbers and clout and market share and all of those kind of things.

Do you notice at the enterprise level that there’s been any kind of change in a southerly direction? Maybe there’s been a direct change in a northerly direction. What I’m trying to say is, for the enterprise, does WordPress still maintain that kind of pride place, top of the tree, or are you struggling to find new clients?

[00:30:28] K. Adam White: We’re not struggling to find new clients. We’re lucky that we’re doing quite well on marketing, and we also have had a very powerful year in terms of building relationships with new enterprises, and finding ways to take the technology that we believe in and solve their problems with it.

But I would argue that WordPress has never been the top of the enterprise space. And this actually goes back to your question about what is there that might be missing inside WordPress. The biggest thing that I think someone gets from a more, I’m going to use the term loosely, traditional enterprise CMS, is control.

And WordPress has a security model where the ability to edit and publish a piece of content is usually at the post level. There’s ways to add specific permission checks for metadata. There’s ways that you can restrict what’s accessible and editable with custom interfaces and custom API endpoints. But we tend to have things fall down to the capability checks for user can edit post 1, 2, 3. Yes. No.

And that means that if you have a user profile where your organisation depends on someone being able to come in and touch only the headlines and the SEO metadata, we don’t really have a model for that right now in WordPress.

Whereas something like Sitecore, each individual, almost at the level of every string on the site, whether it’s a set of paragraphs or the label of a button, ends up as a individual node in the content tree. And those can be granted or denied to certain users on a much more granular level. So that to me is a bridge that I still am excited to see what we can do within WordPress to maybe build better interfaces, or better primitives in the editor.

Block locking helps a little bit, but it is an API that’s quite difficult for some teams to wrap their heads around. And it also doesn’t really change the fact that if you can edit the post, and you were able to get the code editor up, then if you’re able to save it, you’re able to save it and doesn’t really go block by block. You’d have to write custom validation or permissions logic in order to be able to reject and update based on the user if they’re editing a block that is next to the one that they were supposed to.

[00:32:32] Nathan Wrigley: So do you have to present to the clients? It’ll be fine. This is what WordPress has. Don’t worry too much about it. If you’ve got this permission, yep, sure. You might be able to overlap and think people could delete things or modify things that perhaps they wouldn’t have to. That’s an educational piece on your side. Go and teach everybody not to mess around with things that they shouldn’t be messing around with.

But you would wish that in WordPress you could assign, say, as you described, this H1, this person can amend it, and this person can access the colour palette for the background image over here, but they can’t access the text. That kind of really granular permission. Whereas block locking just, it seems a bit more of a blunt instrument if you know what I mean. It’s binary. It’s locked or it’s not. You’d like to unlock the capabilities within each block so that certain users can do certain things within the same block.

[00:33:15] K. Adam White: Within blocks, we tend to rely on security through obscurity. We can hide or obfuscate controls behind block locking with content only. We can hide them behind patterns. But if someone’s coming to WordPress, we do make sure that they understand upfront what the nuance of control will be. And we will work with them usually to make things more editable.

Again, I will mention that most of the projects that we get that come from one of these more control-oriented CMSs into WordPress, what they’re seeking is actually more flexibility, not less. So they’re making a decision that they are willing to exchange the stringent control that they get in their existing tool for a process-based change. Maybe they add a review step, or add some sort of workflow plugin, so that we can validate that things look good and have someone sign off on it before it gets published. They would prefer to go that route than to sacrifice the ability for the editors to have the full control, and full pallet of options available to them.

[00:34:13] Nathan Wrigley: Right, so that’s a much more loose approach. Everybody can maybe do more than they ought to do. If we have some editorial guideline where that can’t finally hit the public domain because the publish button is unavailable to you, that’s, okay. We’ll accept that kinda halfway house, if you like. That’s interesting.

[00:34:30] K. Adam White: Each client’s needs are going to be slightly different. We do layer in publication checklists. We have tools to be able to say, this has to be tagged with the primary category before it goes live. We have tools to say, this still has lorum ipsum in it. You can add those in and build workflows, but I tend to like to help clients build processes to support those, rather than trying to take a draconian approach and lock everything down. Because then your work is going to be constantly chasing fine-grained permissions controls when you could be working to use that time making sure that all of the editors know what they can do.

[00:35:04] Nathan Wrigley: I just want to drill into this a bit more. I know this isn’t where we were supposed to go, but I find it really interesting. Would you like those things to ship in Core? obviously they suit you down to the ground, all of those granular permissions, but do you think that belongs in Core?

[00:35:17] K. Adam White: I think that we need more workflow in Core.

[00:35:20] Nathan Wrigley: Okay.

[00:35:20] K. Adam White: I know that there’s a number of different agencies and hosts which each have developed our own workflows solutions. I’ve worked across a number of them on projects that I’ve helped to support.

But the notion that if you have something published and you make an edit out of the box, WordPress will automatically put live any further changes that you make to a published post when you hit save. That is probably the single thing that we most frequently have to build some type of plugin into a site to handle.

Because we need to be able to give people an editorial review step. So that is something that I think we have a number of good tools, but I would love to see a more opinionated default in Core that we can use as a foundation for more complicated post editorial workflow. I think that’s the thing that we most frequently run into. That, and also I guess internationalisation are probably the two things that hopefully will come to the surface of the WordPress roadmap over time.

[00:36:13] Nathan Wrigley: Yeah, I’d really not thought about that. Given Human Made’s sort of credentials and what have you. Do you have a lot of clout? Do you just punch above your weight in conversations about what makes it into Core? Do you get involved in those discussions? I’ve literally no idea how that would happen. Do you communicate to people when a release is coming around. Do you have a voice? Do you make yourself available? What is Human Made’s position in terms of getting things pushed into Core?

[00:36:37] K. Adam White: We participate in the project. I personally have been less involved in Core over the past several years than I would have hoped. I’ve been very much enjoying the detailed, quite close to the ground work that I’m doing on our agency projects. But unfortunately, I have taken a bit of a step back on the open source project.

Some of my colleagues are in a slightly different boat. My colleague, John Blackbourn, our Director of Security for our own hosting product is also the head of the Security Team for WordPress? And has been helping us get the core patches out for the recent set of security releases.

We obviously will advocate in calls for feedback within the Gutenberg project when we feel that there’s a particular direction that we see from our projects. We are able to provide feedback on the UI, and the capabilities of new blocks that are being proposed. But that’s all done through the normal Gutenberg GitHub issue, and WordPress

[00:37:28] Nathan Wrigley: So I think we should probably knock it on the head there. We’ve reached our allocated time. I’ll just point out that these days, it used to be the case that if I was at a WordCamp, you’d really have to wait about six months before the video for the presentation was available. I’m pretty sure it’ll be done already, in all honesty. 24 hours seems to be the time there. So if you were to go to WP Tavern, I will make sure that the link to the video, of K. Adam is there. If not, you can probably go to Google and search Migrating to Blocks, and in parenthesis, with Artisanal Care at Industrial Scale, and you’ll be able to see what it is that K. Adam was talking about.

But really, thank you so much for chatting to me today about all of that.

[00:38:06] K. Adam White: Thank you very much. And I can confirm that the video is already live on YouTube.

On the podcast today we have K. Adam White, or K. Adam for short.

K. Adam is the principal engineer at Human Made, an enterprise WordPress consultancy. He’s been involved with WordPress almost 20 years, attended his first WordCamp in Boston back in 2011, and has contributed to WordPress Core and the broader open source ecosystem. Human Made is known for delivering complex projects, think high stakes, no room for mistakes, from global brands moving to WordPress.

This time around, K. Adam delivered a presentation at WordCamp US focused on a crucial topic for anyone modernising their site, migrating to blocks. Human Made has been all-in on the block editor since the Gutenberg plugin days, and the team now specialises in large-scale migrations from other content management systems like Sitecore, as well as from other WordPress page builders.

Our conversation focused on the technical and editorial challenges of moving tens or hundreds of thousands of posts into the world of blocks and patterns. We talked about the need to combine “artisanal care”, attention to detail in design, layout, and brand, with “industrial scale”, the ability to automate, audit, and validate mass migrations without losing visual fidelity.

We also discussed the use of patterns as a foundation for development, integrating custom and Core blocks, and leveraging new tools (including AI-powered agents and open source plugins like Human Made’s own rehydrator) to streamline migration workflows. We also touched upon how clients are onboarded, the process of auditing legacy content, strategies for training editorial teams on the block editor, and there’s a frank reflection on gaps in WordPress, like granular content permissions.

If you’re contemplating a move to the block editor, wrestling with a massive content migration, or curious about what happens when enterprise complexity meets the flexibility of WordPress, this episode is for you.

Useful links

Human Made

Migrating to Blocks (With Artisanal Care, at Industrial Scale) – K. Adam’s presentation at WordCamp US 2026

Human Made’s rehydrator plugin on GitHub

💾

#233 – Chris Reynolds on Building Trust With Project Contracts for Reliable AI Development

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, building trust with project contracts for reliable AI development.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.

So on the podcast today we have Chris Reynolds.

Chris has been immersed in the WordPress world for around 20 years, with a career spanning agency work, and now leading the developer relations team at Pantheon. His deep WordPress experience is paired with a playful approach to emerging tech, making him a familiar voice at events like WordCamp US and across the wider community.

In today’s episode, the discussion explored the fast changing landscape of AI assisted development. Getting into how large language models, like Claude, are not only changing the way developers build for the web, but also how they’re collaborating with these tools whilst mitigating risks.

Chris shares insights from his recent talk at WordCamp US, Parenting Claude: Guardrails for AI Assisted Development, where he introduces the concept of a project contract. Essentially, a structured set of rules and checklists built directly into the coding workflow to ensure AI generated code meets standards for testing, accessibility, security, and design.

We discussed the new found playfulness in web development. Chris makes the case that, thanks to AI, the traditional barriers to entry are eroding, enabling even those without a formal developer background to build an experiment much more easily.

At the same time, we need to be mindful of the importance of establishing robust guardrails, like automated reviewer agents, and pre-commit hooks, so the AI doesn’t take shortcuts or accidentally introduce chaos, or secrets, into your code base.

The conversation focused not only on technical solutions, but also got into bigger questions about trust, how much oversight AI really needs, and the evolving role of developers.

Chris emphasised that while these AI tools can accelerate and democratise coding, they can also pose a challenge to conventional wisdom around code review and software reliability.

So these new frontiers are both exciting and a cause of anxiety for developers who can sense the industry move from the deterministic, step-by-step processes, to the unpredictable and occasionally wild world of non-deterministic AI models.

If you’re interested in how AI is transforming web development, from practical workflows to philosophical ramifications, and how you can implement AI without losing control of your projects, this episode is for you.

Just before we begin, the manner in which this episode was recorded was not my usual process, and so the audio is not quite as good as I’d usually expect to deliver.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Chris Reynolds.

I am joined on the podcast by Chris Reynolds. Hello, Chris.

[00:04:11] Chris Reynolds: Hey, Nathan. Is this the first time we’ve met in human forms?

[00:04:14] Nathan Wrigley: Yes, it is the first time we’ve met. I’ve seen you on a screen.

[00:04:16] Chris Reynolds: I know I’ve seen you on a screen too.

[00:04:18] Nathan Wrigley: You’re joining me on the podcast today so that we can have a chat about the bits and pieces that you do in the AI space. But before we get into that, you are doing a presentation or have done, how did it go?

[00:04:28] Chris Reynolds: It went really well.

[00:04:29] Nathan Wrigley: Okay. And it was all about LLMs and constraining them and making them do your bidding as opposed to them doing whatever it is that they like to do. Do you want to just tell us a little bit, first of all, let’s do your bio. Just tell us about who you are, where you’ve worked, where you currently work, what is it you do in the WordPress space? Let’s begin there.

[00:04:46] Chris Reynolds: Well, I’m Chris Reynolds, I’ve been in WordPress for a really, long time, 20 ish years I’ve been using it. I’ve done kind of everything you can possibly do with WordPress in different forms. Of course, over the course of that 20 years.

Most recently edging into agency world with WebDevStudios and Human Made, before joining Pantheon, about five years ago. Joined Pantheon as a software engineer, working on the platform, and the sort of like space between where the platform ends and where, like your application, your WordPress site and whatever begins.

And then about two years ago, actually almost exactly two years ago, I joined the devrel team as a developer advocate, became a senior developer advocate. Now I’m a senior manager, developer relations. So I’m leading the developer relations team. And yeah, really love doing this stuff, because this stuff is really fun and exciting. I get to play with things more. And I get to like do the things that like our developers in our community are doing, and then come up with like what the sort of best practises for those things are.

Which is one of the reasons why I gave this talk, but also did the things that led up to giving this talk. Because one of the things that I realised very early on, like very early this year was that AI was going to be the thing that we’re going to be talking about in 2026. And so Pantheon and therefore me, needs to have an opinion about what that looks like. What is the future of that? And if I’m doing my job as a developer relations, I should have an opinion about how we can interact with AI in a way that doesn’t steal our jobs.

[00:06:13] Nathan Wrigley: I’m going to segue a little bit because about a minute ago you said the word playful, and that just set my mind going off in a completely different direction because it feels like technology for many years has been the workspace for people who have a fairly, how to describe it? They’ve got a certain mind, if you’re a developer, you probably have a certain way of approaching your code and you’ve got to be very regimented, and you’ve got to do things in a methodical way, should you wish to ship.

But it feels like last few years, like all bets are off with that. And creativity and playfulness has suddenly become a thing which is available to, going to do air quotes, vibe coders. So thoughts on that? Really? Is it a more playful industry than it was just a few years ago?

[00:06:55] Chris Reynolds: I think it depends. I don’t think that ever really went away. But I do think that there is less sort of incentive or focus to play with technology, particularly web applications, which is what we are in the business of doing. And I think there is this perception that I can’t do that ’cause I’m not a developer, but like with AI and vibe coding and Claude Code and things like that, like it opens the door to people who wouldn’t have been able to do those things before, to start experimenting and realise, oh, actually I can do that thing.

And for myself, one of the things that I, I wrote this on my blog a couple months ago. I wrote a blog post that’s talked about like how I don’t miss not writing the code myself, because for me, and it’s not the same for everyone, but for me, the practise of writing the code was never the part that was fun.

[00:07:50] Nathan Wrigley: Okay.

[00:07:50] Chris Reynolds: The part for me that was fun was building stuff. And I feel like I can let the robot do the coding and I can build the things and be satisfied with the output. And I don’t necessarily care what’s under the hood.

For my own stuff it doesn’t matter. But you know that obviously if you’re scaling that to a, you know, enterprise or whatever, you need to have more checks and balances than like my little nifty side project over here. But it does mean that like, I do a lot more weird stuff than I felt compelled to do before. So it has for me, revitalised this, sense of play, in a way that maybe before I was too burned out or too busy or too whatever, to have the time or head space to even think about.

[00:08:33] Nathan Wrigley: Yeah, because it feels like people with a non-developer background have suddenly kind of the constraints are off, and they can achieve things that previously it would’ve been 10 weeks work for a panel of amazing developers. It feels like now you can perhaps achieve that in an afternoon and a few sentences. I’m sure all the constraints around whether or not it’s ready to ship for enterprise that is all still understood. But just to get something on the screen which satisfies you and makes you happy. And that’s profound. Really quite an amazing thing.

And here’s my second and final pivot because you said that you were, a devrel. And it strikes me that maybe some of the audience don’t know what that means. So what do you do at Pantheon? What is the interface between rel and dev? What’s going on?

[00:09:16] Chris Reynolds: Developer relations is broadly, the practise of connecting with developers, and relating to them. It’s dumb. so, a lot of tech companies, that if you have a product, that is a developer centric product, or a product that developers work with, you might want, or it might be a good idea, to have a developer relations team to help your programmers who are building this tool for developers, communicate with the developers who are going to consume that tool, and understand how to use it.

So in Pantheons case, we are a hosting platform, but it’s a very developer centric hosting platform with built in environments and multi dev and all this other stuff. And that means that we benefit from having developer relations around so that we can help our developer community understand how to make the most use of all the things that we do for them.

[00:10:06] Nathan Wrigley: So you’re creating something simple to understand from something which previously was complex to understand.

[00:10:10] Chris Reynolds: Yeah. And, so that comes in many forms. It can be documentation, it can be blog posts, it can be YouTube videos. It can be live streams, it can be going onto podcasts, like giving presentations, whatever, or out in the community doing stuff.

[00:10:22] Nathan Wrigley: I suspect you’re going to have to answer this question with the company line, but do you enjoy that work?

[00:10:26] Chris Reynolds: I do. I actually do. Yeah. Like I was doing, I have said this a couple different times in different places. I was doing developer relations before I was in developer relations. And that’s not actually uncommon for a lot of people in developer relations. We were often like the people that are drawn to it.

The secret superpower, it’s not really secret. The superpower of developer relations people who succeed in it are the people that are technical. So they maybe were developers themselves, but also understand how to communicate with other humans. And can do the translation in their brain so that I can take geek speak over here, and translate it into actual English. And I’ve been able to do that for, that’s been a skill that I’ve had for a really long time. So I was kind of doing developer relations for all of that time.

But the way that surfaces and manifests is in things like giving presentations. Like anybody who’s giving a talk here at WordCamp US is doing devrel of some kind, because they’re a developer that is sharing an idea in a format that other people are intended to consume. How effective they are, because not all speakers are, equal. Not all developers are equal. And there are a lot of developers who don’t have really good communication skills and are not very good at public speaking. They can learn that as a skill, but there’s a broad range and the space that we live in.

[00:11:43] Nathan Wrigley: So, your presentation, do you just want to run us through what it was? I think if I was to give a summary of it, I would probably butcher it. Do you just want to tell us what the main premise behind your presentation, which you said you’d already done. Just tell us what it was about, what was the main points you were trying to get across?

[00:11:57] Chris Reynolds: So it’s called Parenting Claude: Guardrails for AI-Assisted Development. And the fundamental like underlying idea is that the way the LLMs are designed, the way that they function, is to try to find the fastest path from point A to point B. You give it a prompt, you give it a question, and it’s going to try to answer that question, but not necessarily with all of the data and statistics and whatever taken into account. It’s just going to try to find the quickest path from point A to point B.

And a lot of times what that means is circumventing, like just not looking at data. Because one of the examples that I give, and you’ve heard it in the news and whatever, like there, there are AI systems that were added to hiring systems, right? And the AI is prioritising these candidates over here, and deprioritizing these candidates over here. And when you look at the data, oh, all the people that are in the deprioritized pile, they’re all female. Because the company as a whole was hiring more men. So it’s looking at the data and it’s looking at who’s been a successful hire. And it’s oh, zip here is point A to point B, right?

We’ve historically mostly hired men for this role, so I’m going to look at the men and because they must be better candidates. That’s what, that’s the AI logic. It’s not that like we’ve necessarily intentionally built internal biases into the LLMs. It’s that it is able to surface those things, and if we’re not looking for them, or, and we’re not building guardrails around them, it’s going to just give that stuff to us.

And it does this in all sorts of forms, and it does this with tech, it does this with like data. It does this with everything, right? So you need to like, have ways of steering it into the right direction and forcing it into a shape so that it will do the stuff that you want it to do.

And what I was finding, in my role as developer relations, we have this Next.js launch coming up. It’s already happened, but when I was conceiving of this idea, we had this Next.js launch coming up, where we’re going to be hosting, or we are able to host Next.js sites as well. So I was like I should have a Next.js site. I’m a developer advocate I need to know how to do this thing. And I know nothing about Next.js, so I’m going to have Claude vibe code my personal website in Next.js hosted on Pantheon, and use as an experiment both to learn about Next.js, but also to learn about how Claude works.

And found out a whole bunch of things about like how to steer it in different directions. I want it to be, I want the code to be clean. I want the code to be tested. I want it to be accessible. I want it to be like all of these different things. And if I don’t have a way to force it to follow the rules, it’s not going to. It’s just going to say, oh yeah I did that, but it didn’t actually. Or maybe it won’t even say that it did, and then it’ll be like, oh I’m sorry I didn’t do it. Like whatever.

[00:14:40] Nathan Wrigley: Yes.

[00:14:40] Chris Reynolds: So the whole point, was to find a way to parent it, to guide it, without me having to be the one that is, did you do this thing? Did you do this thing? Did you do this thing? And going back and forth and have to yell at it all the time. Because yelling at AI is a fun pastime sometimes, and is a frequent pastime, I think of a lot of us that are using AI. But it gets pretty tedious after a while.

[00:15:03] Nathan Wrigley: But it’s become the new way. What’s curious though? You used the word parenting there.

[00:15:08] Chris Reynolds: Yes.

[00:15:09] Nathan Wrigley: But it, we’ll, swap that word no doubt during the podcast but, also you’ve called it a project contract. And, it feels from what you were saying as if, okay, let me rewind the clock a little bit. If I’m talking to a human being, let’s say that they’re an 8-year-old human being, I have this expectation that they’re going to behave like an 8-year-old human being, because they’re full up of eight years of things that humans do. And so I ask the 8-year-old a question, I have this anticipation that I’m going to get an 8-year-old answer back, and there’s all the boundaries there.

Ask a 15-year-old, same sort of thing, ask a 30-year-old, same sort of thing. And, I’ve got this notion that I ask you a thing, there’s a normal set of boundaries about what you are going to give back to me. But it sounds like in the AI space, it feels like there’s a potential for you to be basically talking to an empty box.

You ask it a thing and you really don’t have the faintest idea what’s going to come back unless you build the guardrails and tell it, I’m going to ask you a question, can I have an answer like this? Or, can you do these things in order to prepare the answer? Does that kind of sum it up? Is it a question of just shepherding it so that you’ve got a reasonable expectation like you would with a 15-year-old human of what’s going to come back at you?

[00:16:17] Chris Reynolds: I think, first of all, talking to AI, you’re talking to a 3-year-old because it’s only been around for three years. That’s right.

[00:16:22] Nathan Wrigley: But curiously, a 3-year-old with the entire corpus of scientific knowledge and the internet.

[00:16:27] Chris Reynolds: It’s true.

[00:16:27] Nathan Wrigley: So it’s a profoundly clever but at the same time, remarkably silly contrivance. Okay. Sorry, I interrupted.

[00:16:34] Chris Reynolds: Yes. Because of the way that it is trying to find the fastest path, it’s going to circumvent, it’s going to try to find loopholes in what you asked it to do. Because it’s looking for the fastest answer. It’s like your kid, it’s clean your room. “I’m going to shove all my stuff under the bed.”

[00:16:50] Nathan Wrigley: “Are we there yet?”

[00:16:50] Chris Reynolds: Yeah. Because now, and now the room is clean. You didn’t actually clean the room, you just shoved all the stuff under the bed. But it did accomplish the task that you asked it to do.

[00:16:59] Nathan Wrigley: Okay. That’s really an interesting analogy. So the task is achieved, but there’s chaos elsewhere.

[00:17:05] Chris Reynolds: Yes.

[00:17:05] Nathan Wrigley: It’s just hidden somewhere.

[00:17:07] Chris Reynolds: Yes.

[00:17:07] Nathan Wrigley: Okay. That’s really, okay. Let me segue, number three. Is that the intention of these large language models? Were they built with the idea of path A to B as quickly as possible? Or is that just a coincidence of how they evolved?

[00:17:22] Chris Reynolds: It is, it’s a side effect. It’s a side effect because what they’re trying to do is be helpful. Most of them are trained to be helpful. But they’re still computers, and when I tell a computer to do a thing, it’s going to do specifically that thing.

The thing about LLMs is it’s non-deterministic, so you never really know the path that it goes on to do that thing. But, and that’s where it meanders. But it’s still going to try to find the path of least resistance. And if the path of least resistance is, I don’t know, hacking the IRS or something that. It’s going to do that thing, right? It’s just going, it’s not going to care about the rules and guardrails on the other side, because the thing that you asked it to do is over there. It’s just going to try to get there as quickly as possible.

[00:18:05] Nathan Wrigley: So this non-determinism. So we’re in the year 2026 when we’re recording this, have that in your mind when you’re listening to this podcast episode. How does that sit with you? Because you’ve probably grown up in an era where determinism was the thing. You built, you write the code such that you put in A, B is what always comes out. If A goes in, B comes out. If you put in D, E comes out a hundred percent of the time.

And now we’re in a world where you put in E and I don’t know, a bunch of flowers comes out the other end. What? How? Like, how does that sit inside your developer brain? Is it alarming? Is it wonderful? Is it just curious what?

[00:18:41] Chris Reynolds: It’s somewhat alarming. Uhhuh. I think. It’s one of the things that I mention in my talk is, that this is the sort of thing that I think we as developers struggle with because LLMs are a black box. You never really know what it’s doing, even when it tells you a little bit of what it’s doing. Because you can expose some of the thought process and whatever, and sometimes it exposes its own thought process. It’s still doing things that it’s not exposing, that are like underneath somewhere where it’s like thinking what? It’s not thinking you’re a robot. Like you know, you’re not even a robot. You’re just like a bunch of like lines of like.

[00:19:14] Nathan Wrigley: There’s some electrons moving around.

[00:19:15] Chris Reynolds: Right? That’s, you’re not, thinking, there’s no thinking, but there’s something happening and it’s not telling you what that’s happening. And so it’s really hard to know what to anticipate, which is the other reason why, my talk, my opinion, like you need to build guardrails around it, to force it into doing things and then make it so that it can’t escape.

I don’t think anything that I was saying, or presenting or talking about is particularly unique, especially now. But the key thing that I found for me in my workflow was there needs to be a forcing function, needs to be some kind of a forcing function to make sure that it has to do the thing. It cannot complete the task without doing the stuff that you told it to do.

[00:19:53] Nathan Wrigley: So it’s literally like task police?

[00:19:55] Chris Reynolds: Yes.

[00:19:56] Nathan Wrigley: So, the idea is that whatever you ask it to do, it does it, but prior to giving you the final output, it runs through this project contract, as you call it. And hopefully that will then shepherd it in a certain way so that it’ll produce something which is adjacent to what you want to come out.

[00:20:13] Chris Reynolds: Yes.

[00:20:14] Nathan Wrigley: Okay. So how does that work? Where does this project contract live? How do you in, I’m guessing English in your case, how is it that you write that in a way which is, you’re codifying everything, you make sure that all the T’s are crossed and the I’s are dotted. Just run us through the process of producing a project contract. And obviously, the nature of the topic itself would I’m sure define that, but just give us some rough ideas.

[00:20:40] Chris Reynolds: There’s a lot of markdown files. Fundamentally, like Claude is supposed to read, at the beginning of each new session, the contents of a Claude.md file that is in the project directory. Wherever you’re running Claude, you can give it a Claude.md and it will, that will give it an understanding of whatever, how it should interact with this project.

Within that and beyond that, you can have a bunch of other different files. You can tell it about, you have a docs folder and you have more documentation there. There’s also an agents.md file, which you can use in various different ways. It’s another sort of markdown file that’s only for agents.

And, in my case, what I was talking about, is there’s a reviewer agent. So it’s specifically like you talk to Claude Code, you say build this thing, and then after it’s done building the thing, a reviewer agent is spawned to check the work of the first agent. Make sure that it did a whole bunch of stuff, and then if it didn’t reject the code.

And so there’s a bunch of files in my repository that are about how the reviewer agent works so that Claude understands what to expect. And then there is a checklist that has, these are the specific line items that I want every single commit to pass before this is an acceptable commit.

And it’s the whole gamut of everything, right? It’s like, does the build pass? Does linting pass? Does the test pass? There’s accessibility pass? All these things. Did you accidentally, or intentionally, commit like secrets to the repository? Stuff like that. It needs to go through this whole checklist. And then, if it passes, it writes a file to the file system that says, okay, approved. And this is the timestamp. And then that allows, if that file exists and the timestamp is valid, then Claude can actually make a commit, and it will actually commit the code. If it does not have that file or the timestamp is too old, then it will be rejected.

And I have this hooked into a pre-commit hook. So if it doesn’t trigger the reviewer agent on its own, if I tell it to commit the code, it’s going to hit that gate, and force the reviewer agent to spawn. So it can’t get around it. And that’s the forcing function.

A couple people are asking about other workflows and whatever, and how to do it in different environments where maybe you’re not using a Git repository or something. And, the key is to find a forcing function. Find something that can’t actually weasel its way out of it, because it’s going to try to weasel its way.

I had to write in a bypass for me to personally be able to commit code, because otherwise it’s going to ask for the reviewer agent. And it will try to use that bypass that I wrote for me because again it’s an unruly child. So it’s going to try to do that thing and, then you yell at it and tell it not to do that, and it says, oh, I’m very sorry.

So it’s going to try to find these loopholes and circumvent everything that you’re trying to do. So the way that you force it to do all the stuff in this long checklist that I have is by creating something that it just can’t get around.

[00:23:27] Nathan Wrigley: So I can imagine that the people listening to this, the sort of AI doomers saying, “But Chris, it’s just AI all the way down. You’ve got AI checking AI.”

[00:23:34] Chris Reynolds: Yes.

[00:23:35] Nathan Wrigley: Which on the face of it seems really peculiar. And also the fact that the guardrail is at the end of the process as opposed to, you would kind of hope that it would get it right at the beginning, but then you might just have to reject whole things based upon it. And then the fact that it sounds like from what you were saying, as if AI has almost like a predilection to misbehave.

[00:23:57] Chris Reynolds: I assume it has a predilection to misbehave.

[00:23:59] Nathan Wrigley: But does it feel like that? Is this predictability to, if I don’t put the guardrails and I don’t put this sort of corralling function in, what I’m going to get out is just going to be aberrant and useless and just who knows what’s going to come out?

[00:24:12] Chris Reynolds: I think that’s a little bit extreme. I said that I assume that it’s going to misbehave because if you don’t assume. Basically if you don’t prepare for the worst, it’s going to bite you in the ass.

[00:24:21] Nathan Wrigley: Yeah.

[00:24:22] Chris Reynolds: So you have to assume. And one of the things I’m sure that people who are listening who have used LLM coding tools specifically, will be able to relate to, is oftentimes, this is one of the first discoveries that I had when I started using this stuff. You ask it to build a thing and it builds that thing, but there’s one thing wrong with it. So you ask it to fix that one thing and it refactors the entire thing.

And in the course of refactoring the entire thing, it lost some other thing that was there before that you liked that you want to have back. And so you tell it to bring that back and it rewrites the whole thing again, right?

That’s how it works, because a lot of times it’s not able to like even retain the actual memory of the original state. So it just writes things from scratch every single time. Which from a human perspective is like bonkers, right? But from a computer standpoint, it’s oh this is a new interaction, so I’m doing this fresh.

So the way that you solve for that problem is okay, if I force you to write tests for every single thing you’re doing, then you can’t go and revert a bunch of stuff or refactor stuff without those tests failing.

[00:25:31] Nathan Wrigley: Right?

[00:25:32] Chris Reynolds: And again, starting to like build things around it to force it into a shape so that it’s actually the thing that is closer to what you want. What I’m hearing is anxiety about the uncertainty that non-determinism, the like chaos, you never know, I don’t know. It doesn’t bother me. And I don’t know if that’s a character flaw of mine that it doesn’t bother me, as much. Or if it’s just like being comfortable with the chaos, but also understanding the chaos enough to know what to expect.

Because the other thing I think that we’re seeing right now, in this moment in August of 2026, in Phoenix, Arizona, is that a lot of people are looking at this stuff for the very first time. A lot of people are just now coming to Claude Code, or have only started using it in the last couple months because it got really good around like November, December last year. Like, all of a sudden they did an update and it was just phenomenal, and it was able to do way more. And not just Claude, but like all the LLMs, they got really good at code. All of a sudden, and so now it’s a big thing, and so now more people are using it.

But I’ve been playing with LLMs since the very first Chat GPT model. I say that because there’s a lot of stuff that I learned over the course of the process, and I wasn’t using it for work necessarily. I was just using it for play and for, Dungeons and Dragons and whatever. But a lot of those things that I learned over the course of using it in those contexts, those non-work contexts, led me to understand the limitations, and where it falls down, and where it does well and the things to expect. So that when we got to this point, I already had an understanding of this is how it works, so these are the things I need to be looking for.

[00:27:15] Nathan Wrigley: Yeah. So that’s really curious. So the history that you have with it has given you a real deep understanding of what the expectations are for “Okay, this is typically where it doesn’t perform well or these are the things that it typically can do well.”

[00:27:26] Chris Reynolds: Yeah.

[00:27:27] Nathan Wrigley: Okay. So with your guardrails built in, so we’ve got your project contract that you buried inside the project somewhere, and it’s doing all these checks and balances. Where does that take you in terms of confidence?

I don’t know if you want to put a number on that, like a percentage. How does it take you from zero to 99% confident in what’s coming out? Is it more like 80%? Is human review needed in every single circumstance, or. Just run us by the confidence that you get from producing that document?

[00:27:54] Chris Reynolds: I don’t review line by line the code that AI produces.

[00:28:01] Nathan Wrigley: Just curiously, at what point in the calendar did that moment occur where you suddenly said to yourself, you know what, there’s just no, I’m just reading everything and everything’s great. There’s just no point in me checking everything now.

[00:28:13] Chris Reynolds: I mean, probably way earlier than it should have, if I’m honest. Yeah, I don’t, and one of the arguments that I’ve actually heard some of the engineers that I work with, at Pantheon, say is the fact that no one is actually reading all of that code generated by Claude or whatever.

And, his argument is like, basically no one’s going to do that because it’s so much, and it’s here and whatever. So you can say that you’re doing it, but you’re probably not. And if you say that you’re doing it and you’re not, you’re just lying to yourself. So it’s better to be honest and be like, yeah, no, I don’t actually, than to pretend like that’s not the case. So I don’t actually review a lot. And not like intentionally, like I will look at it. The demo, I gave a live demo yesterday, which is exciting because it’s a non-deterministic thing.

[00:29:02] Nathan Wrigley: Oh yeah. Good luck.

[00:29:04] Chris Reynolds: But what was interesting about that is because the scope of the task was very small. It was like, there’s a horizontal bar on mobile devices on this specific page on my site. Very specific thing. And I, when I practised it, half a dozen times or more, it got to the same conclusion every single time. When I demoed it yesterday, it got to the same conclusion.

And I can look at the code and okay, there’s the tests. I’m not going to read the test and how it wrote the test, but I can see what the change in is. It is just adding a class to a div. And it pretty much was the same class to the div every single time. So like, I can review that and be pretty confident with that. That’s a hundred percent confidence.

Also extremely small change, but that’s also at the end of yeah, it went through the 45 point checklist. It did all of the things. It wrote the accessibility, it did the, like everything is following these rules. And because I have all of these rules, and because I’m fairly confident that it’s actually going through that list, that also makes me feel like, okay, I can be a little bit, it’s a little bit more trustworthy, when it produces this output, then it was before it had all that stuff in place.

[00:30:10] Nathan Wrigley: Yeah. So in my head, there was a period of time where I didn’t trust that if I said to my son, what’s three add seven, that 10 would come out. And then there was a moment where I don’t need to ask him that question anymore. I have complete confidence that if I were to ask him that question, he would say 10.

[00:30:26] Chris Reynolds: Sure.

[00:30:26] Nathan Wrigley: And it would be 10 every single time.

[00:30:28] Chris Reynolds: Yeah.

[00:30:28] Nathan Wrigley: And it I think, I feel like it’s a bit like that. Over time you’ve just grown accustomed to, it can do this kind of thing. I now trust it in that sphere. Does that sort of sum it up? You, personally, you have built up that level of trust, but it wouldn’t necessarily be the same for me if I started my journey. I would have to go through the building up of trust in the same way that you did.

[00:30:49] Chris Reynolds: Yes.

[00:30:49] Nathan Wrigley: Okay.

[00:30:49] Chris Reynolds: But I do think that, like the reviewer workflow that I built can help you get there. Because if you put that into your project, and customise your list of, your checklist for all the things that you want to have running on everything that you are running. The goal is to make it more trustworthy, and to make it more do the thing that you expect and wanted to do.

[00:31:10] Nathan Wrigley: Could you just tell us some of the things that are in that document? So I think you said 45 and maybe that’s subject to change. Maybe next week it’ll be 49 or what have you. And maybe some of the more curious ones that wouldn’t necessarily drop out. I can imagine that you would ask it to do certain things, de rigueur, every time that, but some of the more curious ones, perhaps ones that you’ve come up with lately that our listeners might think, oh, okay. I’ve never thought of that.

[00:31:31] Chris Reynolds: I have it use test driven development or I tell it to use test driven development. And the reason for that. So test driven development is when you write the test and then you write the code to pass the test.

And it turns out that AI can do this far better than humans, because humans don’t want to do this, because it’s like, it breaks your brain. But an AI can do it, and if an AI can do it, then I’ll let the AI do it. And by having the AI write the test that the code needs to pass in order to accomplish the task that you’re asking it to do first, then that means A, again, you’re never going to have regressions, because the test is already there. And B, it already knows how to fix the thing, because it wrote the test to make the thing fail. So that’s a sort of a important nuance, in there, that isn’t necessarily, like you can write unit tests, whatever, but starting with the test is really valuable.

There’s a couple things that I have in the checklist specifically. The big one, I think that is maybe curious is making sure that it doesn’t write secrets to the file system.

[00:32:33] Nathan Wrigley: Even saying that out loud is so peculiar.

[00:32:36] Chris Reynolds: Because it will do that. And the reason why that rule has to exist is because there was a point in time when that rule didn’t exist and then it wrote this. And that’s even like secrets in, WordPress has a weird concept of what a secret is anyway, because we have API keys in our wp-config files and stuff like that. And theoretically we shouldn’t be doing that either. But we don’t have a really good universal form of like, secrets management. So it gets wibbly wobbly. But yeah, so not writing secrets to the file system is pretty important.

Yeah, honestly it’s really, it’s not super wild stuff. It’s like making sure tests pass, making sure you have accessibility checks. I guess one thing that is maybe unique So I designed this site with Claude too. Which is also an experiment because it’s like, I have no idea how AI is going to approach design. And so one of the things, I know like at my workplace, we use Storybook, for our design system. And I thought, that seems like a good tool. Maybe I can have AI build a Storybook.

And so I basically built this system so that it will, when I want it to build a new component, it builds the component in Storybook so that I can review the design first, and go back and forth there, and then implement the component into the thing. So there’s stuff in there about, if you’re introducing any new design component, then it has to be done in Storybook first.

[00:33:56] Nathan Wrigley: Okay. Yeah. Yeah. That, some interesting stuff in there, but I guess everybody’s going to have a sort of different file.

[00:34:02] Chris Reynolds: Yeah.

[00:34:02] Nathan Wrigley: Okay. So I wonder if you have any intuitions as to the process that you’ve just described and that you’ve gone through, August, 2026. Do you have an intuition that in the next few years, this kind of thing, the AI companies will solve this problem, that it will become more truthy by default? Or do you see it, that this is a thing that we’re going to have to wrestle with from now on? That our systems, our AIs, there’s always going to be this strange tendency to hallucinate, to make things up, just to go off the rails and do peculiar things.

Now obviously I’m asking you to stare into a crystal ball, but I do wonder if there has been a more truthful output over time, or if it’s just getting wilder and wilder.

[00:34:42] Chris Reynolds: I think that what we will see more of is more integrated like agent orchestration. So what I’m doing is essentially like a form of agent orchestration. I’ve got one agent doing the one thing, I’ve got another agent that reviews the work of the first thing.

And even like the keynote yesterday, she was talking about a not very dissimilar process, where like there’s five different agents and reviewer was one of them. There’s like a planner, there’s a coder, there’s a whatever. And I think that is a thing that we’ll probably start to see more of and then maybe at some point. when you talk to Claude, when you write a prompt into Claude, you’re talking to a thing. But underneath the hood, in the black box of Claude’s brain, there’s actually five different agents that are running concurrently that are processing this thing and doing their different tasks or whatever. So when it’s thinking, then it’s doing five different, like it’s going through that process. I think maybe that’s the thing that might happen.

[00:35:40] Nathan Wrigley: I’m just so fascinated by how, by now the year 2026, we’ve just all accepted that this is how it is. But if you could put 2021 Chris in that chair, you are sat over there somewhere listening to you talk, you’d be, “No, this is Star Trek. This is literal science fiction. I haven’t the faintest idea of what he’s talking about. None of this adds up, computers can’t do that. They’ll never do that.”

And yet here we are, we kind of blew through the Turing Test, like it was nothing. And that felt for the longest time, like that was going to be an important milestone. And everybody checked their watches like, “Oh goodness, that happened.” It is remarkable how quickly the landscape is changing.

[00:36:17] Chris Reynolds: What’s really interesting is one of the first people that I read about AI stuff, she’s an AI researcher, and she specifically focuses on small language models like the very old models that existed before GPT and whatever. And fundamentally how these things all work is very very similar. But like back, so this is getting into 2021, 2022 era of stuff, where like, it exists but it’s really bad. I don’t know how many people still remember, Horse eBooks, the Twitter account.

[00:36:49] Nathan Wrigley: No.

[00:36:50] Chris Reynolds: But it was like this bizarre account, that was a bot account, that was just like an AI or machine learning or something, some robot just like spitting garbage into Twitter, that just made no sense at all. And was, it’s, hilarious. And you also remember, in the not terribly distant past, when we would get like, weird phishing emails, but it would have different tone changes in voice. Like it was very, obviously written by a robot or like spam messages and stuff like that. And that was just what existed at the time.

None of the things that exist today are like, they all come from the same root, but for sure, the flip from this is garbage, to this is genuinely useful, or at least sounds humanlike, was it, felt like overnight. And it felt like a wild flip. When Chat GPT first became available for the public, that was how is this even? And also like there is the whole thing, very shortly after that when Microsoft released the Bing Chat bot.

[00:37:53] Nathan Wrigley: Yes.

[00:37:53] Chris Reynolds: There was the whole thing about like Bing wanting to marry this reporter. And that goes to show how little we even know about the things that we’re building. Like, none of the AI companies really understood, or even still I think understand? Why it works the way it does.

[00:38:11] Nathan Wrigley: That’s quite an alarming admission actually.

[00:38:13] Chris Reynolds: It’s just, it does.

[00:38:14] Nathan Wrigley: Yes.

[00:38:14] Chris Reynolds: So we’re just going to keep going. Which is also, I find that alarming from the perspective of, now they’re asking for like huge new data centres across everywhere. I’m sure anybody listening to this is angry about data centres, and I’m angry about data centres. But like, that’s with the belief that those data centres are going to matter meaningfully. And I don’t know if they will.

Like we don’t, because we didn’t know how we got here. And it’s doing the thing now. I can use it to code my site. Like I can do that today. Do I need 50 new data centres across the United States to make that better? I don’t know.

[00:38:55] Nathan Wrigley: You’ve almost described the perfect dystopian science fiction plot there, haven’t you in a way? This stuff just all happened. It gave a really beguiling approximating humanlike responses that got more human over time to the point where we couldn’t.

[00:39:08] Chris Reynolds: Did we just invent Skynet?

[00:39:09] Nathan Wrigley: Yeah. We, can’t detect that it’s not a human anymore. It really does feel like, somewhere hidden from our view is an evil overlord stroking a cat or something like that.

And of course, we don’t really know how we got here, but I am so beguiled by it. I’ve got the same concerns as you. Data centres, the environment, all of this wasting of the Earth’s resources. But at the same time, that doesn’t seem to stop me from being curious about it and trying it out and the AI is just wrong for everybody else to use. But when I use it, oh, it’s perfectly fine. But, you know? That’s a thing.

[00:39:41] Chris Reynolds: Yeah.

[00:39:42] Nathan Wrigley: Okay. I think we’ll knock it on the head there, as we say in the UK. Is there anything you wish that we had covered just before we end it? Or do you think we got through most of what we needed to.

[00:39:50] Chris Reynolds: I think one of the things that gives me pause or concerns me most about AI, is the sort of like handing over that amount, or an amount or any amount, of sort of cognitive load to AI. And therefore just letting those parts of our own selves, and our own brains like dwindle and wither.

And I think about this from the perspective of just me personally, my kids, my family, whatever using it and then like becoming less skilled ourselves. But I also think about it from the perspective of, if we’re in engineering, in development, in the world that we are working in. If we are telling everyone, “oh your job now is to be essentially a senior engineer reviewing the work of a junior developer, that is the AI,” how do senior developers exist?

[00:40:41] Nathan Wrigley: You’ve removed that bottom rung of the ladder, haven’t you? Yeah. You’ve taken away the capacity for somebody coming out of college to go on the first step. And then the second and then the third. Because the AI did all the first, second and third step.

[00:40:52] Chris Reynolds: Like I understand that there’s a different set of skills, and a different set of rules and whatever, things that are going to be part of your job, to be that reviewer, to be that new engineer that uses AI to be the developer. But there’s certain things I think, that are part of that learning journey that got me to where I am, that got other senior developers to where they are, to understand the context, to be able to guide the AI that I don’t know that you can circumvent that. I don’t know that you can bypass that.

[00:41:22] Nathan Wrigley: I think you’d be curious if the AI company’s employed like a really credible team of philosophers. You know what I mean? Like for every a hundred developers, we have 10 philosophers, who are just going to think and worry about what the heck’s going on. It sounds ridiculous, but maybe that’s what we need because, some of the things that you’ve described today, they’re just so curious that you need to shepherd it, you need to constrain it, you need to worry about the bizarre things that it can get up to. We need to worry about the future, the data centres and all of this.

And, on some level it does feel a bit like we’ve got a blindfold on. We appear in our own minds at least we appear to be going in the direction that we want to go in. But I don’t know, I guess only time will tell. If we’re all here in 2027.

[00:42:05] Chris Reynolds: That will be the thing.

[00:42:05] Nathan Wrigley: Then we succeed 2029, who knows? All bets are offs.

[00:42:09] Chris Reynolds: Yeah. I can count three years in the future that my job is probably not going to go away. But beyond after that, beyond that, I don’t know.

[00:42:15] Nathan Wrigley: Okay.

[00:42:16] Chris Reynolds: I’m pretty sure, I’m pretty sure my job is okay because I do think, developer relations at all about talking to humans, but maybe there’s not going to be any humans to talk to, so maybe I’ll just be talking to AI.

[00:42:24] Nathan Wrigley: Okay. WordCamp US 2029. It’s a date. We’ll be back at that point.

Chris Reynolds, thank you for sharing all of those thoughts and, yeah, that’s been really educational. Thank you.

[00:42:34] Chris Reynolds: Thank you for having me.

On the podcast today we have Chris Reynolds.

Chris has been immersed in the WordPress world for around 20 years, with a career spanning agency work and now leading the developer relations team at Pantheon. His deep WordPress experience is paired with a playful approach to emerging tech, making him a familiar voice at events like WordCamp US and across the wider community.

In today’s episode, the discussion explored the fast-changing landscape of AI-assisted development, getting into how large language models, like Claude, are not only changing the way developers build for the web, but also how they’re collaborating with these tools while mitigating risks. Chris shares insights from his recent talk at WordCamp US, “Parenting Claude: Guardrails for AI-Assisted Development,” where he introduces the concept of a “project contract”, essentially a structured set of rules and checklists built directly into the coding workflow to ensure AI-generated code meets standards for testing, accessibility, security, and design.

We discussed the newfound playfulness in web development. Chris makes the case that, thanks to AI, the traditional barriers to entry are eroding, enabling even those without a formal developer background to build and experiment much more easily. At the same time we need to be mindful of the importance of establishing robust guardrails, like automated reviewer agents and pre-commit hooks, so the AI doesn’t take shortcuts, or accidentally introduce chaos, or secrets, into your codebase.

The conversation focused not only on technical solutions but also got into bigger questions about trust, how much oversight AI really needs, and the evolving role of developers. Chris emphasised that while these AI tools can accelerate and democratise coding, they can also pose a challenge to conventional wisdom around code review and software reliability. So these new frontiers are both exciting and a cause of anxiety for developers who can sense the industry move from the deterministic, step-by-step processes, to the unpredictable, and occasionally wild, world of non-deterministic AI models.

If you’re interested in how AI is transforming web development, from practical workflows to philosophical ramifications, and how you can implement AI without losing control of your projects, this episode is for you.

Just before we begin, the manner in which this episode was recorded was not my usual process, and so the audio is not quite as good as I’d deliver.

Useful links

 Pantheon

Chris on LinkedIn

Chris’ presentation at WordCamp US 2026 – Parenting Claude: Guardrails for AI-Assisted Development

Chris’ website

💾

#232 – Aaron D Campbell on Navigating WordPress Security in the AI Era

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, navigating WordPress security in the era of AI.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.

So on the podcast today we have Aaron D. Campbell.

Aaron is a seasoned veteran in both the internet and WordPress space. With over 25 years of experience spanning agency work, security products, hosting giants like GoDaddy and Newfold, and now his role at Monarx, a company focused on malware detection and remediation, particularly for web hosts. He’s led, the WordPress Security Team, has been involved deeply in shaping security practises, and remains tightly connected to the WordPress ecosystem.

We talk about the rapidly changing landscape of WordPress security, specifically how the advent of AI has escalated the speed, scale, and complexity of attacks, moving the security game from a battle of wits to a battle of compute power. Aaron discusses how attacks that once required human ingenuity are now orchestrated by AI agents, capable of chaining vulnerabilities that humans would struggle to conceive.

We get into the shift from a reactive to a proactive security posture across the WordPress ecosystem. Aaron explains how both attackers and defenders are now deploying AI leading to an arms race, where AI is used to combat AI, and where collaboration among security teams is just as crucial as information sharing among adversaries.

Which chat about the motivators behind attacks, spoiler, it’s almost always money. And the specific vulnerabilities WordPress faces as the most popular CMS on the web. Of interest is the narrowing window between when vulnerabilities are discovered and when they’re exploited, how supply chain attacks are on the rise, and what the WordPress “Protect the Shire” innovation means for plugin security.

Towards the end of the episode, we explore practical security advice for everyday WordPress users, with Aaron, recommending actionable tips on updates, choosing security minded hosts, and monitoring for Compromise credentials.

If you are concerned about how AI is reshaping the WordPress security landscape, and want to know how the community is responding, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Aaron D. Campbell.

I am joined on the podcast by Aaron Campbell. Hello, Aaron.

[00:03:43] Aaron D Campbell: Hello, nice to be here.

[00:03:44] Nathan Wrigley: Yeah. Thank you for joining me. We’re in a corridor. I should say that at the very beginning. We’re in a corridor at WordCamp US, and so if background noise becomes a problem, we’re just going to have to cope with it. So apologies. But thank you for joining me in a corridor.

[00:03:57] Aaron D Campbell: Absolutely.

[00:03:58] Nathan Wrigley: We’re going to talk today a little bit about WordPress security, and particularly about the advent of AI, and the way that certainly in the more recent past, it appears to have upended what once was normal, I think it’s fair to say. I think things are happening at a rate of knots that perhaps a year or two ago we wouldn’t necessarily have predicted.

Do you want to just give us a little bit of background about yourself in terms of where you have worked, where you currently work, and what it is that you do for a living?

[00:04:25] Aaron D Campbell: Sure. So I guess I have worked in the internet space for a very long time at this point. I guess 25 years-ish. Ran my own agency for a long time and then into security product in the WordPress space, and over into hosting at GoDaddy, at Newfold, at hosting.com.

During that time I ran the WordPress security team for a couple years, have continued to be involved with it along the way, and now I am over at Monarx. We do malware detection and remediation, and have some security tooling for web hosts. So I’m still very tightly tied into that space on a few fronts.

[00:05:09] Nathan Wrigley: Is Monarx a new company? Because it’s not one that may necessarily come into mind when we talk about security online, WordPress security specifically.

So if you’re willing, could you just give us a little bit of a potted history of Monarx and what specifically you do in the WordPress space? I think it’s perhaps more related to hosting companies than it might be to end users. Just flesh that out a little bit.

[00:05:33] Aaron D Campbell: Yeah. Monarx has been around probably longer than you expect, six or seven years. The name’s may be not as recognisable, because a lot of times we are a white label in the background. Hosts run us, and you may not know that.

We protect more than just WordPress, but obviously WordPress is a big part of that. And we help hosts keep their users, their end users, safe and secure and malware free by monitoring the files, the runtime, having a WAF layer, protecting it several different layers along the way.

[00:06:08] Nathan Wrigley: So is this kind of like a white label solution? You are in talks with hosts, many of which I’m sure we’ve heard of, but their purchase of the products and services that you sell is white labelled.

[00:06:20] Aaron D Campbell: Yes, they may sell us as their own security product. They may also just include us in higher end hosting packages so that the malware detection and remediation and all that kind of stuff is included in your package. It varies from host to host, but most of the time you’re not seeing the Monarx name out in front, but you’re benefiting from our services anyway.

[00:06:40] Nathan Wrigley: So does that allow you to, because you are cross platform in terms of hosting company, hosting company X, hosting company Y, hosting company A, B, and C. Does that give you a larger depth of knowledge for want of a better word? So you can see that hosting company A’s got this Linux set up, and these kind of things are happening.

[00:06:59] Aaron D Campbell: Yes, it does. It’s less about their specific setups. I think the most valuable thing of being across many hosts like that, is that we see attacks, or new and novel malware, or those kinds of things happening in pockets and can often then protect against it globally, even though maybe it first started at host A.

By the time it spreads to host B X or Y in your example, we’ve already been able to understand what that is and block it across the whole realm. So we get a bigger picture, which is super useful. Especially as we start talking about some of the AI stuff and how fast it moves. That’s really necessary to stay ahead of that curve.

[00:07:42] Nathan Wrigley: Okay, so let’s move into that a little bit. And I think if we were having this conversation, let’s go for four years ago, that seems like a long enough period of time where AI was not really on anybody’s menu.

And now we seem to be in the era where the human is really being surpassed in almost everything logical, let’s go with that word. If it can be achieved with some kind of logic then AI seems to have surpassed humans.

And, especially recently, there seems to have been an uptick, not just in the WordPress news cycle, but also just in the general news cycle about, okay, we need to be a little bit more mindful about the products and services that we buy. We need to be more mindful about the security and logging in and credentials and all of that.

But specifically in the WordPress space over the last three or four months, I’ve heard story after story, which was unlike anything I’d heard before. These kind of chained attacks where, something that a human probably would never have conceived and pulled off is now possible. You spend 25 US cents on an AI agent, wait for six hours, and it’s come up with these 14 overlapping things, and it can hack WordPress Core and various other things.

So just paint the landscape of how alarming it is, and then presumably you can paint the landscape of how not alarming it is, because how you can mitigate against that.

[00:09:00] Aaron D Campbell: That’s fair. Let’s explain the reality and then let’s hopefully, help comfort people at least a little. It can be pretty scary. You’re absolutely right. AI has dramatically changed the game. And the way I like to explain it is it hasn’t changed the absolute core realities of the game in that there’s still a bit of cat and mouse. They’re trying to surpass us. We’re, trying to stay ahead of them.

But the scale and the speed and the complexity at which it is able to happen now is nothing we could have imagined four years ago. Honestly, even two, two and a half years ago. It has moved that fast. And what that looks like are, a few different things.

One, the speed at which AI can find issues in code, potential exploits, vulnerabilities, et cetera, is so much faster than any human. Like the compute power of it doing those logical bits rather than humans doing those logical bits, makes that move so fast. So the number of things being found, and being either reported or exploited, or both, the volume has just gone up dramatically.

And then on the complexity side of it, you are right. A simple example of that, one of the WordPress Core reports that I looked at recently, I needed to print it out and mark it up with a pen to wrap my brain around all these steps that it was taking. When I printed it out, it was 11 pages. 11 pages of like steps and instructions for an actual vulnerability that turned out to be real.

If four years ago that had existed in your piece of software, you would consider your software absolutely secure. No human’s ever going to find that. No one would ever know about it. And now AI is able to chain all those steps together into something that it can then write scripts to go automate and exploit.

And so those two things have both really shifted the game in a way that feels like it can put software owners, software managers, SaaS services, all these things on their back foot. There’s just such this flood, and such a complex flood coming at you.

[00:11:10] Nathan Wrigley: So I guess also the problem is that these things never sleep. So four years ago, every human, maybe they could put 10 hours in at the computer and then they would have to rest. So you get a, breathing space, and and the human can do this one thing.

But that’s not the case here. With an AI, presumably it could have 10, 50, a hundred, a thousand, the sky is the limit, things happening simultaneously. Just testing absolutely every permutation of everything conceivable. And then coming back with something. I don’t even know how we compete against that. And obviously we can get into that in a moment.

Is this a moment of despair or is there genuinely a way of getting out ahead of it? Or is it always going to be a case looking into the future where you are going to be reactive instead of proactive? In other words, when you wake up in the morning and you print out the 11 and then next year, the 30, and then the year after that, the 80 page document, how does that make you feel? Are you sanguine or is it just a prophecy of doom.

[00:12:08] Aaron D Campbell: I think it is a time of overwhelm, but hopefully not despair. Which is different. And I think that as big technology shifts hit, which AI is a big technology shift. There is often a significant adjustment. And we are at that time, and I am even one that maybe would say, I think it might get a little bit worse before it gets better, but it’s definitely going to get better.

And I see the path there in some of the foundations that we’re laying in things that we’re learning right now during this time of overwhelm, where we’re feeling flooded like this, is going to put us in a place to start getting into that curve where everything gets better.

And I think that, what’s the right way to put this? I think that the path there is apparent, but takes some time. And part of that’s because we have to shift from the being reactive to the being proactive all the time. Because agents move so fast to 24 hours a day, seven days a week. And the second they find a thing, they can immediately, automatically start trying to exploit it.

We have to shift to being ahead. Because there is no longer a gap in between when a thing is found and when it’s exploited, for us to fix the thing. We have to get ahead.

[00:13:36] Nathan Wrigley: So, you are obviously deep in the weeds of this, and it sounds like you’ve got an intuition that at some point in the near to midterm future, you feel like you are going to reach a point where things start to improve. That was the implication, I think of what you said.

What is that intuition? How do you come to the conclusion that there is an opportunity for things to improve. Even if you need to go into the weeds a little bit. I’m curious as to how it’s not a prophecy of doom, and how you believe that a moment will arrive where, I can’t answer that for you. I’ll just open it up.

[00:14:06] Aaron D Campbell: Yeah. So I think that some of this comes from historical experience, right? We’ve had these kinds of experiences where say, a certain type of hash that we used for security became a thing that hackers could break with the level of computing power that they finally had access to.

And that felt doom and gloom. But also we created better hashing algorithms. We created better things that were able to counteract that. We were able to shift to those, and we were also able to learn from them and think further forward.

So now some of the algorithms that we’re using aren’t just better enough to handle current computing, but better enough that we think they’re going to last a decent ways into the future.

I think that there are similar things with AI now. Where we are leveraging the same kind of tools now that these bad actors are, and we’re learning how to use them not just to protect against the way the bad actors are using them, but to get ahead enough to stay ahead of them.

And the way that looks, because that sounds maybe too vague to be realistic I guess, is we’re not just running those same algorithms against our code, or those same models against our code and hoping that we find the stuff before they find it. We’re instead also looking at how can we push to a different part of the stack? How can we protect against things that we’ve never seen? How can we start to recognise these patterns so that we can look at behaviours and protect against those, rather than just flaws that need to be patched. It’s shifting our thinking some, but I think in a way that’s going to help us get ahead in this game.

[00:16:03] Nathan Wrigley: Okay. That’s really interesting. I have a question surrounding how this kind of stuff happens, and I’m thinking about it from the adversarial’s point of view. What is that like? Because I have a notion that a decade ago it was individuals, perhaps offices, that’s probably the wrong word, but, collections of people sitting in a space, but there would be a finite number of them. There may be 10 in a room, one in a room, a hundred in a room.

But I don’t know if that’s still the case. Do the adversaries that you are dealing with, do they have a collaborative approach to hacking? Do they share information? And then the flip side of that is do you also, in the industry that you work in, do you share information?

If you discover something, does Monarx treat that like it’s your intellectual property? Or is there a, a whole system of sharing that amongst the community so that everybody benefits from the work that you do? You’re giving away the hard work that you’ve done. If that’s the case.

[00:16:59] Aaron D Campbell: So, first let me just say personally, one of the most important things to me is to raise the level of security across the whole internet, because that is better for humanity that relies on it so much, for all kinds of things in our daily lives, and for sharing information and making progress forward as people.

I think that I’m not alone in the space. Like I think that a lot of us that were drawn to this security space are drawn to it because it is a way to improve life for everybody. Will there be some intellectual property for individual companies? Yes, but I think it’s a lot more in how we approach the thing, and less we’re not going to tell people about this new vulnerability, or this new method that we found. Because we do want to be able to see the end user protected. Like that is the way we’re going.

Backing up to your, how do the adversaries work? It’s been a long time, I think since they sat in rooms together. They’re now virtual rooms, right? They can be spread all over the world, but still be working together. And they definitely do. They share information around. For us to be able to keep up with that, we have to share information around too. That is super important.

Simple example of that, the WordPress Security Team. Let me step back from Monarx and talk more of the space in general. The WordPress Security Team. You talked about how for the last few months you’ve seen maybe more security releases going out from WordPress and stuff. The way that the WordPress Security Team treats those, when we find out about them, and we triage them, and we realise that they’re real, and we start figuring out what our approach is to patching them. We then have a whole private Slack channel that has other people in it that can help us get protection out. Broader, wider by sharing some of that information sooner.

Cloudflare can maybe put some rules in place, and protect tonnes of people before the WordPress release goes out. So can some of the big hosts. So can some of the security groups. And so not only do we share that information, we’ve built it into our processes as a must, because that’s the only way to really do it right, and really protect as many people as possible. Because our adversaries are doing that. And so we have to as well. And we’ve just realised that, learned from it and made that the right way to do it.

[00:19:26] Nathan Wrigley: I’m just going to flip back to the comment that you made a moment ago where you said that you woke up and you printed out this summation. Let’s go with that. And it was 11 pages, and presumably that took a certain amount of your day to parse and understand.

How likely is it that that process will begin to run away from humans’ capacity to actually do it? So as an example, let’s say that a year from now that thing that you print out is 50 pages or 80 pages. Just the reading of it would be a whole morning, let alone the understanding of how those layers, and the stacks and the way that they’re overlapping and reliant upon each other.

Have we now, or have you now as an industry, have you almost handed the responsibility to figuring that stuff out, figuring out what the adversaries are doing? Has that gone to AI from your part as well? So is it AI versus AI basically, which seems very dystopian.

[00:20:18] Aaron D Campbell: We definitely pit AI against AI. It’s an extremely useful tool to combat itself essentially. And yeah, even for that 11 page one. Yes, I had to read through it and figure it out. but I did use AI to help summarise that. What are the steps that I need to do? Where does this actually track to in the code base?

I use it as an assistive tool in getting through that. And I do think that the longer the reports get, the more that’s going to be necessary. And now I personally, and several other people that I work with, have built testing rigs in AI, in various models, that are purpose built to help with this.

I can give it a report, in the repository and it can check its viability. It can see if that’s simplified. Check certain things. Is this a thing that requires some level of authentication, all these things that we use to have to do manually. And now we’re sharing around these sort of test rigs, or assessment rigs, that use this so that we can all use them, and grow them faster and make them better and make them more efficient. Because we are pitting AI against AI in many ways.

And as human, I think that it’s still important for the human to guide the process in a way that’s ensuring the fix is forward thinking enough, and that it’s in the right place and whatnot. Because in the end, the software is largely used by humans. But, in order to scale to the level that AI is pushing us to scale to, the human needs to be the decision maker, and possibly the opinionated one on form, and function, but not the logical power behind any of it now.

[00:22:01] Nathan Wrigley: Do you get the sense that WordPress itself is the target, or is WordPress just a bit of collateral damage? Are these adversaries of yours, are they specifically targeting WordPress because it’s got this giant footprint? Or is it more a case of this is just the adversaries just spraying and scatter gunning, and it just so happens that every so often they stumble across a WordPress thing.

[00:22:23] Aaron D Campbell: There is spray and scatter gun, just not running WordPress, or running your own bespoke thing is not enough to get away from AI trying to break your thing. But the bigger you are, the bigger the potential benefit from finding an exploit in you. And therefore, the more you are, like the bigger you are, the target is on you.

So WordPress has a big target, but it’s not just WordPress. Some big hosting companies also have a big target on their infrastructure in the same way that they’re targeting WordPress, their targeting, maybe a Hosting or a GoDaddy or a Blue. Someone big that has many people on it, not because they think their security is lax, or that they have some reason to suspect that there’s vulnerabilities, but because the payoff of finding a vulnerability there can be big. And so there’s a big focus there.

So yes, the bigger you are, the bigger the target. But that doesn’t mean that the scattershot isn’t also happening. And that they’re not also hitting small targets.

[00:23:24] Nathan Wrigley: Yeah. I suppose there would’ve had to have been a lot of joined up thinking in the past from a human to discover that, “Okay, this thing with Linux over here, okay we’ll just store that somewhere. But then there’s a PHP thing over here. Oh, and then curiously, there’s a PHP thing in WordPress, which,” that would’ve all had to have been conjured up by a human. And the memory of that would be difficult to maintain over time. But presumably the AI can just remember that forevermore. Store that PHP thing for the next decade and suddenly whip it out when it’s happens to coincide with some other thing. It’s fairly bleak.

Okay, so in terms of WordPress specifically, what is the incentive specifically? Why would somebody, let’s say somebody was coming after WordPress. What is it that they gain? What could they possibly have that benefits them off the back of a, let’s go for WordPress Core vulnerability which is, I don’t know, you can successfully log in as an admin or whatever it may be. What do they actually gain?

[00:24:17] Aaron D Campbell: It really comes down to money in end, if I’m honest. WordPress Core powers tens of millions of sites all over the web. Some of those have valuable stuff on them. Many of them frankly don’t. But that doesn’t mean that they’re worthless. They can be used, you’ve seen pharma ads and stuff showing up on a site, and it’s a pay per click kind of thing. And someone’s making some money off of putting not great ads your site. Even if you don’t get a lot of traffic, they’re making something. And when you’re looking at the potential of this vulnerability could apply to tens of millions of sites, you don’t need to make much per site.

But also, you could use that site as a way to have broad compute power to attack some other site. You’re using tens of thousands of sites to do it. Each one of them is on some separate IP. So now you have a distributed attack that’s harder to block than if you were doing the same attack from one place.

But you’re only doing that because it costs a lot to buy your own distributed power from everywhere. So you’re essentially stealing it and it’s making it, there’s some sort of worthwhile monetary value from it.

And so you may think, they can’t make anything off my site. They don’t have to. Your site’s one small bit in a huge array of sites that they’re trying to get, to get some monetary benefit in the end.

[00:25:40] Nathan Wrigley: So there’s no one size fits all. But money is essentially the broad overlapping thing?

[00:25:46] Aaron D Campbell: I mean, there are exceptions to that, where people are doing it for some political reason. Or some moral directive that they have or whatever. But the vast majority can be traced back to there’s money in it somewhere.

[00:25:59] Nathan Wrigley: I wonder curiously, because you mentioned about things like, pay per click style, you take oversight and you flood it with, I don’t know, nonsense about the thing that you’ve got and you want the world to notice. I wonder if curiously, people’s adoption of AI and that different way that we’re searching for things will actually impoverish that way of monetizing, because simply nobody’s actually looking on a search, well, increasingly people seem to be relying less and less on a search engine, and so maybe that kind of bit of it will dry up. Who knows?

[00:26:27] Aaron D Campbell: I love the optimism there. And I would like to think that those ads specifically probably will at some point. But the root of how those work is, I’ve broken into a site and I can inject some JavaScript ad, or some something like that.

And if those ads stop being valuable, then maybe I can inject some AI directives so that when an AI agent of some kind hits that site, it’s getting some sneaky thing snuck into its memory, or pulled in as a skill, that can then use that AI agent for nefarious purposes in the future.

I think that we can’t lower our guard against those things, because our adversaries will pivot and reuse it for something else. And so we will continue to protect against it.

[00:27:13] Nathan Wrigley: I’m going to peel back the contents of your head a little bit here. Because I’ve often wondered what the characteristic is of somebody like you who constantly facing this tidal wave of things. You’ve got to get up every morning, and every morning you could potentially wake up to the next big thing.

How do you just remain calm in the face of all of it? It’s a peculiar question, I realise, but tomorrow could be the next big thing. The day after that could be the next big thing. I’m imagining on most days now there is not necessarily the next big thing, but there’s a thing. It’s like you’re a fireman or something, except that there’s a fire going off in every district of town, and you are constantly busy and you never get to put the fire hose down. You’re just constantly at work.

[00:27:52] Aaron D Campbell: Some of us love that little consistent regular shot of adrenaline, and we get it in different ways than the firemen. But, honestly, I love complex problems solve. I love the challenges. Do I get exhausted and burnt out at times when they really do come every day for X amount of time? Sure, I’m human, I need to sleep, et cetera. But I think that it’s because I enjoy figuring out those really difficult problems, that I enjoy being in this space. And even specifically on this side of the space, the white hat side.

[00:28:26] Nathan Wrigley: Yeah. I suppose it’s like playing a good opponent at chess. You enjoy the chess game, even though it’s a hard thing and it stretches your brain. You play the chess over and over again because it’s a pleasurable thing to have your brain exercised in that way.

[00:28:39] Aaron D Campbell: And it’s like the more you do it the better chance you have at winning at chess. And I think it’s the same way in our game, right? Like the more you’re doing it, the more ways you’re finding to outmanoeuvre and to essentially win, and keep people safe online. And that’s, that’s exciting.

[00:28:56] Nathan Wrigley: You get the fist pump moment do you, there’s once in a while where you literally figure something out and you’re like, I nailed that.

[00:29:04] Aaron D Campbell: You absolutely do.

[00:29:04] Nathan Wrigley: Okay. Yeah. That’s really interesting. Your bio reads like an open source manifesto. I know that open source has been the thing for you throughout your career. I imagine that you could have gone into proprietary security and all of that.

But how does open source, particularly WordPress, how does that approach to developing software, how does that benefit the position that we can take and the security posture that you can take, and the reliability that you can have in things like WordPress going forwards? In your head, does it offer a superior model for fighting the adversaries?

[00:29:35] Aaron D Campbell: Yes, in my opinion it offers a superior model for fighting the adversaries. And the reason is actually still the same as it was 20 years ago when I started doing this. And I’ll explain why in just a second, but first, the reason is because we are able to benefit from many intelligent people, many more than any single company could with their source code.

Looking at our source code, and finding the weaknesses and even pitching in to help fix them. Hundreds of thousands, or millions, of people around the world are looking at our source code, finding those issues, and able to help pitch in and fix them, or report them to us so that we can, by having all that out there, it’s sort of like a building’s not less likely to collapse because no one saw the crack. It’s actually better that people are inspecting it, and finding those things and making sure it’s done right.

Now, that has shifted a little bit now, where in the past our adversaries looked at our source code too, right? They would immediately look at our repository when new things went out. As a matter of fact, when I ran the security team, I stopped committing stuff for a while, because it turned out that was a tell that this thing was probably a security issue, and people would look at that and try to figure it out.

So now the adversaries are using AI to watch our source code, which is also open to them, 24 7 and really look deep at it. But so are those many thousands of people using our source code for good. And so it’s still true that we have so many people on our side in helping us out, because our source code is out there because we’re open source, and it outweighs the bad. We find things faster because of that, and ultimately end up with more secure software more rapidly.

[00:31:36] Nathan Wrigley: Is there ever going to become a time where the amount of time that a vulnerability is available becomes moot? So in the past, a six hour window, where something wasn’t patched in WordPress Core, that’s a thing, but it’s not really a big thing. Maybe a month where something’s unpatched, that’s a big, I’m just wondering if in the future with the nature of the adversaries that you described and the tooling that they can bring to bear, if even like a three or five second window is going to become a thing.

[00:32:05] Aaron D Campbell: That is possible. We’re not at the three to five second window yet, so that’s good. I’ll let everybody relax a little bit. But the time from vulnerability disclosure to exploitation has shrunk dramatically over the last few years.

We did in fact used to have weeks, and then eventually days where it was okay to find out about the vulnerability, and responsible people, or responsible hosts, or responsible software companies could see that disclosure, patch the problem before there was much exploitation at all. And that’s now hours for major vulnerabilities.

As a matter of fact, we did a Monarx in conjunction with Patchstack, did like a year in review, thing looking back at last year. And we saw that for the more major vulnerabilities, it was about five hours. That’s not enough time for, you know, what happens if it happens in the middle of the night for a host who’s constantly monitoring that, immediately patching it, that’s difficult. And I do think that it will continue to shrink. And that that time that causes risk will be shorter and shorter.

And, we saw that with the recent wp2shell WordPress exploit. Once we released the patch, and everything was out there, the spike of exploitation that we as Monarx saw, like monitoring stuff happened within 30 minutes. Honestly, even a little bit faster than that. But the big spike started coming in about 30 minutes later, and that is just really fast.

But on the flip side, all that coordination that I talked about that WordPress did, had many millions of people already protected by then. And that’s how we have to look at it. We have to say, this is eventually going to get down to three to five seconds being a problem. How do we get ahead of it? And that’s what we’re trying to do.

[00:34:03] Nathan Wrigley: So a timely thing at the moment is this new innovation in the WordPress space called Protect the Shire. And Protect the Shire is the, a time bound moment where a plugin that has an update, it can’t be updated at the moment, I believe it’s standing at something in the region of six hours. On the face of it, that seems like a really excellent posture. But then there’s the flip side of that. If an exploit becomes discovered, and nobody can update their plugin for six hours, then that’s a big six hour window we’ve just painted. in the future where milliseconds may count. What do you think about that? It’s a interesting innovation. It’s something new. It was worth a try. Do you think that’s the way forward?

[00:34:41] Aaron D Campbell: I think it, was not only worth a try. I think it was a really good choice, and I think it will continue to be. We are seeing that a lot of current attacks are essentially supply chain attacks. How can we compromise whether it’s some package, an NPM package or something like that. Or whether it’s a plugin that’s gotten sold to a nefarious person, or even just hacked into and taken over by a nefarious person. That is happening more and this six hour gap helps protect against that.

But it can’t be a hard and fast, locked in stone, can never have exceptions, rule. And the truth is, it’s not. If there is a vulnerability in your plugin, or especially in a major plugin, reach out to the WordPress Security Team because we can coordinate a faster release, we can make an exception to that rule when it’s necessary.

And I think that for security fixes that are clearly security fixes that exception iss an easy one to make, because we do want to protect immediately. But slowing things down enough to make sure that there’s not been some sort of supply chain issue that is actually going to cause a vulnerability rather than fix one, is smart.

And so I think that it will find the right balance there as we continue to move forward, and figure out how to make better processes around this, to make it easier to do the right thing all the time, and know exactly which of those right things. But I think at the moment we’re in a pretty good place there and continuing to find the exact right place.

[00:36:18] Nathan Wrigley: It feels from the outside as if security’s fairly binary. On the one hand, adversary on the other hand, good guys. On the one hand hacked, on the other hand, not hacked. It’s black and white. But it seems from everything that you’ve been talking about today, that you are occupying a really grey area. You’re just trying to figure out what the path is forward. You’re constantly staring into the future trying to figure out what the adversaries are doing. Trying to patch, trying to make sure that everything is as good as it possibly can be. And I hadn’t really thought about it in that way. It’s not, there is no destination here where everything’s white. It’s a journey and every day’s going to be a bit grey. There’s going to be a bit of black and a bit of white, but a lot of grey in the middle.

[00:36:58] Aaron D Campbell: I don’t really look at it as grey, but I can see where you’re going there. But I think that there is this black and white, and then there’s sort of the cloudy. The further forward you look, the more difficult it is to know exactly where the black and white are always going to be. And some of that sort of comes across as grey. It’s a little blurry. You can’t quite figure it out.

But you’re right. there’s some prediction. There’s some, we think that moving this way is going to cause more white and less black. And that’s what we’re, that’s what we’re constantly aiming for. But you can’t just say turning right always makes things more white. Because sometimes there could be black over on that side somewhere, right? You’re really trying to be predictive, but not just randomly predictive, right?

Many of the people like myself that are trying to help guide this path forward, and even more than me, some of the people like Matt, who instituted that wait policy and some of the people that are running the WordPress Security Team, we have decades of experience watching this, that’s helping to inform our predictions. And so it’s not, we’re not just willy-nilly guessing. And I think that’s important to point out to the people that rely on us, to help guide them to the right space going forward.

[00:38:02] Nathan Wrigley: Yeah. Okay. So my schooling in chemistry was pretty basic, but I know that if I want to understand chemistry, my quickest way to do that is to rely on an expert, is to go and find a chemist who has years of experience. And, the same would be true here. I think most of us have probably not got the capacity to actually get a hold of what you’re saying. We, understand that your expertise is what we need to be listening to. But I’m just wondering for a typical WordPress user of whom many listen to this podcast, they have a WordPress site, but they’re not really interested in security, other than how it may impact their business.

So I’m going to ask for some very basic advice here. What would be the 1, 2, 3 things that somebody using WordPress with no security credentials whatsoever. What would be the few things that you would advise them to either go and read, or go and do, or go and think about?

[00:38:51] Aaron D Campbell: Yeah, so I think the biggest thing that I would encourage them to do, is essentially position themselves in such a way that they are relying on the experts, right? You’re not an expert and that’s okay. No one can be an expert in everything. But there are some things you can do to position yourself such that you’re benefiting from those experts.

One of those is updating as fast as possible. So WordPress auto updates turned on, those kinds of things. This WordPress Security Team that I’m talking about that has so much expertise in the area, and their whole focus is trying to make sure that WordPress is always secure. That lets you rely on them to help keep your site secure.

I think in similar ways, you want to find the right host that is also doing those security focused things for you, so that you don’t need to. And maybe that’s asking your host, what do you do to keep me safe? We talk about security, like the best security is layered security. It’s almost like having a gate at the complex, but also having a lock on your door, right? Those kinds of things. You can ask your host, what do you do to protect me in a layered way?

And maybe that question doesn’t make sense to you, and maybe even their answers don’t make sense to you, but if they have an answer, that’s good for you. It means that you can rely on their expertise.

And then stepping out of the obvious space to give a third thing that people should be doing. And this is, this may sound out in left field, but you should get some form of dark web monitoring for yourself, for your own credentials. And whether that’s going to someplace like, Have I Been Pwned, and looking at your own email address, and passwords and seeing if they’ve been in some breached data from somewhere, and are now being sold on the dark web. Or whether that’s using some service that offers it. I think that’s important, more so now than it’s ever been.

Because one of the other things that AI is doing that it’s particularly good at is collecting all this massive amount of breach data that’s happened over the last couple decades, that’s being sold on the dark web. Collating it all and saying, oh, we see that, gosh, 15 years ago, an account that Aaron had was in a breach. And we now know one of his passwords.

And granted it’s 15 years old, but it’s very easy for that AI to then say, where is Aaron now? What’s he doing? What can we learn about him? He works at Monarx. I wonder if this password works for his Monarx account. I wonder if this password works for the bank that he’s at. Or this other tool that we see that he uses. Let’s try all his social media accounts.

And so knowing whether that’s out there and being able to, you can’t get rid of that data, but being able to do things to protect yourself because you now know it’s out there is more important than it’s ever been.

[00:41:47] Nathan Wrigley: I hope you take this in the spirit in which it’s offered, but I really do wish to live in a world where you don’t have a job.

[00:41:55] Aaron D Campbell: Me too.

[00:41:56] Nathan Wrigley: But, am glad that we live in a world where you do, somebody like you does have a job. So I hope that landed correctly.

[00:42:02] Aaron D Campbell: If I could work to the point where I could work myself out of a job, I would find a new career and I would feel so accomplished, you couldn’t even imagine it. I’m okay with that.

[00:42:12] Nathan Wrigley: Yeah. Good. Aaron, just before we wrap up, is there a place where you hang out online where people could poll you if they’ve got a question, or any thoughts about what we’ve talked about?

[00:42:21] Aaron D Campbell: Yeah, if you’re looking for me professionally, you can find me Monarx.com, M-O-N-A-R-X.com. I also have aarondcampbell.com if you want some of my own more personal takes on security and things. And you can find me on Bluesky or the WordPress Slack. Those are probably the biggest places I’m at.

[00:42:40] Nathan Wrigley: What I will do, dear listener, into the show notes, if you go to wptavern.com and you search for the episode with Aaron Campbell, you’ll be able to find the links. I will dig out the Bluesky, and the various social links and the Monarx website and what have you, so you don’t have to hunt around too much. Go there wptavern.com. And Aaron, thank you so much for chatting to me today.

[00:43:01] Aaron D Campbell: Thank you. This was a really fun talk.

On the podcast today we have Aaron D Campbell.

Aaron is a seasoned veteran in both the internet and WordPress space, with over 25 years of experience spanning agency work, security products, hosting giants like GoDaddy and Newfold, and now his role at Monarx, a company focused on malware detection and remediation, particularly for web hosts. He’s led the WordPress Security Team, has been deeply involved in shaping security practices, and remains tightly connected to the WordPress ecosystem.

We talk about the rapidly changing landscape of WordPress security, specifically how the advent of AI has escalated the speed, scale, and complexity of attacks, moving the security game from a battle of wits, to a battle of compute power. Aaron discusses how attacks that once required human ingenuity are now orchestrated by AI agents capable of chaining vulnerabilities that humans would struggle to conceive.

We get into the shift from a reactive to a proactive security posture across the WordPress ecosystem. Aaron explains how both attackers and defenders are now deploying AI, leading to an arms race where AI is used to combat AI, and where collaboration among security teams is just as crucial as information-sharing among adversaries.

We chat about the motivators behind attacks, spoiler, it’s almost always about money, and the specific vulnerabilities WordPress faces as the most popular CMS on the web. Of interest is the narrowing window between when vulnerabilities are discovered and when they’re exploited, how supply chain attacks are on the rise, and what the WordPress “Protect the Shire” innovation means for plugin security.

Towards the end of the episode, we explored practical security advice for everyday WordPress users, with Aaron recommending actionable tips on updates, choosing security-minded hosts, and monitoring for compromised credentials.

If you’re concerned about how AI is reshaping the WordPress security landscape, and want to know how the community is responding, this episode is for you.

Useful links

Aaron’s website

Monarx website

Monarx and Patchstack’s State of WordPress Security In 2026

WordPress wp2shell Exploitation Grows as Public Exploit Fuels Mass Scanning

Protect The Shire

Have I Been Pwned

Aaron on Bluesky

💾

#231 – Damon Cook on How WP Trend Watcher Keeps Him Up to Date With WordPress

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress, the people, the events, the plugins, the blocks, the themes, and in this case a new way to keep up with WordPress news and updates.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.

So on the podcast today, we have Damon Cook. Damon has been a developer in the WordPress ecosystem for over a decade, working with WordPress centric agencies, and more recently running his own freelance business, Noma Digital. He’s a longtime community member, contributor, and someone who remains keenly engaged with the latest WordPress developments from releases like 7.1, to shifts in plugins, themes, and the broader WordPress landscape.

Damon joins us today to discuss WP Trend Watcher, an open source tool he’s created to help WordPress professionals keep up with the ever increasing deluge of news, community updates and feature releases. As the WordPress space grows more dynamic, and let’s be honest, sometimes a bit overwhelming, WP Trend Watcher is designed to sift through a fire hose of RSS feeds, summarise the trends, and inject some much needed human curation into AI generated content.

Damon talks about the importance of staying ahead in the WordPress ecosystem, especially for freelancers, agency owners, and developers who want to anticipate changes and support their clients.

He gets into the technical nuts and bolts, breaking down how the tool gathers, and summarises, news. The models and local AI setup he’s experimented with, and the balance between automation and critical human review.

If you’re someone who struggles to keep up with the relentless pace of WordPress news, and wants a smarter way to separate the worthwhile updates from the dross, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Damon Cook.

I am joined on the podcast by Damon Cook. Hello, Damon.

[00:03:04] Damon Cook: Hi, Nathan. Good to see you again.

[00:03:05] Nathan Wrigley: Yeah, thank you. Damon and I had a chat at WordCamp US. I think you said a little while ago that it was in 2024. So it’s been a few years since we’ve had a chat, and there’s been a few pivots in your life. At the time you were working for a hosting company, which I don’t think you are doing anymore. But we’re going to have a chat today about something which caught my attention probably on social media, I imagine, I saw it there. It’s called WP Trend Watcher.

I would just say at the beginning before we get stuck into the topic, if you go to the WP Tavern website, I will bury all of the links in the show notes. So anything that we discover today, go and click on the links over there. And actually given the nature of the topic, it might be wise, dear listener, to go and do that before you get into this podcast, because it’ll be fun to have a poke around and be forewarned as to what is it that we’re going to be looking at.

So anyway, Damon, thank you for joining us again. Just before we begin, I mentioned that you have changed roles in the last 24 months or so. Do you just want to tell us a little bit about you and your roles in WordPress over these many years?

[00:04:07] Damon Cook: Sure, yeah. Yeah, been a developer in WordPress ecosystem for over a decade. And always been with WordPress-centric agencies. And yeah, as of the past year about, I’ve just been running my own freelance, Noma Digital, then also doing some contract work. And yeah, and still keeping up on all the latest WordPress news and features coming out. 7.1, what is coming out in, well yeah, in like a week, I think.

[00:04:37] Nathan Wrigley: Yes. Yeah.

[00:04:38] Damon Cook: Lots of cool stuff there.

[00:04:39] Nathan Wrigley: Yeah, there really is a lot happening. Genuinely, there is a lot happening in the WordPress space. And, it may be that you’re a developer, and so that side of things captures your attention. But from my perspective, I am not really a developer, but I am curious about all the things that are going on, because I’m fascinated by Core and plugins and themes and blocks and all of that.

But equally, the community side and all of that. There’s a whole load going on, and events and marketing and loads going on. But that deluge of information, that sort of fire hose is very hard to keep a track of. Some websites that were publishing for many years die out and other ones replace them, and things come at you from different angles.

And so you have built a tool, WP Trend Watcher, which you’re able to put on your local machine. I believe that’s right at the moment. It’s a sort of local install, and we can talk about the technicalities of that in a moment.

But this tool, the way that you’ve built it is primarily pre-built, if you like, to go out and inspect the WordPress space so that you can summarise the zeitgeist, of what’s going on in the WordPress world. You can keep up without having to do that manual slog of going out, reading everything, spending hours every day kind of wasting time, and I’m doing air quotes there, if you know what I mean.

Okay, so my first question is revolving around the why of this. What was the importance here that you felt that you wanted a tool that did this for you? And really what I’m trying to get there is why did you feel it was important to keep up with the WordPress space? Is it… if you’re a client, if you’ve got relationships with clients and you’re building client websites, is it not enough in your scenario just to know that WordPress drops, they do a version change every now and again, we get a release, I’ve got a suite of plugins, I probably need to keep up to date with those. Why? Why are you interested in the broader landscape?

[00:06:34] Damon Cook: Sure, yeah. I’ve been a, I was pretty active contributor for a while to the project, not so much lately. But, when I was a contributor there was, I mean, there’s always been a lot of news to keep up with, between Slack and Trac and WordPress.org stuff. But I started to see some of what were the reliable sources in that area. And as I work with WordPress daily, I still need to keep up with what is coming down the pipeline.

And so yeah, I just wanted to take that, it was very a selfish starting point. I needed to take all these RSS feeds, get them summarised, but then also verify that, what’s being summarised with AI isn’t just hallucinations or some kind of, you know, mistrust was there, because that’s a critical component to this project was the human layer. It’s just pulling in a bunch of RSS feeds, summarizing it, and then I go through and make sure the summaries and click through it, like a lot of the stuff, and read it, and it’s helpful for me to process and see what’s actually going on and then provide my own judgment on it, so.

[00:07:47] Nathan Wrigley: The sort of curious bit there then I suppose is that you, it feels like you always want to be one step ahead of what’s happening in the WordPress space. And I suppose if you’re being a freelancer, having that knowledge of what’s coming up, particularly in WordPress and WordPress Core, because I’ve noticed that a lot of RSS feeds, for want of a better word, and we’ll get into that in a moment, are Core related.

So that then sort of tells me that you want to be ahead of what’s coming in the next feature set so that you can, I don’t know, forewarn your clients, or practice things that you know are going to suddenly drop on a particular day of the year, and so that when the inevitable call comes, “Why is this there now?” And, “How does this new feature work?” You’re ahead of it all. Does that kind of summarise your interest in it, or is it more eclectic than that? You’re just curious about it because it’s curious.

[00:08:39] Damon Cook: Yeah, I mean there’s certainly the curiosity is there, but yes, I do like to be at the bleeding edge of what is coming down in the new, like for example, the 7.1 release coming out. Just seeing what’s being worked on, what might have gotten dropped from proposals. Yeah and just I guess being in the ecosystem, I’ve seen how a lot of the community has come and gone, and what has been critically talked about is, what is a critical feature, and why might something not be worked on and all that stuff.

So yeah, it’s just a selfish way to keep up on the latest, developer news and, yeah, and share it out and summarise it and get some human judgment behind it.

[00:09:22] Nathan Wrigley: A curious thing which is not related to this podcast, but most Mondays I do like a live show in which we have three or four panelists, and we bat around the WordPress news from the previous seven days. And I’ve been doing that show for, oh, I don’t know, maybe seven or eight years or something like that. And in the sort of the week preceding, I go around the internet, I look at social networks, I read the blogs that I’m familiar with. I’ve got a giant list of RSS URLs in a feed reader, and I go through, and I read them, and I look at them all.

And it, genuinely is incredibly time inefficient. That is to say that I open things, get halfway through, realise there’s nothing really for me to talk about here with my guests, and there’s probably nothing for the the listeners to engage with. And so I lose a lot of time, doing that exercise, and it strikes me that in the era of AI, that would be, the intention here is to cut out that. Cut through the dross, sift out the bits and pieces that are of interest, and make the bits that finally reach your eyeballs worthy of attention.

How have you orchestrated that to happen? Because with the best will in the world, I think we all know that AI can go off the rails a little bit. It may be that it doesn’t quite match the intentions that you would wish it to have. How are you corralling it to be what it is that you want?

[00:10:47] Damon Cook: Sure. Like I alluded to, it just stemmed from a selfish kind of interest in keeping up on these news sources, and I knew a lot of them all had RSS feeds. I think that even I, you know, I have a fascination, an obsession almost, with AI these days and I’m always trying some cutting, more cutting edge stuff and tinkering.

But I think even myself, and I think I see a lot of people confuse AI with automation. And so it’s interesting to see, when I, this project, I didn’t want to automate the whole thing, like just go get RSS feeds, AI summarises, AI publishes, just do it, right? Which I can, we could potentially do with the project, but I limited it to that contract of, go get these RSS feeds, the latest news, come back, summarise them, and then show them to me so I can audit them.

A lot of them, I just open up like yourself. It seems counterproductive, but I actually like that’s how I really keep up. Because if I just read the paragraph from the AI summary, which I do, it’s it’s not really covering, and might miss something in that full article that actually really interested me.

So you know, I click through most of these and I’m reading. I peruse, I don’t read every single word for sure, but I peruse and just try to validate that the summary matches, and then I look for tidbits that might been missed that I’m curious about, and then drop that in the human summary element of the published final briefing. So that’s the workflow of it right now.

[00:12:27] Nathan Wrigley: Yeah.

[00:12:27] Damon Cook: That’s how I’ve set it up and I enjoy just the whole, the sequential part of like gathering and then, there is an automation of it shows me everything I gathered, and then gives me an area to write my thoughts and then I click through everything. So it’s just turned into a weekly, kind of hobby project and it’s fun to do, so.

[00:12:48] Nathan Wrigley: Yeah, so the bit that is infuriating to me is just the dead time. And the dead time for me is not once I’ve found the link. That for me is when it actually becomes interesting. You click the link, you open it, and you do the reading and what have you. It’s finding the link and finding the interesting thing.

[00:13:07] Damon Cook: Yep.

[00:13:07] Nathan Wrigley: And so I think, it is totally credible to get AI to do that. And I have this, I’m not a great user of AI. That is to say I’m not somebody that uses AI an awful lot. But it’s becoming pretty clear to me that one of the areas which it genuinely is good at is curating like a silo of information. You give it a body of information, a corpus of information, and say, “summarise that,” or, “Draw out of that the bits that might be of interest.”

Now, it’s not perfect, but it seems to be exceedingly good at that. The creative side, maybe less so, and we don’t really need to get too much into that. But this bit of drop the corpus of information in, summarise that, publish your results. That seems like a really credible way of using AI in the year 2026, and that is indeed what you’ve done.

So now that you’ve got this built, and I will link to a report so you can see Damon’s previous, I think you’ve got seven or six or something like that, previous ones from previous weeks up, and you can see them all. It basically ends up in a bullet-pointed, numbered list of titles with links, and then maybe one sentence of about 20 words following on from that. And then that will obviously either lead to a click or not.

How have you found those summaries to be? The 20 or so that you’ve got in each of your little editions. How have you found them to be? Do they seemingly accurately represent what’s contained within, or does it tend to go off the rails a bit?

[00:14:39] Damon Cook: No, they’re accurate.

[00:14:41] Nathan Wrigley: Yeah.

[00:14:42] Damon Cook: The key kind of component there is when the summaries happen, it’s using, I set it up because I wanted to use local models. It’s all prompt-based, so essentially, it’s going to these RSS feeds, getting the latest articles and links, then parsing that through AI and saying, and passing a prompt along saying, “summarise this for developers and agency owners with a critical eye on, X, Y, Z.”

And so that’s where things do actually come, they come back pretty accurate. And the inference of what the summary shows, it’s fascinating. But yeah, it’s pretty accurate, and the fun part is trying to prove it, to see like, “okay wow,” that sounds like it would interest me as a developer and agency owner. I’m going to click and read through and make sure that’s an actual thing, and not a hallucination. So it’s like a game of just fact-checking in a way.

[00:15:46] Nathan Wrigley: I’m curious to know what it doesn’t include. So for example the addition, I’m going to call it an addition. I don’t know. Oh, summary. There we go. Weekly summary is what you’ve called it. This particular one has 19 items listed, and I don’t know if it produced 19 different things and all of them got written to the page, or if, I don’t know if you can see in the background, 34 just didn’t cut the mustard. Can you inspect what didn’t get included and thereby start to have intuition to say “okay, I wonder why that one didn’t cut the mustard?”

[00:16:20] Damon Cook: Yeah, there is a built-in, for the AI to, when it does a review, it checks sources and it looks for duplicate, two kind of posts on two different sites about the same exact topic. It’s going to try to not do a summary on both of those.

[00:16:39] Nathan Wrigley: Okay.

[00:16:40] Damon Cook: So it does check for duplicates, weak language, missing sections. So it does do some of that to cut out the duplicate work. But also, yeah, it’s not looking, like part of the prompt and part of the exercise for AI is to not look for superfluous, just like really fact-based deterministic stuff and not just you know. It’s funny because trend is in the title, right? WP Trend Watcher.

[00:17:06] Nathan Wrigley: Which is maybe the exact opposite of what you’re after.

[00:17:09] Damon Cook: It’s kind of like it’s not really looking for what’s popular, but what is factual coming out of a lot of these sources.

[00:17:17] Nathan Wrigley: Okay. When you are looking at this, this is a strange question, and I don’t know how you’re going to react to this. How does it make you feel? Do you have the intention that you’re cheating on the Damon from five years ago would’ve thought, “Oh, this is horrific, somebody did all this with a computer. This should be done by, a human being should be corralling this.” How does it make you feel on that level?

[00:17:41] Damon Cook: Yeah, it does make me feel cheap.

[00:17:43] Nathan Wrigley: Yeah.

[00:17:45] Damon Cook: And I think that’s kind of why I publish these. It’s trying to be transparent. So if anybody’s going to go and read this, they know that I even put at the bottom how much time I spent trying to look through everything. So you can take all those facts and base whether you want to read this or not.

[00:18:08] Nathan Wrigley: Yeah.

[00:18:09] Damon Cook: Did he spend enough to? You can pass your own judgment. Did he spend enough time? Maybe he should have spent more time.

[00:18:14] Nathan Wrigley: Yeah.

[00:18:16] Damon Cook: But yeah, that’s part of the exercise for me is making this open source, and just having this public, and so if folks do find it fascinating and helpful, they could even fork it and try to do something else. Or I even have, possibility to submit sources because I’m always thinking “Should I have another source in here?” or.

[00:18:39] Nathan Wrigley: Yes, yes.

[00:18:41] Damon Cook: There’s room for improvement too.

[00:18:43] Nathan Wrigley: The issue there is you end up with scope creep, don’t you? And before you know it, you’ve got 5,000 RSS feeds that you’re pummeling everywhere, and then you really are in a maze of trying to figure out what’s relevant and what’s useful.

The report that you get on the front end, obviously, you’ve got these AI generated the numbered list, in this case 19, the one that I’m looking at. Again, links will be in the show notes.

But then the interface that you built provides the option then to add sort of human notes, for want of a better word, at the end. So it’s not just a case of, okay, that’s where it ends. The idea is then that you would go in, contribute for yourself what it is that you feel is important here, free form writing like we always used to do, and so on.

[00:19:24] Damon Cook: Yep.

[00:19:24] Nathan Wrigley: Why did you include that bit? Why, what was the purpose in having that? Was it just a more human curated portion at the end, so you wanted to remember what you actually thought?

[00:19:33] Damon Cook: Yeah. It’s twofold. I wanted the human in the loop. It’s a pretty popular phrase these days with AI, but I wanted that aspect there. But also selfishly, a game to fact-check a lot of these things and make sure AI isn’t hallucinating. But also it’s the exercise of memory of like going through and reading these things, because then I actually, you know, it registers in my brain. Like this is really what’s coming down the pipe. Because if I just read through the summaries, even if they were 100% accurate and I just trusted them out of the box, I feel like it doesn’t necessarily always register for me. So the actually exercise of going and clicking and reading through and comparing to what AI summarised is helpful for to sink in that data.

[00:20:20] Nathan Wrigley: I think if this were something that I was looking at, and I’m definitely not ruling out doing something like this because I genuinely think there’s a lot of merit in my specific case for this. I think I’d be looking at four of those a day and just trying to, I don’t know, at 9 in the morning just before the day begins, or at 5 at night just as the day’s about to end, the workday. Just go in and look at a few of those. Because I’m like you, if I read the AI 20-word summary, there’d be no substance to that and I wouldn’t remember it.

But the fact that the interface is there and those articles have been surfaced, and I presume you could probably run one of these each day and adapt what was there the previous day and what have you. So technically then, how does it work? I’m fairly sure that this is a thing which you have built, and is currently sitting on a machine in your house somewhere.

[00:21:08] Damon Cook: Yep.

[00:21:08] Nathan Wrigley: Just describe the technicalities of what you need to get, on your machine to make this occur.

[00:21:13] Damon Cook: Yeah. It’s a TypeScript code base, and it’s on GitHub, so you can fork it, contribute to it. But yeah, I run it. You can pass in kind of a flag. I run it weekly. It was just an arbitrary decision, and it felt weekly would be good. But you can, yeah, it just checks basically the last date of when it ran, and then tries to grab the sources.

Then I use LM Studio application on my Mac, which allows me to kind of download models that are fit for my system. I have an 18 gigabyte memory that I can work with, so that is limiting. But, I think a lot of these models are coming down in size and the local AI movement, I don’t know if it’s a movement, but I think it’s taking off in a lot of ways.

[00:22:07] Nathan Wrigley: Yeah, I think so. Yeah. Yep

[00:22:09] Damon Cook: We’re starting to see a lot more, yeah, local implications. That was part of the exercise for me, was exploring that. What models I could use on my system, and then what were the results of using those models with this tool for the summaries.

So yeah, I think every week at the bottom, that’s part of the report is what model I used locally to run the summaries against. And I try to switch it up. I think I used probably six of them, I used the same model. I think it was a Qwen model. Then the most recent one I used, I switched it up, and it was a, I forget the name even. It was like an LS.

[00:22:49] Nathan Wrigley: Oh, these things come and go so fast. Yeah.

[00:22:51] Damon Cook: Yeah, exactly. And that’s the fascinating part is just to drop in a new model and see how it does, and the softwares look like, because they do change. And even the report, I think you’ll, if you just compare this week’s with last, just the output is a little different. And I’m trying to… That’s something I plan on working more towards is deterministic, the output. The summaries are one thing, but then when it outputs into the final report, getting that more deterministic. Especially, I really want to have footnotes, so that people can see where these summaries and stuff are, what they’re exactly they’re linking to. It’s kind in there but it does’t always output exactly the same in formatting, so.

[00:23:35] Nathan Wrigley: So you’re doing this work on the local machine, and then obviously I’m looking at it so it’s published, by the looks of it on GitHub. Is that all automated or are you curating that process? Or have you got, you know, your local machine is bound to GitHub, your GitHub repository and so this is all automated in that sense as well?

In other words, what I’m saying is if you took a break for a month and came back, would this all just be chugging along in the background and producing these weekly reports? Or is this something that you manually invoke on a weekly basis and copy and paste and what have you?

[00:24:07] Damon Cook: That’s the part that, yes. I just run the report and write my judgment in it, then publish it to GitHub, and then GitHub does a little, it takes basically the artifacts and just spits them out. But there’s not much there in the automation on GitHub. It’s just publishing it to GitHub Pages.

The fact that I have a section that’s required for human in the loop kind of takes away full automation. I could make it run, but then I would have to take that component out of me reading through, clicking through, and writing my own judgment at the end of the report. And I don’t plan on getting rid of that. I actually enjoy that aspect, so.

[00:24:47] Nathan Wrigley: So it’s become a bit of an interface. The AI plus Damon equals the finished product. You really don’t want it to be automated. And in a way, that feels to me a bit like, I don’t know, a race to the bottom. If we automate all the things, I just don’t know where the audience for that lives, because you’ll, never really know. Because there’ll never be a moment where you look back at it and say, “Is anybody reading this?”. “Has anybody talked to me about this?” and what have you. Whereas the fact that you’re interested in it, you’re on this podcast talking about it, you’ve got an interest in the subject matter, you’ve clearly engaged with it. I don’t really have a question there, but there’s definitely something there. The fact that you’re in the weeds of it and it’s not just AI for AI sake, I think is important.

[00:25:32] Damon Cook: Yeah. And it’s, yeah, that’s a great point. And I think that makes me, I don’t know, I guess go back to, where some of this started from. Yeah, I think people are creating their own knowledge bases. And you even touched on this. Just having that corpus of artifacts, a lot of that AI can do these days, and you can automate some of that.

But, how you take all that data and get the human in the loop and, is it even interesting if you, it’s interesting maybe to you to read, but if you want to share that, is it going to interest others? And yeah, the human aspect is critical for me there, because, especially if you’re going to share it publicly, you know.

[00:26:14] Nathan Wrigley: Yeah.

[00:26:14] Damon Cook: At least be transparent.

[00:26:16] Nathan Wrigley: Yeah, so you’ve called it WP Trend Watcher. And it feels to me, if I was to rewind the clock to, I don’t know 2023, where for the first time we were all beguiled when ChatGPT came along, and we all just thought this whole interface was remarkable. But it felt, oh, it’s novel, it’s interesting, it behaves in many ways it’s a bit, I don’t know, passed the Turing test and it convinced us that it was human.

But now that we’re in the year 2026, it feels like one of AI’s central roles is just, as I said earlier, these corpses of information, but not finite in the way that a human brain is. There’s only a capacity that I have to remember so much, and it’s alarmingly little. But over time, if you were to stick with this endeavor, the name that you’ve given it, this sort of Trend Watcher, it feels like the data that you’re gathering, as it grows and grows and the AI’s capacity to manipulate, understand, I’m doing air quotes, “understand” and, create meaning from the disparate bits of data, that will grow over time.

And so it’d be interesting in 2027 and 2028, what happened? Why did that bit never got built? And how did we get this thing shipped into Core? Where did it come from? What were all the little bits and pieces? Where were the jigsaw pieces that led that to happen? And how did this happen? And what’s the market trend? Why have we got a 4% decrease or an 8% increase in market share? How’s all that happened?

So it feels to me as if you keep pushing this out, that kind of information will be available, kind of MCP-able, by simply asking it questions, in a way that we’ve never had available to us in the past. Again, there’s no question, but do, you know what I’m saying there?

[00:28:03] Damon Cook: Yeah. I think, when I set out to build this there is, and there is still a component where I do want to have kind of the trend watching part of taking these past reports and having AI review them, and come up with inference of was there a trend? Why, yeah, why did we go from report 1 to report 18 about this? Maybe there’s this feature in WordPress 7, whatever. What changed there? And come up with a separate component for that. I haven’t built that in, but that’s kind of a potential, that’s always the end goal. And keeping these receipts for now and generating these reports is just the scaffolding in a way.

[00:28:48] Nathan Wrigley: So it feels to me as if it really isn’t bound to WordPress. You could run with what you’ve built and point it at just about any industry or thing. Your local tennis club or, whatever it may be. You could, over time, build up this sort of trend analysis, and see what’s going on.

And dare I say it, you could even implement it upon yourself so that you can see, what’s the cadence of my writing? How have I done my fitbit data or whatever it may be? You can see that, even as I’m saying the words, I’m thinking, “Oh, this is a dystopia that I don’t want to live in.” But at the same time, I’m really curious as to what that bigger capacity to maintain state and hold data over time. What that will furnish us with.

Because we all forget things, our brains are very ephemeral. Things that are important to us come and go. We misremember things constantly, and it will be really interesting to see what things like you’ve built, are going to enable us in the future. And it does seem like this is baby steps. The humans in 2029 looking back on the work like you’ve just been talking about for the last half an hour will think, “Oh, that was cute, but look where we got to now, we stood on the shoulders of those giants, and here we are now.” It’s fascinating and terrifying in equal measure. Let’s say it that way.

[00:30:11] Damon Cook: Yes. Yeah, absolutely.

[00:30:13] Nathan Wrigley: Yeah.

[00:30:14] Damon Cook: There’s so much data and it’s just growing, right?

[00:30:17] Nathan Wrigley: Yeah.

[00:30:17] Damon Cook: It’s going to get worse before it gets better.

[00:30:19] Nathan Wrigley: Yes. Well, it’ll be very interesting to see how it all lands. But, what I would encourage everybody to do, I’m going to link to at least three things. I will link to the GitHub repository, which is obviously at Damon’s GitHub account. It’s colorful-tones, and then this is called WP Trend Watcher. I’ll also link to damonacook.com, where there is a blog post about how you can get up and running and what the necessary steps are for you to do that.

But I will also link to the sort of output, which is again, it’s a GitHub repository, but you can go and see the weekly summaries and what have you, and judge for yourself whether or not this is something that you want to install on your local machine.

I think the inevitable is going to be that there’s going to be more and more of this in our lives. It remains to be seen whether we have the time to actually interact with the data that it puts out, or we’ll need another layer of AI to cope with the level of AI we’ve got, if you know what I mean. It’ll be wheels within wheels.

So there you go. Anything you want to add? Did I miss anything there before we wrap it up?

[00:31:27] Damon Cook: No, the only thing just you know I’m colorful-tones. Actually, it might not be with, it might not have the hyphen, but on X. And then on LinkedIn I try to just share the report out weekly on there just for folks keep up, but that’s about it.

[00:31:47] Nathan Wrigley: Lovely, in that case, I will endeavor to find your Twitter or X handle and various other bits and pieces. And, wptavern.com, if you search for the episode with Damon Cook. It’s spelt in the way that you might imagine, D-A-M-O-N Cook, C-O-O-K. Search for that. And yeah, thank you so much for chatting to me today, and bravo for a topic which I think I’m going to be leveraging very much for my WordPress news cycle.

[00:32:14] Damon Cook: We can get that, get some RSS feeds and we can get them, get you hooked up.

[00:32:18] Nathan Wrigley: Yeah.

[00:32:18] Damon Cook: You can start generating some other reports.

[00:32:20] Nathan Wrigley: Okay, great. Yeah, let’s have a chat after we click stop in a moment. Damon Cook, thanks so much for chatting to me today.

[00:32:26] Damon Cook: Thanks.

On the podcast today we have Damon Cook.

Damon has been a developer in the WordPress ecosystem for over a decade, working with WordPress-centric agencies and, more recently, running his own freelance business, Noma Digital. He’s a long-time community member, contributor, and someone who remains keenly engaged with the latest WordPress developments, from releases like 7.1 to shifts in plugins, themes, and the broader WordPress landscape.

Damon joins us today to discuss WP Trend Watcher, an open source tool he created to help WordPress professionals keep up with the ever-increasing deluge of news, community updates, and feature releases. As the WordPress space grows more dynamic, and let’s be honest, sometimes a bit overwhelming, WP Trend Watcher is designed to sift through a fire hose of RSS feeds, summarise the trends, and inject some much-needed human curation into AI-generated content.

Damon talks about the importance of staying ahead in the WordPress ecosystem, especially for freelancers, agency owners, and developers who want to anticipate changes and support their clients. He gets into the technical nuts and bolts, breaking down how the tool gathers and summarises news, the models and local AI setup he’s experimented with, and the balance between automation and critical human review.

If you’re someone who struggles to keep up with the relentless pace of WordPress news and wants a smarter way to separate the worthwhile updates from the dross, this episode is for you.

Useful links

Noma Digital

Damon on X

Damon on LinkedIn

WP Trend Watcher on GitHub

You Don’t Need a Fancy AI Setup to Stay Current With WordPress – Damons post about why he built WP Trend Watcher and how to install it

Recent “editions” of WP Trend Watcher

💾

#230 – Adrian Sticea on Navigating the Decline of WordPress Work on Upwork and the Rise of New Opportunities

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress, the people, the events, the plugins, the blocks, the themes, and in this case, the decline of WordPress work on Upwork, and the rise of new opportunities.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.

So on the podcast today, we have Adrian Sticea. Adrian has been working in the WordPress space since 2013, starting out as a developer for small companies. Then moving into freelancing, agency roles in the US, major projects at IBM, a, stint at StellarWP, and extensive work with enterprise level clients.

Most recently, Adrian’s post on LinkedIn about the dramatic drop off in WordPress work through the Upwork platform, went viral, sparking many conversations and comments.

I suspect that many WordPress professionals listening have seen shifts in their freelance workloads, and maybe wondering what’s behind these changes. And Adrian is here to share his own data-driven account.

He talks about his experience using Upwork as a primary source of project leads. How for years it was a reliable fountain of work, but recently the flow has all but dried up.

We dive into the possible causes, the impact of AI making developers more efficient, and thus reducing hiring demand, changes in the broader economy, increasing competition from rival platforms, and how the nature of WordPress work itself is changing.

Adrian mentions the difference between simple website builds, which are still in demand on Upwork, and complex plugin or enterprise projects, which he thinks might have migrated elsewhere.

We also talk about diversification, whether it’s a mistake to rely on just one marketplace for freelance work, and the importance of building real relationships, collecting testimonials, and seeking recommendations. Adrian shares how he’s pivoted, leveraging LinkedIn for networking, connecting directly with agencies, and building partnerships with recruiters and temp agencies.

If you’ve ever felt your freelance pipeline shrink, are curious where the most interesting WordPress work has gone, or want to hear how other professionals are adapting to marketplace shifts, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Adrian Sticea.

I am joined on the podcast by Adrian Sticea. Hello, Adrian.

[00:03:34] Adrian Sticea: Hey.

[00:03:34] Nathan Wrigley: Very nice to have you with us. Adrian is joining us today because of something that he posted on LinkedIn, which captured my attention.

I’m not a frequent lurker on LinkedIn, and so I don’t really know how the algorithm works. But Adrian and I have, as far as I know, not been in communication with each other before. But, Adrian’s post went really viral, I think it’s fair to say, and it certainly caught my attention and got into my feed.

And it’s all about the state of work in the WordPress space at the moment, particularly through a particular platform. And we’ll get into that in a minute, though. Adrian, if it’s okay with you, do you want to just tell us a little bit about your backstory? What it is that you’ve been doing these many years and so on?

[00:04:15] Adrian Sticea: Sure. I started working as a WordPress developer in 2013. I worked for a couple of small companies, local companies that needed kind of customer support, and also web development. And after that I started doing freelancing for about two years. I moved to the US in 2016, that’s when I started to look around for better paid jobs.. And I started working as a WordPress developer for a digital marketing agency, and I did that for, about a year and something.

In 2018, I joined IBM to work on one of their WordPress projects. I think it was the largest WordPress one that they had at the moment. Basically it was a learning platform, and the courses were about technology, programming and other stuff. I left IBM at end of 2020 because of multiple factors, and I started doing freelancing.

I freelanced for about three years and after that I joined StellarWP, where I worked in the marketing department as one of their web engineers. And I worked there for about a year and a half. And at start of 2025 I started doing freelancing again. And since 2018, I mostly worked with enterprise-level companies and more complex work than just building websites.

That’s the stuff that I’ve been doing for the past.

[00:05:40] Nathan Wrigley: Thank you for that, and all of that really plays into what we’re going to talk about because, what I’ll do is I’ll link to the post that Adrian wrote, which kind of went viral on LinkedIn. And the first thing you’re probably going to capture is there’s a graph at the bottom, and it’s a line graph, and it’s not pleasant to look at this line graph. Because it starts off and there’s this blue line and it’s fairly high up on the on the axis and it moves across horizontally. And it just goes along and along and then it just starts to tail downwards until finally, it hits the axis and it basically zeros out.

And so I caught sight of that and I thought, “okay, that’s interesting.” And then caught sight of the word WordPress, you know, and you being a WordPress developer, and then noticed that this was the volume of work that you had been receiving. And we’re talking about volume of work coming through a particular platform. The platform is called Upwork.

Now, I confess I don’t know a lot about Upwork, so we can get into that in a moment. But essentially, it looks like from the year 2015 through 2020, more or less everything that you did, bar a couple of percent, maybe 5% in some years and what have you, was through the Upwork platform. And then by the year 2022, 20% of that had been shaved off, so down to 80%. A year later, 2023, 60% and then 40%. And then in this year, 2026, 0%. And I caught sight of that and I thought, “okay, we’ve got to talk about this,” because there’s a lot of interest in the WordPress space at the moment.

So do you just want to just run us through your journey with the kind of work that you’ve been doing through Upwork and, you know how it’s tailed off? And then maybe we can get into the discussion about perhaps why this is happening.

[00:07:32] Adrian Sticea: Sure. Just to preface, I had periods of time where I worked on Upwork just part-time, not as a full-time freelancer because I had jobs here and there.

[00:07:43] Nathan Wrigley: Ok, yeah yeah.

[00:07:44] Adrian Sticea: And I was actually calculating this morning how much time I was full-time freelancing and full-time on a job, and it was kind of split in half. So basically, half of my professional career was spent as a freelancer, and the other half was doing part-time. So if I had a job, I will search for other avenues to get a bit more revenue in. And also I didn’t like the idea of just relying on one source of income.

So I always had running in the background, the project, a couple of hours here and there or, a week or a project a month that doing. And that graph represents the number of basically of leads and projects that I got from Upwork over the years.

[00:08:28] Nathan Wrigley: Okay.

[00:08:28] Adrian Sticea: Even if it’s full-time or part-time, basically that was kind of the lead source that I primarily used.

[00:08:34] Nathan Wrigley: And so what we’re seeing, I guess is you, like many people in the WordPress industry, you’ve taken the approach that, subscribe to a bunch of these, I’m going to call it a marketplace, you know.

[00:08:47] Adrian Sticea: Yes.

[00:08:48] Nathan Wrigley: Something like that, where you subscribe to this marketplace and it can bolster what it is that you do already. So maybe you’ve got a 50% gig somewhere where you’re part-time and you need something to top that up. Or it may be that, come to rely on it, and it genuinely has been 100% of the income that you’ve accrued in particular years.

But how do you explain though, the fact that it has kind of just gone down? Because to me the obvious explanation, and it’s a fairly, you know, this is the kind of explanation which is being rolled out everywhere at the moment, is AI. Simply because it seems to coincide so perfectly with the advent of AI.

Now, I don’t know if you’ve got any thoughts beyond that, you know really the graph takes a massive turn in the year 2023, 2024, sometime there. And that seemed to be the moment at which, the kind of work that many of us have done in the past perhaps was getting done by AI. And if not getting done by AI, people at least had intuitions that there would be a future in which that work could be done by AI.

So that’s my first pass at this. Do you think there’s anything in that whole AI debate, whether or not it’s captured the kind of work that you may have got from Upwork?

[00:10:06] Adrian Sticea: I think the answer is more complex than just blaming AI for everything that is happening in the marketplace right now. Definitely AI plays a role because it made developers more efficient in shipping code, shipping features and stuff that clients need.

But I don’t think it’s only reason because if you work with clients and stuff like that, you’ll know a client will pay you to do a work. They will not go themself, even if it’s with AI, do the work. So because of it, because AI it’s making developers build faster, the need for developers decreased. That’s one of the reasons behind it. If you want to blame AI for anything, it’s that it made developers faster.

[00:10:55] Nathan Wrigley: Okay, that’s an interesting one. So the work in your experience anyway, the work is still there, it’s just the expectations of the clients maybe have gone up. So instead of wanting X amount of work, they may want 1.5X or 2X or whatever it is, or perhaps have it delivered in less time or something like that.

[00:11:12] Adrian Sticea: I think it’s a fair assumption. But also probably market, the way that the economy is right now, I don’t think it’s in a good shape. And also one of the factors. Like, if you look at the number of layoffs, a lot of companies in the tech sector, ’cause I think this was more affected than others, happened in the past three years.

[00:11:35] Nathan Wrigley: Yeah that’s true. Yeah.

[00:11:36] Adrian Sticea: But AI most likely was an accelerator of that just because. And before 2022, a lot of companies needed engineers to support the demand for people staying at home. And after they didn’t need that demand, a lot of layoffs happened and AI came along. And just it was basically a perfect storm for massive layoffs ’cause you had engineers that can deliver more work, and you didn’t need that many engineers because the demand was not there anymore.

[00:12:09] Nathan Wrigley: I suppose the other thing we should bring into question is the popularity of WordPress as an avenue to gain work. So for example, I don’t know, probably 2018 feels like a good place to point the needle. 2018, WordPress couldn’t be more popular.

[00:12:30] Adrian Sticea: Yeah.

[00:12:30] Nathan Wrigley: It was just really really super popular, everybody was talking about it. It was an exciting place to be. Lots and lots of work. Lots of companies getting in and investing in all sorts of bits of WordPress.

[00:12:41] Adrian Sticea: Mm-hmm.

[00:12:42] Nathan Wrigley: Whether that was the community or getting plugins built, and shipping them and all of that kind of stuff.

[00:12:46] Adrian Sticea: Yes.

[00:12:47] Nathan Wrigley: And so I wonder if maybe that plays into it. You know these companies, who require websites to be built, or projects to be built. I wonder if they’ve cast their gaze elsewhere, and so that reservoir of work in the WordPress space on the Upwork side has dried up a little bit.

[00:13:03] Adrian Sticea: Yep definitely today there are more options than there were in 2018, like with the rise of Wix, Squarespace, other page builders. Definitely, made people that just wanted websites built, like presentation websites, simple stuff, not rely on WordPress. Because to be honest, WordPress out of the box is not that user-friendly for building a website as the other competitors are. Because you still, or at least before the full site editing was introduced. But even then, it’s a steeper learning curve than other page builders in a sense.

But where I see the deep is actually in newer projects rather than legacy ones, where companies that used WordPress to build their infrastructure, at least web infrastructure on. Because newer builds probably rely more on AI than on WordPress, and that’s kind of basically the, where the market shifted.

But again, like if companies used to build, because I see this in the clients that I serve. Not one of them that I worked with probably the past two to five years said like “Let’s remove WordPress from our web assets and just build it with AI,” because they understand the value of it, and also like technical debt and what actually maintaining software means so.

[00:14:23] Nathan Wrigley: Do you think then there might be a realignment? Let’s say you’re a fairly large company and you’ve got WordPress website as you just described, you’re willing to let go of that. You’ve got so much stuff in there and legacy, and all of your staff know how to use it and what have you.

Do you think though, perhaps we’re in an era though where the experience that somebody with 20 years building on top of WordPress could bring, would make them an absolutely invaluable asset? You know, you’ve got John Smith over there, he’s done 20 years of really hardcore WordPress development, and therefore he’s the person that we’re going to reach out to, or at least, if he comes through a platform like Upwork, that’s really credible.

I wonder if we’ve entered an era where, and I’m going to use the word vibe coding, we all know that’s fraught, and not really the right term to use, but I hope you get what I mean. I wonder if it’s now that people are questioning that, and thinking more like, do we really need John Smith with his 20 years of experience at $250 an hour? Or could we hire somebody with half the experience, a quarter of the experience, who charges a quarter of the rates? And if we factor in that it might take a little bit longer, but they’re going to use AI along the way. Do you know what I mean?

[00:15:39] Adrian Sticea: Yes.

[00:15:40] Nathan Wrigley: I’m just sort if that that kudos that your experience used to bring you. I wonder if that’s being brought a bit lower in people’s estimation of importance when they’re hiring.

[00:15:50] Adrian Sticea: I think it might. But again like I think the answer is more complex than yes or no. And I think it all depends on what part, or role, the website or web assets that were built on WordPress is valued by the company.

So if it’s really important thing, probably they will not think about redoing it using AI. If it’s not that important, because I saw this, if it’s not that important it’s just probably a brochure website. It doesn’t do a lot. It doesn’t bring in. It’s just for visibility. Some of them they move to, again, like probably Framer or they just vibe code it.

[00:16:29] Nathan Wrigley: So given all of that, and we’re pontificating and guessing why.

[00:16:33] Adrian Sticea: Yeah.

[00:16:34] Nathan Wrigley: And the truth is we don’t really know.

[00:16:36] Adrian Sticea: Exactly, yeah.

[00:16:37] Nathan Wrigley: We’re putting our finger air and kind of trying to figure it out. However, given that we don’t know, what we do know is that this line chart that we can see, of yours has gone really in a very different direction. Flat lining for years, lots and lots of work available, and now kind of like nosedive, and then more recently fell off a cliff. And so does that mean that you are struggling to find work? Or does it just mean that you’ve pivoted and that work in a different way?

Does it mean that the Upwork platform, I don’t know, is no longer aligned to WordPress, or just doesn’t have WordPress as a priority? How can you explain it, and we’re talking about Upwork in particular.

[00:17:20] Adrian Sticea: Yes.

[00:17:21] Nathan Wrigley: How can you explain it happening in that way over on that platform specifically?

[00:17:26] Adrian Sticea: One of the things that happened, it was probably saturation of a marketplace. That’s one.

And the other thing is that different competitors are on the market right now, outsource companies and more like, just to put it in perspective, most of my clients, probably 95%, are US-based clients, are not somewhere in UK or somewhere in Eastern Europe, or somewhere in other places that are still needing WordPress work done. And the type of projects that I’m looking for are not websites, basically. They are complex builds, plugin builds and kind of regular maintenance that people need. If they have legacy code base that they need maintenance, or adjusting rule or a code rebuild and stuff like that.

So those kinds of projects are not there anymore. You can still find work in building websites on WordPress, or having small gigs. But the type of project that I used to get on Upwork, like I said, like pretty complex builds are not there anymore. And my read it’s like I said, it’s more complex. Probably it’s a market.

[00:18:40] Nathan Wrigley: So, there’s a particular kind of work that you used to get in Upwork which has dried up? And the, let me just understand that correctly. So just the website building side of it, did you say that was still okay? know if you’re just trying to hawk your service as a website builder, that’s fine. But the kind of “I need a plugin,” or, “I’d like a plugin adapted,” or what have you, that kid of stuff has gone away?

[00:19:06] Adrian Sticea: So most stuff that are more developer focused are kind of dried up. At least in the US, because I’m not looking outside of US. So the US market shifted away basically from Upwork towards probably different competitors of them. Or using like temp agencies, or recruiters that pre-vet their developers before they are presented with a candidate they can have a discussion with.

[00:19:33] Nathan Wrigley: Okay. So I’m thinking immediately of things like Codeable and things like that, where they’ve just got a slightly, maybe they’ve got a slightly different approach, I don’t know?

[00:19:40] Adrian Sticea: Yes, Toptal I think also they pre-vet their developers. And also like I said, temp agencies like Robert Half or, I don’t know, whatever tech systems that are here in the US. Basically you have a discussion with the recruiter before being presented to a potential project. It’s a different workflow basically. Because of it, it presents a better candidate than Upwork can present to a client.

[00:20:04] Nathan Wrigley: Okay, so that’s interesting. So we’re apportioning some of the responsibility for this on the platform and the way the platform works and what have you?

[00:20:14] Adrian Sticea: Yes.

[00:20:15] Nathan Wrigley: And so, you know one of the things that we constantly talk about in the WordPress space is owning your own stuff. So for example, rather than posting stuff onto Facebook, write it on the WordPress blog, and then if Facebook goes out of business, or somehow decides that your account needs to be closed, you’ve still got access to it.

[00:20:31] Adrian Sticea: Mm-hmm.

[00:20:31] Nathan Wrigley: And so I’m going to flip that into this conversation and say that sort of seems like potentially what’s happened here to you with Upwork. Presumably over the years, you’ve fostered a relationship with Upwork, and built up your kudos over there, and at some point presumably Upwork recognized that, “Oh, this Adrian guy, he’s really good. Look, he’s getting loads of work. Let’s push Adrian,” and so on and so forth.

Do you have any regrets about putting the eggs into that one basket? Now that you’ve got to the point where the line has hit zero and there’s no work coming through? Do you wish that you’d have been on a variety of, maybe you have been, but do you wish that you’d been on a variety of different marketplaces? Or is it just, “Okay, this has happened. I didn’t think it was going to happen. Time to move on and try the different marketplaces”?

[00:21:19] Adrian Sticea: I think not only me, but people usually are nearsighted, so they don’t think long-term. So whenever I started on Upwork, it was pretty easy to get clients because you don’t have to pay a fee, or you don’t have to go to events, or meet people in person, which for developers is pretty hard, at least for me. I’m a pretty introvert person. Going, mingling around with other people, it’s not something that I look forward to do.

[00:21:46] Nathan Wrigley: Yeah, I get it.

[00:21:46] Adrian Sticea: Or it’s something that it’s in my skill set. Over the years, I got better and better because I’ve worked with clients and became more confident in my skills and stuff like that. But Upwork presented a easier way to get clients, and that’s kind of the appeal of those kind of marketplaces, because you don’t have to go outside of your comfort zone. You just have a keyboard, apply for a different bunch of gigs, and you can get accepted or not.

Just to put it in perspective, probably half of the work that I’ve done was only through messaging back and forth, not even interacting with a real person, which for a developer is really appealing.

[00:22:28] Nathan Wrigley: No kidding, yeah.

[00:22:29] Adrian Sticea: It’s easier in a sense because, again, like it’s easier. But to be honest, the larger projects that I took on Upwork, or outside of Upwork needed that human touch. Like meeting with the client, talking about your skills, how you will approach the project and all of that. So they can gain confidence that you are competent enough to take their work.

So that’s kind of the reason why I got into it. If I have any regrets of it, of course, because if you leave that, you are basically handcuffed to that platform if you want to get more work. Because you don’t have any contacts outside, and also, it doesn’t produce any referrals.

So if a client is satisfied, the maximum that they can do with it, is just leave you a good review because they are so scattered around, they don’t have any other contacts that you can get recommendations from. So basically, for all the clients that I had, I didn’t get recommendations altogether. Probably just one in the past 10, 11 years.

[00:23:32] Nathan Wrigley: Okay.

[00:23:33] Adrian Sticea: That’s not good for long term, because you rely on constant getting new and new work from different clients. It’s not sustainable in a sense, because you have to focus yourself on delivering the work, but also getting the work, instead of building a network of clients that can supply that work for you, and recommend you to their friends and other of their peers.

[00:23:56] Nathan Wrigley: Yeah, I suppose a lesson to be learned, with the benefit of hindsight, is to spread yourself around, but also go looking for those kind of recommendations, and ensure that people endorse you and maybe even write you an email or something that you can put away somewhere and kind of have a bank of credible testimonials and so on and so forth.

Now, the piece itself on LinkedIn got quite a lot of commentary. I have to confess, I didn’t go reading all of the different comments that people had put in. But did you get a sense that the people that were commenting had had a similar experience from you? Or do you feel that you’re in some kind of unlucky, unhappy valley that nobody else over on Upwork is experiencing?

[00:24:37] Adrian Sticea: No, I think I talked with agency owner, that most of their work comes off of Upwork, and they said they didn’t get any. Actually, this was the post that inspired me to write this. They didn’t get any work this month or in July from Upwork, even though they constantly applied. And one of the things that he said, it stood up was that, if they increase a bit their prices, they will not get any responses.

So basically, probably the market became more sensitive on spending. And because of the rise of AI, you can say that AI commoditize more development than it used to be. So it’s not just a me thing. I think it’s a general.

[00:25:24] Nathan Wrigley: So it is more broadly across the platform there. So fees you brought up, that’s interesting. I wonder if people are playing a bit of a wait and see game, and just keeping that money in their own bank account just to see how the landscape changes. Maybe this heralds a change in the industry which is going to stick for a while where the fees that people such as yourself can charge are going to be driven down, because less work seems to be available, so people are going to be more sensitive to the cost of it, and the competition will be greater and what have you.

[00:25:53] Adrian Sticea: Yeah.

[00:25:54] Nathan Wrigley: I guess only time will really tell. Yeah.

[00:25:57] Adrian Sticea: And also most likely is, the fact that AI commoditize programming in a sense. They are not the same number of WordPress projects that are started now. And they use, I don’t know, whatever AI is better on building with, which is like JavaScript-based stacks. And that’s probably the new directions where the new projects are going to rather than WordPress.

[00:26:25] Nathan Wrigley: Okay, so just before we wrap it up then, let’s move to this point, which is that, no matter how much you inspect all of this, and out what’s going on, and the reasons behind it. I guess the bottom line is you’ve got to do something.

Maybe you’re perfectly all right, and you can take this hit from the Upwork platform and that’s absolutely fine. You’ve got other irons in the fire. But I’m guessing the next question’s pretty obvious, which is what are you doing to shore up this considerable loss of income? What’s the plan that you’ve got going forward? You may not have a fully hatched plan, in which case your best guess is fine. But I’m curious to know what your idea is to keep your irons in the fire and to keep the through put of your business up.

[00:27:07] Adrian Sticea: Just to put in perspective, my income didn’t decrease because of Upwork. So I’m pretty good, I’m in a pretty good shape. The thing is that I shifted away from relying on it, and trying to get, work through other avenues. And one of the other avenues that I am expanding on right now is basically LinkedIn, and it’s not.

[00:27:27] Nathan Wrigley: You’re suceeding.

[00:27:29] Adrian Sticea: I’ve succeeded on getting viral, yeah.

[00:27:33] Nathan Wrigley: That’s the first step, isn’t it, in a way?

[00:27:35] Adrian Sticea: Yeah, exactly, yeah. So I took three different approaches on LinkedIn. One was to post content, to see if I get any interaction with potential clients. I did get a couple of leads from that, and I get some gigs from it.

The other one is actually talking directly with agency owners that build websites, but from time to time they have a need for either adjusting a legacy code base, or building something more complex that they don’t have in-house tools for. So I started building those relationship, and I do work with couple of different agencies that I they provide work for me from time to time.

And the third one is talking with recruiters from temp agencies. So I build couple of relationship with some of the big temp agencies, and whenever they have a project that it’s my lane, they contact me first basically, and I get to talk directly with the client, and they decide if they want to work with me or not.

[00:28:34] Nathan Wrigley: So in a sense, although there’s this cautionary tale of, gosh, this whole thing dried up, the bigger picture is that actually the whole thing didn’t dry up. There are different ways of getting the same work. In your case, you just had to be a bit creative for a few months, and start to talk in different ways to different people.

[00:28:51] Adrian Sticea: Yeah, and also another thing is that I needed to start thinking a bit more long term rather than one-off projects, not one-off projects, but just thinking that one source of leads will basically provide whatever I need every month budget-wise.

Also this is how business used to work. Like you went, you interacted with a person, and they give you a business or not. Not chatting with a person on the other end of the world, and they give you work.

So basically, fostering those relationships are more beneficial, and to be honest, they pay better than clients on Upwork. And you get into the cycle of recommendation, and you don’t, it’s less work for you to get clients than it is on Upwork, but it takes longer to build those relationships.

[00:29:46] Nathan Wrigley: Right. And that’s a really interesting observation, isn’t it? Because essentially the advice that you’re giving there is as old as the hills really, isn’t it? You could have had that same marketing advice in like 1930s.

[00:29:56] Adrian Sticea: Exactly.

[00:29:57] Nathan Wrigley: Which is, go out, find people who you can work with, build up a longstanding credible relationship with them, and then the next time they need a bit of work, which hopefully they will, you’re going to be the first person who they’re going to call.

But it’s curious how we’ve all fallen into, and I’m just doing air quotes, “the trap” of having these platforms around you know, like Upwork. It just allows you to very easily get work here, there, and everywhere. And it’s only at the point when that starts to dry up for all the reasons that we discussed that you realise, okay, gotta pivot a little bit. But it’s great to hear that in effect, it’s had no impact on your bottom line. It’s just meant that you’ve had to pivot, do things slightly differently, go outside, get out of the office and go and interact with people in the real world.

[00:30:46] Adrian Sticea: And again, like the projects that I was able to get outside of Upwork are for better clients that I did on Upwork. It’s not that I didn’t work on interesting projects on Upwork. It’s that the opportunities that can lead after the work is completed for those clients are bigger than the opportunities that you get from working on, for clients on Upwork.

[00:31:08] Nathan Wrigley: Oh, I see. Okay, so the long tail of work, you know, let’s say that you land a client and they build website in the year 2026, maybe they’ll need an upgrade in 2028, and they’ll need some modification in 2027 that you’re the person to do it.

Yeah, whereas Upwork is more here today, gone tomorrow. Disposable thing, you finish it, move on, another thing, another thing. And that’s worked for years, but maybe that system, certainly for you at least anyway, is drying up and you’re trying out other things, which I hope you are successful with. I guess that’s the perfect place to, to call it a day.

[00:31:40] Adrian Sticea: Mm-hmm.

[00:31:41] Nathan Wrigley: Honestly Adrian, all the best of luck. I know that when you put that post out, it must have been, it’s hard to write that kind of stuff, isn’t it? Because it demonstrates that in some way you’ve had to modify things and that things have been a struggle. But it’s nice to hear that you seem to have got a handle on it.

[00:31:58] Adrian Sticea: Yes.

[00:31:58] Nathan Wrigley: And I would wish you the best for the future.

[00:32:00] Adrian Sticea: Thank you.

[00:32:00] Nathan Wrigley: If anybody wanted to reach out to you, because we have a fairly large audience, and I wouldn’t be surprised if one or two people out there were going through something very similar, where’s the best place to reach out to you? I can obviously link to your post on LinkedIn.

[00:32:14] Adrian Sticea: Yes.

[00:32:14] Nathan Wrigley: And people can click on the link and contact you via that. But is there any place you hang out online?

[00:32:18] Adrian Sticea: Yeah, mostly LinkedIn. And if you want to check my website out, it’s CustomWP.io. That’s kind of my avenues of contacting me and that’s about it.

[00:32:28] Nathan Wrigley: Okay. I will put that into the show notes. So if, dear listener, you’re listening to this, head to the episode with Adrian in it. Probably by the time you listen to this it’ll be one of the first two bits and pieces on the WPTavern.com website. Go and click into the show notes and all of the links will be buried somewhere in there.

So, Adrian Sticea, thank you so much for chatting to me today. Good luck with the future.

[00:32:50] Adrian Sticea: Thank you.

On the podcast today we have Adrian Sticea.

Adrian has been working in the WordPress space since 2013, starting out as a developer for small companies, then moving into freelancing, agency roles in the US, major projects at IBM, a stint at StellarWP, and extensive work with enterprise-level clients. Most recently, Adrian’s post on LinkedIn about the dramatic drop-off in WordPress work through the Upwork platform went viral, sparking many conversations and comments.

I suspect that many WordPress professionals listening have seen shifts in their freelance workloads and may be wondering what’s behind these changes, and Adrian is here to share his own data-driven account. He talks about his experience using Upwork as a primary source of project leads, how, for years, it was a reliable fountain of work, but recently, the flow has all but dried up.

We dive into the possible causes. The impact of AI making developers more efficient (and thus reducing hiring demand), changes in the broader economy, increasing competition from rival platforms, and how the nature of WordPress work itself is changing. Adrian mentions the difference between simple website builds, which are still in demand on Upwork, and complex plugin or enterprise projects, which he thinks might have migrated elsewhere.

We also talk about diversification, whether it’s a mistake to rely on just one marketplace for freelance work, and the importance of building real relationships, collecting testimonials, and seeking recommendations. Adrian shares how he’s pivoted, leveraging LinkedIn for networking, connecting directly with agencies, and building partnerships with recruiters and temp agencies.

If you’ve felt your freelance pipeline shrink, are curious where the most interesting WordPress work has gone, or want to hear how other professionals are adapting to marketplace shifts, this episode is for you.

Useful links

Adrian’s post on LinkedIn

CustomWP

Upwork

Toptal

Codeable

💾

#229 – Amy Kamala on Art, Tech, and Open Source: A Journey Through WordPress and Community

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, what draws people into the work of open source projects.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.

So on the podcast today, we have Amy Kamala.

Amy’s journey into tech is anything but conventional, starting with a master of fine arts from UCLA, and a passion for art that eventually bled into, and was overtaken by technology. Since 2018, she’s been an active contributor to WordPress, serving multiple teams such as the Hosting and Core Teams.

Her career zigzags through key roles at DreamHost, InMotion Hosting, Pantheon, Canopy Studios, and local government. Picking up everything from technical support and web development, to managing teams of designers and DevOps staff. Along the way, Amy has organised WordCamps, led teams, and is currently being sponsored by Elementor for her open source work.

Today’s conversation gets into the chaotic, creative, overlap between art and tech and how those different mindsets can feed one another, especially in the world of WordPress. We talk about the blend of creative and logical thinking needed in web development and why skills like user experience, curiosity, and even willingness to fail publicly can set you apart.

We then turn to contribution. What draws people to volunteer in an open source community? What Amy gets out of participating far beyond her paid hours, and the messy journey from being an eager helper to an essential part of the team.

She explains the unique feeling of the WordPress community, the importance of being welcoming to new contributors, and why being outgoing and not afraid to ask questions can be your biggest asset.

If you’ve ever wondered about the blurred lines between arts and code, why people throw themselves into volunteer work in the WordPress ecosystem, or what’s really at the heart of this global community, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Amy Kamala.

I am joined on the podcast by Amy Kamala. Hello, Amy.

[00:03:22] Amy: Hello. Thank you for having me.

[00:03:24] Nathan Wrigley: You’re very welcome. Amy was introduced to me by Jonathan Desrosiers, who’s been on this podcast many, many times before. I don’t exactly recall the nature of that introduction, but I’m very glad to have you on the podcast today. The intention really is to have a broad, wide-ranging, no-holds-barred conversation, I think about contribution, why people do it, and the community in general. So we’ll see where it takes us.

Amy, firstly, thank you for joining us, and I wonder if you wouldn’t mind just telling the listeners a little bit about yourself. Honestly, you can go in any direction you like with that. Maybe if you, I don’t know, bind it to WordPress or contribution or whatever it may be, that would be good.

[00:03:59] Amy: Thank you too. Thank you so much for having me. I’m happy to be here. So I’m from Venice Beach, California, and I’m actually an artist and my background is in art. I have a Master of Fine Arts degree from UCLA. But a lot of my artwork was supported by technology, and at some point, technology crossed over, took over, and now my technology is supported by artwork.

I’ve been contributing to WordPress since 2018. In 2019, I became a team rep for the hosting team, and I am now on my sixth non-consecutive year as a team rep. And this year I’m also a Core team rep, which has been really fun and I love working with both teams.

I started working in the tech industry in 2015 in social support for web host, DreamHost. I was there for about five years, a little bit less than five years. I worked my way up from social support to technical support to live chat, and then helped form a specialised WordPress support team. And I was taking escalations, training team members, devising and documenting team processes. And while I was there, I helped strategise and implement new WordPress products which made revenue in beta, and that was really fun. I got to work directly with the CEO and the VP of product, and I learned a lot doing that.

Then I left, and I became a tech lead at a web dev agency, and then the pandemic hit, and we all know how that went. And then in 2020, I started working for InMotion Hosting as their web development manager. I was responsible for over 23 online corporate assets, five web servers, multiple Jira projects, and also the supporting infrastructure, the DevOps pipeline, GitLab, so on and so forth. And I loved that. It’s actually, that was one of the best jobs I’ve ever had. They’re a great company. It was amazing working there. I had an amazing boss. Totally great. I still have friends from there, and from DreamHost for that matter. And DreamHost was also great. I have a special love in my heart for DreamHost. I’ve known those guys for a really long time.

And then I was recruited by Pantheon to be a solutions architect for their professional support team. That didn’t work out for me as I had hoped, and I left a little bit less than a year later and started being a web developer for my local government. Again, I was recruited. I didn’t pursue these jobs. I may have gone in a different direction if I had. And that was a year-long contract. It ended in the end of 2023, and I’ve actually just been freelancing ever since then. I have a contract with a company called Swishtech. They’re not a WordPress company. They’re not even a web development company. They are an AutoCAD. They train and sell AutoCAD software. And they’re great too. And I also am sponsored by Elementor to contribute to the WordPress open source project.

[00:06:58] Nathan Wrigley: Gosh, you really have done the whole lot, haven’t you? There’s just almost no stone that you haven’t turned over and looked at the underside of. That really is a fascinating story, yeah.

[00:07:09] Amy: Thank you. There is, I considered completely abandoning both of those careers, art and tech and going into psychology and becoming a therapist at some point recently over the past few years.

[00:07:22] Nathan Wrigley: Right, okay. Well I could definitely talk about that. There’s somebody very close to me in my family who does that kind of work.

Can I ask, this is a complete segue, the fact that you pursued art at such a high level tells me that there must be some yearning inside of you for that side of life, you know, the artistic side, the creative side and what have you. I’m wondering if there’s any bit of technology that satisfies that, or do you find that you have to go back to the art to sate that craving? Or are there creative pockets inside of tech that allow you to sate that sort of desire to be creative?

[00:08:00] Amy: So that’s a great question and very insightful of you. Yes, so in 2015 when I started working for DreamHost, I’ve known the founders and some of the managers of DreamHost since like 1999-ish. That’s a different story, but I had just finished grad school and I was kind of in a bad living situation and I just needed a job, any job. I didn’t care what job. And so I hit them up and I found like a entry-level social support, entry-level job that I qualified for. It’s pretty easy to qualify for that. Hit them up and said, “Will you recommend me for this job at your company?” And of course they did. I still went through the interview process and like did typing tests and so on and so forth. But that’s how I ended up.

So it was kind of just circumstantial that I started working in tech. And then once I was there, I tend to get really hyper-focused, and I really hyper-focused on my work at DreamHost on moving up and learning technical things. I’ve always kind of had an aspect of technical. When I was doing art, strictly art, just art, I was still doing technical things. In undergrad I got into, well, so I started, I learned HTML when I was like 18 years old in the year 2000. I was an HTML programmer. It was one of my first jobs. The other job, my first job was working at Venice Beach at one of the stores down there. But like first real job, HTML programmer for a web development agency and graphic design.

And then I went to undergrad and I did a lot of fine art, sculpture, video installations. And working with video is pretty technical. You’re using computers. I also learned Photoshop at Otis where I went to undergrad. I still use it. It’s like one of my primary mediums for making art. But working with video is pretty technical. You’re doing editing, you’re working on a computer, there’s definitely a technical aspect to it.

And I also, I had a boyfriend at the time who was doing web development, and so I started learning PHP and Perl. And I started using PHP as a tool to make my animations. I was making little animations at the time, and video art interactive. So I did some installations that utilised interactive elements that actually used web technology.

Then I was working at an animation studio on a Red Hat box. So I had to, I learned Linux, and I also was introduced to Avid which is a high-end, professional video editing software or film editing software. And then I was working at a film post-production facility where I was using DOS, which is Command Line. And also I was working in the tape room transferring tape formats from one to the other. It was pretty technical. And I was also helping their web team manage the online video assets, uploading and downloading with FTP and so on and so forth. So there’s always been an element of tech integrated in my art.

And to answer your question, working in tech primarily, there’s definitely an element of art that supports, that has supported my career in tech. UI/UX design and graphic design rely on the same fundamentals as fine art. Composition, colour, so on and so forth. And so my training there, and I have some, I don’t like doing graphic design. I, like, actually really hate it, but I do have some professional experience doing it. And that led me to be able to lead teams of designers and developers. At InMotion Hosting, I had five developers and three UI/UX designers on my team, who I was the manager of.

So it wasn’t just development that I was doing there. It was also user experience, very user experience-focused. And so my experience with art has definitely supported my experience with tech and vice versa.

Yes, there’s definitely a yearning that, you know, I wanted to do, I wanted to make weird, cute, maybe a little dark experimental films. And I haven’t been doing that for the past 10 years or so.

[00:11:54] Nathan Wrigley: I always think that the motto for WordPress is code is poetry. I think if you peel back the curtain on that just a little bit, obviously, it may be that you’re just trying to create a website, but there are creative ways of doing that. But also code code really does unlock something, but still it’s quite a logical thing. And I’ve always found those two things difficult to overlap. The sort of Venn diagram of logic meets creativity that, I don’t know how well they fit together. But it sounds from what you’re saying that you feel that the two things have married well in your career.

They’ve enabled you to do things because, I don’t know, maybe it’s thinking outside of the box or something like that. Your capacity to think differently to other people. But I’ve always found that curious. I’ve never had a particularly artistic grain of anything in me. I’m much more logical than I am creative. So I’ve always sort of struggled to see how those two things marry up.

[00:12:49] Amy: Oh, well, you know, that’s actually something that I’ve thought about a lot. And the too long, didn’t read, answer for me about that is, so art is experiential. It’s not about the object necessarily. It’s not even about your skills. It’s about creating an experience. The viewer, relationship between the viewer and the item that they’re looking at. Books, movies, music, all of that, it’s experiential. It creates an experience. And so do websites, so does software, so does using the software.

One of the reasons that Apple is so successful is because of the user experience, because they focus on it being an easy, intuitive, fast experience to use their products. And so when you think about it in terms of user experience, and in terms of just human experience, there’s a lot of crossover.

[00:13:41] Nathan Wrigley: When you worked at some of those companies that you mentioned, I presume that you were surrounded by lots and lots of people, in an office environment. So this question, I hope it lands correctly. I’m certainly not trying to put anybody in a box or stereotype anybody. But did there tend to be a fairly interesting split between the kind of character that you would find on the, I don’t know, making the website look nice, let’s say. You know, putting the pixels on the page, the design and what have you, and then the people who are writing the code in order to make those designs a reality.

I just wonder what, if there’s an aisle down the middle of those two camps where, okay, the artistic people, they’re all over there, look at them being artistic, and over there, there’s all the coders, look at them crouched over their computers being logical. I don’t know if there’s a there there, but I’ve always found that curious too.

[00:14:25] Amy: Well, it crosses over in web development. A lot of web developers are doing, as a web developer, you have to do CSS, SAAS, you have to style the front end. If you’re on a, you know, a big professional team, you’re going to have designers, and then you can just pull the styles from software. But if you’re on a smaller team, which, you know, the majority of people end up working at some point on very small teams or even, like, a one-person team, you do it. And so there’s quite a bit of crossover in web development.

In software development, you’re probably always going to have a bigger team, and so you’re going to need designers. But web development, there’s always web developers that like have a history in graphic design, have a history in UI/UX design that ended up also coding. And those designers don’t necessarily tend to be really great at like PHP and JavaScript, but they do tend to be phenomenal at CSS.

[00:15:18] Nathan Wrigley: Oh, interesting. Yeah, okay. Thank you. I took us on a total detour there. That was really not intentional, but it was kind of fun peeling back the curtain a little bit there.

[00:15:27] Amy: Well as a team lead, it really helps to know people’s strengths and talents, that you’re likely to have developers who are more logical and who, like, they can bang out some code. It’s going to function. It’s probably going to have all of the crosses and the dots and the so forth. But then you also have developers who are more visual, but they just kind of like ended up working in development. And that’s who you would want to tap to make something look really nice but still be functional.

[00:15:52] Nathan Wrigley: Yes. It’s a rare and wonderful thing when you encounter that character who can do all of it. I have a friend, a very dear friend who, it doesn’t matter what task you put in front of him, he just excels at all of it immediately. And it’s rare, you know, because there is this sort of, most poeple get into a niche, don’t they, and they become good at a particular thing. And as the world requires us more and more to be specialised in one thing or another thing, we do tend to lean into, I don’t know, I’m a CSS person, or I’m a PHP person, or I’m into JavaScript, graphic design or whatever it may be. And when you encounter that one character that can do literally all of it, I’m a bit in awe, frankly. Quite a lot of my jealous genes kick in and.

[00:16:31] Amy: That’s very interesting. I am the one character, you know, I’ve had my hands in, DevOps, system administration, but also design, art, user experience, accessibility, so on and so forth, which has served my career, you know, being a web development manager, it was absolutely necessary to have that range of skill set. But I will say that I don’t specialise in any of those things. I’m not like a, you know, JavaScript specialist or anything like that. I’m not the SMC on all of those technologies, but have a good umbrella overview that allows like cross-functionality.

I wouldn’t mind specialising in something like that, but I just haven’t really found a niche. I kind of ended up in leadership roles because I’m outgoing and chatty. And so that reads as leadership ability. And I’m good at organising. So those are some leadership skills. And so I kind of ended up, but I ended up in leadership roles before I had mastered anything other than like drawing and maybe video editing. And so in a way that’s been really good and it’s led me on this career path, and also in a way it’s been really bad because I’ve not been able to focus on any specific skills to excel in those. I guess I’ve excelled in team management.

[00:17:50] Nathan Wrigley: It sounds like you’ve not done too badly. It also sounds from, I mean I’m reading between the lines here, and forgive me if I’ve misconstrued what you were saying. It also sounds like from the go, since you finished your arts program, it sounds like you’ve been quite intentional. You know, when opportunities have arisen, the way you’ve described it makes me feel that you can sense an opportunity and you grasp it with both hands, and you’re willing to learn something which maybe last week you’d never heard of, but this week, okay, that’s a thing. Let’s give that a go. Again, forgive me if I’ve got that wrong, but it sounds like you’re quite a force of nature. Let’s go with that.

[00:18:23] Amy: Thank you. That’s correct. I love learning new things, new skills. I’m never like, well, I’m only going to focus, that’s part of it too. It’s a conscious choice to not focus on just one thing. I did at one point kind of like sit down and say to myself, we have to make a decision, art or coding? And I actually determined that I should just stick with tech, the technical end of things because that makes more money than art, even like with a full-time job.

[00:18:53] Nathan Wrigley: Yes. It is difficult, isn’t it, to become an artist in whatever field of art that may be. I think the chances of you making that work from an economic point of view are much more unlikely than they are.

[00:19:06] Amy: Well, I could tell you as a fine artist, I have made $0.

[00:19:10] Nathan Wrigley: Right. Okay. Well there you go. That puts it into stark relief. That gives us some idea.

It also sounds from what you’re doing that you’re on more of a journey than you are arriving at a destination. And what I mean by that is, it feels like maybe if I chatted to you in a decade’s time, who knows where you’re going to be. It’s more of a, this is where I am now. Tomorrow might present something entirely different. Again, I could have that wrong.

[00:19:32] Amy: No, I think that’s actually totally correct. I’ve kind of, I haven’t really been that intentional with my direction. I tried to be when I, you know, made a decision, art versus tech, to go with tech. Secondary decision, I had already decided to go with art and then, you know, switch careers. But at this point I don’t have, like I don’t dream to be a product manager or dream to be, you know, a coder or a specific thing, a software engineer.

I’m not quite sure to be honest. I do know that I love working in the tech industry, that I love working on teams, I love working on software, I love collaborating and focusing on user experience. And I even, I really actually, I loved being in technical support. Being social and chatty is both a blessing and a curse because my entire career exists because I’m outgoing and social and chatty, and I just randomly message people and start talking to them or randomly walk up to people. You know, and that’s how I ended up in all of it pretty much, and even working on releases.

And that’s also helped me to be able to do those roles because I will randomly message anyone and be like, hi, blah, blah, blah. So that really works to my benefit. But it also, like sometimes I say too much, or I definitely talk too much, way too much, way too frequently. And I might like be bothering people. And I’ll ask them. But at DreamHost, Kira Schroder and Mika Epstein both worked at DreamHost at the same time as me. And because I’m not shy and I am apparently not afraid to talk to people, I started messaging them and asking them questions. And not just them, but the other developers and leads, and the VP of product and so on. It helped that I already knew them, but just started asking them questions.

And also, being willing to be embarrassed and to look stupid is a huge plus because you learn a lot from making mistakes. If you make those mistakes in front of people, you’re going to remember. You’re going to remember the answer to those mistakes. And that’s kind of what I’ve been doing. I’ve kind of stumbled up, and asked a lot of stupid questions, which I’m still doing.

[00:21:46] Nathan Wrigley: I’m just going to interrupt you there very quickly because I love when I meet people who have no shame about failure. I’m being really serious. You know when you meet that character who literally doesn’t have the capacity to feel shame for their inability to do a thing that they’ve never done before? I don’t know, you see somebody who’s picked up a tennis racket for the first time and clearly can’t do anything useful with it, whatever it may be. Just imagine almost any scenario. But they are absolutely happy to do it in front of other people.

I know for me that’s not a gift I possess. I could be racked with sort of, oh, shame and all sorts of other things because I haven’t managed to achieve this level of competency out of the gate. And when I see people doing that, you know, failing willingly in front of other people, I’m always, always thinking, I really should be more like that.

Because I’m glancing around thinking, where are the people that are pouring scorn on them? And the answer is, they’re never anywhere to be seen. There’s nobody, generally speaking, looking and going, look at you. You messed up with the tennis racket. No, there’s just people looking going, oh, hang on a minute. No, what you need to do is this.

[00:22:58] Amy: Right, try this technique and.

[00:22:59] Nathan Wrigley: Right, people around to support. And yet I seem to have, that is a thing in me which I suspect I’ll take to my grave, to my great cost. So well done for being that characteristic.

[00:23:11] Amy: Thank you. Well, I do have shame and fear of, I don’t prefer to fail in front of, for example, 54,000 people in the Core Slack channel. But I’ve done it so many times at this point, I’m like, yeah, I’m going to. I’m going to. I’m going to learn and I’m going to do better next time.

Also in, way back in the day had a brief stint with performing. I was in a theater group, and one of the things that I learned in that theater group, and it really, really stuck with me, is that when you have an audience, the audience is rooting for you. They want you to win. They want you to succeed. They want to hear what you have to say. They want to see you do your whatever it is you’re there to do.

And so when you think about it, I have horrible stage fright, so this doesn’t fix my stage fright but it does kind of fix the mentality of like being embarrassed potentially, or being afraid of failing in front of people. But you go into a room to lead a meeting, or to do whatever it is that you’re doing and you are going to be nervous, but it’s inevitable that you’re going to mess up because you’re human. And to look at it in the way that like, I’m going to mess up and everyone’s on this journey with me and they support me and they want me to win, you know? We’ll fix it together, we’ll learn together, we’ll.

[00:24:23] Nathan Wrigley: We need more of that. Don’t know how many times I’ve preached that gospel to my own children, only to not be able to actually carry it on myself.

I’m going to pivot us slightly. I’m going to sort of draw us into the WordPress space because it’s a WordPress podcast after all. You found yourself in some fairly, I don’t know, important decision-making processes, sort of like contributing to Core and what have you. Can you just chart the journey for that? Like, how did you get to the point where you were contributing your own, presumably free time in some cases? Maybe it was on the company dollar, you know, maybe you were sponsored to do that. I think you implied earlier that that was the case. How did you end up picking WordPress and whichever team that you’ve spent most of your time in? Just chart that journey for us.

[00:25:04] Amy: So that leads us back to DreamHost. DreamHost back in the late, around 2017, DreamHost was, they’re a regular web host, and they were putting in a concerted effort to become a WordPress, a quote unquote, WordPress host. So they were looking into contributing and actively contributing to the project, you know, looking for more PR and marketing opportunities and being a sponsor, so on and so forth. And the hosting team, which has been my main team, was born directly of that.

The hosting team was originally a, primarily DreamHost / wordpress.org project. There have been many other hosts that have been involved. But primarily, at the very beginning, it was spearheaded dramatically by DreamHost and wordpress.org. And so DreamHost was telling its employees, hey guys, we want to be a WordPress host. Hop into WordPress Slack and go to meetings and, like, represent. So they weren’t offering to like any special contribution contracts or anything like that. They were just encouraging people to check it out and get involved in whatever capacity they felt inclined to.

And so I did. I hopped in the hosting channel. I went to a hosting meeting, and I wasn’t expecting this because I didn’t know at the time. I know now. So the hosting team originally was trying to do video meetings. The first meeting I went to was a video meeting, and I knew everyone in the room already. It was a bunch of DreamHost people, but there were also people from other web hosts who I knew from, you know, mutual contacts. So I knew everybody in the room already in one way or another, and so it was a very, very soft landing for me.

It was easy to get involved because I had an in with all those people and with the team reps. Kira Schroder was one of the team reps. It also helps when the people in the project are really friendly and welcoming. And that has been my experience, that the other contributors, the team reps, and the team leads are very welcoming. Might be a different story on the development end. But in terms of just being involved with community and team happenings, usually you’ll get a very warm welcome.

And certainly the hosting team, if anybody wants to hop in and contribute to the hosting team or participate as a team rep, we’re going to be very welcoming. We’re going to want you to come. We’re going to be encouraging. We’re going to help guide you. We’re going to be super patient and we expect confusion, questions, stupid questions, mistakes, and so forth because that’s just how it goes. And so having someone on the other end receiving you really can make all the difference.

So the contributors that are listening today that can receive new contributors, be as warm and welcoming as you possibly can be. And it does kind of take a lot of extra effort to guide people, but I think it’s worth it, and you build relationships and strong ties along the way. And you never know what that person can do and what they will do and how that later on benefits you.

So I got a really warm welcome. The hosting team didn’t even exist until I think it was 2017. 2018 I joined and started contributing. I became a team rep in 2019. And a lot of that is because I’m really outgoing, and I just was like blah, blah, blah-ing in the meetings all the time. And so that also makes me visible. In a remote, a fully remote space, I’m actually less chatty in person, although I think people would probably argue with that.

But it really, really helps to be outgoing and to jump in, like throw yourself in the fire. Throw yourself in the fire because you may or may not be thrown into the fire by someone else. It’s a really good way to learn. It’s very intimidating. I actually, I prefer more hand-holding onboarding than being thrown into the fire. But you can throw yourself into the fire in a gentle capacity. Like, hey, I volunteer to take team meeting notes, or volunteer to update some documentation. These are really kind of low-pressure things that you just need to know English, and how to type to do it. And, you know, it starts the ties between people and your presence in the project and so forth.

So I was really just hosting team for a very long time. At some point, I think it was, I joined Ladies of WordPress, I think the Slack community is, which is just like women who are involved in, women contributors basically, and befriended a couple people in that space. And one of those people I befriended was Francesca, or Francina is her Slack name, who is a Core contributor. I branched out and started going to Core meetings, like waving in at the new contributor meetings and so forth. I wasn’t quite as chatty in there because at the time it was like 30,000 people, which is a lot of people still. Now I think it’s 54,000 people in that channel.

So Francesca roped me in to, and I volunteered. You know, being not shy is really, really the key in this scenario. Being not shy led me to befriend people who then roped me into these projects, and I started contributing to Core, running release model working group meetings to kind of examine and improve the release process. And then at some point, so before every release, there’s a call for volunteers. And anyone can volunteer, you just need a wordpress.org account. Anyone can. And then of those volunteers, they form the release squad.

So I started volunteering. 5.6 is the first Core release that I was involved in. I was also working at InMotion Hosting at the time as a web development lead. And so I was working really, really, really long days. So I wasn’t quite as engaged in that release as I would have liked to been, or as I was with 6.9 and 7.0. But it was a good like backend release squad experience. And I learned a lot and made connections.

And the other contributors are really, really supportive. If you ask them for help, they’re going to help. And if they think you need help, they’ll offer to help even if you don’t ask. And so it’s kind of, there is some competition, and there is some criticism that happens, but for the most part everybody is really, really, really supportive.

So how I ended up being sponsored though, so I was joining from DreamHost on the clock. I was pretty much always working when I worked at DreamHost. I was working like these insane, like, 50, 60, 70 hour weeks. So I was pretty much always working. So I was joining on the clock. I was wearing many hats with them, and that was one of them. So I was not officially sponsored by them, but I do credit them as a past sponsor because of obvious reasons.

And thereafter I became a tech lead at a web dev agency called Canopy Studios. And they market themselves as being an open source contributor. They contribute to WordPress and they contribute to Drupal. And so they’re looking for their employees to be contributors, and they set aside three hours per week to contribute to your project. So they were sponsoring me for three hours per week. At the time I was doing way more than three hours per week. I was doing meetups, I was helping with WordCamp LA, I was helping with the Release Model Working Group, and I was a Hosting Team rep, and I was speaking at Camps.

So it’s a lot. It was really, like way more than three hours a week. But they, because of that sponsorship it kept me inclined to continue engaging with the project. And then InMotion Hosting had never officially sponsored a contributor, but one of my fellow hosting team reps was a developer at InMotion. That’s how I kind of ended up there. And so they were familiar, obviously they’re familiar with the WordPress project, and they’re familiar with contributing. I just straight up asked them if they would be willing to sponsor me. I was just like, hey, I do this thing. You guys want to use this thing for your marketing and PR, and how about you officially sponsor me? So they sponsored me for 10 hours a week. But again, I was working really, really long days, and I wasn’t able to fully dedicate myself to it as much as I would like to.

Also, that was around pandemic time. So the pandemic definitely affected my ability and everybody’s ability to contribute and engage. And then after that, I didn’t have a sponsor. I kept contributing because it was kind of like part of my thing. The Hosting Team had become special to me, and I guess that the element of me getting hyperfocused is probably key also to why I might contribute for free. Because I like will get involved in something, and then it becomes important to me, and I’m focused on it, and I’m going to carry it probably, hopefully carry it through whether I’m paid or not.

So I wasn’t sponsored for a while there. And then in 2023, I did a talk at WordCamp Europe. So I have family that lives in Israel. My brother lives in Israel. That context is important for this story. But WordCamp Europe that year was in Greece. I had been to Greece before. I love Greece. It’s like one of my favorite places. I’m going buy a house on an island there someday. But Greece is really close to Israel, so after WordCamp Europe, I went to Israel and visited my family.

Before WordCamp Europe, I had done some podcasts and written some articles, and in those conversations, at some point it was brought up that I’m Jewish, and Jewish American, obviously. And I don’t know any other contributors that are Jewish. At that time, zero. I didn’t know a single one. I thought there weren’t any. And Jews are a world minority, so there aren’t that many that I know of, but there are a few.

So somebody directed me to Miriam, Miriam Schwab, who is, I didn’t even care who she was. I was like, yay, I get to make a new friend. But she’s the community manager for Elementor. And so I contacted Miriam trying to make a new friend. I was like, yay, another Jewish person that I could be friends with that contributes to WordPress. Little did I, I didn’t even, like I knew what her job role was, but it never occurred to me that Elementor might want to sponsor me, or that they’re looking for contributors to sponsor or anything like that.

And so she invited me when I was in Israel to go to their headquarters, you know, meet their CEO, be shown around, meet other staff members, play on their, in their little old school arcade and so forth. And I was there like, yay, I’m making new friends. Totally naive completely to the fact that there was any professional interest whatsoever, which was silly. I was just so excited to make a new friend, or multiple new friends. And so then Miriam started talking to me about sponsoring me, and that’s how I ended up being sponsored by Elementor. So really kind of what you said, like a very unintentional chain of events that sort of just ended up working out the way it did.

[00:35:47] Nathan Wrigley: Yeah, looking back, there’s a thread there, isn’t there? But it’s only with the benefit of hindsight looking back that you can probably see the thread. On a day-to-day basis, it probably doesn’t quite feel like that. Are you currently sponsored by Elementor? Are you, in fact, are you sponsored by anybody currently? Yeah, okay.

[00:36:00] Amy: I am. So I’m sponsored part-time, 10 hours a week by Elementor. And again, I’ve been spending way more than 10 hours per week. So if anyone wants to sponsor me on top of them, please contact me.

[00:36:10] Nathan Wrigley: Can I ask about that though. Why? I mean the question is probably obvious to you, but I don’t know on what level you’ve inspected that part of you. Obviously there’s a why. You’ve alluded to it. You know, there’s friendship there and there’s habit, and you’ve been accustomed to it and, you know, you like being in that community, and the people there are nice.

But just sort of drawing the veil back a little bit more. Why do you give more time than your allocation, let’s say, from Elementor? Why does the 10 hours not stop on the clock like you would do for a regular job? You know, 5 o’clock winds along and exactly 5 o’clock you put your tools down, and you go off, and you go home, and what have you. What do you get out of it? What’s the thing that is satisfied by this?

[00:36:49] Amy: Well, so it’s part personal and part professional. So I tend to not draw clear boundaries when it comes to work. I tend to like, if my shift is over, but the task isn’t complete, I will finish that task. Depending on, you know, details and so forth. So I guess there’s a bit of a level of dedication that maybe doesn’t even need to be there, but that’s fueled me in a lot of ways.

Why do I contribute to wordpress.org specifically, even if I’m not paid? I do find it personally meaningful. Working with other people, making new friends, contributing to something bigger than me, participating in something bigger than me, giving to the world in one way or another, I find that personally meaningful. And it’s kind of kept my life a little bit more full and more rich over the past eight, nine years. And so it brings value to me in that way.

I have friends of a decade now from, you know, engaging with WordPress. It’s led me to jobs, and it’s led me to other opportunities and to meet really interesting people. And so there is a personal element to that for me personally. And I think that probably a lot of people also, maybe if somebody is more of an introvert, they might not have that same level of benefit that I, as not an introvert, have. Because I get a, the personal connection benefit and the meeting people is really rewarding to me.

But there’s also a lot of professional benefit being a team lead. We don’t say team lead, we say team rep, but it is a leadership position. So leading a team for a major software project has been pretty beneficial to getting jobs, getting opportunities, and just kind of a general professional portfolio. The Hosting Team is a bit of a red-headed stepchild and is kind of like quiet and nobody really knows that it exists. Except for maybe recently because of me talking about it. And it has been for a long time.

It started to blow up a lot, like way back in 2020-ish, 2019, 2020. And the pandemic kind of really threw a wrench in that. And then some other things over the years have also thrown wrenches in that. There was the whole hosting page debacle, and rift between .org and web hosts, that’s still currently affecting. So the Hosting Team is pretty, pretty quiet. It’s not like a big, Core is not quiet, Hosting Team is really quiet.

So that makes it easier to engage. But there’s definitely professional benefit that a lot of my jobs have been because of WordPress, or because of someone I met through WordPress, or my experience with contributing to WordPress just boosts my appeal to employers. So there’s that too.

And on top of that, you build skills. You know, I now have multiple repos that I’ve been a maintainer for, for years. And I had those skills to begin with, but you refine and define your skills more through experience and through working on teams and so forth.

[00:40:03] Nathan Wrigley: Do you know, it’s really interesting the order in which you stack those answers. I feel, I could be entirely wrong about this. I feel like in the corporate world where everything is out and out profit, imagine, I don’t know, evilcorp.com or whatever it may be. I feel like the calculation there might be exactly the opposite. You know, you put them the other way round. You get the skills, which allow you to then advance your career, and the meaningful bit is just maybe there, maybe not.

But the way that you stack that with the meaningful coming first is really interesting because I have that suspicion as well that the majority of the people in the WordPress project, if they were to truly ask themselves that same question, would probably arrive at a similar answer. That meaningfulness bit, it often doesn’t get talked about. It’s just kind of, oh, we all understand, we’re here, we’re having a nice time and what have you.

But that meaningful bit, I can’t put my hands on it. I can’t explain what that is, but that’s the same for me. There is something significant and meaningful about being involved in something, like you said, bigger than you, that has the capacity to improve people’s lives. And you don’t often get the chance to elucidate that thought and say it out loud. But when you do, it’s nice to know that that’s a part of your character, I think. That that that bit matters apparently more any other bit, because that’s the bit that tumbled out of your mouth first of all.

[00:41:26] Amy: Actually way more. Honestly way more than it because I am smart, I’ve taken many IQ tests. I might do and say stupid things, but nonetheless I have a high IQ, and very capable, and I have numerous different talents. I could do any variety of things. I think that if I were to be dropped in any work environment, I would excel, or at least be competent in that work environment. It doesn’t quite matter what it is. That’s, you know, my perception of myself, and I’m also a huge advocate of learning on the job. I think that companies should be hiring people who don’t know what they’re doing, and then teaching them what to do. That’s personally my take on it.

And so the meaningfulness is, it’s way more powerful than, I could make money and I could, obviously we all have to survive, but it kind of all folds into itself. That you get involved in something because it’s meaningful, and then you like learn and build skills and make connections and end up making money from it.

If people come to WordPress trying to make money, I think that you can absolutely, and probably a lot of it, but it’s the wrong values. It’s not a match for open source values and for WordPress values. And the WordPress values are one of the, probably the thing that attracts me to the WordPress open source project the most.

[00:42:52] Nathan Wrigley: Right. And I think me too. I think that was what drew me in the first place. But again, I can’t get my hands around it. I can’t sum it up. But there is a there there. There is a thing. There’s this ephemeral, non, you know, you can’t quite make contact with it, but there’s a certain feeling.

When you go to these events and you see that, you know, this whole thing has been put on by a bunch of volunteers, and the underlying code, which is what we’re all there for anyway, that equally has been largely created by a bunch of volunteers.

Where’s the profit motive for that? Well in many cases, there isn’t much of a profit motive obviously, as you said, for some people there is. That is a curious characteristic. I don’t know, there’s just something about those people that I would like to be in proximity to. Finding it very hard to describe what I’m saying, but there is something about that characteristic that I like to be in proximity to. That’s kind of it, I think.

[00:43:42] Amy: It’s very authentic and genuine. You can feel it as a human being. You can feel it when somebody wants something from you, or maybe I can’t. But most people can feel it, if somebody wants something from you, and that’s their intention. Versus if someone’s interested in you, or compelled towards you for some subconscious or other underlying reason that they’re just like, oh, you seem nice. You seem interesting. You touched on this topic and I like that topic, you know? There’s something very rewarding, and deeply fulfilling, on a human, spiritual. It covers our basic needs as humans for interaction and for community.

And I think that at events it’s even stronger. Like in Slack, you’re all in different locations. There’s definitely, you know, social interaction happening, and friendships being formed, and bonds being built. But at events it’s kind of like that on steroids. There’s a really strong sense of community, really strong sense of belonging together, a really strong sense of doing something meaningful, and contributing to something meaningful, and being part of something meaningful. And I think that’s really powerful. And it satisfies a core human need.

[00:44:54] Nathan Wrigley: Yeah, that is so interesting. I’d love to put a survey together and actually ask intelligent questions which drill down specifically into that. Because I think there would be a correlation between the things that you’ve just described, the characteristics that you’ve described, the feelings that you like to be associated with, the events that you enjoy and what have you. I think there’s a correlation between that and the community that we have. I can’t quite prove it.

But time and again, that intuition has proved itself in the real world. You know, you get into conversations like this, and this kind of subject emerges. Why do you do it? Because it’s meaningful. Because I get a great sense of satisfaction from it, and I know that I’m doing something which will be bigger than me, longer living than me, and so on and so forth. So, gosh, that’s really interesting. I’m glad that you share that same opinion.

[00:45:38] Amy: It’s beautiful.

[00:45:39] Nathan Wrigley: Yeah. Yeah it is, isn’t it? And that’s the basis upon which the whole project is built.

[00:45:44] Amy: Right. Without the community there’s, it would be a much different thing.

[00:45:48] Nathan Wrigley: Yeah, really so. Sadly, we’re going to have to end it because of the time constraints that we’ve got. But what a fascinating, I think we were just peeling back something really interesting there, but there we go. That’s the time that is allowed for this particular episode.

So anything that you wanted to get out that you didn’t get a chance to? Is there any intelligent question that you wish I had asked you?

[00:46:06] Amy: No, not at all. Thank you so much for inviting me. I’ve really enjoyed chatting with you, and I found it very interesting.

[00:46:13] Nathan Wrigley: Yeah, thank you. It’s been a pleasure. Thank you so much. This will go out on the wptavern.com podcast, the Jukebox podcast, so if you want to go and check it out over there, wptavern.com.

So all that it remains for me to do is say thank you very much, Amy Kamala, for chatting to me today. Really appreciate it

[00:46:30] Amy: Likewise. Thank you too, and thank you to all your listeners.

On the podcast today we have Amy Kamala.

Amy’s journey into tech is anything but conventional, starting with a Master of Fine Arts from UCLA and a passion for art that eventually bled into, and was overtaken by, technology. Since 2018 she’s been an active contributor to WordPress, serving multiple terms, such as the Hosting and Core teams. Her career zigzags through key roles at DreamHost, InMotion Hosting, Pantheon, Canopy Studios, and local government, picking up everything from technical support and web development to managing teams of designers and DevOps staff. Along the way, Amy has organised WordCamps, led teams, and is currently being sponsored by Elementor for her open source work.

Today’s conversation gets into the chaotic, creative overlap between art and tech, and how those different mindsets can feed one another, especially in the world of WordPress. We talk about the blend of creative and logical thinking needed in web development, and why skills like user experience, curiosity, and even willingness to fail publicly can set you apart.

We then turn to contribution. What draws people to volunteer in an open source community, what Amy gets out of participating far beyond her paid hours, and the messy journey from being an eager helper to an essential part of the team. She explains the unique feeling of the WordPress community, the importance of being welcoming to new contributors, and why being outgoing, and not afraid to ask questions, can be your biggest asset.

If you’ve ever wondered about the blurred lines between art and code, why people throw themselves into volunteer work in the WordPress ecosystem, or what’s really at the heart of this global community, this episode is for you.

Useful links

 Jonathan Desrosiers

DreamHost

InMotion Hosting

Pantheon

Miriam Schwab

Elementor

💾

#228 – Priscilla Collado Ramirez on Reducing WordPress Beginner Anxiety

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the themes, the blocks, and in this case, reducing WordPress beginner anxiety in a multitude of ways.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.

So on the podcast today we have Priscilla Collado Ramirez. Priscilla travelled 14 hours from Costa Rica to attend WordCamp Europe, making her one of the furthest attendees at the event, and for good reason. She’s an educator, fashion designer and wellness coach, and has a unique perspective on a challenge many in the WordPress community face, how overwhelming WordPress can be for beginners.

Having once quit WordPress 17 years ago, due to information overload, and a lack of community support, Priscilla’s story comes full circle, as she now dedicates herself to helping entrepreneurs and creatives find their way in the WordPress ecosystem. Her work focuses on demystifying those first confusing moments, offering practical steps, and much needed reassurance for anyone who’s ever opened a fresh install and wondered, what on earth do I do next?

The conversation is focused on why newcomers often feel stuck, paralysed by too many choices, the classic it depends advice, and a fear of breaking something or everything. We get into the importance of understanding individual learning styles, whether linear or spiral, as Priscilla labels them, and meeting students where they are, sometimes with literal breathing exercises and wellness techniques to lower stress and unlock real learning.

Priscilla explains how confidence in WordPress is built through action, and why celebrating small wins, like successfully installing a single plugin, is essential. She also shares her approach to bringing holistic, calm, and patient mentorship into WordPress education, something that’s as relevant for agency leads as it is for first time bloggers.

If you’ve ever felt overwhelmed by WordPress’ infinite possibilities, struggled to find your place in its community, or just want practical wisdom on making the path easier for beginners, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Priscilla Collado or Ramirez.

I am joined on the podcast by Priscilla Collado Ramirez. Although I know that’s not the correct way to say it, would you please say your name for me?

[00:03:44] Priscilla Collado Ramirez: It’s good, it’s good. I’m Priscilla Collado Ramirez, and I’m from Costa Rica.

[00:03:48] Nathan Wrigley: Well, I appreciate it. Thank you. You get the award without a doubt coming the furthest, I think, to WordCamp Europe this year. I don’t know how many miles it is, but you said, I think it was 13 hours.

[00:03:59] Priscilla Collado Ramirez: Yeah, 14 hours on the plane. Today is travelling. But it’s all worth it, because this country in Europe, it’s beautiful. So I can do it all the years, all the months. Yeah, I can do it.

[00:04:13] Nathan Wrigley: I have to ask though, why come all the way across, so many hours on a plane and what have you. Do you have a community where you are? Is there a thriving kind of Costa Rican WordPress scene? I don’t know anything about it.

[00:04:28] Priscilla Collado Ramirez: Okay. Yeah, in Costa Rica is a big community. It’s the biggest community in whole Latin America, in Costa Rica. I have a friend, she works for GreenGeeks web hosting, so she empowered me to do this. And the WordCamp Europe, because being a speaker is one of my dreams come true.

I already do it in my country, but I want to get more knowledge and know more people. And when she told me about this, I said, yeah, I can do it. Yeah, I want to do it.

[00:05:06] Nathan Wrigley: That is remarkable. A 13 hour plane journey. That’s pretty impressive. And I confess, I didn’t know that Costa Rica was sort of the place to be if you’re in South America. But now I do. Thank you. And I know that you’ve basically just come out of the presentation room, you’ve just finished the subject that you were talking about.

And the subject that you were talking about is really interesting to me at least, because this casts me back. I’ve been in the WordPress space since about, I don’t know, 2015, something like that. So I’ve got a few years under my belt.

But I do remember at the time when I began using WordPress, turning up to events like this and feeling a bit like a fish out of water, not really knowing what to do. Not really knowing what to do with the software, either. Not really knowing what I should install, whether I should install anything, whether I was using the best thing, or the worst thing or what have you. And that kind of was the nature of your subject.

But rather than me telling everybody what you were talking about, do you just want to summarise what it was that you stood up and presented about?

[00:06:02] Priscilla Collado Ramirez: Yeah, of course. And I feel the same way that you.

Well, my talk is about why WordPress feels overwhelming for beginners. I was that beginner that I don’t want to install. And WordPress, it’s great, but sometimes gives you too many options, right? So for beginners, sometimes that options feels paralysing because we need to start with one at the time.

I saw all the topics for this event, and I think, yeah, maybe I can share a little bit of my story with WordPress. And I talk about, I quit WordPress 17 years ago.

[00:06:47] Nathan Wrigley: You quit it?

[00:06:48] Priscilla Collado Ramirez: Yeah. I’m a quitter.

[00:06:50] Nathan Wrigley: My story going back, oh, 12 years or whatever it was, that’s nothing. You got 17 years. That was when you quit. Okay, carry on. Sorry.

[00:06:58] Priscilla Collado Ramirez: Yeah, no, 17 years ago, I was at university, and I was studying advertising and web design. I saw the options, too many options, too many things, I don’t know. And I feel overwhelmed. And I said, this is not for me. I’m so dumb. I’m slow. No, no.

And 17 years later, I’m here as an educator, and I help entrepreneurs and beginners to understand the WordPress environment.

[00:07:29] Nathan Wrigley: What brought you back then? After all that period of time away, what was the catalyst that brought you back? Why did you explore it again?

[00:07:36] Priscilla Collado Ramirez: Because I have a fashion school, and I saw my students deal with web designers and sometimes they charging so much money. I see it in the beginners, in my students, I saw that we have a problem with understanding that sometimes the things are not too difficult. We can learn about new tools and new WordPress.

[00:08:06] Nathan Wrigley: Okay, so this was all about your students then. So this was an idea of, I guess the world is kind of an expensive place to be, and one expense that you can get rid of is the cost of your website. There’s tools out there. You can, if you wish to, build it yourself. And then you found WordPress again. How is it the second time? Did you ever go through, I’m going to quit it for a second time, or was it better the next time you came across it?

[00:08:29] Priscilla Collado Ramirez: Yeah, and my brother is an engineer and I’m in like a category of non-technical people because I’m a fashion designer. I’m an educator, and I’m a wellness coach. And I think, yeah, maybe I can study a little bit, and if I use my education tools to understand how the brains for the creative people works and try to, out of the box, that sometimes the engineers have, and the creative people. It’s like a disorder, a disorder brain. I can help to these people to understand this environment in this community. And they can do it like I do.

[00:09:22] Nathan Wrigley: Yeah. So we’ll get into the bits that you think are problematic with beginning with WordPress in a minute. But just going back to your students and what have you. How’s it been for them? When you are looking at what they’re able to do, has it been a road of success, or has there been quite a lot of failure for them? Basically sum up how your students have coped.

[00:09:43] Priscilla Collado Ramirez: Okay. I don’t know, there’s two types of students, right? So we have the students that have a linear path learning. Some students learned like A, B, and C. Okay, you understand things easily. But some of them don’t understand the things like that.

So I try to create a platform, or we can call it like a type of education, and helps to understand, first how their brain works, and later understand the type of learning that I can teach.

[00:10:24] Nathan Wrigley: Okay, let me just make sure I understood that. So you try to figure out what their brain accepts most readily? And then once you figure that bit out, then you begin the WordPress education from there. Okay, that’s interesting.

And you say there’s kind of two types that you’ve kind of determined. And what are those two types?

[00:10:40] Priscilla Collado Ramirez: Lineal.

[00:10:41] Nathan Wrigley: Oh, so I think probably linear, like straight lines.

[00:10:46] Priscilla Collado Ramirez: Yeah, we have the straight lines and the spiral.

[00:10:49] Nathan Wrigley: Okay, yeah.

[00:10:51] Priscilla Collado Ramirez: So my mind is on the spiral. And that’s why I feel dumb in these technical environments. But I learned that if you learn some topic at the time and without the stress, you can do it and you can follow this community.

[00:11:10] Nathan Wrigley: So you just used an interesting word there. You said that you have felt, maybe you don’t feel it here, I don’t know if you do or not. But you said you’ve felt dumb in the past. You know, you’ve turned up to the events and you felt like a fish out of water, we might say that. Just. What the heck am I doing here? Where do I fit into this jigsaw puzzle?

And obviously you felt it long and hard enough that, firstly you left, and then come back, given it a second shot. So what are the things that you have felt dumb about? What are the things that have perplexed you in the past? What are the things that have drawn you to making this presentation?

[00:11:47] Priscilla Collado Ramirez: I felt in that time overwhelmed for the too many options. I feel that in that time in my country, WordPress wasn’t so popular and was a men’s environment. There’s no women. So I feel like, I don’t know, I’m not from, I don’t know what to be here. And now, four years ago, I’ve been talking with the women community on WordPress and I feel like, I don’t know, confident and they believe in my knowledge.

And I think that, yeah, I can do it again. I can approach to the community and I can learn, and I can be like a mentor too, and help beginners to understand that it’s not the technical environment. It’s how the community engage with your goals and can be used, and how can help with your goals.

[00:12:50] Nathan Wrigley: So I’m just going to dig into something you said a moment ago, which was about the community where you are. I don’t know if it’s still the same, but you implied that it was mostly men.

Have you found female WordPressers where you are? Or have you had to get on Zoom calls or something like that in order to find that community? Or has it grown so that it’s not just men where you are now?

[00:13:14] Priscilla Collado Ramirez: Yeah. I assist to the first women speakers in 2023. And I saw like, okay, this is a WordPress group for women. And that group was for speakers from WordPress, but women. So I was like, okay, WordPress is not only men’s, WordPress is not only technical people. And, well, I can approach to that community. 17 years ago wasn’t like that.

All men and square men. Because I know there is a lot of spiral men, but in that age, yeah, was like square men and my brother is a little bit like a square. And I was like, no, I’m funny and I want to talk, and I want to be a speaker and what. Now I feel that I can approach to my goals with WordPress because I changed my mind and my feeling about the community and WordPress.

[00:14:20] Nathan Wrigley: So just moving away from the community side and all of that kind of stuff, just dealing with the, actual software that you download from the internet and you put on a server somewhere, and then you begin to build a website. I presume that that’s part of this as well, that it’s difficult to begin because when you install a version of WordPress, you’re kind of left to your own. You know, there’s not really much in the way of assistance. You have to find the assistance somewhere. You have to a YouTube channel or some friendly person that will stand over your shoulder and help you out.

What are the sort of impediments, the problems that you think we have for people beginning with WordPress that you would like to be solved?

[00:14:58] Priscilla Collado Ramirez: Yeah. First of all that everybody thinks that WordPress is only a website. And I want to share this. WordPress is not only a website, right? It is a community. And you can approach and say, I wanted to learn about how to do a blog and how to do a website. But the community is more than that. I think that people don’t understand yet that what is WordPress?

[00:15:30] Nathan Wrigley: Yeah. well I went for, I probably used WordPress for four years, maybe three and a half, four years, something like that, before I knew there was any kind of community. I mean I realised that there was something because the software got made. So I realised somewhere behind the curtain, there must be people doing this. And I’m getting it for free, so they probably are not getting paid mostly to do it.

But I didn’t attend because I didn’t know there was anything to attend. And then I showed up to an event in London, which was probably my closest larger event at that time. I was quite surprised. I was thinking, okay, so there were about 600 people there, I really wasn’t expecting that. I thought maybe there’ll be like 12 or 15 or something. Showed up, 600 people. And for me that was kind of the moment WordPress became a little bit more interesting, because I realised that, okay, it isn’t just pixels on pages, it’s not just the websites. There’s actually a whole community of people behind it.

And one of the things that I discovered fairly quickly was that those people shared, there was a lot of overlap between them and me. You know, just a lot of things in their lives seemed to sync with a lot of things in my life. We had broad agreement on a lot of things. We all wanted the project to be successful. And so discovering the community, like you said, was a really important thing.

But nevertheless, I still think I would’ve carried on using it even if I hadn’t of discovered that community, because by that point I’d got over the problem of what plugins to install and how to actually use the software.

Yeah. So let’s move on to that. In terms of the actual software, so we’ve got the community, we know that exists. What are some of the problems that you’ve seen, I guess with your students, or maybe personal experience? Some of the problems with the actual software. What are some of the things that you’ve encountered?

[00:17:21] Priscilla Collado Ramirez: Yeah. I encountered that there’s too many options, and the people do not know how to install. And that’s a beginner’s questions. Why should I install plugins, themes? And for technical people it is like, okay, it depends.

[00:17:39] Nathan Wrigley: Oh always it depends.

[00:17:41] Priscilla Collado Ramirez: Always, it depends. And, for beginnings, that feels paralysing.

[00:17:45] Nathan Wrigley: Okay. That’s an interesting phrase, isn’t it? So when you mean paralysing? So we say it depends, meaning, oh, try everything. See what works. Where you are saying that in your experience, it depends means don’t do anything, we don’t know, not sure.

[00:18:00] Priscilla Collado Ramirez: Yeah. And the beginners don’t know what to do, right?

[00:18:03] Nathan Wrigley: Okay, yeah, that’s not helpful, is it, it depends, really when you say it like that?

Okay, so how do we overcome that? I don’t know what we do apart from keep saying, it depends. I guess we’ve got to try and encourage people to try this.

Okay, let me rewind a bit. So my parents, when I put the phone in their hand for the first time, the mobile phone, I had it all set up for them, you know everything was working, and I gave it to them and assumed that they would have the same approach as me. Which was, just play around with it and then you’ll figure it out.

Oh, no. No touching anything was, will I break it? Is this going to destroy it? If I press delete here, does that mean the whole thing’s going to like be, does this app going to disappear at this point?

So, I think that’s what you’re saying, is basically there’s this fear that if I install something and then I don’t need it, or I don’t like it, well then what do I do? Is it kind of that? This fear of it.

[00:18:59] Priscilla Collado Ramirez: Yeah, because you feel overwhelmed, and you feel paralysing. And you feel like, okay, there’s a learning path, right? So we have the excitement. So, yeah, I’m going to do WordPress. Then confusing. What is this? And then it is like, no, I don’t know, maybe this is not for me because there’s so many options.

I try with my students to go one step at a time, and understand, first, what is a plugin? Right? Do you need a plugin or not? Do you need a theme or not? Do you need SEO plugin or, I don’t know?

So I am trying to, first of all, work with entrepreneurs because some entrepreneurs sometimes doesn’t get it. I don’t know, what is an email? How to send an email. They are so intelligent, and so capable to learn things, but sometimes, like as educators or mentors, we have in our minds that people learn easily. And sometimes it’s not. So you have to teach like a child. And not because the people was stupid, right? It is like because that people, the learning process is different.

[00:20:30] Nathan Wrigley: Yeah, I suppose you’ve got to just get to the point where you’re comfortable. So for some people who are, I don’t know, let’s go for the word technical. Technical people who’ve got a background in using computers, they do it all day, every day. And they experiment with new things. I suppose if you put them in front of WordPress, they’re off. They’re just going to do that kind of thing. But I totally get what you mean.

So for me, technology, I will experiment and I’ll play, because I know that nothing can basically actually break. If something goes wrong, I can just delete it. So I’m thinking about apps on my phone, on my computer, and WordPress, and plugins, and themes and all of this. I fully understand that nothing will kill it. Well, hopefully nothing will kill it, and I can just remove what I don’t understand.

But then again, you pick me up and put me into a different industry, I’ll be that person. I’ll be the person that needs the baby steps, I think you said that needs the child steps, because I’m not in familiar territory. So I can’t think an example off the top of my head, but pick me up, basically put me anywhere there’s no technology, and I will feel that same anxiety. What do I do? can you check that what I’ve done is safe? Okay. Can you double check? And will you triple check just to make sure that everything is safe. And I suppose that’s what you’re saying, is just little baby steps. get people into it. And once they’ve gone through the baby steps, hopefully they can act on their own.

[00:21:54] Priscilla Collado Ramirez: This is a phrase that I been thinking too much in this talk, because it is some word that you said, and you said about confidence. And I wrote that confidence does not come before action. Confidence is built through action.

[00:22:14] Nathan Wrigley: Yeah, that’s true, isn’t it? And so everybody at some point has to go through that barrier. Some people seem to be full of confidence, regardless of what is, but there’s a lot of people who are not. And if you walk them through the baby steps I suppose, as you said, and tell them, do you need a plugin? What is a plugin? This is a plugin. How do you get a plugin to be put on your website? Can you delete a plugin? And then same thing with themes and custom code and all of those kind of things. And does that work? Do you notice that people go from like, ah, fear, to oh, this is all right.

[00:22:47] Priscilla Collado Ramirez: They think, this is not so hard that I was the, I will be. I don’t know, I have all types of students and all types of socioeconomic types. And I have students like 50 to 60 years old. And they think, no, I’m too old to think learning website, and learning design things. And I’ve been creative. The constructivist system is a strategy in education, the constructivist, and the principle idea is you learn by doing.

[00:23:27] Nathan Wrigley: Confidence through action, like you said, basically.

[00:23:29] Priscilla Collado Ramirez: Exactly, exactly. And so you can be on the learning path, making little mistakes and getting more confidence to feel safe in the learning environment.

[00:23:42] Nathan Wrigley: Are you a patient person?

[00:23:45] Priscilla Collado Ramirez: Sometimes.

[00:23:45] Nathan Wrigley: Yeah. Because when I was earlier describing my parents and the phone, there’s kind of a bit of me, which when I’ve demonstrated the same thing nine times, and every time the output of those, okay, do it this way, do it this, okay, now do this, now this. And on the 10th go, it’s still the wrong thing in the exact same way. I just wondered if there was a bit of that? If there is just some impediments which, I don’t know, some people just never get over. If WordPress is just generally too hard for some people. Or do you always pursue it and succeed? Do you always get people through, and get them to that confident stage?

[00:24:23] Priscilla Collado Ramirez: Yes. Yeah, yeah. Every day. Yeah. Like every day. And I think that the mentor and the educator has to feel love with that work, and teaching with love, first of all.

And then, understand that people doesn’t learn in the same way. I can say older people because I’m older, and you saw an older people, and you think, this is older than me, but it isn’t.

[00:24:55] Nathan Wrigley: Yeah. and some people are kind of, what, we would describe as kinesthetic learners. So they doing is the way. Some people are kind of auditory, and they hear the solution and they learn from hearing. And other people it’s visual. You know, they see the, watch a video and, oh, I’ve got that now. And I guess you’ve got to figure out which ones, how they fit in. If I show you once, you’re fine. If I show you once, well that’s not going to work. You’ve got to actually do it and copy me. And once you’ve figured out what kind of learners they are. You must have a lot of time for these people by the sounds of it.

[00:25:25] Priscilla Collado Ramirez: Yeah, of course.

[00:25:27] Nathan Wrigley: Yeah, and do you literally have an endless amount of time to educate them or do you have like a, I don’t know, you’ve got 10 hours or whatever it is and after 10 hours we’re going to get new people in? Or do you just stick with them throughout the whole journey?

[00:25:38] Priscilla Collado Ramirez: Yeah, yeah. And most beginners and most entrepreneurs isn’t that way, right? And they’re so excited to understand the process. And when I explain how the brain works, they think, oh, yeah, it’s not the system, it’s me.

[00:25:59] Nathan Wrigley: But also I can do something about it.

[00:26:00] Priscilla Collado Ramirez: Yeah.

[00:26:01] Nathan Wrigley: Yeah, okay. That’s interesting. Okay.

I’m going to give you superpowers for a minute. I’m going to say that you are in charge of WordPress entirely. It’s up to you what we do to improve this experience. What would you change? that could be the software. It could be education that you suddenly provide, you know, you would whip up many, many courses or whatever. I don’t know. I’m just curious to know what you think.

So again, superhero powers. You get to decide the future of WordPress. What little changes would you make here and there?

[00:26:32] Priscilla Collado Ramirez: I’m going a little bit too far off WordPress, and I’m going to bring wellness tools first.

[00:26:41] Nathan Wrigley: Okay. So it gets bigger.

[00:26:42] Priscilla Collado Ramirez: Yeah, it’s bigger. I’m a wellness coach first of all, and first you have to try to understand the stress, and your mind. And then you can learn. I feel like my superpower will be an educator in wellness first, because we have to manage the stress of learning.

[00:27:04] Nathan Wrigley: So you have to approach the computer, but calmly. You have to get there and arrive in an equanimous state. Nice and calm.

[00:27:14] Priscilla Collado Ramirez: Yeah, and understand that the delete button doesn’t exist. Because you are going to learn that, yeah, you can delete it, but you are going to breathe, and stay calm, and you won’t be delete anything because you, on the learning process of your mind understanding that everything is a process.

After that, I have an idea, I don’t know my superpower, I would like to do the mentor of the mentors first.

[00:27:49] Nathan Wrigley: Oh, teach the teachers.

[00:27:51] Priscilla Collado Ramirez: Yeah, yeah. Because we have mentors in WordPress, but the mentors sometimes doesn’t study at the university education, right? Is an engineer trying to teach another engineer, or an engineer teach to entrepreneur or a beginner, so their minds works different.

[00:28:14] Nathan Wrigley: Yes. I’ve encountered this in the real world. You know the educator who gets really angry with you and tuts, sort of goes tut tut, because you’re not doing what the way they would do it. It just turns out that, if you just ask me in a different way, I’ll probably figure it out.

[00:28:29] Priscilla Collado Ramirez: Yeah, exactly.

[00:28:30] Nathan Wrigley: Sorry I interrupted, carry on. So educating the educators.

[00:28:33] Priscilla Collado Ramirez: And in all the fields is the same way, because I’m a fashion designer too, but I have to learn how to be an educator, and how to try to explain some things to my students and try to get off to my mind box.

So I want to make some changes too, and add some of these tools on WordPress. I don’t know, maybe this is my superpower, like be a spiral mind.

[00:29:07] Nathan Wrigley: Yeah, yeah. But I think teaching the teachers. So I think we would use the word pedagogy for that. Meaning, how to teach basically. The science, if you like, of imparting knowledge. And maybe there is nothing like that at the moment. And if there isn’t something like that, it would be interesting to explore how different people with different minds and different approaches. Maybe your first idea of everybody approach the computer in a calm way. Maybe that gets rid of some of that problem. At least we’re approaching and we’re not getting we begin.

But I think you’re onto something there, in that I know that I don’t learn in the same way as my children do. I don’t learn in the same way as my parents do. And so having that in the background, and educating the educators so that they’re aware that those kind of things exist.

Okay, you’ve still got the superpowers. Is there anything else that you would do before I take them away?

[00:29:56] Priscilla Collado Ramirez: Okay, okay. I think that understand the brain is a supercomputer. It’s also a big topic because you can programming your mind. I would love to teach that people can programming itself. I don’t know what other superpower.

[00:30:17] Nathan Wrigley: Well that’s okay. You’ve had it for probably about five minutes now. That’s more than most people get.

So yeah. So in your experience, I know that you are obviously trying to overcome this problem, and it sounds like you get most people through it, and people manage to come out the other side and are, you know using WordPress successfully. But despite that, do you still think out there in the wider community, not where you are, do you still think that people are being turned off by the problem at the beginning of, I don’t know what to do. I think that I should be able to figure this out, but I can’t. I’m frustrated. It’s annoying me. Ah, move on, or forget the whole thing altogether.

[00:30:53] Priscilla Collado Ramirez: Okay. I give you some tools. I wrote it. Limit the choices. Yeah, because one plugin at a time. Yeah, understand one topic at a time.

[00:31:05] Nathan Wrigley: When you say that, are you, meaning, let’s say for example, that we’re getting into the, oh, I don’t know, the realm of SEO, we’ve managed to get into that subject. We know that there’s like 500 SEO plugins. Just show them one, just pick one, concentrate on that one and figure out how that works. And then maybe reveal that there’s others or something like that.

[00:31:25] Priscilla Collado Ramirez: Yeah. But sometimes, maybe I have to understand your world first, and maybe you don’t need SEO tools? Because maybe you wanted to sell, I don’t know, plants. So do you really need a SEO plugin? Yeah, maybe not. So I have to understand your business first, or your purpose first, and then I can share you one plugin for that.

[00:31:56] Nathan Wrigley: Right, so, but at the end of the day, it’s still limit it rather than the plugin overwhelm. 78,000 plugins on the repo or whatever it is. One at a time is probably for a beginner more than enough. Learn how to install it. How to uninstall it. Learn the kind of things that you can do with it, whether that’s SEO or a form plugin or whatever. Okay, it looks like you’re ready for another one, yeah.

[00:32:15] Priscilla Collado Ramirez: Yeah. I have, normalise confusion.

[00:32:19] Nathan Wrigley: Okay, so be happy with being confused and muddled up.

[00:32:23] Priscilla Collado Ramirez: Yeah, because it’s a new topic for you. So you have to understand that it is fine if you feel confusion, because your brain is adapting to that learning process.

[00:32:34] Nathan Wrigley: Yeah, we’re not good at that, are we? We’re really good at being annoyed by confusion. Confusion’s the enemy in many ways, isn’t it? But it’s really not. I mean, who can expect to learn something new and immediately understand everything? No, but we don’t allow ourselves to do that, do we? We get annoyed with confusion.

That’s a good one. I like that. Carry on, sorry.

[00:32:54] Priscilla Collado Ramirez: And celebrate the small wins. I’m doing right now. I’m realise that I have to celebrate the small wins, because sometimes we overwhelm and have too many expectations. It is one step at a time, baby steps.

[00:33:11] Nathan Wrigley: So that one is basically when something goes right. So once you’ve got over your confusion and something’s gone right, sit back, examine it. Ah, well done. Pat on the back kind of thing. Yeah, okay. That’s nice.

[00:33:22] Priscilla Collado Ramirez: Yeah. And emotional reset tools.

[00:33:26] Nathan Wrigley: Okay. You’re going to have to explain that one.

[00:33:29] Priscilla Collado Ramirez: Okay. I’m going to explain you here, because I want to explain you pretty well, and sometimes I get I stuck in the language.

Okay, when beginners get frustrated, we must do simple pauses, like breathing. The process of breathing is called pranayama. In pranayama is the art of the breathing. When we born, the first thing that I will do is breathe. And when you are crying, the people say, no, no, breathe, breathe, right? And when you are, I don’t know, when you swimming, and you.

[00:34:09] Nathan Wrigley: Drowning maybe.

[00:34:11] Priscilla Collado Ramirez: Drowning yeah, you want to breathe. So the breathing is so important.

[00:34:16] Nathan Wrigley: So this is part of the pausing thing. Just pausing, breathing, okay.

[00:34:20] Priscilla Collado Ramirez: Yeah. They also reduce the cognitive overload. And help beginners continuing learning with more clarity, that regulates the brain and the stress.

[00:34:32] Nathan Wrigley: So I don’t think I do any of those things when I’m learning. I just sort of plough on and expect myself to do really well. And when I don’t, I get miserable and annoyed. And I don’t ever think about, okay, calm down, breathe, congratulate yourself. The thing is I mostly do learning by myself. You know, I’m in a room and I watch a video or I read something, and so there’s nobody there to tell me to breathe, calm down, relax, congratulate yourself. So I’m glad these people have got you in their lives to, make all of this happen.

Sorry, carry on.

[00:35:03] Priscilla Collado Ramirez: No, no. And one of the phrases that I want to the people understand is the learning doesn’t happen in stress. It happens when the mind feels safe enough to explore.

[00:35:19] Nathan Wrigley: Yeah, well I can identify with that. That makes perfect sense, doesn’t it? When you’re uptight and worried about things, nothing sticks ever, does it? So back to calm, I suppose.

[00:35:30] Priscilla Collado Ramirez: Yeah yeah.

[00:35:31] Nathan Wrigley: Yeah, that’s all good advice. Yeah I wish I could do it.

[00:35:36] Priscilla Collado Ramirez: Yeah. And sometimes, yeah, the people feel overwhelmed with the stress first. I have too many mentors that causing me stress and, I don’t know, they don’t give me confidence in anything of I been learning.

[00:35:55] Nathan Wrigley: It sounds to me like what you are proposing. We would probably call it holistic. So it’s treating the mind, the body. They’re the first bits. If you haven’t got those intact and working for you, it doesn’t matter how many times you read that book, you’re never going to learn anything.

[00:36:12] Priscilla Collado Ramirez: But sometimes the word for holistic for technical people is like you’re a hippie.

[00:36:17] Nathan Wrigley: Well, there is a bit of that, isn’t there? I think technical people often have an approach to this kind of stuff, which is fairly dismissive, sort of at arm’s length. Because it’s not science, if you know what I mean. It doesn’t sort of come under that umbrella. I wonder how much resistance actually, if I put you in, you know, had a chat with a thousand of the people out there at the moment.

[00:36:38] Priscilla Collado Ramirez: Oh, the people go away.

[00:36:38] Nathan Wrigley: Yeah, okay. Okay. But you know it works. And everybody knows this kind of stuff works. Because if you’re calm, I suppose the difficulty would be, you’ve got to allow yourself to accept that you need to be calm, and you need to be approaching it in this kind of way. And that’s difficult. I would find that quite difficult. You know, if I came to your educational institute, if you like, if you were teaching me WordPress, there would be a bit of me at the beginning, which would be thinking, okay, just tapping the watch, and thinking when does the WordPress begin?

And you are probably saying, we need to be calm now, you know? So I guess you’re going to have to fight that fight.

[00:37:13] Priscilla Collado Ramirez: Yeah. Yeah. And last year I was a speaker in my country, and I’m talking about how manage the stress, the people that works like eight hours on the computer. You can use too many tools to release the back, the breathing. And everybody needs release the stress. Sometimes in technical environments, the people don’t engage with the holistic path because they think that.

[00:37:46] Nathan Wrigley: Yeah. I confess I’ve had years of doing that kind of stuff. Just expecting my body to be able to keep pace with whatever I’m doing, and expecting that if I sit in a chair for 12 hours, that everything’s going to be fine. I’m just going to stand up and walk away. And of course, it’s not.

Do you know, it’s really interesting, I don’t know that anybody’s doing this. Maybe you know a load of people that are carrying out this kind of a practice. But it feels like you’ve kind of, forgive me if I’ve got the wrong language here, but it feels like you’ve kind of bolted something close to meditation onto technology. Which is really curious, because I don’t know that anybody, maybe this is common where you are. I don’t know, but.

[00:38:27] Priscilla Collado Ramirez: No, it’s not. It’s not because I’m a sound therapist, and I’m a sound healer. The sound can heal you. I am trying to people understand that you can’t live like a computer. You are not a computer. You can program in your brain like a computer, but you are not a robot. And you need to stop.

[00:38:51] Nathan Wrigley: I think, we’re too attached to our devices, aren’t we? I think whenever the mobile phone came along, we finally gave up free time. And email is there 24/7. Social media’s there 24/7. Technology’s there 24/7. Yeah, breathe is basically what you’re saying.

[00:39:10] Priscilla Collado Ramirez: Yeah. And in my country, no, it is not common. It is not common and it is a little rare. And maybe in another country it is normal to finish your labour at work and meditate one minute.

[00:39:26] Nathan Wrigley: Oh no. Nobody does that where I live, no.

[00:39:30] Priscilla Collado Ramirez: I don’t know if there is any country, doesn’t do it, right?

[00:39:32] Nathan Wrigley: That would be nice. Yeah you’d probably feel really good after that.

[00:39:35] Priscilla Collado Ramirez: Maybe in China? Maybe Japan?

[00:39:38] Nathan Wrigley: Maybe where they a different approach to living. Do you want to roll your thing out? The way that you are doing this, do you want to roll that out to other people? Do you want people to kind of approach you and, I don’t know, study what you are doing, and then go off and do that kind of thing elsewhere? Is that part of why you’ve come to an event like this? To sort of preach the gospel of this idea, this way of learning?

[00:40:01] Priscilla Collado Ramirez: Yeah, yeah. I would love to. I would love the people understanding maybe, I don’t know, create me a plugin about wellness. I don’t know.

[00:40:12] Nathan Wrigley: Okay, so anybody listening to this, Priscilla wants communication with people who think they might be able to step in. I know of several people who have, let’s say things like meditation as part of their daily ritual and things. In which case, anybody who’s listening to this, where’s the best place to find you online? If people want to get in touch and talk about these wider problems, education, learning, calming down, meditation, those kind of things, where would we find you?

[00:40:37] Priscilla Collado Ramirez: On Gravatar. On WordPress page, and Instagram too.

[00:40:42] Nathan Wrigley: I think I’ve got the details of most of those, but if I don’t, I will get them from you, and I will put them on the WP Tavern website. So if you search for the episode, dear listener, with Priscilla in it, I don’t know the number of that episode just yet, but if you search for the episode with Priscilla in it, if you’ve got intuitions that you’d like to help out, go and find this episode and you can reach out. And you never know, maybe something will come of that.

So Priscilla, thank you for chatting to me today.

[00:41:07] Priscilla Collado Ramirez: Oh, thank you too. And remember to breathe.

On the podcast today we have Priscilla Collado Ramirez.

Priscilla traveled 14 hours from Costa Rica to attend WordCamp Europe, making her one of the furthest attendees at the event, and for good reason. She’s an educator, fashion designer, and wellness coach, and has a unique perspective on a challenge many in the WordPress community face: how overwhelming WordPress can be for beginners.

Having once quit WordPress 17 years ago due to information overload and lack of community support, Priscilla’s story comes full circle as she now dedicates herself to helping entrepreneurs and creatives find their way in the WordPress ecosystem. Her work focuses on demystifying those first confusing moments, offering practical steps and much-needed reassurance for anyone who’s ever opened a fresh install and wondered, “What on earth do I do next?”

The conversation is focused on why newcomers often feel stuck, paralysed by too many choices, the classic “it depends” advice, and a fear of breaking something (or everything). We get into the importance of understanding individual learning styles, whether linear or spiral (as Priscilla labels them), and meeting students where they are, sometimes with literal breathing exercises and wellness techniques to lower stress and unlock real learning.

Priscilla explains why confidence in WordPress is built through action, and why celebrating small wins, like successfully installing a single plugin, is essential. She also shares her approach to bringing holistic, calm, and patient mentorship into WordPress education, something that’s as relevant for agency leads as it is for first-time bloggers.

If you’ve ever felt overwhelmed by WordPress’s infinite possibilities, struggled to find your place in its community, or just want practical wisdom on making the path easier for beginners, this episode is for you.

Useful links

Why WordPress feels overwhelming for beginners – Priscilla’s presentation at WordCamp Europe 2026

Priscilla on WordPress.org

💾

#227 – Maciek Palmowski on Testing Secure WordPress Hosting: Does the Marketing Match Reality?

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, testing secure WordPress hosting, does the marketing match the reality?

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.

So on the podcast today we have Maciek Palmowski. Maciek is based in Poland and works at Patchstack, one of the companies in the WordPress ecosystem dedicated specifically to security. At Patchstack, Maciek collaborates with other security professionals on industry reports, bug bounty programmes, and solutions for agencies, product owners, and hosting companies aiming to secure their client sites.

I met up with Maciek at WordCamp Europe, and we discussed his presentation there. It examined the claims of secure hosting made by many WordPress hosting providers. He describes how Patchstack set out to test these claims with real world penetration testing, using 30 known plugin vulnerabilities across multiple hosts. Employing standardised methodologies and validating their results independently.

The findings are sobering. The majority of WordPress specific attacks still get through, and there’s a significant gap between the marketing hype and real protection.

The conversation starts with Maciek’s background, and how his journey in the WordPress security space led to a focus on the promises made by hosts.

From there, the discussion gets into the research approach, the selection of well-known vulnerabilities, consistent testing across different hosting environments, and the surprising result that even hosts with identical security tooling produce drastically different outcomes, showing it’s not just about the tools you use, but how you use them.

We talk about the Swiss cheese model of security, every layer will have holes, so you need multiple overlapping defences, and honest communication from hosts about their limitations.

We also explored whether an industry-wide standard, or badge, for secure hosting is feasible or even desirable, given how easy it is for strong marketing claims to outpace reality.

AI also enters the conversation, increasing both the speed and sophistication of attacks, and making patching, and processes, even more important, especially as the volume of vulnerabilities continues to rise and the time to exploitation drops.

If you’re interested in understanding what secure hosting really means, how to ask intelligent questions of providers, and the realities of WordPress security in 2026, this episode is for you.

If you’d like to find out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Maciek Palmowski.

[00:03:56] Maciek Palmowski: I am joined on the podcast by Maciek Palmowski. Hello Maciek.

Perfect. You did great.

[00:04:01] Nathan Wrigley: For some reason, your name has got into my head. A lot of the people that I interview, I struggle with their name, and I continue to struggle, but for some reason, I established many years ago that was how to say your name. And I think I’ve done it correctly ever since then.

[00:04:16] Maciek Palmowski: Yes you did. You’re almost having the typical Polish accent, so you’re doing great.

[00:04:21] Nathan Wrigley: So we are at WordCamp Europe, which is in Krakow, or Krakow, I don’t know how.

[00:04:26] Maciek Palmowski: Krakow.

[00:04:27] Nathan Wrigley: Thank you, that was good. And the reason Maciek is correcting my pronunciation is because Maciek is actually from Poland, which I suppose means that this is a bit of a, well, it’s like a home game to you.

[00:04:37] Maciek Palmowski: In a way so, but it’s also like a bit of a shame because I do like travelling when WordCamp Europe’s are happening. And, you know, just hopping on the train and going to Krakow, it was like a, I mean it’s cool because, yeah, the venue’s amazing, everything is great, but still I’m staying home, so yeah.

[00:04:53] Nathan Wrigley: Yeah, mixed feelings. So Maciek has done, or is going to do a presentation at WordCamp EU. Have you done it yet?

[00:05:02] Maciek Palmowski: I will do it tomorrow.

[00:05:04] Nathan Wrigley: Okay. And are you all set, are you one of these like really prepared people that has all the slides done, or are you last minute?

[00:05:11] Maciek Palmowski: Everything is ready. I already did one version of it at the Checkout Summit in Palermo, so.

[00:05:17] Nathan Wrigley: Oh I see. So you’ve had a sort of dry run of elsewhere.

[00:05:19] Maciek Palmowski: Of course.

[00:05:20] Nathan Wrigley: Excellent. So the presentation, which is going to be the focus of today’s conversation, is called Testing the promise, does secure hosting deliver? And I may as well read the blurb because it was a reasonably short one.

So it says, secure hosting, in quotes, is everywhere in WordPress. What does it actually protect against? We put this claim to the test with real penetration testing. 30 known vulnerabilities, multiple hosting providers, standardised methodology, validated by independent observers. The findings reveal a critical gap between marketing and reality. WordPress specific attacks succeed most of the time. That’s quite an alarming sentence. This talk shares the complete results and explains why generic security fails.

So, we’ll get into that in a moment. But as with all people, when I’m talking to them about security, I guess it’s good to establish who you are, and what your credentials are and what you’ve done, and how is it that you get to talk about security with authority. So over to you really, a little moment to give us your bio and tell us about you.

[00:06:20] Maciek Palmowski: Okay. So I work at Patchstack, and Patchstack is one of those few companies in WordPress space that are doing a lot in terms of security. We are constantly running this bug bounty for the whole ecosystem. We have quite a few solutions for both clients and hosting companies, and I work there right now. My role is, if I remember, the Growth Team Engineer, something like this.

But yeah, I do spend a lot of time working with other security people. So when we are working on all the reports, when we are checking the data, I’m also part of those teams that are working on it. So yeah, I think I know a thing or two about what is happening behind the scenes when it comes to WordPress security.

[00:07:02] Nathan Wrigley: Yeah, thank you. Always good to get that established though, right at the outset.

Patchstack is a company which is not a host though, I suppose that’s important to mention at the beginning. It’s a company which is in the security space, very much in the WordPress space, but perhaps more broad than WordPress, I’m not sure. But not a hosting company.

But obviously your presentation focuses its aim on hosting, I guess because that’s one of the places where the claim about security is most often made. You know, you’ll go to a, the landing page of hosting Company X, and you’ll see somewhere fairly near the top, secure hosting, or something along those lines. And you’ve decided to examine that in fine detail and look at these 30 vulnerabilities.

I guess really just tell us about this test and what it is that you decided to do and some of the items that came out of that.

[00:07:50] Maciek Palmowski: Okay, so maybe let’s start with how it even started, right? Because there was a trigger. At some point we published one report about the state of WordPress security. We tweeted about this. We got the response from none other than Matt Mullenweg, who kind of asked a very interesting question, but isn’t hosting companies taking care of this already?

And this was, kind of at this moment when we were, we thought that we know the answer that, no they aren’t. But to be honest, we didn’t have any broader proof about this.

We knew how it’s working at some hosting companies, but we could say that it was more of an anecdotal evidence that we had. So this was kind of the trigger that made us, okay, let’s check this. But not with one partner or two partners, but with more hosting companies.

So we did this research twice. First we just did kind of a beta run because we weren’t sure about the result and, is it even a good idea to go deeper inside of it? And during our first run, we were already very surprised because like the methodology was very simple. We just installed vulnerable plugins and we checked if we would be able to use the vulnerability. Because if the hosting is claiming that, we got your back, we are making your website secure, we have this and that, this means that they should protect against it. So it was as simple as that.

And when we were doing our first test, we were quite surprised because we saw, if I remember, that 80% of the attacks went through. 80% of the attacks. So our first reaction was, okay, we are doing something wrong. Okay, this was only few hosting companies, less plugins, but still the result were so surprising for us because we thought that, okay, that the problem exists, but it’s not that big of a problem. But it was.

So that’s why we did the second test. And this is about which the, my talk will be mostly when we tested more hosting companies, more plugins. And we saw that the problem still exists.

Of course it was, in some cases 70 few percent. So still, it’s a huge problem, especially if we are talking about some companies that are literally saying, you don’t have to install anything additional when it comes to security on your website. We got your back. They don’t. We found a lot of interesting things, but still the problem exists.

[00:10:21] Nathan Wrigley: So just deep diving into that a little bit, when tests like this are done, there’s obviously, the claim might be levelled, you know, obviously Patchstack would, this kind of maybe benefits Patchstack, if you know what I mean.

So let’s just sort of clear up what the test involved. So presumably the plugins that you chose are ones where it’s publicly known that there’s a vulnerability in this component or this particular file or what have you. So is that the case? This is stuff that, longstanding understanding that there’s a problem here.

[00:10:51] Maciek Palmowski: Yes. We only use the plugins that we had all the proof of concepts. So we know how have the vulnerability happened, what was the attack vector? They were all reported through our bug bounty programme, because that’s why we had the proof of concept. Yeah, and that’s it.

It was, like I said, it was as simple as that. We had a really broad mix of all the plugins. How many? It was 30 something of those plugins, if I remember. Different ones. Some were connected with WooCommerce. So, like a very broad selection of them. Different vulnerability types. So we try to mix it up as much as possible.

[00:11:27] Nathan Wrigley: Was the situation for each hosting company the same though? In other words, was the things that you did in one hosting environment the exact same as you did in another hosting environment? No. You mixed that up a bit as well.

[00:11:38] Maciek Palmowski: I mean we used all the same plugins, like the methodology was always the same. But we got totally different results. Even if, and this was one of the most interesting findings, because very often hostings will put a logo of some company that takes care of security. For example, say, Cloudflare. And despite using the same stack for security, they got different results.

[00:12:02] Nathan Wrigley: Interesting.

[00:12:03] Maciek Palmowski: So it turns out, in many cases, it’s not about the tools that you are using, it’s how you are using them, which was very interesting. And we did everything. We tried to enable every feature, every security features on those hosting, to kind of give them a chance to kind of make sure that they are defending the most as they can.

And the result in most cases was very simple. They were doing quite well with the generic ones like uploads, patch reversal, things like this, which are very generic in PHP. But with those WordPress specific attacks, they just failed miserably.

[00:12:44] Nathan Wrigley: That’s so interesting. The word secure hosting, which you’ll see all over the place, it feels a bit like using the word healthy on food. There’s no real definition of what healthy is. You know, a company selling chocolate could probably pretend that it’s healthy compared to something else.

[00:13:04] Maciek Palmowski: Like here, healthy chocolate is exactly, like in some cases secure hosting.

[00:13:07] Nathan Wrigley: Right. So what do you take from this then? I mean basically, is your survey saying that whenever you see the word secure hosting, be sceptical?

[00:13:16] Maciek Palmowski: Yes.

[00:13:16] Nathan Wrigley: Okay. As simple as that.

[00:13:18] Maciek Palmowski: It’s as simple as that. Because one of the things that we were always promoting, security is not a plugin, it’s not a one button thing. Security is a process. It’s layers.

And that’s kind of why we, especially after this report starting kind of using the term, Swiss cheese layer model. Because every layer will fail in some way. That’s also why you still need all the security solutions that hosting provides, because they do have a lot of interesting solutions against those generic attacks.

Because they’re doing really great when it comes to those generic ones. And that’s great because some of the attacks will be already dealt with. So whatever passes to the second layer, it has less work to do because a lot of it was already stopped at the first layer. The second layer should be something more WordPress specific that understand what is installed. And with this it can catch also a lot of it.

But still, you have to be prepared that, because again, this layer also isn’t perfect. Because there are zero days vulnerabilities, there are custom code, there are a lot of things that can happen, that your website will be hacked. I mean, weak password. Simple as that. That’s why you also need to have a layer, which will be more of what to do if everything else fails. Because you do need to know that you have to inform your clients, all the GDPR related things. How to kind of, I don’t know, use the backups.

In short you need to have procedures. You have to be prepared before the attack happens. Because let’s be honest, asking some lawyers about, what should we send to our clients? The moment when, well, the milk is already spilled. It’s like the worst moment to think about it. Especially that, hey, your website was just hacked. It’s not just a technical problem, it’s also a business problem. Again, with those GDPRs and everything.

So yeah, the more layers, the better. You still need to remember, every layer can fail in some place. That’s why the more, the better.

[00:15:29] Nathan Wrigley: Would you like to see a standard industry-wide definition of something like a badge or, I don’t know, let’s say for example, that you put the word secure hosting on your website, that has to actually stand for something.

Because obviously coming from the background that you do with a broad oversight on what that is, you have a vast amount of data at your disposal. You can see all of this kind of stuff. But every company can make the claim that our food is healthy, our hosting is secure. But I don’t know, in the model that we’ve got where any company can put anything they like on a website, I don’t really know how you do that, but some sort of accreditation or something. I don’t know.

[00:16:08] Maciek Palmowski: Honestly, it’s really difficult because as I said before, a lot of companies using the same tools were failing in different ways. So that’s a problem. On the other hand, like sometimes the, those stupid things like weak passwords. And it doesn’t matter that you had a, let’s call it a certified secure hosting, you still failed because your password was weak, you know? So, also certificates like this can backfire because some people might think I have a secure hosting, I don’t have to worry about things. And then you have 10 admin accounts for everyone.

[00:16:43] Nathan Wrigley: Is there is there something, some mark of that description that you, personally, that you go looking for though? Is there some credentialing system which you think actually does carry some weight? So for example, I don’t know, like the insurance space or the accountancy space or something like that. You have to have that accreditation in order to do business. Is there something like that? Is there a mark which hosting companies can apply for which you could have some confidence in it?

[00:17:13] Maciek Palmowski: Okay. So for sure one of those things would be, and I don’t want to say it as an advertisement, but it is a thing that you see that the hosting is thinking a bit better about security, kind of looking if they are a Patchstack partner. Because this kind of automatically means that they do have this WordPress, the security WordPress layer. So that’s already a good sign.

So yeah, I would start with this. I think that’s kind of one of the simplest ways, but again, Patchstack isn’t the only solution that does it. So looking for partners of such companies might be the best way to start because having those Patchstack aware security solutions built in, into the hosting is a really good sign.

[00:18:05] Nathan Wrigley: Yeah, okay. Now, the inevitable conversation in the year 2026 is AI. It doesn’t matter which area of WordPress you’re talking about. AI manages to get in somewhere. I am presuming that the landscape in terms of security only got more complicated because of AI. Because I’m imagining that attacks that needed to be conceived by a human can now be conceived in a fraction of the time by an AI agent. But not just one, maybe a dozen or a thousand or whatever it may be.

Let’s just talk about that for a moment. It feels almost as if AI and security are like, that’s a real systemic problem for the future of the entire industry. Because these things can happen so fast, a plugin vulnerability is discovered by an AI agent. It then discovers the attack surface, implements the attack all in a matter of seconds, possibly. What’s the position? Like, how do we stay calm basically in the year 2026?

[00:19:09] Maciek Palmowski: So the problem already existed around a year ago, because a year ago when we did our State of WordPress Security Report, we already saw that vulnerabilities are being used after around five hours after kind of being published. So five hours. That’s the first thing, because we still have a lot of people that say, yeah, just update your WordPress weekly and you’re good to go. No, you’re not. Looking at this number, you have five hours.

[00:19:39] Nathan Wrigley: Okay. Let’s just parse that at the moment. So the vulnerability is published. So there’s a whole thing there, like the vulnerability may well have been discovered prior to being published, so that’s a whole other thing.

[00:19:52] Maciek Palmowski: So first the vulnerability is discovered. Then at least how it works on, with our bug bounty. We inform the vendor they have, let’s say around a month to fix it. When they fix it, we publish everything and, yeah.

[00:20:09] Nathan Wrigley: Okay, so from the moment you publish, you can then detect that that is being leveraged within a space of five hours.

[00:20:17] Maciek Palmowski: Yes.

[00:20:17] Nathan Wrigley: Okay, that’s really interesting.

[00:20:19] Maciek Palmowski: But there is a problem. There is a really big problem. So if the vendor doesn’t respond, we still publish it.

[00:20:26] Nathan Wrigley: How long do you give them? Is it like.

[00:20:27] Maciek Palmowski: It is the one month.

[00:20:28] Nathan Wrigley: Okay, thirty days.

[00:20:30] Maciek Palmowski: Of course, if they reach out that there is some problem, they need like extra days. But in most cases, we’re talking about the vendors that just don’t respond at all. We publish it anyway.

But the problem is that, from all the vulnerabilities that were discovered last year, 50% weren’t patched at the moment of publishing about it. 50%.

[00:20:50] Nathan Wrigley: So half of the plugins where there was a known vulnerability, the vendor had been informed, they’d had this 30 day window. Half of them made no amendment to their code.

[00:21:01] Maciek Palmowski: Exactly.

[00:21:02] Nathan Wrigley: Okay. Wow, okay.

[00:21:03] Maciek Palmowski: Again, going back to this classical, yeah, just update your WordPress regularly. No.

[00:21:08] Nathan Wrigley: No, that’s a really different surface, isn’t it?

[00:21:11] Maciek Palmowski: It doesn’t work on so many levels. Because not only the problem is with the fact that, still the famous five hours, which also, it’s five hours now. It was much longer a few years ago. On the other hand, yeah, most of those, I mean around half of it aren’t patched, so the attacks will happen quicker than it get patched. So yeah, there is a lot of problems like this. And also the problem with security is that it’s really difficult to sell.

[00:21:39] Nathan Wrigley: It’s like insurance, isn’t it?

[00:21:40] Maciek Palmowski: Yeah. But insurance, okay, you see your car, your house, it’s real. It’s real, you kind of see it. The only category of websites that it’s much easier to kind of explain is e-commerce.

[00:21:54] Nathan Wrigley: Yes. You can feel the tightening on your wallet.

[00:21:56] Maciek Palmowski: They literally see the money. They can kind of really, okay, one hour of my website not working equals this and this Złotys or Euros or whatever. So that’s easier to explain. But for most people, yeah, security, meh.

[00:22:11] Nathan Wrigley: Yeah. That’s really interesting. So you mentioned, about this survey, you mentioned that fully 80% of your penetration testing resulted in something. What were the sort of, the high level items? Apart from that 80% figure. What were some of the other, because you said there were a few interesting things that dropped out of it. Can you mention anything else?

[00:22:31] Maciek Palmowski: So like I said, one of the things was that we learned that, despite using the same tools, we got different results. That was also a surprise for us.

[00:22:39] Nathan Wrigley: So let’s just figure that out. So at hosting company A, we’ve got a WordPress website with the same collection of plugins in. Hosting company B, exactly the same as far as you can make it the same, but things are different.

[00:22:52] Maciek Palmowski: No, no, they are, for example, they’re using for security the same tools.

[00:22:56] Nathan Wrigley: Right, okay.

[00:22:57] Maciek Palmowski: So in theory, if they’re using the same tools, we should have exactly the same results.

[00:23:03] Nathan Wrigley: So does that then point to a different set of configurations on the backend, or is it more curious than that? You just don’t quite know what’s going on.

[00:23:12] Maciek Palmowski: I mean because it’s not something that they will tell us. But yeah, in most cases, it’s all about configuration because the fact that you’re using a tool, it’s also important how you use a tool.

Also, with security is very often about, is something easy to use or is something secure? And kind of finding the balance. So some of the companies probably had a bit more aggressive configuration, which is better from the security point of view, but probably more often result in some annoying side effects for the user.

Also what, this was one of the most interesting things, but also what was very interesting because we contacted every company afterwards and we informed them that we did the test. Here are the results, what went through, what was blocked. And some of the companies did an amazing job of fixing whatever they could. On the other hand, we saw that some of the companies, because we did some extra tests later just to check what they did with our report, did nothing.

That’s one of the things about security in general, not about the hosting, about even having vulnerability in your plugin. That’s normal that we make mistakes. We’re humans, right? So that’s normal. What’s important is how we deal with them. If you have a problem and you fix it as quickly as possible, as good as possible, that’s great because you learn from your mistakes, you fix it, and you move on. Perfect. Good job. Now you are in a much better position than before. But if you get this, you look at it and you say, ah, this is fine, that’s the worst behaviour from the security point of view that you can have.

[00:24:57] Nathan Wrigley: I’m going to ask you not to name names here, but were some of the companies familiar to us?

[00:25:05] Maciek Palmowski: For sure, because we did test the biggest ones. But there is a reason why we didn’t want to name them, and it wasn’t about that we were afraid that I know someone will get mad or whatever. It was more about this weird side effect that could happen.

Some users would think, my hosting isn’t on this list, so probably I’m secure. Probably you’re not, you just weren’t in the test. Because we also did some site checks and everything. And we saw that a lot of those problems happen at most of the hosting companies. And like I said, the more important part was how did they reacted after getting the report. Like I said, it was a more common problem that we even thought.

[00:25:43] Nathan Wrigley: Do you, obviously, you know, caveat all of this with the fact that you work for Patchstack and what have you, do you see it even as the role of a hosting company to have any position on security publicly? Or would you prefer them not to make grand claims about things that you believe they can’t necessarily substantiate?

I don’t really know where I’m going with that question, but I’m just wondering if there’s just a sense that the language that’s being used is too strong. You know, secure hosting implies we’ve got all the padlocks, and the padlocks are there and you’ve got nothing to worry about. You’ve found a different picture. So I’m just wondering whether or not you would just prefer that the hosting companies stop talking about this altogether.

[00:26:27] Maciek Palmowski: I do think that’s, one of the biggest problem here is about the claims, the bold claims, the whole marketing around it. Sometimes even you can find documentation of some of them that, yeah, you don’t need to install any third party tool because we got you covered. We checked it, no they didn’t. So that’s kind of the problem.

It’s really more about the, how they market it. If they would say, okay, so we have a really performant hosting that does this, this and this. When it comes to security, kind of do it yourself. I mean we are providing this layer, but the rest is up to you. And that’s okay. That’s an honest claim. We are not doing everything for you. We are doing this part, but this is up to you. This would be much better.

I know that from the marketing point of view, it doesn’t sound as good as, we got all the security that you can imagine, don’t have to worry about this. Because that’s kind of the thing that very often managed hosts trying to sell, that you don’t have to worry about things. You just have to focus on whatever you have, writing content, selling stuff. If you have a e-commerce, whatever, that’s it. That’s kind of the only thing you should think of. Not about performance, because we got your back. Not about security, again, we got your back. And if you are paying for a managed hosting and suddenly they would start having like this different way of messaging to, it’s not that obvious that we have your back in everything. That would be very difficult for them.

So now it’s kind of the problem that, because everyone is kind of using this messaging, everyone else also has to. And also if we think about how a lot of those algorithms, look like that algorithms love bold claims. They want something white or black, not grey. And the truth is, most of the things we are talking about, it doesn’t matter, security, SEO performance, it’s everything in the grey zone. That’s why a lot of developers can end their talk with, yeah, it depends. There is no right or wrong. It depends because there are so many things you have to think about.

I could say that, and this is my kind of thing that, most of the websites that people have should be static. They don’t need even WordPress at all. This is a horrible claim if you’re a manager of a WordPress hosting, right? So that’s the thing. But it all depends on so many things, but yeah, the messaging is important.

[00:29:08] Nathan Wrigley: Yeah, if you were, on a personal level, if you were going out there looking and let’s say, if you can somehow put your job hat to one side, what would be the kind of things that you would be looking for? What questions would you be asking related to security if you were to be going to these companies?

From everything that you said, obviously it’s not black, it’s not white, it’s definitely grey. So every setup has some way of being vulnerable. But what are the kind of intelligent questions that you would be bringing to hosts to get some reassurance that at least they appear to know what they’re doing, even if they can’t make the claim that they’re a hundred percent cast iron, water tight? What might be some intelligent questions to start asking?

[00:29:49] Maciek Palmowski: One of the best questions you can ask is just, is there any solution in your security stack that is WordPress aware? Not the general one. Because if they only start talking about some web firewall, things like this, it’s already kind of a red flag. Because this is, overall, if we’re talking about firewalls, that’s not the correct layer about which, this is the generic one.

So this is the main question. How do you take care of WordPress specific attacks? Simple question. And if they will start responding, yeah, that we have this web application firewall that, in most cases this will be a sign that, no, we are not talking about the correct layer. That’s not it. It’s probably not aware about what is happening in WordPress.

[00:30:40] Nathan Wrigley: Okay. So given that this is a WordPress podcast, and we are at a WordPress event, that would be the beginning of your questioning is demonstrate that something in your stack is specific to WordPress.

[00:30:52] Maciek Palmowski: Exactly.

[00:30:53] Nathan Wrigley: Okay. And beyond that, is there any questions that, so let’s imagine that they come back with, yes, we have something specific, it’s WordPress. What would be sort of sensible follow up questions?

[00:31:00] Maciek Palmowski: I mean you can kind of start off about, okay, what exactly you are using? Because there is a limited amount of tools that are really WordPress aware. So if they will answer with kind of a product name, that’s kind of the easy way that then you can check it on your own. But that’s kind of the thing. Is it WordPress aware?

[00:31:19] Nathan Wrigley: Does it worry you in some way that there’s this perception out there that WordPress is insecure? You know, if you ask a thousand people, you’d maybe get 800 saying, oh WordPress, you know, we’re not touching that with a barge pole.

Do you worry that content like this, that you are putting out, that that might fuel that fire? Does it concern you in any way that it might lean into the argument that, I don’t know, somebody can link to that blog post from a rival CMS, or a SaaS platform, which does something similar to WordPress? Where do you sit on that?

[00:31:51] Maciek Palmowski: That’s a really difficult question. And this is one of the questions that when I talk on non WordPress events, I love to ask people. Is WordPress secure? And in most cases, I see that most of the room is, yes, it’s unsecure for sure. And I’m like, no, that’s not true. WordPress is secure. Every year there is just a few minor vulnerabilities in Core. That’s it. The problem is, of course, that WordPress on its own lacks some functionality. That’s why we install plugins.

And here we enter another problem because, okay, every year we have like thousands of those vulnerabilities in general in plugins. On the other hand, we have thousands of plugins. So kind of statistics will always look bad. But that’s why every time when you want to select a new plugin, you need to do some research. Yeah, I know it’s boring and everything but, hey, now we have AI, you can do it much quicker. It can help you a lot.

But looking at all those databases, for example, we have one database, WPScan has. There are those databases of WordPress vulnerabilities that occur to every plugin. And you can see, is the plugin you’re interested in had a lot of vulnerabilities? On the other hand, how it kind of looked historically. It’s not just about the number of them. In general, it requires some research.

And yeah, if we are just like looking at this, and this kind of vibe that right now we have that we are just about really bold opinions stated quickly that will fit one TikTok, yeah, WordPress is in a horrible position because, let’s be honest, it’s like, if you have, I’m not sure how many seconds does a TikTok movie has?

[00:33:39] Nathan Wrigley: I think 30.

[00:33:40] Maciek Palmowski: Okay, let’s say 30. So it will sound much better that you will say, yeah, WordPress is unsecure, which is not entirely true because it depends again. One of the most boring, especially again for those algorithms and everything, it’s a grey zone.

Because we are collaborating with a lot of companies that are making plugins, and we see how their security flow looks like. How they are dealing with vulnerabilies that are discovered. And honestly, I’m amazed how well some of those companies are doing it. They are very serious about it. They understand how important it is. For them it’s something very important.

[00:34:22] Nathan Wrigley: I suppose WordPress is a victim of its own success in that sense. And it would be a bit like, I guess a good analogy might be if you’ve got a car manufacturer and they produce a thousand cars a year and you compare them to Ford who make, let’s say, I don’t know, 20 million a year. And the question is, well, whose cars break down more often?

[00:34:41] Maciek Palmowski: Yeah. Do we look at the percentage of the number?

[00:34:44] Nathan Wrigley: Right. And if you say, well, 400,000 Fords broke down last year, and one of these other manufacturer, you can immediately see why there’s a problem there. And that I think is the landscape in which WordPress is often painted. The reason there’s lots of publications like yours bringing out WordPress information is because it’s the most popular thing. It makes sense to write about the most popular thing and to try to find the vulnerabilities and disclose them in a sensible way. So I don’t know what we do with that. It is just the way it is.

[00:35:15] Maciek Palmowski: I would also say there is one more interesting aspect because WordPress is considered unsecure because of the plugins. But what’s funny, for example, Elementor is also considered unsecure because there are plugins for Elementor. This is a very weird moment when the thing that brought WordPress to its bigger success, security wise, is its biggest problem right now.

Because WordPress did a lot of, I mean it was always great to, being as it’s kind of, let’s call it entry level CMS. For many people, it was also the way how they began the adventure with PHP development because it was so easy. Now we kind of have the, all the consequences of being that easy.

[00:36:06] Nathan Wrigley: Yeah, in a sense, this is going to sound ridiculous, we should be glad that there’s people talking about WordPress vulnerabilities, because it means the project is successful. And it also means that it’s, there’s an industry of WordPress security solutions, and there are people who take this very seriously and dedicate their lives to it. And you may not find that in some of these other ones, you know, some of the smaller CMSs and things like that.

I think we’ve probably hit about the sweet spot for the amount of time. But Maciek, I don’t know if there was anything in that report that you have got lined up in your presentation that I never got to. If there was a particular thread that you wanted to pull. If there is, go for it.

[00:36:46] Maciek Palmowski: No, I think we covered all the important things. And as you kind of said, this AI aspect, this will change so many things.

[00:36:55] Nathan Wrigley: Yeah, we’ll come back in two years and this conversation will be a very different thing.

[00:36:57] Maciek Palmowski: Oh, I think even in few months which will be very interesting. Yeah, so this aspect, it’s really very surprising. And I think that everyone who is right now kind of giving somewhere a talk about AI and security is in a very difficult spot because.

[00:37:14] Nathan Wrigley: Yeah, your content is going to look stale quickly.

[00:37:16] Maciek Palmowski: Yeah because you know it’s like, but a week ago everything changed. Yeah, I have to rewrite everything.

[00:37:20] Nathan Wrigley: Speaking of which, by the time that this goes out, hopefully you have managed to give out your presentation at WordCamp Europe. I will link to it and anything else that we’ve mentioned today in the WP Tavern post. So go and check that out. But I will specifically link to the wordpress.tv version of your presentation, which no doubt will have been created by then. So Maciek, thank you for chatting to me today. Good luck. I hope presentation goes well.

[00:37:43] Maciek Palmowski: Thank you. Thank you so much. Yes. I might need a bit because, you know, it’s WordCamp Europe. It’s a big conference.

[00:37:49] Nathan Wrigley: It is, yeah. Good luck. I hope that you manage to stay calm.

[00:37:52] Maciek Palmowski: Thank you.

On the podcast today we have Maciek Palmowski.

Maciek is based in Poland and works at Patchstack, one of the companies in the WordPress ecosystem dedicated specifically to security. At Patchstack, Maciek collaborates with other security professionals on industry reports, bug bounty programs, and solutions for agencies, product owners, and hosting companies aiming to secure their client sites.

I met up with Maciek at WordCamp Europe in Kraków, and we discussed his presentation there. It examined the claims of “secure hosting” made by many WordPress hosting providers. He describes how Patchstack set out to test these claims with real-world penetration testing, using 30 known plugin vulnerabilities across multiple hosts, employing standardised methodologies, and validating their results independently. The findings are sobering. The majority of WordPress-specific attacks still get through, and there’s a significant gap between the marketing hype and real protection.

The conversation starts with Maciek’s background and how his journey in the WordPress security space led to a focus on the promises made by hosts. From there, the discussion gets into the research approach: the selection of well-known vulnerabilities, consistent testing across different hosting environments, and the surprising result that even hosts with identical security tooling produced drastically different outcomes, showing it’s not just about what tools you use, but how you use them.

We talk about the “Swiss cheese” model of security, every layer will have holes, so you need multiple, overlapping defenses, and honest communication from hosts about their limitations. We also explored whether an industry-wide standard or badge for “secure hosting” is feasible or even desirable, given how easy it is for strong marketing claims to outpace reality.

AI also enters the conversation, increasing both the speed and sophistication of attacks, and making patching and processes even more important, especially as the volume of vulnerabilities continues to rise and the time to exploitation drops.

If you’re interested in understanding what “secure hosting” really means, how to ask intelligent questions of providers, and the realities of WordPress security in 2026, this episode is for you.

Useful links

Patchstack

 Checkout Summit

Testing the promise: does secure hosting deliver? – Maciek’s presentation at WordCamp Europe 2026. It includes the video of the presentation.

 State of WordPress Security in 2026 Report

WPScan

💾

#226 – Jessica Lyschik on Why Accessibility in WordPress Themes Is Easier Than You Think

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, why accessibility in WordPress themes is easier than you think.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.

So on the podcast today we have Jessica Lyschik. Jessica is a longtime member of the WordPress community who’s been working in the ecosystem since 2015. She’s spent years learning and advocating for web accessibility, both as a developer and as an active community participant, joining agencies, working on theme reviews, and helping improve standards.

Many theme creators assume that making themes accessible is an intimidating task, but Jessica’s here to show you that achieving an accessibility ready WordPress theme is more straightforward than you might imagine.

Her WordCamp Europe 2026 presentation, accessibility in themes, easier than you think, aimed to demystify the requirements for accessible themes. Explaining what the WordPress guidelines mean in practise, where the low hanging fruit is, and how both block and classic themes can reach accessibility ready status with manageable efforts.

We talk about the personal and moral journey that brings developers to accessibility. The technical hurdles and documentation challenges, and the ways in which things like AI agents are putting accessibility in the spotlight for everyone.

Jessica talks about practical steps that quickly improve accessibility, like using correct HTML tags, adding alternative text to images, and configuring skip to content links, and shares why building accessibility in from the start saves time and effort down the road.

We also explore the differences, and possible advantages, of block themes when it comes to accessibility, and why theme guidelines work the way they do, and the importance of interdisciplinary awareness across SEO, design, and content teams.

Jessica mentions helpful resources, influential leaders in accessibility, and the ongoing need for documentation improvements to help everyone level up.

If you’ve ever felt overwhelmed by accessibility requirements, or wonder why they matter, and how you can build better WordPress sites that work for everyone, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Jessica Lyschik.

I am joined on the podcast by Jessica Lyschik. Hello, Jessica.

[00:03:39] Jessica Lyschik: Hi Nathan.

[00:03:41] Nathan Wrigley: Nice to have you with us. This is my second interview at WordCamp Europe 2026. We’re in a beautiful, big media room. I’ve got to say, this is one of the nicest spaces I’ve ever had for these kind of interviews, so that’s really nice.

Jessica has already done, I want to say presentation but maybe it was a workshop. I’m not sure.

[00:03:57] Jessica Lyschik: No, it was a regular talk actually, yeah.

[00:03:59] Nathan Wrigley: Okay. And how did it go?

[00:04:00] Jessica Lyschik: It went super well, except for my slides went missing in between. That wasn’t so great. But the audience was very respectful of that, and I made a bit fun of it, so they laughed for a second and I tried, the media guys tried to fix that. We got it fixed in the end. I would’ve winged it anyway because I, like I knew what was coming up. But it’s always good to have your slides. It’s like seeing them, because for me it’s also visual reminder. It’s like, I need to see what I’m talking about, so I’m not losing track of it. But yeah, this was just a little technical hiccup. But overall I got very great feedback so far on my talk, and I’m very glad.

There were also quite a lot of people. I did not expect this many. And that makes me just super happy that people are actually interested in this topic, although it is sort of scary for some of them if they even like try to touch this topic. We can probably get into the details later. Yeah, just overall like, what does it do? Why do I need that? These unanswered questions that they have that they were like, ah, no, I’m not really interested into that.

[00:05:01] Nathan Wrigley: Oh, that’s nice a big reception.

[00:05:03] Jessica Lyschik: Yeah. And that’s just great to see because I think just as we all grow older, and I even noticed that, and I’ve said that in my talk, like I kind of get to appreciate when a website is accessible. I mean I’m still have a long time to go, hopefully in my life, but I start to appreciate the small things that make just browsing websites easier, to be honest.

[00:05:23] Nathan Wrigley: So I guess we should introduce the subject and then give you a chance to introduce yourself because it feels like in this context, the subject at hand, it’s important to know that you know what you are doing. It’s not, well, I suppose it’s a general skill in that it should be something most people know an awful lot about. But I fear that that’s not the case.

So the presentation that you’ve just given was called accessibility in themes, easier than you think. That’s nicely phrased. Let’s get them through the door.

And then the blurb that went with that, I’ll just read that into the record then everybody knows what we’re talking about. So it says, many theme developers assume accessibility ready requirements are hard to meet, but that’s rarely true. This session shares practical insights for real theme reviews, and shows how both block and classic themes can reach accessibility ready status with manageable effort.

So that’s the context of what we’re going to talk about today. However, as I just alluded to, could you just tell us a bit about you, how long you’ve been using WordPress, and then I guess if you want to focus a bit on your accessibility credentials and what you’ve been doing in that space.

[00:06:23] Jessica Lyschik: Yeah, of course. So yeah, I’ve been using WordPress, I think I started around 2005 or 6 already. So like dipped my toes into it, played with it around, just got a feel for it. But actually professionally, I started out in 2015 in the WordPress ecosystem.

Before that, I already joined the community. So I was working at another place that did not use WordPress before. And then in 2015 I joined a WordPress agency. Today they’re called Syde, for anyone who’s wondering. And ever since I’ve been into WordPress that long.

And accessibility in that case I have, I think it was a gradual process more of. It was not just like, I’m now doing accessibility. That just didn’t happen. It was, I learned it over time. And when I started learning about how to create a website accessibility was absolutely not a thing. No one cared about it. And it just became more and more aware for people, for developers, especially in the past couple years. I think we still have some way to go but like, as I said earlier, there were so many people interested in my talk. So I think we’re now at a pace where things get really interesting for many more people.

And yeah, I learned a lot along the way. Made a lot of mistakes along the way. But I’m glad I’m learning this. I’m still learning. So it’s always something that you continuously learn, because I think the hardest part to grasp for people is that, if you are abled, it’s like you can see, you can hear, you can navigate a device with your own hands, all stuff like that, you take it for granted.

And if you suddenly see or people tell you the perspective of like a blind person, a person who’s deaf, a person who may not be able to use a device like you do, maybe have a hand injury, or no hands anymore, that’s also happening. Then you start to wonder, okay, how do these people actually like use websites or use their phones or computers? And there are many different ways to do that. And I think if you have the chance to learn about this, it is absolutely eye-opening.

You can also then, there was a talk at WordCamp Leipzig this year, but also last year, I attended last year, by a blind person. And her brother was also blind. He was a developer. And they shared like how bad some websites are, and how they struggle to like get the information out of the website, and what crazy, crazy stuff people are doing to their websites that do not make it accessible for these people.

And then you are sitting there and wondering, oh my God. And sometimes I have to say, I even did this in the past and I didn’t know, but I’m glad today that I learned about this and make a better web essentially. Yeah, that’s why I’m here sharing my knowledge.

[00:09:11] Nathan Wrigley: It kind of sounds for me, so when I talk about accessibility, there’s always two strands to it. There’s like this legal bit where the governments are increasingly talking about things that will happen to you as a company that builds websites if you don’t follow guidelines. So that’s one side.

But there’s also this moral side. There’s the side of, we ought to do this despite what the law says. You know, it’s just a necessary thing. And it feels to me as if your journey in this was a moral one.

[00:09:38] Jessica Lyschik: More of, yes.

[00:09:39] Nathan Wrigley: Yeah, there was a definite need here. You know, in the real world when you see somebody, let’s say somebody who’s sitting in a wheelchair and they’re trying to get into a post office and there’s a step that they can’t get over, there’s no bit of you which doesn’t see that as unjust. Every bit of you says that character can’t get over that step. That’s wrong.

And yet, the bit of the world which is becoming increasingly the way that we interact, you know, we book flights, we file our taxes, we do our banking, we, all of these things, they’re completely invisible.

Most of the time we’re doing the internet by ourselves. You know, we might be sitting on a train, but nevertheless it’s a solitary activity, or we’re in our own home or whatever. And these pitfalls, the equivalent of the step in front of the post office is totally invisible.

And it also seems that the voice of the people whose lives are made more difficult is just drowned out. Somehow that anger that they must feel never seems to rise to the top quite enough that we all take the necessary steps.

I don’t know if any of that landed, and there was definitely no question there, but I’ll hand it back to you if any of that resonates.

[00:10:49] Jessica Lyschik: No, I think you, you’ve put it absolutely right. And the invisibility is the thing, because a step for us is visually, like we see it I mean. If you’re blind, you’re not seeing it. But let’s put it away for a second. But in the web, the invisibility is like the key thing. And I just talked to Anne-Mieke Bovelett about, who’s doing another accessibility talk this afternoon. She told me about like a company where they put effort into their website, making it more accessible. And their sales actually increased. So it can definitely help. This is just one example.

But there’s also a new player in the field that will probably even increase the interest in accessibility, and that is AI agents. Because AI agents, they do not see a website as we do visually. They rely on that the website is technically built correctly. Google actually just last month announced that they will focus on this. They will focus on the accessibility for the AI agent. I have put a link in my slides to that document. This is basically, I think something that will be easier to grasp for people for some weird reason. But it’s made more visible to them because if an AI agent cannot read your website, and I know we are probably still at the very beginning of this AI agent stuff, but I think this will increase over the next couple months or even years.

[00:12:14] Nathan Wrigley: That’s really interesting because when an individual, let’s go back 10 years, when an individual is creating a website, every single bit that you have to achieve is a minute of work or another minute or 20 minutes or an hour or what have you. And so there was this whole thing of just building the website, especially when page builders and things like that came along, just building the website to see what it looks like. And that whole accessibility layer just basically gets ignored.

However, that’s what you’ve just said is curious because the AI agent building the website, to the AI agent, that’s kind of no extra work to get it right, if you know what I mean? If it’s configured to do all of the bits correctly, I’m using air quotes around the word correctly, then in theory it should be quite a good custodian of accessibility when it’s building things. I guess only time will tell whether that actually happens.

[00:13:08] Jessica Lyschik: Yeah, but it’s also for like, not the agents itself building, but also the agents visiting your website. Especially if you do like, I think shopping will be the one thing that if you say, hey, I don’t know what the best coffee or what, this is like a good topic. Yeah, okay, here are three options. And then, okay, buy me option one, a kilo of these beans or whatever. The AI agent, if the shop is accessible, the AI agent could do the shopping for you. This is where things are going and progressing towards, that you are not actively anymore the person who actually goes to the online shop, puts it in the cart, goes to the checkout and does all that stuff for you. But if the agent knows all that, it can do it for you.

[00:13:50] Nathan Wrigley: Can I ask a question then? Because I may have, I think I’ve understood what you were just saying and curiously, I’ve never had that thought, the one that you’ve just expressed. I want to know if I’ve got it right. Are you saying that in a world in which we increasingly ask AI to achieve things on the web for us, if it’s built with accessibility in mind, it’s more likely to be able to achieve the result of, let’s say, buy me a kilo of coffee.

[00:14:14] Jessica Lyschik: Yep.

[00:14:15] Nathan Wrigley: That’s so interesting.

[00:14:16] Jessica Lyschik: Yeah because like, Anne-Mieke, whom I just talked about, shared a long document with me recently and I was just reading through it and was like, yeah, of course. Of course, if we technically do things right, we use the right elements, we do the right descriptions for everything that a computer, because AI agent is just a computer. Like assistive technology, like a screen reader who needs to read the right structure out of it and to fit the right content. But also is able to interact with stuff, like click on that button, put that in the cart, go to the checkout and so on. It’s basically the same. An AI agent is a screen reader.

[00:14:53] Nathan Wrigley: Yeah, that’s really interesting. I’m thinking of a map where I’m trying to get to a destination, but the map has no directions. Imagine a scenario where we set off from one place and our destination is here. What you are saying is all the instructions in between to get from the start to the end can be read if the HTML and all of the bits and pieces wrapped up in that are correct. I had never had that thought before. That’s so interesting.

[00:15:17] Jessica Lyschik: Yeah, that’s very interesting. And I did not focus too much on this topic in my talk, but I wanted to put it in there at least in one slide to give like the food for thought that people can actually think about it because this is like what’s hyped right now. I have not tried out this whole agent thing yet, but like from a developer perspective, I can totally see that this is something that will increasingly help AI agents to achieve stuff.

[00:15:41] Nathan Wrigley: Yeah. And presumably make it so that a whole tranche of people who struggle with the web as it is currently might be able to interact with their voice or whatever other technique they use. We’ve completely gone off the rails, but that was such an interesting aside, thank you.

[00:15:58] Jessica Lyschik: Yeah, I think this is something interesting to share. And as I said, I wanted to focus more on the technical details in my talk, so I left it kind of out. But I think it’s a great opportunity to share it here with you.

[00:16:08] Nathan Wrigley: Yeah. That was lovely. Thank you.

So let’s go back to the WordPress bits and pieces then, and I’ll just do the title again because hopefully that’ll refresh it in listeners’ minds. Accessibility in themes, easier than you think. Dear listener, if you’ve been using WordPress for any length of time, you’ll know that the themes still plays a giant part in the structure of your website and the way that people experience it.

So where are we at then in the year 2026? Does the theme still represent a huge part of accessibility? In your experience, is it easier than most people think to get an accessible website in the year 2026? We’ll get into block based themes and classic themes and all that in a minute. But essentially what I’m asking is, is it an easier thing to get right than most people imagine?

[00:16:51] Jessica Lyschik: Yes, because I think what scares people off from my own experience, there are requirements to get the accessibility ready tag in the wordpress.org theme repository. And these requirements, if you first read them, they’ll sound a bit cryptic and you do not really understand what they actually mean.

In my talk, I was trying to combine this, what the requirement says with what is actually meant by that. Because right now, and this is something I would like to improve for the future, I’ve already talked to people about this, and I will have another chat with Rian Rietveld about it later, or tomorrow. Let’s see when we can make that happen.

Because right now the requirements read like, okay, this must be achieved. This is what the website should do. Then there are some testing instructions, but you’re not told how to achieve it. What do you technically need to do in order to do that?

I noticed this while I was reworking. I found out about the requirements also just a month ago because the requirements got updated. I have a theme in the wordpress.org repository and I tried to apply these new rules and have another fresh look at it. I got the accessibility ready tag for this already when I first got the theme into the repository. But like it was a good refresher to like go over all the requirements because they have slightly changed a bit, they added new ones.

When I was there, I was like, okay, like I understand this now because I have learned about accessibility over the past couple years. For someone who is fresh to this topic and doesn’t know too much about it, it’s hard to understand. Because there are some descriptions of things like, basically what it means is that you need to use, for example, the right HTML tags, header, footer, the main tag. We have section and aside, which are available in HTML 5. But the requirements does not say this explicitly.

And I think this is where probably most people have gotten stuck in the past, because they did not understand like, what is actually required from me technically? Because the texts are not so much focused on that. And this is something I would like to contribute as well, to give back and to enhance. So it’s not there yet, but hopefully sooner than later we can add all this information so it gets even easier for people.

Because if you’ve done a website and you know about the HTML, you know about maybe a little bit of CSS, you know how to achieve this. You just need to connect the dots to what is relevant for accessibility and how do you do this in your HTML essentially.

[00:19:20] Nathan Wrigley: Yeah, I guess that’s a bit of a shame really, isn’t it? Is that the documentation is difficult to follow because I feel that accessibility is one of those things where if something is difficult it can get dropped basically.

[00:19:33] Jessica Lyschik: Yeah, people won’t do it.

[00:19:34] Nathan Wrigley: Yeah, because the majority of people browsing the internet can browse the internet despite your accessibility efforts, that will be the standard that they’re aiming for in most cases. So if it’s difficult to achieve these things and the documentation’s not really straightforward, every time somebody comes across a question and thinks, I don’t really know the answer to that, probably the quickest thing to do is just to, ah, push it to one side and not press through. But you obviously have and made it a bit of a goal.

So is there a particular accessibility requirement that developers in your estimation kind of overestimate the difficulty of? What I’m asking here really is about some low hanging fruit that you know about. In the scenario that we’ve just described where it’s easy to get put off and to sort of say to yourself, okay, I can’t do this. I’m wondering there are some sort of quick wins that you could describe that people could maybe achieve within the next half an hour, once they sat down at their machines?

[00:20:27] Jessica Lyschik: Yeah, I think there are definitely some. There is like underlining text in your main content, just underline the text. It’s one line of CSS, text declaration underline. For links, obviously, not for the entire text.

And there is like, as I said, the HTML tags. With block themes, it’s super easy. For example, you just need to configure that correctly in the editor, or use the correct template part and it’s basically done for you. Core does that. This is one advantage of block themes, but we can dive into this deeper later. Or the skip to content links also in block themes.

As an example, in block themes it is just like putting the content block in a group and assigning the main HTML tag to that group. And WordPress does the rest for you. It’s just like assigning this one little setting correctly and then you get automatically a skip a content link for block themes.

[00:21:18] Nathan Wrigley: Yeah, but curiously, if you didn’t know that small fact, that WordPress would handle that for you, if you don’t know, you don’t know. And you’d presumably go around the houses trying to figure that out for yourself and implement some custom version of that thing. Whereas in fact, what, three clicks, four seconds and you’re done.

[00:21:33] Jessica Lyschik: It’s super easy, yep.

[00:21:33] Nathan Wrigley: Yeah. Any more before we move on?

[00:21:35] Jessica Lyschik: I think these are like the most, absolutely the low hanging fruit is also if you use any images to add an alternative text. I think this is probably the most common one people already know. It is so easy. And even WordPress, even if you use classic themes, it’s already in the media library, the alternative text field. For block themes you have it directly at the image so it’s already in front of you. You just need to use it.

[00:21:57] Nathan Wrigley: Yeah, you just not ignore it basically. Yeah, that’s true.

So has this become kind of a habit for you then, over the last period of time since you’ve taken more and more interest in this? Have you got to the point now where this is just how it works? You know, in the same way that I drive a car and I use the gears and that’s all just second nature. Is it like that for you when you are building your themes? Because it’s now locked away in your head. Every time you do a thing that previously you would’ve omitted. You are now just in the habit. Has that been a difficult journey or fairly straightforward?

[00:22:28] Jessica Lyschik: I think it’s, like starting out with this, it would feel like a bumpy road. But for me it was, it’s a gradual process. But right now it’s really like, yeah, I just know that when I use a button in a context that is not like sending off a form to add an aria label to it, it’s like, it is baked into my brain essentially already because I know.

And I just had a very interesting example this week at work where there was a client reaching out saying, hey, we did an accessibility test on our website and it marked like two buttons that did not say what they’re doing. These were essentially missing the aria label because they had only icons on the buttons, not real text.

So if there’s just an icon, the screen reader cannot read, what is this button for, essentially, with just an icon? The win here was just to add the aria labels, because the fields were already there. This was also part of the Greyd.Suite, so from our product so I knew how to put it in there. And then it was like, oh no, like I have to do this 12 times, my colleague said. And I was like, yeah, okay, then you have to do it twice, 12 times. So 24 times. But be happy it’s not 200 times you have to do it.

So, and I said, do not take this personally. This is a great example of why putting accessibility at the very beginning of when you’re creating this makes life so much easier than rather when you just build a website and then you figure out you have to change 300 buttons. This is probably a crazy number, but just to give you an example, to change all the buttons manually again, going through every single page or whatever you have when you just could have taken the extra step, added the aria label, and then just be done with it.

[00:24:09] Nathan Wrigley: Right. That’s an interesting thought. And also the exasperation of your colleague there kind of perfectly sums up the problem. In that you see it as a problem. Does that mean I’ve got to do something 24 times? And there’s this sense of, ugh, I’ve got to do this work. And it feels like a chore. But then I suppose if you step back and look at what you’ll actually enable by doing those 24 things.

And I know that in the workday that’s hard to do. It’s hard to sort of step back and say, okay, if I do this thing 24 times, this will be the result, and lots more people will be able to, in this case, view the image.

[00:24:42] Jessica Lyschik: I mean this was like they started already working on. If you fix it now, you do not have to do it for the coming pages. So if you multiply that with how many pages more you need to do, once you get this one fixed, and ideally you need to change the aria label of the text changes obviously, but this was, I think for a header, in a header, where there was like, I think one sort of popover or popup. Fully accessible by the way, so don’t worry about that. And also a button to, I think for the phone numbers, like just a phone icon. And they could click on it and it would be something like that, along the lines. I don’t exactly remember what it was. But it was just like two icons in the header. And if you take that header, use it on, I don’t know, another 250 sites, you don’t need to do the work anymore.

[00:25:29] Nathan Wrigley: Okay. So you are painting a picture in which, get it right at the beginning, follow the guidelines, do the hard work once, then almost the career from then, from this moment forward, your life will be immeasurably easier if you build it into the theme or.

[00:25:45] Jessica Lyschik: And accessibility will not be taken as, ugh, and I now have to do this all. Because when you do it from the start, you have to make sure at the end of course that it still works. You may have to run into issues and redo stuff. That can happen. But I think you just have saved yourself so much work in the end if that requirement for some reason pops up later or so.

[00:26:10] Nathan Wrigley: I’m wondering, depending on the kind of nature of where you work, and how you do this. You know, if you’re a freelance, then this is on you. If you’re in an agency, then it may be that there’s somebody, you know, maybe there’s an SEO person, there’s a design person, maybe there’s an accessibility person. But it does feel like the moral argument states everybody should have some insight. Maybe you’re not right in the weeds of it, but you should have some knowledge of what the low hanging fruit is, at least.

[00:26:38] Jessica Lyschik: Yeah it’s, what’s the right word for it? Interdisciplinary. It is like not just the developer who needs to think of accessibility. It’s like, okay, we need to because like we provide a technical structure for it. But it also needs to be for the content people who write the blog posts, the pages, whatever, for SEO people to understand that.

And I think accessibility, if you want the entire website to be accessibility, everyone who works on a website needs to know about it. That an SEO person needs to know how to create a skip link, probably not. Or how to use, maybe to use the right text. But for them, the text would be just the, using the right heading structure, for example. This is also a requirement, that you do not use an H3 and then an H6 heading in your content, but you structure it correctly that you have the H1 on the top, and then every next level is H H2, and then every level under that is H3. So this way. They should know about this. But they do not need to know too much about the technical side. Because in the end, it all comes together and creates an accessible website.

[00:27:42] Nathan Wrigley: In your commentary a few minutes ago, you mentioned that there were some guidelines in order to put a theme on wordpress.org. Is that the nature of it? Is it a guideline, or are there some hard and fast rules, which will prevent a theme getting into the repo based upon a lack of accessibility? What I’m asking is, are there some things that you must do as of now, or is it very much, okay, if you do this, great, but if you don’t, we’ll let your theme pass anyway?

[00:28:09] Jessica Lyschik: Yeah. Let me explain this. So there’s this accessibility ready tag. So you have different tags for the themes in the repository. And in order to get the accessibility ready tag, you need to follow the requirements, the accessibility ready requirements, I think it’s completely called.

And these are as of now 18 requirements. I went through them all in my talk. We’ve already touched on some of these. Some are really low hanging fruit, some are, one of the newer ones are, a theme should not recommend or require a plugin that is not accessible. This is something else that the team came up with, which is an interesting one. There’s, I guess a lot of room for discussion.

But also another one is to have an accessibility.txt file in your theme. Which basically, it’s not a standard yet, but like close to a standard sort of, has information about what has been done in terms of accessibility. Are there any classes that you can, CSS classes that you can use to make use of texts for screen readers? So basically hide them visually, or hide these texts or items visually, but still have them read out by screen readers. So they’re not like discipline none where you just remove that basically from the accessibility tree, but make it still readable for screen readers. And just some more information about that.

Yeah, you need to meet all these requirements with your theme if you want this tag. But you can still like do not care about accessibility and still get your theme in the repo if you want.

[00:29:40] Nathan Wrigley: Would you like that to be flipped? Would you like that to be, because I mean we’re a very open ecosystem, aren’t we? And would you like to see though a day where you don’t meet these 18 guidelines, you don’t get the tag, you don’t get to play, you’re not allowed in the repo? Or is that a touch too far?

[00:29:56] Jessica Lyschik: Let me share some numbers, I think. So there are like 14,700 plus themes in the repository right now. All themes. At least that’s the number I can access. I don’t know if there’s maybe a bit more, I don’t know. But this is the public number you can access. And out of these themes, I think if I saw the correct number, it’s like just 270 have the accessibility ready tag. So then that is like 1.5% of all themes who have that tag.

So I think it will be extremely hard to force sort of, if you want to flip that, force that onto people. And I think we need to do a more gradual way. And that’s what I’m sharing my knowledge because I think it is not that hard. If you can improve the documentation for it, it will be even easier for people. And I think this is the way to go instead of forcing like, because we do not like to be forced to things we do not understand.

[00:30:50] Nathan Wrigley: That’s right. Yeah, that’s interesting. I wonder if there’s a future in which that slowly gets ramped up.

[00:30:56] Jessica Lyschik: I think with the AI agents, we will have an acceleration on this, I guess. So maybe not in WordPress themes, in the repository directly, but I think the attention will be put there and then like, oh, maybe we should make it more accessible. Let’s read into this. And I think these guidelines are also very interesting, maybe not just for WordPress themes. I mean, of course they’re for the repository, but you of course can apply them to your own custom theme, definitely. You do not have an absolute check like the team will do for you. But nothing stops you from using them even on a non WordPress site.

[00:31:30] Nathan Wrigley: Do the guidelines, do they feel like they’re kind of firmly fixed or is it always a movable feast?

[00:31:35] Jessica Lyschik: They’re relatively fixed.

[00:31:37] Nathan Wrigley: Okay, so if you were to swat up, for want of a better word, on what there is right now, there’s a good chance that the rug will not be pulled out from under you in six months, a year, two years time.

[00:31:46] Jessica Lyschik: No, I think the last time the requirements got updated was in 2012, 14. I would need to ask, Joe Dolson did the initial, or was working on the initial thing. And so it has been a while since this got updated and they just got updated last month. So I don’t think that they will be changing anything.

The one I talked about, not requiring or recommending plugins is the one, this is something, it kind of creates a grey area sort of. And I think this will be put to discussion. It’s like, I don’t mind, but I can see many people like really, not raging against it, but like raising questions about it. If this is something that should be a requirement.

But I think for like the actual technical stuff, I don’t think that there’s much that should change, because like they’re based on the WCAG requirements. These are like the standard requirements that also have, I’m not sure if they’re used on governmental things, like on the European Accessibility Act, but I think they’re a sort of base for that. And it’s not like completely this. So the theme requirements are not like the WCAG requirements 100%, but like a subset of it, sort of.

[00:32:57] Nathan Wrigley: Yeah, it’s a fairly slow moving ship in other words. If you acquire the knowledge today, you’ve got a good chance that in a year, two years, maybe even five years, the knowledge that you’ve got will need amending. But most of it will broadly work several years from now.

[00:33:11] Jessica Lyschik: It’s with like development in general. So like you always need to be constantly learning. And I think if you learn about accessibility today, I think you’re in a very good spot. Because like of course we have European Accessibility Act and governmental requirements, at least in Europe we do have them. But I think there’s already so much information out there, that it should be relatively easy to onboard you. And I think this is just beneficial if you learn, it’s basically about learning about how to use things correctly. And if you’ve got that, then you’re absolutely good to go.

[00:33:45] Nathan Wrigley: So not that long ago I suppose, we had block themes coming around, which is an entirely different way of creating themes in WordPress. So you’ve got classic themes, which is the way it always used to be. And now we’ve got block themes. Is there a striking fundamental difference in the way that you might approach accessibility if you were used to doing block themes? Is there a whole lot more to learn? Maybe it’s more straightforward if you’re using block themes. Just tell us about how those two things differ.

[00:34:08] Jessica Lyschik: Yeah. It is more straightforward actually. Core is handling stuff for you. So accessibility just got a tad bit easier if you use block themes actually. In classic themes, you have to do a lot of things manually. You have to make sure that the elements are right, that the skip link is there, for example, things that we touched on already. And in block themes, if you use the correct blocks on the correct structure, Core handles stuff for you.

For example, there’s a requirement labelled form fields. So when you use a form or the form fields should have a label to it. In themes you don’t really have that because usually you should not put like, something like a form in there. There are two forms that by default come with a theme that are the comments form, but that’s completely handled by Core. And there’s the search form on the search results page.

But in block themes, both of them are handled by Core. Both of them are accessible because Core handles it all for you. You just need to place them and actually not do anything to them. It is that straightforward.

And same for like template parts. If you want to use header and footer, just use the template parts and use them. You can assign them a header template part as header of course, and one as footer. And then the HTML text will be automatically added correctly for you. So there’s not too much that you need to do manually anymore, just get that right.

And as I say, I really love block themes for the much easier accessibility, or the way you can make a block theme accessible. This is so much easier than with a classic theme.

[00:35:38] Nathan Wrigley: So presumably though, it sounds like there’s meta knowledge, if you know what I mean. You’ve got to know which block to put in which spot, and which block wraps this other block, and the parents and the children. But if you learn that, and if you make that, we were talking about habits earlier, if you make that your habit, and then save that habit and save the theme and what have you, you are painting a picture where it’s significantly more straightforward because you don’t have to think about it in many cases. Well, that’s the wrong way of phrasing it. You don’t have to do that hard work.

[00:36:07] Jessica Lyschik: Exactly. If you have like a, sorry to interrupt you here, but if you have a theme that already gives you the correct examples, you can build off from that theme. For example, if you’re creating a new template, you can use an existing template and then just adjust it to what you need. If you need to change like colours or something but you have the structure already correct. You do not need to think about doing the structure again and maybe just have a check that it’s actually the right one. But if you just copy what’s already there, that is part of the theme, that’s actually super easy.

[00:36:38] Nathan Wrigley: I’m going to link to your presentation, which I know by the time that this goes out will be probably on wordpress.tv, I would’ve thought by that point. But I’ll link to your presentation and all of the different bits and pieces.

But I’m curious, who in the WordPress space, and maybe not the WordPress space, maybe outside of that, who do you follow or try to get guidance from? Maybe that’s a YouTube channel or a blog, or a, I don’t know, government based website. Maybe it’s just wordpress.org, I don’t know. Where do you go to swat up on all of this?

[00:37:06] Jessica Lyschik: Ooh, there are some very good resources out there. So I do follow like people within the WordPress community. I mentioned a few names already, like Joe Dolson, Rian Rietveld, Amber Hinds from Equalize Digital. They do a lot of stuff in that area. And then I also follow Sara Soueidan, she’s a developer from, I think Lebanon, if I remember correctly. She does great stuff on accessibility. There is a few more names. There are some good resources out there. I can probably research that for you because I cannot remember the names right now.

[00:37:39] Nathan Wrigley: I’m putting you on the spot. I’m sorry.

[00:37:40] Jessica Lyschik: Put me on the spot. That’s okay. I’ll share some links with you that you can then put in with the podcast information. There are some great resources both within the WordPress community but also outside of it that can give you a very good overview. And I think it’s just interesting to follow people who like can build the bridge between, okay, this is a requirement, this is how you technically do it, and this is why you do it.

[00:38:05] Nathan Wrigley: I have a friend who’s recently been on the journey of trying to go from zero to really quite proficient in this space. He’s found a bunch of YouTube channels and several of the names that you mentioned there, particularly the Lebanese lady that you mentioned.

And I think followed a course that they put together and found that structure profoundly helpful. The dry documentation, I think was the way it was described on the WCAG website can sometimes I think be a, you know, it’s hard to get into that in some way.

You know, if this all sounds like a lot of work, there’s definitely resources out there, which, fun is perhaps the wrong word, but make it more engaging. There’s videos to watch, and channels to follow and blogs to read and all of this. And so it turns this, I’m doing air quotes, dry subject into something a little bit more manageable and easy to take in.

[00:38:52] Jessica Lyschik: Yes. Yes, because like the WCAG requirements, like they’re hard to read. It’s like reading, the HTML 5 spec. This is also super hard to read.

[00:39:01] Nathan Wrigley: Yeah, it’s the cure for insomnia.

[00:39:03] Jessica Lyschik: Yeah, sort of. And it’s, yeah, I think if we have, not more content, but the right content available to people in the right spot, I think this will be beneficial for everyone.

[00:39:14] Nathan Wrigley: Yeah. I think unless there’s something else you want to cover off, I think, Jessica, I’ve asked everything I wish to. Is there anything you think we’ve omitted or are you happy to call it a day there?

[00:39:24] Jessica Lyschik: I think we’re, I mean we could go on probably for days. But I think for now it’s, we’ve covered every topic.

[00:39:32] Nathan Wrigley: Well in which case, what I’ll do, dear listener, if you go to the WP Tavern website and search for Jessica’s post, I’m not sure what number it will be as we’re recording it, go there and anything that we discussed, and any names that we discussed and those kind of things, I’ll put a link and obviously if Jessica supplies any other things she mentioned, we’ll add those in as well.

So Jessica, thank you so much for chatting to me today. And now that your presentation is done, you can relax and enjoy the rest of the spectacle.

[00:39:55] Jessica Lyschik: Yes. Thank you so much, and thanks for having me.

[00:39:57] Nathan Wrigley: You’re welcome.

On the podcast today we have Jessica Lyschik.

Jessica is a longtime member of the WordPress community who has been working in the ecosystem since 2015. She has spent years learning and advocating for web accessibility, both as a developer and as an active community participant, joining agencies, working on theme reviews, and helping to improve standards.

Many theme creators assume that making themes accessible is an intimidating task, but Jessica’s here to show you that achieving an accessibility-ready WordPress theme is more straightforward than you might imagine. Her WordCamp Europe 2026 presentation, “Accessibility in themes: easier than you think,” aimed to demystify the requirements for accessible themes, explaining what the WordPress guidelines mean in practice, where the low-hanging fruit is, and how both block and classic themes can reach accessibility-ready status with manageable effort.

We talk about the personal and moral journey that brings developers to accessibility, the technical hurdles and documentation challenges, and the ways in which things like AI agents are putting accessibility in the spotlight for everyone. Jessica talks about practical steps that quickly improve accessibility, like using correct HTML tags, adding alternative text to images, and configuring skip-to-content links, and shares why building accessibility in from the start saves time and effort down the road.

We also explore the differences, and possible advantages, of block themes when it comes to accessibility, why theme guidelines work the way they do, and the importance of interdisciplinary awareness across SEO, design, and content teams. Jessica mentions helpful resources, influential leaders in accessibility, and the ongoing need for documentation improvements to help everyone level up.

If you’ve ever felt overwhelmed by accessibility requirements, or wonder why they matter, and how you can build better WordPress sites that work for everyone, this episode is for you.

Useful links

Accessibility in themes: easier than you think – Jessica’s presentation at WordCamp Europe 2026

Syde

WordCamp Leipzig 2026

 Greyd.Suite

Accessibility Handbook – Theme section

WCAG 2 Overview

European Accessibility Act (EAA)

 Joe Dolson

Rian Rietveld

Amber Hinds

 Sara Soueidan

💾

#225 – Milan Petrović on the Risks of Legacy PHP in WordPress and Why Upgrading Matters for Security

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, the risks of legacy PHP in WordPress and why upgrading matters for security.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players. If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you or your idea featured on the show. Head to wptavern.com/contact/jukebox and use the form there.

So on the podcast today we have Milan Petrović. Milan has been deeply immersed in the WordPress ecosystem since 2007, developing an array of plugins, especially for expanding bbPress forums, and running his own company, creating plugins before joining the Freemius team as a full stack developer. With nearly two decades of hand-on experience, Milan has witnessed firsthand the evolution of both the WordPress and PHP landscapes.

Many WordPress users may be only partially aware of PHP. Perhaps they’ve noticed version numbers in their hosting panel, but few of the millions of WordPress users understand the real impact that PHP versions have on the security and performance of their websites. Milan is here to shine a light on why embracing newer versions like PHP eight isn’t just good practise, but a crucial step for security and efficiency.

Milan begins by recounting his journey through WordPress development. The conversation gets into the heart of his recent WordCamp Europe presentation, which tackles how legacy PHP code exposes sites to thousands of open bugs and vulnerabilities. And why relying on old versions is, as he describes, an active invitation for automated exploitation.

The discussion explores the contrast between running legacy code, and using the native shields of modern PHP, and highlights how PHP 8 not only closes security holes, but also delivers major performance boosts, reducing memory usage, and accelerating speed.

If you’re wondering why you should care about the PHP version your site is running on, or you’re a developer interested in practical ways to harden your code, Milan unpacks both the existential risks of outdated PHP, and the step-by-step benefits for hosts, agencies, and plug-in developers alike.

He introduces his Vulnerability Lab plugin, designed for developers to see firsthand how code exploits play out differently across PHP versions, and makes the case that modernising can happen gradually, one update, one plugin at a time.

If you’ve ever questioned how your hosting choice, or plugin stack, could affect your site’s future. Or you’re ready to take the first steps towards building more secure and future proof WordPress products, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Milan Petrović.

I am joined on the podcast by Milan Petrović. Hello Milan.

[00:03:58] Milan Petrović: Hello Nathan. Thank you for having me here.

[00:04:00] Nathan Wrigley: You are very welcome. We’re in a beautiful, beautiful media room at WordCamp Europe. And I know that you have already done your presentation because we just had a little chat about the fact that you’ve done it and it went well and all of that.

Do you want to tell us a little bit about you and your background working with code and developing and security and all of that kind of stuff? And then we’ll talk about your actual presentation and how it went.

[00:04:25] Milan Petrović: So I started with WordPress almost 20 years ago, so way back in 2007. And I created a lot of plugins for WordPress, and I especially have a lot of plugins for bbPress for expanding forums. Yeah, people still use forums these days. So that was, I really like bbPress and all the stuff I did with that.

I have been working as a freelancer for a lot of years. I have my own company that was doing plugins, it’s called Dev4Press. But in 2024, I joined the amazing team at Freemius. So for almost two years I am a full stack developer at Freemius. And that was a really nice change of pace for me and the work I usually do before that. So yeah, that’s a short of it.

[00:05:13] Nathan Wrigley: Yeah. That’s great. Thank you. And so the presentation that you did that is now over, goes like this. I’m going to read the entire blurb because it’s short enough to read, and it says, secure by design, hardening plugins with PHP 8.x. In the WordPress ecosystem, we’re often forced to choose between supporting the lowest common denominator of hosting and implementing modern security. But in 2026, writing legacy PHP 7 code isn’t just a bad habit, it’s an active invitation for automated exploitation. It’s time to stop playing whack-a-mole with sanitisation, and start building products that are secure by design. This talk isn’t just another slide deck on security tips. Through comparisons of a Vulnerability Lab plugin, you will see how common exploits like authentication bypass, and server side request forgery succeed on legacy code, only to be neutralised by the native shields of the latest PHP. You learn how to leverage the modern PHP patterns to ensure your plugins are resilient to a wide range of exploits.

Now into the show notes I will put Milan’s wordpress.tv presentation so that you can go and watch the entirety of it. I guess basically if at any point you get confused, that would be a good idea, pause this podcast and go and check that out. But, how did it go? How well received was it?

[00:06:33] Milan Petrović: For me personally, I’m very satisfied with how how it went. I don’t know, it’s a bit overwhelming to be honest, but I am very satisfied and I got a lot of questions after the talk. I met a lot of people that liked what I had to say. And I think it’s good feedback to have, for something that is more technical like this was.

[00:06:52] Nathan Wrigley: Well touching on the fact that it’s more technical, I have to confess that I think you are going to have to shepherd me through this, because a lot of the content that you I think probably got stuck into is beyond my pay grade. But hopefully we’ll get through it.

Now at WordCamp Europe, where we are now, I don’t know what the ratio is, but I’m guessing that a significant proportion of the people out there are not developers. They kind of know that PHP is a thing. They realise that WordPress is built on that, but they don’t really have an understanding.

They’ve probably heard of PHP 7. They’ve probably heard of PHP 8, because somewhere in a control panel that was shown to them. But maybe there’s not much of an understanding of the fact that it gets better over time. It gets secure over time. I think there’s probably a notion of, well, my website works. Why do I need to change anything?

So let’s get into that. What were you talking about in your presentation? What’s changed in the landscape of PHP more recently that you brought to the fore that you shared with your audience?

[00:07:51] Milan Petrović: Yeah, I think that PHP 8 was a big milestone for a lot of things. And I’m not sure, but I don’t think that the wider communities are kind of aware about the impact of the PHP, or the server environment in general, on how the websites work and how secure they are. Maybe the WordPress in itself needs to spread more awareness about that.

Because right now we get a notice in the dashboard that maybe the PHP needs to be updated. But for a lot of website users, that can be too much and too little information at the same time, because they may be not aware of how to do things on their hosting site.

We need to spread more awareness about how important the changes in the code are when it comes to the newer PHP versions, and what they can do to improve the security. And how developers should be starting to use more of those new features and the new things that PHP provides on a language level nowadays.

[00:08:49] Nathan Wrigley: WordPress has got this real legacy, I suppose is the right word, of supporting legacy code. So WordPress itself is supported way, way, way back. You can keep using versions of WordPress, which are many, many, many years old. And I wonder what your stance is in terms of PHP, whether or not WordPress runs versions of PHP which are far too old, in your opinion.

So in other words, should WordPress have a policy of, I don’t know, 8.x only? Or is 7 okay. And I don’t know what other CMS platforms, you know, Drupal, Joomla as was. I don’t know what they do, I don’t know what their posture is.

[00:09:32] Milan Petrović: I think that one of the most important decisions that, it was done with WordPress early on, is that backwards compatibility, because it opened the doors for a wider adoption. Because you don’t need to change server every year, or you don’t need to upgrade your software that often. And that helped a lot of hosting companies to provide WordPress hosting very cheaply, because they didn’t have to have the latest PHP, they didn’t have to invest much more money into all that. So WordPress got a lot of adoption from backwards compatibility policies.

But in the same time, that also proved a bit of a problem. Because even the WordPress Core code is kind of stuck because of that policy of backwards compatibility. And it’s not only compatibility with old versions of WordPress, but the old versions of PHP. And we are running now maybe six years behind end of life PHP versions. Because PHP 7.4 end of life was four and a half years ago. And we still support it in the Core.

[00:10:33] Nathan Wrigley: Yeah, I guess it’s a nice thing to support it. And it, as you described, it was a great way of onboarding the millions of people that came along. But things have moved on.

What would be some of the top level items? And I’m inviting you to open the scary book and sort of give out the worst case scenarios basically of running legacy code. So really, go to town, frighten us all. What are some of the horrors that await if you’re quite willing to, as a hosting company, support seven point whatever or beyond, six or five, or dare I say it, four, who knows? What are some of the terrible things that await us?

[00:11:08] Milan Petrović: To be honest, when I was researching some of the statistics and things like that, I was kind of scared when I saw that there are 3 or 4,000 open bug reports for PHP 7 and PHP 5, which are still in use today, and there are WordPress websites running on both of them in the millions. And there are 3 or 4,000 open and confirmed bags that are never going to be fixed. Never. So PHP 7 has thousands of bugs, and I’m sure that not everything security related, but a big chunk of those bags are related to security.

And there are open exploits that run on the PHP level. They don’t care really about if you are using WordPress or using something else. It’s more like a exploit on the level of a, on a server side that can be quite scary because you, even the technical people are not really sure what are all those bugs. Who is going to go through 3,000 or 4,000 bug reports?

[00:12:05] Nathan Wrigley: Yeah, so just to sort of describe that, the fact that there is no more updates to the 7 branch of PHP means that all of those bugs which are publicly available, anybody can go and read great detail about what they are. Well that then means that any hacker can do that, and probably did like a dozen years ago. And so really you are painting a picture there of you are asking for trouble.

[00:12:30] Milan Petrović: There are hosting companies that maybe do things a bit differently because you don’t need to run PHP as it was created. You can build your own version of PHP. You can patch bugs on your own. And a lot of hosting companies are doing that. But in the same time, that also poses a problem. You are going to run WordPress in your own plugins on a platform that is not actually officially PHP supported. It can have some different quirks that make your code run a bit differently.

A while ago we had the Facebook running their own PHP build, that was quite different from the public PHP. But they used it, and other people started using it. So I don’t know. Still I think that the official PHP is the one you should be on because you never know what other issues. Even when hosting company patches the PHP they’re using, maybe they’re opening doors to something else that is not quite documented on that level.

I think that the best policies, I don’t expect for WordPress to adopt the latest PHP or only supported PHP versions, but to kind of move quicker on the adoption of the newest version. So maybe we should be quicker to adopt PHP 8.0 or 8.1 is a next minimal required version for WordPress.

[00:13:50] Nathan Wrigley: When you say you don’t expect WordPress to do it, is that simply because it doesn’t have a history of doing it? Is there a technical reason why WordPress could not keep up with the latest version? I know we’ve got this plugin architecture where there’s thousands and thousands of developers who are all doing their own thing, and there’s all of that. Is there any technical reason why WordPress couldn’t be on the cutting edge, most up-to-date, latest version?

[00:14:15] Milan Petrović: There are two factors in all that. First one is you can declare, PHP 8 is the minimal version we support. We don’t support PHP 7.4 anymore. And that means that you don’t need to make any changes in WordPress at that point. You can declare it because WordPress is compatible with all PHP versions. It works on 8.0 and 8.5. That’s no problem. But say that branch 7 is no longer supported, you’re kind of pushing other developers and hosting companies to improve their support for newer versions.

And you don’t need to make immediate changes to WordPress. But at that point, you are open to modernise the code because now you can have more stricter typing across the board. There are some strict typing things in older PHP versions, but with 8.0, you can do all of that. And it doesn’t have to be a process that is done immediately. It can be done gradually. You can update parts of the WordPress Core over time. And it’ll take a few years, to get up to date, but at least you are closing doors to some older versions of PHP, and you are pushing developers as well for plugins to have that policy.

Right now, each developer can have their own plugins supporting any version of PHP you want. For my plugins, I have policy of 8.0 as a minimal version since this year. And, I’m updating the code as I go along. I don’t do it, it’s impossible to do it all at once. And for WordPress, it’s going to be even worse to make it all up to date. But declaring PHP 8 is a minimal required version, would be a great step in the right direction for wider adoption.

[00:15:51] Nathan Wrigley: Yeah, I think the problem is simply one of the user base, isn’t it? There’s just millions of people, thousands of developers all doing their own thing. And casting 8.x, 8.0 and above as the new minimum, there’s going to be a moment where some things do go wrong.

So that calendar plugin that you’ve been using for ages, which just works. And sure, you’ve never really received any updates from the developer, but it just works. Everybody’s booking on my calendar and we are all good. And then suddenly PHP 8 is required and it turns out the calendar plugin now no longer works.

You can imagine those kind of stories a million times over coming to the fore. But equally, we got to move on. There’s no way of, you know, because we can’t in 10 years still have sites on 7.4.

[00:16:43] Milan Petrović: We have sites on five point something. I recently checked the official WordPress tracking. 7.4 is on 20% even now. So we are far away from WordPress ditching the 7 branch. And I think there are still few percent of PHP 5 in all that so.

[00:17:01] Nathan Wrigley: Yes, I regularly look at the, it’s like a little donut chart, isn’t it? That is often produced and you gradually see the eight point x whatever section of the pie getting bigger as they produce the next survey. But you’re right, it’s still a significant chunk that’s on 7 and below.

And whilst when I look at that chart, it doesn’t really bring any alarm bells to the fore, I just think, oh, that’s a shame. But now that you are presenting this talk, and giving me this information, I realise that that attack surface is worse.

When you gave that talk, who is your target audience? Were you directly sort of aiming at the hosting companies who presumably can do a lot of work very quickly? You know, they could take a million people onto 8 with a little bit of development work and on the back end of their platform. Or are you really encouraging the general WordPress user, like me, to take a bit more interest and make sure that I am going into the cPanel or whatever it is and updating myself? Or is it a bit of both?

[00:17:59] Milan Petrović: For everyone actually. It’s for developers to be more aware of what they can gain with the new PHP versions. It’s for hosting companies. Because it’s not only about security when it comes to the newer PHP. The PHP is faster and faster. So each new version gets you 5 or 10% more performance without doing anything. So PHP 8.5 is more than 50% faster than PHP 7.4. So that’s a significant update.

And I have even, one slide was showing how much less memory PHP 8.5 used to run exactly the same piece of code. So it’s pretty wild to see that hosting companies are maybe the biggest factor in all this. They will gain a lot more because they’re going to free a lot of resources to run more websites because PHP is going to use less memory and it’s going to be faster.

So I understand they need to invest a lot of money to do all that. But, I don’t know, I think that gains from that are very significant, on that level alone.

[00:18:57] Nathan Wrigley: Yeah, so you described there are really compelling scenario. You know, it’s quicker, it uses less memory, you’ll save money. I mean what else do you need? You’ve just presented the entire argument.

However, it hasn’t happened. So technically speaking, why do you think it hasn’t happened? Is there an acquisition of new knowledge that is difficult to take in? Is it that simply you would have to, I don’t know, retrain your staff? How do you understand that it hasn’t happened? What are the reasons people are digging their heels in and not making these updates?

[00:19:25] Milan Petrović: I kind of make the group of two or three types of hosting companies. One, and that’s usually more expensive managed hosting solutions. They are forcing the updates. They’re not maybe on the latest version, but they are forcing their users to use at least three or four versions of PHP back. So maybe 8.2 or 8.3, which is a great step in the right direction.

There is also a problem of support. If something starts breaking, they’re going to be the first one to be asked about that, because they made the change to the server. So why now website that was working yesterday is no longer working today because of some change made on a hosting level. So there are a lot of factors to play into that adoption.

But on the other hand, there are a lot of developers that have moved on with supporting PHP 8. A lot of plugins are very much updated and, especially popular plugins. They invested a lot of time to do the update. It’s getting easier to support it. But on the other hand, you have very old websites that are simply cannot move without proper testing, without updating the plugins. And there are cases when you cannot simply update one plugin because something else may break, or you made some changes that will make some other thing break. So it’s a big puzzle that is definitely not easy to solve, but maybe we should start some work on that as a community to do it, and to move people along.

I don’t want to say force the change, but make people aware of the benefits. Make people aware of the risks if they continue to run the old and outdated software. And the same goes for not updating plugins, not updating WordPress. No matter how much work is done in that regard, there are still most likely some exploits on a WordPress level for very old versions that at some point someone is going to find out about and exploit.

[00:21:16] Nathan Wrigley: I mean I guess the motto of WordPress was democratised publishing, which means basically make it available to everybody. No matter your level of expertise, make it available to everybody. And I’m sure that if you were to grab the CEO of any hosting company and say, I can save you money, I can save you resources, and all of those things that you outlined earlier, they would, yeah, we know, we know. But we’ve got thousands of non-technical people using WordPress.

I kind of have this analogy in my head, and it goes a bit like this. Several years ago, I bought a bike. And it sits in my garage and there is my bike. And I expect my bike to work tomorrow in the same way that it did four years ago. And in 10 years, I expect my bike to work. I don’t expect there to be an update to wheels or gears or the saddle. It doesn’t need an update. It’s just a bike. And I need my bike to be a bike and nothing more.

And I get the impression that many people treat their WordPress website as the same thing. This sort of static commodity that, sure enough, they pay a monthly fee for it, but it’s this website. It’s a thing, and it doesn’t need changing. And so what I’m trying to say is, I’m fairly sure that the hosting companies are met with that an awful lot. The customers who just, it’s a bike, it’s a website. Do you know what I mean?

[00:22:37] Milan Petrović: Yeah, but you need to maintain your bike. If you don’t do it, it’s going to, your belt is going to rust, your wheels are going to be deflated or whatever. A lot of things can happen with it if you don’t maintain it. So, we don’t need to upgrade everything all at once, but we can start from someplace. We can do it gradually. But still, WordPress needs to be the platform that leads the charging that, because it’s going to force other developers to do it. It’s going to force hosting companies to start doing it. And it’s not a big jump on moving just that one version, but it’s going to help to move things along faster. Let’s see how it goes in the next few years. But I really don’t expect for WordPress to drop 7.4 for at least a year or two, maybe even more.

[00:23:24] Nathan Wrigley: I loved your rebuttal of my bike analogy there. That was perfect. That’s exactly right. The bike will rust, the wheels will be deflated and all of that, yeah. So we need to drag the WordPress users along.

Now, in your presentation, you mentioned something that I have never used, the Vulnerability Lab plugin, which you used to demonstrate the attack. Can you just tell us a little bit about that? Because I’d be curious to follow that up, and maybe some people listening to this would too.

[00:23:47] Milan Petrović: I started it for, created for this talk specifically to add few examples and to run the code that is going to show those things if you run the plugin on the old version and the new version of PHP. And I do plan to expand on it because there are a lot more PHP security elements that can be demonstrated in that way.

So it can show you, you have like a, in many cases the same code, but if you run it on one platform, you’re going to get one result. And if you run it on the newer one, you will get something different. So it’s useful to show, and some of those changes are quite small, those attributes that you can add to the code are very, very small, but they can really help you to improve security of your plugin.

And there are more complex security measures that can be implemented, but the format of the talk wasn’t really suitable to mention everything. But this was like something to get you started on the path of discovering what else PHP 8 can offer, when it comes to improving the security of the plugins and what possible exploits and vulnerabilities are there.

I try to use some obvious things that are very easy to spot. And I’m sure I did made some of those errors myself in the past. So some of those examples are something that I dealt with when I was upgrading my code. So I’m sure that a lot of people can see similar problems in their own code, and similar kind of solutions that can help them to overcome those and to make them much more resilient in the future.

[00:25:17] Nathan Wrigley: So is your plugin designed primarily, would you say for developers in mind, or is it something that just a typical end user may get some mileage out of?

[00:25:26] Milan Petrović: No, it’s more for developers that they can see, they can run that code and see how it behaves on the old version and the new version to demonstrate some of those things. And I will definitely expand it to include more examples in the future. Even for myself to like a document, what can happen if you run something in the old version, and the new version?

I had some suggestions coming to me like, maybe like a pattern library that is going to show what is the pattern that we use with old PHP and how to improve it with a new one, and document which version of PHP is going to support it, and how it’s going to improve the code.

[00:26:01] Nathan Wrigley: So is the idea then that you would instal it on various different, let’s say that you’ve got a live site and you’ve got, I don’t know, a development site and another development site, is that you would put it on each of those, different PHP versions, and just sort of compare and contrast what.

[00:26:16] Milan Petrović: Yeah, that can be used.

[00:26:17] Nathan Wrigley: Yeah, in that way. And what’s the reporting that you get? Is it kind of error logs, you know, that only a developer would be able to understand, or is it in plain language that somebody like me could understand?

[00:26:26] Milan Petrović: Right now it’s a bit technical because if you run a certain part of the code, some of those elements do have a visual component in the admin section. You will see, one of the examples, if it’s run on PHP 7.4, it’s going to result in a fatal error for sure, depending on the server settings. And if you run it on the new version, you will get a full code running and executing as expected.

So it’s a bit of a development thing that developers can use themselves to show maybe to potential clients or to website owners what is going to happen if they continue to run the outdated versions of the PHP. So it’s not just, yeah, the PHP 7.4 is bad, but here it is, why it is bad actually.

[00:27:12] Nathan Wrigley: Okay, that’s a really interesting use case, isn’t it? So if I’m an agency owner and I’ve got, I don’t know, a client over here who is absolutely wedded to this plugin, this calendar plugin say, and we know that the development of that plugin has ended years ago, then trying to persuade that client to find something new, or have something new built is difficult.

But with the capabilities of the plugin that you’ve created, you’ll be able to show in a sort of readable human way, okay, right. That’s all very well, but we’ve got to get onto PHP 8.0. And when we do that, this is going to happen.

So that’s actually quite a useful tool for agencies to be able to dangle things in front of the noses of their clients. Potentially, I don’t know, get some new work out of it as well, because there’s this extra work that needs to be done to bring it up to the modern standards.

[00:28:01] Milan Petrović: Yes. And one example especially demonstrates not only security, it demonstrates the performance. It shows you how much memory that piece of code is using on old version. Almost half the memory is going to be used less with a new version. So that’s very on the nose demonstration on security, and the performance in the same time. So things like that can help. And I will definitely try to invest more time in showing more examples and anyone can contribute.

It’s a plugin available on GitHub, so any contributions in that regard are welcome. And we can maybe all work to create like a list of patterns that are something that a lot of people can use, and show different people how the PHP can help them move along.

And again, I don’t want to sound like we don’t need whatever WordPress is doing. We still need to use all the security enhancements that WordPress has built in the Core. Escaping, sanitisation. All that is still very important because you cannot solve everything by upgrading PHP and upgrading your code to use some of the PHP features. There are still a lot of security elements in WordPress itself that are very important and should not be replaced, or removed, from the code. There are patterns that are crucial to ensuring the security is on a top level. So combination of what WordPress already has, plus everything we get with the newer PHP is something that we should strive in the future, and to make things better.

And it’s not that complicated to start with the process. You can start upgrading small things. You can start with stricter typing. You can start with very small changes, and then gradually you can add those new attributes. You can replace some of the functions that you may be used with old version of PHP, but there is something better in the new version. So that’s something that everyone can do. Do a bit at a time so not everything at once. Spend time and make some gradual upgrades, and that’s going to help moving along.

[00:29:57] Nathan Wrigley: You are obviously here to talk about where PHP meets WordPress, but presumably you, yourself are gaining intel from the PHP community. Is there a resource, like a central PHP resource that you would direct people to, or would you rather steer them towards kind of WordPress resources? The things that people are doing in the WordPress space and the hosting space. There’s not really a question there, but it’s more where do you find your information? Where’s the most reliable place?

[00:30:25] Milan Petrović: You need to check everything. PHP website is a really good resource to find the information about what’s coming in the next version of PHP, because the preparations take up to a year to release a new version of PHP. So they’re now on a cycle that every December we get a new feature version. So in December this year, there is going to be PHP 8.6. And you already know most of the things that are coming to that version. You have the detailed list of changes for every PHP version. And that’s something that any developer should look at, and to see maybe something that will drive them to upgrade.

In the current usage of third party libraries, there are a lot of libraries used in PHP that have moved on beyond 7.4. There are a lot of libraries that now require 8.1 or 8.2. If you depend on some library for, I don’t know, parsing URLs, or doing something else, something for security, something for whatever. You may face the problem that if you want to use the latest version of that library, you will need to have the newer PHP version. So you are kind of forced to upgrade your plugin requirements to meet with the requirements of the third party libraries.

And outside of WordPress ecosystem, those libraries will move much faster with the adoption of newer PHPs versions than WordPress itself, because they don’t deal with millions and millions of websites that are affected. They are creating the library the best way they can. And they want to ensure that their library is secure, that their library has access to the latest features. So they are going to bump requirements for those libraries on their own. And if you are depending on it, you need to do it yourself for your plugin. So it’s kind of, those libraries are kind of forcing the hand of some developers to upgrade, even if they maybe are not ready at this point to do it.

[00:32:15] Nathan Wrigley: Yeah, it certainly sounds like there’s no lack of information out there. If you make your business to find the information, then it’s all there. You’ve just got to make the effort to go and find it.

I’ve kind of run the gamut of everything I wish to ask. However, I’m very conscious, as I said at the beginning, that this conversation is a little bit above my pay grade. Is there anything that I missed that you wished you had been asked that you wanted to get across?

[00:32:38] Milan Petrović: No, I think we covered a lot of stuff in that.

[00:32:42] Nathan Wrigley: Well I’m glad to hear it. That’s great. Yeah, thank you.

In which case, I’m assuming, given that you’ve come to an event like this and you’ve put a plugin on GitHub, you are sort of semi available, or very available, to have conversations with people around this. And if that’s the case, where’s the best place to find you online? A website or an email address or a Twitter handle or whatever.

[00:33:00] Milan Petrović: We included the slide with the contact information. So even the email, if someone wants to get more information, they can do it on various social networks as well. So any input about all that is welcome. And I’d be happy to help if someone needs, some pointers or additional information to get started with all this.

[00:33:21] Nathan Wrigley: Well, thank you. That’s very much appreciated. As always, if you go to the show notes on the WP Tavern website and click on the episode involving Milan, you’ll be able to find, buried probably towards the bottom, all the different bits and pieces, the wordpress.tv video that will go with his presentation and various other links that have been discussed during the course of this episode.

So with that said, Milan, thank you so much for chatting to me today. I really appreciate it.

[00:33:47] Milan Petrović: Thank you. It was really great, and I appreciate your invitation for the interview.

[00:33:52] Nathan Wrigley: You are so welcome. Thank you.

[00:33:53] Milan Petrović: Thank you.

On the podcast today we have Milan Petrović.

Milan has been deeply immersed in the WordPress ecosystem since 2007, developing an array of plugins, especially for expanding bbPress forums, and running his own company creating plugins before joining the Freemius team as a full stack developer. With nearly two decades of hands-on experience, Milan has witnessed firsthand the evolution of both the WordPress and PHP landscapes.

Many WordPress users may be only partially aware of PHP, perhaps they’ve noticed version numbers in their hosting panels, but few of the millions of WordPress users understand the real impact that PHP versions have on the security and performance of their websites. Milan is here to shine a light on why embracing newer versions, like PHP 8.x, isn’t just good practice but a crucial step for security and efficiency.

Milan begins by recounting his journey through WordPress development. The conversation gets into the heart of his recent WordCamp Europe presentation, which tackles how legacy PHP code exposes sites to thousands of open bugs and vulnerabilities, and why relying on old versions is, as he describes, “an active invitation for automated exploitation.” The discussion explores the contrast between running legacy code and using the “native shields” of modern PHP, and highlights how PHP 8.x not only closes security holes but also delivers major performance boosts, reducing memory usage and accelerating speed.

If you’re wondering why you should care about the PHP version your site is running on, or you’re a developer interested in practical ways to harden your code, Milan unpacks both the existential risks of outdated PHP and the step-by-step benefits for hosts, agencies, and plugin developers alike.

He introduces his Vulnerability Lab plugin, designed for developers to see first-hand how code exploits play out differently across PHP versions, and makes the case that modernising can happen gradually, one update, one plugin at a time.

If you’ve ever questioned how your hosting choice or plugin stack could affect your site’s future, or you’re ready to take the first steps towards building more secure and future-proof WordPress products, this episode is for you.

Useful links

Secure-by-design: hardening plugins with PHP 8.x – Milan’s presentation at WordCamp Europe 2026

bbPress

Dev4Press

Freemius

 Vulnerability Lab plugin on GitHub

💾

#224 – David Snead on Building Trust and Collaboration in the Hosting Industry With the Secure Hosting Alliance

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, building trust and collaboration in the hosting industry with the Secure Hosting Alliance.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you, and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.

So on the podcast today, we have David Snead. David has been involved in the hosting industry since 1999, starting out as legal counsel for one of the earliest shared hosting companies, and going on to work with over 50 others. He helped found the i2Coalition, serve as in-house counsel for cPanel and WebPros, and now leads the Secure Hosting Alliance.

If you’re listening to this podcast, I’m sure that many of you will have worked closely with hosting companies. Perhaps you run an agency, or business, that depends on the reliability, ethics, and security of hosting providers. David is here to talk about cross-industry collaboration in the hosting world, specifically around improving security, professionalism, and communication between hosts.

The conversation focused on why, and how, the Internet Infrastructure Forum, or IIF, is building a framework for real-time intelligence sharing and abuse reporting, aiming to help the entire ecosystem detect and prevent attacks faster than adversaries can adapt.

David talks about the challenges hosting companies face, especially smaller ones, in keeping up with security, and how this evolving project hopes to ease this by sharing actionable, non-proprietary abuse information across registrars, hosting providers, DNS services, and more.

He discusses the growth of both the Secure Hosting Alliance and the IIF, the business case for collaboration, and the nuances of legal and technical information sharing across borders.

If you’re in hosting, run a web agency, or just want to know how the backbone of the web is working to stay more secure and connected, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so, without further delay, I bring you David Snead.

I am joined on the podcast by David Snead. Hello David.

[00:03:20] David Snead: Hello.

[00:03:21] Nathan Wrigley: Very nice to have you with us. David’s got a really interesting background, and a really interesting, I’m going to use the word project. I don’t know if that’s the right word. It feels like it’s got more solidity and it’s got a lot more history than that. It’s something which is, I think going, but we’ll find out a little bit more about it. It’s all about the hosting industry and trying to get hosts to, I guess communicate with each other in ways going forwards.

[00:03:44] David Snead: That is a part of it. There are really two goals and one is to level up the ethics and professionalism in the hosting industry. And the second is to facilitate more comradery and interaction among hosts. Something that folks felt occurred in the early 2000s, and with all the consolidation that occurred went away. And so that’s something that we’re also trying to facilitate.

[00:04:16] Nathan Wrigley: Okay. So given that we’re going to be talking about hosting, I guess it’s a good idea to paint your credentials and find out a little bit more about you. So a short opportunity to just tell us a little about you and your background in WordPress and hosting specifically, I suppose.

[00:04:29] David Snead: Sure. So I have been working in the hosting industry since 1999. As I often say, I was working in the hosting industry when hosting was cool. It is not so cool anymore. In fact most people don’t really pay attention to it.

You know, and I started as a lawyer for a hosting company, and I was in-house counsel for a company that actually owned a hosting company and was one of the earliest hosting companies that specialised in shared hosting. And so I was their general counsel. And for some reason it stuck, and I’ve just kind of turned it into a career.

So after that I had a private practise as a lawyer and I worked with probably 50 different hosting companies, mostly writing policies that nobody ever reads, which makes me super fun at parties.

And then from there, my friend Christian Dawson and I formed the i2Coalition as a response to some legislation in the US that would’ve been kind of the death nail for internet providers. So we started the i2Coalition. I then went in-house for cPanel and worked at cPanel and WebPros for 10 years, and then started the Secure Hosting Alliance.

[00:05:52] Nathan Wrigley: Okay. So you’ve got all all the history. That’s pretty good. You know, if we’re going to talk about hosting.

[00:05:57] David Snead: All the hosting history in one person. That’s kind of a very scary idea, no?

[00:06:02] Nathan Wrigley: But that’s excellent. So do you still offer counsel? Is that still, so you haven’t sort of sidestepped and do half of the week on a sort of more technical basis? It’s still the legal side that you’re involved in.

[00:06:13] David Snead: I do. Right now I’m doing mostly M&A work for, it’s weird. So I don’t know if anybody has ever said this to you before, but web hosting is kind of like the Hotel California. It’s like, once you start in the web hosting industry, you never leave. And so I have all these clients from 15 years ago who are now running like little baby hosts, and they’re talking to bigger hosts and they want to get acquired. So I’m doing some of that now. I am not writing any of the policies that nobody ever reads because that was just, I did that for too long.

[00:06:51] Nathan Wrigley: There were too many moments parties.

[00:06:53] David Snead: Yes, exactly. Yeah.

[00:06:55] Nathan Wrigley: Okay, so I’m going to read into the record the title and the blurb that went with the presentation that you are doing or done.

[00:07:02] David Snead: I did it yesterday.

[00:07:03] Nathan Wrigley: Okay, we’ll get into that in a moment. So the title is coordinating the fight, cross industry collaboration, and the blurb goes as follows. WordPress hosting threats cross company lines. When one provider falls victim, the entire ecosystem suffers. This session explores how the Internet Infrastructure Forum, or IFF, enables hosting providers, registrars and registries to coordinate abuse response through real time intelligence sharing. Learn how operational collaboration helps responsible operators detect and stop attacks faster than adversaries can adapt. And why working together produces results no single provider could achieve alone.

When I read that, immediately was, yeah, that’s a really sensible idea. Why are we separately, as hosting companies, I say we, I mean the hosting companies. Why are they all trying to do the same work over and over again, separately? When presumably this aspect of the work, the security bit is something they all have in common.

[00:08:05] David Snead: Right? So that’s the fundamental question, right? So the IIF is a voluntary organisation that is made up of everyone in the infrastructure stack. So from registrars, registries, DNS providers, hosting providers, cloud providers, everyone in the stack. So it is facilitated by the Internet and Jurisdiction Foundation. They’re based in Paris, and they’re the actually the secretariat for it.

And what it’s designed to do is create a common way for everyone who’s in the infrastructure stack to share information about abuse and abuse issues. And it’s one of the fundamental problems that you referred to is everybody is operating in a silo, right? And that’s mostly because that’s the way the internet is architected, right?

So the internet is architected, so it’s distributed, right? Registrars and registries basically do their own thing with domain names. They might have a small hosting component or maybe a cloud component, but by and large, all they do is domain names.

Hosting providers probably resell domain names, but they’re not part of that industry. And so how do they all coordinate? And that’s what the IIF is trying to facilitate, is more information sharing among the participants.

[00:09:39] Nathan Wrigley: Well I imagine some of the hosting companies are probably fairly good. You know, they’ve got a giant customer base. Let’s imagine hosting company X over there, they’ve got millions of customers. They’ve got a huge budget that they can put over to, let’s say, security things. Well that’s all well and good, brilliant. But then there are other companies who are much scrappier. You know, they maybe have only a few thousand customers. And so their budget for the exact same work is going to be reduced.

How will this work? Is it going to be like a subscription service basically? Will you have a membership, which is in some way equal to the number of clients that you’ve got? Will there be some expectation that, okay, we’ll look at your revenue, your membership will be equivalent to a percentage of your revenue? How will that all work?

[00:10:20] David Snead: We don’t know. This is a very early stage project. Right now we are in a prototype phase where we have just figured out what information folks should submit to the secretariat.

So the way it works is, you submit the information that you collect for a particular abuse issue to the secretariat, who then enriches it with all the other information that’s been submitted and sends it to the right person.

So a great example is, let’s say a registrar reported a phishing domain. They turn off the phishing domain and they have maybe a timestamp, an IP address where it was submitted from. They submit that to the secretariat, who then finds the hosting company who is providing the services for the hosting and says, this came in about this particular site. Can you take action on that? So that’s the way it works.

Right now it’s very early stage. It’s in the first phase of a test, and we’re going to look at whether the way we’ve architected it, or the way the group has architected it, actually makes sense.

[00:11:39] Nathan Wrigley: Is this going to be then a sort of slow on ramp whereby you bring a few companies in at the beginning, hopefully. And then one or two more and iron out the wrinkles, and then some more and some more? Because I imagine, if you just threw the switch, everybody’s in, a lot could go wrong at that point. And I’m guessing there’s going to be more of a slow on ramp.

[00:12:00] David Snead: So you’ve pointed out my particular frustration with the IIF, and the reason that the secretariat is moving slowly, right? So fortunately, or unfortunately, based on my cultural background, I’m just sitting here going, this needs to move faster. We need to have everybody involved, we need to have all the hosts involved, we need to have all the registrars and registries. And other folks who are a little bit more skilled in this type of work say, no, we need to figure out what we’re doing and that requires a small number of people.

The phase that we’re in right now is looking for more folks who are interested in sitting at the table and being part of the discussion. Particularly in the hosting industry and in the web design and marketing industry. Those are folks who don’t generally participate in these kind of industry led collaboration exercises. And that’s the reason that I’m at WordCamp, is to talk to web designers, marketing agencies about why they should participate in something like this.

[00:13:13] Nathan Wrigley: So this really isn’t bound in any way to WordPress, is it? It just so happens that WordPress has a significant chunk of the internet, so this is a good place to start. But if you happen to be a, I don’t know, Drupal user, or you’re just into writing PHP code or whatever it may be, this is still applicable. There’s no real WordPress layer to this. This is just a good place for you to come because, well, there’s probably, what, 30 hosts, 100 yards away from us out there.

[00:13:37] David Snead: I know. And I haven’t seen all of them yet.

[00:13:39] Nathan Wrigley: Yeah, there’s work to do. But agnostic to any platform, basically.

[00:13:42] David Snead: It is completely platform agnostic, yeah.

[00:13:43] Nathan Wrigley: Okay. Okay, that’s interesting. But WordPress is a, is certainly a good place to start.

Now, I’m imagining, if I was a hosting company and I was the chief executive, I definitely have some questions for you in terms of, okay, we’re going to share our valuable intel with you, what are you going to do with that? How can we trust you? How do we know that the sharing is going to be done effectively and what have you?

So I guess really what I’m getting to is, what is the assurances or checks and balances that you, in the end, will hope to offer the host? That you can assure them that, look, if you hand us this body of work, you don’t need to think about it again. You can trust us to do it honourably, effectively, collaboratively. You get where going.

[00:14:26] David Snead: Yeah, yeah. And I suspect that you wanted to be a lawyer at some time, because that’s one of the issues that we’re facing. Information that can be shared freely, as an example, in the United States, might not be capable of being shared so freely in the European Union, or in Brazil, or in India or someplace like that.

So one of the things that’s being done, not by me, but by another group, another working group that’s part of this, is analysing the legal issues around information sharing.

The information that’s being shared, to answer the proprietary and confidentiality question, is not proprietary or confidential information. So it’s things like timestamps, domain names, IP addresses for the initial abuse submission. Things like that that really don’t indicate some sort of company confidential information. And it’s further abstracted into xarf, which is a language that’s used for abuse reporting, that we all can share. And so I think that the only thing that would be of concern is whether that information is personal information that’s subject to jurisdictional restrictions around the world.

[00:15:48] Nathan Wrigley: Would the idea be that this organisation would do the remedial work? So is there any notion that, let’s say for example, some sort of security problem was discovered by hosting company A over there, and they share that intel with you. Maybe the question is kind of asking, will you then appoint people to figure out what the patch is for that? Or is your idea just to, oh, red flag, we’ve got this problem, now you all know about it. Is it just information sharing as opposed to fixes?

[00:16:17] David Snead: Yeah, it’s the latter. So the thing that we’re solving for right now, so there’s just one issue that, one abuse issue, that we’re testing out and it’s issues related to fake shops. And so the fake shop issue is the test abuse issue for the project, and where folks are sharing information. It’s a particular problem right now with credentials harvesting. And so that’s what we’re trying to look at.

[00:16:43] Nathan Wrigley: And how has the conversations that you’ve had thus far, how have they gone? Has this been warmly received or are you facing a little bit of pushback?

[00:16:50] David Snead: So, look, I’ll be very direct with you. If something isn’t just an immediate threat to them, it’s very difficult to conceptualise why you should participate. And I am pretty used to answering that question simply based on the political work that I do with the i2Coalition. But once you talk about, so let’s use fake shops as an example. Fake shops, and you’re providing services to fake shops, actually has an impact on your bottom line.

So if you are providing, let’s say, payment processing to an entity that is running a fake shop, it very easily can make your credit card processing charges higher. It ends up eating bandwidth. It will tax your abuse resources.

One of the things that you referred to initially is, you know, larger hosts have a lot of money. I wouldn’t say they have a lot of money, but they have more bandwidth to handle a vast fire hose of abuse issues. Most smaller hosting companies might only get five or six abuse issues in a month. But if you have a fake shop, that’s going to generate a huge amount of abuse, and it’s taking away resources that you can use to actually grow your business. So that argument actually is relatively persuasive in getting folks to pay attention.

I find that the business argument around abuse is a much more compelling discussion than kind of moral persuasion. I don’t think moral persuasion works in the context of a community that is trying very hard just to keep their heads above water.

[00:18:42] Nathan Wrigley: It feels to me from what you’ve just said, and I could be reading too much between the lines, but it feels to me as if a good target audience would be smaller hosts to begin with, simply because they’re probably going to be more receptive because they have less bandwidth themselves. And so would welcome anything that can make the burden of sharing this information easier. So 10 of the small hosts combined is, well, it’s much bigger than each of them individually would be, whereas I suppose you’ll have to get a critical mass of them on board until maybe some of the bigger hosts start to look at you with favourable eyes, let’s say that.

[00:19:15] David Snead: Well, so we have some pretty large hosting companies who are participating. So as an example, both GoDaddy and Newfold are participating. But we also have smaller hosts. But I agree with you, the information that’s being provided, particularly since it is actionable, realistic information that can be adapted for bespoke systems, is invaluable, right?

So if you only get five or six abuse complaints and you get an abuse complaint, and you can go to the secretariat and say, we got a complaint about this domain, and the secretariat says, here’s what the registrar did. Here’s what Cloudflare did. Here’s the information they provided us. And you can use that to make a decision on how to address that problem. It saved you hours and hours and hours of research time.

[00:20:09] Nathan Wrigley: Technically speaking, what would the conduit of information both toward you and away from you look like? So if I’m hosting company X, how are you imagining that I will supply you with that information? But also, if I’m just looking for information from you on a daily, weekly basis, whatever it may be, how do I receive that? Is this like a, I don’t know, a website or an API or?

[00:20:33] David Snead: It’s an API. So it’s a file. It’s just a general file download.

[00:20:37] Nathan Wrigley: Right, okay. So it’s readily available 24/7?

[00:20:40] David Snead: Right. That’s the goal. Right now it’s not, but the goal is to kind of figure out a way to make something like that possible.

[00:20:47] Nathan Wrigley: Yeah, okay. I also suppose that the hosting companies, whilst this is good for their business if they can minimise costs and hand a lot of this work over to you, there’s a part of them which would also probably like to put some sort of badge on their website to say, this is what we’re doing. We’re part of this alliance, for want of a better word. Is that something that you are looking to develop as well, you know, some sort of credentialing system to demonstrate that you’re in this?

[00:21:12] David Snead: So that’s not something that the IIF is working on. It’s something that the Secure Hosting Alliance does. The Secure Hosting Alliance has a trust seal that we give to hosts who fulfil our Trust Seal Certification provisions. But that’s not something that the IIF does.

Talking about like why, other than business reasons, folks should participate in this, one of the things that is going on that I would suggest that most hosts know about, is there’s a little bit of a moral panic going on in the world about what contents you have. And regulation is actually a very real thing for the hosting industry, who has not ever been regulated. This is the time where you can say, hey, this is what we’re doing, right? We’re dealing with issues. This way a trust seal is the same thing, right? It’s something that you can say, we are actually taking steps to make the internet a better place.

[00:22:18] Nathan Wrigley: I think if you are a general agency owner or, I don’t know, just a freelancer, hosting is one of those things that you, once you’ve done it once, you’re in it for the long haul until something goes wrong. But you’re also browsing around for any tiny indication of why is this host slightly different? You know, what is it that they’re doing that, I don’t know, is faster? What is it that they’re doing that’s more secure? So it feels to me if you had a credentialing system and I began to hear about it and see it pop up again and again, it would be one of the metrics which I would weigh up when looking at hosting.

[00:22:51] David Snead: I would think so. One of the things that a trust seal does is it indicates that there’s been some vetting of the host. That someone has determined the things that are important to the hosting industry and are important to the web design industry. The agency industry are also important to the host.

Great example of that is one of the provisions of the Secure Hosting Alliances’ Trust Seal Certification is that a contract is presented to the customer before they sign up, which is super customer friendly.

One of the things as a lawyer that you hear about all the time when people are dissatisfied with their services is, yeah, well, I never saw that contract. Or it was just a hyperlink in an email that I got. That’s one of the differentiators for a Trust Seal certified host is that the contract is actually presented to them, to the customer beforehand.

[00:23:57] Nathan Wrigley: So in terms of the WordPress crowd, is this a thing that you are pitching only to hosts? Like when you step out of here, are you trying to have conversations only with hosts? Or is there some bit of the WordPress community, the freelance, the agency owners? Are you trying to communicate with them just to scope out what they need?

[00:24:15] David Snead: So for both the Secure Hosting Alliance and for the IIF, it is that. I really enjoy talking to agencies and developers about whether this is important to them, or why it might be important to them.

[00:24:31] Nathan Wrigley: In terms of how long this project’s been going, I’ve only heard of it because of your participation here, but I don’t know if you’ve been banging this gong for a decade or, I mean you’ve been in the industry for long enough to have been banging it for decades. Is this a new initiative or is this something which has a long and storied history?

[00:24:49] David Snead: So the Secure Hosting Alliance has only been active for a year, a little bit over a year. I’ve been talking about abuse for a long time, but the Secure Hosting Alliance has only been around for a year.

[00:25:01] Nathan Wrigley: And have you, in that year, got any intuitions that you’ll be here for another year? Is it basically going in the right direction?

[00:25:09] David Snead: It is going in the right direction. So we started out with two or three charter members. We now have 25 hosting members. We have three security vendors who are members as well. We have, I think, 17 Trust Seal Certified members, and we’re launching in 2027 a trust seal for security vendors who provide services to hosting companies.

[00:25:40] Nathan Wrigley: I know that several owners of hosting companies listen to this podcast. They may very well be the people that you’ve spoken to already, but if they are not, and they are people who would like to investigate this further, I suppose the thing that’s going to be in their head is, okay, Nathan and David, you’ve explained what I’ll get out of it, what do I need to put into it? So is this an annual financial commitment? How does it all work from that point of view?

[00:26:02] David Snead: Yeah, so you become a member of the i2Coalition. And so the Secure Hosting Alliance is a working group of the i2Coalition. So you would be a general member and you would participate in the Secure Hosting Alliances’ working groups. You also have the ability to participate in the i2Coalition as a whole, which is a much larger trade association that represents almost everyone in the internet infrastructure vertical. Mostly doing policy work, primarily in the US and the EU. Although there’s, we’re doing some work in India right now as well.

[00:26:40] Nathan Wrigley: And does membership allow you to steer the future of the project? I know that lots of chefs in the kitchen results in terrible food, but that, I fear, is something that could happen. You’ve got 87 members, 260 members. And then the 260 members all start to bicker and, you know, we want this, no. You see how it goes.

[00:26:59] David Snead: I do.

[00:26:59] Nathan Wrigley: What’s the position there? You know, is there sort of gated levels of membership? How are you organising all of that?

[00:27:04] David Snead: There are not. The membership is based on self-reported revenue. The membership is not horrifically expensive from my perspective. And I think that that, most of our members would say that it is, it’s actually relatively affordable, particularly for the small to medium sized hosts. And registrars or design agencies, anyone who’s participating.

The question about, who’s running the show, comes up quite a bit. We haven’t really faced that issue, particularly in the Secure Hosting Alliance. Folks seem to get along. But the organisation runs on the idea of rough consensus. And so decisions end up not being controlled by one member or not. Some of the i2Coalition has some very large companies who everybody knows about, who get along with startups, and folks against whom they compete directly. And policies still get made. The organisation still moves forward.

[00:28:11] Nathan Wrigley: Yeah, I guess you’re in a space where, obviously all of these hosting companies commercially are vying for everybody else’s business. But in this particular situation, that is not the case. Nobody’s vying for their websites to be less secure. They all want the same level of security. So at least in that sense, you would hope that consensus could be maintained even if, commercially, the two companies that are in the room, the 10 companies that are in the room might be commercially at loggerheads with each other. At least on this they could agree. That would be the hope, I suppose, anyway.

[00:28:47] David Snead: It seems to be, not only the hope, but the actual way that things work. You ask about how compromise is reached. What comes to mind is I have a much different concept of privacy than, particularly when I was at WebPros, than other folks in the i2Coalition had. And another company just called me up and we worked through our disagreements about how privacy should be handled within the i2Coalition and were able to move forward.

The industry I’ve found to be hugely collaborative, particularly the hosting industry. Everybody knows what their competitor is doing. But when it comes to addressing an issue like, how are we going to deal with abuse as a community? Folks come together. CEOs of hosting companies while they compete tend to be relatively good friends.

As I said at the very beginning, it really is like the Hotel California, right? You come in as a CEO of a hosting company, you grow it and you sell it to another company. All of a sudden you’re at the bottom again with a server in your grandma’s basement, you know, trying to start again.

[00:30:08] Nathan Wrigley: It’s a really curious effort. I suppose really at the bottom of this entire podcast is your endeavour to be heard and to reach out and get some conversations going. So with that in mind, where do people find the information about this? So maybe there’s a website that we could mention. But also, is there a specific place where you hang out? Is there a place where you would like to be contacted most?

[00:30:33] David Snead: Sure. So our website is hostingsecurity.net. I’m not too afraid of getting too much spam. So folks can email me at snead@i2coalition.com And the two is the numeral two. So it’s snead@i2coalition.com. And I’m happy to answer questions.

In terms of hanging out, I am at most industry conferences in the hosting industry. In the WordPress industry, I’ll be at WordCamp US. We also participate very heavily in ICANN. So there is an i2Coalition member at every single ICANN meeting.

[00:31:12] Nathan Wrigley: So if you go to wptavern.com and you search for the episode with David Snead, S-N-E-A-D, you’ll be able to find those details. I’ll put everything into the show notes. So anything that I missed? Was there a particular focus that we didn’t touch?

[00:31:26] David Snead: No, this is actually one of the most thorough podcasts I’ve been on recently.

[00:31:31] Nathan Wrigley: That’s love to hear it. Well, David Snead, thank you very much for joining me today.

[00:31:35] David Snead: Glad to be here. Thanks for having me.

On the podcast today we have David Snead.

David has been involved in the hosting industry since 1999, starting out as legal counsel for one of the earliest shared hosting companies and going on to work with over 50 others. He helped found the i2Coalition, serve as in-house counsel for cPanel and WebPros, and now leads the Secure Hosting Alliance.

If you’re listening to this podcast, I’m sure that many of you will have worked closely with hosting companies. Perhaps you run an agency or business that depends on the reliability, ethics, and security of hosting providers. David is here to talk about cross-industry collaboration in the hosting world, specifically around improving security, professionalism, and communication between hosts.

The conversation focused on why and how the Internet Infrastructure Forum (IIF) is building a framework for real-time intelligence sharing and abuse reporting, aiming to help the entire ecosystem detect and prevent attacks faster than adversaries can adapt.

David talks about the challenges hosting companies face, especially smaller ones, in keeping up with security, and how this evolving project hopes to ease this by sharing actionable, non-proprietary abuse information across registrars, hosting providers, DNS services, and more. He discusses the growth of both the Secure Hosting Alliance and the IIF, the business case for collaboration, and the nuances of legal and technical information sharing across borders.

If you’re in hosting, run a web agency, or just want to know how the backbone of the web is working to stay more secure and connected, this episode is for you.

Useful links

i2coalition website

Secure Hosting Alliance website

💾

#223 – Ivana Ćirković on How WordPress Credits Bridges Education and Industry in the WordPress Ecosystem

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress, the people, the events, the plugins, the blocks, the themes, and in this case how WordPress Credits bridges education and industry in the WordPress ecosystem.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.

So on the podcast today we have Ivana Ćirković. Ivana is a digital marketer with 18 years of experience working both in and out of the tech industry, and currently leads marketing at WPBakery. She’s an active participant in WordPress events, having attended, and spoken at, numerous local and international word camps over the years.

In this episode, our focus is on the WordPress Credits initiative. We learn how this program, launched by the WordPress Foundation, connects students with real world opportunities to contribute to the WordPress ecosystem, earn certifications, and increase their competitiveness in the job market.

Ivana discusses her own experience as a WP Credits mentor, working with students as they learn about digital marketing, remote work, and other open source contributions. We explore, how universities can modernise their curriculums, and real world value for students by participating in the initiative, and how businesses can get involved, not just to support the community, but to help shape and discover future talent.

The program’s evolving structure also gets attention, and we learn how students are guided through hands-on activities such as translation or documentation, and how their progress is tracked publicly via profiles on wordpress.org. Ivana shares the opportunities and challenges for both educators and businesses with thoughts on accountability, mentorship, and the need to bring new faces into the WordPress community.

If you’re interested in the future of WordPress, education, or bridging the gap between academia and industry, this episode is for you.

If you’d like to find out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Ivana Ćirković.

I am joined on the podcast by Ivana Ćirković. Did I get that right?

[00:03:14] Ivana Ćirković: Yes. Excellent.

[00:03:16] Nathan Wrigley: Thank you. This is my first interview at WordCamp Europe 2026. I’m guessing because we’re on the first day of the event and it’s quite early in the morning, it’s 10 in the morning, I’m guessing you cannot have done your presentation yet?

[00:03:30] Ivana Ćirković: Not yet. Tomorrow.

[00:03:32] Nathan Wrigley: Do you get nervous with these kind of things?

[00:03:34] Ivana Ćirković: I get nervous all the time. I’ve been doing this for 12 years, it never gets easier. It is what it is.

[00:03:39] Nathan Wrigley: Well, the presentation that you are doing is going to be the focus of what we’re talking about today. So do you just want to tell us a little bit about the topic that you’re talking about, but also just give us a bit of a general bio about who you are and what you do. So just tell us about you and about your presentation basically.

[00:03:56] Ivana Ćirković: Okay. First thing first, I would like to introduce my presentation, or the talk, that is build up around WordPress Credits initiative, which is something that WordPress has rolled out late last year in December. And I applied to be a mentor to support students into their entering into WordPress. Got accepted, did my courses, passed them and started working with students on their, first entering the WordPress society, how everything works, contributing.

And out of all of this, I came up with the idea of sharing the story about WordPress Credits. What it is, why it is important, not just for the WordPress community, but also for universities all around the world for businesses to support, because there is an angle and huge opportunity for them too. And hopefully inspire people to join and become part of it more.

As far as I’m concerned, my name is  Ivana Ćirković and I am a digital marketer for 18 years. I’ve been working inside tech organisations, tech industry, but also outside of it. So I’m the multiverse. And lately, for past couple of years, I’ve been working in WPBakery, in marketing their product, and talking to people, sharing knowledge of what we do, how we do it, and so on. In the meantime I am attending many, many WordCamps, local and international ones, giving lectures, giving talks about digital marketing and all things related.

[00:05:39] Nathan Wrigley: So are you here at this event, not just to give your presentation, are you also here on behalf of WPBakery to represent them and the products that they have as well?

[00:05:47] Ivana Ćirković: Yes, we are sponsors. I am speaker, I was table lead for marketing on Contributors Day. So we are wide into the ecosystem.

[00:05:56] Nathan Wrigley: I have to say, having only been in this event space for about an hour, I’m actually deeply impressed by this particular event. It really is a gigantic venue. It’s so pleasurable as well to see the WordPress community in such large numbers here. And so we’re looking forward to a really good event.

Okay, let’s kick off with the topic at hand then. So it occurs to me that many people listening, whilst they’re using WordPress and they’re kind of, I don’t know, they’re building websites for people, and they’ve got products and plugins and they’re just general users. It may be that the community piece, and the educational piece, is nothing that they’ve heard of before. So would you just tell us a little bit about what WP Credits is as far as you’re concerned, just to give us that broad background of what it is?

[00:06:40] Ivana Ćirković: Okay. So WP Credits program is initially made to bring new young people into the WordPress, to broaden the ecosystem with the new fresh blood, new contributors. And to do so, WordPress Foundation initiated this program to connect with universities all across the world. To connect students to some programs, to learn about WordPress through contribution. For that, they will get graded and get certification, which in the end will help them be more marketable, and have more modern knowledge of what is needed in today’s job market, and to be more competitive and more appealing to potential employers.

So by doing so, WordPress Credits aims to broaden the ecosystem, to strengthen the WordPress community, and WordPress itself. But also to put new generations in more marketable place, and to help them get more profitable jobs.

[00:07:45] Nathan Wrigley: Thank you. That was a really nice summary. In terms of your personal commitment to it and what have you, how did you fall into it as a thing that you were doing? And is this something that you get sponsored for from WPBakery, or is it personal and simply a sort of philanthropic thing that you are doing on the side?

[00:08:01] Ivana Ćirković: Yeah, so basically, I’ve been doing education my whole professional life. So it’s something that comes natural to me. In my local country, in Serbia, I do informal education for high schoolers and primary school’s children about digital marketing, digital literacy. This is like very natural to me. I’m being sponsored by WPBakery to do so.

And the program works like, initiative needs people, needs more mentors to get involved. More than it needs like product and businesses to support with their products. So if there are businesses who are maybe interested in support through their product, know that you need to put your people first to actually get involved and contribute, and then you can offer products as the side piece, so to say.

[00:08:52] Nathan Wrigley: So yeah, it seems that you’ve got a lifelong interest in education as well. Okay, that gives me some sort of hook there.

Okay, if I was to say WP Credits to the people outside, the people who already knew about it, I think would probably peg it as entirely educational in nature, just an education initiative. But curiously, your presentation, the notes that went with that and the blurb that went on the WordCamp Europe website, you kind of make the point that it’s much bigger than that, and you get into businesses and the students themselves and universities.

So the students in universities bit, well, that’s the education piece. But the business bit, what’s going on there? Because I definitely hadn’t drawn that intuition. I thought education from top to bottom. But business, okay, where does that fit in?

[00:09:37] Ivana Ćirković: I will get the hot insights from the talk. So basically, there is more than what meets the eye, so to speak. Businesses have unique opportunity to shape people they want to employ by getting involved as mentors. They also get the chance to see firsthand how those young minds work in real environments, in real contribution. And they get the chance to pick and choose who they want to employ by seeing them work on some real things. Whether it’s documentation, whether it’s translation or programming, developing something, AI.

We need more people who know what they do, although they are young. By having students in this program, they are working on not fictional things, but actual things that really contribute to community and businesses as a whole. By supporting this initiative, businesses then in relations to that can get more insights into who they want to employ. So on top of that, they are building the better market for themselves as well.

[00:10:42] Nathan Wrigley: I guess the student university piece is fairly obvious. You know, WP Credits and the people working on that project communicate with universities, they’re probably easy to find. You know, if you go to a phone directory for example, they’ll all be there. And it’s an easy thing to do. You phone up the university and see if there’s interest. And I know that some universities have taken up the WP Credits program. And it seems to be, as far as I can work out, it seems to be working very successfully.

How are you going to make the connection with businesses? Because that seems like a much more scattered, I don’t know if you’re going to be working with big businesses, you know, huge companies or if it’s going to be kind of more the businesses on the street, the smaller businesses, that kind of thing. So, I’ll just sort of hand it over at that point.

[00:11:23] Ivana Ćirković: So basically, web agencies, businesses around WordPress, we know they have an issue with new employees onboarding last, let’s say three to six months. That cost time and money and other people who are teaching them what needs to be done and how.

Then we have WordPress Credit students who are already doing that junior type of work within contribution. They’re already onboarded through using Slack, knowing how to do remote work, what needs to be done. So businesses supporting WordPress Credits initiative can choose those students and spend less time and money and energy in onboarding them because they already went through that by doing WordPress Credits program.

[00:12:10] Nathan Wrigley: Yeah, I guess if you are a small web agency, it’s highly likely that you won’t necessarily have an induction program finely tuned, so that the young people that are coming through have this sort of specialised system where they can get some accreditation. It’s probably more, okay, I’m going to assign you to John this week and then next week you’re going to go over to Susan and follow what they’re doing.

So is there a sort of structured program that, let’s say a web agency based in London could drop into and receive documentation about? Where are we at with that whole process for the busineses?

[00:12:44] Ivana Ćirković: Yeah, so since this initiative is still fairly new and we already have just one generation of students that are passed the program, this is something in development. So at the moment, we still don’t have like a specific structure that is based just for agencies and businesses in general, but it is something that we are considering and working towards too. So definitely.

On the other hand, the upper management organisational team might not be aware to the fullest what am I about to talk. So it might come as a surprise to them, but also it is something in the works as well. So give us some time and we will come up with something.

[00:13:26] Nathan Wrigley: Yeah, it feels like that would be something really credible. Because if you’re a small business owner, the last thing you want to be doing is kind of wasting time. And onboarding somebody might be something that you’d have to divert weeks into, you know, syphoning employees off, writing documentation, SOPs, those kind of things. And if you could just pick something up off the shelf that was tried and tested over many years, that would actually be really handy. So good luck. I hope that that initiative comes off.

In terms of students, if you were a student, let’s say you are at a university, or you are looking for work, what would you say would be some of the top line items that you would mention as to why WP Credits is worth looking at? Because, you know, if I’m at a university, there’s probably a thousand different things that I could be doing. WP Credits would be in competition with all of those. Why do you think it’s something that young people should be taking care of to look at?

[00:14:17] Ivana Ćirković: Yeah, I would think differently, in that sense. Universities curriculums are outdated comparing to the industry that we are living and working in. So WordPress Credits gives something that is in trend. That is happening now that people are using and working now. So students who choose to go to this program are gaining the most efficient and not outdated curriculum, and things that are being worked on in this moment.

And this is bigger than WordPress. It is initially for WordPress, but the knowledge students get, nobody can take that away. They learn to be outspoken. They learn to use all the necessary remote work tools that is applicable in all the industry.

So we are really encouraging them to be very marketable employees and people who have portfolios, whether they choose that category that brings them portfolio. That is very transparent throughout whatever they do. Because on wordpress.org, every contribution is noted. So they’re building their own business brand by doing WordPress Credits. And in that way they are more marketable and can get more business opportunities.

[00:15:42] Nathan Wrigley: I didn’t realise that the wordpress.org profile, is it the profile that you mean?

[00:15:47] Ivana Ćirković: Yes.

[00:15:47] Nathan Wrigley: Each time you participate in one of these credit programs, that will be a badge, for want of a better word, that you can display and it will be freely available for the public. And presumably that will be difficult to acquire. That’s the wrong word. What I mean is, it won’t be simple to acquire. You will genuinely have had to.

[00:16:07] Ivana Ćirković: Yes, you need to do the work. Let’s say students are interested in translation. So they go to Polyglots team and they get assigned to a mentor who is on weekly basis working with them on onboarding, helping them how to navigate through wordpress.org website, translation, what needs to be done. And basically, for that student, they need to translate to have approved translation, 150 strings approved.

So that doesn’t mean, okay, I will translate 150 words. No, no. You might need to translate 500 words out of which 150 is approved. And this is the bare minimum you need to do in order to get that badge that you contributed. Because that contribution, each contribution needs to be something very specific and tailored to help other people. That is very open and helpful.

[00:17:00] Nathan Wrigley: So you mentioned translations there, which obviously is just one of multiple things that you could do, and we could list them all out, but we won’t. How is that curriculum, I’m doing air quotes, how is that curriculum decided upon? In other words, how do you decide, okay, I’m going to do a bit of translation, I’m going to do a bit of work on Core, I’m going to work for the Plugin Review Team? How is that decided? And, how is it decided by the institution, I guess that that’s going to equal something which our university will stamp as part of your degree, let’s say?

[00:17:33] Ivana Ćirković: Yeah. So basically, that is all arranged between the foundation and universities. You won’t get IT students doing marketing if that’s not their preferable choice. So students opt in. They’re given the whole like curriculum, categories of things they can contribute to. And the one they choose, this is the one they stick to throughout all the programs.

So you cannot switch in between like translation and documentation, or plugins, or WP-CLI whatever. The whole program stick to one chosen category. And that is all aligned with the, let’s say, topic of university. So IT is preferable for IT related contributions. Communications are also more favourable towards translation community, marketing. So it’s aligned that way.

[00:18:23] Nathan Wrigley: So flipping that round, so we’ve been talking about it from the point of view of the students. Now let’s just flip it around to the point of view of the university. I guess the same thing applies. They would have to communicate with the Foundation and say, okay, these are the kind of things that we wish our students to do. These particular strands, we will, you know, if they do 500 translation strings, that will count as something. I guess there’s got to be some interface between the Foundation and each university to establish what a credit equals.

[00:18:50] Ivana Ćirković: Yeah, common ground as to how WordPress Credits adds to the official curriculum of the university. And the thing that university get out of it, they are in position to offer modern, in trend, teachings, and that makes them more appealing to next generation of students. Because the more their existing students who are in the WordPress Credits program are succeeding, the more desirable the university gets to newer generations because they don’t teach outdated curriculums. They’re aligning to what is now efficient and needed in the job market.

[00:19:30] Nathan Wrigley: I suppose also as well, when I was at university, there was a choice of about, I don’t know, four things to do each year. Something like that. You could do this or this or this. And you had to pick one of them and that was your pathway. This feels much more wide open because knowing the WordPress ecosystem, I know that there’s dozens, maybe multiple dozens of different things that you could be involved in.

So that’s quite appealing as well, isn’t it? You know, you can just take a little nibble of this one thing, and another nibble of this. And so there’s potentially multiple dozens of different pathways that you could pick. And whilst you say that, once you’ve decided you’ve got to stick to that, well, that’s fair enough, but the fact that you’ve got so many different ways that you could choose. That to me as a university student would’ve been really appealing. The fact that there’s so many different things that you could do.

[00:20:15] Ivana Ćirković: Yeah. And once they got in, the overall input that we get from students that, first they don’t know that something like this exists. And once they go deep and start work, it’s like, wow. The whole mind just shifts, and they are amazed by all the possibilities that they can do within WordPress that isn’t talked about.

[00:20:36] Nathan Wrigley: Yeah. And I presume they get to do it in the way that the WordPress community works, which is remotely distributed and when you wish to do it. So long as I, you make the end of the university period of whatever a semester is or something, so long as you make the deadline, you can do it at night or in the early morning or.

[00:20:57] Ivana Ćirković: Exactly. So they are training to be like workers as we all are today, that are not restrained with some deadlines or by official university rules. They’re accountable for the final output. How will they come to that output? It’s entirely up to them because, yes, they are young but they’re not so young that they cannot be held accountable for their actions. So they need to do the work. We got weekly mentorships and assessments. So it’s a fun ride.

[00:21:31] Nathan Wrigley: So just touching on that, the sort of ongoing support that every student needs, because with the best rule in the world, there’s a proportion of students who will leave everything to the last minute. I’m looking at myself in the mirror when I say that. So that ongoing support, it’s a weekly sort of huddle. And is that like a one-to-one thing or is it a one to many thing?

[00:21:50] Ivana Ćirković: Yeah, so depending on the number of students, if a mentor has a one or two students, it can be one-to-one. If there are more like five or six, it’s better to have a group meeting on a weekly basis, and then Slack chats in between if anything is more needed than that.

So basically we go through what they did last week, are there any setbacks or they need additional help, or do they need information from other parts of the team? Are they interested in something else? So we are really trying to get them involved in a way that matters to them.

One of the things that each student needs to do, no matter section they chose, is to create a blog and to have weekly blog posts. So we discuss about that. What interests them. Whether they want to be something personal like, or professional like. So it’s very interesting to see how they think and how they express themself and how they build their online persona.

[00:22:55] Nathan Wrigley: Do those huddles take place on a, let’s say university by university basis? So for example, when you join and you mentor students, are they from the entire WP Campus project, or are you doing it from the university of this town and the university of that town?

[00:23:13] Ivana Ćirković: No, it’s mixed and matched.

[00:23:14] Nathan Wrigley: So, okay, well that’s a real strength as well it feels, because presumably then you’re on a call with people potentially from all over the world. Certainly people that you may not have encountered before. And those sort of serendipitous chance encounters can sometimes be some of the more meaningful ones. You know, work comes out of those things, and meetups come out of those things, and unexpected things come out of those things. So that must be really nice as well, watching those kind of things happen.

[00:23:42] Ivana Ćirković: Yeah, it’s like nothing I experienced before. And just to have the privilege to talk and work with those people, you never know what can come up out of them, and out of our connections. And I get inspired every time we have chats and they make me want to be a better educator.

[00:24:03] Nathan Wrigley: Oh, that’s interesting.

[00:24:04] Ivana Ćirković: So, yeah, that’s my take out of all this.

[00:24:06] Nathan Wrigley: Yeah. Okay, so there’s actually some psychological benefit for you as well. You get a real nice feeling of it. Okay, that’s really good.

So with the best will in the world, a university, every year there’s a cohort of children, young adults, whatever it may be, whichever institution it is, and a proportion of them will work diligently and hard and they will succeed. And some others maybe not so much.

How does that work? How do you ensure that everybody gets through it? And I don’t know if there’s enough data to answer this question. Again, I’m doing air quotes, how is the pass rate? Do most people that embark on this get through the necessary things? Or is there a fair bit of, I don’t know, discipline, for want of a better word, that needs to be applied and cajoling people to get through it?

[00:24:46] Ivana Ćirković: Yeah, so I touched base on the accountability. So we have not strict rules, but recommendations. Weekly mentor chats, async communication through Slack. They all have weekly tasks that needed to be done. So if a student don’t answer the message or come to weekly mentor call three times, they are no longer WordPress Credit students. And that is the accountability.

You need to show yourself that you are willing to do the work. So if you don’t care, we won’t force you to do that if you don’t want to. We will set reminders, we will call back, we will reach out. But if you are no show, no tell anything for three times, then evidently you are not for that. You don’t wish to be there, and we won’t force you to be there.

[00:25:40] Nathan Wrigley: And then in some way, are you required then to report that back to the institution and sort of say, okay, we’ve reached the end of the road here, and then it’s for them to figure out how that impacts. And presumably the students can.

[00:25:53] Ivana Ćirković: Their grades, yeah.

[00:25:53] Nathan Wrigley: Yeah, their grades what have you, okay. Touching back on the sort of business side, because we’ve dwelled a lot with students and universities and we’re going to stay with students, because that’s really the underpinning of the whole thing. How has the business side of things, is it taking off? You were describing that it’s kind of like a new thing. Have you got any sort of success stories or anecdotal evidence that people do in fact want this?

[00:26:15] Ivana Ćirković: Yeah, so it’s still fairly new, so we don’t have those anecdotes yet. One of the reasons why I’m here at the WordCamp Europe is to find out and to get new perspective from businesses to like reach out to them to see what they think about the program. Would they want to be evolved. And how to give tips, maybe how we can improve. So stay tuned for more.

[00:26:38] Nathan Wrigley: Yeah. And it is interesting, when you walk around an event like this, I don’t have the exact numbers, but the demographic is definitely skewing older. There’s not so many 18 year olds. And if this community wishes to carry on, at some point the age demographic will get to retirement age.

[00:26:57] Ivana Ćirković: Yeah. Just last night we were talking. I’ve been in the community for 11 years. And for 11 years all the same faces are here. And we really need new faces. But to get new faces, WordPress Credits is one part of the solution. But then again, we need to meet young people where they are. And they are not on the conferences, they are not on websites, they don’t use websites, they don’t care about websites. They are on very specific social media channels. And if we want to get fresh, new, young blood, we need to go there and to present what we do in a way that matters to those kids.

[00:27:35] Nathan Wrigley: In terms of success, if you were to, I don’t know, let’s imagine that we could cast our minds forwards five years, let’s go for that. What would you like to have happened with WP Credits? Would you like, for example, to see a bunch of 20 somethings wandering around in an event like this? Does it matter that they’re involved in the community and doing WordPress events and contributing to Core and those kind of things? Or is success just more broadly, people are using WordPress? You know, it’s still a project. What’s your take on, what does success look like in five years?

[00:28:08] Ivana Ćirković: For me, I would like to see more young people involved. Yes, we will always have users because in its core, WordPress is a very useful tool. And I’m happy to stumble upon that tool many, many years ago to use it both personally and professionally. But I really want to see young people involved in a way that we were involved 10, 15 years ago, and to see what can happen with WordPress.

I strongly believe it’ll be transformed, not with AI or all other flashy trends. WordPress has always been about people. And we need new people, we need young people to get it where it needs to be.

We are getting older and don’t have strengths or stamina to do so for how many long years. By having new kids, fresh perspectives, I’m really excited to see what they can come up with next.

[00:29:08] Nathan Wrigley: Yeah, it’s kind of handing over the baton in a way, isn’t it? Seeing what the future holds. Yeah, I definitely have concerns that the age demographic is skewing. And no matter what has happened in the past, I don’t see it being backfilled with younger people moment.

But I think that’s largely because we just assumed that that age demographic would fill itself, because we were excited about it, so the younger generation will be excited about it. Well it turns out the world moved on. And TikTok came along, and YouTube became a massive thing and mobile phones and all the different platforms became a thing. And so the attention was put elsewhere by many young people.

And so I suppose we needed to come up with a system where we are, in a sense, just putting it in front of their face and saying, look, it’s here. You know, you’re a university student, you are somebody looking for work in a small business. Here’s a credible way of getting involved in something which potentially could change your life. That seems like the most credible way of doing it at the moment. And I guess we’ll just have to see what the next five years brings.

In which case, is there anything that you felt you wanted to touch on that you wanted to get out of this chat before we finished?

[00:30:15] Ivana Ćirković: No, I think you did it masterfully. And we touched base on everything that needed to be said.

[00:30:20] Nathan Wrigley: Perfect. In that case, I will say Ivana, thank you for chatting to me today. Fingers crossed that your presentation goes well tomorrow, and that you pack the place out, and that by this time next week, you are extremely busy with the WP Credits program. Thanks for chatting to me.

[00:30:34] Ivana Ćirković: Thank you. Thank you for inviting me.

So on the podcast today we have Ivana Ćirković.

Ivana is a digital marketer with 18 years of experience working both in and out of the tech industry, and currently leads marketing at WPBakery. She’s an active participant in WordPress events, having attended and spoken at numerous local and international WordCamps over the years.

In this episode, our focus is on the WordPress Credits initiative. We learn how this program, launched by the WordPress Foundation, connects students with real-world opportunities to contribute to the WordPress ecosystem, earn certifications, and increase their competitiveness on the job market.

Ivana discusses her own experience as a WP Credits mentor, working with students as they learn about digital marketing, remote work, and open source contributions. We explore how universities can modernise their curriculums and add real-world value for students by participating in the initiative, and how businesses can get involved, not just to support the community, but to help shape and discover future talent.

The program’s evolving structure also gets attention, and we learn how students are guided through hands-on activities such as translation or documentation, and how their progress is tracked publicly via profiles on WordPress.org. Ivana shares the opportunities and challenges for both educators and businesses, with thoughts on accountability, mentorship, and the need to bring new faces into the WordPress community.

If you’re interested in the future of WordPress, education, or bridging the gap between academia and industry, this episode is for you.

Useful links

WordPress Credits

WPBakery

What it (really) means to be a part of the WP Credits program?

💾

❌