#30 – Matt Mullenweg on the Future of Technology and Where WordPress Fits In

On the podcast today we have Matt Mullenweg.

Matt is the co-founder of WordPress, and as a result, he has been a user for as long as anyone.

We recorded this podcast whilst at WordCamp Europe in Portugal a couple of weeks ago. It’s a wide-ranging discussion, covering a lot of ground. 

We start out with Matt’s reflections of WordPress at 19 years old. Which aspects of the project would he change if he had his time over, and which parts is he proud of?

Did Covid, and the restrictions around community events, have an impact upon the project, given that much of the time dedicated to WordPress is done by volunteers? What lessons have we learned about events like WordCamp Europe?

In recent news, and for the first time, there’s some data pointing to the fact that WordPress’ market share might have flattened out. Is this a cause for concern?

Where are we at with WordPress right now, given that it’s changing the scope of what non-technical users can do with it out of the box?

We then get into some more personal matters, including how Matt manages his time over the variety of projects he’s involved with, and does he regard advances in artificial intelligence as always positive?

You might notice that the sound is a little patchy in places. This was a function of the environment we were in. There’s a few booms on the mic here and there, but it’s certainly listenable.

Useful links.

Five for the future

DALL·E: Creating Images from Text

OpenAI

Transcript

[00:00:00] 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 place of WordPress in the technology landscape.

[00:00:38] 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 go to WP Tavern.com forward slash feed forward slash podcast. And you can copy that URL into most podcast players as well. If you have a topic that you’d like us to feature on the podcast well I’m very keen to hear from you and hopefully get you, or your idea featured on the show. Head to WP Tavern.com forward slash contact forward slash jukebox. And use the contact form there.

[00:01:13] So on the podcast today. We have Matt Mullenweg. Matt is the co-founder of WordPress. And as a result, he’s been a user of WordPress for as long as anybody. We recorded this podcast while at WordCamp Europe in Portugal, a couple of weeks ago. It’s a wide ranging discussion, covering a lot of ground.

[00:01:41] We start out with Matt’s reflections of WordPress at 19 years old. Which aspects of the project would he change if he had his time over and which parts is he proud of? Did Covid, and the restrictions around community events, have an impact upon the project, given that much of the time dedicated to WordPress is done by volunteers? What lessons have we learned about events like WordCamp Europe?

[00:02:08] In recent news, and for the first time, there’s been some data pointing to the fact that WordPress’ market share might have flattened out. Is this a cause for concern?

[00:02:20] Where are we at with WordPress right now, given that it’s changing the scope of what non-technical users can do with it out of the box.

[00:02:30] We then get into some more personal matters, including how Matt manages his time over the variety of projects he’s involved with. And does he regard advances in artificial intelligence as always positive?

[00:02:43] You might notice that the sound is a bit patchy in places. This was a function of the environment we were in. There’s a few booms on the mic here and there, but it’s certainly listenable. If you’re interested in finding out more, you can find all the links in the show notes by heading over to WP tavern.com forward slash podcast, where you’ll find all the other episodes as well.

[00:03:07] And so without further delay, I bring you Matt Mullenweg.

[00:03:17] I am joined on the podcast today by Matt Mullenweg. Hello Matt.

[00:03:22] Howdy, good to see you.

[00:03:23] Yeah. They’re really nice to see you.

[00:03:25] As far as I’m aware, you’re one of two people who can claim to go all the way back with WordPress. And it’s been just last week, 19 years, I think.

[00:03:35] Yeah, that was a pretty exciting anniversary.

[00:03:37] Yeah, does that kind of stuff fill you with nostalgia? Do you sort of look back and think, wow, what a journey this has been? Or are always focusing on the future?

[00:03:45] You know, I am very future-focused personally, but it’s partially because I have a terrible memory. No really. It’s one of the reasons I started blogging. I learned a lot from the archives of my blog that I forgot. It’s also why I’m not too attached to like, arguing about the past. It’s like, you remember it differently. It’s fine. I’ll even go with your version, but what’s happening next? What are we doing in the future? And I try to live my life primarily oriented towards moving forward.

[00:04:12] The reason I laughed is because I’m exactly the same. I more or less everything that happened 30 minutes ago. But looking back over those 19 years, what would be some of the highlights? So I’m forcing you to be nostalgic.

[00:04:25] Hm. You know to me, it’s all about the people. Like we created lots of great stuff together, and still are. And so there’s definitely things like the first plugins, the first themes, the first international versions of WordPress with the Wiziwig coming in, which was quite controversial. And then Gutenberg coming in, which is quite controversial.

[00:04:46] That’s part of why I dipped back into more active WordPress stuff day to day for a while there. But, I really think of the people. From the early folks like Mike Little, some who’ve passed away like Alex King. To the incredible array of people we have here today.

[00:05:00] And my favorite part about WordCamps, what I miss the most was just meeting folks. Reconnecting with people who I’ve seen before, or just meeting people who, lives have been touched by WordPress in some way. And I’ve never, we’ve never run into each other before. I really enjoy that side of it. I learn a lot too. So it actually is very helpful for me in terms of thinking about the roadmap for WordPress. Just the stories. I hear, the things I see in the booths, the talks that happen. I definitely learn a ton from it.

[00:05:29] Staying on nostalgic thing, are there any bits which you think, I wish it had played out differently, bits where you look back and you think, oh, WordPress could have gone in that direction, or there was a moment in time where we could have done this, and we we didn’t do that?

[00:05:40] Hmm. Probably would have left the Rest API as a plugin, or maybe skipped straight to GraphQL or something. We did need to support all the feeds other than RSS2. We probably didn’t need all the others. Gosh, what else? I definitely, if I could go back to the very early days, we’ve always been really big on backwards compatibility.

[00:06:00] And so there’s a few database tables that are just inconsistent in their namings, you know, as capital ID or something like that. Going all the way back to the B2 days, even before WordPress. So I kind of wish we had just renamed some of those early, actually it might be easier to do it now because no one accesses those tables directly anymore, but some of those minor things kinda.

[00:06:18] I’d say broadly on the whole year you got it fairly right? I’m staying on the nostalgic bit, but this is the last couple of years. I mean, everybody knows what I mean by that sentence. The last couple of years, Covid and so on. How’s that been for WordPress in general? Everybody started staring at screens and looking at Zoom and, I feel that we were as prepared as an industry, as any. We got the zoom calls. We knew how to get the computer to do all those things. We had the mics, we had the cameras, but yet it wore pretty thin, after a period of time. And I wonder if the community, was sort of slowly leached away a little bit and I if there’s any of that.

[00:06:56] I don’t think in a way that was unique to WordPress. Like you said, we’re fortunate that we’ve always connected online. It’s a fairly positive community. People are very supportive of each other. Competitors grabbed dinner together. What we miss was definitely these events like what’s happening right now.

[00:07:11] It’s always been part of our magic sauce, secret sauce, if you will. Like we work remotely, but then when we get together, it makes it that much more special. And then more broadly, I think it’s just, you can’t ignore the impact all this has just had in people’s lives. And if there’s something going on in your life, you’re gonna have less energy for work or volunteering or other things.

[00:07:32] And certainly if it’s anything health related, right. All the priorities melt away, right? When you, or a loved one facing a health challenge. So I think that, so many parts of the world are back to normal or like nothing happened, but it’s easy to forget, like the vast human costs of what we’ve been through. And it’s still ongoing for many people.

[00:07:49] In terms of the contributions to the project, did that wick away? Is there the same engagement today, well, maybe let’s say three months ago, as there was two years ago, to core and all the other bits and pieces, or was that a struggle to keep going?

[00:08:07] I don’t have the numbers in front of me, but if I recall there was a boost at the beginning, when we’re stuck at home. And I think like, as people started returning, to normal life, it dipped a bit, which makes sense, right there probably like have saved up. I know I’ve been going to like a thousand weddings. It feels like everyone in the world is doing their wedding. So I think there’s just some natural time that goes back to life, which by the way is great, because then we’ll return to equilibrium there. If you looked at 6.0 though, amazing number of contributors, contributor day yesterday was way over populated.

[00:08:42] Yeah, it was so overpopulated, there was a struggle with food.

[00:08:44] We literally ran out of food and we always over half that. So I think that’s showing that there is a, um, to say WordPress can continue to serve the needs of the world and our community. There’s no reason for it to, uh, not continue to grow and get more involved. That flywheels, it gets more users, some percentage of those contribute. And then of course we have programs like five for the future. That I feel like every open source project should have, but it’s very mature in WordPress where it’s just a cultural mores of people, for whom they get a lot from WordPress, take a little bit of time to give back. And that again is part of it. It’s all the people at the end. I think I’m going to say that 10 times.

[00:09:22] No, it’s okay. I don’t know if you know, but apparently the two thousand seven hundred people who are registered, apparently 1,700 are brand new. Never been any WordPress event. About 60% of the people who are in this building have never been. So it feels if that was the thing it’s back in reverse.

[00:09:41] It makes me wonder what the 2022 WordCamp Europe would be without a global pandemic we are just are coming out of and like, kind of in, in many places still. So yeah, 2,700 that’s amazing.

