EDITS.WS

Category: wptavern.com

  • WordPress.org Enables Commercial and Community Filters on Plugin and Theme Directories

    During the 2022 State of the Word, Matt Mullenweg announced a plan to add new “Community” and “Commercial” taxonomies for the theme and plugin directories that would help users more quickly ascertain the purpose of the extensions they are considering. Shortly after the announcement, instructions were published for theme and plugin authors to opt into the new taxonomies.

    The new filters are now enabled on both the theme and plugin directories, giving users the ability to quickly sort between free community extensions and those with commercial upgrades. Anything with a “pro version” should be designated as Commercial. These usually come with some upsells for more features than are offered in the free version. So far, the number of themes identified as commercial vastly exceed the number of community themes.

    In the Plugin directory, extensions designated as free are nearly equal those designated as commercial. Many of the most widely used plugins have already been identified as commercial, including Yoast SEO, Jetpack, Akismet, Elementor, WooCommerce, All-in-One WP Migration, and more. Examples of community plugins include the WordPress Importer, Classic Editor, Classic Widgets, Gutenberg, Performance Lab, and Debug Bar.

    In both directories it appears only a small percentage of authors have designated their extensions using the commercial or community taxonomies. At this time, use of the taxonomies is not required. This gave rise to some questions in the comments of the announcement.

    “Would a better classification system would be to just have either no label for the majority, and then something closer to ‘includes paid upgrades’ that just implies they also offer additional services on top of their free (and often fully functional) version?” WordPress developer Kevin Batdorf said.

    “All plugins are open source regardless of whether they sell something, and that doesn’t make those developers any less passionate about open-source. Nor does it imply non-commercial plugins have any less features, or that the level of dedication to support is any less dedicated.”

    Batdorf also asked if use of the taxonomies would be a requirement in the future, because, at the moment, their low usage could give some plugins an advantage under these new classifications.

    “Should it also be a requirement?” he said. “Otherwise this also seems like something to be gamed for visibility. Do Community or Commercial (or neither) plugins show higher install growth? I guarantee you people are tracking this already.”

    WordPress’ Meta team is seeking feedback on the current implementation. Automattic-sponsored contributor Steve Dufresne said “work is continuously underway to improve the browsing experience and refine the visual aspects of the Theme and Plugin Directory as part of the site redesign.” The new filters will be incorporated into the upcoming redesign changes that have been slowly rolling out across WordPress.org.

    These filters will also be making their way into the admin theme and plugin browsers, so users can access them from wherever they search for extensions. In the meantime, users and theme and plugin developers can leave feedback via Meta Trac on the specific tickets outlined in the announcement, as the team continues to iterate on the project.

  • WordCampers Demand Changes to Q&A Format

    Q&A segments at a live event are a valuable point of connection where attendees have the opportunity to gain the undivided attention of the speaker or panelist and get answers to important questions. Inevitably, people who abuse the format can lower the quality of the experience for everyone. A Twitter thread addressing this chronic problem is gaining momentum today following the conclusion of WordCamp Europe 2023.

    “One problem is that they often add very little value – although they’re supposed to achieve the opposite,” WordPress Core Committer Felix Arntz said. “Unfortunately, those who ‘ask’ are often telling stories, promoting themselves or their business, [or] mansplaining the speaker.

    “Sometimes they’re not even asking any question at the end which is ridiculous. If that is you, you may not even notice it, but you are seriously wasting people’s time, potentially harming the speaker, and preventing folks from actually learning something.”

    Arntz suggested that those asking questions longer than a minute should forego the Q&A time and ask the speaker informally at a later opportunity if it is relevant.

    “Just to clarify, while some of the issues apply especially to sessions with more exposure, like a Matt Q&A, they all also apply to any other session,” he said.

    “While these problems mostly occur due to individual folks in the audience, I think the WordCamp organization needs to take action to improve the situation as it’s been happening for years.”

    Arntz proposed a number of actionable ideas, including submitting questions to a central platform where they can be upvoted by community members, discarding lengthy questions, and providing mandatory training or documentation for emcees on how to handle problematic Q&A situations. He also noted that having questions in writing can assist non-native English speakers in understanding other non-native speakers.

    Arntz also contends that Q&A should be optional, depending on the speaker’s preference. This may also have the added effect of creating a more inclusive environment for speakers.

    “Particularly for new speakers, it can cause lots of distress or anxiety, especially because, as mentioned before, it very often isn’t questions but any of the aforementioned problems,” he said.

    “All of this can be another blocker for folks from underrepresented groups to even apply to speak, which came up in the session on women & non-binary folx of WordPress.

    “Making Q&A optional is a great and simple way to at least improve the latter issue while working on addressing all the other problems. It’s literally just a decision to make, so I urge the community and organizing teams to make it.”

    Arntz’s thread has received positive feedback and support, and other WCEU attendees have joined in with suggestions for improving the Q&A format.

    “Many other open source conferences use apps that do more with Q&A, rating speakers, and even helping attendees schedule networking,” GoDaddy Developer Advocate Courtney Robertson said. “The favorited events export to iCal/gCal.”

    Raymon Mens, a first-time-attendee at WCEU, said he was “negatively surprised by the Q&A part” for every session. “I would have preferred some more time for the speaker to go more in depth and not have a long Q&A that doesn’t add a lot.”

    Jon Ang, an organizer for WordCamp Asia, said he is taking Arntz’s feedback into consideration for their next event, and future global leads for WCEU said they are also discussing these ideas for next year.

    “At WordCamp San Francisco 2011 there was a Q&A session with Barry and it used a P2,” WordPress core committer Aaron Jorbin said. “For the off topic questions, others often chimed in. I think an MC with knowledge of the subject matter asking questions off this would be perfect.”

    Changes will likely originate from WordCamp organizers who can recognize the existing problems with the current Q&A format and depart from tradition with a better way of bringing quality questions to speakers who wish to entertain them. Getting Q&A right may also become a stronger priority as WordPress’ community team evolves the WordCamp format to promote adoption, training, and networking. Based on the feedback on Arntz’s Twitter thread, it’s past time to update the Q&A format and WordCampers are eager to see it happen.

  • #78 – Mike McAlister on Why Block Themes Are the Future

    Transcript

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

    Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, a journey inside creating a block-based theme.

    If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast, player of choice. Or by going to WPTavern.com forward slash feed forward slash podcast. And you can copy that URL into most podcast players.

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

    We released these podcast episodes every Wednesday, but next week there’s going to be a break. I’m going to be heading to WordCamp Europe in Athens to record some more interviews. And if you’re there, I do hope that our paths cross. Normal service will resume soon.

    So on the podcast today we have Mike McAlister, and he’s here to talk about his experiences creating a block-based theme.

    Mike is a veteran product developer and designer in the WordPress space. He founded and sold multiple WordPress products, like Array Themes and Atomic Blocks. Now he’s focused on the future of WordPress with his new product brand, Ollie.

    Mike kicks off the podcast by telling us about his WordPress journey, and how WordPress blocks have renewed his passion for the platform. We get into some history and talk about the era when WordPress themes were extremely popular. Marketplaces like in Envato made it possible to sell themes and creates a career in ways hitherto unimagined.

    Mike explains what the key differences are between a block-based theme and a classic theme. How it’s possible to create themes inside the editor and how you can do this without needing to know much code.

    We talk about the fact that, if you are a coding expert, you could always create complex themes, but this fresh approach opens up the possibilities for those with less technical backgrounds. The experience in the editor might not be exactly what everyone wants, but it’s evolving quickly and maturing with every new release of WordPress.

    The conversation moves onto why Mike is so confident that block-based themes are going to succeed. You don’t need to use one, and your trustee classic theme and the associated customizer, will work for the foreseeable future.

    We then turn our attention to the technical hurdles that Mike has had to overcome. What new workflows and tools did he need to adopt and master to make his work possible? Mike’s been really focused on using WordPress core blocks to create his themes, digging into the weeds of what they can do and what their limitations are. It’s been a part of steady learning punctuated with minor setbacks when the editor and blocks are updated in unexpected ways. Thankfully, these bumps in the road are now relics of the past, as breaking changes have given way to stability.

    We then talk about a specific theme that Mike has just released. It’s called Ollie, and it’s the focus of the rest of the podcast. How did Mike build Ollie, and what is he hoping to achieve with this new brand?

    Patterns feature heavily in Ollie we talk about how it’s possible to alter the look and feel of your site quickly. Typography and colors are easy to change with the new suite of design tools which ship with WordPress.

    If you’re wanting to develop block-based themes, or are just curious about how other developers are building them, this podcast is for you.

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

    And so without further delay, I bring you Mike McAlister.

    I am joined on the podcast today by Mike McAlister. Hello, Mike.

    [00:04:51] Mike McAlister: Hello. Thanks for having me.

    [00:04:52] Nathan Wrigley: Yeah, you’re very welcome. Mike is going to be talking to us today about block based themes, block patterns, blocks in general, I’m sure. And if you haven’t been in the WordPress space for any great length of time, you are about to learn about Mike’s pretty impressive history in the WordPress space.

    So Mike, it’s a fairly generic question, but I hope you don’t mind us asking you at first, just to orientate the listeners. Would you mind just telling us a little bit about yourself and your history, coding, theming, and whatever kind of other work you’ve done in the WordPress space.

    [00:05:24] Mike McAlister: Absolutely. Yeah, I’ve been around WordPress for some time now, probably since about 2010. 2009, 2010. So fairly early on. And I think I came upon WordPress like many folks, building client sites and looking for just a better way to do it. You know, when you’re in that world and you stumble upon WordPress, you’re like, whoa, light bulb moment. This is going to be a game changer.

    So yeah, I started pretty early on using WordPress to build websites for clients. And then at some point, I started to see the commercial aspect of it, right? Instead of building one theme for one client, I could build one theme and maybe sell it to a thousand different clients.

    And so I experimented pretty early on with, you know, I have a history in design and so that was my focus. I thought that could be a differentiator for me. I’ll make themes that are just beautifully crafted, really lightweight. Maybe they don’t do everything under the hood, but they do specific things very well.

    And so Array was the first theme shop that I had. And I operated all over the place. I had themes on my own site. I had them on the Themeforest marketplaces. I was selling themes on wordpress.com. So I was kind of everywhere and growing. And then at one point blocks became a thing, and so I dipped into there and started experimenting with blocks, via the Atomic Blocks theme which grew really quickly, it was one of the first block themes out there. And I think it was, blocks were still a really new thing and people were trying to understand what they were and what the benefits could be.

    And so having a plugin out there with all these examples in it, and kind of showing that, oh no, you can replace all kinds of stuff. Like short codes and all of these other archaic ways of building could be done with blocks now.

    So I worked on that for a bit. And then in 2018 WP Engine acquired both the theme shop and the Atomic Blocks plugin. And worked there for four and a half years, and then just recently I have gone back into the freelance and entrepreneurial space.

    [00:07:21] Nathan Wrigley: Thank you very much indeed. That’s really, really interesting and it sounds to me at least anyway, as if you arrived on the WordPress scene, not only with the right products, but also at the right time. You kind of managed to hit that tidal wave just as it was creating out in the ocean somewhere.

    And you had the product. Everybody was buying themes at that time. Became really, really popular. Do you consider yourself to have had a lucky break there, in the sense that, do you feel that that is something which can be repeated in the year 2023? Or do you think that block themes and just themes in general, the shine and the commercial prospects of that has dwindled a little bit?

    [00:08:04] Mike McAlister: That early era was certainly something special. I think there was just so much attention focused on themes, and as this new shiny thing. And they unlocked a lot of capabilities for people. They were able to go from, trying to make their own sites. To making their own designs. To having these tried and tested templates.

    And so that was a huge thing. And the rise of the Envato market at the time was a huge part of that success. Love it or hate it, at the time, that was a huge thing and proliferated WordPress themes out into the world, beyond our bubble. And so that I think was a huge deal at the time.

    Now, whether or not now we can kind of replicate that is really tough to say, because since then the market has become quite saturated, in that there are so many different ways of building with WordPress. And you have things that are spinning off like Elementor going off into their own world.

    They’re still kind of one foot in WordPress, one foot out. And we have all of these other. website builders that we didn’t have back then, other platforms. So there’s just so many different ways to build a website. WordPress is still massively popular, even if it’s slowly declining.

    We still have such a huge footprint on the web that it, there’s a ton of potential So, I don’t think we’ll see the same wave we saw before. I do think though that this whole new world of the block paradigm and block themes. It is the biggest opportunity commercially in WordPress I think that we’ve seen in a very long time. It may be the biggest we see for a long time.

    [00:09:38] Nathan Wrigley: Yeah. I think we should probably stray into that right, the outset, if that’s okay. Because, there’s probably a proportion of people who are listening to this podcast who are very, very technical. They completely get what you mean by block based themes and the opportunity afforded there.

    But equally, there may be a bunch of people who are listening to this who genuinely have no idea that there is such a thing as a block based theme. They’ve got a, what we would now call a classic theme, and it’s installed and it has been for a long time. And as far as they’re aware, there’s no change in their WordPress website. Things just carry on as normal.

    But are you able to describe to us, I know this is a difficult question, and certainly trying to cram it into a portion of a WordPress podcast is a big ask. But are you able to give us a high level view on what a block theme is, and how it differs from a classic theme? Something which you might know, if you’ve got access to the customizer, you have a classic theme. If you don’t, you don’t. And so let’s take it from there. What are they and what do they promise?

    [00:10:34] Mike McAlister: Absolutely. So, let’s first just do quick block refresher in general. So blocks, instead of throwing your content all into TinyMCE or the content area, and kind of making it mostly text-based, and throwing some other little elements in with things like short codes, like we used to do in the past. Blocks, they’re basically content elements. It could be anything from a button, to a paragraph, to an image gallery, to a slider.

    And all of these things you add to the WordPress editor. And they could be used to build, you know, more beautiful content. They could be used to build page sections. They can be used to build a full page. And you put together enough blocks, and you can build an entire theme with it, right? So, WordPress comes with many blocks built in. And all of these things you use to build your website now.

    So with that in mind, block themes are effectively entire WordPress themes that are built entirely with blocks. And the benefit of that is that it makes your website almost entirely editable by you, in the editor. So instead of having to, you know, if you want to change your header, instead of going into the code and opening up the code editor and tinkering there and saving and going back to your site. You can go into the site editor and WordPress, which is effectively a interface inside the WordPress admin, where you can create your header.

    You can modify it. You can change the colors. You can add new links. You can change out your site logo. And all of that happens in the editor. It can be a no-code or low-code experience for you. So the benefit here is the customization, right? We can now get closer to the experience that you might have seen at something like a Squarespace or Wix where the interface and the experience is tailored around creation, and it’s more focused around that.

    [00:12:31] Nathan Wrigley: Yeah, I guess if you are an expert themer and you’ve been creating themes for years, what it brings to the table, the way that you construct them is different. But you’ve always been able to achieve whatever it is that you wanted to achieve because you could write the code. But I suppose what this is bringing is the capability for non-technical people to be able to modify just any part of the site.

    I guess the header is typically fairly constrained, you know, header, navigation, logo, that kind of thing is normally what we see. But perhaps a better example would be a footer. Because typically your footer would be controlled by the theme and you’d go into the customizer and modify whatever options were available to you.

    Whereas now you can just build out rows, columns, put in images, put in contact forms, whatever you like, other navigation menus, anything. If you can imagine it as something that you can build in the block editor, that can then become your footer. You don’t need to dabble in any code at all. There’s a lot going on there, but you don’t need to be involved in that.

    And so non-technical people can become involved in that process and, you know, enjoy creating different aspects, different parts of their theme. That being said, what are your thoughts on the state of the UI for editing themes at the moment? We’re in May 2023. Version 6.2 of WordPress is the current latest version.

    And I think it’s fair to say that it’s not where it probably wants to be in the end, but how do you think about it? How do you think about the UI? You’ve probably been in there, you’ve ironed out all the kinks, and got over all the road bumps that were in the way. But for a typical user, a non-technical user, do you feel it’s delivered on the promise that it hoped to?

    [00:14:09] Mike McAlister: I don’t think so yet. I talked to all kinds of WordPress users from novices to veterans. And the number one thing that always comes up is the UI the UX, the experience. And, you know, I get it because we’ve known WordPress for 20 years now. We’re celebrating a 20 year anniversary right now.

    And it has been one way for a very long time. And even some of the big changes that came, like the customizer, they weren’t that big of a change, right? They were bolted on and they were additive and iterative. But the block editor and going into the site editor and full site editing, these kinds of things, it’s quite different.

    It’s adding a lot to WordPress. It’s a lot of new context. It’s a lot of new paradigms. It’s a lot of new workflows, and I think that is a very difficult thing for people to figure out. Especially with the past few years where things have been shifting so much and people don’t know quite when to hop in. And then when they do, it doesn’t work exactly like they had anticipated.

    Or some of the features are released as working prototypes. We’re kind of met with these things. And so I get the frustration when you hop in there and somebody’s telling you, oh, it’s way better, and you can do all this stuff now, and you’re, you install a block theme from dot org and it’s like half busted, and the styles don’t work and you don’t know your way around. So I get it. It can be a very frustrating experience.

    I will say the past few releases I think have been a lot better. And they’re ironing out a lot of the kinks. The ground underneath the software isn’t moving as much from release to release. And if you follow along on some of the GitHub tickets or you stumble into some of those, there’s a great deal of discussion going on about the many shortcomings of the UX. And so it is something that’s always being worked on. And I think it’s important to just remember that.

    It is never going to be easy to change, to drastically change, a piece of software that is being used for so many use cases, for so many people. We know it powers half the web and to make a leap into the block era like this, it was never going to be easy. It was never going to be comfortable.

    We hope that it will be worth it in that, these kind of growing pains in this transition will give us a new era. It will refresh WordPress. It will make it viable for another 10, 20 years. It will give us the new tools to keep up with these other platforms that are maybe outperforming us. And so while the growing pains are there and the experience is a little rough, I do think that it is all for the greater good of the software.

    [00:16:45] Nathan Wrigley: Let’s explore the sort of reverse of that, if you like. And I’m going to use a product that I have as an example. I use Gmail to do my emails. And I have this Chrome extension, and the Chrome extension alters the Gmail interface in a way, which allows me to be slightly more productive. I won’t get into the detail, but it does that.

    And every couple of weeks something breaks, because Gmail alter some aspect of their interface. And the guy that makes the Chrome extension, he’s not in the loop of that. And the thing breaks and he has to contact all of his users and say, right on it. And gets it fixed and so on and so forth.

    And I feel, as we’re going to discuss in the future, you are now really committed to having a proportion of your income come from block based themes, and yet at the same time, although you’ve got, you’ve got a voice there and you’ve definitely got skin in the game. You are reliant upon the technology stack that is WordPress and it’s in a constant state of flux.

    You said it’s not quite there yet. I just wondered, and I don’t wish for you to become incendiary or anything like that. I wondered if you could highlight some of the grievances that you, well, not grievances, some of the things that you wish were better right now. Some of the areas where, if you could be in control of just fixing it by clicking your fingers, what would you amend?

    [00:18:03] Mike McAlister: Ooh, that’s a, that’s a really good question. Although I’m just releasing a block theme now, I’ve been dipping into and exploring block themes for years now. And only until recently did I feel like, okay, this is ready enough to put something out there. Because I’ve run a product business before, and a WordPress theme business before and support is a huge part of that, right?

    And in these early days of the block editor and block themes, with it being, you know, on a bit of shaky ground. Putting something out there I’ve seen it as like a support nightmare. I’m going to end up not just supporting my theme, I’m going to end up educating people on tons and tons of WordPress features, which I think that’s okay and great. And I think it’s actually a business model in itself.

    You don’t want to take on the frustration of the users, and have them funnel that through to something that’s your product, right? And they look at something I’m making and say, this thing sucks, or whatever. When really it’s just they don’t know this new WordPress yet, or they haven’t had the time, or that the pitfalls and the UX hurdles are being kind of painted onto your product. So yeah, I think up until recently I’ve felt like, okay, this is, it’s still going to be a bit of a transition, but I think it’ll be less painful.

    So that being said if I could snap my fingers and have one thing, well I’ve just recently written a post about responsive controls, which is another big hurdle. But I think even more than that, I would snap my fingers and bring together this UI UX in a way that makes a lot more sense.

    I feel like we’re in two worlds here. I think we have many remnants of the old WordPress. In fact, if you’re not in the site editor, you maybe wouldn’t even know that there’s a new WordPress. You’re looking at the same sidebar, same posts, pages. All of that is the same and that’s great. That’s worked well for a long time.

    But now we have our other foot in this whole new era of the site editor and block editor and blocks and block themes. And then when you’re in the site editor you can edit things live and do all this stuff. And so I feel like there are two entirely different WordPresses existing in WP admin. And it is, to me, not a great experience. I feel like if we’re going to go this route, I feel like it should be almost entirely wrapped around the site editor experience, and we’re able to do almost everything in there.

    And that gives us an opportunity to maybe rethink, and this is, I know, grandiose and big ideas, and there’s probably a lot of people who are cringing at the thought of redoing a lot of WordPress. But I think that there is an argument to be made about kind of moving forward in a more bold and meaningful way. And tying that experience together. So that when you’re editing a page, it looks like you’re editing a page, and not like you’re editing a page with content field or something like that, you know? So the great unification of sorts.

    [00:20:57] Nathan Wrigley: Thank you. That’s really fascinating. In terms of the skillset that you’ve had to adopt over the last period of time. When you decided, okay, I’m going to go all in on blocks. And it sounds like you’ve been doing this really, right from the beginning, which is fairly impressive. Very prescient of you.

    What are the new interesting, perhaps difficult, things that you’ve had to learn? The new tooling that you’ve had to acquire? What has had to become part of workflow over the last few years, which is different from how it would’ve been five, six years ago?

    [00:21:26] Mike McAlister: Yeah, it’s It’s quite fascinating actually, because I think those of us who are in WordPress a long time, you would typically think that the answer would be like, oh, I had to learn Webpack or React or whatever. And if you’re building blocks, that might be the case. When I’m talking about block themes, it’s not a technical skillset that I’ve had to pick up.

    But literally just spending the time in WordPress and understanding how all these things work together. Learning fluently how to build with all of the core blocks, in a way that you can build a layout using columns and groups, and the alignment settings, and justification and the row block. It is a skill that has to be learned use all these things fluently, and to just know it like the back of your hand so that you can go and build out a pattern, a page, whatever it is.

    And that did take, even for a WordPress veteran like me, quite a bit of time to get fluid with that stuff. But learning all of that stuff and then kind of dipping into block themes, that made that process a whole lot easier. Because block themes are just all of those things. It’s the row block. It’s the group block. It’s using the padding settings and building a design system with theme json.

    So that becomes a skillset in itself. And that’s where I spent so much time. And I think that’s why when I released this Ollie theme that we’ll talk about, I think a lot of people were kind of like blown away. Like, oh, you can do all this with this new stuff. And it’s all core and native features.

    But it took me a long time to pull all that stuff together and to be able to present it and a package that was like, oh, okay, this is coherent and well made and well designed and it actually works.

    [00:23:07] Nathan Wrigley: How much does the sand shift beneath your feet? So you mentioned earlier about getting skilled with the interface and using the group block and managing it to make these pixel perfect, really beautiful layouts which we’ll get onto in a moment. How steady has that process been?

    Or have you noticed that your designs from, well, let’s not say month to month, maybe half a year to half a year. Are there things which come along in the core blocks, changes which are made in the core blocks, which upset what you’ve managed to lay out in this perfect way? Or has the progress been steady away? Everything looks the same today as it did a year ago.

    [00:23:43] Mike McAlister: At this point, it’s very steady. The core blocks, the group blocks and things like this, buttons. These are not changing in any major way. There are little additions being made, but they’re iterative, and they’re backwards compatible as far as I’ve seen. There might be every once in a while, the spacing’s a little off or something like that and usually gets fixed pretty good.

    But I think with the amount of people using the Gutenberg plugin, where a lot of these big features are tried and tested and workshopped. I think there’s a good amount of eyeballs on these features there. That definitely helps, by the time it gets to core, it’s been vetted, it’s been worked out.

    People actually build with Gutenberg enabled. So I think there’s that. And so these days, when creating a theme, I didn’t have any major issues with the fundamentals.

    [00:24:31] Nathan Wrigley: Nice. I’m going to direct everybody listening to this podcast. Maybe just pause and go to this URL. The URL is olliewp.com. It is, as you might expect, o l l i e w p .com and have a little poke around. Have a look at what Mike has built, and what’s on offer. But just tell us about the theme itself. I’ve had a little bit of a play.

    I downloaded it. Currently, we can get onto this and the reasons for moment, it’s on, available on GitHub. You download it from there, and I installed it on a local install and had a play. Tell us a little bit, what’s the thinking here? Are you trying to make one theme that anybody can use? Do you have a particular niche in mind? What’s going on with Ollie?

    [00:25:13] Mike McAlister: I think Ollie started as an experiment for myself. I used it as an opportunity to, like I was saying, to learn all of these features. And one of the best ways to learn them is to build a block theme. Because it forces you to use all these different things, like patterns and global styles, and theme json. All of these features that make up a good block theme.

    So, I started it as an experiment to learn, and then along the way, you know, as a product minded person, and somebody who’s had a theme shop before, I thought, no, there is some commercial value here. I don’t know what it is yet. But I thought on top of it being a potential pivot for me to do, I just saw it as an opportunity to dip back into WordPress in a more meaningful way, in the product space.

    And I like creating things that people can learn from. I like putting things together in a package that you can hand off to somebody or send them the repo and they can see, and pick through the code and learn. And so that was the kind of intent behind Ollie. And right now it is, it’s just one theme with a bunch of beautiful patterns in it that you can use to quickly build out pages.

    I’m just using this early phase of Ollie to see what people think. How are people building with block themes? Are they building block themes? I think there’s so much unknown about this space because it’s so new, I’m just kind of sitting back and just learning and listening and watching people.

    Do they want more patterns? Do they want pre-made sites with block themes? There’s so many questions that I have. I’m using it as an opportunity to effectively ask these questions and learn.

    [00:26:41] Nathan Wrigley: The thing that really struck me, I should add at this point that I saw this from an article in the WP Tavern, which Sarah Gooding wrote on April 26th, 2023. I’ll link to that in the show notes. The thing that struck me immediately was the patterns. And I saw screenshots of the patterns and I thought, wow, they look great.

    And there was a video that I think she put together, scrolling through some of the patterns and thought actually that’s new, that’s interesting. They are right on the money for me. They look how I wish I could do things. And so downloaded the theme and really discovered that you really have gone to town with the patterns. I don’t know what the number is. It certainly looks like it’s more than 50 or 60 or something like that.

    That feels like where a lot of your endeavors have gone. So you’ve categorized them, obviously now in the site editor you can you click on the patterns button and then subcategories come down. And then a nice thumbnail appears, and you can enlarge those if you wish, on a big modal, which takes up the whole screen and so on.

    You’ll see straight away that the effort in building a typical website, brochure site for somebody has been taken away. So that’s my question. Did you approach this with patterns in mind? Like this is going to be a repository of great patterns and the rest hopefully will build itself, if you know what I mean.

    [00:27:56] Mike McAlister: Yeah, absolutely. I knew right away patterns were and are going to be a huge deal. Way back, late 2019, I was even playing with this rudimentary idea of what patterns could be with my friend John Paris. We experimented and prototyped out this idea of sections and layouts in WordPress. And it was effectively what would become patterns. This idea that you have pre-designed sections of your site, that you can click together like Lego pieces and make full layouts.

    I’ve always looked at patterns as a huge opportunity because it takes the pain out of building websites or even just sections. If I’m able to put together a beautifully designed hero section, or a featured section with blocks and make it look great and hand it over to you. You can throw that on your page. You don’t have to mess with the design. You just tweak the colors if you want, and change the content. And then you go about your business.

    We’ve removed the pain of even you having to build your own blocks or your own patterns. And hopefully that is the paradigm that we go with. Hopefully people latch onto this idea that maybe I don’t have to tinker with every single part of my website. Maybe just going with these beautiful designs, changing the content, changing the color, and then focusing on my content, and focusing on my audience and focusing on my following. And I think the patterns are going to be a huge deal for sure.

    [00:29:21] Nathan Wrigley: Truly I think the designs are absolutely fabulous. They are categorized into posts, texts, call to action, cards, features, heroes, pages, prices and testimonials. Who knows, maybe that will be expanded over time. But in each of those there’s in some cases a handful and in many cases multiple dozens really of different patterns that you can select.

    And if you’ve never had the experience of doing this in a theme, you just pick on one that you like, and you just click on the icon and there it is. It’s now the next part of your website. And you can then amend it, you can change it.

    Give us a bit of an insight into what people can do in terms of saving things. So let’s imagine that they’re using yours as sort of boiler plate and they’re going to click things in, but they want to amend the colors. Yours is fairly opinionated. It’s nice dark black, and there’s this lovely kind of blue color, which dominates everywhere. But obviously that might not fit with everybody.

    Is it fairly straightforward, again for inexperienced users, to save those and modify them and keep their own modifications with this new site editing interface?

    [00:30:25] Mike McAlister: Absolutely. That’s kind of the beautiful part about this, right? Is that you can go into one of your preexisting pages and click to add one of the patterns I’ve designed, and put it on your page. Or you can throw a full layout, which I’ve included a few full layouts, like home, about, and features, and things like this.

    You throw it onto your page. You customize it how you want. You can change the content inline. You can change the colors on the page if you want. Or you can go to the global styles in the site editor, and you can change that bluish purple color that I’ve chosen to whatever color you want, your brand color. And instead of going through and changing it in every little pattern, it will change that color on every single pattern I’ve included in this theme.

    So you don’t have to go change the colors anywhere. It will literally propagate that color throughout the whole site. Because this whole thing is a live design system, right? It’s effectively a design system that is tied into every aspect of WordPress. So when you’re in the site editor, when you’re in posts, when you’re in pages, all of these styles travel with these patterns.

    Even typography, you don’t like the font? You can change the font. It’ll propagate through the whole thing because that’s how this is all wired up. So yeah, so if you want to go in and change a page, all you do is, you go in there, add a pattern, save it. Save it just like you would any other page. And it’s good to go.

    [00:31:47] Nathan Wrigley: Yeah, it is increasingly becoming a really compelling system. It just requires people like you to get as many people over that hump as possible and experiencing it. But I can only say if you download it, have a go. Within minutes I suspect that you’ll have something that you are very, very happy with and that you can modify.

    In terms of the patterns of themselves, is that an area that you’ve explored? Or would like to explore commercially? So okay, I know you’ve got Ollie, but have you given any thought to the commercial possibilities of just patterns, simply patterns? Not bound to any theme. Just a downloadable set of patterns. And obviously you’re a very, very credible designer, we can see that. That you could then give to people, sell to people, so that they can download them into any site no matter what block-based theme they’re using.

    [00:32:34] Mike McAlister: I always knew patterns were going to be a big deal. But I think, after just releasing Ollie to GitHub and seeing it get picked up by a few news outlets and some people on YouTube, were making videos about it. I think the number one thing everyone always raves about is the patterns. And maybe if they’ve explored patterns before on wordpress.org or used other themes that have patterns.

    I don’t know if they’re just kind of underwhelming typically. But I think I did spend a great deal of time making sure these patterns were making a statement. They are saying, no you can do this in WordPress. I wanted to prove that I can design something as good, if not better, than what we had before. And I’ll do it all with blocks, native blocks. Not one custom blocks in there. These are all just core blocks, and they’re going to be beautiful, and they’ll be fully responsive and fully customizable.

    And so, I think that’s what people see. And when they see these patterns and how they all cohesively fit together. You can pop these onto a page in any different order and they kind of just fit together and that’s part of the overall design system. But yeah, so I see patterns as a huge opportunity and I wasn’t sure commercially. And still I don’t know. I’m using this opportunity to ask a lot of questions.

    But I think the first few weeks, the response has been largely very positive about patterns. And so I’m definitely curious about that. And I think there’s opportunities to do more advanced patterns, and maybe use some pro blocks to make patterns even more appealing. So yeah, pro patterns is definitely something I’m exploring

    [00:34:07] Nathan Wrigley: You mentioned that you’d spent a lot of time learning the core blocks, and you also just mentioned that everything that comes with Ollie is based around a core block. Was that a straightforward experience? Or did you find that there are certain limitations in what you could achieve based upon the capabilities of core blocks? Or would you say basically you can implement almost any design you wish with core block? Certainly looks like you’ve managed to achieve that.

    [00:34:34] Mike McAlister: Sometimes I’d have an idea of what I wanted to do, and couldn’t quite do it. But I think if you get clever, you can get really close, right? For example, I would love if WordPress had a icon block. A core icon block that we could tie into. I don’t want to have to make my own, because there’s a bunch out there.

    And I also, you know, in terms of the ease of distribution and giving customers designs right out of the box. I don’t want them to have to install a plugin to do it. And icons are so prolific. I would just hope that we could have that in core. Well, we can’t have that yet. And so, when doing simple things like wanting to add an icon here for people to see like, kinda like a placeholder for an image or an icon.

    I used the HTML star, right? And I use that in ratings, you know, in design, like if you want to put a rating there, I put like five HTML stars, and I use it on feature sections. So, clever little things like that. It’s giving people enough to understand, oh this is what this is meant to be. This is the design. Oh, I might put my own icon here. Or even things like cleverly using the rows and group blocks to get things aligned how you want. Grouping of blocks to do unique things with them, spacing wise. It’s just a lot of clever usage of what’s there.

    And I think part of that does come from tinkering enough. And if you really want to get that design out of your head and on to the page, you’ll figure it out. But it might take, it might take some tinkering.

    [00:36:01] Nathan Wrigley: Yeah, I’m on the install that I have at the moment and I’m on the star rating. You’ve got five stars, and I can see that they’re using paragraph blocks. And then elsewhere you’re using the social icons block to display those social icons. And I guess that’s the experience you would want, is just pick an icon, much like you do in the social icons block and make it more straightforward. That’s really interesting.

    Why GitHub? Why not the WordPress repo? Was there some sort of decision there? Again, I should emphasize it, at this moment in time, if you want to grab this theme, you’re going to be heading over to GitHub and downloading it. Why there and not in the repo? Is there a decision behind that?

    [00:36:36] Mike McAlister: No philosophical decision. I think it will be on the repo soon actually. Like I said, with these block themes, there’s so much to learn and I wanted to put it out there. You know, it worked great for me when I was building it and making it. But I wanted to get it out there and get people using it to understand if there was any major shortcomings or just catch any early usability patterns that I was seeing. Any issues like that and see like, oh, actually people don’t love these patterns.

    Or, is there something about the workflow that I could improve before releasing it to a wider audience? So, I just mostly wanted to iron out all the kinks and GitHub was just the obvious place to do that. But to be honest a lot of the quirks that people have brought up with the theme on GitHub and the GitHub issues and stuff, are largely just Core issues. Just usability, preferences and workflow preferences and things like that.

    I haven’t uncovered any major issues and so I feel like what I’m going to do is kind of wrap it up. It’s already fully tested and gone through the theme check and everything. So it’s pretty much ready to go. And I think I’ll do that in the next week or two.

    [00:37:41] Nathan Wrigley: Oh, okay. In that case, by the time this podcast airs, this question will be somewhat moot. But anyway, worth, asking I think. I noticed as I was moving around on the site, olliewp.com. I noticed buried somewhere was referenced to Ollie Cloud, and that got me thinking, okay, in that case, is Ollie something bigger than simply this one theme?

    And so that’s where I’m going to take the conversation next. Is Ollie, in the same way that you had Array Themes and you had Atomic Blocks. Is Ollie something bigger for you, Mike? Is that a direction that you’re going to take it in? Are you now hoping to, sort of, have a bunch of things wrapped around in the Ollie branding?

    [00:38:22] Mike McAlister: I think so. I wasn’t sure about that initially. Again, this just kind of started as a experimental WordPress theme. But I don’t know the product creator in me, the entrepreneur in me, always tries to see things from that sphere as well. And so as I’m looking at the WordPress ecosystem, and I’m exploring what is this thing like now? It’s been a while since I’ve had a product out there.

    I do see all kinds of opportunities, and I’m still learning what they are. But I also have my own opinionated ideas about how we could wrap up this new, all these new capabilities, and deliver a new experience. A premium experience with some of this stuff. And so, on the Ollie WP website I had, I do have a box at the bottom about Ollie Cloud. And the idea there, I think is it could be Ollie Cloud, it could be Ollie Pro. I don’t know. I’m really just gathering feedback and seeing what people want, as I mentioned.

    But the idea is that all of these new features, these theme assets, patterns and theme json files and all that stuff. They’re all very lightweight, and very movable, and very modular, and they can kind of plug and play in to WordPress. And I don’t know, I think there’s an interesting idea about the experience about how we build sites these days.

    Should you have to start from scratch on every site? And should we still be copying and pasting themes around like it’s the mid two thousands? And is there a better way of doing that? Is there a better way of pulling in a site template?

    There’s a lot of interesting things there and I think, another thing I’m learning, and I think we’ve seen just generally is that, I don’t know, I think users are maybe a little fatigued with that in WordPress. Starting with a blank slate and being like, ugh, I have to find a theme and then I have to maybe try out a few themes, and then I don’t know if I need to pay for one, and then I need a form block, and then all of a sudden I need a buy a contact form.

    And then there’s a bunch of upsells for contact forms. And I don’t know. All that stuff to me, after all these years on WordPress, feels kind of icky. Uh, I guess. And I think customers and users want experiences and solutions more than they want individual themes and plugins. So a premium offering or a premium experience is something I’m interested in. What kind of experience can we do differently that delivers the same result, but takes all of the pain building on WordPress?

    [00:40:46] Nathan Wrigley: It kind of feels as if you may be repeating history for yourself here in that, you know, 2010. Array themes, we mentioned you were right there at the beginning of that tidal wave. Maybe with a fair wind, the same thing may happen again here? You may well have discovered that seam of gold, just as it’s starting to take off. Because all the chatter that I’m listening to at the moment is very much related to blocks and exploring patterns, blocks, block based themes, and how you can maybe tie those three things together.

    And pro blocks, which bring additional functionality. You know, areas where Core perhaps doesn’t cut it. I’m thinking, in my case, one that just keeps coming into my head is a superior navigation block, that does a whole load of styling and what have you. And who knows what’s going to be around in two or three years time? But there do seem to be companies who are straying into this and dabbling with it and trying, like you are, I guess, to figure out what the landscape may look like.

    [00:41:43] Mike McAlister: Yeah, I’m just as unsure I think as anybody about where this thing goes. But I’ve never been afraid to try and put in the work to get something going and see where it goes. Like I said at the top, I think there’s an opportunity here that we’ve not seen in a long time in WordPress and may never see again.

    And if these are the early days of the new generation of WordPress, I’m certainly going to try and throw my hat into the ring and craft a new experience, and maybe rebrand WordPress, and help outside folks see WordPress in a new light. Because I think that’s a huge part of this new reboot. Is that WordPress maybe hasn’t been traditionally like, quote unquote cool, to a lot of web folks.

    It’s certainly very popular and very prolific, but we maybe haven’t attracted the best talent and the best coverage in the wider web world. So, I look at it as an opportunity to rebrand that and maybe grab another cohort of the web that we haven’t had yet. And I think part of that is new products, and different products, and better looking products, and better experiences, and taking some of the pain out of WordPress that we’ve traditionally had.

    [00:42:57] Nathan Wrigley: If somebody listening to this is inspired about block themes in general, because that’s been the broad tenor of what we’ve talked about. Do you have any names to drop or resources that you’ve used, that enabled you to learn this kind of stuff? And if you do mention anything, I will endeavor to link it into the show notes.

    I don’t mean like a laundry list of hundreds of things, but a couple of things which you thought, actually, for those that are exploring this, this is a really great resource. This is a really profoundly interesting person and so on.

    [00:43:24] Mike McAlister: Yeah. First I would start, I’m somebody who I need to work from examples. I need to see the code and I need to see the, a working thing to get inspired and know how to do things. So, on that note you mentioned that Ollie is on GitHub. It will remain there. This version of Ollie that I’m putting out is always going to be free. And always going to be on GitHub. So it is a great resource for picking through the code, especially theme json, where I think there’s so, so much you can do in there, but it is hard to understand what you can do when you’re kind of looking at it from the outside.

    So if you’re curious, start there, because I’ve wired this thing together. I think how it should be, or largely how it should be at this moment in time. And so it’ll give you a great headstart and great understanding of how all these things tie together. So start there.

    And in terms of people, I actually, on my Twitter list or on my Twitter page, I have a list of WordPressers. And on that list is a great many folks who are a lot of voices in this stuff. WordPress Core folks like Nick Diego and Rich Tabor, and Carolina Nymark. These people spent a great deal of their time in WordPress, and listening to WordPress conversations, and taking part in the GitHub conversations. So I would check out that list. I can actually send it over to Nathan as well if he wants to include it?

    [00:44:43] Nathan Wrigley: Yeah, that’d be great. I will in some way copy and paste it into the show notes or somehow link to it. But yeah, that’s really helpful. Thank you so much.

    [00:44:50] Mike McAlister: Twitter is, love it or hate it. It is where traditionally the WordPress community has hung out, and so it still is the case, even though some people are coming and going. It still is where a lot of conversation happens on WordPress and WordPress development and what’s new. And so it is a good place even if you just want to read and follow along. It is a good place to see those conversations.

    [00:45:13] Nathan Wrigley: I will link to whatever it is that you send me, Mike. Thank you for that. Okay, just one final question. It’s more about people finding you really. If somebody’s listened to this and their interest has been peaked. What are the the best ways, it sounds like it might be Twitter, but it may not be. What are the best ways to get in touch with you, Mike?

    [00:45:32] Mike McAlister: Yeah, I’m most active on Twitter. Like I said, I think that’s kind of where our community is still thriving. And so, yeah, I’m on Twitter largely. My personal account is @mikemcalister. I do a great deal of tweeting about WordPress and design and the intersection of all these different things.

    And then, there’s a dedicated Twitter account for Ollie as well. You can follow that, that’s @buildwithollie. I’m also writing on the Ollie WP blog fairly regularly. So this is another place where I’m able to share my learnings of all of this stuff with block themes and WordPress in general. And, I’m writing some long form content, some short tips and tricks and, that’s all the time I have to hang out.

    [00:46:17] Nathan Wrigley: You have other important things to by the sounds of it. Mike, really appreciate you chatting to us today. Thank you so much, and every success with Ollie, whatever direction you take with that.

    [00:46:28] Mike McAlister: Thank you so much. I love chatting about this stuff and this was a great form for that, so thank you.

    On the podcast today we have Mike McAlister, and he’s here today to talk about his experiences creating a block-based theme.

    Mike is a veteran product developer and designer in the WordPress space. He’s founded and sold multiple WordPress products like Array Themes and Atomic Blocks. Now he’s focused on the future of WordPress with his new product brand, Ollie.

    Mike kicks off the podcast by telling us about his WordPress journey, and how WordPress blocks have renewed his passion for the platform.

    We get into some history, and talk about the era when WordPress themes were extremely popular. Marketplaces like Envato made it possible to sell themes and create a career in ways hitherto unimagined.

    Mike explains what the key differences are between a block-based theme and a classic theme. How it’s possible to create themes inside the editor, and how you can do this without needing to know much code. We talk about the fact that, if you’re a coding expert, you could always create complex themes, but this fresh approach opens up the possibilities for those with less technical backgrounds. The experience in the editor might not be exactly what everyone wants, but it’s evolving quickly and maturing with every new release of WordPress.

    The conversation moves onto why Mike is so confident that block-based themes are going to succeed. You don’t need to use one, and your trusty classic theme and the associated Customizer will work for the foreseeable future.

    We then turn our attention to the technical hurdles that Mike has had to overcome. What new workflows and tools did he need to adopt and master to make his work possible? Mike’s been really focussed on using WordPress Core Blocks to create his themes, digging into the weeds of what they can do and what their limitations are. It’s been a path of steady learning, punctuated with minor setbacks when the editor and blocks are updated in unexpected ways. Thankfully, these bumps in the road are now relics of the past, as breaking changes have given way to stability.

    We then talk about a specific theme that Mike has just released. It’s called Ollie, and it’s the focus of the rest of the podcast. How did Mike build Ollie, and what is he hoping to achieve with this new brand?

    Patterns feature heavily in Ollie and we talk about how it’s possible to alter the look and feel of your site quickly. Typography and colours are easy to change with the new suite of design tools which ship with WordPress.

    If you’re wanting to develop block-based themes, or are just curious about how other developers are building them, this podcast is for you.

    Useful links.

    Array Themes on Themeforest

    Atomic Blocks

    OllieWP website

    Ollie GitHub repo

    WordPressers Twitter list mentioned by Mike

    Mike’s Twitter

  • WordPress Turns 20

    WordPress is 20 years old today, an estimable milestone for open source software running on the web. Parties are happening all over the world – in Geneva, Los Angeles, Istanbul, Bangkok, Lahore, Jakarta, Mumbai – in over 150 different locations.

    The software has been downloaded more than 2.8 billion times but the most impressive stat is the project’s staggering 112,000 contributors, past and present, who have improved and energized WordPress with their passion, talent, and hard work.

    None of the global collaboration we enjoy today would exist without the inspiration and leadership of co-founders Matt Mullenweg and Mike Little. They worked in a distributed way from day one, having never met when they started WordPress. This way of working created the foundation for a global contributor base that now supports 43% of the world’s websites.

    WordPress has had a profound impact on the lives of millions of users, giving them a voice on the web and the tools to launch businesses, create jobs, and bring ideas to life. The #WP20 hashtag is replete with stories of how WordPress and its community have given people a place of belonging and launched them into successful endeavors.

    Does WordPress have 20 more years in its future? Two of the biggest challenges ahead are capturing the hearts of the next generation of builders and maintainers, and preserving the open web where WordPress has thrived. The project’s 2022 annual survey showed that the respondent demographic is aging. The percentage of respondents under age 40 has decreased every year, as WordPress enters its third decade.

    Ensuring that WordPress remains resilient and relevant to future generations has required some courageous leadership decisions, like introducing the block editor, and may bring some significant shifts down the road, as we enter a new era of AI-powered innovation.

    Major milestones are are a good time to acknowledge the efforts that made all of this possible. Thank you, dedicated contributors, for lending WordPress a little bit of your fire and a lot of your patience, nurturing, and support. The code under the hood may look very different from the early days in 2003, but WordPress is still that same scrappy, irrepressible force of good on the web that users can count on for years to come.

  • WordPress and Drupal Co-Founders Discuss Open Source, AI, and the Future of the Web

    WordPress is celebrating its 20th anniversary tomorrow and recently its co-founders, Matt Mullenweg and Mike Little, joined Drupal founder Dries Buytaert together on stage at a private event for the first time on May 17. They discussed how their lives were influenced by open source and how they built their projects around the freedoms it guarantees.

    Founders of both projects expounded on the benefits of open source collaboration, and Buytaert characterized their continued improvements as an example of the flywheel effect, accumulating small wins that compound over time. They discussed the early history of WordPress and how something as seemingly insignificant as a comment on a blog can be the first step towards building a better future for the web.

    Mullenweg acknowledged that it may not be possible to reach everyone with open source philosophy so “at the end of the day you have to make the best user experience.” This has been WordPress’ path over the past 20 years, working in tandem with the power of its open source license and the freedoms that has enabled for the community.

    “I consider all proprietary software to be an evolutionary dead end,” Mullenweg said. They discussed how AI is changing the developer experience. Mullenweg is optimistic about AI working with open source and reiterated what he said recently on Post Status’ Slack:

    Open source and AI are the two mega trends of the next twenty years, and the reason they are complimentary is that GPT4 hasn’t read Shopify’s code. It’s read Drupal’s code and WordPress’ code, and all 55,000 plugins and everything else, so it can write it. If you ask it to write a website, it’s going to write it in an open source thing. It’s not going to write it in these propriety things. From an evolutionary point of view, if you go far enough into the future, someday we’ll see even our proprietary competitors – the Wix’s and Squarespace and Shopify’s of the world, actually running on open source software.

    That’s part of our vision with Gutenberg as well as why we made it an even more permissive license than the GPL. We dual-licensed it under the MPL so it could even be embedded in commercial applications, because I really think it’s so important that I want it to be in even commercial applications.

    Check out the video embedded below to hear this historic conversation between some of the pioneers of open source publishing on the web.

  • WordPress 6.2 Core Performance Analysis Finds Improving Template Loading for Classic Themes Could Make a Major Impact

    WordPress’ Performance Team has published a summary of a core performance analysis they completed in order to identify and prioritize areas for improvement. As part of this process, contributors created a methodology with a standard set of tools that can be used to collect and share profiling data for various components of the application.

    The team tested a classic theme (Twenty Twenty-One) and a block theme (Twenty Twenty-Three) configured with the Theme Unit Test data. They tested out of the box functionality, in addition to different scenarios such as a homepage displaying the latest posts, a basic text-only page, a page with a large set of images and default blocks, and a homepage and a basic page with translation.

    These tests uncovered numerous performance issues which the team has documented with related trac tickets and detailed in the summary of the findings. The first priority identified for improvement is template loading for classic themes.

    Although WordPress contributors are blazing forward on the project’s roadmap for the block editor, with most of the headline release features focused on site editing, block theme adoption is not where one might expect it to be more than four years after Gutenberg landed in core.

    “A majority of websites still use the classic theme architecture, so improvements made here could have the largest horizontal impact,” 10-up sponsored WordPress Core Committer Joe McGill said in the summary.

    McGill referenced data collected in April 2023 for the HTTPArchive which uses a query based on a new HTTP Archive custom metric to detect block theme adoption. Based on this information, improving template loading and rendering for classic themes should remain a high priority. Most of the WordPress-powered web is still running on classic themes.

    The summary highlights the improvements for template loading that would make the most impact:

    In the classic theme tested, the most expensive process is related to locating and rendering template parts. This starts with get_template_part(), includes the process of locating the template part files with locate_template(), and rendering the content for each template part. This whole process accounted for approximately 30–60% of the entire server response in the test results, with much of that time spent handling filesystem checks (e.g., file_exists() is responsible for 4–9% of all time measured and can likely be optimized with a cache), rendering widget blocks, etc. Given many of these filesystem checks aren’t likely to produce different outcomes often between requests, there are likely opportunities to find substantial improvements here.

    These improvements are the first of five priorities the Performance Team identified as the result of analysis. The second recommendation is to improve translation loading, as more than 56% of all WordPress websites are using translations.

    The other three priorities include improvements for block-powered sites, with the first two ringing up as the most costly operations in terms of performance:

    • Improve handling of block registration from metadata
    • Improve resolving block templates
    • Improve rendering of block widgets

    “These efforts will likely require additional research and architectural design before engineering begins,” McGill said. “All other items identified could be worked on directly through individual Trac tickets as capacity allows.”

    The Performance Team is considering making the tooling for performance profiling more broadly available so other contributors can extend their work. In the future, they may also consider contacting hosting companies to get them to run analysis on their infrastructure and examine additional use cases, such as PHP versions, Object Caching configuration, and more. Once the methodology used for this analysis is nailed down, future efforts to improve performance may become more frequent and easier to produce.

  • WordPress; 20th Anniversary, a Mini Series. Episode 2 With Meher Bala, Robert Windisch, Simon Kraft and Tammie Lister.

    Transcript

    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 20th anniversary of WordPress.

    Today is a bit of a departure for the podcast. It’s the second of two episodes all about the last 20 years of WordPress.

    You’re going to hear a round table discussion with four WordPressers talking about their thoughts on the last 20 years. It features Meher Bala, Robert Windisch, Simon Kraft Tammie Lister and David Bisset as the discussion moderator.

    They cover a lot of ground, and it’s fascinating to hear their WordPress stories from the past two decades.

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

    And so without further delay, I bring you David Bisset, Meher Bala, Robert Windisch, Simon Kraft and Tammie Lister.

    David Bisset: We have so much to talk about. We have 20 years of WordPress. We gotta condense in the next 60 or so minutes. Um, for those listening or, um, heaven and forbid if we can use AI to clean up my face. We will be putting this on YouTube maybe hopefully soon. Uh, for video perhaps. We’ll have to figure that out.

    I only promise these people audio broadcast, so I have to see if I have to have them sign another contract. My name is David Bisset. Um, I have been talking to people on the 20th anniversary of WordPress, and I’ve been asking ’em a bunch of different questions, and today we have four more interesting people from the WordPress community and me to talk about some particular th and don’t worry, the, the, the, the humor gets self-deprecating, but it goes up from there.
    The next 90 minutes, you know, it’s gonna be fantastic. I have four people here that are fantastic contr, uh, contributors and representatives of the WordPress community. Um, I’m gonna let them introduce themselves and then we’re gonna start getting into some particular areas of WordPress history that I think they’re gonna love to share some memories, and hopefully you can relate.
    The first is Mihir. Hello Mihir. How you doing?

    Meher Bala: Hey everyone. Hi. Uh, my name is me. I’m from Mumbai, India. Uh, I’m a front end developer and a codeable expert. I’ve been using WordPress since last 10 years.

    David Bisset: Oh, good. I thought you were gonna say last week. No. All right. 10 years. Wow. I’m sorry. Go ahead.

    Meher Bala: I don’t know.
    I think it’s more than 10 years because I quit my normal nine to five job, eight, eight years back, so it has to be more than that. Just giving 10 plus years.

    David Bisset: That’s okay. It’s okay to round.

    Meher Bala: I joined the community quite late because I didn’t know there was a community existing, especially my local and then the global.
    So it’s been fun from the time I joined.

    David Bisset: You’re not going anywhere, are you? You sound like this is Oh, I’m fine. I’m still up on Okay. It sounds like you’re about to send off here and I don’t want this to be that type of podcast. All right.

    Meher Bala: No, no, definitely no. All right. I’m here for sure.

    David Bisset: Okay, well good. It’s glad to have you. Thank you very much for, uh, coming. Have we ever met before?

    Meher Bala: No, I have not met you. I’ve seen all your tweets. I love your

    David Bisset: Okay. We can stop there. Alright, we, Robert, Robert, uh, you’re up next?

    Robert Windisch: Yeah. I take over before, uh, David like sings in under the screen.

    David Bisset: Quickly, quickly, Robert.

    Robert Windisch: So yeah. My name is Robert. I am, um, uh, c o of Insight at WordPress agency. I’m in WordPress since 1.52. So for me it’s very e very easy. I’m so old. I can name the release I came in, which was in 2005. Um, and, and people go like, no, you were older. No, no, no, no, no. I’m a late bloomer. Like, I came in like two years already when everybody, when the, the server were already set up, the, the forums was there and I just came in, swooped up and was like, Hey, is can I help with developer stuff? And they got, and the community, German community was like, you can develop here a server admin access. So I just, uh, um, grab a hammer and then like cleaning pipes in the WordPress server community.

    David Bisset: All right. Well, good, good to have you on board, Robert. All right, Tammie. Hello. Tell us a little bit about yourself.

    Tammie Lister: Yeah. So I am Tammie. Uh, I’ve. Uh, I had to check how long, which was quite a thing apparently. Um, according to my profile, 2006. Mm-hmm. Uh, I think I, I came because I was torturing a cms, like everybody back in the day, and someone showed me that there was a better way with WordPress.
    Um, I think I might have been a bit before that because I was kind of doing it. Um, so that was on wordpress.org and themes brought me to WordPress. So, and since then I’ve been, uh, doing various core contributions. Um, and that’s me.

    David Bisset: Yeah. Well, well, if anybody’s been word WordPress, any measure of time, I have seen you in some way, shape, or form.
    Ah, Simon, bring it home. Hi. Bring it home.

    Simon Kraft: Yeah. Hi, I’m Simon. I started using WordPress in 2008, exactly 15 years ago. Um, I started with like, Easy front end development stuff. Worked my way a bit to the back end and at some point graduated from developing stuff myself. And now I am a product owner at Group One. Um, and I spent like the last 10 years organizing meetups and, and wood camps and stuff like that. So I really love that part of our community. Um, and I’m looking forward to at least the next 10 years of that.

    David Bisset: Oh good. You, you’re okay. Well exercise and eat, eat a good diet and we’ll see. Uh, well thank you all and again, I’m David, if you’ve probably already know. Um, I work, uh, I’m employed at Awesome Automotive. I run a project called WP r WP Charitable or Charitables, the products for non-for-profit organizations. It’s been a recently acquired and I’m a project manager there. I’ve been, uh, I’ve experienced with, uh, work camps. I’ve been. With Word Camp Miami started in 2008, and I think I was around and since, um, WordPress 1.5, whenever that was. Um, that came out with, with I think, uh, themes and pages and that sort of thing. So I’ve been with, with WordPress for a while. This is not gonna be about me today. This is because I’ve talked enough in the past episodes, um, of that. So I want, I want to feel, um, we’re gonna go around. We’re gonna, I’m gonna, I’m gonna get your picks in terms of the categories we’ve selected, but this is an open conversation. So as soon as the, the initial person gets their, gets their words out of their mouth, you’re feel free to have a discussion and I’ll, uh, I’ll poke up accordingly. So, Mihir, um, Let’s start with you. Uh, let’s talk about, one of the things that we wanted to, wanted to talk, and this is gonna be a little bit different than if you’re, if you’re listening right now, you’ve listened to the others. These are slightly different topics and categories I wanted to touch on here, cuz these, cuz I wanted to get some, there’s so much to cover for WordPress’s. 20th, 20th anniversary in 20 years. There’s so much to cover. So I wanted to make sure we, we, on some of the shows and some of the people I talked to, we, we kind of varied our discussion points.

    So first thing we wanted to cover was a memorable design or refresh in WordPress history. Now, some people ask me, well, does this mean this? And does this mean that, um, does this mean project or does this mean that I, when I ask these questions, they’re open for interpretation. So I am not looking, I am looking for something within a scope. But wherever you read that question, you can go from there. So what Mihir, what was your. Memorable design or refresh and WordPress history?

    Meher Bala: Uh, my memorable was 1.3. Uh, one was having a multisite built in the co. Mm-hmm. And one was a 20, uh, 10th heme, which was most stylish, more simple and very readable to normal users who, you know, what, just wanna run the WordPress as a blog because blogging had just begun and everyone was using WordPress. So for me it was, 3.0.

    David Bisset: Yeah. Uh, I was a big multi-site fan back in the day, and I remember he had to download two versions of WordPress. Yes. Uh, and that was, and that’s, but that was, um, and see that was the, what was the theme again? What was the year 2010?

    Meher Bala: 2010 was it? Uh, 2010 was a theme. The year was, uh, 2010.

    David Bisset: Right. That makes sense. I was trying to, I was trying to pull up what it looked like, cuz I’m drawing a blank. Remember we were talking about, um,

    Meher Bala: it’s the white banner on top.

    David Bisset: Oh, there it is. Yeah. I remem Oh yes. Oh my goodness. Yes. That was with the trees in the road. Yes. Is the default picture. Yeah. And it’s kind of hard to describe audibly, but if you just do WordPress 10,000 theme in Google images, you get all the clones appearing and there is some, there was a little bit of styling there, but it was mostly what blogs, what the typical stylish, simple blogs were back then. It was like a large hero image or a large full width image. And then you had your two columns, right?

    Meher Bala: Yes. It was something new for a lot of people.

    David Bisset: Well before that, not too much before that. I don’t know if there was another word. I, I forget when WordPress year theme started, was this the first one?

    Tammie Lister: That was the first default theme? That was the first, that was second one. No, that was the first official default theme. Mr.

    Simon Kraft: Well, there was Kubrick before that.

    David Bisset: No, I see. Dang. I lost a bet. Years. Yeah, because yeah, I was, I, I should have said that’s the first default theme that was named after years because we had Kubrick for like four or five years before that. Oh yeah. So this is kind of memorable because this

    Tammie Lister: is the first default, the one that started the default years
    David Bisset: because we got so sick and tired of looking at that, uh, Corick theme. No, I mean, it was nice and pretty, but I mean, it’s like my kids, I can only look at ’em so much before I need something new, new, new to glance at.
    So, but yeah, it was perfect. But, alright, so I think that’s pretty memorable. Nice. Round number 3.0, multi-site, no more Kubrick, first year theme. I agree. That’s a pretty good design moment in WordPress history. Um, let’s, uh, so Robert, what’s your, yeah, what’s your, what’s your big, uh, design moment that you wanna share?

    Robert Windisch: So, so first, Mihir taking multisite from me, like, uh, we have a conversation next, next word camp like, and from me by the way.

    David Bisset: So is that your, was that gonna be your pick?

    Robert Windisch: No. Yeah. Uh, I’m the multi side person. Yes.

    David Bisset: Oh. Oh, see, we already have our first

    Meher Bala: right after three, so.

    Robert Windisch: Yeah, yeah, yeah. That, that’s totally, it’s, it’s, you, you are the first one. Um, and I am, I shying away from other things because I want, I know Tammie wants to, wants to mention that that one thing that end ends with a number, probably this, the design refreshed, but like, I, I give Tammie the, um, the, oh, no. Okay. I can take it. I can take it. Okay.

    David Bisset: See, you try to, you try to be a nice human being. Well, well,

    Robert Windisch: yeah, yeah, yeah. Yeah. Because like, I, I’m the second one, so, um, but I have, like, you are welcome to that one. Yeah. But that’s my, would be my second pick. So, um, so I would, with the, with the biggest like, design, uh, um, like seismic shift from like, uh, from, from the, from the feeling was when the, when the menu went from the top to the left. Like that. That was like that. I have no idea when this was. Like, I’m very bad. Right? Like it was eight ago.

    David Bisset: Menu went from the top. You mean the admin making

    Robert Windisch: the WordPress menu was in the top third

    David Bisset: one? Yes, it was. Cuz I remember in one five it was, but I, I can’t, I can’t remember now. You’re gonna have to make me look things up.

    Robert Windisch: I, I would guess, but I’ve, I’ve, I’m bad with like, because it’s, so we’re currently talking about like between like which dinosaur were alive when this happens. So that’s why it’s, it’s so, it’s so far off. And I will simply say like, uh, the biggest, like design wise for the future, for the user interface was really when the, when the top menu, which was not like, it could not scale because you had, uh, determined like link in the menu. We experienced that in the WordPress org menu also that we have a problem with, with link there. So, so that was for me, like a, a, a big, um, like design visible decision that, um, was, was made and then, Like, it’s now the current, the current way of the WordPress backend.

    David Bisset: Okay. For now, I’ll, we’ll, I’ll, I’ll guess that it was around 2.0 cuz I remember it being in one five and it was pretty, and I started using one five, but very quickly after I started using it. Like, I don’t remember the top stuff match for very long, so I mean, I’ll be, I’ll be Googling to fill that in, but, okay. Well, we’re gonna, we’re, we’re gonna put 2.0 as a placeholder, but That’s right. It’s, and just fortunately, I mean, we think the sidebar is a bit of a mess today. Although the stuff that we had, just imagine if it was a top-down navigation menu in the admin.

    Robert Windisch: Yeah. All the, all the, uh, like upsell things now in the top menu bar, that would be like, lovely. What would it be?

    David Bisset: Why, how would that work? You, we all the plugin authors have to add like a second navigation, second dropdown. It’s like a mega menu.

    Simon Kraft: We just, we’ll just like break and add another line, and you have a huge block on top of every Diamond page.

    David Bisset: Tammie’s miming all of the facial expressions as we’re talking here. That’s fine. All right, okay, well, Tammie, now it’s your turn. Robert, I’m gonna get back to you on a version number on that exactly, because

    Meher Bala: I think version number’s, uh, 2014.

    David Bisset: Okay. That’s a year. That’s close. That we’re, we’re, we’re getting closer now. So 2014 is the next clue. 2014, the menu came inside. So that’s four years after the 2010 theme. I know I can do math, but I mean, that would mean it would be greater than WordPress.

    Robert Windisch: No, no, no, no. The the menu, the, the, the, the, it was was already decide when the, when the other thing that I want to mention later, uh, um, come, come.

    David Bisset: No, don’t ruin it. Don’t worry, don’t worry. We’ll figure it out. All I know is that I was. Yeah, all I know is that, um, there’s probably dirt younger than the version number that we’re gonna find, but anyway. All right, Tammie, time, time to go from miming to audio and sharing your, uh, the biggest or most memorable design moment. And this should be right up your alley

    Tammie Lister: 2005 and it’s Kubrick. And the reason is, if you speak to most people that got their visuals or, or some front end work in WebPress, uh, have been around for a while, they got their start because of Kubrick. That was one of the themes that got them into it. Or they started tinkering around with themes. Um, it was one of those themes that you like cut your teeth on, you learnt with, so that, I know we were kinda saying it was around for a while, but honestly it’s what. Most of us learn how to theme from. So for me, I think it’s the most memorable design. Um, mainly for cuz of the gradient. If you think of Kubrick, you see the gradient. So that’s the one for me. It’s gotta be Kubrick.

    David Bisset: Well, for me personally, I may have mentioned this on another episode, um, but Kubrick wasn’t just another design or even a design that stayed for a long time. It was when WordPress was really starting to get popular for blogs. Yeah. And I think visually speaking, at least for me, that whenever you ha if you wanna get a couple of screenshots or photos or memories Yeah. Of just how, when blogging got popular, Um, yeah.

    Tammie Lister: Would, and I set the tone. Yeah. So many people just were never color gradient or had that big header and that header format stayed for a very long time. The big headers. We’ve only just very recently stopped having big headers in our designs and kind of started moving away from the big header design and realizing you don’t have to have that in every design, so,

    David Bisset: well, you know, what they say about big headers.
    What’s that?

    Tammie Lister: Um, for, for me, I feel that you, you can’t really include this list without saying that because it feels quite seminal to Yeah. What you learn and at the front end, the code level, because we really learn how to create themes from it as well. Oh yeah.

    David Bisset: Iconic. Iconic, very good choice. So, yeah, we’ve had, um, WordPress 3.0, our mystery WordPress 2.0 theme that we’re gonna go to do, and, uh, Kubrick 2005. So, uh, Simon, what I, can you share with us what your memorable, uh, design. Moment is in our WordPress history. So far we’ve, we’ve, and I’m, so far, I’m glad we have stayed in the past, but are you gonna, are you gonna be there with us, Simon, or are you edging a little closer to the future? Like pick something from the future? Um, no, I mean, I meant far past.

    Simon Kraft: Yeah. Okay. I, I think mine is not that, that long ago. Well, it should be like 10 years. Um, Robert already, um, alluded to it. Um, I pick MP six, the, the redesign of the word presentment interface. Um,

    David Bisset: see, you hear that Si Simon. That means I can Google it and get a year versus Roberts description

    Simon Kraft: it should be what? Press 3.8.

    David Bisset: Well, I’m not gonna fact check-

    Robert Windisch: just keep in mind the new redesign of the interface.
    Simon Kraft: Yeah, yeah. It, it’s just 10 years old. That’s, that’s still good. Um, and that was was a point where I really started. Loving the way the WordPress back end looks, because before that it was, it was cool, it was nice, it was usable.
    Uh, but with that, it felt like really fresh and still to a certain degree does, uh, today. And I think there were a couple of smaller, um, redesigns, I think WordPress 5.7 at the standardization of, of colors or something it was called, where we had a bit more contrast, a bit more unified set of colors, which is also very nice. I came to really love that. But that’s the interface on the web that I interact with, like every single day of every year, ever since. Uh, so that’s, that’s quite cool.

    David Bisset: I, it looks like, to me, the, I mean, I think this plugin was around a while before it actually officially came out in the WordPress police, because I’m finding posts from 2013. Um, and do you remember why it was called MP six? I mean, must stand for something

    Robert Windisch: Tammie doesn’t know. Nobody knows here.

    David Bisset: Yeah. I’m looking at,

    Tammie Lister: I think it was a project name.

    David Bisset: It had to be Matt, think it was, it had to be probably Matt or who, or I forget the original designer or the original project creator cuz I’m, cuz this was nine years ago.

    Tammie Lister: It was a group, group of people who created it and got together.
    It was one of the first projects where a group of people got together and created it and kind of worked on it. Um, it was kind of the first attempt at that, um, to get kind of designed, done collectively, I guess.

    David Bisset: Yeah. Was that the first, what do you call them? Um, project plug-ins. No, that’s not the right word. Um, feature. I’m not even sure. Feature plug-ins turns back then. Yeah. Cuz this, would this been considered plugins or anything? Yeah. Yeah. I mean, the term didn’t exist, but it was, I think it was probably one of the first quote unquote feature plugins. Right. Yeah, I mean without that we’d still be looking at the uh, um, now if I can find a screenshot between Robert’s Pick and Simon’s Pick for the WordPress admin where the, it was side navigation, but it’s still an before MP six. Man, I can’t remember it.

    Robert Windisch: People, people will not, people will not like if you show them MP six, it looks very like the current, um, interface. So that’s why, um, oh yeah, we don’t change anything. Just need to like the pre, the pre MP six phase, because that was the new redesign, as I always, I cannot, I cannot emphasize nothing. That was how new this was for, this was for the WordPress people, and we are like, finally someone is investing in the WordPress Pega interface. So that was really like a, a, a jump in in, in, um, in user, in, in, um, user interface, um, and, and usability of WordPress.

    David Bisset: It had a bunch of new dash icons, remember, da remember Dash icons. Um mm-hmm. For those of us who know what those are a redesigned widgets page by Sean Andrews from his Widgets project. If, uh, P six included that. Wow. I didn’t, I totally forgot about the widgets project. Improvements to the customizer color schemes. Is this, is this when we got our color schemes like Ectoplasm or some, I wonder if that’s Yep.

    Tammie’s shaking her head vigorously guess. And a new midnight color scheme. So that’s, thank you, Debbie. Thank you Sarah from 2013 for helping us remind that. Well, that sounds fantastic. So we have stayed. We have stayed pretty, pretty well pre 2015 pre Gutenberg. That’s a i I applaud you all for the biggest, most memorable design moments, not being part of, uh, anywhere beyond the 5.0 release of WordPress.

    Thank you. So just to, just to rehash here, Mihir, uh, WordPress, uh, 3.0 multi-site and the first year themed theme. Um, yes, Robert, uh, we’re still gonna hunt for a version specific for that, I assure you. But when the, but we’re talking about when the big jump made from moving navigation from the top to the left hand side.

    Uh, we’re gonna guess that’s 2.0 WordPress for now. Kubrick, who could forget Kubrick? We didn’t. Tammie thought that was, and that probably one of the most fundamental images and thumbnails representing the blog when blog blogs went. We’re in its heyday when movable type was, was starting to fade and WordPress jumped on the scene, how iconic.

    And then MP six, Simon picked that. And that of course is just, you know, we still have that with us today. And that’s been, it’s been, been probably, it’ll probably around 10 years. So, Fantastic. Well, uh, from design-wise, I really don’t have much to, to say in this department. Um, I, I think we’re, I think the early version of WordPress that introduced pages was great, but that’s not really much of a design feature.

    That’s just, I think it did open it up for a little bit more design. Um, I, if I had to pick something, I, I don’t know if this would be my most memorable, but I use it every day. It is the redesign of the WordPress site, um, wordpress.org. Um, a lot of people don’t remember how that looked way, way, way, way back then.

    Um, with, and then it was all split out into various groups, uh, various categories as we have them today, you know, core and design and plugins and, and all of that. Um, I don’t know, maybe I’m, maybe this is an old person talking, but it was really, really clunky and really plain back in the early days. And now with the learn.wordpress.org and the redesign stuff’s, it’s happening.

    It’s looking so much more professional and grown up maybe is the, is the best word I can describe it in. But anyway, that’s, that’s just me. And maybe for, I will share some, if I can find some old screenshots of that, which I couldn’t initially, um, I would love to, love to share them with you. So let’s move on to our next category.

    Mihir, you are up again. So we are talking about the most notable enhancement to WordPress core that isn’t Gutenberg related. So I definitely, so I definitely put that. That, that qualifier in there, because I think that would be way too easy. Um, we in way too broad. Um, and when I say most notable enhancement to WordPress core, that means this is, um, it, it had to appear in WordPress core at some point.

    Maybe it’s something that’s not there anymore or maybe something that it was acquired or merged into WordPress core. Didn’t have to start there, but it was something, a most notable enhancement to WordPress core. And I had some people say, well, what do you mean by enhancement? Do you mean coding wise or design wise?

    Again, this is up to your interpretation. As long as you don’t say the G word, we will be Okay. Mihir. So go ahead. What is your most notable enhancement to WordPress Core? We had no guten, guten free.

    Meher Bala: Mine is the events, uh, widget on a dashboard.

    David Bisset: I’m sorry, say that again. My, my ears exploded. What was that?

    Meher Bala: The event widget.

    David Bisset: Oh, the event widget, yes. Ooh. This is why I like talking to people that are above the age of 18, cuz that’s all I have in my house for, for like a week, every week. The events widget. Oh, tell us, tell us a little bit about that in case people have have forgotten about that.

    Meher Bala: So, uh, whenever there’s any, uh, meetup happening or WordPress happening, uh, in your locality, the events are displayed there.

    And in our local, what I noticed is once the widget came out, a lot of new people who didn’t know the community started, you know, attending meetups, started interacting with the community. So we had a few different people at every meetup. So that’s something which is memor, which is.

    David Bisset: That for me is an amazing pick. I never would’ve thought of that. And apparently you did.

    Meher Bala: I see the community grow even with that. So for me, that’s still in the mind more than Gooden book.

    David Bisset: That’s amazing because not only does it serve, did it serve a purp? I I, I can’t remember if this is when people realize meetup.com was crap. I can’t remember exactly when. Uh, sorry. Meet, sorry, or sorry to our sponsor meetup.com by the way. Um, I love you. Uh, so mom, uh, who works there? So, meetup.com was probably the only way WordPress people were fighting each other at the time. I do you have a, do you know when that, I guess we’re gonna have to find out when that came about cuz I have no idea.

    Simon Kraft: That was WordPress 4.8.

    David Bisset: And do you have a year for that? No. Oh, well, now that we know a version number, hello. Welcome to a podcast, but we’re doing our research live on the air. Thank you. 2017. 2017 or something like that.
    Robert Windisch: Welcome. Welcome to a normal community conversation, by the way, we don’t, we don’t run around and no version numbers and years.
    We just go like, do you remember this feature? Oh my God. That’s it.
    David Bisset: You get what you pay for the hallway track. People are getting what they

    Tammie Lister: for when someone get, gets their phone out and starts tapping and then finds it, and then you go, oh yes,

    David Bisset: someone’s rolling their eyes right now and starting a letter.
    Dear David, oh, well

    Tammie Lister: I can’t believe they didn’t know that.

    David Bisset: David Professional in quotes, uh, we have that before that 2017. The reason why I was wanting a year is because that is before I think Slack and where Press Slack, I believe.

    Robert Windisch: No, no, no. Slack was, slack was uh, in civil already. Slack was there.

    David Bisset: So, yeah. Okay, so. I don’t wanna pinpoint it, I guess. Yeah. Cuz 20, I remember a community summit when they made the announcement, but 20, that could have been as early as 2015. So if that widget came out in 2017, there was still ways. I guess the two top ways you would know about WordPress community would be meetup.com was still probably the biggest way there.
    And then maybe if you were on WordPress Slack at the time. Right.

    Robert Windisch: Yeah, but meetup media.com was the, we, we, so we decided on media.com because I remember the conversation we had internally be, Hey, let’s build this. And like, people who know project management was, was like, um, you know, that we want to do democratizing publishing, not democratizing events here.

    So, so that’s why luckily we decided to simply give meetup.com money and let they run all of this. And we simply like hooked the meet, hooked the Meetup API into their system and was simply like, um, doing, let them do all the work.
    David Bisset: Oh, I was talking, when I talk about meetup.com, I talk about the interface on meetup.com because my experience with it was, I was running meetups through meetup.com and creating the meetups, um, even searching for meetups, and I’m, I’m sure it got better over time.

    I think Amaz, coincidentally enough, is when Weber, when there was that single. Page for the WordPress meetups. Like you said, they, I think there was some, some deal with the, uh, with, um, with, I don’t know. I would, I’m gonna guess WordPress Foundation on this was, was involved or something, but before a while you would just have random spots of communities on meetup.org.

    Which org, which was hard to find. That’s the experience I remember cuz I was running one of those meetups, or two of them actually for a while. And then there came a time where everything was under one umbrella. Organizational wise, I think it had a dedicated page and probably, I’m guessing at that time is where the widget would probably start pulling that kind of information.

    Right. Cuz it’s all centralized Meetup. It’s probably, it’s probably, um, like a meetup organization or something like that. So apologies for me getting it a little confused. I think it did get better, but I, I remember once we had that widget, I pointed people toward the widget and we would have meetups where I said, how many people found us through the widget and we always had one or

    two people at our meetups raise their hand. So I think that’s an amazing pick. Does any, did, doesn’t, does any, I I’m seeing a few people nod. So is that your experience as well, Simon?

    Simon Kraft: Yeah. I think our meetup in, in Germany, multiple meetups in Germany, like grew tenfold or something in the year following the, the, this update with 4.8. So that’s really huge for the meetup community.

    David Bisset: Yeah. So not only do we get a nice new widget on the dashboard, which doesn’t come by that often, but it had an impact on the community. So I think that’s a really cool pick. Really appreciate you take us down me memory lane and my apologies to meetup.com. Um, Robert. I believe you’re up next. Um, so again, just in case, uh, people have nodded off here listening to us

    Robert Windisch: totally like, yeah, totally fine. I can bring up something that is nothing with five. Oh, that is a feature that influenced many people and that, uh, everybody goes like, yeah,

    David Bisset: just I said Guttenberg related. Now if there’s anything else in five that wasn’t,

    Robert Windisch: no. Not even close. No, no. I’m, I’m still, I’m still in a very old feature. I’m still in three, 3.0. I’m talking about, menus.

    David Bisset: Menus. Oh, you mean like creating menus?

    Robert Windisch: Before that you needed to have pages and pages needed to have redirect because you needed to get some structure. And then the only thing to have a high, high cultural, uh, a structure where you have like a parents and chil uh, children was with pages. And that was like when people like fumbled their menu structure together with external links. And then you had a drag and drop in the WordPress back and with menus.

    David Bisset: You. Wow. That act. Wow. I can’t remember that o That was wor that was 3.0. Yeah.

    Robert Windisch: Wow. That was merged from Wu. Seems the WCI feature of menus were merged in the WordPress core

    David Bisset: wow. That’s so hard to believe. Looking back on that now, 3.0, not so, not only P 3.0 had multi-site and, and, and the new theme it had, it had the menu stuff too. That’s amazing that, that would’ve been so barbaric. It’s probably the reason why my webs

    Robert Windisch: no difference with me. No promise with me with features and breakfast.

    David Bisset: Uh, that’s so barbaric. It’s like, for a long time it’s like, why do all these WordPress sites don’t have barely have any menus on ’em until this date? Co. I remember Cooper, I don’t, I might explain why my early Cooper Gays, I don’t see many, I don’t see many menus. They were on the, they were on the sidebar. A lot of the links for websites. Yeah, I re I don’t know,

    Tammie Lister: it was all a widget or, or kind of lists

    Robert Windisch: and No, that the link, the link, the link feature where you could have like defined what’s,

    Tammie Lister: that’s what it was. Cause that’s all we had. You didn’t have anything else. And then when you had early menus, you had to do those walker things. The, you only knew a few knew special magic words and more wizard. That was because it was really, really difficult.

    David Bisset: Oh wow. Okay. Well, yeah, definitely notable enhancement menus. Where could we be without menus? It’s like a, it’s like a car without, I dunno, a steering wheel or something. All right, Tammie. Uh, notable enhancement to WordPress core and no good. Yeah.

    Tammie Lister: I think I’m back at 3.0, but I want that checked custom post types is where I’m going. Uh, I feel like we’re just settling on that release, but it’s one of those releases where we just kind of, it feels like it grew up or we got the features, which then meant the, not just people could write logs or, or use, you could then pivot and grow and extend.

    That’s really what that release felt about. And custom post types, if you think about everyone that’s made a product or everyone that’s used in an agency or anyone’s done anything with WordPress, they wouldn’t have probably done that if it hadn’t been for a custom post type. So it kind of was there, or, or at least that concept.

    So, and even Emberg has the, the G word, I’m sorry, but that has the roots in that kind of thinking. So yeah, custom post types is the thing for me. That’s, it’s,
    David Bisset: that’s, it’s, it’s. It’s really what started to make WordPress more than a blog. Like everybody’s, yeah. But then

    Tammie Lister: you could, like ex you could make it yours and you could take it your your direction and you could build on top of it. You know, we now think about like headless and doing everything you want and all that. That would not been impossible if we hadn’t started thinking about custom post types, which now sounds really like simple. Right? Um, but it’s not that back then that was radical thinking. Yes.

    David Bisset: So yeah, you could start making. And history would rather us not learn this lesson too deeply. But I mean, you, you could make a like WordPress into any sort of application you wanted to. Yeah. Yeah. Not that you should, but I mean, you could. Right. And there was, and there was already custom post types.

    Tammie Lister: It wasn’t just these pages with, with Kubrick, but it was just this flat file. You, you, I mean, as we’ve just heard, you had navigation and, and then you had these different things. You had so much in 3.0. 3.0 was basically like Christmas.

    David Bisset: Yeah. I mean, how much brain matter had this. How much brain matter was scraped off the floor at the Word camp announcement for 3.0. You know, it’s like our minds were blown so much. Just stop it. Yeah, stop it. It’s all, it’s already dead. Uh,

    Tammie Lister: yeah, but if you think back then about the upgrade paths of 3.0 as well, cuz back then it was very different as well. Let’s say we don’t have releases that are that significant now because so many things happen then it’s kind of mind blowing.

    David Bisset: Yes. It’s like you, you went out, you went to, you went to, you went to the customer saying, let’s upgrade you where this is the customer. No. Really? No. Yeah. Let’s, let’s do it. Let’s do it. Let’s, let’s go nuts. Just cup take. All right, Batman. So, all right Simon. So we’ve got an events widget, we’ve got menus, we’ve got custom post types.

    Uh, I don’t wanna put any pressure on you here, but, um, do you have something he’s gonna say entering text into a box? For the win, Alex,
    Simon Kraft: and that, that was exactly what I was going for. Now, actually, in the first round, all my picks and the backups and their backups were picked by everyone else.

    David Bisset: But this time I, I said to come, I said To come with a sat.

    Simon Kraft: Yeah, yeah. And, but this time, every single one of my, of my picks is still in the race. And that makes it a bit hard. And I’m going for the, I think most insignificant one of them, because it’s no longer in core. And that’s something we don’t do that often. Oh, no.

    David Bisset: Um, oh, no, I think I know what it is. It’s post formats. Yes.

    Simon Kraft: Um, I, I really loved that feature back in the day. Uh, as I said, I was

    David Bisset: te Tell us a little bit about post formats, Simon.

    Simon Kraft: Yeah. I, I, I was, I was building a lot of themes back then and post formats basically had the idea that you cannot only post a post. So not just a blob of text, but also. Oh, I have lists somewhere here so I don’t have to bumble around like an idiot.

    Um, something that was called a site, like a, a small kind of update kind of post. You had a galleries, links, uh, images, quotes, a status while reading that. I’m not so sure how that compares to a site. Um, video, audio and chat. And they’re gone now. They were introduced in 3.1. Um, but they were like, that was a really fun way of, of styling different kinds of content in blocks.

    David Bisset: I remember Matt talking about it on stage, by the way, and I mean, I’m that old.

    Robert Windisch: I’m so happy that they are gone. I’m so happy that they, I’m not, I’m not at all.

    David Bisset: Robert. Robert, Robert. They’re some confusing for people. Robert, we, we’ll get to, we’ll get to your negative emotions, but let’s, I’ll, I’m sorry Simon, I interrupted. Go ahead. You were telling us about this wonderful feature.

    Simon Kraft: It was so wonderful and at some point, I’m not sure when. It was removed from Core. I think there’s still a way around that. You can still technically use it in some capacity, but it’s not an ongoing core.

    Tammie Lister: I mean, still you can also use a block now you could use a block and, and have it as a, that’s not the same. Yeah. I mean, no, you could sign it.

    David Bisset: Well, it was introduced in 3.1, it says here. So it almost made like we were writing an, we were writing high back then as a WordPress. People we’re like, oh man, 3.0 is so awesome. What’s next? What’s next? Oh, this post format stuff. Oh man, we gotta do this. And then, and then crickets. Why, why do you all think that post formats didn’t make it?

    Simon Kraft: I think, uh, blogging is not that relevant anymore. Yeah.
    Tammie Lister: Unfortunately. So I think that’s, that’s one of the things is like, It’s very in the blogging sphere, I think it works just for blogging or not for a particular type of blogging even. Mm-hmm. Um, and there was a, you know, if you think about, what was it?

    Timelines, it was a big thing back then. I went kind of wanna bring them back, you know? Mm-hmm. Um, and like listening to, and I’m doing and status updates. It was kind of in a time before we used social media as well, so people were using their blog to post and syndicate everything on there. And people just started doing that in other places rather than their blog.

    Not saying they’re not gonna come back with, uh, the world as it is and owning your own content. But I think that because it was very particular, and then WordPress was starting to become about more broad in its terms. I think that’s the thing when we moved to plugins being about particular things rather than the interface.

    Robert Windisch: Yeah, I just want to pick on my like, negative thing that I said I, I just wanted, like in terms of the user, for the user, it was very complicated to like decide while writing. And, uh, if we are emphasizing on like for the majority of users and have it very lean, mean, uh, interface, then it’s like going like, okay, what of these seven things, is that what you currently want to do?

    And or nine or whatever it was. And it was not extendable, so it was Oh my God. So that’s why it was very, for the user, not that, that’s why I’m saying like, uh, um, it was not easy to understand and they just want to publish and then we are going like, please do this checkbox and otherwise you cannot like, start the car.
    So that’s why I was like, um, really against, uh, the, the post format because they were against the, the, the, the directory of WordPress having like becoming easier to use for people. Yeah. And, and as much as I love the feature, I think that’s a valid reason to, to remove it.

    Meher Bala: Because even a lot of my clients. They want, they choose a, uh, post type, and they expected some result, something else came up. So a lot of people were confused. Users.

    David Bisset: I could see that. S all right, so I have here events, widget menus, custom post types, and r i p to post post formats, although I think it’s in the code somewhere, it’s, and, um, you, you can up to this point, right?

    They wouldn’t just outright kill it. They hit it and it’s still in there somewhere. And it’s just one of those few things in WordPress that had a lot of, uh, fanfare. And again, it just, for one reason or another, it just kind of fizzled a little bit. And the, and so anyway, um, so I’m, I’m gonna throw in mine.

    So, believe it or not, there is something that was once popular. And I don’t know if post formats, you could say it was popular, but I, I like to think it was at least it had a little bit of, uh, runway. There was something early on in WordPress that was popular, that was used quite a bit. And then inversion 3.5, I think at 3.5.
    Feel free to correct me, uh, future Self that, um, it, it disappeared. Um, I’m talking about something in the admin. I’m talking about Something was, started very on in WordPress and in fact, it was part of blogging culture for a long time that if you had a blog on your website in the sidebar, I’m looking to see if peopleare starting to think about this.

    You had a list of other people’s blogs that you could l that you would link to, and that was called drum roll. Please think I broke my table. Um, blog roll. That was called a blog roll, but in the WordPress backend, does anybody remember what menu that was? No. Okay. Links. I’m All right. Thanks for reading it.

    Links. Sorry, there was a links menu. No, no, that’s right. I made, so it was the links. So I don’t know if this was in WordPress from day one. I like to think like pretty soon in WordPress it was, I couldn’t find when it was actually officially added, but I’m pretty sure I could have, I put my mind to it. But link management phase out of WordPress, from what I can see around WordPress, 3.5, um, supposedly wordpress.com added them back or something along those lines.
    I’m not sure if they’re still there. Um, so when WordPress 3.5 links was gone, and, you know, by the time it was gone, nobody was using it. Very few people were using it. Um, it, because I remember when it was gone, it was like one of those things that like, it was, it was getting old and crusty anyway. And it had, it would needed to be taken out to the refuge, trash bin, dumpster, whatever you kids are calling it these days.

    But I remember using that as one of the first things when I started with WordPress 1.5. Cuz blog rolls were a thing, you would like link the top. Like you people were reading your blog, they wanted something similar to, and you needed something on the sidebar. And believe it or not, um, when people stopped using that, they kind of went over to menus.

    Um, like a menu widget or something, I think was, some people wanted to continue that. But yeah, the links management system blog rolls in the early days of blogging. Those were things, you know. Um, so anyway, um, r i p to R one links management. So that was for me. All right. Lastly,

    Robert Windisch: can I jump, can I jump in?

    David Bisset: Can you link to something? Sure.

    Robert Windisch: Yeah. Yeah. I, um, I cannot like, because it was also hard for me to pick something and, um, uh, Simon, do you do the other thing? Um, yeah. Okay. So, um, uh, one of the, one of the things that, um, was very, was very, very important, but it’s not like really visible to see this to people, um, is for me the, uh, the rest api.

    Um, because, um, if we talk about like what we are currently like doing with all the, the word we cannot mention here because it’s a, it is a, it’s a history show.

    David Bisset: The he who cannot be named yes.

    Robert Windisch: But without the rests api, many things currently would not be possible because that’s the foundation and like the, um, the sheer energy to put this into WordPress against all arts against, like, why do we need this?
    It’s not a visible feature. And when everybody was like, but we need a rest api, XML L P C is not gonna make it. We need to have the future to really communicate with the WordPress backend, and this needs to be in WordPress. We really, really need this. And then we got it like, um, some base features in there, and now we have it like as the foundation of, we cannot name it here.
    Uh, we have this, uh, foundation that if you would disable that you would like have a really a timeish and jump back in a time with the features that we are currently having.

    David Bisset: Yeah. Yeah. The rest

    Simon Kraft: and probably the next, next iteration of the WordPress interface, like WP admin. Is, I guess, very likely to also be based on the rest api.
    David Bisset: So here are some runner-ups. Just thought I’d throw ’em out there real quick. Auto updates, I’m,

    Simon Kraft: that was the one that Robert meant, uh, I, I should mention. Yeah, uh, we discussed that earlier. Um, all updates were introduced in 3.7 and changed, I guess, WordPress forever. Because since then, every WordPress website is updated, at least patched, uh, to its new version, which is really cool.
    And until recently we, we also kept like all the, I dunno, what was the last version of, of 3.7 still supported like

    Robert Windisch: 30, something like that. 30 or 30 something. Yeah.
    Simon Kraft: So it was really crazy that all these old versions are still still maintained to a degree.

    David Bisset: Mihir, did you? I, I had, I’m sorry. No, I’m sorry. I wanted to get Mihir. Mihir was shaking her head like a bo, like a bobblehead doll. Um, there, did you grasp auto updates because, uh, Mihir as well as everyone else, I think, because I know there was a lot of controverts in the beginning about WordPress back then. Smaller market share than it does now. Were you comfortable with auto updates, Mihir, in your, in, in your, um, decade?

    Uh, well, I’m sorry you weren’t a decade before, but how were you comfortable? Were you comfortable with WordPress updates? Initially,

    Meher Bala: no, because a lot of, uh, sites broke. That was because of the theme and the plugins. But as yours past auto updating WordPress is good because at least people have reduced saying that WordPress is not secure.
    Yeah. When it is auto updated people, okay. Find that fine. And WordPress is secure, what we add to it with a theme or plugin. There is some vulnerability over there.

    David Bisset: So you, you, so you, you got warm to it. What were you saying, Tammie? Yes.

    Tammie Lister: Uh, I was gonna take in a different direction, so I’m checking wherever we are done on order updates.

    David Bisset: Oh yeah. Well, uh, yeah. The other two I only wanted to mention in, in, in passing was the customizer. Um, that’s kind of, we’re getting, we’re kind of seeing that maybe in the rear view mirror a little bit. For a while though, that was the true no-code interface to customizing a theme, um, of, in core anyway. And la lastly was the, um, uh, let’s see.

    I pasted a u URL in this URL does not make sense. There is also smaller things too that maybe doesn’t play to, I wouldn’t say. A huge part, but we had things like site health, um, import exporting, WordPress, um, in from core with the plugins, that sort of thing. So lots of little things. Uh, and
    Tammie Lister: I had one from 2012, which was, uh, something that’s gonna get redesigned or reworked mm-hmm.

    Uh, in this cycle or this phase, which is the new media management happened in 2012, which sounds a long time ago for it.

    David Bisset: Yeah. I, I can’t remember what it was like before then. I think you had to draw something and mail it to your WordPress blog,

    Tammie Lister: be glad that you don’t remember it. It was, it, it was a big thing. And I think that, and even you could have picked like the old way we used to do revisions, which even now you look at revisions and you think, oh, that’s quite dated. The old way was even more dated back in the day. Um, and why I kind of thought of those ones was because they looked dated to us now, but. We are redoing them now.

    And I kind of think that that’s kind of interesting to think of. Like the cycle of like every 10 or so years is kind of when we kind of redo things, which kind of is kind Oh, that’s healthy.

    David Bisset: It’s a project. Hey, well we’re an open source. If we can get to the 10 year mark, that’s a win, right? Uh, pretty healthy actually.
    To, just to wrap, just to wrap this section up. Um, completely forgot about revisions. Um, not that I used them too often, but, um, that and the little thing when the slider came in. Yes.

    Tammie Lister: From when we first got the sliding,

    David Bisset: I’m not sure if I took to the slider very quickly because I’m like, it’s kinda like going to the eye doctor, does a look better to you?
    Or B, I worked on that A or B, no, it had nothing to do with the design. It had me trying to keep in my head what, and then the side by side stuff, I think, uh, wa was, was a lot better. But revisions has saved more people’s butts probably than, than one would remember. Oh. Because I, uh, that an auto save. Um, for a while, I don’t think, I don’t remember when, but I know WordPress, when it started, did not autos save your posts as you were typing them.

    And I remember Matt said, standing on stage saying, no, now your power can go out or whatever. And you’ve got that post and revisions, incl. And, and that also for me, blended into later revisions where, uh, you, you’re, there’s a previous revision. Are you sure you want to edit this or do you wanna look at that or go back to it?

    Tammie Lister: But I think back then revisions was, um, Yeah, I think I always kind of forget the words, but it was when we were trying to make things look real, I think skew morphic or something. It was like when you were trying to make like apple, uh, you’re trying to make things look real or those kind of design things.

    And I think unfortunately it did inherit a little bit from that. Um, so I think now we would go a lot more, um, streamlined. Uh, design has come on a little bit. Uh, it’s more information based. It’s more how you are gonna process. It’s more kind of quick. If you look at the way GitHub and all those kind of interfaces are now, you know, we’ve learned.

    But back then we were trying to solve a problem that hadn’t really been. Kind of comprehended. We were trying to visualize issues that we hadn’t. So it was kind of really interesting to think of like, going back to it now with everything we know about the complications of those. And now we know that people probably do want to extend those, probably do wanna export them, probably do find them useful as well.

    David Bisset: We may see a little bit of a change in this department with phase three, with the, um, multi-user stuff too.

    Tammie Lister: Oh, I think we’re gonna see a complete change in that way, at least I hope we do, because honestly, that’s not gonna scale.
    David Bisset: Yeah. You think? Yeah, I would. Yeah. I, I always get, I get, my daughter says, I’m trying to edit up, posting your site and it says, you’re still in there.

    Can you close a tab? And I’m like, I, or I can kick you out. I’m like, fine. You’re your mother’s daughter anyway, so. Alright, so we have one last category here. Um, Mihir, you are up first. Now this category is how I described this. And I’m getting them, I’m getting these, these are getting wordier as we go along, but okay, so this is a memorable community moment or community initiative or community Cause that wasn’t a WordPress release and you’re saying, well, why did David put not a WordPress release?

    Um, well, because there have been a couple of memorable WordPress releases focused on who was releasing, who is contributing, all great things. But we’ve got a lot of that feedback in the, in the past about, oh, it was, it was, um, you know, the WordPress releases, especially the ones where, um, the underrepresented groups took over forward word press release.

    Great. That that could be counted as a community moment. Fantastic. But everybody says that when they first think of one. So I wanted us to be a little bit more tougher, no word press releases, but anything else is open game in terms of a community moment initiative or a cause. So, Mihir, I would love to hear what you’ve got to say about this.

    Meher Bala: So, For me, when I joined the community, I always, uh, like the very few women who participated and when I used to go to work camps, also the women were fewer. So I just started, you know, gathering all the women and started taking group fit pictures and it became a thing, like if I was there in Word Camp, it was, you know, I had to do a group with them because everyone got excited, new people added.

    So pre pandemic, each word camp I went to, I had, I mandatory went on stage in the lunch break and decided a time place where, you know, everyone will get together. I heard a few things, but I said, this is helping encourage other women. So I don’t see any problems, so why not? And I used to put on, put on Twitter as well.

    David Bisset: So, so, so you organ Yeah. It’s kinda encouraging someone else. What’s that?

    Meher Bala: It’s kind of encouraging another woman to be a part of the community.

    David Bisset: Absolutely. Um, so like selfies, but good, but selfies representing under underrepresented groups. I, I, they’re there. Yeah. The WordPress, I mean, you can talk about this all, all day. And this is not exclusive to the WordPress community, it’s tech in general, right. We’re always used to that. I have a daughter who is growing up and she kind of grew up in the WordPress community more or less for the last 10 years, you know, with the word camp exposure and everything. And you know, today we kind of take some of the efforts to make people feel welcome for granted a little bit.

    Um, there’s still obviously a lot that needs to be done in the community, but back in the early days it was, um, You know, especially if someone, someone relates to an someone who relates to a subject or a con or a conference, they love seeing people that represent them on stage or representing them organizing an event.

    Right. And maybe it’s not apples to apples. Exactly. But you know, it’s, it’s, it’s like, especially, um, especially if, just think if you’re a young woman, I can’t, but I have a daughter, so, you know, I’ve seen her reactions and, um, it’s, she, she can connect so well with when people, when women were speaking at meetups.
    So just imagine like back then we just, you know, their focus wasn’t there cuz we were just happy to have meetups in ward camps, period. And then once we started getting people to speak, then we kind of, like some people especially, started to notice a pattern and that had to be brought to a lot of people’s attention.

    So that kind of, we kind of evolved into a way where, yes, okay, now we’ve got the ba, we’ve got some basics down, but now we’ve got a lot of improving to do because if we want this community to grow and be decent human beings, we should try to make things as as. And you know what that does for me as an organizer, I was focused on speaker stuff, but there were so many people at the work camps like you, Mihir, we’re doing these, um, side, I don’t want to use the wrong term because they’re important, but um, Site events, right?

    Or something like that. But I mean that respectfully in terms of like, yeah, let’s, let’s take a, let’s get this certain group together and take a photo or let’s, or, or have this, um, mini meetup or like an after dinner thing at WordPress meetups and that sort of thing. Or even now online, you know, there’s various, um, communities out there that exist for particular kinds of groups.

    Um, black Press and so forth that, um, that I, at least I’m familiar with. So I think that was a fantastic idea. I don’t know if anybody else is familiar with anything else or wants to jump in, but I think putting down a moment in terms of, now I don’t know how to word this exactly, so maybe you can gimme a term.
    I can put in the show notes. I have women’s selfies written down here just because that’s how my brain works and I don’t wanna be canceled later. WordPress, sorry. If you can gimme another term. That’s what I got. What’s that? Women in WordPress. You got it. I will quote you on that.
    Tammie Lister: Have you seen that? It’s possible to not just see one of you though, as well, which is what you are identifying.

    You are, you are saying that there’s more than one of you and there’s more than one possibility of you as well, which is really, really important. Um, seeing all the different possibilities that you could do in all the different areas, I think that’s important for whoever you are as well. So I love that. I think that’s amazing.
    David Bisset: And more of it, and in the WordPress leadership roles too. So many are women. My family, women are the hardest working ones. Anyway. Okay, we got that on tape. All right, good. All right. Just, just made just a little insurance from, from my wife later. Um, alright Robert, let’s talk, let’s talk a favorite community moment. Or cause Okay. Something along those lines.

    Robert Windisch: So my, my job, uh, my day job is to challenge processes. Now, let’s see if I, if I come, if, if I have a runner up. So I just want to see if it’s like how close I am to the things that are not allowed. Okay. Uh, my, uh, favorite or my, like most re uh, community moment is when the, when the whole room at the, at the state of world guest.

    Um, the point was when met stopped the release cycle, so when, when the, uh, before like, uh, before the, um, um, five oh release, um, like we had this like every three months we had to release and then, um, this was like, it not going to, it was not gonna cutting it because the, the changes we needed to do, um, were really, were too big.

    So we cannot, we, like I heard from so many core people that was not, um, um, Like was, was not gonna like cut it in a few months back to just get it in. So my question is, does counting of a re uh, like starting a release cycle counts. So because, um, that was like, I, we were in the room and was like, yeah, and now that’s why we, uh, need to explain.

    Matt explained that and that’s why we stopped the release cycle now and everyone was like, what the hell just happened for me? That was like, he dropped the mic amenable

    David Bisset: moment. I think he dropped the mic too. I can’t remember. Uh, when was that?

    Robert Windisch: Um, 2017, like, uh, weekend as Tammie, because she was uh, um, uh, design, I think Design team rep after that. Yeah. And like Matt was simply,

    Tammie Lister: it would’ve, I think it would’ve been, well it would’ve been 4.9, but we didn’t do that. Uh, and so yeah, it was four, 5.0. Then we. Had a pause, ended it. So yeah, I think it was 17. I dunno the year exactly. 17. There’s many years. 17, 18 blended into each other during that time.

    David Bisset: But there was a 4.9. There was a 4.9, wasn’t there?

    Simon Kraft: It were many 4.9 s.

    Tammie Lister: It would’ve been like 5.0. It was after 4.9. It would’ve been. So,

    David Bisset: so it’s kinda like 3.0, sorry. It’s kinda like walking toward a, walking halfway toward a wall and then walking halfway toward a wall. There’s 4.9, there’s 4.99, 4.9 9, 9, 4 0.99, nine, oh, not 5.0 yet very

    Tammie Lister: long. 4.9 release,

    Robert Windisch: Yeah. But the, the, the beauty was really that, that there was no release. So there was like, we will have a release when we have a release and like there wasn’t release in between where we like fixed small stuff because we still needed to do while like Tammie and other people were like, okay.

    How, what are we doing? How do we, like, what is the goal here? And, and that’s why it was really for me, like it sh it, it really, uh, in this, in this moment, in this room at the Word camp us, you really could, like, you could feel a needle drop in the room because like, it was something that never happened before, because like you could, uh, um, um, you can set your watch to Roberto releases.

    Mm-hmm. And then we simply stopped doing that while deciding that we, like, stop doing it because it doesn’t make any sense. So it was really, really weird and really good because it, it helped us to make this leap that we not talking about right now, but it, it helped us to really, uh, prepare for that.

    Tammie Lister: It was also a stop and help was also kind of part of it.
    It was a stop and this is how you can get involved. I think that was kind of the other bit like once everyone kind of gets over that Uber stopped, it was, and then here’s how you can get involved. So it kind of had that double um, or this, that was my, my through the haze of time impact, um, was it brings about the, okay, now I can get involved cuz people do like a release circle.

    Right. Um, so consistency. Now I get involved and now I can do that. And it, it did get us to 5.0, it absolutely got us to it. And without that we would not have had the 5.0. You know, there’s no point in releasing something there. We are radically different from what we were, but there’s no point in releasing something that would’ve been half-baked. It wouldn’t have worked.

    David Bisset: Yeah. So we have actually done that once in our, at least once in our WordPress history. Right. Yeah, I, I, I don’t know if we’ll see a moment like that again, at least anytime soon. It seems like Gutenberg phases seem to be planned out, or at least not like that drama ish type of thing.

    Right. It’s not, it wasn’t a press release Rob Robert’s. Right. I remember. I remember saying Matt, Matt said it, and I think a few people had to change their pants. It was that kind of a moment where you just kind of expected like, this is all, this is all we’ve known, you know? And that’s funny because, you know, fast forward to a few days before working at us and, and, uh, you know, me in a hotel room, super caffeinated trying to finish something as Matt is in a chat room saying 5.0, it’s coming out now, whether we like it or not, it’s coming out, you know.

    Anyway. I better stop with the analogies. It was ready. Oh, it was, it was, it was ready. Kind of kinda like I’m on top of this, uh, on a heel skiing and somebody says, oh, you’re ready, you’re ready. And slowly pushing me off the ledge. It’s, it was that type of ready. Oh yeah, it was ready. It was ready. Um, I just did, you know, just, just thinking my life flashing before my eyes right before it came out though. Um, let’s see, Tammie, I think your next, um, community initiative, cause whatever,

    Tammie Lister: I’m going to take you back to 2014 to, I don’t wanna go Miami and the first ever kids workshop.

    David Bisset: Ah, you actually snagged something.

    Tammie Lister: Oh. Cause that fell. I still have. Really fond memories of it. It kind of felt really incredible to, it wasn’t even really that organized. It wasn’t really that.

    David Bisset: Thanks Tammie, really appreciate it. It was that big in,

    Tammie Lister: I’m sorry, but there’s no, like back then we were David all over initiative. I’m sorry. We weren’t, we weren’t trying to do we, we were just gonna be doing the event. We weren’t gonna necessarily try and do anything bigger with it.

    And I think it planted a good seed that maybe took a bit of time before anything else happened, but that was absolutely fine. Um, and it was really important for just to start that. I think it’s both important for representation, but also important for an open source project doesn’t work with older people only working on it.

    So for me it was incredibly special if I think of the people that were in that room as well, who were passing on. Many of them are still involved, contributing, in fact, all of them that I can think of. And it was just really special for me. Yeah. Yeah.

    David Bisset: Um, that, now, just to be clear, for someone who was about to write that email to us, this is not the first kid’s camp ever in a work camp.
    It was the one Tammie attended? No, it was a kid’s workshop. Workshop. It was a, well, I don’t like to use the word kids and work very close to each other because people get sensitive about that.

    Tammie Lister: Yeah. It was 2014. It was no like kids camp or anything like that. It was, it was just, I, I don’t think it was that long, either, we weren’t doing it for or anything like that.

    David Bisset: Kids don’t exactly have long attention spans. So, yeah, that’s under we,

    Tammie Lister: no, it was, it was nothing official. It was no official kids camp. It was nothing. And it, it was, it was long time ago, so there was no kind of officialness of it. Um, but no, it was, I think we got them set up on a blog and we got them to customizing a theme and writing their first post.
    That was as far as we got. That was our goal for the day.

    David Bisset: Some people vowed never have children after that. Our younger, uh, younger volunteers look, well, I mean, I, I, it was there at Miami because I was at Phoenix and saw something very similar. I think it was a one day event at Phoenix. I saw there, I was there watching the kids.

    Which nowaday, it sounds creepy when you say, are you here? Do you have any kids? No, I’m just watching them seeing how they do things. All right. Sarah, security and, uh, but I was watching how they did it in Phoenix, and this was, I don’t know, maybe it’s 2 20 12 or 2013 or something like that. And then, yeah, that’s when we started doing in Miami and now it, now there’s lots of kids’ camps.

    There’s a whole kids’. Section now of learning and, and people in charge of that type of thing now. And there’s probably gonna be something at, uh, us, I know there’s something at Europe coming up, uh, which is fantastic. So it’s exploded. And then when we did our 10th anniversary word pr, our 10th anniversary were Camp Miami.

    It is prog, it progressed to a point where we had the kids, I forget what the ages were, I’ll be gonna say like seven to 11 or seven to 12, seven to 13. That age group doing what you said, more or less. But then we kind of took the pe, the teenagers, 14 to like high school level. And then we had a day where we taught them WordPress.

    And then a day after, like we taught them WordPress and how to build a store in WooCommerce. Then the next day we taught them s e how to market it.

    Tammie Lister: Wow. I think it was also back then we were being very experimental with what could a word count be? Remember the day of rest and all the different kind of buddy camps and different things.

    Oh, yes. I think we were just kind of experimenting with different formats as well. Yeah, exactly. We were just, uh, I think that was part of it as well as like, how can we start? And it’s great to kind of think about that as well. So I think that was kind of amazing.

    David Bisset: Fantastic. Memories. Still one of my mentions. So Simon, um, let’s, let’s cover, let’s cover the, um, anything from a community moment standpoint that stood out for you.

    Simon Kraft: Yeah, I’ll, I’ll stay in the, um, event space, I guess.

    David Bisset: Oh, he’s, he’s choked up. This is a, this is gonna be so good.

    Simon Kraft: Um, and I just noticed that we’ll stay in the 2013 ish, uh, kind of timeframe.
    David Bisset: It’s the WordPress 3.0 3.0 of years, right? Yeah.

    Simon Kraft: Um, because in, I think it was early October, 2013, uh, we had the first word Kim Europe in, in Liden and it was such a stupid idea, um, back then and still.

    David Bisset: Wait, let me, let me write that down, Simon. Yeah. Stupid. Okay, go ahead Simon. Just wanna make sure I got this cuz

    Simon Kraft: it’s just the, the kind of stupid idea that hold on and exploded into the kind of mega event that what computer is today. And it was totally different back then, but the idea to bring like a whole continent together and have a joint event, um, It was beautiful and also it was a nice event.
    Um, I have to say that, um,

    David Bisset: possibly the first regional event, although I don’t know if Word Camp Asia or it’s forced in existence. What’s that?

    Simon Kraft: Yeah, yeah. Oh, it really was. And uh, there was no word can be asked before that, at least. No, no official one.

    Robert Windisch: There was none. There was just the, just San Francisco, the global one as, as we European call that. Yeah. And I think it’s,

    Simon Kraft: it’s some, sorry.

    Tammie Lister: No, you go. As it was the first, and it was done in an incredibly short time. Uh mm-hmm. I don’t think anyone ever realizes how short a time it was done in the end as well.

    David Bisset: Somebody only had a few people, only had one change of clothes was that quick.

    Tammie Lister: But yeah. And, uh, so as, as someone that was involved in it, I, um, it was one of those things that I, I think you, I.
    Rarely get to experience, but the venue was incredible. Mm-hmm. I plus one that mm-hmm. That was one of those venues. Um, we, several of us had gone to a conference before in that venue and got to see that venue and it’s was one of those venues that I would love to use again for something. It’s just a great venue.

    David Bisset: It really also symbol started to formulate the idea that we could have larger word camps and the community had matured to that point where we could bring in a larger event and we could coordinate across multiple countries for that sort of thing. Um, before that, um, you all you had was cities or I think in a few places or, you know, general regions like Word Camp Southeast or Midwest or something, some direction in the us.

    Um, but that was a very memorable moment in terms of community history. Cuz again, I don’t know, I, I think, I don’t know when Japan. I know Word Camp Japans have been very, very long standing, but, but for Europe it was, it was got a lot of attention and I think rightly so. So I’m, I’m really good for that cuz it kind of set the, it set the pattern for all for, for camp us a bit.

    It set a precedent for, um, the scene. There’s War Camp Asia and there’s probably, I feel like I’m leaving somebody out. I think there’s one on the books and I just can’t remember what region is now gonna be. I know they want to have a war camp, Africa War Camp

    Robert Windisch: Nordic. You had a WordCamp Nordic regions in, in, in Europe.
    Mm-hmm.

    David Bisset: Yeah. And you know, who knows in 30 years War Camp Mars. So anyway, that, I think that’s a pretty, pretty, pretty good thing to put a pin on in terms of the community there. Now I, uh, I could, as, as much as I like my, uh, work camp Miami, there really was nothing. Uh, there’s, there’s nothing that equals that level.

    So I’m gonna leave that out because I’m biased anyway, I do wanna put together. You mentioned two things, um, from a community, uh, cause or initiative standpoint. One was reco, and I may have mentioned this in the past episode, so listener, I apologize if I’m repeating myself, but it’s also when we talk about the community, recognizing those that we no longer have in our community.

    Um, so I thought, uh, one thing that stood out to me, that representative was the Kim Marshall’s Memorial scholarship. Um, and you know, and because a lot of the old, old timers remember her, um, I remember her at Work Camp San Francisco. Um, But also like all those other people that, you know, our community, the older community gets, people get old.

    Um, that’s, that’s life, uh, currently. So people will leave the community, uh, in that manner. Not, you know, not, not, not drama wise. I’m never coming back community, but people pass away or people have, uh, accidents and that sort of thing. So it is that, that kind of represents to me, not just the scholarship itself, which is a great initiative on its own, but it’s a recognition of, you know, we have important people that we want to remember the WordPress community, whether it’s in the form of scholarship or honoring them on social media every year, seeing their names and releases.

    I know there’s a couple of people, and I am really, really bad at remembering his name right now, but he created a plugin. He was race, he was into a race car driving. I remember him in a race car. What’s that? Wipo? Yeah, VI, right. But what was his name though? Yeah. What was the name I, I’m gonna kill my why was 0 0 7?

    Yes. The user name. Yeah, but I’m talking about his real name and I’m frustrated with myself. I can’t remember it, but I remember when he passed away, I forget what plug-in he did. I guess I’ll have, I’ll include that in

    Simon Kraft: Shownotes, but he did the regenerate thumbnails plugin and his Alex,

    David Bisset: yeah. Oh, okay. So we, we remember ’em by reputation, but it’s all of those people that do these plugins and Alex Mills. There you go. I’m horrible at remembering names, but yes,

    Robert Windisch: I’m googling ju just like,

    David Bisset: oh, I don’t judge. Just keep your hands here. So we have Kim Parcels, we have Alex Mills, all of these people that, that are involved, that with the community that, that we, that we’ve taken their plug-in, we’ve taken their plug-ins and their work and they’re, you know, and it’s in WordPress core now to our popular plug-in now.

    And the other, the other thing I wanted to point out as a community initiative or, or moments was the Wampoo itself has, and, and I see one behind, um, Tammie, hopefully she knows it’s there. And we have so many, it’s incorporated, like every word camp now has a wpu. Um, it was also a lot of the kids’ stuff had wpu involved as a cartoon character and, you know, that was part of the kids’ camp stuff.

    And, um, I’m sharing a link with you all right now. One of the, one of the coolest swag moments I ever had was, um, for, I don’t know which, where Camp Miami was, but we came out with these UNO cards, with wpu s on them, and. I put it on his open source on GitHub and be, this is the community angle, like a couple of work camps from like the other side of the world.

    I think from, I think from India or Indonesia, I believe it was somewhere in that general area. They pinged us and said, can we use these? I said, yes, they’re open source. So what they did was they just changed the design a little bit. Like they, they put the work camp logo on it and made it, maybe translated it a little bit in their language, but now people are saying, oh, those are cool cards.

    And like, you know, I have a little bit of pride. I said, yes, those, I, those are cool when we thought of them over in Work Camp Miami. But I am, so I’m even more happy to see people repurposing swag like that. And I thought the Wampoo, um, was an original great idea and I’m glad that, um, um, Matt kind of adopted that as part of the unofficial slash. Unofficial. I’ll say unofficial mascot cuz I’m not seeing it on official.

    Robert Windisch: Unofficial. Official. It’s the official term for the, it’s unofficial official.

    David Bisset: Just think of all the pins, all the badges, all the shirts. I don’t know if you ever saw the Work Camp Wpu shirt from Work Camp Miami that had the face,

    Tammie Lister: there was an actual physical wapuu.

    David Bisset: Yes. The one walking around there.
    wapuu became physical. I was wandering around. It was the best work camp Miami 2019. I know the people that were in that suit. It was like a walking Cheeto, but it was so worth to see a walking wapuu around.

    But yeah, it’s just, think of all the swag and like the MAs, the just the very thought of a mascot, um, itself. Not a logo, but a mascot I thought really helped shape the WordPress community was a great community moment. So anyway, thumbs up to all those people. I have one to, what’s that?

    Tammie Lister: Yeah, I have one to add. I think the sustainability initiative, which is a newer one. I think that’s just getting started. But I think. And gathering momentum and finding out what it means. But as someone that’s organized a word camp before and tried to do it, sustainability when we in Brighton, um, I think it’s really good from that app. But I also think it’s really good from just the impact as a project that we leave and like the technology, I think it talking about like trying to be around as a project for a while, we kind of have to be aware of all those aspects.

    So I think that initiative deserves a kind of mm-hmm. Call out because it crosses so many of our areas and it doesn’t necessarily get and so much kind of eyeballs I think.

    David Bisset: Yeah. Make sure to throw that in the show notes by the way, cuz. We’ve shared so much here today. And, and, uh, no, I’ll include everything that you’ve mentioned. Everything you thought of, throw it in the show notes. I’ll do a array matching thing so we don’t get duplicates. Um, all right, so I, we’ve covered kind of the categories and we’ve covered a lot of stuff and I’m really happy cuz a lot of stuff we’ve talked about here today is, is not been mentioned in depth in my other conversations.

    So that’s fantastic. I got exactly what I wanted out of you all. But, so what I wanted to do is I wanted to go around one last time and see if there’s any random thoughts that appeared in your head about anything else. Sky’s the limit. In terms of, in terms of any moments. Um, you know, I was gonna say good, bad and ugly, but let’s just, we’ll, let’s just keep it or good or bad because I don’t have time to cover ugly.

    Um, Mihir, um, what have we left out here? What did we not mention that you think could, could be mentioned real briefly?

    Meher Bala: Uh, recently Michelle has created a side WP speakers.

    David Bisset: Ah, yeah.

    Meher Bala: So this. I see this helping the organizers with finding out, uh, speakers in their areas or n nearby do not go and approach them. So that is one thing which just came across my mind right

    David Bisset: now. Yeah. Kudos to her for that initiative. She does so much now, the job things on Wednesdays and all her, all her community work, which we don’t have time to go into here. That’s fantastic. Yes. So speakers of speakers project. My, um, Robert, anything we might have, we haven’t touched on at all briefly?

    Robert Windisch: Yeah. Um, so small thing, um, the time when W P C L I became a make project, Because it was a project outside. And, uh, it’s really like if, if people like, cause the people who work, um, professional with WordPress sites and like on local, on local, um, machines and like automating stuff like the W P C L, I be becoming like a, a real make project with all the um, good and bad things around it. It was really, really good for the project and for Daba P c I to jump the simply make sure it stays around

    David Bisset: wp I, yeah, develop. If, if you’re a developer and you’re not familiar with that, slap your face twice and get reading in the documentation. Tammie, what have we not mentioned here at all?

    Tammie Lister: This is almost like project management, but I’m gonna say in core, when started to have more organization core meetings and recognizing roles for releases, I think that that started to allow people to see where they could be part of it.

    Um, and. Gave enough order to those meetings that someone could follow along, you know, you can follow the agenda. Um, so those kind of things. Having enough project management, uh, so that someone could belong. So just being able to have a call. We didn’t do that. We didn’t have calls for releases and Oh, yeah.

    And people being part of it and, and having like, Hey, would you like to have these roles? And people been able to step up and have those roles, that’s really important. And it’s not that far, but we’ve had that. So I think that is really, really important for us. Yeah.

    David Bisset: You take that stuff for granted sometimes, not realizing how you do, it’s never been, and

    Tammie Lister: it’s not just like tech, it’s like documentation and it’s growing.
    Right. The options that people can step up and be part of. So yeah, I think that,

    David Bisset: and that’s what some people that have come into the WordPress community in the last couple of years, they haven’t known a time before that. It’s kind of like

    Tammie Lister: no. And Core Chats used to be a lot, there used to be a lot to be part of and try and follow and keep up with. Um, and it would put off a lot of people. So this is an incredibly welcoming, so yeah, more inclusive.

    David Bisset: It’s trying to explain what a V H S tape is to my daughter today. Yes. That was, there were times before digital media. So Simon, what? And one or two things briefly. We may not have covered that. Yeah. Could see.
    I can see your gears turning. Sorry.

    Simon Kraft: No, no. I have something, uh,

    David Bisset: stuck in your teeth . Oh, um, oh, I’m sorry. I thought I could read, I thought I could read people. God, what else? You got anything in the tank?

    Simon Kraft: I would like to give a shine a light on a make team that I think has its work a bit undervalued sometimes. Um, the accessibility team. Uh, you do like a really great job speaking of inclusivity, um, in making sure that more people can use WordPress, and I think that’s part of democratized publishing. So they do very, very important work.

    David Bisset: Yeah, I can’t argue with that. I, I am always amazed at the new, it’s especially so much harder now with all the more complex technologies, especially in the admin, right?

    And that’s still a work in progress. I think all the initiatives that we’re doing today, you know, ev moving forward, I, I want, I wanna, I wanna see more attention to them, um, because a lot of accessibility needs that kind of attention and just like performance or anything else. And so many times accessibility is, is not a first brain thought type of a thing.

    So I really think that deserves a real good shout out as far as I’m concerned. I’ve got three random things left. I, we’ve talked about acquisitions in the previous. Shows, but I always thought the Tumblr acquisition really stood out to me in terms of a potential that it has for WordPress moving forward that isn’t WordPress.

    Um, Gutenberg is supposed to transcend WordPress. Maybe, maybe that’s, uh, Matt’s made that comment a couple of times, so it’s interesting to see where that might go. Um, P two. Speaking of things that, like some, somebody just said, does he need to do at the restroom? No. The letter p and two. Is a, if you don’t know what that is, Google it.

    But because, but when, when, when Tammie said something about the structure of, of, of backend WordPress organization, um, it is a blog that Matt and Matt actually talked about this a number of times, and I think they have a new version called oh two. Um, I’m not sure if that’s out yet in terms of a, like a plugin or a theme you can download. I think, I, I can’t remember. All I remember is it was, Cutting more cutting edge in them. But we used to,

    Robert Windisch: it’s a hosted version on wordpress.com. Yes. The

    David Bisset: hosted version version. It’s like halfway. It was halfway. They’re like, you can’t get it, but you can. You can get it because it’s hosted this place. So if you don’t know what those are, just go ahead and Google ’em.

    But P two was fundamental to the organization of a lot of WordPress stuff, even it as it exists today. So like as early as last year, I remember like Word camps, having a P two doc with people organizing writing notes in there. And Matt was always a big, big fan of P two in terms of like, you know, because it’s basically more or less a block for teams, right?

    A big, big, big use at automatic. And I’m pretty sure it still does. And finally, I have elevator advertising at work camps, and we’ll just leave it at that. So thank you very much for everybody. Um, Mission here wasn’t to cover everything. That’s impossible. But I wanted to cover things from your brains, cuz all you I respect and are unique and I you brought the game today.

    Thank you very much. I greatly appreciate it. So, um, let’s go around and then do your, do your, let’s, let’s say we’re people, I was gonna say do your closing remarks, but this isn’t a talk. Um, where can people find you, uh, on social if they want to cont if they wanna follow you, because these days we, we, it’s, who knows? It’s social blog, whatever you want to, whatever you wanna share. But here you go first.

    Meher Bala: Uh, I’m on Twitter, me, I’m on LinkedIn and my website meher.com.

    David Bisset: Yes. And we’ll also put these in the show notes too, so I don’t have to worry about spelling everything out cuz I can’t spell. It was very nice to have you, um, Robert, um, the, yeah, if, if, uh, yeah, go ahead.
    I was gonna say, where can we buy that hat? But I don’t think that exists anymore.

    Robert Windisch: That’s very like with pins or without. Um, so it’s, uh, it’s nubis on, on Twitter and otherwise it’s nubi it on the WordPress profile.

    David Bisset: Thank you very much, Robert. It’s good to see you in the hat again. And, um, if you ever wanna sneak into a Word camp, just don’t wear the hat and people won’t recognize you. Um, Tammie, uh, where can we find you?
    Tammie Lister: You can find me at karmatosed on all the things.

    David Bisset: Yes. Pretty much still and don’t What about, yeah, well, we’ll just put show notes. Just that. And well, people will find you again. You also have a, um, you also have you started a new blog recently too, or am I, I have now next slab.

    Include that in show notes as well, because we’ve been, I’ve been reading, I’m, I, I, I’ll, I, I be ashamed to admit, I don’t know when you started it, but I’ve been picking up the last couple of posts, so they’ve been very insightful. It’s only been a couple of weeks. Thank I’m so God. I put myself out there and it will work.
    I’m sorry, go ahead. Yeah,

    Tammie Lister: I’m just starting to write just generally about where could WebPress go in the now and the next. Oh yeah.

    David Bisset: Okay. I’ll throw that into show notes as well. Just some thoughts. Yeah. Well, you’ve always had some good thoughts. I think it’s worth sharing. Simon, where can people be finding you?

    Simon Kraft: I think the easiest is https://simon.blog/ . Yeah. Yeah. I was an early adopter.

    David Bisset: Um, you don’t have to rub it in, but Okay.

    Simon Kraft: And I think I’ll link to basically all the other things from there. So I won’t try and, uh, spell out my masteron username and domain thingy.

    David Bisset: Sorry. Please don’t, because it sets off my Amazon Echo for some reason when you start saying master on things. Nope, we’re good. All right. We’re fine. Uh, yes. Yeah, Simon Dolo. Wow. And you’ve got an English translation too. Oh, that’s great. Last crappy Twitter in beds, please. Ooh, I’d like to read that one. All right. So Simon Dolo for you. So, um, just if you’re hearing this and you wanna follow me, um, best place to go would be either david bis.com or David bi.social.

    But thank you all for coming. Your time is precious. Greatly appreciate it. And, uh, we will talk later. Thank you.

    Simon Kraft: Thank you. All right.

    Today is a little bit of a departure for the podcast. It’s an episode all about the last 20 years of WordPress.

    You’re going to hear a round table discussion with four WordPressers talking about their thoughts on the last 20 years. It features Meher Bala, Robert Windisch, Simon Kraft and Tammie Lister, with David Bisset as the discussion moderator.

    They cover a lot of ground, and it’s fascinating to hear their WordPress stories from the past two decades.

    Notes from David Bisset:

    To honor WordPress’s 20th anniversary I locked myself in a room with four wonderful community members to talk about some highlights in it’s history.

    Primary topics include:

    • a memorable design or refresh in WordPress’ history
    • the most notable enhancement to WordPress core (that wasn’t Gutenberg related)
    • a memorable community moment or cause

    There’s also lots of ‘forgotten’ history and features also come up in the discussion. So, regardless of how long you’ve been involved with WordPress, you’ll learn and maybe have your memories jogged!

    Discussion subjects and links:

    Robert Windisch

  • MariaDB Health Checks Plugin Now Available on WordPress.org

    A new MariaDB Health Checks plugin is now available on WordPress.org, thanks to the efforts of contributors involved in the 2023 CloudFest Hackathon which took place in Germany. MariaDB is a popular open source database used by those looking to further scale their websites, as it is generally faster than MySQL with better support for a concurrent number of connections.

    “At the moment it appears WordPress is dominating the PHP world, so this seemed to be the perfect target,” MariaDB Foundation Chief Contributions Officer Andrew Hutchings said about creating the plugin at the hackathon.

    “The MariaDB Foundation loves WordPress (I’m writing this post in WordPress right now) so it seemed like a logical project.”

    The plugin helps users debug their MariaDB databases by displaying important information, such as logs, locale, connections, character set and collation, and options. It also shows a graph of the number of queries and the execution time over the last 24 hours.

    The plugin also integrates with WordPress’ Site Health feature with two checks: an end-of-life check and a check for whether Histograms have been run. Histograms are an optimizer that can help improve MariaDB performance, and the plugin enables calculation of histograms to run on WordPress tables with the click of a button under the plugin’s Tools menu.

    “There are a few features now and it is a good framework to add more features to in future,” Hutchings said. “This is a community project and is open to suggestions and pull requests. This is a project that we at the MariaDB Foundation want to support in the future.”

    MariaDB Health Checks is developed on GitHub where developers can follow the plugin’s progress, contribute to new features, and report bugs.

  • #77 – Mario Santos and Luis Herranz on What the Interactivity API Is and How You Can Use It

    Transcript

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

    Jukebox has a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes and in this case, how you can start to make your sites more interactive.

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

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

    So on the podcast today, we have Mario Santos and Luis Herranz. They both work for Automattic but are sponsored to work full-time in WordPress.

    The main focus of their work is the block developer experience, and they are part of the group of contributors that worked on the Interactivity API proposal.

    The Interactivity API is the main focus of the podcast today, and if you’re working with blocks and dynamically displaying data, this is sure to be of interest to you.

    We start out the podcast today with the usual introductions, and get to know Mario and Luis. And then we learn what the Interactivity API is and what it can do.

    The conversation is framed around a blog post written by Mario entitled, The interactivity API, a better developer experience in building interactive blocks.

    In this Mario shows examples of what website interactivity is. In short, it’s the ability for content to be amended on the fly without a page refresh. Of course, this is nothing new on the web. We’ve been seeing this for years in WordPress sites and elsewhere. But now you’re going to be able to create interactivity in a standard way across the different blocks on your site.

    The project hopes to absorb complexity and make the creation of interactive objects fairly trivial. Mario and Luis talk about examples of where the API might be used, and how it can be implemented.

    We also discussed the fact that in the past developers have gone their own way to make their sites interactive. It all works, but it means that no two implementations are the same. This causes issues if the project is taken over by another developer. But it’s also a drain on resources.

    Mario and Luis make the point that having a standard way of creating interactivity will benefit everyone in the long run. We get into the weeds a little and talk about the approach the team took when building the API. They decided to use directives and we find out why this was, and what benefit it brings over other possible solutions.

    The project is still experimental, and they’re looking for people to test and report back on what they find to move the interactivity API forwards.

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

    And so without further delay, I bring you Mario Santos and Luis Herranz.

    I am joined on the podcast today by Luis Herranz and Mario Santos. Hello.

    [00:04:15] Luis Herranz: Hey, hello Nathan.

    [00:04:16] Mario Santos: Thanks for inviting us.

    [00:04:18] Nathan Wrigley: You’re so welcome. We had an introduction on Slack from Anne McCarthy, who listeners to the podcast may very well have heard of, and she wanted me to chat to these two about the Interactivity API, so we’re going to get onto that. It’s a brand new project. Could be very interesting if you’re a developer implementing it, but also if you’re an implementer of WordPress websites and not a developer, you’ll be interested in the outcomes of it.

    Before we do that, the usual questions at the beginning. I’m going to go to Luis first, if that’s all right. Would you mind just giving us your backstory, how you’ve come to be on a WordPress podcast, how long you’ve been working with WordPress, who you work for as much or as little as you wish.

    [00:04:57] Luis Herranz: Okay, thank you. I started creating websites with WordPress 2010, I think, maybe nine, I don’t know, a long time ago. And I wanted to start a company in 2013, with Pablo Postigo. And we thought, okay, we wanted to create native apps for different companies, like services and so on.

    And we knew WordPress, so we basically started with what was later known as headless WordPress, but back in 2013. And since then we iterated, we created a team. We got some investment and we started doing things on top of WordPress. Mostly in headless. First with native applications. Then we moved to just web have applications, but still on headless. Very focused on React.

    And in 2019 we launched a open source framework for headless WordPress, powered by React. So we were very focused on developer experience and performance.

    And in 2021, that company, Frontity was acquired by Automattic, so we could become like full-time contributors and focus on, well, basically what the Interactivity API proposal is today. Bringing some of those user experiences, what are possible with other solutions, to WordPress itself, on top of full site editing, or block themes.

    [00:06:31] Nathan Wrigley: Thank you so much. That’s really interesting. I appreciate your nice history there. Thank you. And we’ll ask the same question this time of Mario. So Mario, backstory please.

    [00:06:41] Mario Santos: Thank you. Actually, my story is really similar to Luis. Well first, when I finished the degree, I studied industrial engineer, but I didn’t want to be an engineer. So I started trying different things, and while I got my first job, I created a store in WordPress with WooCommerce. And then, that is when I started to learn about WordPress and all those things.

    And later, based on that, I joined Frontity. I don’t remember exactly the year, 2015 maybe. And from there I really learned what was WordPress because we started going to meetups to WordCamps, and we started to, well at least I started to learn from the community.

    From there the story is mostly the same as Luis. We were working on headless mainly. We were working with WordPress. And at some point, we were acquired by Automattic, and now I’m a sponsored contributor, working full-time. And as Luis said, we are focused on the developer experience, and the Interactivity API that we are going to talk about is part of it.

    [00:07:45] Nathan Wrigley: Thank you so much for that. So the Interactivity API, I’m going to link in the show notes to a post which you can find. Now the post you’re going to be looking at is on the make.wordpress.org website. It’s written by Mario. It was on the 30th of March, 2023 that came out, and it’s entitled, Proposal, The Interactivity API, A Better Developer Experience in Building Interactive Blocks.

    Now, if at any point during this podcast you become a little bit confused or you wish to have some more background, I would recommend pausing and going and reading what is an incredibly lengthy and detailed post, with actually a boatload of interaction and comments as well. It’s really heartening to see so many people chipping in, and giving their thoughts on this Interactivity API.

    But I guess the best place to kick this conversation off simply asking, what is it? What is the Interactivity API? What does it do? Why does WordPress need such a thing?

    [00:08:47] Mario Santos: I can start with this one. So, the Interactivity API is what we are proposing. The group of contributors that are working on that. It’s basically a new standard system to easily add front end interactivity to your blocks. Until now, most of the Gutenberg APIs have been focused on the block editor side, and there was unintentional gap on the front end.

    So block developers could choose whatever they want. They could choose any Javascript framework, or other solutions. And the Interactivity API aims to cover that gap. Creating this standard.

    So imagine functionalities like, like this post or e-commerce functionalities like add to cart, or the checkout, the instant search, page transitions, the comments form, without a page reload. So those are the user experiences that the Interactivity API aims to cover.

    In a way that is real easy to build them, and block developers don’t have to deal with complex scaffolding or external tools. And it’s important to note also that it’s completely familiar and compatible with PHP and the block ecosystem. So overall, that’s what the Interactivity API is. Basically a standard to easily create any interactive experience that your users want.

    [00:10:06] Nathan Wrigley: Luis, anything to add?

    [00:10:09] Luis Herranz: No, it’s really filling that gap, or even that opportunity of absorbing as much complexity from the developers. Standardizing everything in a single solution, and making sure that it’s performant, and so on.

    So yeah, there’s some advancement in web development in other places, mostly in the Javascript ecosystem and WordPress has never been opinionated in the front end, so this is kind of the first time for WordPress.

    But yeah, we think that it’s an opportunity as well to absorb a lot of complexity for the developers, and to enable some of the user experiences that were not possible with WordPress before.

    [00:10:52] Nathan Wrigley: Now we have some show notes, and we’ve got a list of questions that we’re potentially going to run through, but I’m going to skip to the end, more or less of the list of our questions. Because one of the things I think to do at the beginning would be to provide listeners concrete examples of how this might be used.

    So do you have any examples that you think would demonstrate clearly the kind of things that the Interactivity API is touching on? I’ll just mention one. Which is the very first thing you’re going to see more or less when you open up Mario’s article, and it’s a video. It’s pretty short, two minutes long. And it demonstrates something a little bit like Netflix, where you’ve got, a view of three or four different video thumbnails. There’s a bunch of different movies there.

    And the intention is that you would like to preserve your favorites. And so there’s a little heart icon, which is lodged in the top left of the thumbnails for each video. And as you click on that thumbnail, the heart becomes colored in. It goes from gray to red. But also in a different part of the UI, in the right hand of the view, the menu, traditional place for the menu, there’s a little total which goes up from two to three to four, and if you remove the hearts, it goes back down to two and so on and so forth.

    So that’s one example of how you might use this. It’s able to do things on the page without needing to do page refreshes. And the idea is that this will be a standard way of doing it in blocks. And I wonder if you could give us some other examples. You mentioned WooCommerce and things like that. But let’s go into that a little bit. Some examples of where this might be useful for developers and end users to know.

    [00:12:35] Mario Santos: Yeah, so basically the use case is anything that is interactive and requires Javascript should be able to be done with the Interactivity API in an easy way. So imagine like a slide show or light boxes in the image. So when you click on it, it zooms, and when you click out or scroll, it goes out. Some models like search, subscription, quizzes, e-commerce integrations, like you just have mentioned.

    And one of the features that is enabled by having a standard is the client site navigation that basically is navigating through different pages of your WordPress site without triggering a page reload.

    It’s important to know that this is something that is going to be enabled by the Interactivity API, but it’s going to be completely optional. So if you don’t need it, you don’t have to use it. But it powers other features like you can see in the movie, that we are paginating between the different pages. We are in the query loop. You have the pagination block, and you can go through the page one to the page two without page reload.

    And for example, well, in the movies demo, we are showing that you can play the trailer and you can keep navigating and the video doesn’t stop. So those kind of user experiences that, for example, in this podcast you could be listening to this podcast in WP Tavern, and you could navigate to the articles.

    So, maybe you can be reading an article while you are listening to the podcast in the same way. And the podcast will keep playing. Those kind of user experiences are enabled by client side navigation. And you can also find in the movies the instant search that you start typing and the list of results is automatically updated.

    Infinite scroll could also work. Client size submissions like the comments form right now, in typical WordPress sites, when you submit a new comment, it triggers a page load. So this could be done directly in the client. So those are the kind of user experiences that we are talking about. And yeah, I think it’s important that this is totally compatible with the current block templating system. So whatever you change in the editor is going to keep working.

    [00:14:54] Nathan Wrigley: That’s great, yeah. Luis, anything to add?

    [00:14:57] Luis Herranz: I would add that I really like that demo. Because it’s a demo that we didn’t come up with. It was a demo that existed before. There is a version of that demo created with all the major Javascript frameworks out there. So there is one for React using Next, Vue using Nuxt, Svelte, Quick, Astro and so on.

    So, you can compare now the WordPress version with the other Javascript frameworks, out there. I’m super happy to say that it really, in terms of user experience now with Interactivity API, you can provide the same user experience than the others. And this demo was created to show these type of complex or great user experiences.

    With WordPress, now with the Interactivity API, you’re able to create that type of user experience, but leveraging the server side and the block editor. So the other Javascript frameworks version is 100% code, where this movies demo version of WordPress is done with Gutenberg and everything is a block, and you can go and change wherever you want. Which we think it’s really powerful.

    And there’s yet another thing there, in comparing with the other frameworks, and it’s that if you look at the performance is a top performer there. It’s only 13 kilobytes of Javascript. Only a new experimental mode of Solid is able to be as performant as that one. So yeah, I’m really happy about enabling those user experiences, but with full compatibility with the Block editor and block themes, and with such performance.

    [00:16:44] Nathan Wrigley: It’s true to say, I guess, that if you go to that demo, you will not be seeing anything that you haven’t seen somewhere else online. You’ve seen the ability to like things, and you’ve seen infinite scroll before, and you’ve seen elsewhere online the ability to paginate without a full page refresh, and you’ve seen comments being added, again without having to submit a new page and so on and so forth.

    But this is creating a standard inside of WordPress. Why did you feel it was important to do this? Why not just leave developers to do their own thing? Again, we’ve seen WordPress websites implementing this. You know, I’ve been to countless WordPress websites where I’ve seen these features.

    Clearly somebody’s dealt with it before and implemented it in their own way. I guess you’re just trying to make it so that everybody can build on top of the work that you are doing, rather than everybody going off in their own way and implementing a completely different solution based upon, well, however they wish to do it?

    [00:17:43] Luis Herranz: Yes. It’s about absorbing complexity. So, definitely anything you can imagine, it’s possible with WordPress. The thing is how easy is to do it. And with this kind of standard, our hope is that those user experiences are not only easy, but also working practically out of the box.

    [00:18:05] Nathan Wrigley: I’m guessing that this standard is going to be something that you are aiming at developers. Presumably the developers will then make it fairly straightforward for end users to interact with blocks and what have you, to make this available to them. But how would the standard actually work? What is going on in the background? How are developers going to implement this?

    [00:18:25] Mario Santos: If I can add one note to the why this standard, is I think it’s also important to note apart from what Luis says, is that it absorbs a lot of complexity. In an ecosystem like WordPress where there are a lot of plugins interacting with other plugins and those kind of experiences that we have.

    It’s important that following a standard enables things like block communication. For example, we can see what we were talking about in the demo that you are liking a movie and it’s updating another block, in another place. So if different blocks, created by different block developers, in different plugins are not using the same approach, it’s really difficult to be able to communicate those blocks. And having a standard solves that. And yeah, that composability and compatibility to nest the structures of different interactive blocks is possible thanks to a standard.

    [00:19:21] Nathan Wrigley: Right. Okay, so you’re really opening it up so that any block developer can implement this so that, I don’t know, a different block developer can hook into the exact same standards so that two completely separate blocks, created by completely separate individuals can have interaction via the Interactivity API, right?

    [00:19:42] Mario Santos: Yeah, that’s it.

    [00:19:43] Luis Herranz: And they also use this, the same code, the same framework. Because if each block developer starts choosing their own framework, maybe some developers like React, some developers like Vue, some developers like Svelte or whatever comes next. Then WordPress sites could end up loading a lot of unnecessary Javascript.

    So yeah, it’s important. Now that sites are, are a mix of blocks from different developers, these blocks are like small units. Yeah, it’s important to agree on a single kind of solution.

    [00:20:17] Nathan Wrigley: Yeah, good point. Okay, so how is it actually going to work then? You mentioned in the article, and I think one of you mentioned it just a moment ago, that you’re trying to make it so that people are familiar with PHP, don’t necessarily have to get into the whole space of learning React or what have you. I’m not entirely clear on what the position is there, but is the intention to make this as simple as possible for people who are steeped in WordPress’s PHP history.

    [00:20:44] Mario Santos: Yes. We wanted to make it as easy as possible to everyone. So yeah, that’s included. And yes, we said this is compatible with PHP, and it has been designed to be block first and PHP friendly. So yeah, it’s should be easy.

    And going back to the question, how this standard work. Basically a system based on directives. I’m not sure, for those who are not familiar with directives, they are a way to extend HTML. They are custom HTML attributes that tell the Interactivity API to attach a specified behavior to a DOM element, or even transform it. So for those familiar with Alpine. it’s really similar, but it has been designed to work with WordPress.

    [00:21:32] Nathan Wrigley: I know it’s potentially a bit on the technical side, but you talked about the CSS nature of things there. I’m wondering if you can give an example of how that might be implemented. What would you actually be doing, declaring those directives?

    [00:21:47] Mario Santos: Okay, in order to create an interactive block using Interactivity API, you have to add directives to your markup. So you have some HTML, so you add custom attributes that are directives, and they call an action that is defined in Javascript in the view.js file of your block.

    [00:22:06] Nathan Wrigley: What is the benefit of doing it in that way? You mentioned that you want it to be available to everybody. Is this the kind of thing that, obviously experienced developers can probably pick this up in a heartbeat, but are you trying to get people, how do we describe this, who are less experienced say. Is this going to be something that you could pretty quickly learn even if your developer chops are not all that impressive?

    [00:22:29] Luis Herranz: Yes. The initial goal for this proposal is more enabling user experiences for WordPress that were not possible before, or were very difficult to do before. We also have a focus on developer experience, but that’s something that we think we can also keep improving over time.

    This doesn’t have to be like the final API of creating blocks. We can work, keep working on simplifying things over time. For example, right now none of these touches like the editor part. So if you are creating a block, the edit is just, is still done in the same way that it is done today using a React component. But maybe in the future we can explore how we can kind of extend these directives also to the editor and if it makes sense to unify and simplify the templating for both use cases. But is not the main goal of this proposal at this moment right now.

    [00:23:32] Nathan Wrigley: When you were making decisions about this, and you decided to go with directives instead of things like using React or something. Was there quite a lot of toing and froing? Was there a lot of soul searching, what the best way to do it was? Or was it just fairly straightforward from the very beginning that using directives was the way you were going to do it? How long did the conversation take before you settled on this? is it fair to say that everybody’s on board with this? This seems to be the way to do it.

    [00:23:58] Mario Santos: We believe so. I mean, we have researched a lot of alternatives. Actually, as we mentioned, we come from Frontity, that it was a React framework. React was like the first alternative we had in mind, but we defined as a list of requirements and we started researching different possibilities, and at the end we come up with the solution to be the only one that it was the only one fully compatible with WordPress.

    Just to explain this a bit better. As directives are custom attributes that we have in the HTML, we are using the HTML as the templating system. And this comes with many benefits, for example, were not possible with React. As HTML is the templating system, the service rendering is supported by default, for example.

    That is something really important in WordPress, or WordPress, APIs like WordPress hooks, that we are used to WordPress hooks in plugins, to extend some functionality, or translations. Those things, with directives using the HTML as the templating system work out of the box. And we can keep using those APIs to even extend the directives.

    And I think this was one of the main blockers to not use React. This system, the service rendering is supported, and the WordPress API are supportive as well. That using other approaches can get tricky or even impossible, I would say.

    [00:25:32] Luis Herranz: Yes. I think we spent like a year or so researching this. And at first we tried with Javascript, JSX, or even JS templates like Vue or Svelte, and so on. But yeah, I think that that direction, things start getting like super complex. And once we switched to using HTML as the templating language, it was like boom. Like everything works out of the box. Everything is like super simple. Everything is compatible. So yeah, it was like seeing the light a little bit.

    [00:26:04] Nathan Wrigley: if I’m a current block developer, there’s obviously now going to be this conflict of, do I carry on with what I’ve been doing so far? I’ve got some kind of interactive component in my blocks. Do I carry on with what I’ve been doing up until this point? Or do I flip over and start using the Interactivity API?

    You’ve obviously just mentioned some reasons why that could be the case. But I’m wondering if there is anything else buried in there. In other words, what’s the use case to switch? There’ll be a bit of retooling, you might have to rewrite a whole bunch of stuff that you’ve already rewritten.

    Do you think the benefit’s going to be in there purely for people who are creating new things? Or do you think there’s going to be a benefit for people who already have existing things out there in the real world, to go and rewrite what they’re doing using the Interactivity API?

    [00:26:54] Luis Herranz: Of course, as everything in WordPress, this is optional. Even though we want it to become a standard. It’s optional. But there’s going to be some kind of sitewide experiences that can only be enabled if all the blocks use this language, or this standard. So yeah, our hope is that there’s not going to be any reason for new blocks to not use this.

    Because it absorbs a lot of complexity and it works out the box with all these things. But there’s also going to be some benefit on migrating existing blocks to this system if you want to make your blocks compatible with these new user experiences. And also, get rid of all the complexity that you have to deal with in terms of bundling and performance and things like that.

    [00:27:42] Mario Santos: And actually it can also improve the user experiences, beause due to this complexity, we have seen many cases of blocks using React in the front end, but having issues with the server side rendering or not having server side rendering at all. So it could be a good approach to migrate to the Interactivity API, because it’s going to be easier to improve their blocks to support server side rendering, hooks, or other user experiences. There may be cases that they could benefit from that as well.

    [00:28:13] Nathan Wrigley: Yeah, I guess the intention would be for a slow but steady migration over to using the Interactivity API, to the point where it just doesn’t make sense to use anything else. One of you, I can’t remember which one of you it was, mentioned performance implications there. I’m just wondering if you could dwell on that a little bit. Have you, in your testing so far, really noticed this? Has it speeded things up, made less use of resources and so on.

    [00:28:39] Mario Santos: Yes. We’ve been testing and we want to test everything better and we will keep testing it in real sites. But it’s something that we had in mind from the beginning, that it has to be as performant as possible. And that’s why the runtime code is so small. It’s around 10 kilobytes. And yes, Luis before compared with other Javascript frameworks is performing pretty well.

    I think we did mention this, but it’s using React under the system. So that’s why it is so small. And yeah, it is actually performant and we are looking for other ways of optimizing it. For example, we want to only send the directives that are needed by the blocks that are in the page. Or we want to send the scripts so they don’t block the page rendering.

    Or for example, we are also exploring the possibility of the scripts, so they are only load when they are in the view port. So, yeah, overall I would say it’s performant. It’s been designed to be performant. The code is relatively small, and we are still looking for ways to optimize it even more.

    [00:29:51] Luis Herranz: Yeah, I think that’s important. It’s not only performant today, but you have the guarantee that it’s going to be performant in the future, in the terms of you don’t have to, as a block developer, you don’t have to deal with performance in that sense anymore. Because that’s absorbed now by, well will be, hopefully absorbed by WordPress at some point.

    And then if there’s something new in the web platform that can be leveraged to increase the performance and so on, it will be done in the WordPress side. So your block will just benefit from that, from just adopting this standard.

    [00:30:29] Nathan Wrigley: In the article that you wrote, Mario, the first word is the word proposal. Which implies that this is a work in progress, shall we say. And I’m just wondering how far down the path of usability you would say you’ve got. In other words, can developers begin using this out of the box? Have you seen real world examples of people using this?

    And have you had some interest from developers who perhaps haven’t implemented it, but certainly want to get on board? Because I’m guessing the more yes’s we can answer to that question, the more likely it is that other people will say, okay, yeah, let’s take a, let’s take a look at this. So, can you use it, and have people been using it?.

    [00:31:08] Mario Santos: I would say, yes, you can use it, but we remind that this is still experimental, although we included the proposal word there. This is still experimental, very likely to change. So the APIs that we are using right now, that are used for example in the movies demo site, we are confident that they work, but maybe the syntax change.

    So we haven’t promoted it yet to be used too much. There are people experimenting with it and giving feedback. For example, there’s an ongoing experiment in WooCommerce to replicate some of their blocks using directives. But there’s nothing in production yet because, as I said, this is still experimental.

    There are some missing functionalities that may break your site, and it doesn’t have any documentation yet. So, I would say you can use it at your own risk because it’s experimental. We would love people to test it. To give feedback. We want to understand better if it’s easy to use the blockers that people may face.

    Just to to clarify. In order to be able to use it, we are working on repository in GitHub. It’s a plugin that you can install, and from there you can create your own interactive blocks. Or if you prefer, there’s also the repository for the movies, with some examples that you can take a look and modify or whatever you want to do.

    [00:32:34] Nathan Wrigley: Are those repositories linked from Mario’s article on make.wordpress.org?

    [00:32:40] Mario Santos: Yes.

    [00:32:41] Nathan Wrigley: Okay, so perfect. So if you want to find those, you can just go to the article, which is going to be in the show notes and you can find them all there. Now you’re both working at Automattic, and although it was only about 30 minutes ago that you gave me your bio, I wasn’t quite sure.

    I know that you’re both sponsored full-time in WordPress. Is this project, the Interactivity API, is this a focus for both of you at the moment? In other words, are you being asked to implement this, full-time, part-time? Are you tasked with making this happen?

    [00:33:12] Luis Herranz: Yes, we are. But we are not the only ones. It’s a large group of contributors. But yes. It was part of when we stopped developing Frontity the headless framework, and joined Automattic, it was precisely to focus on this. And we thought it made a lot of sense. Yeah, and thanks to Automattic for sponsoring us to be able to work on this for WordPress.

    [00:33:40] Mario Santos: One note on this, as you said, there are more contributors working on this Interactivity API, and yeah, we are part of a bigger group that is working on the whole developer experience of Gutenberg. So this is just a project to improve the front end interactive parts of your blocks, but there are ongoing efforts to improve the whole developer experience.

    [00:34:04] Luis Herranz: Yeah, and maybe it’s a good moment to say that if anyone is interested in this topic, just come to the repository and so on. And contact us and join us.

    [00:34:15] Nathan Wrigley: Yeah, I was going to ask about exactly that. How open are you to contributions? Presumably any people that you can get interested in this, the more the merrier.

    [00:34:24] Luis Herranz: A hundred percent open. We need people. We need people testing these. We need people using it. We need people giving feedback. Sharing different ideas. The most exposure, the better. How do you say that?

    [00:34:37] Nathan Wrigley: Yeah, exactly that. So I guess really if this podcast serves to do anything, it would be exactly that. It would be to encourage people to go over. Read the post on make.wordpress.org, and if you’re interested and you think that you can help, then certainly it looks like your help would be most welcome. Testing, getting involved.

    In terms of what’s coming, you mentioned that there are things which you desire to have. So I guess that’s a roadmap question. What is on the roadmap? What do you want to have in there that is not in there? Don’t worry about timeframes. It might be a year off, two years off, six months, doesn’t really matter. What are you hoping that it will do that it currently is unable to do?

    [00:35:16] Mario Santos: Basically finish the Interactivity API, because it’s not finished. But, for example, our initial idea is to create the list of core directives that covers, I don’t know, 90% of the use cases, most of the use cases. Although then developers can create their custom directives.

    So for example, that list is not finished yet. We still have to ensure that the APIs work for most of the use cases. We have to finish. And our idea for this is to, at some point, include it as experimental in Gutenberg. Start testing it in real core blocks, for example. Doing some experiments there.

    Ensure that those user experiences are easy to create with the Interactivity API. Start receiving more feedback. So yeah, the idea is that. Keep experimenting. Keep developing the API. Receive feedback of users using it. And I think that’s it.

    [00:36:16] Luis Herranz: It’s going to be important the moment when we add, we added as experimental API in Gutenberg. Because that’s going to increase the exposure by, I don’t know, ten fold.

    tenfold.

    [00:36:25] Nathan Wrigley: One of you mentioned before we click record that you are going to be giving a presentation at WordCamp Europe around the Interactivity API. By good coincidence, this podcast episode is going out just prior to that. So it may be that people listening to this are very soon going to be getting in the car train or a plane to head to Athens. Which one of you is giving that talk and what is it that you’re going to be covering exactly?

    [00:36:51] Luis Herranz: That would be me, Luis. I hope Mario helps.

    [00:36:55] Mario Santos: Yeah, I will help.

    [00:36:57] Luis Herranz: It’s going to be a workshop. I don’t know if it’s a two hour workshop or two hour and a half workshop. It’s going to be hands-on. A step by step introduction to the Interactivity API and creating some interactive blocks and user experiences.

    [00:37:12] Nathan Wrigley: So very much a hands-on experience. You are going to be teaching people and hopefully getting them to learn in real time. Do you know if any of that gets recorded and put on WordPress TV?

    [00:37:22] Luis Herranz: I don’t know if workshops are recorded or not. Presentations are, yes. I don’t know.

    [00:37:27] Nathan Wrigley: Yeah, okay. So you can very much be seen at WordCamp Europe, in Athens. Hopefully both Luis and Mario are going to be there. Head over to the workshop and say hi, and get involved. If people want to reach out to either of you, be that on social media or email or whatever works best. Maybe we can go to Luis first. Can you give us some details of where people could get in touch with you, specifically around this topic?

    [00:37:53] Luis Herranz: Sure. I actually started like, I left Twitter for a while and I’m back from last week or so. I’m going to try to answer any question that people may have about the Interactivity API and to share the progress there at my personal account, which is @luisherranz, like my name and surname in Twitter.

    [00:38:11] Nathan Wrigley: Thank you very much, and Mario, where can we reach you?

    [00:38:14] Mario Santos: I would say Twitter as well. I’m not actively tweeting, but if someone writes to me, I will answer for sure. Handle is @santosguillamot. It’s a bit difficult, so maybe it’s better to include the link?

    [00:38:28] Nathan Wrigley: I will link to it in the show notes because yeah, that might be the best way of doing it.

    [00:38:33] Luis Herranz: And probably I would say come by the Block Interactivity Experiments repository. So in GitHub, WordPress slash block interactivity experiments. And then there’s, open a issue, open a discussion. Yeah.

    [00:38:47] Mario Santos: And if people don’t use Twitter, I think they can reach both of us also in WordPress Slack, if they prefer to do so.

    [00:38:55] Nathan Wrigley: I will link to both of those things as well. I will include both of your Twitter handles and both of your Slacks, plus all of the links to anything that we mentioned during the course of the podcast. So yeah, an interesting discussion about the Interactivity API. I know it’s not just the pair of you, but Luis and Mario, much appreciation for taking on this work, which hopefully in the near future will be improving, not only the performance, but the interactivity of our WordPress websites. Thanks very much for joining me today.

    [00:39:21] Mario Santos: Thank you a lot for inviting.

    [00:39:23] Luis Herranz: Thanks, Nathan.

    On the podcast today we have Mario Santos and Luis Herranz. They both work for Automattic, but are sponsored to work full-time in WordPress. The main focus of their work is the block developer experience, and they are part of the group of contributors that worked on the Interactivity API proposal.

    The Interactivity API is the main focus of the podcast today, and if you’re working with blocks and dynamically displaying data, this is sure to be of interest to you.

    We start out the podcast with the usual introductions and get to know Mario and Luis, and then we learn what the Interactivity API is, and what it can do.

    The conversation is framed around a blog post written by Mario entitled The Interactivity API, a Better Developer Experience in Building Interactive Blocks. In this, Mario shows examples of what website interactivity is. In short, it’s the ability for content to be amended on-the-fly without a page refresh.

    Of course, this is nothing new on the web, we’ve been seeing this for years in WordPress sites and elsewhere, but now you’re going to be able to create interactivity in a standard way across the different blocks on your site. The project hopes to absorb complexity and make the creation of interactive objects fairly trivial. Mario and Luis talk about examples of where the API might be used and how it can be implemented.

    We also discuss the fact that in the past developers have gone their own way to make their sites interactive. It all works, but it means that no two implementations are the same. This causes issues if the project is taken over by another developer, but it’s also a drain on resources. Mario and Luis make the point that having a standard way of creating interactivity will benefit everyone in the long run.

    We get into the weeds a little and talk about the approach the team took when building the API. They decided to use directives, and we find out why this was and what benefit it brings over other possible solutions.

    The project is still experimental, and they’re looking for people to test and report back on what they find to move the Interactivity API forwards.

    Useful links.

    Frontity

    Proposal: The Interactivity API – A better developer experience in building interactive blocks

    Interactivity API GitHib repo

    Repo for the movies demo

    Luis’ workshop at WordCamp Europe 2023

    Luis’ Twitter

    Mario’s Twitter

    Block Interactivity Experiments repo

  • Automattic Releases wp-now: A Local Development Environment Powered by WordPress Playground

    Automattic has published a new project called wp-now that creates a local development environment in seconds. The tool is a NodeJS app that is powered by WordPress Playground, an experimental project that uses WebAssembly (WASM) to run WordPress in the browser.

    wp-now allows developers to quickly spin up a new WordPress site with their chosen theme and then open it in the browser automatically logged in as admin without having to enter any credentials. It uses the SQLite Database Integration plugin for its database and developers can quickly swap out versions of PHP and WordPress for testing.

    Automattic software engineer Antonio Sejas explained how it works:

    When you use wp-now from a directory, we create a php-wasm instance, download the selected WordPress version and mount the necessary directories in a virtual file system (VFS). Then, we initiate a NodeJS express server that listens and proxies all requests to the php-wasm. As a result, wp-now can easily log you into WordPress automatically, activate plugins and themes, and automatically configure your WordPress site.

    wp-now can be installed directly from npm. It works across all platforms (Mac, Linux, and Windows). Although it doesn’t support custom domains or SSL yet, Automattic has it on the roadmap. wp-now contributors are also looking at auto detecting when a file is modified and automatically refreshing the browser, importing a database from another WordPress site, and adding a deploy feature for SSH/SFTP hosting, among other features.