WordPress.org

WordPress Planet

December 17, 2021

WPTavern: Yes, a Block-Based Version of the Kubrick WordPress Theme Exists

It is literally the one thing that no one was asking for, but we can all collectively agree it is kind of cool. A block-based version of the old-school Kubrick WordPress theme exists.

Gutenberg lead Matías Ventura tweeted a quick video of it in action yesterday. Fellow Automattic engineer Riad Benguella had put the theme together.

I am always on the lookout for those nostalgic plugins and themes that harken back to my early days on the web, the early-to-mid 2000s, the golden age of blogging. And, there is nothing that embodies that more than Kubrick, WordPress’s second default theme. It was literally named “Default” and represented the platform for over half a decade.

Even today, Kubrick/Default still has over 10,000 active installs. I wonder whether it is running on now-defunct sites or if the number represents still-active bloggers.

The theme was the face of WordPress during its rise to dominance as a CMS. Theme authors owe more credit to it than any others. It was copied, forked, repackaged, and redistributed more times than most of us will likely ever know.

Kubrick 2, as it is named in the GitHub repository, is still a work in progress. There are still a few kinks, such as single posts showing the excerpt instead of the full content. However, it is a working theme.

The shocking thing about it is how little code it took to recreate Kubrick with the block system. The original theme, last updated in 2020 and now at version 1.7.2, falls short of 11 kb of CSS. I cannot remember the last time I saw a classic WordPress theme with so little code. The block-based version currently uses a handful of theme.json settings and has no CSS.

Of course, it did not take me long to dive into the site editor and start customizing. The most recognizable design aspect of Kubrick was its gradient-blue header. It was also one of the pieces that users from around the blogging world would customize to make their site feel like their own. They would decorate it with custom colors, gradients, and even images.

Today, with the block editor, that is far simpler than a decade and a half ago. Plus, there are more options.

With such power in my hands back in 2005, I am not sure if I would have pursued theme development at all. I probably could have done everything I needed to do within the WordPress admin. Kubrick was one of my first introductions to theme design, and I owe an unpayable debt to it. It is nice to know that its legacy continues to live on.

For old time’s sake, I spent a few minutes making modifications via the site editor — ever so slightly modernizing it. However, I did not want to lose the flavor of the original work.

I am as comfortable as anyone can be in the editor. I know most of its pain points, but this somehow felt more natural than usual. Maybe it was the simplicity of a theme from a bygone era. Perhaps the site editor and I were just seeing eye to eye today. Or, it might simply have been in the cards. I had a lot of fun venturing down memory lane.

I doubt Kubrick 2 sees a lot of action in the real world. Maybe a few folks who are as nostalgic as I am will install it when it is ready for production.

Much like Ian Stewart did with Kirby in 2010, maybe some adventurous theme author will take it upon him or herself to build a modern-day successor to Kubrick. One that both leans into the block system and has readable typography. I am getting older and blinder. A 13px font size is not as easy on the eyes these days.

by Justin Tadlock at December 17, 2021 12:29 AM under kubrick

December 16, 2021

Post Status: Matt on Acquisitions and Work in WordPress — An interview with Michelle

Following the 2021 State of the Word, Michelle Frechette spoke with Matt Mullenweg about the wave of mergers and acquisitions in the WordPress space this year and their implications for employment and the product ecosystem.

You can read Michelle's and the rest of the Post Status team's takes on this year's SOTW. We've also got a community discussion hosted by David Bisset following Matt's address for you to listen to, and we rounded up reactions to the event from the whole Post Status team.

by Dan Knauss at December 16, 2021 06:20 PM under SOTW

Post Status: Post Status Comments (No. 4) — State of the Word 2021 Analysis

Members of the WordPress Community on Their Takeaways from SOTW

This episode of Post Status Comments features a live conversation in Twitter Spaces that was recorded right after Matt Mullenweg‘s State of the Word 2021 broadcast on December 14th. Bet Hannon, Eric Karkovack, Maciek Palmowski, and Rae Morey joined David to share their reactions. Others from the audience join in, including Jeff Chandler, Ryan Marks, Hazel Quimpo, Scott Kingsley Clark, Jason Taylor, and Amber Hinds.

Among the questions discussed: What stood out in the State of the Word for each of our guests? What did they think of Matt Mullenweg's take on web3, NFTs, and ownership? Was there agreement about Matt's points on WordPress market share, acquisitions, and contributions to WordPress core teams?

This engaging conversation went on for a little over an hour.

Bonus: Michelle Frechette caught Matt for a brief interview after the SOTW address, and we rounded up reactions to the event from the whole Post Status team.

Post Status Comments 💬 provides a stage for WordPress professionals to exchange ideas and talk about recent topics and trends.

Browse past episodes and subscribe to our podcasts on  Spotify, Amazon Music, Google Podcasts, iTunes, Castro, YouTube, Stitcher, Player.fm, Pocket Casts, Simplecast, or get them by RSS. 🎙

🔗 Mentioned in the show:

🙏 Sponsor: Pagely

You need durable Managed WordPress Hosting for all your mission-critical sites. 

Pagely offers managed DevOps and a flexible stack with the same enterprise-level support to all its customers. Peace of mind starts with Pagely. Try it today!

Transcript

David Bisset: [00:00:00] Uh, my name is David Bisset. I am one of the people at post status. Um, if you're not familiar, go to post status.com. It's a great community. In fact, they might as well be sponsoring this whole thing. What we do is we record, we do Twitter spaces every once in a while we record them and we make them available as podcasts.

So, um, a few rules before we get started here, as we still get a few more people coming in, um, just we'll make it very simple, prove a code of conduct. Just pretend this is a work camp. Be nice. You try to be family friendly in terms of your language and your feedback and your comments. And be be advised that this is a public space and you will likely be recorded and used later in a podcast or something like that.

If you are listening on your mobile app, you have the opportunity to request, um, feedback. We would like to, uh, like to ask if you could limit your questions or feedback to at least 30 or 60 seconds at a time. Initially that [00:01:00] way we are only planning for maybe 30 minutes or so of discussion this evening may be a little bit longer.

So we'll try to get to everyone. And I know people are still digesting what Matt spoke about tonight as well. I didn't get a chance to hear everything he said either. So we're hoping if we don't bring up some things that were covered. And if you feel like something was important that stood out into night's state of the word, then please feel free to bring it up.

We're also watching the post status slack right now on the club channel. If you feel like typing rather than talk. So anyway, um, there is a distinction just once again, we had some confusion on this last month, you can listen to Twitter spaces on the desktop that does work, but you will not be able to raise your hand or talk as far as I know you need the mobile app for that.

So if you feel like you want to contribute, switch over to the mobile app. Okay. So we have with start off with our initial four, um, speakers for tonight. [00:02:00] Um, Eric, can you tell us just a few seconds of, can you unmute yourself first of all, Eric, and tell us, um, who you are in the WordPress space in 30 seconds or less.

Eric Karkovack: I'm Eric Karch, evac. I'm a web designer and writer for specie boy.com. And I've been using WordPress for well over a decade. And this is my 25th year in the industry overall.

David Bisset: Um, Ray, is this the F, is that your first? Am I doing that? Right? There was only three letters, but I feel like, okay. Where, where are you from right now in the world? 

Rae Morey: Um, I'm based in Melbourne Australia. It's currently just after 11:00 AM here.

David Bisset: I am so stinking jealous, but go ahead. What, what published, what publication are you from?

Rae Morey: I published the repository. It's a weekly newsletter that, um, takes a bit of a deep dive into the news each week and, and kind of picks apart [00:03:00] with the headlines and what people are saying about 

David Bisset: oh, excellent. We'll be look forward to hearing some of your comments. Um, Mr. Palomo Palomo whiskey. I think I butchered that like some fine beef.

Uh, can you, uh, unmute yourself and tell us a few things about. 

Maciek Palmowski: Yes, you did a bit. Uh and, uh, well of course, when you say it that fast, it sounds better, but go ahead. Yeah. Uh, yeah, you know, Polish is, is, is very hard. So English is hard for me, but yes, but if you're from another publication as well. Yes. Uh, I am from WP owls, uh, which let's say I do at night because, uh, during the day I am a hundred percent Basadur at body and, uh, w P owls.

Uh, we also try to find some interesting things that are happening in the WordPress space. Uh, we try to [00:04:00] focus a bit more on the things that happens for developers, but of course, we also find all the news and try to share everything with this interests. Hmm. Here at night. WPLS I S I see the connection.

David Bisset: All right. Finally, that Hannon welcome to the program. 

Bet Hannon: Hi, David I'm Ben and I live in central Oregon and the USA. I run an agency that designs and develops WordPress does manage hosting for WordPress. So we have a specialization with accessibility. So we do a lot of things with accessibility, and I'm also a local meetup organism.

David Bisset: So we, uh, we have a little bit of a diverse bunch here in terms of, at least we have at least an agency owner. We have a couple of people from the news we have, and there's a lot more interesting people that hopefully we'll get to meet in the audience as well. So Eric, why don't we start with you from maybe a developer perspective, but from any perspective, what's the biggest thing that jumped out at you that Matt talked about tonight?[00:05:00] 

Eric Karkovack: Well, first of all, I was glad that he, he kind of explained, uh, you know, the whole web series. Um, topic that, you know, we weren't quite sure what he was going to say on that. Uh, we weren't sure if maybe he was going to introduce NFTs to a WordPress somehow. Uh, so I was glad he kind of, um, spoke about how that already fits in with work.

WordPress, WordPress is already doing it. It is a decentralized platform. It is, um, you know, something that you own the content of your site. So I was really happy about that. And I think the other thing that really, um, interested me was when he was actually talking about his youth a little bit about his time building B2, um, those things kind of stood out to me because he started out much the same way I did no, you know, formal education and it just did it because he was passionate about it.

And I think that's something we don't always hear from Matt. So I thought that was, um, [00:06:00] really great to hear.

David Bisset: He seemed to be a little more personable. I mean, I don't mean, I, you know, I guess I'll go next and a little bit in terms of what I thought overall. Um, we'll, I'll let you all handle the technical, but overall, maybe it was the smaller stage.

Maybe it was the fact that he hadn't spoken in front of people maybe in two years, I think he said, or maybe he, or at least in front of a WordPress crowd, he seemed to like be more happy or at least like a little bit more. And he seemed to be a little bit more, um, I don't know. I can't really put a word on it of personable or, um, maybe nervous too, maybe a little bit of that.

Maybe it could have been the most nervous. I've seen Matt out of state of the word in a long time and maybe that was because of the proximity or because of COVID or whatever. Um, 

Bet Hannon: I think it's really different when you're speaking to a small. Based versus thousands, you know, thousands of people in a big auditorium, it just feels really different when you're in front of a small audience since we, you, since we have you bet, why [00:07:00] don't you tell us what, what's the one thing that probably stood out to you the most now?

Yeah. Yeah. You know, it's actually a thing that kind of surfaces again and again for me, and it's a little bit of a push Paul. And so, uh, uh, on the one hand, I really celebrate all the ways that we are, um, making customization so much apart. And we're giving so much ability for people with little or no coding skills to be able to do these amazing things with their sites.

As an agency owner, you know, I have clients who have, you know, five or 10 or 15 content creators, and they don't want to give that kind of, they don't want their content creators necessarily going off brand for example. And so there's, uh, I'm always kind of trying to think about, uh, you know, balancing that out or, uh, thinking about how will we help our clients work with their content creators, amid [00:08:00] all of this amazing ability to customize.

David Bisset: As an, as an agency owner where you overall satisfied with what was presented tonight. 

Bet Hannon: Oh yeah. You know, uh, it's always great to hear how things are going, looking. Uh, I thought it was really interesting the, um, the perspective that Matt was giving on some of the acquisitions, but it's a, it's not just happening in WordPress, that there's a much broader kind of, um, you know, that's happening at a much larger scale and all across many industries.

And, um, so yeah, no, I, I really was pleased. 

David Bisset: So, um, our, our WP gals and our repository people here, they cover the news. They cover acquisitions as far as everything else. I'll let you decide which one of you wants to go first, but again, same question. What was the biggest thing that stood out to you during maths?

Talk the seat. 

Rae Morey: I'm happy to jump in. Um, I think, um, [00:09:00] one of the big things for me, I think, which you've kind of already touched on is the energy of the address today. Um, it was very obvious that Matt was really happy just to be around like-minded people who, like he said, I got him dancing, a jig as an animator, which he also pointed out or your case, but it was really nice seeing him so happy he's been there and vocal about how uncomfortable he was last year during the prerecording.

So it was nice to see him in front of a crowd again. Um, but I, I guess just the energy of seeing things moving forward again, after a bit of a, not a stagnant past couple of years, but things have been a bit slower with contributors being involved, I guess in WordPress has been, um, a bit of a slow down in number of people contributing to the project.

Um, And I, he was feeding off the energy in the room, as bet said. Um, I guess one of the other takeaways for me was, um, just, uh, you know, uh, [00:10:00] we didn't know what he was going to talk about, um, around web three. And, and if T's, it was, uh, you know, there a bit of speculation around what he was going to say, few ideas floating around, but it was really nice to see or to hear him talk about, you know, basically WordPress is already leading the way when it comes to web three to centralization of the web and, and ownership over content.

So it was really nice for him to address that and, and talk about where WordPress fits into that space. Um, you know, as well as the focus on open verse and, um, you know, where that's going to go in, in 2022 is, is really exciting. 

David Bisset: Oh, and Mr. Owl, I feel like I need to ask you something about the Tootsie roll pop, but I don't think the kids today will get that.

Maciek Palmowski: So, um, for me, uh, there were two things that really stood out. First of all, uh, when he mentioned the number of, uh, people doing translations and the languages in the repository, uh, because [00:11:00] I am a non native English speaker, which probably you can hear with my thick accent. 

David Bisset: I think it's cool. 

Maciek Palmowski: Thank you. Uh, but um, I know how many people in Poland, for example, need to see their CMS in, in Polish because English, it's not something they want to, they want to read some, some of my clients that I had don't even knew English or just didn't felt comfortable with it.

So, um, the, the growing number of polyglots, this is really something great. And this is really a thing that, uh, Um, that will really make WordPress bigger and bigger. Uh, w when we confronted with, uh, other CMS is out there because most of them are still mostly created and maintained [00:12:00] in English. So this is something very important.

And there was one sentence that was also very intriguing for me. Maybe I, um, I misheard it, but I thought that Matt, at some point mentioned something about breaking a bit, uh, how he called it, that backward compatibility. Yeah, he did. I remember him talking about that, what specifically thinking of exactly.

And this is, um, I know that he mentioned it, uh, in the, in the context of, uh, in the context of themes, maybe, maybe, and this is. A bigger step to some bigger changes in, in inside of core, inside of, uh, uh, of, of, uh, of the coal tooling and stuff like this. So, uh, really Matt saying, let's break the [00:13:00] backwards compatibility.

This is something huge. 

David Bisset: Did he say that though? Break? I remember I may have missed that quote. 

Maciek Palmowski: You mentioned something. I mean, it wasn't, uh, as the size, if it's let's break that backwards compatibility, but in terms of WordPress, when we, I would say we have a bit paranoid, backward compatibility, which is great in some cases, um, Talking about breaking any backward compatibility is something.

David Bisset: Yeah. Matt did quote, this was a quote in this again, take, take in context and keep in mind that, you know, we'll listen to this again. And again, probably a few times to get a better understanding of what was said, but he did say in the presentation that a theme that was created with like an early version of WordPress, will it be like 1, 2 0 1, 5 or something like that would work with WordPress 5.9 next month.

That is what he said. And that's his, and that he said, quote, that's how serious we are about backwards compatibility. [00:14:00] Um, but like we said, that I would have to go back and listen, but I know, I know at least currently has strengthened backwards. Compatibility seemed pretty strong, at least from that statement now, whether or not it stays that way.

Maciek Palmowski: Um, but I think it was a sentence before, when he mentioned that. The developers should move from the old editor to the new one. So we should update. So this is something, uh, but, uh, yes, I, like I said, I wasn't sure about this, but, uh, it caught my attention. So I think that, uh, yeah, I will have to relisten it once again to, to make sure.

David Bisset: So we'll let, we'll let that, uh, bet chime in here and then I'm going to open before you start that. I'm good. Then after you, I'm going to open the floor a little bit of a few other people who are going to raise their hands and we're going to keep everyone on stage though. So you can keep interjecting back and forth.

We're not kicking anybody off. I'm sorry. Go ahead. 

Bet Hannon: I might be wrong, but I think that Matt was referring to the breaking the backward compatibility in terms of the introduction of Gutenberg that the Gutenberg would break a [00:15:00] backward. That that would not be backward compatible as we move forward with blocks. Well, I might be wrong.

David Bisset: Well, I don't know about you, but some of my old themes won't work with flux gear guaranteed. Yeah. And, and the old editor things in the old adage that use that tiny MCE editor are not going to work. And so there's some backward compatibility that is broken with the introduction of blocks. So, um, all right.

Uh, Jeff, welcome to the show. Welcome on stage. Um, Eric Ray, Brett, and Mr. Owl. I'm going to refer to him as, um, are still on stage with us and are going to interact with anybody we bring up. Can you hear us, Jeff? Uh, absolutely I can. And Ray, you have an awesome accent. Thanks for that. She has, she's also in the morning too, so she's got that.

Perkiness that currently very few of us have right now, but oh, I have a coffee. So I'm doing well, sorry. You're not making me [00:16:00] like you in any more, right. Uh, so Jeff, what for the, for us up here on stage and for the rest of the audience, what would you like to share about what you heard.

Jeff Chandler: Um, I, you know, I think people on the, in a web three space might look at what Matt said on stage as him maybe Disney web three.

But I think what he did was he cautiously tiptoed around the subject. He brought it up, he skimmed the surface. So I think at the very least people know that he's aware of it. He's going to keep his eye on it. And it may come up again in next year's state of the word, but I don't, I think you did a good job with bringing it up.

But one of the things I also enjoyed that he brought up, I'm glad that he brought up was when he went over the market share numbers. And this is something that Yoast EVOC did in his CMS market analysis posts is that he talked about how software as a service company is Wix Squarespace. And, uh, some of the other ones they're all rapidly growing and all of the open source solutions minus WordPress are losing.

And I was glad that he brought [00:17:00] that up and that's something that we should keep an eye on. Uh, here in the next few years, 

David Bisset: He also said something interesting too. About, and this was in a different part of the presentation, but regarding Drupal and Joomla, I got him quoted as saying he thought they would be more successful if they had apps, which I thought was interesting.

Jeff Chandler: I, I thought, I thought they had the apps, but if they don't, I think that's a very valid point.

David Bisset: Yeah, that's true. So market share was definitely something that, that brought up 43%. And I won't go into it now because it's not relevant to the state of the word precisely, but wean very soon because of an Amazon shutting down, Alexa, we may not have the privilege or the opportunity to have percentage of market share numbers like we do today, so that, you know, examining this information now for Matt, I think during the state of the word is very important because without those are W3C texts, numbers are based on Alexa and Alexa is shutting down in, I think may of next year, Amazon shutting it down, not that Alexa, [00:18:00] the other Alexa, and I'm just turned on a bunch of Alexis and people's houses.

Jeff Chandler: And one of the last things I'll say here before I get off, is that I think it's obvious that 20, 22 is going to be the year of the open verse. 

David Bisset: I, I can't, I, every time I think of open verse, I think of something else and I hate myself every time. I think of that associate, thank you very much, Jeff, for, for sharing with us, Scott.

Um, let's see. We're inviting Scott upstage or SKC. I think he likes to, I think that's his rap name. 

Scott Kingsley: Hey, what's up? 

David Bisset: What's up?

Scott Kingsley: Let's say Casey, you know me? 

David Bisset: Oh God. He started her up already quickly before, before he does tell us what you thought of tonight. 

Scott Kingsley: Uh, the 

lack of banana milkshake representation, it was kind of a disappointment, but, and wanted to run that operation banana milkshake failed.

David Bisset: It was fine. Nobody knows what we're talking about.

Scott Kingsley: Oh, one out, but, uh, availed on asking the question. [00:19:00] So, cause he got up right near the end. I was like, oh, come on. You can get, you can get the question in there. But uh, I thought it was really interesting. Um, well obviously. I think web three is a whole thing, but I'm really glad that he brought it more towards like reminding people.

You need to remain cautiously optimistic about things and keep things open. Um, especially from the perspective of making sure things are, are done right. And you're not watching hucksters and stuff, but, um, but I think maybe the part I really liked the most was probably all around how, um, collaboration is phase three and we're, I know we're still a year out now, but, uh, if we could have gotten to that in 2022, I think that would have been a pretty big thing because there's so much about the collaboration idea of just like going into, um, uh, Figma or Google docs and you seeing everyone else were working together and, and just that collaboration aspect of things could make things so much easier, especially on the open web, we're trying to replace something like Google docs, [00:20:00] having an experience like that inside of WordPress and being able to collaborate like that would be pretty, pretty.

David Bisset: Yeah, I wish I knew more about it in terms of, um, he did say he was going to talk about web three and he did say NFTs in his blog post, but I don't think he said much about it unless I missed that part. I think he was just putting a bunch of keywords together. Um, yeah. Um, but he did make it a point to kind of bring up the larger issue about what those individual things stood for, at least from a philosophy philosophy standpoint, what you hear on the web in terms of, um, ownership.

And I'm drawing a blank on the other things right now, but he did really kind of go into why WordPress was representing those things. And he did make a point that you can overlook some of the things that are the WordPress has four freedoms can be overlooked if you focus too much into some of the, I don't think he used the word hype, but I think he meant something like it.

So [00:21:00] there's a danger there overlooking what he thinks are the critical freedoms to WordPress. Eric, did you have. 

Eric Karkovack: Yeah, I think he was also talking about decentralization a little bit with that. Um, just the basic idea that, you know, you can take your WordPress website with you to any host. Um, maybe it doesn't fit in exactly with like something like blockchain.

Um, but it does kind of speak to, you know, the danger of going with, uh, you know, his favorite, uh, competitor Wix. I think he said that WordPress grew by two Weeks's over the last year, which was kind of a good line. Might have been my favorite of the night. I, I have a, I have a little chalkboard up here and every time he made a mark a comment about Wix, I drew a line and I've got a couple of lines here on the board, but yes, he did make that comparison.

David Bisset: Go ahead. 

Eric Karkovack: Okay. I just going to say, I think that, that, um, you know, having that ability to move content from place to place is what's going to [00:22:00] separate. WordPress from everything else right now. I mean, as we see Joomla and Drupal dropping down well, WordPress is kind of like the last bastion of hope for open source at this moment.

Maybe. I don't know, like see what other people think about that 

David Bisset: You need to write a transformers movie.

 That was excellent.

Eric Karkovack: Well, I, I think, you know, if, if, if that's the case, then you know, that's going to be the big selling point. Um, I actually had someone in my family wanted to start a blog this week and I pushed him to WordPress and not to Squarespace or Wix, because if you don't like the service, you're not going to be able to just take the website with you.

It doesn't work that way. 

David Bisset: So let me let, speaking of that, um, let me ask a broader question. Cause I get a feeling we're going to boomerang back to the web three stuff anyway. Matt said, and this question goes for everybody on stage or anybody in the audience. Matt did say a quote later on in his, um, I think in his Q and a about, he said that, um, [00:23:00] 85% or some big percent of the web doesn't really care about it was either open source or owning your own content or something along those lines that most that WordPress would have in order to be usable.