[00:09:54] What do you think about events like this? It’s a generic question, but what are your thoughts? I mean, you’ve got such a different perspective, I guess, than somebody like me who turns up, attend events and go to people speaking and go to various different bits and pieces. What is this for you? Is it an enjoyable experience?

[00:10:11] I mean, that’s, that’s what I do too. You know, I’ll drop it in the back and check out talks. If for whatever reason not in the room often I’m live streaming them. I would say the difference for me is like, I leave a pretty under the radar life generally. It’s not like people recognize me or anything like that. But at WordCamps, definitely. So I go stopped sometimes every five feet, to take a picture or talk to people, but you know what, that’s kind of why I’m here too.

[00:10:40] Like if that’s a any way I can be of service to the community, sign me up for it.

[00:10:44] Maybe that was the target of the question. Is it a strange thing to drop into for a period of time where life generally is normal and then it’s extraordinary for a bit, and then it goes back to whatever the normal is.

[00:10:57] You know, I also just love talking about WordPress and technology. So I’m doing that for fun anyway. I’d say the main difference from my normal life is being recognized, which is just kind of a bizarre human experience. I never want to be actual, famous. Keep me out of the Daily Mail or The Post or whatever it is like. I’m happy to be well known among a community creating things like we do in WordPress.

[00:11:20] So yeah, that’s kind of fun. And also the to and from, because like all the restaurants around. The planes to and from the event. You’ll just run into people and, you know, I could take a hundred flights without anyone ever stopping me. Yeah, my backpack actually has the WordPress logo embroided on it, but it’s black on black, so it’s a little subtle.

[00:11:36] Normally no one recognizes. But often to or from a WordCamp, people will be like, oh, hey. But even I can go to WordCamps. I remember, often before WordCamp US, I’ll go to a bunch of the smaller ones. Just to kind of test out my material, like a comedian, playing smaller clubs before the big ones.

[00:11:51] I remember going to working at Scranton, I think it was. Uh, Pennsylvania. I forget where Scranton is, someplace, um, and smaller WordCamp, maybe 110 people, which are some of my favorites, but, you know, we sat down at the lunch. No one knows who I am. They’re like, what do you do? And then after my talk, they were like, oh wow.

[00:12:08] You’re like, you did that. And so it’s, it’s also fun to just kind of be like a secret shopper, if you will. Like often I’ll just sit down at random tables or go over to people. And, uh, again, like I said, I learn a ton, and sometimes when people don’t know who I am, I’m able to learn even more because they are more unguarded and more relaxed.

[00:12:26] These kinds of events feel to me almost like the glue that binds so much more together. These are three days where all sorts of new relationships are forged and old relationships are rekindled, and it feels like there’s been a great, big chasm. They’ve been missing. And, I’m just really glad they’re back.

[00:12:45] It’s funny, one of the things I’ve said that gets quoted the most, like on Instagram posts and stuff, is technology is best when it brings people together. And that really came out of the WordCamp experience. It’s a tremendous amount of work, and this is where I’d actually like to call out and thank the WordCamp Europe team.

[00:13:00] They really push the bar every year and raise it. Right. I have a little more involved with US. Every time Europe happens I’m like, man, we got to up our game. And I know it’s exhausting. Everyone like, you know, needs a break at the end. But wow. Really is one of the, I think one of the best contributions to the WordPress community.

[00:13:18] They’re all wearing black t-shirts and there’s black T-shirts everywhere. You know, there’s hundreds and hundreds of people who are giving up their time. And It’s amazing, you know, they’re doing it because they want to do it. There’s no coercion there. They’re really keen on the community and it’s this lovely.

[00:13:33] It’s a lot of fun too. Often my sister, she’s been to, I think, WordCamp US and Europe until this one. Unfortunately she tested positive before the flight, so she ended up staying home, wasn’t feeling well. But often she’ll volunteer at like the check-in stage or something like that. But she now loves it for the people, you know, like she’s a fan of mine obviously. We’re brother and sister for a long time, she has so many friends here now.

[00:13:56] I know for a fact that there’s people here just in the few people that I know who’ve brought their husband or wife and they’d just in, cause it’s a nice thing to do. Staring into the future, forever, it seems, the numbers for WordPress up, up, up, up, up, 25%, 40%, 43%, whatever it is. I think, you know where this is going.

[00:14:15] Recently, I don’t know how dubious the statistics are. There’s this possible leveling off. Is any of that of interest to you? Is growth the thing, or is it, is there something else? Are you thinking about that at any point? Does it worry you or give you pause for thought?

[00:14:31] I think growth is the result. So if we create something that’s accessible, well designed, solves people’s problems, we should grow. And so, yeah, it’s concerning to me when we don’t grow. That number is going to be a little wonky over the next year, year and a half, because as you’re probably aware, Alexa, the toolbar is shut down.

[00:14:51] So even though they’re still providing data, the W3Techs, that data is more stale than it used to be and will, I think degrade over time and eventually W3Techs are switching to a different data set. I forget which one it’s called. So I don’t know that off the top of my head, sorry, my computer’s over there, but on Built With, Built With is something else that indexes the whole web and says how many it is. We’ve generally talked about the W3Techs number, which I think got up to like 42 or 43% before it started to wobble a little bit. Built With had us at like 30 something percent. I think the answer is somewhere in between there.

[00:15:23] So I can see the W3Techs number coming down, maybe even 15 or 20%, uh, regardless of the actual underlying fundamentals of WordPress. And luckily we have some other of data that we get back, and the wordpress.org plugin directory from the update pings, things like that, that show the health of WordPress.

[00:15:40] Uh, so those are always what I look at as the leading metrics. So we keep an eye on those. If there were to see a big migration, we would definitely take a look at the why, and see if there’s something we can improve in the software. And then finally, I’m a little less worried least at the moment because I’d really like to switch Tumblr over to WordPress, which is, well half a billion blogs. There’s a lot of Tumblrs out there.

[00:16:03] And of course not all active, so it won’t move the number that much, but, yeah, a good amount. I’m very excited to bring that part of the web, which is so vibrant, has such a strong community and has a demographic, you know, younger, more female, than we might normally have at a WordPress event. Having it be like an on-ramp to the WordPress world.

[00:16:20] Some of the commentary around that, whatever that was, this leveling off, was around things like, well maybe WordPress, there’s a lot of work to do in terms of performance and things like that. And I know that there’s initiatives in place and things are being done. I just wondered if there was anything you had on that.

[00:16:38] I think we need to improve every single part of WordPress. And there was some performance data. I think is it, Alaine talked about today in his presentation? That shows that some WordPress sites are not as performant as some others. Now, the tough thing is I think you need to adjust to that per dollar.

[00:16:57] So, you know, comparing it to essentially a hosted platform, like Squarespace that people might be paying $25 a month. To a web host you might be paying like $4 a month for is not an apples to apples comparison. There’s going to be some performance differential there. And of course, one reason why so many people use WordPress, especially globally is the accessibility.

[00:17:16] The job that the web hosts do, making it extremely affordable. You know, the average Shopify subscriber spends $1,200 per year. Average WordPress subscriber, it’s, I don’t know cause it’s across so many hosts, it would be closer to like a hundred dollars a year, maybe even less when you look at like how reasonable a lot of these hosting plans are, but definitely anything we could do in Core is helpful.

[00:17:39] And it’s also part of why, I think part of the story of the past 10 years of WordPress has been our really close partnerships with all the hosts. So the auto upgrade almost every well, every major host upgrades by default. Getting them on the new PHP versions, which actually have huge performance increases. PHP seven doubles performance essentially. So helping them be on the edge of the technology adoption curve.

[00:18:01] But it’s not true, I’d strongly disagree that WordPress is slow. In fact, WordPress sites can be some of the fastest ones out there, but when you think of 40% of the web, a lot of them on less expensive hosting providers, it’s going to pull our overall numbers down. If you’re looking at all sites, not just the fastest ones.

[00:18:20] Gutenberg WordPress 5.0. At seminal moment, everything changed.

[00:18:25] Yeah. It was a good one.

[00:18:27] There’s been a lot, there’s been a lot that’s changed since then. I’m just wondering over the course of those, what is that? Three years, some, three years.

[00:18:34] Yeah, right about.

[00:18:35] How you feel that’s gone. was a messaging thing at the beginning, you know, how, how did it get rolled out. But it feels to me as if the people who are developing on top of it more and more and more. Are getting excited and the talk is more and more and more about the possibilities and what’s going to be possible. So just that really. Are you pleased with the direction it’s going in? Where we’re at now, full site editing, all of those, block themes.

[00:18:59] I’m pretty thrilled with it. Of course, I’m an impatient person. So I would love to move faster. But the truth is in 2022, if you’re not building a site on Gutenberg by default, you’re kind of setting it up for obsolescence or really expensive upgrade paths in the future. It is so capable. I think people underestimate how much you can do with Core blocks

[00:19:21] Like without adding any of these block ad-ons or anything. And yet also, that’s such a clear roadmap, so many improvements are coming in every release. It was just at 6.0. I’d like to move us to be more releases per year. You know, maybe we can get to four per year instead of three, but it’s coming along. I’m thrilled with it.

[00:19:37] And other CMSs are starting to copy it, and we’re getting Gutenberg and a lot more places too, which is also exciting. Um, Gutenberg is live for Tumblr by the way.

[00:19:47] Is the intention that it’s the editor for the web, basically.

[00:19:49] A hundred percent. It’s bigger than WordPress.

[00:19:51] It’ll be everywhere and ubiquitous. So on the phone and on the, whatever CMS that you’re using and the whole thing.

[00:19:58] Yeah. And there was this announcement for something called the block protocol, which I think, if you look at it, it’s exactly what we’ve been doing with Gutenberg and they probably should just adopt a Gutenberg and then like build from there.

[00:20:07] Yeah. That was a really interesting project. The idea that it’s completely interoperable across everything. Yeah. Really, really, really interesting.

[00:20:14] That’s what we’re doing. We have the mobile versions for iOS and Android. I believe we’re relicensing those right now to be even more open. So they’re easier to embed in commercial apps. And then of course the web version is getting pretty robust. And it’s just, it’s weird edge cases that you start to deal with.

[00:20:29] There was one I found the other day actually through a friend. This is why I love doing tech support and people talking to me about the problems with WordPress. I think it was copying and pasting from Facebook images. So they had a lot of their photos on Facebook and they would right click to click copy and paste and in Gutenberg, what it was doing was making that a link to the image, versus actually uploading the image. And so, because it was to like a private URL, it would break for other people. But it would look normal to that person.

[00:20:59] This was just a workflow no one has pointed out to us. It was like pretty easy to fix once we knew about it. But, it was interesting because one thing we do when something like that comes up is we look at other editors and see which other editors support that use case. Actually Google docs did. So at some point, Google docs figured this out, but a bunch of other editors did. Google docs is actually one of the software projects I repect the most.

[00:21:22] I entirely agree. I’m waiting for the day when, um, we can do the concurrent editing, that will be.

[00:21:26] Oh my goodness.

[00:21:27] It’s almost as if that’s the minimum requirement now. I’ve got so used to using Google docs and seeing the other people contributing at the same time. I remember the experience of seeing that for the first time and thinking what that’s voodoo.

[00:21:39] How, did that happen? But you you’re happy. You’re pleased with the development and you’re pleased with the way it’s looking?

[00:21:45] No, I’m impatient. I’m really proud of what we’ve done, but there’s so much more to do. And especially if we’re trying to make the editor for the entire web, it’s even bigger than WordPress. I think that’s going to have such a benefit, to both developments, like speed of development. It’s not unlike web components or other things like we’ll have these standard things everyone can use.

[00:22:06] And then there’s also usability because users will be able to learn how blocks work, once, and then create almost anything. Like how cool is that? It’s like a fundamental, literally fundamental building block of the web, almost like the DNA.

[00:22:17] I’m going to phrase this in a way which I suspect you’ll push back on, but let’s see where we go. The five for the future initiative. That would be so great if everybody was a part of that. And I wonder if you would like more people to be a part of that? Whether or not there’s some inertia.

[00:22:36] I’m struggling to find the words. The speed of everything could go more rapidly. Everything could happen more quickly. And that speaks to your impatience. If more people were able and willing to step up for that initiative.

[00:22:49] You know, I value even if people just have one hour, once a month. You know, five for the future isn’t meant to say you need to do 5% or nothing. It’s just meant to say that, Hey, if enough people do the 5%, WordPress will really thrive. But if not everyone does it, that’s okay too. In fact, you know, not everyone does it and doing pretty well.

[00:23:12] It’s funny cause contributing, it’s kind of hard to start and maybe it’s intimidating to think like, oh, do I take like two hours a week to be part of WordPress. 5% of a 40 hour week or something. But it’s hard to stop too. Once get involved, it’s infectious because it’s such a great way to learn.

[00:23:28] It’s really great to be connected to something larger than yourself. Do some work and then see the ripples throughout the web or throughout WordCamps. It’s really fun to like overhear someone talking about something at a WordCamp that you were involved in building or contributing to or documenting or translating.

[00:23:44] I dunno, it’s just like a source of pride. It’s kind of how I got involved. Like I contributed some code to B2 at the time and I just got such a high. From knowing that, you know, hundreds of websites were running my code, and I’ve just been chasing that ever since. Like it’s still compelling, even if it’s a plugin that only like 10 people use to like, you know, obviously any changes the Core go to a lot of the web. At any point it’s just kinda like leaving a dent in the universe, leaving the world a little bit better than you found it.

[00:24:10] It’s funny, you said the word proud, well you said pride and my question contains the word proud, and it is follows. What are the things, and you’ve covered this a little bit. But this doesn’t have to be the code, it doesn’t have to be the community, although maybe that is the bit. What are the bits that you’re most proud of? The bits that you look back and think I am so pleased that bit happened. And it could be a big thing, could be a tiny thing, but the bit that makes you internally smile.

[00:24:36] I’m really proud, to the extent WordPress, it can be a very welcoming place. We really strive to be inclusive, to bring folks from all over the world, all backgrounds. Now I’m sure there’s mistakes. I’m sure there’s things that happen at WordCamps sometimes, but like we correct that and the norm of the community is expecting to make someone feel welcome. Yeah, I really appreciate that. I mean you look around WordCamp, could not be a more different group of folks.

[00:25:03] Yeah, that’s true. They’re an interesting, there’s an eclectic mix of people up there.

[00:25:08] Oh my goodness, even it just like fashion styles or like you know, like hairstyles, styles, ages, colors, everything. And how beautiful that? That we can come together with a shared passion, communicate with each other as humans. Every person is unique. You’re not what it says on your badge or where you work. It’s really about connecting as humans and that’s, to me, what’s great about blogging. It’s about, what’s great about the open web. It’s recognizing the beauty, brilliance and uniqueness of every person.

[00:25:37] How do you manage your time? Because I know that you’ve got more things than I’m doing. Let’s put it that way. You’ve got Tumblr, you’ve got WordPress. Where does it all fit in? Do you like a run a regular week? Are you a 40 hour a week person? Do you tend to work late into the evening or?

[00:25:53] I guess there’s multiple levels to answer that. Where I’m spending my time in terms of all the projects that are going on, is kinda like rotations. Like often I’ll move into something, spend a lot of time there and then I’ll drift back out once, you know, whatever I was coming in for has changed. Probably a good example of that recently was Gutenberg.

[00:26:16] So that’s one took a more active role and kind of release lead, the driving, the getting that happening. Even like the product itself. And then as that really got great you know, 5.1, 5.2, able to step back and allow others to like take a more active role and leading that or driving that. Tumblr’s is a good example.

[00:26:38] Like, you know, stepping into it for a bit. I hope to be able to pass it to someone in the future and say like, take this, keep it going. It’s going great. And so that’s kind of how the projects do. And then personally, I just try to manage my energy, to match that to the tasks that are happening.

[00:26:53] Unfortunately, I work very strange hours sometimes, and, I just try to capture, like, if I get a burst of inspiration late at night to write something or, feeling really engaged, we’re in the mood for like doing communication stuff versus like I’m in the mood for reading, whatever that is, and run with it. Versus trying to say like, every morning I’m going to do this. Some mornings I’m tired. Some mornings, you know, maybe I’m feeling a little more burnt out. And so, like, I don’t feel that sort of creative spark to, to write a thousand words, but it might be easier to catch up on some P2 posts. Catch up on the Slacks.

[00:27:26] It sounds like you take care of yourself. You take time to step away and, I came in here you were listening to jazz music, which was quite nice sort of background. But, you know, you take time to do all of that. And have you always coped with pressure well, because I’m guessing there’s a fair amount of pressure your life, yet you always have this fairly serene composure to you.

[00:27:46] I guess what a lot of people think is pressure doesn’t bother me very much, because you know, I feel like you should worry about the things you can change. So if you know, we got to note your biggest client is leaving you, they’ve already made up their mind. You can’t do anything. It’s like okay. Like learn from it, but don’t beat yourself up over it. Like suffer once. Like so often we suffer more, this is a quote, we suffer more in our heads than we do in reality, either for imagined things which is anxiety. Reliving the past, or just kind of beating ourselves up for something. And so it’s better to just recognize reality. Acknowledge it, learn from it, get as much information as possible, but then what’s next?

[00:28:27] Where it definitely hits me harder is when there’s something you can’t change, with a loved one, you know, like someone passing, getting sick, those things hit me really hard. That’s probably the place where, when that happens, I have to step away for a bit. Just kind of recharge or get in nature, hydrate, make sure I’m sleeping well. Those things are tough for, I think everyone, but the calmness that happens in normal, like code or business or whatever it is that normally would stress me out. Those are bigger.

[00:28:59] There’s this phrase, I’ve written it down here. Benevolent dictator for life. Benevolent is such a nice word. It’s great. Everybody loves benevolent. Dictator, maybe that’s a different thing.

[00:29:10] I feel like that branding’s a little less good recently.

[00:29:13] But, we all know what that means? Do you plan to be here in several years time? Would you love still to be at the helm of WordPress? Is this going to be the life for Matt Mullenweg for the foreseeable future?

[00:29:26] Yeah, three out of those four words are millions to. I hope to be of service to the WordPress community, benevolently. That’s always something I will do my best. I always say I’m human. I’m going to make mistakes. We’re going to mess up That’s the only thing I can a hundred percent promise. But we’ll try to learn from them.