WordPress would have to be a great user experience and WordPress will be invisible to those people. And that's okay. Does, what does anybody think about that? Do you agreed, or do you, do you think that number is larger or smaller or does that seem to gel with your philosophies and your observation?

Bet Hannon: That's true for a lot of people, they think they just, you know, uh, they just want to get the website up and they're really, uh, a little more platform agnostic. They want to know. Is it going to be hard? Right. They want to know about ease of use. They don't, but they don't really care that it's open source for not.

David Bisset: Jeff, what do you [00:24:00] think?

Jeff Chandler: Uh, I think for a lot of people that way, he said in terms of like maybe one or 2% of the people who understand TPO and its freedoms and what they mean, uh, those are the people, very, very small percentage of people. Uh, you know, it be an open source is not the concern. It's how to get the aid to be the fastest and the easiest.

And you, that pretty much explains why a Shopify and somebody software as a service solutions are growing a market share because they're providing a great user experience for a lot of people out there to get from a to B quickly and easily. So I think it was a nice for Matt to bring it up and saying, you know, if we're going to, uh, become the dominant player and get open for some more hands that even if it means that we're presses invisible.

David Bisset: That's okay. Yeah. I think that's reasonable. I think that's a little hard for some of us to like we accept on the surface, but I think some of us have to kind of dig down a little bit and realize that some of the things that we're passionate about us, not what 99% of most people passionate about. You know, they want something that works.

Ray Ray, uh, did [00:25:00] you have something to say, and then I'm going to bring in a new speaker?

Rae Morey: Yeah, no, I'd absolutely agree if you're running a small business, you know, like my hairdresser, for example, she just built a website recently to support her new business and she's, um, using, um, GoDaddy, um, and they're, you know, website builder, and she built a site in an afternoon really easily with WordPress and, you know, people like that, they don't want to muck around with something that's really tricky to, to work with.

They, they wanna drop in their images or their content and have their website up and running with in her case. E-commerce as well, really quickly. And, um, you know, it's important. Um, platforms like, you know, it's not all about, um, WordPress being the center of attention in, in that space. It's, it's about elevating the user experience and making sure that users, um, can, um, have the tools they need to run their business without WordPress necessarily being front and center.

Maciek Palmowski: And, um, [00:26:00] I wanted to mess one more thing because when the whole COVID madness started, many people realized that their business needs a website. Right. And you all remember that this was the moment. Uh, workers had a much bigger amount of downloads. WooCommerce was downloaded the biggest amount of, uh, of times.

And this was because first of all, workers was kind of popular. So people were able to find materials about how to insulate, how to create their first e-commerce. So they could, so their business could work during the pandemic. And it seems that WordPress was easy enough for them to just start to make their business round during those, uh, those hard times.

And probably during the process, [00:27:00] they started to. More and more things, how to optimize some things. And some of them learned probably a finger to about, uh, about C, about search engine optimization about performance and stuff like this, but still, uh, we saw how many businesses started their websites on WordPress, because it was easy.

It was free. 

David Bisset: Yeah. Free. In fact, a real Aruba hope. I probably butchered your name in the chat. She says, I think for a lot of folks open source means free in that vein for some folks, open source also means hard to install. And she says, when I pitched WP, I rarely talk about the open source aspect. I talk about the ease of use security, constant updates, et cetera.

So, you know, playing to the strong, playing to the strong points there. If it's okay with you, Mr. Owl, I liked to switch over to Hazel. Who's been waiting patiently. Hopefully she's not mad at me. 

Hazel Quimpo: Hi. I don't get mad. Um, [00:28:00] quick. No, I mean, I think I'm on the same page with a lot of the folks is like, I don't know.

I think of like travel agents, right? And I feel like we're at this stage where, you know, you used to go to a travel agent to get all your stuff. And I think if you have a really small website, you don't need to even go to like your cousin. Who's a WordPress developer. Well, you might need to today. But I think that the expectation is you shouldn't have to.

Um, and I like from the lay person who doesn't know about WordPress, who doesn't know what, whatever they think they should be able to go and set up their website and frankly they can. And I think that's where we need to realize that's where the people, I was recently looking at tons of web hosts. And so many of them tout like image compression.

And do you know how many people I know that start businesses every day, who care about image compression? Like zero to say a lot, but I guess I was way wrong

for touting these things. Expect. And I think we need to realize some of that when we do WordPress stuff is like, cool. Like we do believe in the open source nature of the things we believe in [00:29:00] owning your content. But I view it a lot of the way. Like, you know, my doctor tells me to drink less and eat healthier, and I think that's a good idea, but I don't care that much.

And I think that's how the rest of the world is right. And Hazel, for as long as we have you in the living, as long as we have you in the living world. 

David Bisset: Thank you for, thank you for that. Um, I'm gonna put, I'm gonna put you back into the audience, but for the love of God, please don't disappear right away cause you're scaring me now. Um, stick around please in the world that we're living and in our, in our little chat room here, Dave, Ryan, um, you're onstage. Welcome to whatever we're calling this little freak show. How are you? Apparently Dave's a quiet person. That's fine. 

Dave: Sorry, Twitter space is cut out there for a second.

David Bisset: No problem. Real quick. Tell us what you thought of that. What, what stood out to you or what did you, or maybe you're responding to someone else's comment? 

Dave: Well, I guess on the current topic, I think of WordPress. You know, if we look at [00:30:00] automobiles, there's a lot of different ways to get where you want to go, right?

But WordPress is ideally these sort of Toyota Camry, the undeniable, you know, lay person, car that anyone, you know, that almost just blends into the background, but is everywhere. And you live where I live with. But also, you know, like the Ford transit van, if we're looking at blue commerce, the thing that every business needs to get, where it needs to go and, you know, it can be customized.

Um, I guess the one thing that really stood out to me about the presentation today is just kind of the talk about the open verse photo directories, digital art, the project doesn't really have an apparatus today to do content moderation at scale. And I'm not sure that that's something that volunteers could really easily be asked to do.

Um, you know, once you create a way for people to easily express themselves, you also open up, you know, copyright [00:31:00] issues, uh, hate, um, questions about what's decent and what isn't, and you have to navigate a global web of legal frameworks or. So I think as excited as I am about those ideas, and I think it's a great opportunity.

I also think that Twitter and Facebook have proven that money and AI don't necessarily solve those problems. And so I'm just curious how the project that going forward. 

David Bisset: That's uh, I would, I would say that too, Adam attempted to ask that toy. He did ask it, um, or attempted to address that as well. And I'm, I'll, I'll be honest with you.

I don't know much about now there was a distinction between the open verse project and the, what was the other thing? Was the WordPress photo project or photo library? Something, um, I'll admit. I admit I, I'm not really good in depth on both of those, by the way. Did I mention, I worked for post tennis? Um, But I, yeah, so there was definitely talk of like, if you uploaded a [00:32:00] photo somewhere with that data, some of the data that sticks to it, you know, like how you upload a photo, like if you upload a photo to Twitter, for example, from your phone on your phone, there's metadata attached to that photo.

And when you upload it to Twitter, it's gone. Um, but that's just, that's just one level. And what you're talking about is the, what hits the news a lot, like in terms of, you know, you could be posting photos without people's permission, or you could be posting hate speech or that sort of thing. So, and we all know that's a moderation nightmare, right?

Guest: I think today, the ways that we contribute to WordPress have a steep enough curve and our barrier to entry that we don't deal with as much of that. But I think the big question is going forward as we make it radically easier to contribute, how are we going to tackle the problem that all these other networks have had to deal with once they scale.

David Bisset: That's an excellent question. I feel like I'm still at the Q and a part of State of the Word. I really, yeah. Subtly we should, [00:33:00] we should get that question in front of Matt and some other, some other people's. So I think that's an excellent question. Dale has decided they don't have a really good answer.

A thought about that. Thank you though, for, for speaking up. Um, so one of the other things that was spoken about here, and I get a feeling this was in, in an inescapable gravitational force in 2021 was acquisitions. And we mentioned this briefly. Um, do you agree, does the, is there anybody here that maybe sees Matt's point, but has a different opinion in terms of this is I think it's, I think the point he was getting across was this is happening everywhere.

It's not just in the WordPress space. Is that, is that generally something that you would agree to? Um, the way he presented it, especially with lots of nice old charts. Does anybody have an opinion on his take on acquisitions?

And if I can take a silence as a yes. If anybody wants to, [00:34:00] I, I can, uh, chime in, I guess. 

Jeff Chandler: Um, I think one of the things he mentioned, he mentioned Yost by name, and I think he also talked about, you know, the number of employees and what they're doing and kind of extrapolating the impact that, that accompany like that has like all the millions and millions of websites that are like, just for example, running Yoast right now.

Um, and I think he's what he's kind of getting at is that there's a lot of responsibility in that. And for a lot of smaller entrepreneurs who started out with these plugins. You know, maybe that's just getting to be to a point where they're just not able to do it anymore. I know that was part of the, the case with advanced custom fields from they, they were sold, um, you know, it was a one man operation with a user base in the millions and, you know, kind of how do [00:35:00] you, how do you manage that?

How do you continue to, to support it and build the product at that scale? When, you know, you're just a small group of people or even just an individual. Um, so it's, it's a matter of WordPress is growing so radically big and you can't be a one person team, especially on something that large sure. Seems like it these days.

I mean, I I'm, I don't doubt that, you know, individuals are still gonna come up with amazing things, but to compete at the level of a Yoast or an AC. I don't know how that's sustainable for a long period for such a small group of people.

David Bisset: Well, I think that also, and not to get off track here because this isn't, I think Matt didn't mention this at some point directly cause he ma he brought up the CD comic about, um, about it there's I tweeted [00:36:00] it, but I'm looking, I'm trying to look at the picture right now.

It's basically about picture a all modern digital infrastructure being a giant castle. And there's this one little piece of the bottom that says a random, some random person in Nebraska, thankfully maintaining a project since 2003. Um, that, that is kind of also the same problem, in my opinion, in terms of like, it is this, there is a strength of open source and yet there's this weakness.

And I think this week two, if anybody's been following the news about the Java exploit that came out on Friday, who's named now, I'm not remembering logs. Um,

Guest: log4j

David Bisset: yes, that's, that's it. So we're beginning to see these things happening outside of WordPress and open source that we've been kind of contemplating now for quite some time, whether it's bugs, whether it's something that needs to be addressed in terms of open source manpower, or woman power human power, or it's a, like you said, Eric, it's an acquisition thing you absorb, somebody gets [00:37:00] acquired because they can't physically maintain it on the same scale anymore.

Um, did that did accurately that I accurately represent you there? Eric didn't mean to? 

Eric Karkovack: Oh yeah, absolutely.

David Bisset: Okay, great. I've got uh, oh, Ooh. We've got an entire company on the line right now. It's Pagely so this, this should be interesting. Pagely uh, who specifically inside page? 

Dave from Pagely: It's Dave struggle as I'm probably having dinner right now.

David Bisset: Bless his heart. Go ahead, sir.

Dave from Pagely: Well, it's great to see us on the big board with the acquisitions. It's been quite a month for us. We've been part of GoDaddy now for a little over four weeks, and I want to dovetail something that was said earlier, which I tweeted a Jeffer a second ago. Um, we should be concerned about closed source platforms gaining in popularity, um, because none of us want to see the depth of the open web, right.

And it's great to see or press with the market share that it has. And you know, when everyone kind of says we need to get online, what's the first thing I think of is usually [00:38:00] WordPress, which is great. Um, Well, we've been brought in to build with GoDaddy is this next generation of, of an open source commerce product on top of WooCommerce.

And that gets us excited because that is open source. That's going to be built upon this platform and not, you know, going the way of, you know, Wix or Squarespace or any of that. So, you know, we're, we're still kind of committed to that, making sure everything is open source and that the open web doesn't go away.

David Bisset: Hmm. Okay. Well, send a thank you very much and thank you for being a recognizable P avatars. I could quickly point around right here. Thank you. I mean, oh, sorry. Sorry. Going through a tunnel, going through a tunnel right now. Sorry, I can't hear you. No, we'll, we'll keep you on. We'll keep you on the stage a little longer.

Um, Ryan, welcome to the party. Do you, did you have a comment for the group, Ryan? I [00:39:00] think that's Ryan mark. It is. Yes. Okay. Ryan, welcome. Welcome to the show.

Ryan Marks: Oh, well, thanks. Uh, the, the graphic that you were talking about and the person in Nebraska reminded me of the recent news with the PHP foundation and the fact that there was a bus factor of two, uh, with respect to how many people actually knew the code base, according to articles.

And, um, I just thought that was somewhat similar, right? 

David Bisset: So, yeah, so I'm, so this was all coming to the original, um, me bringing up the acquisitions part of it. And some of it is the acquisitions that especially, I think it absorbed the one or two people. The small companies are, are probably doing WordPress a favor in some regards in the long run, because otherwise, like you get hit by a bus, what happens to advanced custom fields, which a lot of people rely on, uh, I think Matt presented that pretty well in terms [00:40:00] of, um, the numbers and some people, some people have different opinions about what is happening in the WordPress space, but there is some validation or some validity of taking a step back and looking at the largest.

There was one bar graph and I'll be honest with you. I'm not really that business oriented again. I work at post status. Thank you very much that on 2021, a bar graph just like shot the way the heck up. I think it was the, um, think it was, it was, it was something about the money that was, that was being transferred at hand-to-hand or something along those lines.

Um, it's just 20, 21 just basically exploded for the rest of the tech industry. And WordPress is a part of that tech industry. So it's not just WordPress and, but at the same time, I think WordPress has its own valid reasons for why it's happening. There were 42 logos on Matt's slide. At one point we have a WordPress acquisition tracker.

I posted a sock hops last acquisition. So I'll have to go back later and see if all those logos are. Otherwise, I'm not doing my job. Um, what [00:41:00] else did we, oh, bet. Did you have a common rule? 

Bet Hannon: Well, I was just gonna say, I think some of the acquisitions or, you know, the pandemic really caused people to just stop and think a lot more about quality of life.

And, uh, you know, I think sometimes you stop and you take a look around and you say, I think I want to move on and do some other things, or I think I've done what I can do here for now. And so some of that can be there. And so I think in 2021, you know, that that's a piece of more, more broadly. A lot of those acquisitions happening is just people thinking differently about what they want to do.

David Bisset: There was a good comment made on another podcast of there was, um, if you look at the big tech, big tech companies, now that started maybe 10 years ago, um, Amazon's founder is no longer with the company he's off on rocket ships or something. Um, there's the, the original founders of Microsoft are long, no longer there.

The founders of Google are no longer there. Apple's obviously [00:42:00] had new leadership. The only person I think running the same ship they have for awhile has been mark Zuckerberg at Facebook. So all of these people have moved on after a certain period of time and they've done it all within a relatively short period of time.

I think Twitter has been the latest one where Jack Dorsey just basically stepped completely away and he's off following his next adventure. Other people have just basically retired. So it's not just about the money in the, in the, in the acquisitions, but it sounds like to me, people, you know, you can, if you, if you're really successful, you have the opportunity after 5, 6, 7, 8 years to say, maybe I want to do something different.

Maybe. All right. Um, Jeff, can you, what do you, what are your thoughts? 

Jeff Chandler: I, in and talking about the acquisitions for a little bit, there is kind of like two separate topics for getting conflated with each other, between the five for the future and an acquisition. I dunno, I was getting little confused, but I think [00:43:00] the whole fight for the future initiative, I think is going to take on even more important as we go forward.

As we look at open source maintainers and the bus factor of two and open source is seen as something that's free, but there's people behind it. There were people putting in time and work and effort and the passion, and it can only go so far and somebody is going to have to flip the bill. And I'm looking forward to ma maybe putting like an executive director or somebody in charge of the five for the future initiative and get that out into the public's eye more often because outside of web dev studios, uh, advertising what they're doing and how they're contributing, and then some efforts from GoDaddy and 10 up, I mean, it's kind of like a behind the scenes thing, and I'd like to see more effort on making the whole fight for the future thing, uh, initiative, go more public, get more people involved and get more people to know about, especially companies.

David Bisset: Oh, okay. Sounds good. Sorry, [00:44:00] Jeff. A bucket, a bucket of chicken wings just went by my field of view and I got distracted for a second. Courtney, um, Robertson, let me add you as a speaker here. Um, after this, I want to talk about the next generation of WordPress users, which was part of the Q and a at the end there.

Um, and what we might think might be our thoughts on bringing in, or people attracted to WordPress for the first time, especially the next generation, but Courtney, what do you got for us? 

Courtney Robertson: Hey there. So, um, one, we saw Andrea and Middleton lurking in the crowd, and I just have to say, I am so glad to see your face popping up and we all miss you as we're talking about five for the future, 

David Bisset: let's do a show just about her.

I think that would drive her. I think that she would love it.

Courtney Robertson: I think so. So did anybody else notice piggybacking off of what Jeff just said, but the very last thing that Andrea wrote to the WordPress community, aside from a fantastic series of posts on her own site, you [00:45:00] head over, if you head over to make.wordpress.org/project suggested iterations for the five for the future program and the tool, um, and ways that we can perhaps reinvision what five for the future could look like from this point, moving forward, how to.

Do a fantastic job at connecting the five for the future initiative, with the various teams. Um, there are things in Andrea's post on the project about the pledges to the different teams and ways to get more connected, partnering up the talents of those that are able to contribute with five for the future, with those in the teams that need to have stuff happen to get work done.

Um, I wanna say that I participated in a number. I want to say five probably contributor days over the past year on behalf of the training team, all of these being virtual summit attached to a word camp, [00:46:00] some as part of the translator day, which was really a month and a few other kinds of things. Yoast did a fantastic job at partnering the various folks with different sets.

And reaching out to the various make teams and saying, w we have this day coming up, we're going to break into, um, a hybrid partially online, partially in person break into different groups and get to work on different things. What are some of the tasks that we can look at? I think when we look at five for the future, um, you know, my employer go, daddy has been amazing at helping fund through five for the future fund.

Part of the word camp events that we see happen, um, sponsoring some other great places like post status and other things, too. But as we're, as we're looking to the future, I really am excited around doing contributor days through post status, inviting all folks that are in [00:47:00] post status and the wider community.

To get connected and similar to how Yost has done it. And perhaps in conjunction with Yoast, we'll see in the very near future. Um, but connecting with the various team reps and connecting with the teams that have needs and saying, let's match up these skill sets of the talent that we've got in our company and the things that need to happen.

And also simultaneously open that thing up by calling in the wider WordPress community, because across the teams, teams are really hurting during COVID not only can we seen the attendance of things like bird camps and all of the setback, uh, you know, a number of years comparatively in the stats, but across the teams were hurting to have.

Contributors that are showing up to actually do some of the work on the teams. And there's a lot of talent and a lot of interest in what's going on. So, um, I just, I love the posts that Andrea left us with. I love that Andrea is in the room right now. I loved the, [00:48:00] we could do a five for the future contributor day series through post status.

So quarterly ones that will probably be hybrid. I welcome anyone that would like to help organize something like that, um, to connect with me over in post status. Oh, well, thank you very much. And, um, I'm sure Andrea is very honored. Um, I'll speak for her a little bit here. Um, yeah, so obviously I'm a little bit biased.

David Bisset: Cause my daughter was mentioned. I don't think she'll be in the witness protection program anytime soon. Thanks to tonight. But she was absolutely absolutely thrilled, but she's not like, but I don't. I want her to be more like blending into a larger crowd of younger people that are running their own hackathons or they're doing their own thing within the comforts of, you know, being even mildly associated with the pro WordPress community. Even if they're not sitting down to crew to quote unquote directly contribute. Um, um, Amir, I think, do we have you [00:49:00] back on now? Can you say something, let us know that you're still alive.

We might be having some difficulties, maybe your Mike's not on or something. I try and again here. Um, yep. Oh, you're muting yourself on and off. Are you, is it Morris code? I see a blinking. Nope. All right. I'm going to leave you on speaker for a second and then I'll let Ryan cut into here, Ryan

Ryan Marks: . Um, so I had a question for those that do pledge five for the future.

Do you feel that you do it primarily with people man hours, or do you do it with dollars or is it a mix? Do you feel like you actually get the 5%, if anything, or is it more, we try to get something close. I think that has her hand, right? So we do fight for the future. Um, I don't know that we calculate it, but you know, certainly, um, you know, [00:50:00] I contribute my time.

Bet Hannon: Um, and then our, our agency subsidizes our people as they, you know, they can, they can put in, uh, you know, time that they're doing community work and get, um, get paid for that. Um, as a way that we try to support the wider community, I think that's just a part of, you know, my wife is an economist, so I understand that tragedy, the commons, uh, example really well.

And I want to make sure that the ecosystem stays supported. And so that's, that's a really, you don't have to be really big to do those things right. To, um, to, to make a difference. Uh, but I just feel like that's an important part of what we do is for the community. 

David Bisset: All right. So as we start to run down here, cause.

Did promise, uh, it promise someone I would be home in time for bed. I do. I want lot of stall all us to think about a maybe if, if there's any final comments you had about what Matt talked about or Matt's comments about uni questions or about how that [00:51:00] fits in with your version of WordPress in the future.

While you're thinking about that, let me quickly get, um, Olivia on. I think she wanted to make a quick comment.

You're muted. Olivia,

maybe we have a maximum number here. Maybe it's why this isn't working. Let me remove a speaker. 

Olivia Bisset: I can speak

David Bisset: Sorry, go ahead. What's your comment listener. 

Olivia Bisset: Okay. So with five for the future, I don't know what, but it just got the general vibe that that's starting to head towards, like, okay.

Yeah, we got people now, but like youth, I feel like there was more of a youth focus. This state is a word, especially with the question from Allie and others. I don't know. That's my 2 cents. 

David Bisset: I thought Allie gave an excellent question and [00:52:00] that was followed up by others as well. Um, and we'll have to go back and review that because my memory is beginning to fade a little bit, but I thought she had a very excellent question about what Matt thought the youth, um, what his advice to you would be regarding how to use WordPress for the next generation.

So, um, let's um, let's take one more comment from the audience here and then we'll see if we go around. Anybody has any final thoughts, Aaron Edwards, um, welcome to whatever we're calling this. What, what do you have to share? 

Aaron Edwards: Uh, hi, I'm the co-founder of web three WP. So of course we are very interested in what Matt had to say about web three.

I thought it was a good kind of balance, like opinion, like, like Jeff Rose said, um, just the fact comparing WordPress to kind of some of the ideals, uh, web three, I think that was kind of a good tact that he took, but it was interesting just discussing in our community. It's like, it does follow like those ideals of data [00:53:00] ownership when you're the site owner, but it doesn't really address the site users, which is something that web three is kind of known for you.

It basically allows you, WordPress allows you to create your own data silo, you know, to maybe compete with the Facebooks or whatever centralized apps there are, but it doesn't necessarily empower users to continue to have your site on their own data. So that's kind of a interesting take that I heard in our community.

David Bisset: Interesting take at that sounded like I haven't heard that take exactly like that before. Uh, well, I kind of wrote that same thing on our website, but, oh, would you mind sending a link to that in post at a slack or wherever your finest links are sold?