[00:29:41] Try to course correct and be right more often than not. And then the, for life. Yeah, a hundred percent. Like it’s been 19 years. I think because WordPress changes so much, I’m never bored of it. You know, it’s like one of these things that you know when WordPress launched, javascript was called DHTML. It wasn’t really common. There was no iPhone. like that. Everything has changed so much and it still is. You know, it’s hard to imagine looking from 2003 to now, how much things have changed looking forward another 19 years to that would be 2041 or something. Like what will be enabled? And in technology, and don’t know if you’ve seen things like the open AI projects, like GPT3 or DALL-E, like utterly astounding,

[00:30:25] I find it a bit scary. Aspects of that worry me. The aspects I think that worry me are the loss of control and that, at some point we’re going to just be creating 10,000 word articles. So the bot creates the article, which is then read by the Google bot. The cyclical creation of things.

[00:30:44] And also the destabilization of the belief in what your eyes tell you. You know, you see a picture of some famous person allegedly doing something, which they never did, but somebody created it with a click of a button. Those pieces worry me. So you sound much more sanguine about it.

[00:30:59] I’m pretty excited. The text side is interesting, but I’m actually really excited by the image creation, not the deep fakes, but more like DALL-E, you can give a prompt. Like I want to see a spaceship cat eating ice cream, while riding a bike.

[00:31:17] That’s the one everybody’s going to say.

[00:31:18] And this image has never existed humanity. Yet you can speak your words and it will be created. And it will create like 15 of them. And some of them are weird, but some of them are incredible. And you can say, do it in the style of Salvador Dali, or do it like a Monet painting. Or do it like an illustration. Like that is unlocking that kind of co-creation of art, I find so compelling because that’s essentially, when technology creates things we can’t expect that hypercharged creativity.

[00:31:50] So even when you imagine, when we moved from drumming and using our voices instruments to having, the creation of the first instruments, whether they were stringed instruments, lutes, organs where the most sophisticated technology at a time. Today, the way we can use synthesizers and remix things and multiple tracks. I’m sure it’s certain points, and I’m sure there’s examples of this creating bad art. You have to make a lot of terrible art to get to the good art.

[00:32:13] The boundary comes down, doesn’t it? You don’t need to have that dexterity with the pencil or the pen, the paint brush or whatever it is. You have to have the vocabulary to describe it.

[00:32:22] There’s an art to that too, like. I feel like there’s a skill to doing a good Google searches, like crafting the search term in a way that helps you find what you want. And we kind of co-learn with it. There’s a feedback loop. You put in a search, you don’t find what you want, and you start to tweak it and you learn.

[00:32:38] I think that the sort of generative art tools like a Dali are the same way. I think Mind Journey is another one. You can go through and feed in some texts and then see what happens. And then like keep going. I mean, how cool would that be. Actually for Tavern, I would love for you to see you all use it more, like, make some, more like Mine Journey or DALL-E type images?

[00:32:56] that then leads me to the question about AI creation of websites. So, do you want a future where you build the website with that kind of an interface? So I would like a website that’s to do with volcanoes and I would like a picture of a volcano at the top. No, not that one. Slightly more fiery. And can we have a button, but no, no red, not blue. Wider. Yeah, no stop there. So that kind of an interface. So we drop the mouse and we describe the website and move the components with our voice, or whatever we’re using, maybe we’re plugged point.

[00:33:28] And how powerful are blocks for that? Right, so we’re creating the sort of raw ingredients that could be used. I used to not believe this stuff would happen. But it’s gotten so great. If you’ve seen Codepilot, Codepilot on Github, or some of the stuff that GPT3 can do around like interface creation or even app creation. It’s fairly powerful.

[00:33:49] We’re going to have much better machine learning models around translation of languages. I think we’ll get to a point, you know, we’ve always joked, like will WordPress ever be written in something other than PHP? I think we’ll have translators over the next five to 10 years, that could take something as complex as a WordPress and translate the code to another language and it’ll work.

[00:34:08] Right, because essentially that’s, what’s happening. All these languages go to a bytecode or some sort of something much closer to the wire. So once a computer can truly deeply understand what’s happening in the code and find the equivalents in another language, right?

[00:34:22] You’re close to just thinking a website into creation at that point, aren’t you? The boundary is, can you imagine, and if you can imagine an elucidate it, then you’ve done it.

[00:34:32] And think how much creativity has been unlocked by things like Photoshop or Illustrator or the pen for the iPad anything. Like you put these things in front of a child, they just start producing.

[00:34:42] Oh, immediately. That’s interesting.

[00:34:44] And that’s, that’s cool, right? And so it kind of comes back to what’s what’s the limits of human imagination and a little bit, our limits are what we’ve experienced so far. So there’s this idea of adjacent possibilities. That whatever’s going on in the world, people consume, and then that gives them the ideas for what’s next. But you need the previous stuff to exist first. Right? We build on the, we stand on the shoulders of giants and every generation that’s come before. And now with global communication, everything, a cycle of that feedback loop of new things happening and then spreading throughout the culture.

[00:35:19] I mean, used to take hundreds of years. There’s examples where they knew that scurvy was caused by lack of vitamin C like hundreds of years before it was kind of widely known knowledge. And. You know, they can sequence a novel coronavirus, create the vaccine, literally within like a day, the sequencing being available. What was it, a year and a half later? Like there’s a billion doses in people’s arms.

[00:35:45] The impediment was the testing, not the creation.

[00:35:47] Wow. Even making a billion of something in like a little over a year is kinda wild as well. So that is, think of it both a faster kind of clock speed for the evolution of culture and thought and knowledge that’s enabled, and also hopefully faster antibodies, both literal and societal to things that can cause harm.

[00:36:11] You know, I don’t think it’s, it’s a stretch to think of misinformation, disinformation, you know, sort of the information wars that are happening right now, both hot and cold throughout, um, authoritarian and more democratic regimes as a type of pathogen. Almost like a novel mean virus or idea virus, which right now we’re not very strong against, but we’re starting to develop the antibodies too, including things like detecting bots and coordinated inauthentic behavior.

[00:36:37] That right now I think is causing a lot of problems throughout society. but we’ll get better at figuring that out.

[00:36:44] It’s fascinating because I think technology can take you in one of two directions, you know, the, the apocalyptic version and then the sort of, desirable, let’s say that. And it feels to me that you are ,firmly on the desirable side. You’ve got a very positive approach that the technology in the future doesn’t worry you.

[00:37:03] It’s not that it doesn’t worry me. It’s just I’m a builder. So I need to choose that I’m going to work on.

[00:37:07] Yeah, sadly, my

[00:37:08] work on the things that things better.

[00:37:10] My vocabulary left me at that point.

[00:37:12] Techno optimist, maybe. Yes. Like, uh, I would say that I tend towards optimism and the thing that gives me that optimism is often deeply engaging with a criticism of it.

[00:37:23] So I want to really strongly understand, be able to make the argument for why all the things I just talked about are going to destroy society. But then once you understand that, how can we build it or how can we do it in a way that’s going to be more positive. And also how can we check our assumptions? Like if we look back, to what we thought was going to ruin society before, did it?

[00:37:43] It’s funny, there’s a, gosh, I forget the name of the account, but it just pulls up old criticisms of the technology. And there was one that showed a subway, and everyone’s, um, reading a newspaper? They’re like, oh, what’s happened to society, people used to talk on the subway, they used to engage with each other. Now just the heads are all buried.

[00:38:00] Of course Gutenberg, you know, the original, uh, needs to read it’s, you know, it’s dangerous.

[00:38:08] And it turns out that it was dangerous, like wow. Protestant, like, how much change that kicked off, but it was really about knowledge is power. It was about the distribution of a more wider distribution of knowledge and opportunity. And that shook up society. But you know what? I needed to be shooken up.

[00:38:25] It’s the message. Maybe this is the perfect point to end?

[00:38:27] That’s what WordPress shakes up, you know? So we take things that, by the way, equivalent to what WordPress does for free, 10 years ago, you’d pay like millions of dollars a site core or Magento or something like that to do it, which now like you can download WooCommerce and it does everything that did and way more.

[00:38:45] So we’re kind of taking, I sometimes make the analogy that we have a promethean task, climb mountain, take the fire from the gods and then bring it to the people. As we do that, sometimes it generates a lot of blow back. You know, if you recall a really big criticism of Gutenberg early on was that it was going to destroy agencies and web builders.

[00:39:05] People would just be able to build their sites themselves. They would lose all their business, everything like that. As you walk around WordCamp ask anyone who’s building websites, like, do you have more business or less business? How’s it going? I’m sure there’s some exceptions, but by and large, the businesses are larger than ever.

[00:39:19] They’re growing faster. Site builders doing fine, the themes that are like, you know, there’s going to be some changes, right? Some of us might be making horse buggies, and those might not be as in demand in the future, but you can also like shift and it’s kind of cool. I have people tell me that they’re way more profitable now because they can build things in Gutenberg that they used to have to code custom. So even though they could code a custom, they can just click some buttons and build a site and be done so they can now do more of them. How cool is that?

[00:39:45] So the change definitely disrupts things. It can definitely be sometimes rocky, but ultimately, if you embrace the change and you sort of work from your principles and your morals to be on the right side of history, it can be incredibly empowering. Matt Mullenweg, thank you for talking to me today. Thank you. Thanks for coming.

Contributing to Open Source Is ‘Better Than Any College Degree’

A week ago, I published my thoughts on the block system from a developer’s perspective. Taking a weekend-afternoon deep dive into creating custom block types meant learning some tough lessons and familiarizing myself with a programming language I had little experience using.

Programming has always been a trial-and-error affair for me: write code, refresh the browser, read the error message, and attempt to fix the problem. Then, simply rinse and repeat the process until the program is not broken. Those mistakes are woven into the art of coding, the layers underneath that poetry on the visible canvas.

I have absolutely made the same mistake twice. And, thrice. Probably a lot more than that if I am being honest with myself and you. Eventually, I stop making those same mistakes, and some method or procedure is permanently seared into my brain.

I have written a few hundred WordPress tutorials in the past decade and a half. I am a twice-published author of development books and served as a tech editor on another. However, I am not much of a reader of tech books and documentation. For one, programmers are not necessarily the most engaging writers. Plus, book smarts can only get you so far. You need the street smarts of programming to become good at it, which means learning from experience.

While I firmly believe that reading is a central part of that, there is no replacement for getting your hands dirty. Building things, making mistakes, and learning to fix them is what makes programming fun.

Working on open-source software like WordPress is one of the best ways to do that. There is no upfront cost, assuming you have access to a computer, a prerequisite to programming of any kind. There are usually people willing to lend a hand or answer questions, and there are always problems to solve for those ready to dive into them.

As WordPress Executive Director Josepha Haden Chomphosy chatted with Matt Mullenweg on the Openverse project a couple of months ago, there was a moment that I found myself nodding my head in agreement.

Because, of course, you know, contributing and being involved with open source is probably the best way to learn a technology, better than any college degree.

Matt Mullenweg, WordPress Project Lead

I have learned more about WordPress, PHP, HTML, CSS, and JavaScript by contributing to open-source software than I ever learned in a college course.

I grew up in a generation that was told that we must get a college degree. It was an integral part of the American dream that would result in suburban life in a neighborhood with perfectly aligned rows of houses, ending in a cul-de-sac. It was the first step toward a two-car garage, white-picket-fence, 2.5 kids, and a dog. College was the promise that my peers and I hinged everything on. It was expected of us, and so many of us did our duty.

Here is the thing that our parents did not know. The internet would change everything.

I graduated high school in 2002. This was during that stretch where the online world was exploding. All of the world’s knowledge would soon be at our fingertips. Today that is truer than ever. Anything you will ever need to learn about writing code is available through an internet connection.

My experience with college-level courses in programming was mixed, but I learned a necessary life lesson from them: I was not cut out for a degree in software engineering. I am glad I wised up early on and pursued a different degree, saving myself some time and money.

I rocked my half-summer C programming class, my introduction to writing code. I also had a passionate professor who once worked on U.S. missile projects as a bug-tester. It was probably not the most glamorous job, but he always made it sound exciting because he loved what he was doing. Our class was tasked with building various programs throughout the course, but we usually had a choice in what we were building. For my group’s final project, we created vending machine software.

I was on the fast track to becoming a software engineer after that first class. I had built a way for merchants to get paid for delivering sugary treats and soft drinks to customers. It was capitalism meeting programming, and I had a taste for it.

The fall semester rolled around, and I was motivated to move beyond the realm of procedural programming in C. Java, an object-oriented programming (OOP) language, would be my next challenge.

The most advanced thing our class built for an entire semester was a basic calculator. I skipped nearly every lecture because I could not stay awake watching the professor chicken-peck his way through programs for three hours every week. I attended the mandatory “labs” — basically a fancy way of saying an extra class where the professor’s assistants would teach the actual coursework.

Needless to say, my fire died down. While calculator programs are handy tools, I wanted to branch out and build things that mattered.

You know what reignited my flame for programming? At first, it was general web development. But, WordPress was what I really became passionate about. And, I have not looked back since I started using it in 2005.

WordPress was my gateway into a world where I could create things that interested me. I could jump ahead into a project far more advanced than my skill level, trial-and-error my way ahead, and eventually build something that others found value in.

Unless universities have changed, most teach step-by-step foundational lessons to their pupils. Some students may luck out and land in that unique professor’s class who gives them leeway to explore various ideas. However, there is no substitute for creating something of your own, solving a problem that you see.

And, that is what programming is all about — solving problems.

In 2007, I released my first WordPress plugin into the wild. It automatically listed all of the subpages of the currently-viewed page. Dozens of similar plugins have been written since and probably before (it seems WordPress would have a simple “list subpages” function by now).

Last week, after writing a new plugin, I was reminded of the free education that the WordPress community has given me over the years. Some of it has been reading documentation. Some from WordPress Stack Exchange answers. Other bits have been studying from those who came before me, building upon their open-source code. All of it was from other people giving something back to our community.

This is not necessarily a knock on college. Some people perform better in that structured environment, and there is value in all forms of education. However, there are alternatives for those who cannot afford college or learn better in a different environment. And, there is no discounting the experience you get from contributing to something bigger.

If you are one of our readers thinking about getting into programming, just dive in. Make some mistakes. Build. Learn.

Upsells, Barriers, and the End/Beginning of the Quality $free Themes Era

The WordPress.org theme directory is becoming little more than a crippleware distributor. I suppose it was inevitable given its reach, which can be worth $1,000s/month for theme authors.

Justin Tadlock via Twitter

As I think back on that tweet from 2019, I realize how unfair it was to refer to the themes coming into the directory as “crippleware.” At the time, I was a part of the Themes Team (formerly the Theme Review Team). However, there were real cases of crippleware submitted to the directory when I wrote that.

To define crippleware: some themes blocked core WordPress features and made them available via the “pro” versions. It was one of the more blatant abuses of the free themes directory I had seen for a profit.

However, the term does not represent the majority of themes submitted. Most of what we see today are “lite” themes. Some of them are well-designed themes that provide value to end-users at no cost. Others are stripped-down versions of what you would typically see from a starter theme. While they are fully functional — the Themes Team’s rules have been strict on this requirement — the real value of the theme is in the upsell.

This is not the start of an anti-commercial theme rant. When WordPress developers and agencies are successful, it benefits the whole ecosystem. But, how do we balance that with providing value — which is subjective, I know — to the free theme directory? How do we transition the theme directory to something flowing with more artistic or even experimental ideas?

Guidelines and Stumbling Blocks

Matt Mullenweg, WordPress co-founder and project lead, posted the following on the Post Status Slack two weeks ago:

The .org theme directory is particularly bad when you compare it to any half-decent commercial theme marketing page, or the designs available on other site building services or Themeforest directories. The .org theme directory rules and update mechanism have driven out creative contributions, it’s largely crowded out by upsell motived contributions.

There is a lot to unpack in his statement. I agree with most of it. The Themes Team agrees with at least some of it. However, its members lack direct control over the system outside of the guidelines.

“I actually agree with this in a sense,” said Themes Team rep William Patton. “Creativity has not prospered in the directory, and I think a large part of it is the barrier of entry. ‘Don’t do bad things’ is the overarching guideline for the theme directory, but that can be viewed very subjectively. If it were the only guideline we would see a lot of things that might not be best suited here. If we want to encourage creativity then more freedom to express it would likely be a good way to start bringing it back. However, it can be hard to know where the line should be placed.”

The team sometimes gets pulled in two different directions. When the project lead asks for things to be more open, many members rally around that idea. On the other hand, the call for stricter accessibility requirements, for example, are popular with others in the community. It is a choice between two ends of the spectrum that are tough to pull together as the gatekeepers to the official directory.

“Why couldn’t it be more like the plugin directory?” asked Mullenweg. “That has all the same potential issues and has been working pretty well. I’d like it to work just like the plugin directory, with direct access for authors, and most reviews being post-review vs. pre-review.”

The Themes Team is not against the idea. More than anything, they just need the help to make any significant change.

“Having the themes directory work like the plugins directory would be great!” said Themes Team rep Ari Stathopoulos. “And, in fact, it’s something we’ve all been asking for years, but there are many technical challenges because they are built fundamentally differently. Plugin authors have access to their plugin’s SVN while themes don’t. Theme reviews are public while plugin reviews are private and closed. There would need to be lots of changes in systems and meta. Not to mention that, as far as I know, plugins don’t do post-reviews, they do pre-reviews the first time a plugin is uploaded and post-reviews for updates (which is exactly what happens in themes too).”

The team has created tickets, asked for help, and have generally awaited a champion to push innovative ideas — or any ideas — forward. Seven-year-old ticket to support the standard readme files available to plugins? No takers as of yet. Allowing block-based themes to be uploaded? Maybe we can make that happen sometime soon.

The guidelines are likely less crippling than the outdated Trac review system, uploading ZIP files for updates (which Mullenweg mentioned), the limitation of a style.css header for the theme description, and the lackluster theme previewer.

WordPress.org theme review Trac system.
Theme review system on Trac.