Aaron Edwards: Yeah. The web three wp.com pages talking about WordPress being, um, kind of along those ideals, but definitely it was, it was interesting to, to hear his take in that, uh, another thing he kind of made a joke about dowels and [00:54:00] domains, um, which kind of seemed like disingenuous to me personally, because I've had experiences where I've had domain registrars, uh, shut down my domain because someone filed a false abuse report, you know?

So it's like that's renting. That's not really owning. As he kind of made it out to be okay.

David Bisset: I can see that point. Absolutely. And hopefully I won't have anything shut down on my side Verde, but thanks. Thanks for sharing and feel free to ping me in post status or on Twitter. I'd like to get that link from you.

All right. So, um, it's been about an hour. Um, so I wanted to, um, I did make, uh, wanted to see if anybody else has any last comments. Um, either somebody who hasn't spoken yet are part of our, um, ongoing panels here, um, that I know you wanted to share. Something felt like a last lot quickly with us, and then I'll nail a few other people that didn't sound right in my head.

But go ahead and you under, do you [00:55:00] please take it, please take the mic from me. 

Bet Hannon: Yes. Um, so I'm a little disappointed that Matt didn't say more about accessibility. And the times when he talked about accessibility, he really meant it in the terms of just making things available to people, uh, like features available.

Um, but you know, we didn't talk about web accessibility and we we've had some issues with that. Um, in the past, things are better than they were, but we still have a long way to go for web accessibility, especially in the WP admin side, in the dash, in the backend side. So Amber Heinz tried to call out Matt earlier in the week, uh, just to try and get him to speak a little bit more about accessibility, but he didn't so well, his slides were probably already written by then too.

David Bisset: I don't, I'm not going to speak for them 

They said they were editing them 

Bet Hannon: up to the last minute. 

David Bisset: I know what that's probably true too. I can't speak to that, but no, he did mention it, but I'm getting a feeling that for some people who wanted him to mention accessibility of may not have filled their cup to. [00:56:00] It's an important piece and growing in importance.

Bet Hannon: And so we have to pay attention to it if we want to keep that market term. Yes. Because like he said, we're pressed should be like, for most of the people, WordPress will be invisible. Right. If the, if the user experience is done. Right. And would you bet, um, I know you've said many times that part of the user experience is what, well, it's gotta be accessible.

Right. And it's gotta be, um, and as we're increasingly in the us having some, um, legal pieces where people are going to be required to have their sites accessible, we we're gonna need to be ready for that. Um, so we can help people do that. 

David Bisset: All right. Um, speaking of Amber, I think we said her name three times.

She's appeared. Um, we'll get right before we get to Ryan. Um, Amber, did you want to share something with us? I'm guessing you want to share something that starts with the letter a and it's not your first name.

Amber: Uh, not Amber, uh, accessibility. Yeah, I think, I think the thing that's interesting too, I [00:57:00] actually got a couple of messages from, um, some users after they read, you know, the thread and conversations and in process.

And I think maybe the contribution to core accessibility, the people on the accessibility team, particularly maybe some people that have disabilities that are part of the accessibility team. Probably I think there are some of them that feel like it's still not as positive or as central of a focus as it as maybe Matt kind of thinks that it is.

Um, I think it still is a lot of an afterthought and really that's, you know, one of my hopes that I'm really would love to see more. Thinking about accessibility as something you do at the beginning, not something that you do wait around at the end of the process, whether it's in core or whether it is, you know, in plugins or themes or on the front end of the end websites, [00:58:00] let's start at the beginning, not in the middle of the end.

David Bisset: It's like how I should do most things in my life, especially the chores around the house. Thank you, Emery. We did see a lot of this stuff in accessibility mentioned in post status too. So we've been following that as well. And thanks for speaking up here today. Really appreciate it. Okay. Let's let's go through the rest here.

We're going to be ending shortly, but Ryan, you are up next. Um, what closing remarks do you have for us?

Ryan Marks: So three things caught my attention. Uh, and then I'll hang up and let you guys talk about, we'll just pretend you're not here. I can remove you as a speaker.

David Bisset: You don't have to hang up, but we can ignore you easily, but go ahead.

Ryan Marks: Um, I thought that there was an open invitation for up to 50 people. So I tend to stand in the word, but then later it seemed like there were about 30 people there, there were all five for the future. And I thought that was just, that was an interesting change. Maybe a two, I thought the idea of a query block was something new and I liked it.

[00:59:00] And there was a lot of focus on multi-lingual at the beginning and towards the end. And I'm really interested to see how that will pan out. Me too. I don't think Matt was in it. It seemed like Matt wasn't in a position to quote a lot about phase four and rightly so, because not even phase three is happening next year officially, but I think we're, can't be aware of me maybe a little strange, a little bit more out of them, but I'm looking forward to the language aspect as well.

David Bisset: In fact, I'm kind of surprised I was at the phase four at the four phases when he first announced it a couple of years ago. Um, Um, let's see who, uh, who else we got here? I think we have, um, let's see. I think we, Eric, I think it's down to you now. Um, you might, you might be closing here. I know no big pressure.

Eric Karkovack: For baseball fans during this lockout, I'll try to be the closer here. Get on the mound and pitches to a victory here, 

David Bisset: not a sports person, but tackle, go and tackle and hit a fuel. Go right through the goalposts for me, please. 

Eric Karkovack: Okay. I'll shoot it into the [01:00:00] net for you. All right. So my bedroom aside, I think one thing I'm interested to watch is the, um, the growth of block themes.

Matt talked about, you know, hoping to have 3000 available, uh, at the next state of the word. That's going to be interesting because. I haven't seen like the commercial theme market takeoff for that yet. Um, there's a few opportunities there. I'm seeing some, you know, some new ones come out. So it'll be very interesting to see in 2022, how much, uh, adoption rate there is for block themes and full site editing and what number of themes we actually get to buy the next state of the word.

David Bisset: What do you think? What's your guess? 

Eric Karkovack: I'm going to say somewhere around a thousand, that'll just be my completely uneducated guests. I think there's so many theme authors that are still kind of hanging to the classic theme, uh, you know, style and way of [01:01:00] building. Um, and it's probably going to be a little bit slower adoption than maybe Matt hopes, but, uh, you know, I may be very wrong on that.

David Bisset: Do you think it has to do with just being, not familiar and trying to stick with what works as long as possible? 

Eric Karkovack: I think so. I think it's. If you watch how this is unfolding, it changes like almost weekly. And if I'm a theme developer, I'm probably going to hold off until I have a pretty good idea of what's going to be required and how these themes are going to work over the long-term before I invest a bunch of time in it.

So I think we're going to get there, but it may just take a little bit of time for people to get used to the idea and for standards to form.

David Bisset: Hmm. That sounds reasonable. That's okay. I don't know. Or it could be something I just drank. That's making me agreeable to everything I'd already said right now. It's possible. Well, anyway, I [01:02:00] really want to thank everybody who I think by the way, that was excellently, put Eric in terms of I could have been, that was just probably. 3000 sounds like an ambitious number. Who knows if we'll get there, but, uh, I think I'll put you down for a thousand and then this time, next year we'll come around and we'll see if we can collect on that bet and see if you were high or low.

So appreciate it. Oh, wait. What's uh, let's get Jeff here is the real closer about you or the fake closer Eric. Let's let's not to put any pressure on you there, but Jeff, can you, can you close this out for us here? Oh, wait, whoa, sorry, Jeff. I think I just,

okay. Jeff. Now you can go,

Jeff Chandler: uh, yeah, three words, block theme generator,

David Bisset: block theme generator. Oh, isn't somebody working on that or is that somebody is already working on it. 

Jeff Chandler: There's going to be more of [01:03:00] those created throughout next year. And 3000 I think is easily doable and there's going to be a bunch of them.

Bunch of themes created from these generators. That's my take.

David Bisset: So we're thinking, we're thinking the themes did themes really take off after the underscore S generator or a discourse came about? Is that, is that where you're considering more or less the equal the, was it underscore? 

Jeff Chandler: Uh, I don't underscore is just like a starter theme, but you know, what, what I'm seeing from the theme.json theme by theme generators nowadays seems to be just makes the theme generation process so much easier.

I mean, if you're, if you're a theme developer and you're not excited about what's coming down the pike in 2022, what is wrong with you? 

David Bisset: Well, wow. I mean, people ask what's wrong with me and I, they don't literally have the, I don't have the time to tell them all day. Um, okay, well, good. Yeah. So generator, we'll put that down as something for 2022.

Jason, did you have something to share before [01:04:00] we close out here or did I accidentally pushed the wrong. 

Jason: No, you didn't accidentally push the wrong button. Hi everyone. 

David Bisset: Hi Jason.

Jason: Hello. Well, there was a lot to, uh, digest and, um, the state of the word think it was interesting. Um, one of the things that we started noticing, uh, during our, our live broadcast of, of it was the fact that it's really interesting to, to have Matt interact with a smaller group of people versus such a larger room of people.

And we were also very disappointed that there was no boot. 

David Bisset: Well, I mean, where did it fit in the room? And that would, would've been a lot of polishing dude to remove any, I don't know. I feel like I would have to be like the Adrian monk on that show where he just, you just basically have to hand wipe the entire thing.

It doesn't seem so clean. Now after the last two years to be coming out of a boot, I mean, it was questionable to begin with. [01:05:00] Yeah, indeed. But yes, but yes, I, I think all of us are walking away here that this had a different, definitely that a different vibe. And I don't think it was just because we have, it's been two years since we've seen Matt in front of a live studio audience.

I think it was the size of the event. I think the mood was a lot lighter. Um, and there was a lot, not just because of the less people in the room. I think Matt's attitude and his casualness were a little bit more open, a little bit more different directed, but it was still very good. So I, I agree with Jason that I think it had a lot to do with the environment on that.

And we got to see me be a little bit more open Frank. Um, I dare say even some of it was even not that even rehearsed, not saying less rehearse, but I think maybe he, this is a couple of times tonight. He did pause for a while before answering a question, usually math pretty quick, usually mats pretty quick with questions.

And he's always been a talented speaker in that regard. Something I'll never learn even after doing so many of these things with you people, but, but yeah, it really did see him [01:06:00] when seeing him pause and consider the questions, especially I think from Allie's question to really. It did mean a lot more.

And I kind of enjoyed what tonight brought even though I think next time in, by if this happens at the end of 2022 and it's in front of a larger audience, I don't think I'd mind that either, but yes. Thanks. Thank you very much for having me. I appreciate it. No problem. No problem at all. Okay. I think that just about, does it this time?

I promise. I want to thank everyone for joining us this evening, especially on the east coast and in where the time zones are and where the time zones, where you're very late. Mr. Owl. Um, I just want to say thank you very much for your, um, it's. What is it like one in the morning over there? I, I can't imagine what.

Putting into your body right now to just doing the morning two in the morning. Oh my goodness. Oh, well, we admire your dedication, sir. Thank you for coming here and we hope to have you back soon. Uh, really, really appreciate it, Ray. Uh, on the other hand, you are bright and [01:07:00] cheery with your coffee in the morning.

So, uh, damn you my dear, but I want to thank you for coming as well.

She's not speaking to

Bet Hannon: thanks so much for inviting me to be part of this chat David. 

David Bisset: No problem. We want you back more for some of you, the more insights that you have, um, examining the entire WordPress through the repository or that's something that's in my inbox and I read it first. Every, every chance I get I'm going to drop in.

I think it's Friday my time. I don't know. Time's a flat circle for me, but thanks for coming. Bet. Thank you for coming as well. Greatly. Appreciate you taking some viewpoints from an agency standpoint and accessibility. Thanks for coming.

Hazel Quimpo: Great. Thanks for having me. 

David Bisset: Eric. Thanks for okay, now we're even now you don't owe me anything.

Thanks for coming.

Eric Karkovack: Hey, my pleasure. 

David Bisset: And I want to thank, um, LemonadeCode, who is the cohost right now. Um, she has been my producer, my, my wing person. I want to thank her as well for her help this evening as well, making sure the equipment has been organized, pointing out when people were raising [01:08:00] their hands and criticizing me when I've made very, very poor means on the web tonight.

So I want to thank you as well, Olivia. Thank you very much. Um, we're going to, this will be recorded and posted on post status in, in a day or two. So you can feel free to check out post status.com or our podcast links for that. And if you have any questions about anything we've shared here, you want a copy of the recording, whatever.

I'll feel free to share it with you. I don't want to thank everybody again and have a good evening. Goodbye.

by David Bisset at December 16, 2021 02:00 PM under SOTW

Post Status: Post Status Team Responses to the State of the Word 2021

Our Thoughts After SOTW

Michelle Frechette

Michelle Frechette: I was shocked and thrilled to receive an invitation to State of the Word in New York, and even happier when my travel was approved at StellarWP.  Arriving at the venue (Tumblr’s old digs) we were required to prove our vaccination status to go up to the loft. I got off the elevator and was immediately greeted by Josepha and then Matt. It was SO GOOD to see so many friends and well-known WordPress faces!

I took a reserved place in the front row and sat captivated by the environment, the information, and the nervous energy in the room. We were returning to some level of normalcy by being in that space together, and it felt both familiar and foreign after the last two years…but it was good.

When the address was done, and all the questions had been answered, and the broadcast had ended, there was an elegant reception with food and beverages. I met new people and enjoyed the conversation.

Not to be one to miss an opportunity, I asked Matt for an interview for Post Status, and recorded a 7+ minute conversation with him on the recent surge of acquisitions and the future of work in WordPress, that we will share later. He was truly gracious with his time, and I appreciated that very much.

On leaving, I gathered my jacket and was handed a swag bag.

All in all, I felt a bit like Cinderella, with a Lyft for a pumpkin carriage, purple hair as my tiara, and scads of friends helping me navigate the time with my electric scooter.

I enjoyed every minute.

Bonus: Michelle caught Matt for a brief interview after the SOTW address!

Anna Maria Radu

Anna Maria Radu: I was happy to learn about Openverse as a visual storytelling fan myself. The fact that Creative Commons has become part of WordPress is probably one of the best things that could happen for creators. Their work can now be even more easily incorporated and credited within anyone's storytelling. By doing this we, as a community, are supporting artists to gain recognition and appreciation through WordPress. Open Content for the win!

But probably the topic that stood out to me the most was the Diverse Speaker Program. I have worn many hats behind the scenes of pre-pandemic WordCamp events and WordPress-themed events in general. I loved seeing so much diversity — yet, there’s no such thing as too much diversity. I immediately joined the #diverse-speaker-support channel on WordPress Slack to learn more about it.

AJ Morris

AJ Morris: I'm excited for the future of block patterns and global styles! Having the native ability to use core block editor options for themes is going to drastically change the way we look at WordPress themes over the next 5 years.

Courtney Robertson

Courtney Robertson: Matt's vision of what contribution could look like was really exciting. As a Make WP Training Team co-rep, I eagerly welcome more contribution efforts across the WordPress project by connecting with teams. See Five Ways to Participate in Five for the Future for examples of how you can get involved as a contributor.

Also, Michelle Frechette's and Allie Nimmons‘ questions for Matt after his presentation — about introducing WordPress to youth and young adults — really reminded me of why I teach WordPress. I've instructed high school students as WP developers, and there are logistical challenges. I'd love to partner more closely with more educational organizations to help resolve these challenges. We can improve content across WordPress.org as we become compatible with COPPA requirementsSandy Edwards, Youth Working Group Team Co-Lead, is also eager to resume KidsCamps as we return to in-person WordCamp events. 

Kayla Demopoulos

Kayla Demopoulos: This year's SOTW was a great reminder that all the pieces of the puzzle work together to create the whole. It is great to remember where the project has come from, but more importantly, inspiring to think where together we can take it.

Dan Knauss

Dan Knauss: What a difference a physical venue makes! At the old Tumblr offices in Noho, this year's State of the Word looked like an opening at a small art gallery. No big screen, just a lot of framed visual art. No stage, just a simple podium. And after such a long period of time without in-person events, there was Matt waiting to go up front, casually leaning off to the side of the audience (maybe two dozen people) a few feet away. There were some awkward (but good!) moments, plenty of laughs, and a personable atmosphere that came through — even on YouTube. A lot of important facts and numbers were shared that we'll dig into later, I'm sure. That's what we usually focus our attention on. But my initial impressions had to do with mood, atmosphere, and tone — the emotional register of the themes that went through Matt's address and into his dialogue with the audience afterward.

We learned Matt wishes he had done things differently with the WordPress 5.0 release, and I thought of Courtney pointing out to me last month how the decision to delay 5.9 was a quiet sign of significant growth. We learned how Matt relates to the story of Ernest Shackleton turning back from an attempt to reach the South Pole only 97 miles from it — and why Matt wears a suit for SOTW. These were small things that came up in the question period, but they touch important themes for the WordPress community — growth and maturity — and maybe what they should look like. (More than a touch of humility and grace?)

Those who were in attendance are well-known for their contributions to the WordPress community, including many whose companies' participate in Five for the Future. The constant and increasing importance of giving back, of getting young people involved, and taking ownership of the largest open source community effort of its kind — together — these are the mature, future-facing themes that stood out to me.

I was talking with Matt Medeiros a few hours before SOTW, and he remarked how WordPress is paradoxically gigantic and small at the same time. It's a huge project with a giant ecosystem relative to the community of active contributors and what we might call the core culture of WordPress — including the people who make, distribute, and consume the news, information, and ideas that help direct the project. There's fragility and power, weakness and opportunity in being small in a big distributed network.

We're coming through (and possibly getting deeper into) pivotal and challenging times — not just for WordPress but the larger world of web tech and the global human community. Matt didn't mince words when he named the threats from big tech companies that aren't friends of The Open Web. If we're not just spinning our wheels, the future we want is what we're building toward today, together. These are some of the big themes we're focused on at Post Status too, as we move into a new year.

David Bisset

David Bisset: After watching Matt give this annual talk for years I could tell early on that something was different (in a good way) — but I couldn’t my finger on the cause. Matt seemed to be the most excited person in the room, along with whatever nervousness he had. He seemed more excited than in any State of the Word I can recall. Matt laughed more, and I think he went “off script” more too, telling stories and jokes. “I haven’t spoken to a crowd in two years,” he said at one point. Maybe that was it. I caught him a few times in a “nervous happy” state before the conference started. With no WordCamp US to provide a big crowd, this might have been the most open we’ve seen Matt, and I think he reflected the energy coming from the crowd.

I'm glad the “next generation of WordPress users” was brought up by Allie Nimmons and later Michelle. This topic was raised in the last in-person SOTW in 2019 as well. WordPress market share growth will eventually stop, and we’ll need to create and sustain new generations of developers, designers, and contributors from within the community. It’s really going to be up to the WordPress community and WordPress companies to mentor, intern, and train our future leaders and core contributors.

About “Be Like David” — it's the worse advice ever. (Editor's note: we respectfully disagree.)

Cory Miller

Cory Miller: Gutenberg and contributing to core continue to be key themes from Matt for the project.

Regarding Gutenberg — I greatly appreciate the work being done to make the Block Editor easier to use. It reminds me of the creative innovations that have happened since I started doing themes in 2006. I hope that continues to accelerate like it did with themes.

About Five for the Future and contributing to core — When I was leading iThemes and as a small team, I always struggled with how to meaningfully contribute to Core on a consistent basis. Courtney and I are working on Post Status Contributor Days for 2022 to help bridge that gap. She’s been pinging Team Leads to ask for their wish lists. Then we plan to put some dates out and tackle them together as a community. Stay tuned.

Post Status

You — and your whole team can Join Post Status too!

Build your network. Learn with others. Find your next job — or your next hire. Read the Post Status newsletter. ✉ Listen to podcasts. 🎙 Follow @Post_Status. 🐦

by Dan Knauss at December 16, 2021 02:00 PM under SOTW

WordPress.org blog: Highlights from State of the Word 2021

State of the Word 2021, the annual keynote from WordPress co-founder Matt Mullenweg, happened on December 14. The hybrid event took place in New York City with a small audience (proof of vaccination required). As Matt said, “we had people join by plane, train, and automobile.” Those who didn’t make the trek to the live event watched the livestream from wherever they call home, all around the world. 

It was an exciting moment for the WordPress community which also celebrated its first in-person WordCamp in Sevilla, Spain, after a lengthy hiatus for in-person events.

You can view the full recording, complete with captions and transcripts on WordPress.tv.

It was thrilling to see so many meetup organizers host watch parties worldwide. Twenty-six watch parties were held across eleven countries, with more than 300 RSVPs.  

Similar to past State of the Word events, Matt covered a broad range of topics. This year was no different. WordPress’ past, present, and future were in the spotlight, with highlights on the growth of the contributors, language translations, recent release milestones, and educational initiatives, to name a few.

Audience members and livestreamers alike viewed product demos showcasing upcoming features that will be the hallmark of WordPress 5.9, such as full site editing, block patterns, global styling options, and enhanced image controls.

Matt took the opportunity to remind everyone of the WordPress roadmap which includes native multi-lingual support and real-time collaborative site editing. He also pointed out that anyone can contribute to WordPress’ progress through a number of different initiatives ranging from creating new features and testing to helping spread the word and educate others.

Matt emphasized the way that open source software gets better by reminding everyone that “The more people that use a program like WordPress, the better it gets.”

Broader topics covering the tech landscape including web3, merger and acquisition activity, as well as the growth and support of open source software, rounded out the energetic presentation. 

The one-hour multimedia presentation was followed by an interactive question and answer session where Matt fielded questions that were submitted ahead of the event, as well as questions from the livestream and studio audience.

Discover everything that was covered by watching the official event recording and join the ongoing #ILoveWP conversation on Twitter!

Special thanks to @dansoschin for review and edits!

by Anjana Vasan at December 16, 2021 01:04 AM under WrapUp

December 15, 2021

WPTavern: David Gwyer Teases Block Theme Generator App, Plans for a Community of Creators

David Gwyer has been teasing ThemeGen over the last couple of weeks. It is his upcoming block theme generator app. Piece by piece, it has seemed to be coming together and could prove invaluable for theme developers. Currently, it is in beta testing.

He provided me with a link to an early preview to get my feedback on the tool. This is also available to anyone who signs up for access via the ThemeGen website.

Currently, the app only generates theme.json files. The feature was first launched in WordPress 5.8 for classic and block themes. It can have a bit of a learning curve for theme authors diving in for the first time. Plus, it is easy to make mistakes when hand-coding JSON files.

The dream goes beyond theme.json. That is the obvious starting point for such a project because it helps with current and future theme development. However, Gwyer wants to take this to another level as the project evolves.

“It’s not 100% functional yet, but I’m adding features daily,” he said. “I’m hoping that designers and non-coders will soon be able to create block themes visually, independently of WordPress. And be able to manage all their themes in a centralized location via the app. This opens up possibilities of a community of theme creators sharing and contributing to a resource of templates, styles, designs, etc.”

These goals align directly with my hopes for WordPress and its block system. I want to see creators actively involved in a give-and-take design community. The ideal place for this to happen is WordPress.org, but third parties can often develop these things faster without any potential hurdles from the platform’s official site. They can also push the WordPress project in a specific direction if successful on their own.

Using the App

Settings fields and generated theme.json.

For generating a theme.json file, the app works well. Currently, it allows creators to configure settings, templates, and template parts. The missing piece is building out styles, which is coming soon.

There is also an “Other” section. It has a single setting for supporting the Theme JSON Schema. This is handy for developers who like built-in validation, tooltips, and autocomplete if their code editors support it.