For the most part, nearly every guideline has been put in place in hindsight. The team finds consistent abuse or issues and course-corrects.

“I don’t think that Matt’s idea of a creative theme is a theme that is not secure or not compatible with GPL,” said team repo Carolina Nymark. “Creativity is not limited by being asked to sanitize options. It is not limited by making sure that your theme can be translated. If the reviewers saw creative, beautiful themes that lacked in some other aspect like basic accessibility, then the team could help explain to the theme author what kind of changes are necessary. But that is not the kind of themes that are being submitted.”

Financial Incentive

In the mid-2000s, the average theme developer could get away with building an entire theme on a lazy weekend afternoon. WordPress was far less complicated. Theme development was not a race to the bottom, bundling every feature imaginable.

Today, we live in the era of the multi-purpose theme. To soar to the top of the popular list, most themes need to handle everything from being the online face of a pizza restaurant to masonry grids for artist portfolios. They also either need good luck, name recognition, or good marketing. That is the reality for the average theme developers trying to make a name for themselves.

It makes for boring themes in a free theme directory. If the theme author has any financial motivation behind creating a WordPress theme, they need to bundle the nicer features into a paid package.

As Eric Karkovack wrote in his piece for Speckyboy, Are High-Quality Free WordPress Themes a Thing of the Past?, “Money changed the equation.”

There is not much incentive to push a free theme out to the directory just for fun. Most themers are spending a month or more of their time in today’s ecosystem to build a theme. The days of the weekend-afternoon project seem all but gone.

Even releasing a theme to give back can often be a letdown. There is little chance of any name recognition as the developer’s creation is swamped by the hordes of lite themes in control of the directory. There is no way for unknown players to get any exposure through the directory except in the brief moments their theme lands in the latest themes list. It is that one make-or-break moment that could potentially help best the algorithm and slip into the nearly unattainable popular list.

In comparison to Themeforest, the WordPress.org directory is lacking. Themeforest is inviting to users because it provides the backend tools for theme authors to market their themes. They can load up custom demos, provide screenshots, use a modern categorization system, and provide all sorts of extra data to end-users. They’re in the business of selling a product to users.

Screenshot of the Themeforest WordPress themes page.
WordPress themes on ThemeForest

While WordPress.org may be free, it should still be selling the promise of a beautiful website to its users. I have always said it, the themes available on WordPress.org are the face of WordPress.

Users deserve better. Theme authors deserve better tools to make it happen.

Even with better tools and a better-designed directory in place, there is no guarantee of an uptick of creative contributions or a better overall balance that keeps pure upsells in check.

“I think that due to the reach a theme or plugin that becomes popular quickly commands, monetization is a necessity to be able to properly ‘support’ such an endeavor,” said Joost de Valk, CEO of Yoast, in response to Mullenweg’s statement on Post Stats. “I think the community also ‘demands’ a certain stability and a certain level of support that is simply unfeasible to expect from any non paid contributor. Because WordPress.org has no way of doing that monetization ‘on platform,’ this is what you end up with.”

He also argued that something akin to an app store would make things like the “balkanization from non-G-based site builders” less attractive to theme authors. Such a store has little or no chance of becoming a reality.

“I think we first need to agree on what the theme directory should be,” he said. “We need a ‘mission statement,’ of sorts. And I think we probably need less control than we currently have, be much more like the plugin directory. But if we have a vision of what it should be, then we could work towards that.”

There is an opportunity to turn things around. Full Site Editing will leave ample room for releasing creative, fully-featured themes with upsells. There is plenty of reason to be excited about pattern design and template packs, better value-adds for theme authors who want to upsell. The problem is going to be getting authors to abandon traditional themes and explore new terrain.

Changes Are Coming, Maybe, Hopefully

Popular themes list on WordPress.org.
Popular listing on the WordPress theme directory.

For some, this is a song and dance they already know the lyrics and steps to. It is a years-long conversation that has netted little in return.

However, the WordPress.org theme directory may be forced to change one way or another. Block-based themes are not arriving in some distant future; they are knocking at the door. Full Site Editing is slated to land in WordPress 5.8 this June.

With this change, the WordPress.org theme directory needs to be prepared. Even with a move today, it will be a mad scramble to get systems ready in a handful of months. If waiting for the last minute, it is just asking for chaos. Block-based themes should already be allowed to be uploaded, for example.

As we saw earlier this week, Automattic launched its Blank Canvas theme. It is designed to work on single-page websites. It does not support commenting out of the box, which is a requirement for inclusion into the official directory.

Block-based themes will forever change the system. In the past, traditional themes needed to cover all their bases, integrating with every front-end feature of WordPress. In the future, that is not necessarily the case. Because everything will be built from blocks and users will have direct access to customize those blocks, a theme has no need to cover everything. The user can add and remove features at their leisure. The review guidelines need to be molded for this future.

Full Site Editing almost seems purpose-built for outside-the-box theme designers. Whether it is a simple, one-page wedding invitation or an author’s book landing page, there are more possibilities upcoming than there ever were in the past. And, these things will be far easier to build on the theme-design side of things. It will remove a lot of burden from developers and from the Themes Team during reviews.

“Regarding the FSE themes: to be honest all my hopes are there,” said Stathopoulos. “They are very different, and it’s a fresh start for the repository. New theme paradigm, a different set of rules (with of course some overlap for basic things), and a new way of doing things and thinking about themes. However, if they are presented in the same way in the same repo we have now, then nothing will change. the theme repo needs to change, and there’s no way around that. But that’s a decision that will have to be made from the WordPress leadership and implemented by meta.”

As always, I remain optimistic about the future of WordPress themes, hoping for the ushering in of a new era. I get the sense that the Themes Team shares some of that enthusiasm, at least cautiously so. More than anything, they need the community, particularly theme authors, to chip in and shape that vision of what the WordPress theme directory should be.

Perhaps today, the stars are nearing alignment. Mullenweg plans to chat with the team and gather feedback in the coming weeks.

Local Avatars in WordPress? Yes, Please

It is an age-old question. OK, well, it’s really a 10-year-old feature request, but that is age-old in software development years. Should WordPress have a local avatar system?

Let’s be honest. Most of us have kind of gritted our teeth and quietly — and sometimes not so quietly — lived with the Automattic-owned properties that are integrated directly with the core WordPress software. At least Akismet is a plugin and somewhat detached from the platform. But, avatars, a feature courtesy of Automattic’s Gravatar service, is baked deep into the platform. Users must disable avatars completely or opt into another plugin to distance themselves from it.

There are the obvious privacy concerns that some people have around uploading an image to the Gravatar service and creating an account with WordPress.com. Even aside from such concerns, regardless of whether they are warranted, new users who are unfamiliar with local avatar plugins are essentially guided to create an account with a third-party service to have one of the most basic features expected from a CMS.

Not all WordPress installs have access to Gravatar, such as within companies that use intranets. Some countries have the power to effectively block access to the service, as shown by the move China made in 2013 to block WordPress.com and Gravatar, leaving users to seek out alternatives.

The itch that many want to scratch is to simply remove Automattic-connected services from the core software. Gravatar’s inclusion in WordPress has hampered any chance of competing services gaining a foothold. To be fair, at the time of Gravatar’s initial inclusion in WordPress, there were few good options. It made sense to leverage a working solution that would get an avatar system rolling. And the notion of a globally-recognized avatar is noble — one service to control your avatar across the web. However, having that service under the control of a for-profit U.S. company will always be an issue that could potentially hold it back from being the service that the web truly needs. It will certainly always be a contentious issue in the WordPress community. Even those of us who love the software and services that Automattic offers can see the problem.

WordPress should be agnostic about what services it includes out of the box. Gravatar should be a separate plugin, even if it is bundled with core a la Akismet. Local avatars is not an insurmountable feature, and it might just be time to make the change.

While possible to build into core, it is not a simple matter of plugging in an image upload form on the user profile screen. The feature carries its own privacy concerns too. For example, uploading images currently requires certain permissions that would also provide the user with access to the entire media library. There is the question of how to deal with registered vs. non-registered users in such a system along with several other hurdles.

Recent chatter in the 10-year-old ticket and the #core-privacy and #core-media Slack channels have reignited the idea of local avatars. There is also an early spreadsheet on local avatar requirements and research.

Much of this discussion is amidst the backdrop of the WP Consent API proposal, which seeks to create a standardized method for core, plugins, and themes to obtain consent from users. Presumably, Gravatar usage would tie into this API somehow.

Matt Mullenweg, the co-founder of WordPress and CEO of Automattic, seems open to the discussion. “It’s exciting to see this older ticket picking up so much steam,” he said on the Trac ticket. However, he further pushed for a separate featured plugin that focused on broader privacy concerns.

In many ways, local avatars feel like the early days of the web in which users had to upload a custom avatar to every single website they joined. At times, it could be tedious. Gravatar solved this issue by creating a single service for people to bring their avatars along their journey across the net. However, we have seemingly come full circle in the last few years. With the passage of the European GDPR and other jurisdictions beginning to follow suit with similar privacy laws, it easy to see why there is renewed discussion around Gravatar in core.

We should have local avatars because it is the right thing to do. Provide a basic avatar upload system on the user profile screen. Beyond that, let users choose what they want by installing their preferred plugin without guiding them toward one particular service over another.