The most fleshed-out area of the app is for generating global settings. It covers border, color, layout, spacing, and typography options. As far as I can tell, it has most of the available flags that a theme author can set. It is hard to remember them all offhand, one of the reasons tools like this are helpful.

I did notice that a way to input font families was missing. He could do a lot with that in the future, especially if a web fonts API is ever bundled in core WordPress.

The “Custom” settings section is still unfinished. This will likely take some time to implement because theme authors can add any type of data with multiple levels of nesting. Unsurprisingly, it is not ready yet, but I am eager to see how Gwyer tackles the UI for it.

Creators can import colors from the Twenty Twenty-Two, Blockbase, or Tove themes. Implementing such a feature this early tells me that Gwyer is likely already thinking ahead to that future of shared resources. How neat would it be to pull in any piece of an existing block theme into another at the click of a button?

Colors, gradients, and duotone filters are missing one configuration option I would like to see. Right now, creators can add a name. However, they cannot manually add a slug, which is automatically generated.

Creating custom colors.

There are scenarios where some designers might use developer-friendly slugs like primary-100, primary-300, and primary-500. Then, they would use names that make more sense to end-users, such as “Primary Lightest,” “Primary Light,” and “Primary Medium,” respectively.

The auto-generated slugs feature is nice. However, it should allow for manual input too.

ThemeGen will likely be a welcome resource for theme authors as they navigate the block theme world in the coming months. Given enough interest, it could also become that community of like-minded creators who are open to sharing with one another. The first step is to get more testers and feedback during this beta period.

by Justin Tadlock at December 15, 2021 09:56 PM under Themes

WPTavern: State of the Word 2021: WordPress Passes 43% Market Share, Looks to Expand the Commons Through Openverse

Matt Mullenweg delivered his annual State of the Word address yesterday before a live studio audience in New York City. The majority of WordPress enthusiasts joined the event through the livestream on YouTube. More than 25 meetups gathered for in-person and online watch parties around the world – from Detroit, Singapore, Pakistan, and Medellín, to name a few.

Mullenweg began by reviewing WordPress’ growth over the past year, beginning with the Polyglots’ continued efforts to make WordPress available to the non-English-speaking world. In 2021, translators have significantly increased access to WordPress through language packs and active translations:

  • 13,659 language packs in core (+76%)
  • 15,900 active translations (+28%)

WordPress also expanded its Diverse Speaker Training program, gaining 135 participants in 66 cities across 16 countries.

The Learn.Wordpress.org site is now available in 21 languages, and Mullenweg said it is going to be a more prominent part of what visitors see when they visit the WordPress website. The platform has had 186 learning spaces, which he said is essentially cohorts of people going through the different courses. Learn.WordPress.org’s catalogue has grown to 73 workshops and 70 different lesson plans. There are now two courses available, which include collections of lesson plans.

“I think this is actually one of our biggest opportunities to expand the knowledge of what WordPress is, and also define it to a new audience through these courses,” Mullenweg said.

One of the most notable stats from the presentation is WordPress’ distribution, which is now at 43.1% usage on the web, according to W3Techs, up from 39.1% last year.

One concern is that open source CMS’s are slowly disappearing from the top five competitors, as proprietary systems pass up Drupal and Joomla. Mullenweg said in general the CMS’s aren’t taking market share from each other but rather from the websites which previously had no detectable CMS.

“We actually grew two entire Wixes this year, which is a new unit of measurement,” Mullenweg joked.

“And to put that in perspective, we’re still 10 times larger than number two out there, but this doesn’t happen for free. And we shouldn’t take any of this for granted. There are in the history of software, and certainly the internet, many services that were once dominant that now we need museums to remember what they were there to maintain.

“We really need to stay humble and stay close to users and iterate the software as quickly as possible.”

Mullenweg hinted that 2022 might be a year that WordPress aims for four releases instead of three.

“I’m proud to say it was a good year for WordPress security,” he said. More than 30 people contributed to security patches, and 1/3 of those were first-time contributors.

“Security is a process,” Mullenweg said. “Anyone who says they are perfectly secure is tempting fate.

“Our ability to be one of the most secure platforms in the world is one hundred percent a result of how much we’re going to be able to update sites because humans are fallible sometimes.”

State of the Word Features WordPress 5.9 Demos

Mullenweg highlighted a few new features coming in 5.9, with demos of block themes, template editing in the block editor, global styles, and pattern improvements. He reiterated that Gutenberg is the future of WordPress for the next decade:

As we look towards the future of WordPress, we are finally achieving one of the things that WordPress set out to do 18 years ago.

This is why we started the Gutenberg project. When we first introduced Gutenberg a few years ago, we said this was going to be the foundation, what the new versions of WordPress were built on, what our next 10 years would be.

Not only are we enabling folks to express themselves uniquely on the web, unlike the cookie cutter that all the social sites try to put you into, the cookie cutter looks. We’re doing it in a way, which is standards based, interoperable, based on open source, and increases the amount of freedom on the web, which is very key, certainly to me, and the most important thing that I work on.

WordPress has just begun on its journey with Gutenberg. Mullenweg reviewed the four planned phases, which began with “Easier Editing” in 2018. The second phase, Customization, started in 2019 and Mullenweg said 5.9 will be the MVP of this phase.

With 5.9 delayed until 2022, he has the third phase, Collaboration, slated for 2023, so that contributors don’t leave customization too early before it’s polished. There are only 28 block themes available so far. “That needs to be 5,000,” Mullenweg said. Later during the presentation he said he hopes that WordPress will “have 300 or ideally 3,000 of these block themes” before entering the Collaboration phase.

There is no timeline yet for the fourth Multilingual phase, which aims to make it easy to publish sites in multiple languages with a workflow that makes sense.

Web3 and the Decentralized Web

Many State of the Word viewers were eagerly anticipating Mullenweg’s thoughts on Web3 and NFT’s, after the controversial topic was included in the State of the Word announcement last month. They speculated on how WordPress might incentivize contribution through tokens or NFT’s. For now, it appears WordPress will keep attracting contributors the old-fashioned way.

Mullenweg’s message was essentially that WordPress already embodies Web3 ideals and has from the beginning.

“What Web3 embodies is two essential ideas — decentralization and individual ownership,” he said. “Those are both things that WordPress is both well-poised to be already doing and to continue doing for some time to come.”

He also cautioned those exploring Web3 projects to keep the freedoms of open source in mind:

There’s been an incredible amount of innovation. I think this has also attracted some hucksters and some folks kind of hustling things that aren’t truly open. So you all are very familiar with WordPress. For every project, which is asking for your money dollars, or for you to pay the cost of a house for a picture of an ape, you should ask, does it apply the same freedoms which WordPress itself does, and how closely does it apply to increasing your individual agency and freedom in the world?

Mullenweg also spoke about the many acquisitions in the WordPress space and put them in the context of what’s happening in the world of business. WordPress appears to be a microcosm of global acquisition activity.

“And if you were to broaden it to the global M&A landscape, not just technology, we’ve seen over 45,000 different acquisitions,” Mullenweg said. This is up over 24% from last year, which is already a huge year and represents $3.6 trillion of different mergers and acquisitions.

“This is driven by another trend, which I found utterly shocking to learn and understand, which is capital inflows to stocks,” Mullenweg said. He shared a chart that shows how much money is moving from other assets into the public equity markets.

A Call to Contribute Back to the Commons

With an economy estimated at over $10 billion per year, and all the companies making millions of dollars using WordPress, Mullenweg took a few minutes to highlight how the Five for the Future program has protected the project from the Tragedy of the Commons.

In one slide, he dispelled the myth that the impact a company has on the future of WordPress is dependent on the size of the company.

For example, Yoast has a major impact on WordPress, despite having 80x fewer employees than GoDaddy, a web host that Mullenweg seemed to be specifically calling out in the presentation when driving the point home:

So the impact the company has on the future of WordPress is not at all related to the size of the company. There’s no reason that if we really take to heart what’s made us successful so far, that we can’t get more companies participating in the commons of what’s happening.

When a company benefits from WordPress, when they put something back into the core, whether that’s your translations community volunteering or code, as this particular graph is representing, it ensures that there’s something left in the future for WordPress to be there. You can’t run Wix or Squarespace on GoDaddy.

Mullenweg also officially introduced Openverse now that the first version is live. He shared some of his vision for the project’s future with WordPress. The plan is to build this into the admin, so that when users upload a new image or video, they will be able to choose from among Creative Commons licenses and perhaps have their work indexed in the Openverse.

“It’s all about creators having the control and autonomy they need to license their content, however possible,” Mullenweg said. “And for those that choose to put into the commons, that then becomes a part of what is shared in humanity and allows us to grow and create cool things together.”

He also introduced the new WordPress.org Photo Directory, which hosts totally open imagery that can be used on any site for commercial and non-commercial uses. Someday WordPress users will be able to insert works from the Openverse into their content with just one click.

In addition to contributing to Gutenberg through patterns and block themes and other means, Mullenweg also encouraged users to put some of their work into the Openverse.

We’ll go deeper into some of his Q&A answers in an upcoming post, but one common theme among the questions was how WordPress might attract a younger generation of contributors and what advice Mullenweg might give to the young people inheriting the investments contributors have made in WordPress.

In his response Mullenweg returned to his call to replenish the commons. This lifestyle of giving back and making things as open as possible is the golden thread running through the message of this year’s State of the Word.

I think if you just give a person a blog, or even worse, a social media account, you feed them for a day. You teach them how to create the web, which is in many ways, in my opinion, the most amazing actualization of shared humanity and knowledge – how do we create something that lasts beyond our own individual lifetimes? It’s the web.

How do we create something that lasts beyond us? A legacy, a true legacy. It’s adding to the information. That’s part of what hopefully goes forward for future generations and then allows us to sort of fast [forward], skip all the mistakes, skip all the learnings, to what’s latest. It’s upgrading the clock speed and version of humanity.

With the official launch of Openverse and the continued growth of WordPress against proprietary systems, Mullenweg was able to make a compelling case for contribution as a matter of importance to humanity — a meaningful way to increase the commons available to future generations and to be part of defining the future of the web. The vision of Openverse goes beyond WordPress, as Mullenweg said it is “something the WordPress community is creating for the benefit of the world,” with works that people are free to use on any platform.

“I think it’s possible to have an abundance of the commons,” Mullenweg said.

“So the more people that use a program, the better it gets in so many ways. More bugs get reported, more translations happening, more plugins get developed, more themes get developed.” This is one of the reasons market share is a strong indicator of the health of the project and its potential to continue meeting users’ needs.

“But part of that is some percentage of the people who essentially directly benefit from WordPress, putting something back into the commons, fertilizing the soil, planting some more grass,” Mullenweg said.

by Sarah Gooding at December 15, 2021 09:45 PM under state of the word

WPTavern: All In One SEO Plugin Patches Severe Vulnerabilities

The All In One SEO plugin has patched a set of severe vulnerabilities that were discovered by the Jetpack Scan team two weeks ago. Version 4.1.5.3, released December 8, includes fixes for a SQL Injection vulnerability and a Privilege Escalation bug.

Marc Montpas, the researcher who discovered the vulnerabilities, explained how they could be exploited:

If exploited, the SQL Injection vulnerability could grant attackers access to privileged information from the affected site’s database (e.g., usernames and hashed passwords).

The Privilege Escalation bug we discovered may grant bad actors access to protected REST API endpoints they shouldn’t have access to. This could ultimately enable users with low-privileged accounts, like subscribers, to perform remote code execution on affected sites.

The Common Vulnerability Scoring System (CVSS) gave the vulnerabilities High and Critical scores for exploitability.

Montpas explained that All In One SEO failed to secure the plugin’s REST API endpoints, allowing users with low-privileged accounts (such as subscribers) to bypass the privilege checks and gain access to every endpoint the plugin registers. This includes a particularly sensitive htaccess endpoint, which is capable rewriting a site’s .htaccess file with arbitrary content. Montpas said an attacker could abuse this feature to hide .htaccess backdoors and execute malicious code on the server.

All in One SEO is active on more than 3 million WordPress sites, and every version of the plugin between 4.0.0 and 4.1.5.2 is affected and vulnerable. Users with automatic updates enabled for minor releases should already have the patch since it was released six days ago. For those who are updating manually, the Jetpack Scan team recommends users within the affected range update to the latest version as soon as possible.

by Sarah Gooding at December 15, 2021 03:08 AM under security

WPTavern: Alara Block Theme Promises a New Pattern or Design Variation Every Week for the Next Year

One month ago, UXL Themes released Alara. It was a theme that carried with it one bold promise: every week for the next year, users could expect a new design variation, child theme, or block pattern. And, all of this would be done on the back of the block theme system that is slated to launch with WordPress 5.9 next month.

Aside from one part-time member of the support crew, Andrew Starr is the sole developer for UXL Themes. With the promise, he put a whole lot of creative work on his shoulders for most of 2022. Alara already has 41 block patterns and one child theme available. Presumably, he will ship global style variations when the feature lands.

Alara is the third block theme by UXL Themes. In February, I covered the first, Hansen. Block theming was still in its infancy at the time. The system has matured, and Starr has built some experience on top of it. It shows with his latest outing. And, for this theme, he has thus far kept up with his plan to offer new features every week.

I am not the biggest fan of the theme’s default typography. The font-size and line-height work well enough for long-form content. However, its light font-weight can make text tough to read. The great thing about block themes is that they integrate with the site editor. Users who prefer a thicker weight only need to select it via the Typography panel.

Changing the theme’s default font-weight.

What Alara does well is offer a large selection of patterns for its users. I will sound like a broken record here, but this is how themes will differentiate themselves from others in the block-theming paradigm. If users can essentially overwrite anything about the design, the value-add is all the extras themers offer to them. Right now, that is in the form of patterns and block styles. Eventually, global style variations will be included in that list.

Alara initially launched with 29 patterns, but Starr has added 12 more since then. They are broken down into 13 categories. One of those is an “Alara – New” category, which showcases the latest patterns bundled with the theme.

Latest patterns bundled with the theme.

I like this approach to letting users know what is new with the theme. Since WordPress has no built-in way for theme authors to highlight new features, I expect to see more theme authors take similar approaches.

The patterns cover a range of use cases. The latest release includes some new recipe patterns for food bloggers. It includes business-friendly layouts for pricing tables, reviews, and call-to-action sections. Plus, it has several more for general-purpose use.

Some of my favorites are the “About” patterns. There are layouts for both single site owners and teams.

“Team 3” block pattern.

The theme also offers two full-page patterns. Users can insert them and instantly have an editable page with filled-in content.

Such patterns often take up a lot of room in the inserter when opened as a sidebar. They are better viewed in the full-screen pattern explorer overlay.

Full-page patterns.

I would still like to see WordPress officially adopt the starter page templates system or something similar to handle these use cases. Many users will rather insert a full page of content instead of piecing it together with smaller patterns. They should have a dedicated section in the UI for easy access.

For users who prefer brighter and bolder color choices over Alara’s more vintage default design, UXL Themes has also released a child theme named Ceres.

Alara could be a solid block theme for those eager to tinker with WordPress 5.9 features. There are still a few quirks, depending on which version of the Gutenberg plugin (or beta version of WordPress 5.9) is in use. I am excited to see if Starr keeps up with the promise of weekly design and pattern releases over the next year.

by Justin Tadlock at December 15, 2021 02:12 AM under Reviews

December 14, 2021

WordPress.org blog: WordPress 5.9 Beta 3

WordPress 5.9 Beta 3 is now available for testing!

This software version is still under development. Please do not run this software on a production site; install it on a test site, where you can try out the newest features and get a feel for how they will work on your site.

You can test the WordPress 5.9 Beta 3 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the beta version.

Option 3: If you use WP-CLI to upgrade from Beta 1 or Beta 2 to Beta 3 on a case-insensitive filesystem, please use the following command sequence:

Command One:

wp core update --version=5.9-beta2

Command Two:

wp core update --version=5.9-beta3 --force

The current target for the final release of 5.9 is January 25, 2022, which gets closer every minute. Your help testing this beta is vital: the more testing that happens, the more stable the release, and the better the experience for users and developers—and the entire WordPress community.

Some Highlights