If nothing else, I’m excited about a wider discussion around local avatars in WordPress and welcome the possibility of such a featured explored via an officially-sanctioned plugin.

Themes of the Future: A Design Framework and a Master Theme

WordPress theming has a rich history. Over the years, theme authors have brought a plethora of features to the platform. In part, it is because they have often had to solve foundational issues with WordPress to create the features that end users want.

The post and body classes all theme authors use today? Those were originally in a theme called Sandbox.

Featured images? Those were popularized by magazine themes a decade ago.

You think post formats originated with Tumblr? Matt Mullenweg, co-creator of WordPress, taught us how to create aside posts in our themes in 2004, but they existed before that.

WordPress features often get their start in the theme world. We sometimes take for granted the years of experimentation and iteration on ideas where theme authors are putting in the work. Even the block editor is handling items that have traditionally been within the realm of theme design. The cover block is a good example. For years, theme authors built theme options for a basic hero image with text and buttons overlain. The result was often clunky and not ideal for users. By bringing this feature into core, it provided users the ability to put this cover block in any permitted block area.

The reason many theme features make it to core is that they simply work better when they are standardized. Users know what to expect, and theme authors can focus on the design aspect rather than solving the user experience problem.

Part of the problem of the past is that each new feature adopted into core did not follow any standard design pattern or naming scheme. A huge skill in designing WordPress themes is committing the mish-mash of hundreds of classes to memory.

The block editor is in a unique position to change that by creating a universal design framework.

Does WordPress Need a Front-End Design Framework?

With block patterns coming in the future and full-site customization at some point after that, theme authors are wondering just exactly where this ship is sailing. It is exciting because the possibilities are boundless for end users. It is frightening for theme authors who have built their empires upon one way of doing things, but development is more about adaptation than anything else.

Armed with the foreknowledge that the landscape is changing, this is the moment theme authors need to band together to shape their futures in a block-based world.

There is a bit of a running joke in one of the developer groups I am involved in that core developers are not theme authors. From the theme author perspective, it can sometimes seem like ideas are haphazardly thrown together with no thought toward CSS design systems.

Oh, I see some BEM. Why does this sub-element not follow the same naming scheme? Wait. Is that a 38-character utility class?

What WordPress has always lacked is a universal front-end design system. At times, that has been a good thing. It has allowed theme authors to use their preferred framework. Any theme author who has been in the game long enough will tell you, that sort of flexibility is great…until it is not. Have you ever tried adding contextual classes to widgets? What about adding a utility class to the comment form wrapper? You will need an Aspirin. Or two.

With WordPress, some things are set in stone and others are pluggable. Some features follow a standard class-naming scheme and others make no sense. The result for themes is often bloated CSS in an attempt to wrangle the various components.

It is next to impossible to fully use a utility-class framework like Tailwind CSS in a theme without recreating core features.

Much of this stems from years of legacy code piling up and WordPress’ commitment to backward compatibility. But, the future does not have to resemble the past. We are at the threshold of a new era, and now is the time for front end designers to jump into the conversation.

WordPress needs a solid front-end design framework.

That is a loaded statement. If you put 20 designers in a room and ask them to discuss design frameworks, it could be a recipe for fisticuffs. I tend to be an optimist and hope the debate provided results.

Gutenberg has pushed us partially in this direction, but it does not quite go far enough. With full-site editing in the future, there is a need for a more holistic approach in tackling this problem.

More than anything, we need more front end designers in the conversation. There is no way .has-subtle-pale-green-background-color should exist as a utility class over something like .bg-pale-green, .bg-green-100, or even .background-pale-green, if you want to be more verbose. There was no concept of optimization that went into that decision. In a time where developers are running on gigabyte internet connections, it is easy to forget that much of the world is following along at a slower pace.

A component-based naming scheme with a healthy dose of utility classes is one option that could hit several sweet spots. This is not an argument for one CSS framework over another. There are many good, existing options. WordPress should tackle this head on by borrowing from the groundwork laid down by other projects and creating something uniquely WordPress. It should be a leader in the field.

Design frameworks are also about plugins. There is some crossover into the realm of themes where the two have been waging an ongoing war since the dawn of the theme system. The battlefield between themes and plugins is littered with the deaths of good ideas. Far too many never garnered the support they needed to land in core. Some sort of universal design standard could stanch the flood of issues and call for a cease-fire.

A plugin that outputs a custom front-end component has no way of knowing how the current theme handles vertical rhythm, for example. Does it use top or bottom margin? What is the value and unit used? This is foundational stuff, and it is almost always broken when the plugin attempts to add custom CSS to handle it.

WordPress needs a design framework, or language, that allows all of its moving parts to come together in harmony on the front end. I am sure we will get there at some point. I hope that it is more cohesive than the random components and naming schemes of the past. We should also have a clear roadmap that fills in some of the technical details so developers and designers might be prepared.

Is a One-Theme Future Possible?

Rich Tabor makes the argument that core WordPress could provide a single parent theme in his article A Look at WordPress Themes of the Future. The idea is that theme authors would be relegated to creating a child theme for this “master” theme.

The gut reaction for many would be that it would not work, themes would lose their personality and we would live in a world of cookie-cutter designs.

The reality is that we are barreling toward a future where the idea of a single parent or master theme is a serious consideration.

Most themes are custom groupings of standard elements that exist in nearly all themes. There are some decisions, aside from stylistic concerns, that make themes different from one another, such as the layout of the header. One theme might have a site title and nav menu in one block. Another might have a nav menu, title, and a second nav menu below. Yet, another theme might show a search box. In a world where full-site customization belongs to the user, those decisions become a part of the user experience rather than the developer experience.

Themes will need to stand out with color palettes, typography, and their own brand of quirkiness — a return of the days of CSS Zen Garden but on a much larger scale.

I won’t be sad about that. It would be interesting to see the competition between the top designers in the field. It may also bring WordPress theming back to an era when anyone could do it with a little CSS knowledge and determination.

While we are not quite ready for a future in which one theme rules theme all, it is a place to start the conversation. If we designed WordPress for this potential future, even if we never implement a master theme, what would the roadmap look like? What obstacles stand in the way? Is it feasible?

The (Upcoming) WordPress Renaissance

The (Upcoming) WordPress Renaissance

The (Upcoming) WordPress Renaissance

Leonardo Losoviz

It has been 8 months since Gutenberg was launched as the default content editor in WordPress. Depending who you ask, you may hear that Gutenberg is the worst or the best thing that has happened to WordPress (or anything in between). But something that most people seem to agree with, is that Gutenberg has been steadily improving. At the current pace of development, it’s only a matter of time until its most outstanding issues have been dealt with and the user experience becomes truly pleasant.

Gutenberg is an ongoing work in progress. While using it, I experience maddening nuisances, such as floating options that I can’t click on because the block placed below gets selected instead, unintuitive grouping of blocks, columns with so much gap that make them useless, and the “+” element calling for my attention all over the page. However, the problems I encounter are still relatively manageable (which is an improvement from the previous versions) and, moreover, Gutenberg has started making its potential benefits become a reality: Many of its most pressing bugs have been ironed out, its accessibility issues are being solved, and new and exciting features are continuously being made available. What we have so far is pretty decent, and it will only get better and better.

Let’s review the new developments which have taken place since Gutenberg’s launch, and where it is heading to.

Note: For more information about this topic, I recommend watching WordPress founder Matt Mullenweg’s talk during the recent WordCamp Europe 2019.

Why Gutenberg Was Needed

Gutenberg arrived just in time to kick-start the rejuvenation of WordPress, to attempt to make WordPress appealing to developers once again (and reverse its current status of being the most dreaded platform). WordPress had stopped looking attractive because of its focus on not breaking backwards compatibility, which prevented WordPress from incorporating modern code, making it look pale in comparison with newer, shinier frameworks.

Many people argue that WordPress was in no peril of dying (after all, it powers more than 1/3rd of the web), so that Gutenberg was not really needed, and they may be right. However, even if WordPress was in no immediate danger, by being disconnected from modern development trends it was headed towards obsolescence, possibly not in the short-term but certainly in the mid to long-term. Let’s review how Gutenberg improves the experience for different WordPress stakeholders: developers, website admins, and website users.

Developers have recently embraced building websites through JavaScript libraries Vue and React because (among other reasons) of the power and convenience of components, which translates into a satisfying developer-experience. By jumping into the bandwagon and adopting this technique, Gutenberg enables WordPress to attract developers once again, allowing them to code in a manner they find gratifying.

Website admins can manage their content more easily, improve their productivity, and achieve things that couldn’t be done before. For instance, placing a Youtube video through a block is easier than through the TinyMCE Textarea, blocks can serve optimal images (compressed, resized according to the device, converted to a different format, and so on) removing the need to do it manually, and the WYSIWYG (What You See Is What You Get) capabilities are decent enough to provide a real-time preview of how the content will look like in the website.

By giving them access to powerful functionality, website users will have a higher satisfaction when browsing our sites, as experienced when using highly-dynamic, user-friendly web applications such as Facebook or Twitter.