Since Beta 2, 14 bugs have been fixed. Here are a few of the changes you will find in Beta 3:

  • Editor: Add FSE infrastructure from Gutenberg plugin into Core (#54335).
  • Formatting: Allow PDFs to embedded as objects (#54261)
  • Language switcher on the login screen (#43700)
  • REST API: Add navigation areas REST API endpoint from Gutenberg plugin (#54393)
  • Themes: Live Preview button bug (#54578)

How You Can Help

Do some testing!

Testing for bugs is vital for polishing the release in the beta stage and a great way to contribute. 

If you think you’ve found a bug, please post to the Alpha/Beta area in the support forums. If you’re comfortable writing a reproducible bug report, file one on WordPress Trac. That’s also where you can find a list of known bugs.

For even more ways to test, you can also refer to this official Full Site Editing post from @annezazu.

Got questions? Here are some answers

In the coming weeks, follow the Make WordPress Core blog for 5.9-related developer notes that cover these items in detail. So far, contributors have fixed 316 tickets in WordPress 5.9, including 100 new features and enhancements. More bug fixes are on the way with your help through testing.

Props to @psykro@estelaris@hellofromtonya, @marybaum@webcommsat@cbringmann, @costdev, and @audrasjb for contributions to this post.

Filed under #release, #5.9, #beta

by Jonathan Bossenger at December 14, 2021 08:19 PM under beta

WPTavern: Creative Commons Search Is Now Openverse

The Creative Commons search engine has been rebranded to Openverse and now redirects to its new home at wordpress.org/openverse.

Users will find the revamped interface maintains the ability to search the same collections, narrowing results by use case, license type, image type, file type, aspect ratio, and more. The Openverse search engine is also now available in more than 10 languages, with more translations approaching completion. This update includes access to images from StockSnap and new  Meta Search providers EDUimages and Images of Empowerment.

“We’d like to once again express our thanks to WordPress for carrying forward the important work of providing the open community with a search engine to find works to remix, reuse, and openly enjoy,” Creative Commons COO Anna Tumadóttir said in a post passing the torch of CC Search to Openverse.

In April 2021, Matt Mullenweg announced that CC Search would be joining the WordPress project. Automattic hired key members of the CC Search team in support of its continued development and sponsors their contributions to the project as part of the company’s Five for the Future commitment.

Beyond hosting the search engine, adding Openverse searching and image downloading is on the roadmap for WordPress core. When asked in the comments of his blog if the WordPress media library can be integrated with Opeverse, Mullenweg confirmed that is the plan. Users may also be able to share their own works back to the commons in the future.

In an episode of the Open Minds podcast published in August, Mullenweg elaborated on one of the motivations behind bringing Creative Commons Search into WordPress. In the early days of WordPress, GPL-compatible images were not easy to find. Mullenweg said he had even shared his personal collection of 30,000 photographs as open works that anyone could use for designs and themes, to spur on creativity when CC0 images were more scarce.

“I also really want to make it easy for people within WordPress to license their images in a way they can be accessible to others,” he said. “Now it’s exciting to know that there’s going to be open-source-compatible images across any number of sites, to any number of people building things for the web, whether that’s on WordPress or something else.”

Mullenweg is expected to speak more about Openverse at his annual State of the Word address tomorrow, which will stream live from New York City with a small studio audience.

If you’re interested to contribute to the maintenance and the future of the Openverse project, you can connect with the team at make.worpress.org/openverse or in the #openverse channel on WordPress Slack.

by Sarah Gooding at December 14, 2021 04:30 AM under Openverse

WPTavern: The Next Generation of WordPress Theme Authors Will Design From the Site Editor

Last week, I played around with a new plugin that allows users to export a custom theme.json file. The project is still a little buggy at the moment, but I look forward to covering it in more detail soon. The export function was more of a secondary objective for the plugin, but it represents a feature I look forward to landing in WordPress one day.

While tinkering with the plugin, I reminded myself to check on the progress of a related ticket for Gutenberg. Currently, the site editor feature allows end-users to export their theme templates. However, there is still no way to do so for global styles.

Essentially, block themes need two components: templates and a global styles configuration. There are other pieces. The functions.php file is increasingly unnecessary, and the standard style.css file is often used for adding theme data instead of CSS. There is talk of adding both /patterns and /styles folder support for automatically registering block patterns and global style variations, respectively.

Twenty Twenty-Two theme folder and file structure.

WordPress theme development already looks different than it did just a few years ago. Soon, old-school themers will hardly recognize it.

That is not necessarily a bad thing. The ongoing mantra is that the platform seeks to democratize design much as it did for publishing. I have often wondered how feasible such a goal really was. I would see sparks of genius littered throughout the project in the past few years. It took a while for all the moving parts to become a well-oiled machine. There are still some missing components, but the platform’s promise is becoming a reality.


Over the weekend, I happened across an old friend’s Facebook profile. He is one of the few bloggers I began following in the early 2000s. I noticed he had shared something from his blog, and I checked it out. He has a background in journalism, and he has always had unique insights into what most of us might consider the mundane, day-to-day life stuff.

I continued reading other posts. It was a welcome change of pace to pour through thoughts from someone who is simply blogging for the sake of blogging, even if still on Blogger and not WordPress. The site does not look any different than it did years ago. He even has a blogroll. I spent about an hour going from site to site, reading the ramblings of other passionate bloggers, most of them on the self-hosted WordPress software or WordPress.com. It was a reminder of why we continue building this platform.

Of course, we all have different reasons for coming to the same place. We must also have a healthy economy behind WordPress, which helps fund the project’s more altruistic mission. At the end of the day, the goal is to provide free software for the masses, offering an alternative to the gatekeepers and walled gardens elsewhere on the web.

Theme design needed to be shaken up. I enjoy finding the odd diamond in the rough. But, it has been a long time since the average end-user has had true freedom with their website’s design. Kubrick was fine in the mid-2000s. WordPress catered to a DIY crowd that was OK with making CSS changes to get their desired outcome. However, in the 2020s, the platform must bring a new set of tools to a wide-ranging audience. That is what the global styles feature is all about.


When WordPress 5.9 launches next month, many users will get a taste of the site editor. Users who switch over to the upcoming Twenty Twenty-Two theme will have more design power at their fingertips than ever before with stock WordPress. From templates to styles, they will change the front end of their sites to whatever they dream up.

Some will undoubtedly stumble upon the “Export” button in the site editor:

Exporting the site’s templates.

It is a handy tool for theme authors transitioning to block theme development, but that little button has a world of potential. Right now, it spits out an edit-site-editor.zip file with a /theme sub-folder. Within that, sits /templates and /parts.

What is missing is the theme.json file, which represents the global styles. When that lands, users will essentially be exporting an entire theme. Well, minus a screenshot and required legacy files like style.css.

Part of democratizing design is not just handing over the ability to customize the site. Fulfilling the mission means people can share those designs. The next generation of WordPress themers will not be stuck in a code editor like those of us today. They will cut their teeth on the built-in site editor. Some will graduate to more advanced development, but others will have everything they need to publish their themes on WordPress.org or even venture out and build their own businesses. In part, it will level the playing field for those with an eye for design but not the coding chops to create those projects.

Exporting global styles cannot get here fast enough. Then, we need to add pattern exports to the equation, but the mission requires we take it one more step.

I look forward to the day when a user can build an entire theme from scratch in WordPress. Then, they submit it to the theme directory without writing a bit of code. Could one of those “average” bloggers find a talent for web design they never knew they had? Could someone who always wanted to learn but did not have the time/resources/privilege create the next most popular theme? I like to think so.

by Justin Tadlock at December 14, 2021 12:37 AM under Themes

December 12, 2021

BuddyPress: BuddyPress 10.0.0-beta1

BuddyPress 10.0.0-beta1 is finally available for testing! 🎄

Please note the plugin is still in development, so we recommend running this beta release on a testing site.

You can test BuddyPress 10.0.0-beta1 in 4 ways :

The current target for final release is early next year : January 5, 2022. That’s only 3 weeks away 😱, so we would appreciate your help making sure this next major version of your community engine is as good as it can be.

Please note BuddyPress 10.0.0 will require at least WordPress 5.4.

As usual, testing for bugs is the key to a safe upgrade. It’s the main reason we actually package beta/RC versions 👉 so please give us a few minutes of your time to make sure this pre-release behaves the right way with your specific WordPress configuration, your theme, and the other WordPress plugins you are using. Try to use a testing site which is very close to the one you are using in production. If you find something weird (aside from the great new features below), please report it on BuddyPress Trac or post a reply to this support topic.

Around 70 changes to expect in 10.0.0

You can check out this report on Trac for the full list of them. Below are the ones we believe will improve your BuddyPress experience in the most significant way.

🛂 Site Membership Requests

Site Administrators wishing to have more control over who can join their community will be able to enable site membership requests from their BuddyPress Options Administration screen. Once done, BuddyPress sign-ups are transformed into membership requests to be manually reviewed and approved by an Administrator to validate new user accounts.

🗞 More engaging logging activities

These simple activities about specific user interactions or events (e.g.: a user became a friend of another user) will be more visually attractive to improve user engagement in your community. The most impressive new activity is that which is generated when a user updates their profile photo: it will include the profile photo that spurred the creation of the activity item, even if it has been updated since 📸!

🎨 WordPress Full Site Editing compatibility

You’re beta testing WordPress 5.9: first thank you, second please take a few more minutes to check the improvements we’ve made to our BP Theme Compatibility API to play nice with themes supporting Full Site Editing such as the next WordPress default theme: Twenty Twenty-Two.

➕ A new place to easily discover our next BuddyPress Add-ons

BuddyPress Add-ons are side projects/projects as features/next BuddyPress blocks maintained by the BuddyPress development team we’ll soon make more widely available by publishing them on the WordPress plugin directory. When BuddyPress 10.0.0 is released, you’ll find a new tab to your “Add Plugins” Administration screen. On it, you’ll see a new add-on for a potentially upcoming feature: BP Rewrites. We think this will bring more contributions to the BuddyPress project as a whole.

🎮 Happy testing!

by Mathieu Viet at December 12, 2021 06:05 PM under releases

Gutenberg Times: Pattern Block, State of the Word and theme.json builders – Weekend Edition 196

Howdy,

it’s great to be home again! How are you?

We are coming up to the end of the year, and it’s time for the annual State of the Word (SOTW). Matt Mullenweg, co-founder of WordPress, presents the accomplishments and challenges of the outgoing year and of what’s to come for next year to the WordPress open-source project.

The event will be live-streamed from New York, on Tuesday, December 14th, at at 5 pm ET – 22:00 UTC. On the SOTW announcement page, you can also find a list of watch parties from around the world, some in-person, some virtual.

After the two-hour event, the Post Status team will hold a live event on Twitter Spaces to discuss SOTW. I’ll be there to listen in.

Now, let’s catch up on last week’s Gutenberg news!

Yours, 💕
Birgit


Table of Contents


Gutenberg Plugin Version 12.1

The new plugin version came out Wednesday Dec 8th, 2021, with plenty of bug fixes that made it also into WordPress 5.9 Beta 2.

Riad Benguella published the release notes: What’s new in Gutenberg 12.1 ( 8 December)

Justin Tadlock took it for a spin. You can read his take in Gutenberg 12.1 Fixes Block Appender Layout Shift, Adds Template List Views, and Enhances Global Styles. And Congratulations to the WPTavern team to the new Site design, released together with the WordPress Special Projects team at Automattic.

Grzegorz Ziolkowski and I discussed the new Gutenberg version in our episode 57 of the Gutenberg Changelog podcast. Lots of links in the show notes.

Subscribe to the Gutenberg Changelog podcast
🎙️ Spotify | Google | iTunes | PocketCasts | Stitcher |
🎙️ Pod Bean | CastBox | Podchaser | RSS Feed 

Plugins and other tools for the Block Editor.

The agency, 10up published their Publisher Media Kit Page plugin that created pre-configured media pages using Block Patterns. It works with Newspack and the Twenty-Twenty-one default theme.

Justin Tadlock gave it a whirl. Here is his post: 10up Releases the Publisher Media Kit WordPress Plugin


The number of “Full-site Editing” Themes in the WordPress repository increased to 31 this week. The newest Theme is Videomaker by the designers at Automattic. It’s aimed at film directors and video creators. Justin Tadlock posted this review: Videomaker Block Theme Targets Film Directors and Video Creators


In Cwicly Gutenberg Toolkit: A New Full Site Editing Solution, David McCan reviews the kit that includes a block-based theme, a Gutenberg blocks add-on, and Advanced Custom Fields Pro. McCan includes a video walk-through of this new tool.


The team of Trewknowledge wrote The Future is Coming, Now. Watch and Learn About WordPress 5.9 Anticipated Features and summarizes the most important features coming to a WordPress instance near you in January 2022.


In his article, Custom Single Post Layouts with WordPress Gutenberg, Jamie Marsland covers the process on how to build a custom layout for your single posts using the WordPress Gutenberg Block Editor and Full Site Editing. He covers the dynamic post blocks and how to use the template editor.

 “Keeping up with Gutenberg – Index 2021” 
A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test and Meta team from Jan. 2021 on. Updated by yours truly. The index 2020 is here

Building Custom Blocks and Features

This week, Ryan Welcher showed us how to create a Meme Block on his live stream. The code is available on GitHub.

“I don’t always type badly, but when I do, it’s during a live stream”.

Phil Sola and James Koussertari are the WPBros and started their YouTube Channel with episodes covering Gutenberg Block Development. The first four episodes are already available. Check them out.

Creating Block Themes

Rich Tabor has been a giant fan of Block Patterns. This week, he wrote a tutorial on Building WordPress Block Themes with the New Gutenberg Pattern Block.

The Pattern block renders a pattern — typically used within a template from a block theme. The main advantage is that it allows for translatable templates in themes.


David Gwyer has been working on a Block Theme Generator and the first version is already online. It offers HTML form and some tools to select all the settings you would want to configure for your theme in the theme.json file, assembles it and lets you download the file to add to your theme. It’s a first version, but already quite nifty. I, for one, had great fun playing around with the color pickers for all kind of features.

Screenshot: Block Theme Generator by David Gwyer.

On a side note, Ryan Welcher is also working on creating a theme.json generating tool within the block editor. You can watch the progress on this GitHub repository.


Jeff Ong and Jason Crist picked 4 topics to highlight in the post Gutenberg + Themes: Week of Dec 5.

  1. New Color Picker is coming to Gutenberg
  2. There is an ongoing discussion on how best to add global padding, and still allow for full-width alignment. Check out the ideas that are tested. 
  3. Opt into block styles via theme.json. This is to allow wp-block-styles support via theme.jscon. 
  4. Contrary to other styling, it seems Global link styles override block-level styles. Chime in on the issue. 

I am a big fan of the digest form of their weekly round-up post.

As always, the weekly round up also lists Overview issues for various feature in the works, like the Typography Tools, the Global Styles interface, the Default theme and a few more items. 

And lastly you find a list of General Resources to documentation and tutorial. 


Block Themes were also a topic for the Ask the Bartender column at the WPTavern: Justin Tadlock answered the question: Is There a Starter for Building Block Themes?


Upcoming WordPress Events

December 13, Monday 1pm ET / 6pm UTC
WordPress Trends to Watch in 2022
Discussion with Paul Lacey, Ronald Gijsel, Cami MacNamara, and Anne McCarthy.
They’ll share ideas about emerging trends beyond WordPress 5.9 for:

  • Full Site Editing
  • Block Themes
  • Where Gutenberg goes from here
  • Performance improvements and more

RSVP now to attend or catch the replay (GoDaddy Pro Online)


Post Status is not the only team getting the hang of Twitter Spaces. Ellen Bauer, friend of Gutenberg Times and co-founder of Elma Studio, also started informal audio-only discussion. Bauer shared her schedule for the next few weeks:

  • 16 Dec, Thursday, 6pm UTC / 1pm ET
    Thoughts on Matt’s ‘State of the Word’
  • 22 Dec, Wednesday, 9am UTC / 4am ET,
    How to prepare for FSE & the WP5.9 release
  • 30 Dec, Thursday, 6pm UTC / 1pm ET,
    Casual End of 2021 WordPress recap/chat

Follow Ellen Bauer on Twitter to get the links to the Twitter Spaces events.


December Fri, Dec 17, 2021 at on 10:00 AM ET / 15:00 UTC
Kyle Van Deusen will host a live event and show people interested in building blocks how he rebuilt the WaveApps homepage with his favorite block packages, He will answer viewer questions. Add the event to your calendar


On the Calendar for WordPress Online Events site, you can browse a list of the upcoming WordPress Events, around the world, including WordCamps, WooCommerce, Elementor, Divi Builder and Beaver Builder meetups.


Don’t want to miss the next Weekend Edition?

We hate spam, too and won’t give your email address to anyone except Mailchimp to send out our Weekend Edition

Thanks for subscribing.

Featured Image: “LetterPressBlocks_RT5” by fiveten is licensed under CC BY-NC 2.0 via Openverse

by Birgit Pauli-Haack at December 12, 2021 12:18 AM under Weekend Edition

December 11, 2021

Gutenberg Times: Gutenberg Changelog #57 – Gutenberg 12.1, Block Theme.json Builder, WordPress 5.9 Beta 2

Birgit Pauli-Haack and Grzegorz Ziolkowski discuss Gutenberg 12.1, Block Theme.json Builder, WordPress 5.9 Beta 2 and Twitter Spaces

Show Notes / Transcript

Subscribe to the Gutenberg Changelog podcast via your favorite podcast apps!
🎙️ Spotify | Google | iTunes | PocketCasts | Stitcher |
🎙️ Pod Bean | CastBox | Podchaser | RSS Feed 

Show Notes

David Gwyer has been working on a Block Theme Generator

Ryan Welcher is working on a Theme.json Builder

Follow Ellen Bauer to learn about upcoming Twitter Spaces

Recording of this year’s React conference

WordPress 5.9 Beta 2 released

What’s new in Gutenberg 12.1 ( 8 December)

Gutenberg 12.1 Fixes Block Appender Layout Shift, Adds Template List Views, and Enhances Global Styles

New directory names for block-based (FSE) themes

Gutenberg + Themes: Week of Dec 5

Follow Twitter Bot @GoodFirstBugs

Stay in Touch

Transcript

Birgit Pauli-Haack: Well, hello and welcome to our 57th episode of the Gutenberg Changelog podcast. In today’s episode, we will talk about Gutenberg 12.1 release, block theme.json builders and WordPress 5.9 Beta 2, and Twitter Spaces. I’m Birgit Pauli-Haack, curator at the Gutenberg Times, and Developer Advocate at Automattic. And I’m here with my co-host Grzegorz Ziolkowski, JavaScript developer at Automattic and WordPress core contributor. So how are you today, Grzegorz?

Grzegorz Ziolkowski: Oh, thank you, I’m great. Winter is already in Poland. We have a tons of snow outside, so we were outside with my daughter today doing angels. That was fun, so yeah.

Birgit Pauli-Haack: Yeah.

Grzegorz Ziolkowski: It’s pretty surprising that it’s so early, because usually it’s in January. Anyway, how is it at your place? How are you?

Birgit Pauli-Haack: Well, in Florida, it’s really warm. It’s 70 degrees Celsius, so I’m not going to complain about anything. And I just got back from Germany where it was really cold and I got to test all my winter clothes configurations, and yeah, it was end to end testing and it worked.

Grzegorz Ziolkowski: Thank you, all good. We are prepared.

Birgit Pauli-Haack: We are prepared. Yeah. And we have to, because we are heading out to Vancouver for the holidays and visit friends. So there is going to be snow in the forecast as well. 

Yeah, so we have a great episode today. No guest, and is also the last one from 2021, the last episode for 2021, because we are going for holidays and there is a release, the Gutenberg release 12.2 is scheduled for December 22nd, but that’s so close to the Christmas holidays that we said, okay, let’s push it into January and we will do two releases with the episode 5.8.

Grzegorz Ziolkowski: Yeah. I’m not sure if there is, will be all on, like the way you said like on time, I mean on time, like at this time of the year. So the Gutenberg core team, there’s always discussion whether to postpone some of the releases or not. So I’m not sure this type of discussion already happened and it can be on 22 because it’s just before major holidays for most of the contributors, so it should be good. But I remember that there was a time when we had three weeks between releases and maybe even once we skipped one of their releases. So it’s something that’s unclear in my opinion.

Birgit Pauli-Haack: Yeah. Okay. So if you want to subscribe, dear listeners, to the Gutenberg Weekend Edition, we will keep up during the holidays, maybe not every week, but definitely more often than the Gutenberg Changelog Podcast. You will learn the newest about the release schedule for the Gutenberg plugin to come. 

Community Contributions

So today I also wanted to, we don’t have any announcements or listener questions, but I found on Twitter that David Gwyer has been working on a block theme.json generator, and I connected with him and it’s still in preview, but it’s a next json, next JS application that he’s building with a form, and then you can then download the theme.json for it. He has different tabs that you can see. So it’s not yet out, but I’m just announcing that it’s something you could keep an eye out for when it comes out. And if you are nice to him maybe, and ask him for a preview link on the Theme.json Generator. Yeah.

Grzegorz Ziolkowski: Yeah. I think it’s a very nice idea. It’s something that, it’s been on my mind as well, that we should have something like that already in WordPress core. So I’m glad that the community, as usual, is ready to jump in and accelerate all the explorations in that regard. So that’s brilliant. I’m looking forward to see how it plays out. And yeah, it’s something that we wanted to mention that Ryan Welcher from Automattic, he is already looking into something similar. I don’t know more about the approach he took in his tooling.

Birgit Pauli-Haack: Yeah. He’s building a plugin that you can install on a site and then you would use the block editor, the forms will show up in the block editor. So you can then do the configuration for the styles, the color settings, and all that right in your block editor. So he is also, he’s not that far yet either, but it’s all something, the two tools to watch evolve and see what is a solution that you would want to use in that regard. So I’m glad that this is going to be a thing over the holidays. And I know that John Q at one point had a site where he started something similar and both Ryan and David knew about that before they started it. But in the meantime, John Q took it offline because it wasn’t updated anymore. The theme.json schema has changed quite a bit since he started that and he wasn’t working on this project anymore. So there are two new initiatives around it. Pretty cool.

Grzegorz Ziolkowski: Yeah. It reminds me a little bit jQuery UI. So in the past, when jQuery was everything, you could use this library for components, and then there was this page that you could tweak the styles using the controls and it would generate CSS files for you. So I think standalone apps is great because of that experience that you have call canvas for you, and you can play with everything and see how it changes. Whereas the approach of using the site editor, it’s a little bit off because you don’t have all the components presented on the page. So that might be a challenge for some of the folks to use a plugin version for that. But it’s like maybe there is something in the middle, that you can combine those two and have this nice experience of using WordPress core and having the standalone experience of the next JS app that you gives you the power of all the components that you could style.

Birgit Pauli-Haack: Yeah. It’s interesting, different approaches, to see how they evolve and how they probably fit different use cases as well. And Ellen Bauer of Elma Studio, she’s a good friend of the Gutenberg Times, has been on multiple live Q and As for theme as a theme builder, and also has a great block theme in the webpress.org repository called Aino that’s A-I-N-O. And she started with Twitter spaces and having discussions around theme building, freelancing, and she sent us the dates for her next events and she will have them… so she will have one on December 16th. And that’s on the topic after the State of the Word from Matt Mullenweg, kind of discuss the thoughts from the community there. Then on December 22nd, that’s a Wednesday, it’s probably too early for US because it’s at 9:00 AM UTC, Ellen Bauer is from New Zealand. So she’s kind of very flexible in her time, but sometimes it’s going to be a real rough thing.

So 9:00 AM UTC, that’s 5:00 PM Eastern. I know people who are up there, I’m not. So how to prepare for FSE and the WordPress 5.9 release, which is going to be quite interesting. And then on December 30th at 6:00 PM UTC, 1:00 PM Eastern, it’s a casual end of 2021 WordPress recap and chat. Now I would love to give you links to all of those, but it seems that Twitter Space still has a few restrictions, and one is that you can only schedule one event in advance. So I would suggest you follow Ellen Bauer @Ellenbauer, E-L-L-E-N-B-A-U-E-R on Twitter. So you get the notification for her next events. So Twitter Spaces has kind of come really around in the WordPress community. I know that Post Status is doing quite a few Twitter Spaces. Have you any experience with Twitter Spaces?

Grzegorz Ziolkowski: So I participated yesterday, I mean, for 10 minutes maybe, but there was a React conference and afterwards they were doing as well, the session with speakers. So they were discussing some key topics that were covered during the day and discussing how the community fits in, all that pictures, other frameworks and libraries. So that was quite interesting, but I could join only SLD center, but still something that I just joined randomly because it’s like there was this blue button on the top with all the faces of participants and that caught my attention. So I like that. But as you said, the fact that you don’t know upfront, that something like that is happening is a bit annoying, I think. Although it has also some benefits because maybe that’s the whole idea to have it to something that just started because people exchange opinions on Twitter and then suddenly they can just jump in and start talking about the topic.

Birgit Pauli-Haack: Yeah. So I like it as a more casual way to connect with other people that are in your Twitter stream, or you are part of it. One restriction is that on your desktop, you can only connect as a listener. If you want to be a part of the… in speaking with the other people and have your input, you would need to be on the mobile app, the Twitter mobile app. So I don’t know if you said it, but Twitter Spaces is just audio. So that is also a lower barrier than a live stream because you don’t have to be on video. It’s almost like a group phone call, so to speak, with other people listening in, and it’s much less formal. And I like that part. Yeah. Oh, speaking of React conference, I think that we have the link for the recordings in our show notes, if you’re interested in what’s happening with React. Are there anything that stood out for you, what WordPress developers would need to know? I know I’m throwing that at you right now.

Grzegorz Ziolkowski: So one thing that they are introducing new features and they’re introducing many changes, although the way how they approach it is very nice because everything will be backward compatible, so they just follow what WordPress does in that regard, which is amazing. And they had some other plans for the next major version, which is 18, that should be released early next year. And what I found very interesting is that initially they wanted to have some sort of switch for new features that is you need to apply for a whole application, however, they changed the plan. And it’s very interesting that you will be able to just pick a subset of your application and enable one given feature.

And there’ll be a few features that you will be able to use concurrent mode, those are very technical things, but in general, they are saying that your application will work exactly the same in 99,999 percent of time, which is great. And yes, I think that there will be a few improvements that the block editor would benefit from. I cannot confirm that because we don’t have any numbers for now, but I think that in terms of performance, there will be some benefits. And yeah, and also Diego Haz had a presentation about accessibility and he was showing his Reakit library that is used inside WordPress.

So that’s an interesting part. And he also was presenting the composite component that we use in the block inserter. And he showed how the new APIs will benefit that. And so one thing that I like the most is that there will be some sort of behavior that allows you to show loaders in a very smart way. So for instance, when you show the results for the blocking set, and the block patterns, you will be able to still present the previous set of results while the new is loading and assume that’s ready, then it’ll replace that. And it’s like very nice APIs for us. So that’s very technical, very deep. And I think the block editor will benefit from that in the next releases in 2022.

Birgit Pauli-Haack: Yeah. So sounds like everything is really evolving. So now let’s get back to our immediate release. 

What’s Released – WordPress 5.9 Beta 2 and Gutenberg 12.1

So what’s released section in the Gutenberg Changelog is, well first, WordPress 5.9 Beta 2 was released on Tuesday, December 7th and the community is going to yeah, asked to really stress test this because it’s one of the latest releases and there are not a whole more to come. There is probably a Beta 3 in the works, but it’s still unclear if there should be a January 4th Beta 4 release before the release candidate comes out. But yeah, so we have the news item, the news page about the release in our show notes. And it gives you great instructions on how you can test things, especially the bug fixes that came in late there. 

And that brings us to the Gutenberg plugin release 12.1. So some of the changes were back boarded to the 5.9 WordPress core. But yeah, so what’s in the Gutenberg, 12.1? Do you want to start us off?

Grzegorz Ziolkowski: Yeah. I’m just thinking about that, if everything was back board, I mean, it will be back boarded as far as I understand that, or no, it might be already there. Yes. It it is already, sorry. I had to think how the process goes and because we are using RC of the plugin when we start cherry picking comments. So that’s like already happened this week on Monday and yeah. So I think the biggest change is that one of the blockers that was right during the time when the release date was postponed, was the experience around picking templates. And now we have a separate page for templates and it contains the list view, that contains the name and the source of the template, whether it comes from the team or maybe whether that was created by the one of the users from the site.

So that shows the list, and on the same screen, there is also a new button that is on the top right side. And it allows you to create a missing template. So let’s say you don’t have a 404 page provided by the theme, and you can just use button to create that one, that experience. Yeah. I mean, it’s like that’s the biggest change. That was something that was missing. I mean, that was in the plugin to work different in a different way. So there was a sidebar on the left side that allows you to do all those things. However, I don’t know. Do you remember why it was not included?

Enhancements

Birgit Pauli-Haack: It was in 5.8. There was a template section in the right hand sidebar. Yes. But that was because the full site editor didn’t have all the right workflow. So you are only able to edit the template that you were on though, the post or the page template, but now they have this under appearance, the additional menu. And that’s where you can look at templates as well as template parts. It’s a separate menu. And that is now available for WordPress 5.9. Another big change is, or what was missing, was that in the site editor, you were able to add blocks as well as block patterns. But now you also can add reusable blocks that you already built to add them to a template. So that was a missing piece right there. And I’m glad that’s in there now for 5.9.

Grzegorz Ziolkowski: Yeah. I think that for sure was overlooked at some point, because there’s so many features already in the post content editor that it wasn’t so easy to bring them to the site editor and it was like, each feature needs to be also evaluated, whether it makes sense in that context.

Birgit Pauli-Haack: Yeah. And I can understand that, yeah, that some features are not finished until they are evaluated for a broader usage. Like if it works in a post edit, it doesn’t mean it works that way in the site editor, so some things need to change to actually make it work for the site editor, which also kind of updates the UI or something like that. So it’s quite a complex system that is back and forth from new features to old features, to new features kind of way. It’s almost like a feedback loop that you also have with users, and you introduced few new features.

So yeah, in the global styles now it’s also possible to opt out of the default palette for the interface. So if a theme and theme JSON opts out in the default colors for a site, then those colors are not shown in the site editor sidebar, which, yeah, certainly that was a big complaint that people said, well, I don’t want users to actually be using those colors. But on the other hand, you need those colors when there is no color palette from the theme. So it, yeah, it kind of offers something, yeah. So it’s kind of an interesting problem to solve.

Grzegorz Ziolkowski: Yeah. But I guess the stats, they still exist because you could change teams and you could be using one of those core colors. So they need to be there in case you use them in one of the overridden templates or template parts, or reusable blocks or whatever. But yeah, I think also on the feature section, it’s something that is more like a developer experience. So we were talking about the schemas for theme.json that helps developers and designers when they building their teams have this hints, what given property could be, or just showing the list of possibilities. And there was change other that allows to use custom blocks. So not only the core blocks, but if you have a custom block and you could apply some style changes and do the hints, because it’s now smart enough to figure out that that’s also a block that could have some styling. So just a handy improvement for-

Birgit Pauli-Haack: Yeah, absolutely. Yeah.

Grzegorz Ziolkowski: …that use, because if you are not playing with the block Theme.json generators….

Birgit Pauli-Haack: Yeah. And that’s certainly a challenge for the Theme.json generators, to keep up with the new changes in the schema. And that’s an ongoing story about Gutenberg development that every person involved in it needs to kind of keep up with it, being theme developers or plug-in developers now, tool developers it’s… yeah. I hope it slows down a bit in, I don’t know, three or four years.

Grzegorz Ziolkowski: Yeah. At least because of backwards compatibility, some of the existing features will stay there. So that’s one good thing, but there’s so many new features coming every two weeks. So yeah.

Birgit Pauli-Haack: And so there was one other improvement, is the position of the block appenders and the behavior of it, which is really, it was a long ongoing problem for the last two or three years.

Grzegorz Ziolkowski: Yes.

Birgit Pauli-Haack: That the layout kind of jumped a little bit when the appenders come in. Appender is the plus sign where you can then add new blocks to it. And now that’s the little plus button and now you can, they are now, what is it, fixed in their positioning. And then so with the relation to the block, so they’re not underneath the block where they created those jumps and that alone is a feature that actually makes the block editor less awkward, I say, yeah.

Grzegorz Ziolkowski: Yes, yes. I mean also that helps you to, because it’s now on the bottom right side of the space that the block occupies, the parent blocks that can have blocks inside, which is really good because you exactly know where are you adding this block. Whereas before the plus sign was in many cases it was positioned in a way that you weren’t sure whether that goes to the block you want to add or just is outside. So yeah. I like that a lot. I must admit when I saw that for the first time I was a bit lost. I didn’t know what this icon is all about. I was thinking that something is misplaced, but once you learn how it works now, it’s so much better.

Birgit Pauli-Haack: Yeah. Yeah. I totally agree. Yeah. Good job everyone. And there is now a keyboard shortcut to double escape unselected blocks.

Grzegorz Ziolkowski: No, no. So you need to press escape twice.

Birgit Pauli-Haack: Okay.

Grzegorz Ziolkowski: So because now alt select all blocks, whereas one escape just makes you go out on the edit mode. So it goes outside of the single block.

Birgit Pauli-Haack: Okay.

Grzegorz Ziolkowski: So it just….

Birgit Pauli-Haack: Yeah. Does that take care of, sometimes it happens that I’m not getting out of select. I cannot edit things. And is that….

Grzegorz Ziolkowski: Yes.

Birgit Pauli-Haack: Yeah.

Grzegorz Ziolkowski: Yeah, because we have two modes. One is for browsing. I know, it’s like, what’s the name, but the idea, yeah. The one is that it’s for accessibility. When you are contained in a blog that you are editing and then when you tap, it goes to the sidebar. And when you tap it just go to the toolbar, like there’s a cycle inside the single block, whereas when you escape and you can just use arrow up down just to navigate between blocks. So that makes you faster to move between blocks if you are using keyboard a lot.

Birgit Pauli-Haack: Yeah. So I’m going to test this out over the weekend when I do the weekend edition, because that’s where I sometimes got trapped and I got out of it by just reloading the page. 

Grzegorz Ziolkowski: When you keep press enter, then you go again in the edit mode so that’s… You need to learn some of those shortcuts and just use mouse and…

Birgit Pauli-Haack: So the next thing is adjust the order of theme blocks and reorder the inserted items, the inserter items, sorry. And that has to do with the site editor and the theme blocks that are available. So the order is adjusted so you might find it on a different spot if you have been testing this before.

Grzegorz Ziolkowski: There are now so many theme blocks and you know, some of them aren’t that important. so that’s why you can see now, like on the top of that is the navigation block or site title, site logo, or the logo that you would rather prefer to use when you start thinking about building the design for your template.

Birgit Pauli-Haack: Yeah. And also, so it’s more the, oh, I did not know that it was actually a login logout block there. I just saw that because it’s now on the top.

Grzegorz Ziolkowski: Yes.

Birgit Pauli-Haack: Yeah, yeah. Awesome. Yeah. What’s next?

Grzegorz Ziolkowski: Yeah. In the block library, there is now a new block, which is comments pagination blocks. So just to explain, there is now an ongoing quark on the comments query loop, which is like more or less the same concept, like query loop, which is a technical name for the list of posts or pages or whatever post type you pick. And the idea is to replicate the same capability for designing how comments look and that pagination is one of the things that you can have with comments in the classic themes. So it’s there and the next and previous blocks for the pagination are missing still, but they should land soon. So in general, this comment square look, I would consider that very experimental in the WordPress 5.9. There will be a different block that is just wrapped around on the comment form or comment template. I don’t remember the name, but it’s just the PHP function that does everything for you and shows you the comments that you see on the single post page.

Birgit Pauli-Haack: All right. Okay, cool. Yeah. So the comments pagination block and all the other single comments blocks that are in the works, or have been released with the plugin will be in WordPress 6.0, because it’s still all experimental.

Grzegorz Ziolkowski: Yes. I mean, if everything is done, which is most likely, yes.Birgit Pauli-Haack: Okay. All right. So then there were some updates on the navigation block and now it shows its changes to the sub menu options to show an error button when relevant and then implement suitable fallback to a navigation block on the front end when there is no menu yet selected. That was something that the team experimented with quite a bit, and there are four or five PRs that are related to that. It certainly is… that’s part of the backwards compatibility also for the navigation block that if there is no menu, because it’s a new site, yeah, you still can use the navigation block and get hints on that. But it also shows you a fall back. I tested this and it was quite interesting to see that it kind of took over and showed me all the pages if I wanted to, the navigation block is coming along quite nicely. Yeah.

Grzegorz Ziolkowski: Yeah. I think they also added PHP filter in case someone doesn’t like the default behavior for the fallback. So you can opt out with that. The filter name is block under score core underscore navigation underscore render underscore fallback, quite long one. And yeah. And basically you can just opt out or just provide your own way of doing that, which is pretty nice. And also there’s a technical change, which is less important, but they decided that instead of having the navigation menu ID attribute, there will be a ref which is aligned with how usable blocks work.

Bug Fixes

Birgit Pauli-Haack: Awesome. Yeah. So next item that we want to point out is the template part block that when you convert it to a reusable block, it kind of removes the color space and layout options of the template block. That’s very interesting to kind of test out if on… I’m kind of wondering, the interesting part is because I’m wondering about the use case for that, but I think the more you use it, the more you kind of understand it much better, then there is a change to the gallery block. That’s the refactored gallery block. And now they turned on the auto migration from our version one gallery block to our version two format when the post is edited. So that’s quite nice so you don’t have to physically do anything when you open up a post or a page that has a previous gallery version. It automatically converts it to the gallery version that has each image as an image block and uses the inner block. So you have all the features of an image block also available to your gallery.

Grzegorz Ziolkowski: Yeah, it’s interesting. Although, I guess you still need to save it just to make sure that the version two is stored in the database. Although if you don’t change anything, that’s probably not that important. So, I mean, when you don’t change anything in the gallery, so you probably don’t have to save it. I haven’t tested that yet. I’m just wondering whether the save button just immediately marks itself as actionable, but you need to do something, whether just something behind the scenes until you don’t change any attribute it is just invisible. So that’s the only thing that….

Birgit Pauli-Haack: Yeah. I’m glad you mentioned that because I’m going through a few tests for the gallery block just to see how it works. And that’s certainly something to test some more. All right. What’s next? We talked about this post featured image to move the width and height controls into the dimension panel.

Grzegorz Ziolkowski: Yeah. Although this, this sounds quite technical. I mean, because it was moved to the dimension panel, is like in a different place now, I mean the width and height is just better organized now. So there’s one important things for the themes. And the change is that when you are creating the structure for the theme, before you would use block templates and the block slash template slash parts folders for your templates and template parts, and the decision was to rename those folder, the old folders you can still use them as long as you use, like you cannot mix.

So you cannot use the new name and old name, as long as you use the old names or new names everything should work as before. And there is, yeah, I think I see that you, I think that there is announcement post for that, that we will link in the notes and yes, so templates and parts, new names, shorter and better. And that is because there are upcoming features coming. It’ll be possible to have a folder for styles and folder for patterns, which is quite interesting, the patterns part, in my opinion that will be great. And yeah for styles, do you know what the plan is for styles? Would it be in there?

Birgit Pauli-Haack: Well, I think it’s a separate PHP file where you register them, and then they’re also talking about variations folders. So yeah. So if you have a block that is an image block, and you want to add additional styles, like frame to it, or a different shape of it, then those don’t have to be in the functions PHP, you can create for each pattern your own file and then have them be added to the theme rendering kind of part. Yeah. So its styles, it’s variations, and it’s block patterns that get a little bit of a better folder structure like that. 

Grzegorz Ziolkowski: Yeah. But it’s far in the future as I understand it.

Birgit Pauli-Haack: Right. Yeah. But the only part that is now in Gutenberg is the renaming of the folders for the template parts and the templates, because you don’t need the block in front of them. Yeah. There was another change that is interesting for those who use the appearance menu, that as soon you use a block-based theme that is built for full site editing, the current theme editor, where you get access to the file system on your site will be under tools. It will not be showing up in the appearance menu. It’s not disappearing, but they decided it to hide it or move it to the tools subheader so it’s not confused with the site editor template, editor, it all looks kind of the same. Naming things is really hard. And it was always a little odd that that was actually available for a user to edit the PHP files on your site and kind of render them. If you make a mistake, you render the whole site with a white screen of death, so to speak. So hiding is probably a good, or placing that under the tools menu is probably a good decision.

Grzegorz Ziolkowski: Yeah. So I just wanted to also mention from the… going back to the global styles and changes apply there. So there was one thing that is quite interesting. So there was a change to the typographic panel, so it’s now better organized. So now they call it elements. So by elements, I means there’s text, but other elements can be a link. So now they are separated in a way that you can drill down into the link and see only settings related to the link, like colors, like, I mean, in this case it’s typographic.

So you can change font size, you can change font weight, and so on. And that’s also a preparation for future changes so you will be able to register your own elements, so let’s say when you have a blog that contains a few visual parts, so that you will be able to mark that. So let’s say in the bottom, you will be able to say, I want to have special, maybe for typographic it’s not the best, but for colors there are a lot of requirements like navigation and then it can have now nested menus. So you could just start differently nested menus. And that would be like using this API. So that’s really interesting how it evolves.

Birgit Pauli-Haack: Yeah. And looking at the PR giphy that the designers use there though it has menus and submenu, or panels and then subpanels, so if you want to change the text, you click on text and then you get an additional panel. If you want to change the link, you click on link. So a it’s a multilevel user interface now, and you need to really know where things are to actually change them. But it’s going from the top and global thing to the yeah, single element part.

And yeah, it’s going to be really interesting to see what people do with that and how they find things. I know that the learn team, the learn.webpress.org team is already looking at creating videos for tutorials for all these features. So I hope… it’s unclear if they will make it to the release, but shortly after, definitely. Yeah. They will have something. It’s a whole new way of editing your site. So we all have to learn how to use it. And sometimes you don’t pick up on the interfaces intuitively unless somebody points you to, well, what was the thinking behind it, you know? So. Yeah, so what else?

Grzegorz Ziolkowski: Yeah. It’s also so powerful that the organization for that needs to be really, really complex, but it’s like as long as you use good workflows that are the same for every block, it’s something that you should learn quite quickly.

Birgit Pauli-Haack: Yeah. Consistency is definitely key for that. Yes. We talked about things, bug fixes, there are plenty of navigation block bug fixes and also for the gallery block that came out of the testing but nothing really major.

Grzegorz Ziolkowski: Yeah it’s quite expected because the navigation block is the biggest feature that is in there that was also iterated for two years. And yes, it should be in very good shape now. So I think it’s fine to have those bug fixes because it improves the experience further.

Birgit Pauli-Haack: Yeah, yeah, absolutely. Yeah. So there’s one change in the components bug fixes that daytime picker is now setting PM hours correctly. I don’t know what was wrong with it, but it sounds like times are really hard.

Grzegorz Ziolkowski: No, that one is really annoying. I think two weeks ago I ran into this issue that I wanted to post something in the afternoon, but it was published in the future, set in a few days in the morning because it wasn’t working correctly. So that’s a very important feature. So I’m glad that is fixed now.

Birgit Pauli-Haack: Yeah. Announcement. Now you don’t have to double check your times on the publishing things. 

Experiments

Yeah. And after, aside from that, there is under experiments, we find an experimental confirm dialogue. Did you see what that was about?

Grzegorz Ziolkowski: Yeah, because the browser, I mean, it’s mostly from as far as I understand that they want to remove the confirm function. That is the one that blocks you, that shows you a big popup. You need to click yes or no. It’s like the one that comes from the browser that doesn’t look good. And I guess that is one of the reasons why they want to remove that and there’s ongoing work to prepare a replacement for that. I’m not quite sure if that’s going to work in exactly the same way, because the good part about this confirm dialogue is then when you have unsafe changes in your editor, when you try to close the tab, it will just prevent that and ask you whether, are you sure that you want to continue, and I hope that this is going to be possible to replicate that using Java script. So let’s see how it goes.

Documentation

Birgit Pauli-Haack: Yeah. Yeah, I understand. Cool. And then we come to the documentation piece, documentation PRs that are in Gutenberg 12.1. And there’s some information about the block gap to theme.json and there have been improvements to the greater block tutorial in the handbook. Well, the developers responsible for the documentation also alphabetized the how to guides section, which is probably an improvement. So you can find things. And then that’s pretty much, oh, for the tools panel it’s updated the panel and read me and the stories all have been updated. And there’s also updated documentation for the pattern block category.

Grzegorz Ziolkowski: I see that there are also changes to the history page. Interesting. Just there is just a news section explaining what it is about. But yeah, if you want to check something the block at your handbook, the history page, that could be interesting to learn about inspiration and like some world post explaining the block editor, and you can learn how far it’ll….

Birgit Pauli-Haack: Yeah. It was interesting. We had a discussion when we were at the theme meetup that the interest in the block editor comes in waves. Yeah. And I’m thinking now we are in the fourth waves of having new people coming into the block editor for the first time. And it’s hard for those of us who have been with it for four years to kind of go back in three years and kind of think, okay, what was published back then that would help anybody now three years later to get started with a block editor? And it’s quite an quite a hard thing to solve when you have been so far ahead of those who are just coming in, to kind of think back into the shoes of someone who experienced the block editor for the first time. So yeah. Having a history where people can go back to read those posts is really good and helpful. See anything else that you want to talk about?

Code Quality

Grzegorz Ziolkowski: Yeah. There’s also got quality section as usual, but that are some minor changes. I think the biggest change is the reorganization in how the PHP files are structured. So there’s an ongoing effort to move some of the functions to folders that are related to the WordPress major version, because we have so many features that we still support for WordPress 5.8, 5.7, and it becomes a pain to make sure that the same features work in older version, even though the code is not in WordPress core, but yes, that helps a lot. And that help also to catch a few smaller bugs that some features weren’t fully backboarded to work with 5.9 release. So I hope that this will prevent some surprises.

Birgit Pauli-Haack: All right, well, and this concludes our Gutenberg Changelog, going through the Gutenberg plugin release. 

What’s in Active Development or Discussed

There are a few things I wanted to point out in the active development or what’s discussed. There is the Gutenberg, the themes team on WordPress, they actually, every Friday they publish a weekly roundup of theme-related discussions. And this week they published the 75th weekly roundup edition. So if you haven’t followed up on that or followed that particular way, Jeff Ong and and Jason Chris picked four topics to highlight in the post.

And so one was the new color picker that’s coming to Gutenberg. And then the online discussion on how best to add global padding and still allow for full width alignment. There are some ideas that are tested and in the post you find the links to the GitHub issues about that. And also how make the WP block style support available through the theme.JSON, to opt in instead of the functions PHP support, and then contrary to other styling, it seems that global link styles override block level styles.

So they try to find a solution for that as well. And as always the weekly roundup has a list of overview issues for various features that are in the works like the typography tools, the global styles interface, and the default theme, for instance. And then it ends with a general resource section with links to documentation and tutorials. So if you are a theme developer and you want to keep up with the Gutenberg development and the discussions around it, signing up for the theme team make blog would definitely keep you in the loop on that. And of course we have the link in the show notes.

So before we leave, I want to point out that the Twitter bot is called good first bugs, which is maintained by Ryan Welcher and it has been updated. And now you can follow along as it tweets out all the GitHub issues that are labeled good first bugs. And for the Gutenberg group, as well as for the tags in the WordPress track. So if you are ready to contribute to Gutenberg and don’t know where to start, follow that Twitter handle @goodfirstbugs and it tweets out, yeah, I don’t know how often, but several times a day, the links to those issues that are good first bugs to tackle.

Grzegorz Ziolkowski: Yeah. I’m seeing those tweets from time to time. I don’t follow the account, but it looks like it’s popular because Twitter somehow is deciding to show it. So yes, it’s a definitely very good way to identify some areas where you could contribute.

Birgit Pauli-Haack: Yeah. Of course there is a label on GitHub, so we can also share the link to the label. There’s also a good first review label, if you want to review some code, that you can do that too. You could learn a lot by reviewing somebody else’s code. And have a discussion with the developer around it. Yeah. All right. So this is the end of our show today. Let me wish you or us wish you wonderful holidays when you celebrate that and a wonderful new year. Prosperity and health to everyone. Yeah.

Grzegorz Ziolkowski: Yeah. I also wanted to wish everyone happy new year and happy release in January and all the best, by using a full site editing experience in 2022 on your WordPress websites.

Birgit Pauli-Haack: Yes. Yeah. That’s the big feature for 2022. Yes. So as always, the show notes will be published on guttenbergtimes.com/podcast. This is the 57th episode. And if you have question suggestions, or news you want us to include, send them to [email protected] that’s [email protected]. That’s an email address. You could also reach out on Twitter, and the links to that are in the show notes. My Twitter handle is @BPH, like my initials, on Twitter. And what’s your handle?

Grzegorz Ziolkowski: My handle is G-Z-I-O-L-O so if you miss us, because we don’t record in two weeks, you can just hang out with us on Twitter.

Birgit Pauli-Haack: Yes.

Grzegorz Ziolkowski: Or on GitHub, or WordPress Slack.

Birgit Pauli-Haack: Yeah. WordPress Slack, definitely. And my DMs are open. Feel free to contact me. I might not respond right away, but asynchronous, is it. All right. That’s it for the year 2021. I can’t believe it’s over. It’s not, yeah. It’s still three weeks, but yeah, it’s been a great experience. Well, thanks for listening and goodbye.

Grzegorz Ziolkowski: Thank you everyone. Goodbye.

by Birgit Pauli-Haack at December 11, 2021 10:44 PM

WPTavern: 10up Releases the Publisher Media Kit WordPress Plugin

Earlier today, version 1.0 of 10up’s Publisher Media Kit went live in the WordPress plugin directory. It is a preconfigured set of blocks and patterns for jump-starting a media kit page for small and medium-sized publications.

When I first noticed the plugin, my mind immediately jumped to press kits and branding pages for businesses. Not enough companies within the WordPress space have such pages, and it can often be hard for journalists and other writers to find information. While this plugin is geared toward publications, small businesses can still get some use out of the plugin with a few changes.

Given that WP Tavern just launched its new design yesterday, this might be an opportunity for us to lead the way. The plugin does give me a few ideas on what we could do with a similar page here on the site.

Publisher Media Kit has been tested with Twenty Twenty-One, Newspack, and several Newspack child themes. I did run it through most of those to check for compatibility, and the plugin worked admirably. However, I primarily tested it with Twenty Twenty-Two, the upcoming default WordPress theme. Aside from a few layout alignment quirks, it worked well.

The plugin automatically creates a new “Media Kit” draft page on the website once it is activated. The content is a set of pre-defined sections built from eight patterns and an accompanying Tabs block.

Partial screenshot of Media Kit page.

This allows users to quickly fill in their own content and make customizations. Once done, it is just a matter of hitting the publish button.

However, end-users can take things into their own hands by using the various patterns on any post or page of their site. The cover, stats, and questions/contact patterns work well as general-use patterns.

The plugin’s custom block patterns.

Note: I deleted a couple of the patterns from the screenshot above. For some reason, they were rendered invalid in the patterns explorer but worked fine when inserted into the content canvas.

I would love to see a standalone version of the Tabs block included with the plugin. It is showcased in the rates and digital ad specs patterns, but it is so easy to create new tabbed content that I cannot help but want to use it with other projects.

Tabs block in the editor.

It could become a popular tabs solution with a few design options like colors, borders, and typography. It is minimal at the moment, but its user experience would make for an ideal foundation for a single-block plugin.

One of my favorite things about the block system is that it makes plugins like Publisher Media Kit feasible. In the past, it was virtually impossible to ship a content-focused plugin and expect it to work with most themes, at least not without a lot of custom design work. That meant that solid solutions would often stay in-house with agencies with no ideal way of shipping them.

The standardization of blocks has bridged much of that gap. As the system continues evolving, especially with more design options, I expect to see similar plugins in the future.

by Justin Tadlock at December 11, 2021 01:23 AM under 10up

December 10, 2021

Matt: State of the Word… in person!

Update: Here’s the recording!

I’m very excited that we’ll be broadcasting the State of the Word “live from New York City” this coming Tuesday, December 14th! There will be a very small “studio audience” of community members there in person.

Recording the solo version last year was actually one of the hardest things I’ve done in a long time. It’s funny, with a live audience I can comfortably present for an hour no problem, but recording that 25 minute presentation, alone in a room staring at a camera, was an excruciating process over two days and dozens of takes. I got the advice afterward that even if you’re just staring into a camera, it can be helpful to have an “audience” of a few friends in the room.

Even more than that, though, I’m positively giddy to see some of my friends from the WordPress community in person for the first time in several years. Please join via streaming on the 14th, and also there will also be at least 20 watch parties around the globe if there’s one in your neighborhood. Looking forward to catching up, celebrating the community’s accomplishments over the last year, and hopefully raising a torch for our march toward freedom on the web in 2022.

by Matt at December 10, 2021 11:08 PM under WordPress

WPTavern: More than 200 Local Newspaper Publishers Are Suing Google and Facebook for Damages

A group of 30 companies that own more than 200 local newspapers have formed a coalition against Google and Facebook in a newly consolidated antitrust lawsuit, alleging the tech giants have manipulated the digital ad market to the detriment of local news.

The Charleston Gazette-Mail, a small West Virginia newspaper, was the first to file suit in January 2021. Doug Reynolds, managing partner at the holding company that owns several West Virginia newspapers, gave an interview to the Wall Street Journal, comparing Google and Facebook to last century’s robber barons.

“These companies are more powerful than Standard Oil in its heyday, so no one wants to be the first to take them on,” Reynolds said. “We felt the political and legal climate have moved in our favor and are ready to go ahead.”

In May, the News Media Alliance successfully filed a declaration to consolidate the newspapers’ cases and they were consolidated by a judicial panel shortly after that in the Southern District of New York.

Clayton Fitzsimmons, one of the attorneys representing the plaintiffs, told Axios their objective is “to recover past damages to newspapers” and
to “establish a new system going forward in which newspapers aren’t just competitive again, but can thrive.”

The newspapers’ collective suit echoes many of the same allegations of the antitrust suit filed against Google by Texas Attorney General Ken Paxton and nine other state attorneys general. They make a strong case for the myriad of ways that Google and Facebook have had a damaging impact on the publishing industry.

The recently unredacted complaint references internal Google documents which show that AMP pages brought 40% less revenue to publishers. The documents show that Google acknowledged that its fees are very high but the company can demand them because of its market power. One Google employee explained that “smaller publishers don’t have alternative revenue sources,” when commenting on the lack competing ad networks. The suit also alleges that Facebook and Google colluded to manipulate header bidding auctions, among many other anticompetitive practices.

Many of the small newspapers among the 200+ included in the consolidated antitrust lawsuit are using WordPress, such as the Brown County Democrat, The Delaware Gazette, Wisconsin Rapids City Times, Waupaca County News, and the Fairborn Daily Herald — to name just a few. They are doing important work, keeping their elected officials accountable and their communities informed.

As the slow death of the American newspaper forced more publications to go online-only, digital advertising was the only lifeline for these outlets. The effects of collusion and manipulation of the digital ad market fall heavy on the already beleaguered local news industry.

The consolidated cases are currently pending and could go a number of different ways. Fitzsimmons said the court could select some as bellwethers, opt to test all cases for the individual claims, or send them back to the states of origination to be tried.

by Sarah Gooding at December 10, 2021 10:37 PM under publishing industry

WordCamp Central: WordCamp Sevilla 2021 in-person! Last Tickets!

Only 2 days left for the first in-person WordCamp after pandemia!

At WordPress Sevilla, we have put hands-on work to get back together and fill the space and distance that has left us this big parenthesis opened by the pandemic.

On next December 11 and 12, the WordPress Sevilla community invites you to participate in the first in-person WordCamp, an event to meet again.

Requirements to attend

To attend WordCamp Sevilla 2021, you must meet at least one of the following requirements:

  •  have a complete vaccination schedule,
  •  have a recent negative PCR,
  •  or having passed the COVID-19 less than 3 months ago.

The program

On this occasion, our program is designed to take a look at the community’s past, to see how this time of pandemic has affected us, and how we have adapted to this new future.

We will discuss in an informal way, giving the word to anyone who, from their experience, wants to contribute new ideas for the relations, meetings, and spread of WordPress and its community.

But the highlight of this first in-person event is the special Community Day that we have prepared for Sunday, December 12. The details are yet to be defined, but if I were you, I wouldn’t miss it!

Your ticket

 For only 18 €, you will enjoy:

  • Breakfast, lunch, and even dinner.
  • Live an authentic after-party.
  • Great gifts.
  • And the human and professional warmth from the members of one of the best technological communities.

BUY YOUR TICKET

Welcome to the first in-person WordCamp since the beginning of this pandemic!

by Ana Gavilán at December 10, 2021 08:51 AM under WordCamps

Post Status: Post Status Excerpt (No. 36) — Help Needed: WordPress Docs Team

“The best documentation is written by people who are using it.” —Milana Cap

In this episode of Post Status Excerpt, Milana Cap tells David about the stark reality of the near-overwhelming workload facing the WordPress Documentation Team. Currently, about four sponsored volunteers and fewer than 10 volunteers in total make up the Docs team — a team that is assigned to manage documentation for software that powers over 43% of the web. If you have ever complained about outdated documentation or a lack of documentation for WordPress, listen to this episode.

Also: Milana shared some encouraging projects and efforts — much of which is recent and associated with the upcoming WordPress 5.9 release. Writers “shadowing” developers could be one of the keys to improving the quantity and quality of documentation in the future.

Every week Post Status Excerpt will brief you on important WordPress news — in about 15 minutes or less! Learn what's new in WordPress in a flash. ⚡

You can listen to past episodes of The Excerpt, browse all our podcasts, and don’t forget to subscribe on Spotify, Amazon Music, Google Podcasts, iTunes, Castro, YouTube, Stitcher, Player.fm, Pocket Casts, Simplecast, or by RSS. 🎧

🔗 Mentioned in the show:

🙏 Sponsor: Wordfence

Who can afford downtime, a black mark on their brand’s reputation, or the SEO impact of getting hacked? That’s why so many WordPress sites rely on the real-time protection provided by Wordfence Premium. Now, Wordfence Central offers Premium subscribers a powerful and efficient dashboard to manage security for all their sites from one central location. Try Wordfence today!

by David Bisset at December 10, 2021 07:00 AM under The Excerpt

December 09, 2021

WPTavern: WP Tavern Is Sporting a New Website Design

We are back with a brand-new edition of WP Tavern. Technically, we have a spiffy new coat of paint that I hope you all can see if viewing from your browsers. If you are reading this post via a feed reader, email, or something else, hop over to the site and check it out.

The Tavern received a few updates under the hood too. I will not go into those details, but some of you may have noticed that we are now hosted on Pressable, a hosting service owned by Automattic. Thus far, things seem to be going off without a hitch.

For posterity, the following is a screenshot of the old homepage design along with the new one:

Old Tavern design vs. new design.

This is as much your home as it is ours. We just write the articles, but you are the ones who spend time browsing the front end — actually using the website. Constructive feedback is always valued and taken into account.

A Yearlong Design Project

It is hard to imagine the last time WP Tavern was not running a WordPress theme that I built. Before joining the staff here in 2019, the website had almost always had a little piece of me tucked in.

I would have to dig back into the archives, but I know for sure it used to run a modified version of the Hybrid News theme I released in 2009 and eventually a custom child theme on top of Stargazer years later.

I created our last theme in the middle of the early block editor days, and the changes over the past two years have been like running a stress test against my skills as a developer and designer. For the most part, it held up well as we ran the latest version of the Gutenberg plugin in production. I had to fix a ton of few things here and there, but I am happy to say that the site kept chugging along.

Our last theme was aging, though, and we needed to freshen up the place. We had ideas dating back to late 2019 that we had not implemented, and it is always tough to squeeze in the time for a full-blown redesign when there is so much going on in the WordPress world. Our first priority is always sharing the news.

We were fortunate that the WordPress.com Special Projects team contacted us in November 2020 with a proposal. Their mission:

We help interesting people, organizations, and projects to have an excellent experience with WordPress.

It did not begin as a new site design project. The team had actually reached out about building a feature that I would like to bring back to the Tavern. That part of the project is not quite ready yet, so we will hold it as a surprise for the new year. Folks are gearing up for the holiday season, and there is no reason to rush it.

Our team had planned on redesigning the site ourselves. We were just waiting for Full Site Editing to launch alongside WordPress 5.7 — so, that did not happen at all.

After some back-and-forth, a group call, and a leap forward to January 2021, we were looking at design tiles. Our plans had changed. And that is part of the magical process of keeping communication open. When you surround yourself with smart people who excel at their jobs, you can end walking a path far better than the one you first set foot on.

Let us fast forward beyond logo decisions, design mockups, and the constant FSE changes throughout 2021. It was a long journey, but we finally arrived at our destination of a new and improved version of WP Tavern.

From the Tavern to the WordPress.com Special Projects team: thank you for your work and professionalism throughout this entire process.

From the Outside Looking In

Admittedly, I had reservations about the project from the beginning. I look at other developers’ code almost every day, and I usually prefer to do my own thing. It is one of the reasons I never took any of the dozens upon dozens of agency job offers over the years. I would be that one employee who would want to uproot everything on Day #1. By the end of the first couple of weeks, I would be “let go,” my employee file labeled with “does not work well with others.”

The team provided me with committer access to our development repo and used my preferred commands for the build process. It was a welcome gesture, and I was happy to know that I could change anything I needed.

But, I have not once used any of the power at my disposal.

I was comfortable feeling like we were in a partnership. Plus, every ticket I opened in the repository was handled — and I absolutely opened plenty of issues.

Relinquishing development control was a weight off of my shoulders. I quickly learned that this was a team of professionals who knew what they were doing.

Sure, there were some things I would have done differently with the code, such as modernizing some of the PHP (something that was unnecessary in the context of the project). I would have probably reorganized a few folders too. At the same time, this was an opportunity for me to learn, and I absorbed as much as I could.

Aside from wearing my student hat, I also kept my client cap on. This was the first time I had ever gotten to play that role. There were moments where I worried whether everything would work out as I scanned an unfinished project. However, most of the time, I was able to sit back and watch in awe as the team put this whole thing together.

by Justin Tadlock at December 09, 2021 10:59 PM under Tavern

Gary: WordPress and web3

Blockchain. Cryptocurrency. Ethereum. NFTs. DAOs. Smart Contracts. web3. It’s impossible to avoid the blockchain hype machine these days, but it’s often just as difficult to decipher what it all means.

On top of that, discourse around web3 is extremely polarising: everyone involved is very keen to a) pick a team, and b) get you to join their team. If you haven’t picked a team, you must be secretly with the other team.

Max Read made a compelling argument that the web3 debate is in fact two different debates:

But, OK, what is the root disagreement, exactly? The way I read it there are two broad “is web3 bullshit?” debates, not just one, centered around the following questions:

Can the blockchain do anything that other currently existing technology cannot do and/or do anything better or more efficiently than other currently existing technology?

Will the blockchain form the architecture of the internet of the future (i.e. “web3”), and/or will blockchain-native companies and organizations become important and powerful?

Max Read — Is web3 bullshit?

I’m inclined to agree with Max’s analysis here: there’s a technical question, and there’s a business/cultural question. It’s hard to separate the two when every day sees new headlines about millions of dollars being stolen or scammed; or thousands of people putting millions of dollars into highly optimistic ventures. There are extreme positives and extreme negatives happening all the time in the web3 world.

With that in mind, I want to take a step back from the day-to-day excitement of cryptocurrency and web3, and look at some of the driving philosophies espoused by the movement.

Philosophies of web3

There are a lot of differing viewpoints on web3, every individual has a slightly different take on it. There are three broad themes that stand out, however.

Decentralised

Blockchain-based technology is inherently distributed (with some esoteric caveats, but we can safely ignore them for now). In a world where the web centres around a handful of major services, where we’ve seen the harm that the likes of Facebook and YouTube can inflict on society, it’s not surprising that decentralisation would be a powerful theme drawing in anyone looking for an alternative.

Decentralisation isn’t new to the Internet, of course: it’s right there in the name. This giant set of “interconnected networks” has been decentralised from the very beginning. It’s not perfect, of course: oppressive governments can take control of the borders of their portion of the Internet, and we’ve come to rely on a handful of web services to handle the trickier parts of using the web. But fundamentally, that decentralised architecture is still there. I can still set up a web site hosted on my home computer, which anyone in the world could access.

I don’t do that, however, for the same reason that web3 isn’t immune from centralised services: Centralisation is convenient. Just as we have Facebook, or Google, or Amazon as giant centralised services on the current web, we can already see similar services appearing for web3. For payments, Coinbase has established itself as a hugely popular place exchange cryptocurrencies and traditional currencies. For NFTs, OpenSea is the service where you’ll find nearly every NFT collection. MetaMask keeps all of your crypto-based keys, tokens, and logins in a single “crypto wallet”.

Centralisation is convenient.

While web3 proponents give a lot of credence to the decentralised nature of cryptocurrency being a driver of popularity, I’m not so sure. At best, I’m inclined to think that decentralisation is table stakes these days: you can’t even get started as a global movement without a strong commitment to decentralisation.

But if decentralisation isn’t the key, what is?

Ownership

When we talk about ownership in web3, NFTs are clearly the flavour of the month, but recent research indicates that the entire NFT market is massively artificially inflated.

Rather than taking pot-shots at the NFT straw man, I think it’s more interesting to look at the idea of ownership in terms of attribution. The more powerful element of this philosophy isn’t about who owns something, it’s who created it. NFTs do something rather novel with attribution, allowing royalty payments to the original artist every time an NFT is resold. I love this aspect: royalties shouldn’t just be for movie stars, they should be for everyone.

Comparing that to the current web, take the 3 paragraphs written by Max Read that I quoted above. I was certainly under no technical obligation to show that it was a quote, to attribute it to him, or to link to the source. In fact, it would have been easier for me to just paste his words into this post, and pretend they were my own. I didn’t, of course, because I feel an ethical obligation to properly attribute the quote.

In a world where unethical actors will automatically copy/paste your content for SEO juice (indeed, I expect this blog post to show up on a bunch of these kinds of sites); where massive corporations will consume everything they can find about you, in order to advertise more effectively to you, it’s not at all surprising that people are looking for a technical solution for taking back control of their data, and for being properly attributed for their creations.

The interesting element of this philosophy isn’t about who owns something, it’s who created it.

That’s not to say that existing services discourage attribution: a core function of Twitter is retweets, a core function of Tumblr is reblogging. WordPress still supports trackbacks, even if many folks turn them off these days.

These are all blunt instruments, though, aimed at attributing an entire piece, rather than a more targeted approach. What I’d really like is a way to easily quote and attribute a small chunk of a post: 3 paragraphs (or blocks, if you want to see where I’m heading 😉), inserted into my post, linking back to where I got them from. If someone chooses to quote some of this post, I’d love to receive a pingback just for that quote, so it can be seen in the right context.

The functionality provide by Twitter and Tumblr is less of a technologically-based enforcement of attribution, and more of an example of paving the cow path: by and large, people want to properly attribute others, providing the tools to do so can easily become a fundamental part of how any software is used.

These tools only work so long as there’s an incentive to use them, however. web3 certainly provides the tools to attribute others, but much like SEO scammers copy/pasting blog posts, the economics of the NFT bubble is clearly a huge incentive to ignore those tools and ethical obligations, to the point that existing services have had to build additional features just to detect this abuse.

Monetisation

With every major blockchain also being a cryptocurrency, monetisation is at the heart of the entire web3 movement. Every level of the web3 tech stack involves a cryptocurrency-based protocol. This naturally permeates through the entire web3 ecosystem, where money becomes a major driving factor for every web3-based project.

And so, it’s impossible to look at web3 applications without also considering the financial aspect. When you have to pay just to participate, you have to ask whether every piece of content you create is “worth it”.

Again, let’s go back to the 3 paragraphs I quote above. In a theoretical web3 world, I’d publish this post on a blockchain in some form or another, and that act would also likely include noting that I’d quoted 3 blocks of text attributed to Max Read. I’d potentially pay some amount of money to Max, along with the fees that every blockchain charges in order to perform a transaction. While this process is potentially helpful to the original author at a first glance, I suspect the second and third order effects will be problematic. Having only just clicked the Publish button a few seconds earlier, I’m already some indeterminate amount of money out of pocket. Which brings me back to the question, is this post “worth it”? Will enough people tip/quote/remix/whatever me, to cover the cost of publishing? When every creative work must be viewed through a lens of financial impact, it fundamentally alters that creative process.

When you have to pay just to participate, you have to ask whether every piece of content you create is “worth it”.

Ultimately, we live in a capitalist society, and everyone deserves the opportunity to profit off their work. But by baking monetisation into the underlying infrastructure of web3, it becomes impossible to opt-out. You either have the money to participate without being concerned about the cost, or you’re going to need to weigh up every interaction by whether or not you can afford it.

Web3 Philosophies in WordPress

After breaking it all down, we can see that it’s not all black-and-white. There are some positive parts of web3, and some negative parts. Not that different to the web of today, in fact. 🙂 That’s not to say that either approach is the correct one: instead, we should be looking to learn from both, and produce something better.

Decentralised

I’ve long been a proponent of leveraging the massive install base of WordPress to provide distributed services to anyone. Years ago, I spoke about an idea called “Connected WordPress” that would do exactly that. While the idea didn’t gain a huge amount of traction at the time, the DNA of the Connected WordPress concept shares a lot of similar traits to the decentralised nature of web3.

I’m a big fan of decentralised technologies as a way for individuals to claw back power over their own data from the governments and massive corporations that would prefer to keep it all centralised, and I absolutely think we should be exploring ways to make the existing web more resistant to censorship.

At the same time, we have to acknowledge that there are certainly benefits to centralisation. As long as people have the freedom to choose how and where they participate, and centralised services are required to play nicely with self hosted sites, is there a practical difference?

I quite like how Solid allows you have it both ways, whilst maintaining control over your own data.

Ownership Attribution

Here’s the thing about attribution: you can’t enforce it with technology alone. Snapchat have indirectly demonstrated exactly this problem: in order to not lose a message, people would screenshot or record the message on their phone. In response, Snapchat implemented a feature to notify the other party when you screenshot a message from them. To avoid this, people will now use a second phone to take a photo or video of the message. While this example isn’t specifically about attribution, it demonstrates the problem that there’s no way to technologically restrict how someone interacts with content that you’ve published, once they’ve been granted access.

Instead of worrying about technical restrictions, then, we should be looking at how attribution can be made easier.

IndieWeb is a great example of how this can be done in a totally decentralised fashion.

Monetisation

I’m firmly of the opinion that monetisation of the things you create should be opt-in, rather than opt-out.

Modern society is currently obsessed with monetising everything, however. It comes in many different forms: hustle culture, side gigs, transforming hobbies into businesses, meme stocks, and cryptocurrencies: they’re all symptoms of this obsession.

I would argue that, rather than accepting as fait accompli that the next iteration of the web will be monetised to the core, we should be pushing back against this approach. Fundamentally, we should be looking to build for a post scarcity society, rather than trying to introduce scarcity where there previously was none.

While we work towards that future, we should certainly be easier for folks to monetise their work, but the current raft of cryptocurrencies just aren’t up to the task of operating as… currencies.

What Should You Do?

Well, that depends on what your priorities are. The conversations around web3 are taking up a lot of air right now, so it’s possible to get the impression web3 will be imminently replacing everything. It’s important to keep perspective on this, though. While there’s a lot of money in the web3 ecosystem right now, it’s dwarfed by the sheer size of the existing web.

If you’re excited about the hot new tech, and feeling inspired by the ideas espoused in web3 circles? Jump right in! I’m certain you’ll find something interesting to work on.

Always wanted to get into currency speculation, but didn’t want to deal with all those pesky “regulations” and “safeguards”? Boy howdy, are cryptocurrencies or NFTs the place for you. (Please don’t pretend that this paragraph is investment advice, it is nothing of the sort.)

Want to continue building stuff on the web, and you’re willing to learn new things when you need them, but are otherwise happy with your trajectory? Just keep on doing what you’re doing. Even if web3 does manage to live up to the hype, it’ll take a long time for it to be adopted by the mainstream. You’ll have years to adapt.

Final Thoughts

There are some big promises associated with web3, many of which sound very similar to the promises that were made around web 2.0, particularly around open APIs, and global interoperability. We saw what happened when those kinds of tools go wrong, and web3 doesn’t really solve those problems. It may exacerbate them in some ways, since it’s impossible to delete your data from a blockchain.

That said, (and I say this as a WordPress Core developer), just because a particular piece of software is not the optimal technical solution doesn’t mean it won’t become the most popular. Market forces can be a far stronger factor that technical superiority. There are many legitimate complaints about blockchain (including performance, bloat, fit for purpose, and security) that have been levelled against WordPress in the past, but WordPress certainly isn’t slowing down. I’m not even close to convinced that blockchain is the right technology to base the web on, but I’ve been doing this for too long to bet everything against it.

Markets can remain irrational a lot longer than you and I can remain solvent.

—A. Gary Shilling

As for me, well… 😄

I remain sceptical of web3 as it’s currently defined, but I think there’s room to change it, and to adopt the best bits into the existing web. Web 1.0 didn’t magically disappear when Web 2.0 rolled in, it adapted. Maybe we’ll look back in 10 years and say this was a time when the web fundamentally changed. Or, maybe we’ll refer to blockchain in the same breath as pets.com, and other examples from the dotcom boom of the 1990’s.

The Net interprets censorship as damage and routes around it.

—John Gilmore

This quote was originally referring to Usenet, but it’s stayed highly relevant in the decades since. I think it applies here, too: if the artificial scarcity built into web3 behaves too much like censorship, preventing people from sharing what they want to share, the internet (or, more accurately, the billions of people who interact with the internet) will just… go around it. It won’t all be smooth sailing, but we’ll continue to experiment, evolve, and adapt as it changes.

Personally, I think now is a great time for us to be embracing the values and ideals of projects like Solid, and IndieWeb. Before web3 referred to blockchains, it was more commonly used in reference to the Semantic Web, which is far more in line with WordPress’ ideals, whilst also matching many of the values prioritised by the new web3. As a major driver of the Open Web, WordPress can help people own their content in a sustainable way, engage with others on their own terms, and build communities that don’t depend on massive corporations or hand-wavy magical tech solutions.

Don’t get too caught up in the drama of whatever is the flavour of the month. I’m optimistic about the long term resilience of the internet, and I think you should be, too. 🥳

by Gary at December 09, 2021 09:16 PM under web3

WPTavern: Surge: A New Page Caching Plugin for WordPress with No Configuration Required

WordPress Core Contributor Konstantin Kovshenin has released a new page caching plugin called Surge. Searching the WordPress plugin directory, you will find hundreds of caching and cache purging plugins, but this one stands out from competitors in that it requires no configuration. The plugin starts working as soon as it’s activated, and there are no options.

What kind of performance improvements can you expect with Surge activated? Kovshenin’s tests indicate that WordPress site performance on cheap hosting can be significantly improved with the plugin:

Surge stores cache files on the filesystem, leveraging the Linux kernel page cache for efficient in-memory caching and invalidation. In various load tests, Surge has shown to easily handle 1000-2500 requests per second at 100 concurrent, on a cheap single-core virtual server with only 1 GB of memory. That’s over 70x faster than a stock WordPress install with a default theme and no plugins.

Kovshenin built Surge because he could not find a suitable plugin to work well with Sail, the CLI tool he has been developing for deploying WordPress apps to DigitalOcean.

“The biggest blocker for me was the configuration, screen after screen after screen, the amount of hoops I had to jump through just to get things working,” he said. “And sure, there are on-screen guides and wizards, video tutorials, hundreds of documentation articles, but all I wanted was a page caching plugin, not a rocket (no pun intended). I had to roll my own.”

In the interest of simplicity, Surge doesn’t even come with a “clear cache” button. Kovshenin said the plugin will automatically invalidate cached entries on various different events, such as when content is updated. He said you can toggle the plugin off and on if for some reason you need to clear the page cache.

“If you have to flush the cache, it means my invalidation is not good enough for you,” Kovshenin said in response to Twitter inquiries about no button to purge the cache. “If you do find yourself flushing the cache every once in a while, do let me know why. I’m sure there are plenty of cases I haven’t considered yet.”

When asked if Surge works with sites that have lots of dynamic content, Kovshenin said only anonymous requests are cached right now. Surge also forces some requests, such as robots.txt and favicon.ico, to be anonymous for better cacheability.

“Expanding into logged-in territory is something on my list to look at, but not going to make any promises,” he said.

I tested Surge on a few simple blog sites and found that it works as advertised. On one site it took the GTMetrix Performance score from 91% to 99%. Please note that the plugin requires PHP 7.4+.

Surge is available for free on WordPress.org. If you are already using a page caching plugin, you will need to deactivate it if you want to try Surge. Kovshenin cautioned in his announcement post that many managed WordPress hosts already have some built-in caching in place, so it may be a good idea to check with your host before adding a caching plugin.

by Sarah Gooding at December 09, 2021 02:22 AM under caching

WPTavern: Gutenberg 12.1 Fixes Block Appender Layout Shift, Adds Template List Views, and Enhances Global Styles

Earlier today, Gutenberg 12.1 landed in the WordPress plugin directory. The latest release was heavy on improvements to the user experience, including a fix for the block appender layout shift, new global styles features, and improved templates list view. Theme authors also have a new flag for enabling all appearance-related tools.

WordPress 5.9 was slated for launch today, but it has been pushed to January 25, 2022. Contributors needed more time to refine the site editor and related tools bundled alongside the release. Thus far, they are using the extra time by fixing bugs and creating an overall better user experience.

No More Layout Shift

If this was the one and only change in Gutenberg 12.1, I would have been the happiest user in the world. Fortunately, there are other nice-to-have items, but my biggest pet peeve in three years of using the block editor has now been fixed.

The block appender (those little + buttons) in the content canvas are now shown using fixed positioning. This means that when you select blocks, particularly those nested within others, the screen no longer bounces around, shifts the layout, or leaves gaps of whitespace in an otherwise-perfect section.

Appender button does not shift layout.

I know from talking to others that this has been a pain point when building complex layouts in the past. For some, they would not use the block editor at all because it was so irritating. If you fall into this camp, it is worth giving it a try once again. It is a marked improvement in the user experience.

Global Styles Improvements

Users can now define custom gradients via the color palette section in the global styles sidebar. These will be available throughout the site and are not tied to the theme.

Creating a custom gradient.

The palette also shows duotone colors under the same gradient section. However, there is not an option for creating custom duotone filters yet. It is a read-only section.

The global styles panel also splits typography options between text and link elements, opening the door for other HTML elements in the future.

Link typography section.

Users probably should not change this for links. Instead, they should generally match the surrounding text. If we get text-decoration or similar options in the future, the separation might make more sense. However, altering settings like the font-size or line-height would likely be detrimental to the design.

Templates and Template Parts Views

Gutenberg 12.1 introduces a new templates and template parts list view from the site editor. The UI for this feature has jumped around over the past few plugin versions. The list was available via the left slide-out panel in the editor for months. Then, it was removed altogether in 11.9. It reappeared between that release and 12.0.

The panel has now been scaled back to include three links for Site, Templates, and Template Parts. The first link brings up the site editor. The others display tables of existing templates.

Templates list view.

Switching between the screens feels slow at the moment. However, this is the 1.0 version of the site editor that WordPress users around the world will see. It will likely change over time. “The current iteration of the design favors simplicity and usability,” wrote Riad Benguella in the announcement post. “Iterations implementing client side navigation and mosaic view might be added in the future.”

There does not seem to be a way to add custom templates, such as a category or author archive. Clicking on the “Add New” button presents options for a Front Page and Search template when using the Twenty Twenty-Two theme.

However, adding a new template part is a much more refined process. After clicking the button to create one, users are presented with an overlay and form as shown in the following screenshot:

Creating a custom template part.

Users can give it a custom name and choose between three allowed areas: general, header, and footer. After creating a new part, users are taken to the editor.

When viewing the template part list again, it displays the user who created it and has an options dropdown (ellipsis button). Currently, the only action is to delete the part.

Template Parts list view.

I would love to see top-level templates receive the same treatment as template parts when creating a new one. While there are some slight differences between them, both are templates at the end of the day. The user experience would benefit if the creation processes matched.

Creating custom templates outside of the default list from this screen would also help designers build themes visually from the site editor.

Empty Navigation Fallback

The latest release introduced a fallback for empty Navigation menu block. Ultimately, if no menu is found, it will display the Page List block. Depending on how many pages a user’s site has, this can quickly get out of hand, as shown in the following screenshot of Twenty Twenty-Two:

Navigation block fallback with long page list.

Theme developers can overwrite this fallback via the block_core_navigation_render_fallback filter hook by either returning a false value or a set of valid child blocks for the Navigation parent. Theme authors, I invite them to make generous use of this filter hook.

Noteworthy Block Theme Items

For block theme developers, the standard template-related folders have been renamed. The old names will continue working, but authors should update the following in their themes:

  • /block-templates renamed to /templates
  • /block-template-parts renamed to /parts

This change cleans up the top-level theme directory, but it also creates a path toward more standardization in the future. There is already an open ticket for /patterns, and a /styles folder is possible.

Gutenberg 12.1 also introduces an appearanceTools flag for theme.json, allowing theme authors to enable support for all current and future border, color, spacing, and typography options. I covered this in more detail in the Gutenberg 12.0 post, which had erroneously marked the feature as bundled with the last release.

by Justin Tadlock at December 09, 2021 01:03 AM under gutenberg

December 08, 2021

WPTavern: Ask the Bartender: Is There a Starter for Building Block Themes?

I read some posts from “Ask the Bartender,” and I appreciate it a lot! Thanks. I have a question now. :)

I want to refine my WordPress theme development process, which is:

  1. To make a unique-creative design with Adobe XD or Figma.
  2. To convert it to static HTML using VS Code with Bootstrap.
  3. In WordPress, create custom post types with PODS.
  4. To convert the static HTML in WP templates with Timber.

Based on my experience, this process is the best for me, but I want to integrate my themes better with WP-Blocks.

So, my question is: is there some starter-theme ready to use with blocks as the main theme and later extend it with a child theme with my custom theme?

Federico

This question depends on one of two things: Do you want to build classic themes with block support or full-blown block themes? How you approach projects going forward will depend on the answer to that. It was unclear which direction you prefer from your question, so I will tackle both.

It also seems like you are more interested in child theming. For clarity, I consider “starter” themes a starting point for building standalone or custom parent themes. My guess is that you want something closer to a blank canvas parent theme that does not have an opinionated set of default styles.

As for your tools, I have almost zero experience with any of them. I suspect you can maintain a similar process by sticking to classic themes with block support. However, with block themes, you will likely want to switch over to visually designing in the upcoming site editor and exporting the templates. It would cut out a lot of the steps you usually take.

Classic With Block Support

I tend to hype WordPress theming with blocks, but let us be realistic. Most theme authors will not take that step forward when WordPress 5.9 rolls around. And, there is no reason for everyone to dive face-first into something that is not 100% on par with what you can build going the traditional route. So, classic themes are the safest bet for a while.

Starter themes or frameworks are a dime a dozen in the classic theming world. My advice is to continue using what suits you best. Adding block support is mostly a matter of some style adjustments and possibly a theme.json file.

If you want to ease yourself into integrating with blocks, start learning the global styles and settings system (i.e., theme.json). It works with any type of theme, so you do not have to transition entirely over to block theming if you are not ready. This also allows you to continue using whatever setup you are accustomed to with one additional file. It has also been a part of WordPress since 5.8, so you can use it now without relying on the Gutenberg plugin or waiting for 5.9 to launch.

GoDaddy’s Go theme.

If you really need a starting point or parent theme in the classic + blocks space, I recommend Go by GoDaddy. The block-first project gets routine updates, supports CoBlocks and WooCommerce, and has a large enough user base to keep the ecosystem around it going.

Building Block Themes

If you want to move forward and put yourself in a solid position for WordPress’s future, block theming is the way to go. Sooner or later, almost every theme author will need to build on top of it. In this context, it also makes it easy to answer your question. And, I have two options for you.

The go-to choice for many theme authors is to learn and build from the latest default WordPress theme. In this case, it is Twenty Twenty-Two. It was supposed to be ready by December 8, along with WordPress 5.9. However, the official release date is now January 25, 2022.

Twenty Twenty-Two screenshots.

While it has not officially launched yet, it is a solid starting point if you want to release a child theme in the next couple of months on top of the latest default.

The goal is for Twenty Twenty-Two to ship with alternate color palettes and fonts. However, this feature is not ready yet. In the meantime, these custom designs are available as child themes that you can tinker around with. They are just as good of a starting point as any.

However, you may be looking for something a bit more mature — as mature as anything can be for something yet to officially launch. Automattic’s Blockbase parent theme is the easy choice.

Custom Blockbase child theme.

Blockbase has a low-key design that makes it easy to overwrite via child themes. It was literally built for this purpose. The Automattic Theme Team rolled out the Videomaker child theme for it yesterday. That makes six altogether, which are available via the company’s WordPress.org profile. Not only is it a good starting point, but it has plenty of examples to learn from.

Plus, you do not need to dirty your hands with code if you do not want to. By installing and activating the accompanying Create Blockbase Theme plugin, you can build child themes directly from the site editor and export them.

by Justin Tadlock at December 08, 2021 12:42 AM under Ask the Bartender

December 07, 2021

WPTavern: Vizio Responds to Software Freedom Conservancy’s GPL Compliance Lawsuit: Will Not Release Source Code, Files to Move Case to US Federal Court

In October 2021, the Software Freedom Conservancy (SFC) initiated a lawsuit against Vizio, an American TV manufacturer, for shipping products with copyleft licenses but refusing to provide the source code after multiple attempts at contact since 2018.

The lawsuit is historic in its approach, because it focuses on consumer rights conferred by copyleft licenses and SFC is filing as a third-party beneficiary.

Vizio has responded by filing a request to remove the case from the California State Court and move it into US federal court. The company contends that the computer programs and source code at issue in VIZIO’s SmartCast operating system “fall within the ‘subject matter of copyright.'”

Vizio’s legal representation cited several past cases involving open source licenses that were litigated within the scope of federal copyright law:

“Although plaintiff asserts claims against VIZIO under the guise of a breach of contract claim, that claim is based solely on rights that are qualitatively equivalent to those protected by federal copyright law. It is well established that exceeding the scope of a license by violating its ‘conditions’ gives rise to a claim for copyright infringement.”

The Software Freedom Conservancy published an update on the lawsuit, speculating on Vizio’s intent based on its initial response:

Vizio filed a request to “remove” the case from California State Court (into US federal court), which indicates Vizio’s belief that consumers have no third-party beneficiary rights under copyleft. In other words, Vizio’s answer to this complaint is not to comply with the copyleft licenses, but instead imply that Software Freedom Conservancy — and all other purchasers of the devices who might want to assert their right under GPL and LGPL to complete, corresponding source — have no right to even ask for that source code.

That’s right: Vizio’s filing implies that only copyright holders, and no one else, have a right to ask for source code under the GPL and LGPL.

SFC Executive Director Karen Sandler and Policy Fellow Bradley M. Kuhn, who co-penned the update, said they expected Vizio held this position since the company ignored their requests during discussions in the past years. They characterized Vizio’s recent filing as “a disturbing step further.”

“Vizio’s strategy is to deny consumers their rights under copyleft licenses, and we intend to fight back,” SFC representatives said.

If you want to follow the progress on the case, the filings are public. SFC has paid the Pacer fees and used the Recap browser plugin to make all the documents in the case freely available via the Recap project archives.

by Sarah Gooding at December 07, 2021 10:53 PM under Software Freedom Conservancy

WordPress.org blog: WordPress 5.9 Beta 2

WordPress 5.9 Beta 2 is now available for testing!

This software version is still under development. Please do not run this software on a production site. Instead, install it on a test site, where you can try out the newest features to get a feel for how they will work on your site.

You can test the WordPress 5.9 Beta 2 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the beta version here (zip).

Option 3: When using WP-CLI to upgrade from Beta 1 to Beta 2 on a case-insensitive filesystem, please use the following command sequence:

Command One:

wp core update --version=5.9-beta1 

Command Two:

 wp core update --version=5.9-beta2 --force 

The current target for the final release of 5.9 is January 25, 2022, which is just seven weeks away. Your help testing this version is a vital part of making this release as good as it can be.

Some Highlights

Since Beta 1, 24 bugs have been fixed. Here are a few of the changes you will find in Beta 2:

  • Block Editor: Remove navigation areas (#54506)
  • Block Editor: Navigation block view JavaScript error (#54456)
  • Block Editor: Block template theme error related to child themes (#54515)
  • General: Fixing existing links to Customizer when the Site Editor is enabled (#54460)
  • Media: Media library showing only the selected image (#53765)
  • Media: Fatal error uploading media on PHP8 (#54385)
  • REST API: Add Global Styles REST API endpoints from Gutenberg into Core (#54336)

Also, note that some users testing 5.9 Beta 1 faced some fatal errors upon upgrade. In turn, these errors revealed the need for some extra work on the filesystem and upgrader. Those fatal errors are no longer a problem, and the enhancements will be part of version 6.0.

How You Can Help

Do some testing!

Testing for bugs is vital for polishing the release in the beta stage and a great way to contribute. 

If you think you’ve found a bug, please post to the Alpha/Beta area in the support forums. If you’re comfortable writing a reproducible bug report, file one on WordPress Trac. That’s also where you can find a list of known bugs.

Where can I get more information?

In the coming weeks, follow the Make WordPress Core blog for 5.9-related developer notes that cover these items in detail.

So far, contributors have fixed 305 tickets in WordPress 5.9, including 110 new features and enhancements. More bug fixes are on the way with your help through testing.

Props to @psykro, @estelaris, @hellofromtonya, @marybaum, @webcommsat, @cbringmann, @davidb, @audrasjb, and @pbiron for contributions to this post.

by Jonathan Bossenger at December 07, 2021 10:02 PM under WP releases

WordCamp Central: WordCamp Taiwan 2021 is coming on December 11-12. Get Your Free Ticket Now!

WFH (work from home) cannot stop us.
Let’s WFH (WordPress from home).

Tickets for the first-ever WordCamp Taiwan are now available! WordCamp Taiwan is a regional online WordCamp happening on December 11-12, 2021. By purchasing a ticket, you can attend the event online OR participate in a local in-person watch party of the camp organized by a local WordPress meetup group in Taiwan.

And yes – you guessed it right, tickets for WordCamp Taiwan 2021 are completely free!

The following local meetups are organizing watch parties for WordCamp Taiwan! If you are based out of Taiwan, join us for one of these events:

WordCamp Taiwan 2021 is a two-day event and has one session track and one workshop track. You can also watch live streaming for the session track on YouTube. However, our workshops are exclusive for attendees who have tickets. Check out our event schedule to learn about all the exciting sessions we have in store for you.

The online event including networking will also take place on Gather Town (a virtual networking tool). By joining us on our Gather Town space, you will be able to roam in WordCamp virtual world and connect with fellow attendees while watching sessions online. You will need a free WordCamp Taiwan ticket to gain access to our Gather Town space.

We have sold most of our available tickets already and we only have a few more tickets left. So why wait, get your ticket now, and join us for WordCamp Taiwan 2021!

We look forward to seeing you this weekend!

by Yuli Yang at December 07, 2021 05:36 AM under wordcamp

WPTavern: Gravatar Says It Was Not Hacked After “Have I Been Pwned” Service Notifies Users of a Breach

Gravatar is fielding questions today after “Have I Been Pwned,” a data breech checker service, tweeted New scraped data: Gravatar had 167M profiles scraped in Oct last year via an enumeration vector. 114M of the MD5 email address hashes were subsequently cracked and distributed alongside names and usernames. It claims 72% of these email addresses were already logged with the service.

The tweet referenced a BleepingComputer article from October 2020 titled, “Online avatar service Gravatar allows mass collection of user info,” which explains how the hashes were originally obtained. After Italian security researcher Carlo Di Dato was unable to get an answer from Gravatar, he demonstrated to the publication how one could access user data by using a numeric ID associated with each profile to fetch it. He then wrote a test script that sequentially visits profile URLs from IDs 1 to 5000 and said he was able to collect JSON data of the first 5000 Gravatar users with no issues.

Many Gravatar users were startled and upset by notices from Firefox Monitor and Have I Been Pwned this morning, stating that their information had appeared in a new data breach.

The BleepingComputer article has gained more attention after Have I Been Pwned’s disclosure today, spurring Gravatar to respond on Twitter:

Gravatar helps establish your identity online with an authenticated profile. We’re aware of the conversation online that claims Gravatar was hacked, so we want to clear up the misinformation.

Gravatar was not hacked. Our service gives you control over the data you want to share online. The data you choose to share publicly is made available via our API. Users can choose to share their full name, display name, location, email address, and a short biography.

Last year, a security researcher scraped public Gravatar data – usernames and MD5 hashes of email addresses used to reference users’ avatars by abusing our API. We immediately patched the ability to harvest the public profile data en masse. If you want to learn more about how Gravatar works or adjust the data shared on your profile, please visit Gravatar.com.

Gravatar does not consider the incident to be a data breach, which is why the service did not disclose the changes made in response to the security researcher in 2020.

The Automattic-owned service is used across WordPress websites, GitHub, Stackoverflow, and other places online. Security researchers and privacy advocates have warned about privacy attacks on Gravatar for years. Many have demonstrated how readily available user information is and how easy it is to scrape it.

In July 2013, Dominique Bongard spoke at Passwordscon in Las Vegas about De-anonymizing Members of French Political Forums. He explained how a custom crawler could be written to acquire MD5 hashes for forum users and demonstrated that an attack with custom cracking software was able to recover 70% of Gravatar users’ email addresses.

Bogard noted that de-anonymizing members of political forums can be particularly dangerous in places where the forums’ users have no constitutional right to free speech, or where participants may be likely to get harassed or attacked.

Wordfence published an advisory regarding Gravatar in 2016, which referenced Bongard’s research, as well earlier work done in 2009 where a researcher proved that he could reverse engineer ~10% of gravatar hashes into email addresses.

Wordfence founder and CEO Mark Maunder explained how using email address hashes can lead to people to googling the extracted hash to find other websites and services that an individual is using.

“For example: A user may be comfortable having their full name and profile photo appear on a website about skiing,” Maunder said. “But they may not want their name or identity exposed to the public on a website specializing in a medical condition. Someone researching this individual could extract their Gravatar hash from the skiing website along with their full name. They could then Google the hash and determine that the individual suffers from a medical condition they wanted to keep private.”

Many Gravatar users were not satisfied with the service’s explanation that all of the information users entered was public, which disqualified the incident from being labeled a breach. In the same explanation, however, the service claims the API was abused, instead of admitting that it was vulnerable and could have been better protected.

After years of researchers demonstrating that this was possible, is scraping Gravatar an unethical data acquisition because the scraper is abusing the service’s architecture? Or is it unethical that Gravatar made it possible to harvest profile data en masse for years?

“If someone is able to use an API for other than its intended purpose and can gather information which otherwise wouldn’t be available through ‘standard’ means… it’s a breach,” Twitter user @RegGBlinker commented on the matter.

Gravatar undoubtedly wants to minimize the damage done by the breach notices sent out this morning to its users, but making this an issue of semantics was not reassuring. Most users did not intend to share their Gravatar emails with whoever has the motivation to scrape the data that was exposed for harvesting. Even if that data was dumped through “abuse” of their API, it feels like a breach to those who expected that user data would not be available for distribution elsewhere.

The incident serves as a reminder that, as Gravatar emphasized today, the data users choose to share publicly is made available by the service’s API and is not private. As a user, there are risks to enjoying the convenience of not having to upload your profile photo multiple times across various websites. Publishers who want their sites to offer a more privacy-conscious option should look to alternatives like Local Gravatars or Pixel Avatars.

by Sarah Gooding at December 07, 2021 01:39 AM under gravatar

WPTavern: Videomaker Block Theme Targets Film Directors and Video Creators

Automattic’s latest Blockbase child theme landed in the WordPress.org directory today. Videomaker is aimed at film directors and video creators. I have put it through its paces in the last week as it waited for approval in the review system.

At first glance, there is not much that separates Videomaker from any other plain ol’ block theme. Aside from a different color scheme, it looks and feels like its parent, Blockbase. It takes some digging to figure out what this theme brings to the table. Once you find its block patterns, it is evident that it would work well for indie filmmakers.

WordPress block themes have a pattern-discoverability issue. I have been noticing it for a while. So many often seem lackluster until you begin tinkering with their patterns, applying them to pages, and seeing what you can build. Custom patterns are where block themes will shine the most, and these need to be front and center when a user activates one.

The most straightforward solution is for themes to bundle a custom front page template out of the box, giving users a small taste of the included patterns. Starter content could also help, but the ticket for making this compatible with block themes is still open.

I almost bypassed Videomaker because I could not see its potential. After some time with it, I enjoyed how much thought the design team put into its patterns. While the theme can be used for anything, its block patterns are specifically geared toward film directors and creators in the indie space.

The theme focuses on two areas. The first is the creator. It includes a few layouts that allow the site owner to show who they are, such as the About pattern:

About creator block pattern.

The second focus area is on the art itself. There is a full-width homepage for showcasing a trailer or film, and there are patterns for the film description, credits, and more.

One of my favorite patterns was one for a film poster. This one stood out in particular because I could have used this back in college when I was going through my filmmaker phase — no, do not ask to see my $0-budget, half-finished vampire picture. I built my film posters in Photoshop back then via on-campus computers. It would have been fun to visually edit them in WordPress.

Film poster block pattern.

The theme never overcomplicates things. It offers a variety of 16 patterns for quickly throwing together a film-related website.

I particularly like the addition of the seemingly-minor sections. For example, the Awards pattern is a simple columns layout that allows users to showcase their film’s awards:

Awards block pattern.

There is nothing especially groundbreaking about the pattern. It is just a Cover, Columns, Images, and Paragraphs. Creating something like this in the classic era would have been overly complex. Users would have likely had to input a shortcode without any chance of seeing it live, at least until they previewed the page. Or, it would have existed as a customizer option and limited to wherever the theme allowed.

Looking back, it is crazy how something so simple was so complicated in the past. With patterns, theme designers can have a lot of fun adding these little touches to their themes, and users reap the benefits.

One area that could be improved would be the addition of featured media. Creators should not be required to manually edit their video list as shown in the following pattern every time they have an update. It should simply automatically show their latest video posts.

Video grid pattern.

WordPress has allowed featured images for years, but video and audio are a no-go. I have a bookmarked ticket that proposes expanding into “featured media” from 2020. There has not been any movement toward a solution. It turns out, the Automattic Themes Team had commented about the need for featured videos when they had started work on Videomaker.

This is not an issue that is best solved via the theme. While it was easier to do with classic, PHP-based theme projects, WordPress should provide the capability out of the box.

I only found one significant issue with the theme. Its default page template currently displays both the post date and featured image. I am hazarding a guess that this was an unintentional copy-paste error during development. Typically, these items are not desirable on pages. One of the best things about block themes is that users can adjust these problems — intentional or not — via the site editor. Don’t want the post date and featured image on pages? Just remove them.

Outside of that, I like seeing the continued experimentation from the Automattic Theme Team. I am waiting to see what they tackle next.

by Justin Tadlock at December 07, 2021 12:00 AM under Reviews

Follow our RSS feed: 

WordPress Planet

This is an aggregation of blogs talking about WordPress from around the world. If you think your blog should be part of this site, send an email to Matt.

Official Blog

For official WordPress development news, check out the WordPress Core Blog.

Subscriptions

Last updated:

December 17, 2021 06:45 AM
All times are UTC.