In addition, Gutenberg is slowly but surely modernizing the whole process of creating the website. While currently it can be used only as the content editor, some time in the future it will become a full-fledged site builder, allowing to place components (called blocks) anywhere on a page, including the header, footer, sidebar, etc. (Automattic, the company behind WordPress.com, has already started work on a plugin adding full site editing capabilities for its commercial site, from which it could be adapted for the open-source WordPress software.) Through the site-building feature, non-techy users will be able to add very powerful functionality to their sites very easily, so WordPress will keep welcoming the greater community of people working on the web (and not just developers).

Fast Pace Of Development

One of the reasons why Gutenberg has seen such a fast pace of development is because it is hosted on GitHub, which simplifies the management of code, issues and communication as compared to Trac (which handles WordPress core), and which makes it easy for first-time contributors to become involved since they may already have experience working with Git.

Being decoupled from WordPress core, Gutenberg can benefit from rapid iteration. Even though a new version of WordPress is released every 3 months or so, Gutenberg is also available as a standalone plugin, which sees a new release every two weeks (while the latest release of WordPress contains Gutenberg version 5.5, the latest plugin version is 6.2). Having access to powerful new functionality for our sites every two weeks is very impressive indeed, and it enables to unlock further functionality from the broader ecosystem (for instance, the AMP plugin requires Gutenberg 5.8+ for several features).

Headless WordPress To Power Multiple Stacks

One of the side effects of Gutenberg is that WordPress has increasingly become “headless”, further decoupling the rendering of the application from the management of the content. This is because Gutenberg is a front-end client that interacts with the WordPress back-end through APIs (the WP REST API), and the development of Gutenberg has demanded a consistent expansion of the available APIs. These APIs are not restricted to Gutenberg; they can be used together with any client-side framework, to render the site using any stack.

An example of a stack we can leverage for our WordPress application is the JAMstack, which champions an architecture based on static sites augmented through 3rd party services (APIs) to become dynamic (indeed, Smashing Magazine is a JAMstack site!). This way, we can host our content in WordPress (leveraging it as a Content Management System, which is what it is truly good at), build an application that accesses the content through APIs, generate a static site, and deploy it on a Content Delivery Network, providing for lower costs and greater access speed.

New Functionality

Let’s play with Gutenberg (the plugin, not the one included in WordPress core, which is available here) and see what functionality has been added in the last few months.

Block Manager

Through the block manager, we can decide what blocks will be available on the content editor; all others will be disabled. Removing access to unwanted blocks can be useful in several situations, such as:

  • Many plugins are bundles of blocks; when installing such a plugin, all their blocks will be added to the content editor, even if we need only one
  • As many as 40 embed providers are implemented in WordPress core, yet we may need just a few of them for the application, such as Vimeo and Youtube
  • Having a large amount of blocks available can overwhelm us, impairing our workflow by adding extra layers that the user needs to navigate, leading to suboptimal use of the time; hence, temporarily disabling unneeded blocks can help us be more effective
  • Similarly, having only the blocks we need avoids potential errors caused by using the wrong blocks; in particular, establishing which blocks are needed can be done in a top-down manner, with the website admin analyzing all available blocks and deciding which ones to use, and imposing the decision on the content managers, who are then relieved from this task and can concentrate on their own duties.
Block manager
Enabling/disabling blocks through the manager (Large preview)

Cover Block With Nesting Elements

The cover block (which allows us to add a title over a background image, generally useful for creating hero headers) now defines its inner elements (i.e. the heading and buttons, which can be added for creating a call to action) as nested elements, allowing us to modify its properties in a uniform way across blocks (for instance, we can make the heading bold and add a link to it, place one or more buttons and change their background color, and others).

Cover block
The cover block accepts nested elements (Large preview)

Block Grouping And Nesting

Please beware: These features are still buggy! However, plenty of time and energy is being devoted to them, so we can expect them to work smoothly soon.

Block grouping allows to group several blocks together, so when moving them up or down on the page, all of them move together. Block nesting means placing a block inside of a block, and there is no limit to the nesting depth, so we can have blocks inside of blocks inside of blocks inside of… (you’ve got me by now). Block nesting is especially useful for adding columns on the layout, through a column block, and then each column can contain inside any kind of block, such as images, text, videos, etc.

Block grouping and nesting
Blocks can be grouped together, and nested inside each other (Large preview)

Migration Of Pre-Existing Widgets

Whereas in the past there were several methods for adding content on the page (TinyMCE content, shortcodes, widgets, menus, etc.), the blocks attempt to unify all of them into a single method. Currently, newly-considered legacy code, such as widgets, is being migrated to the block format.

Recently, the “Latest Posts” widget has been re-implemented as a block, supporting real-time preview of how the layout looks when configuring it (changing the number of words to display, showing an excerpt or the full post, displaying the date or not, etc).

Latest posts widget
The “Latest posts” widget includes several options to customize its appearance (Large preview)

Motion Animation

Moving blocks up or down the page used to involve an abrupt transition, sometimes making it difficult to understand how blocks were re-ordered. Since Gutenberg 6.1, a new feature of motion animation solves this problem by adding a realistic movement to block changes, such as when creating, removing or reordering a block, giving a greatly improved visual cue of the actions taken to re-order blocks. In addition, the overall concept of motion animation can be applied throughout Gutenberg to express change and thus improve the user experience and provide better accessibility support.

Motion animation
Blocks have a smooth effect when being re-ordered. (Large preview)

Functionality (Hopefully) Coming Soon

According to WordPress founder Matt Mullenweg, only 10% of Gutenberg’s complete roadmap has been implemented by now, so there is plenty of exciting new stuff in store for us. Work on the new features listed below has either already started, or the team is currently experimenting with them.

  • Block directory
    A new top-level item in wp-admin which will provide block discovery. This way, blocks can be independently installed, without having to ship them through a plugin.
  • Navigation blocks
    Currently, navigation menus must be created through their own interface. However, soon we will be able to create these through blocks and place them anywhere on the page.
  • Inline installation of blocks
    Being able to discover blocks, the next logical step is to be able to install a new block on-the-fly, where is needed the most: On the post editor. We will be able to install a block while writing a post, use the new block to generate its HTML, save its output on the post, and remove the block, all without ever browsing to a different admin page.
  • Snap to grid when resizing images
    When we place several images on our post, resizing them to the same width or height can prove to be a painful process of trying and failing repeatedly until getting it right, which is far from ideal. Soon, it will be possible to snap the image to a virtual grid layer which appears on the background as the image is being resized.

WordPress Is Becoming Attractive (Once Again)

Several reasons support the idea that WordPress will soon become an attractive platform to code for, as it used to be once upon a time. Let’s see a couple of them.

PHP Modernization

WordPress’s quest to modernize does not end with incorporating modern JavaScript libraries and tooling (React, webpack, Babel): It also extends to the server-side language: PHP. WordPress’s minimum version of PHP was recently bumped up to 5.6, and should be bumped to version 7.0 as early as December 2019. PHP 7 offers remarkable advantages over PHP 5, most notably it more than doubles its speed, and later versions of PHP (7.1, 7.2 and 7.3) have each become even faster.

Even though there seems to be no official plans to further upgrade from PHP 7.0 to its later versions, once the momentum is there it is easier to keep it going. And PHP is itself being improved relentlessly too. The upcoming PHP 7.4, to be released in November 2019, will include plenty of new improvements, including arrow functions and the spread operator inside of arrays (as used for modern JavaScript), and a mechanism to preload libraries and frameworks into the OPCache to further boost performance, among several other exciting features.

Reusability Of Code Across Platforms

A great side effect of Gutenberg being decoupled from WordPress is that it can be integrated with other frameworks too. And that is exactly what has happened! Gutenberg is now available for Drupal, and Laraberg (for Laravel) will soon be officially released (currently testing the release candidate). The beauty of this phenomenon is that, through Gutenberg, all these different frameworks can now share/reuse code!

Conclusion

There has never been a better time to be a web developer. The pace of development for all concerned languages and technologies (JavaScript, CSS, image optimization, variable fonts, cloud services, etc) is staggering. Until recently, WordPress was looking at this development trend from the outside, and developers may have felt that they were missing the modernization train. But now, through Gutenberg, WordPress is riding the train too, and keeping up with its history of steering the web in a positive direction.

Gutenberg may not be fully functional yet, since it has plenty of issues to resolve, and it may still be some time until it truly delivers on its promises. However, so far it is looking good, and it looks better and better with each new release: Gutenberg is steadily bringing new possibilities to WordPress. As such, this is a great time to reconsider giving Gutenberg a try (that is, if you haven’t done so yet). Anyone somehow dealing with WordPress (website admins, developers, content managers, website users) can benefit from this new normal. I’d say this is something to be excited about, wouldn’t you?

Smashing Editorial (dm, il)

WordPress 5.1 Beta 3, New WordPress Leadership, Newspack In The Works 🗞️ February 2019 WordPress News w/ CodeinWP

Hi, WordPress friends! 2019 started strongly, bringing a bunch of impactful news in the past four weeks. During this time, Matt Mullenweg made some major changes to the WordPress leadership team, Automattic announced the release of an open-source platform for journalists, the guys at WPML had to urgently solve a data breach allegedly caused by a former employee, while WordPress itself and the block editor went through another series of improvements and updates.