WordPress.org

WordPress Planet

December 31, 2021

WPTavern: WP Tavern’s 2021 Year in Review

Abstract Lights by Marcus Kazmierczak

A friend prompted me to fix an issue with the WP Tavern archives page a few days ago. Not all of 2021’s posts were visible. As I glanced over the updated list, I realized our team put in a lot of work for the year.

In the day-to-day mix of things, it is easy to forget how much you have written during the year. Some of the articles are memorable and stick with you for a while. Much passes by in a blur. But, I felt a sense of pride in the work our team has put in as I scrolled through the posts.

These year-in-review posts tend to take about two days’ worth of work, gathering up all of the stats and notes and formatting them so that they are presentable. However, they are always one of my favorite articles to put together every year.

We should always take some time to remind ourselves where we have been on this journey. This makes sure we are better informed before taking our next steps. At the Tavern, that means paying attention to what content people are reading and how they are engaging with it.

So, let us just dive right into some of the 2021 highlights.

The Year in WordPress

WordPress turned 18 years old in 2021. That is a massive feat for any software, especially a CMS that consistently faces competition from newer web technologies.

Unlike last year’s three, the platform only saw two major releases this year. WordPress 5.9 was initially slated to land in early December, but it was postponed until January 25, 2022. This should give contributors more time to smooth out several wrinkles with new features.

The Gutenberg plugin was a consistent force, driving new features that would eventually make their way into core WordPress. We have covered its releases throughout the year here at the Tavern.

Matt Mullenweg recorded his annual State of the Word before a live audience in New York City in mid-December. The address focused on WordPress’s growth in the past year, a decentralized web, and version 5.9 features. He also focused on contributing to the commons. He introduced Openverse, formerly Creative Commons Search, and noted the beta launch of the WordPress photo directory.

Favorite Plugin

Newsletter Glue’s theme designer.

One of the best things about writing for WP Tavern is covering a range of new plugins every year. Unfortunately, we cannot get to them all. However, there are always a few projects that stand out in the crowded field.

Maybe it was nostalgia for a bygone era of printed family newsletters. Perhaps it is just a neat idea, but my favorite plugin of the year is Newsletter Glue.

It showcases how a small team can get a complex project off the ground via the block editor. Newsletter Glue is just over a year old, and Lesley Sim and Ahmed Fouad have created a solid product.

Favorite Theme

Eksell theme homepage

This should come as no surprise to Tavern readers. I have touted its well-rounded design and architecture on multiple occasions. Eksell by Anders Norén is my favorite theme of the year. Twenty Twenty-Two would be a close second, but it has not officially launched yet. Maybe it will reign in the year to come.

I have been on the lookout for a block theme to win this for the entire year, but none of them quite lived up to Eksell. Not even Noren’s own attempt with Tove.

Eksell plays well with blocks, supporting all current, stable advancements in WordPress theming. It is far more modern than many other classic-supported themes. And, it is just beautiful.

WP Tavern Stats

Over the past couple of years, we have increased our content output. Engagement via published comments is down, but “likes” continue climbing. The following is a table of the past three years of stats. Note that averages are per post.

2021 2020 2019
Total Posts 443 406 382
Total Comments 3,151 3,699 2,864
Avg. Comments 7.1 9.2 7.5
Total Likes 4,508 3,589 2,676
Avg. Likes 10.2 9.0 7.0
Total Words 324,842 317,231 225,117
Avg. Words 733 791 589

Of course, we moderate comments here at WP Tavern. We could let things run wild for a bump in commenting stats, but we want to continue creating an environment where people feel welcome to participate.

I am the champion of comments this year with a total of 81. I would still like to engage a bit more. That is something I will work on in the new year.

Props to the five people next in line for total comments in 2021:

  • Miroslav Glavić
  • Eric Karkovack
  • Andrew Starr
  • Steven Gliebe
  • Paul Lacey

Without you and other readers, there would be no Tavern. I hope to see more of you all and others in 2022.

Top 10 Most Viewed Stories

Sarah Gooding pretty much single-handedly broke our all-time daily views record in January, a record that had stood since 2015. It now stands at 24,887. I contributed a bit, but her coverage of WordPress.com’s website building service did the heavy lifting. And, it was not even the overall most-viewed story of the year.

The following are the articles Tavern readers viewed the most in 2021:

Top 10 Most Commented Stories

You would think that our most-read articles are those that receive the most comments. However, that is not always the case. While there is some crossover between the two lists, our readers sometimes need to be vocal on a particular topic.

Here are the top 10 most-commented posts of 2021:


I look forward to another year of delivering stories to all of our readers. The Tavern staff will see you all in 2022 for the next steps on this journey.

by Justin Tadlock at December 31, 2021 04:11 AM under Tavern

December 30, 2021

WordPress.org blog: People of WordPress: Collins Agbonghama

In this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature a website builder from Nigeria, who uses the open source WordPress platform to support his family and to share learning with others in his home country and beyond.

Collins Agbonghama

Creating a life in the WordPress Ecosystem

Collins Agbonghama started his journey to becoming a web developer by reading the football news headlines on a friend’s mobile phone. His fascination with development and learning continued to grow, and he now makes a living using WordPress and the web.

Read on to discover his story, which shows with creativity and determination you can create products and make a living using WordPress. 

Starting web building on a phone

Collins Agbonghama headshot photo

Collins began his exploration of the internet while attending Secondary School in Nigeria, or High School as it is known in some other countries. 

A friend at the school had a simple mobile phone which could browse the internet. Collins had his first introduction to the World Wide Web through access to this device. He became hooked by reading headlines on a sports site about a famous English Premier League Football Club, Chelsea, a soccer team which he has long supported.

“Being a very inquisitive person, I wanted to learn how the web works as well as have my own website. I was able to buy a classic mobile phone through the menial jobs I did after school,” he said. 

His first website was a wapsite or Wireless Application Protocol site optimized for mobile devices. 

He took to Google to learn how to actually build a site. He discovered he needed something called an ‘email address’ to sign-up for site builders. Google Search came to the rescue again, and he created the first email account for his first website.

A desire for a website was the catalyst for further learning, starting with HTML and CSS from an online provider. His interest in building sites with more advanced tools grew, and then he came across WordPress. 

Using his savings, he bought the cheapest hosting plan from a local Nigerian web host. He installed WordPress and started writing tutorials for a mobile device platform. He built the site, created the lessons, and started his entry into WordPress all on a mobile phone. 

This led to him having the confidence to start building sites for others, and he was able to earn a small income from that. 

Collins said: “I couldn’t go to the university because of my precarious financial situation. I continued to do menial jobs during the day and started learning PHP in the evenings and at night using my mobile phone via online learning platforms.”

He was later able to get an old laptop, which helped him access ebooks to learn more and practice his coding. 

Keen to share this learning, he started blogging about what he was learning on his website.  

Collins said: “I later took up a job teaching children at a school primarily because I got tired of the menial jobs and wanted to earn enough to take care of my internet data plan. After a while, I became fairly proficient in PHP and even took up a job to build a school management system.”

Using WordPress to make a living

Collins’ blog wasn’t making money through advertisements, but he discovered opportunities to write tutorials for other platforms. 

“I started writing PHP and WordPress development tutorials and got paid a few hundred dollars per article. In Nigeria, that’s quite a lot of money. I was able to improve the life and wellbeing of my family and myself,” he said.

After getting into a higher education program to study computer science, his life dramatically changed. He decided to stop writing and began to focus on building and selling WordPress plugins. His first one was a user and profile plugin for WordPress sites.

“Thankfully, after a year, it started making enough revenue for me to live pretty comfortably here in Nigeria because the cost of living here is relatively low,” he said

Today, Collins has several plugins which have given him a sustainable source of income. He’s also a Core and Translation volunteer contributor to the WordPress.org Open Source project.

I am thankful for WordPress because without it, I’m really not sure I would have been able to live a decent quality life.
Who knows what would have become of me?

Collins Agbonghama

“I am also thankful for the community. I have made lots of friends that have been very supportive and helpful in my journey.”

He added: “I tell people, life won’t give you what you want. You demand from life what you want. You make these demands by being determined and never giving up on your dreams and aspirations.

“If you are poor, perhaps because you came from a humble and poor background, it is not your fault. You can’t go back in time to change things. I implore you to be strong, determined, and work hard.”

Meet more WordPress community members in our People of WordPress series.

Contributors

Thanks to Michael Geheren (@geheren), Abha Thakor (@webcommsat), for writing this feature, to @MeherBala (@meher) for follow-ups and photo-editing, and to Chloe Bringmann (@cbringmann) and Nalini Thakor (@nalininonstopnewsuk) for the final proofing. Thank you to Collins Agbonghama (@collizo4sky) for sharing his Contributor Story.

Thanks to Josepha Haden Chomphosy (@chanthaboune), Topher DeRosia (@topher1kenobe) and others for their support of this initiative.

The People of WordPress feature is inspired by an essay originally published on HeroPress.com, a community initiative created by Topher DeRosia, which highlights people in the WordPress community who have overcome barriers. 

#HeroPress #ContributorStory

by webcommsat AbhaNonStopNewsUK at December 30, 2021 10:45 PM under People of WordPress

Post Status: Post Status Comments (No. 5) — The First Annual WordPress News Draft

“This story reminded me that big company, big money doesn't mean just more profit but can also mean big contributions.” —Aurooba Ahmed

It's the first-ever Post Status WordPress News Draft! The initial group of news “avengers” in this episode are Aurooba Ahmed, Jason Cosper, Daniel Schutzsmith, Robert Jacobi, and Lesley Sim — with David Bisset hosting. In three rounds of draft picks, this group assembled the most noteworthy or influential WordPress news stories of 2021.

Also: There was also a final “quick link” round with some interesting choices the guests brought to the table.

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: Gravity Forms

Gravity Forms is the easiest and most trusted advanced forms solution for your WordPress website. Packed with time-saving tools and features, Gravity Forms is the only WordPress form management plugin you will ever need. Stop losing valuable leads and grow your business with Gravity.

Transcript

[00:00:00] David Bisset: All right. Welcome to the first and maybe even last news draft for post status. My name is David White screen Bisset, I'll be your host this evening. We have some great panelists here this evening. Let me explain to you the concept of what's going on first. So there are sports drafts where people pick players within a group.

And at the end of the draft, these people pick the players they want, and they form these teams. Well, we are basically doing that except for WordPress news. So we have five panelists plus myself here this evening. There'll be introducing themselves in a second. They all have their top WordPress stories of 2021.

I asked what WordPress stories of 2021. They think we're the most important or the most influential that meant the most to them. So in a draft, there is an order. We have our order set. The only two rules, I think are one. You obviously can't repeat another pick once it's out. So you have go to your [00:02:00] alternate picks and you have to be specific in your pick.

So it can't be just acquisitions. It has to be a specific news story. So X acquired Y and I think there is also one more rule where it's about the story, not where it's posted from. So if X acquired, Y was taken from the Tavern, the next person can't pick the same story just because it was the new story there.

The link that they're sharing is from another source Post Status. So if we're all good on that, let's , introduce our panel and the order that was picked by random.org. Ruba, why don't we start off with you

Aurooba Ahmed: I'm Aurooba, I'm a WordPress developer, and I'm excited to be here,

David Bisset: Daniel, your name, occupation, and rank.

Daniel Schutzsmith: Daniel's Schutzsmith. I'm a web developer and get to work on things like WP live streams, directory.

David Bisset: Yeah. And next is Jason Cosper, not Cooper Cosper.

Jason Cosper: Hey, what up everybody? This is Jason Cosper, AKA fat Mullenweg. I am the [00:03:00] WordPress product advocate over at DreamHost and also I cohost WP water cooler with my friends Jason Tucker and Steve Zynga,

David Bisset: Robert Jacoby. You're up next. How's it going?

Robert Jacobi: And grade what a wonderful way to end the sort of year Robert Jacobi director of WordPress at cloud ways, a WordPress cloud manage hosting service.

David Bisset: And you go the way of the clouds last, but certainly not least. Leslie, tell us a little bit about your.

Lesley Sim: Hey, it's Leslie SIM I'm co-founder of newsletter glue.

It's a WordPress newsletter plugin and also a big Post Status fan.

David Bisset: Oh, okay. Well, that's not going to get you anywhere, but the the nice remark is appreciated. All right, let's start off with Aurooba, what is your first pick?

Aurooba Ahmed: I apologize to everyone, but it's that 5.9 was delayed. This was really, really big.

I [00:04:00] remember at the beginning of this year, complaining and complaining about 5.8 being released with half-baked features and, for developers who were working on products for clients, this was a really frustrating time. So on 5.9 was delayed because some of the features were not as you know, still needed some issues fixed in them.

That felt like we were hurt a little bit. And this was setting a precedent of never doing. A release with half big features and maybe even a president of never doing a release around December holidays. Like maybe this will just shift the whole cycle. That would be really nice. And I mean, I remember someone said that deadlines are not arbitrary and they're not, but meeting a deadline for the sake of meeting a deadline is also not a valid approach.

And I hope that we can have more discussions around that with WordPress release cycles.

David Bisset: This was not on my list, but because I only have like five or six items on my list, but I agree that this is a bit of a change. I mean, five nine would have come out. It would have come out. Guess when it [00:05:00] would have come out? On state of the word night.

Yeah, I don't know. It's certainly affecting next year somewhat because I think the schedule they're trying to talk about next year as a potential four release schedule, or at least two of the four or two of the three we've never had. I don't think we've had a release in January. I think that's potential.

That's a very good first round pick. I don't know if anybody got that, but so far I'm safe, but I think that's a very good pick. And that's one of those picks that's going to be by like maybe middle of the year next year, we're going to look back on here and say, this is how much this decision made in terms of change.

And I think it was good decision to . All right. Let's see Daniel, you're up. What's your first pick?

Daniel Schutzsmith: This happened this year and I didn't even realize it was this year was the whole profile press WP user avatar debacle. They had a. 400,000 active installs at the time. And basically I believe what happened was the company got taken over basically and renamed the plug-in [00:06:00] overnight to which it was a bit different than when it used to be.

And for those who didn't use WP use avatar, it was basically a kind of a one function type of plugin. But all of a sudden you had this profile press, which was much more involved. And it basically changed the user interface of everything. I had a few clients using it, so it was a bit of a shock. And uh, since then, I've, I believe on all those, we just got rid of it and just did something else instead.

But to me, I was looking back then, you know, what happened in the past year and 2021 and this stuck out right away. Once I realized it did happen in 2021. Yeah. Well, Collins Collins is the owner of profile press and he's a developer and owner and really nice guy. There's actually a great interview with him over on the WP minute.

That was also done around the same time. So it wasn't a malicious intent at all. I think it was just, you know, just a misstep basically in in best business practices.

David Bisset: And just goes to show you the like, I think now as we get further, along in the WordPress ecosystem, how, like, if that would've happened, maybe.[00:07:00]

Maybe with less users, maybe like four years ago. I think it wouldn't have been such a magnified or a focus type of issue. Right. So as WordPress plugins go on, you know, and people have to be really, even more careful because the audiences are getting bigger. The stakes are getting bigger. My headache medications getting bigger.

All right. But that's okay. Great. Excellent pick. So profile press debacle, unintended debacle, but debacle was Daniel's pick. And thank you very much. So, Jason what's your first pick? Yeah.

Jason Cosper: So, Aruba took my pick naturally. Yeah.

David Bisset: We have our first snipe.

This is awesome. This is like the first night.

I didn't really think we'd have one tonight.

Jason Cosper: Yeah. well, I mean, she's in the catbird seat. She is basically you know, there, first up so I applaud you for grabbing that one. So I've got to go with what was going to be my second pick, which is the WordPress performance team.

David Bisset: Ah, [00:08:00] I got sniped.

Okay.

Jason Cosper: Yeah, there we go. So I snipe with a snipe. Perfect. So as somebody who has been focused on WordPress performance through a pretty significant portion of my time in WordPress making WordPress faster, I think that it is great that we are finally seeing a focus for this on core and the people who are throwing their names in till Cruz Henry Helvetica a few other you know, just really amazing people and just the amount of activity that's happening in the performance channel or when they have their weekly team meetings is just phenomenal to me.

And it was kind of a late in the year thing, but I'm really excited to see it grow in 2022.

David Bisset: I honestly had doubts in the beginning when I first read it, that it was going to be a thing. It was a proposal when I read it first. And I'm not saying that nobody cares about performance, but it was just, I don't know.

[00:09:00] It's one of those things where I guess maybe it was too good to be true. Right. You know, one of those, one of those deals it's being Frank here, my views and opinions don't reflect those of any collective or individual Post Status and Post Status team can incorporate. Well, that's a great first. Okay.

That's a great first pick word, press performance team. And yes, I would. I would admit I was sniped on that. So Robert Jacobi, please leave me with a list I can share

Robert Jacobi: with the 2017 first pick the Chicago bears choose Mitch Trubisky.

David Bisset: That sounds like a great clam chowder too

Robert Jacobi: Rochelle wrong show.

David Bisset: Oh, that's been wrong year. Good Lord. Oh, wrong team.

Robert Jacobi: I'm going to snipe. Everyone's acquisition. Want to be. Drafts and say that the biggest acquisition news of the year was Yoast being acquired by new fold. Digital

David Bisset: hard to ignore that one.

Robert Jacobi: It's I think it's important [00:10:00] because everyone knows Yost from like, you know, community hardcore folk to end your end users and users almost got ghosted by Yoast. And I think it really shows what the WordPress economy is evolving into and no opinions here, but it's changing. And when you have a huge, acquisition by someone like new fold slash blue host, for all intents and purposes of Yoast I think it really sent up flares economic flares throughout.

WordPress ecosystem

it very few long old-school WordPress plugin companies left. And that way I think on a lot of people's lists was the first one they thought of. Yeah. I'm not going to mention the other ones, because if I say it three times, maybe like Candyman there'll be acquired or they're already acquired or they're already in the works for all I know for all we know.

Right. I think it was the suddenness of it too. [00:11:00] That was a quick one. Right. I think with the like advanced custom fields, you could see it a little bit coming, or you wondered in the back of your mind one lazy day on wonder what's. I wonder if they're ever going to be acquired some day, but I personally never felt that way with Yoast.

It's just the yellow steel was approximately nine to 12 months in the works.

David Bisset: Yeah. Which, you know, obviously for that good, you keep a secret, right? Yeah. But yeah. So, okay. Well our first acquisition pick off the tape. Fortunately for us, we've got 85,000 more acquisitions on the table. So that may be a popular one, but it's not the

Robert Jacobi: I'm following all the acquisitions with that one.

David Bisset: Oh, it's going to be a long night. So Leslie, maybe you can what's your pick first round?

Lesley Sim: So my I'm going with an acquisition related topic and it's extending insight Awesome Motives self-perpetuating marketing machine. So I think like this post was inspired because of Awesome Motives acquisition of [00:12:00] Pippins plugins, but it's called something else.

It's not called that. And so what I liked about this article was kind of how it mapped out the huge fast SEO machine that Awesome Motive is building and how Sandhills and all their plugins kind of fits into that and how it kind of, yeah, just like creates this big content marketing machine, which is hard to replicate on a smaller scale.

And I guess like people often talk about WordPress from a developer point of view. I think like most of you here are, you know, developer centric. And so I wanted to bring in marketing the marketing side of things and, you know, like talk about how begin and WP and all of the automotive blog assets plays such a big part in the WordPress ecosystem.

Like anyone who's not a WordPress professional, if they're coming into WordPress for the first time, it's likely that [00:13:00] Awesome Motives blogs will be the first point of contact into WordPress. And I think like that's really interesting to consider and also what that looks like going forward as well for the ecosystem.

David Bisset: They have a very good content management strategy I used to work there. So I can tell you if they've got a nice well-oiled machine over there and that in your right. I don't, I, you know, maybe it's just the circles that I travel with or the circles that allow me to travel with them, if you want to look at it that way.

But I don't think that gets a lot of attention, so, so great job,

Robert Jacobi: David. I think Syed likes it that way.

David Bisset: Let's quickly move on to my pick. So this was my first pick and it's a pick from the Tavern and it's specific it's Tavern. It's partly the subject material, but also because Sarah Gooding just did an excellent job.

It's amp has irreparably damaged publisher's trust in Google led incentives. This got on hacker news, which appeals to a broader audience than beyond WordPress, which is one reason why I [00:14:00] picked it. The other is if anybody remembers how amp was I'm going to say promoted at word camps. And I remember one word camp, it probably it's either 2018 one or the 19 one. Like I think it was in giant letters. Google had a huge, and they were advertised. There was other things being promoted there. But I remember all of the discussion and the effort that went into convincing developers to contribute to the amp project. I remember discussions about.

Well, it's the old automatic contribution controversy that some people like to bring up, like, you know, like it's open source, but there's so many people from this company working on it, that they have a certain level of control that is unfair or is unwarranted and so forth. And people made that case for the Google and people again, to, in that project, regardless of where, which site you fell on that.

Cause I ultimately, in the end, I think that discussion never [00:15:00] really reached an official conclusion or closure. There was a lot of talk and this kind of, regardless of how many developers were aware of what Google was doing, their trust there has been broken and it's broken today. It's going to take a very long time for Google, I think, to come into the WordPress community and open project or not, and not be looked at with a mark of suspicion, even if the developer, and I'm not even saying the developers involved with NAMP knew everything that was going on or what, or whatever was brought up. It's an excellent article by Sarah on that. And I thought it was fair and it got picked up by a wider audience. And it does address, not just Google, but you know what happens when we have companies, larger companies that are in the news because of the, you know, of antitrust or because of their worker policies or whatever, what far extent do you trust them?

Knowing that not everybody in the [00:16:00] company has the same evil intentions, what you think are evil, but how far do you trust them when it comes to the, you know, WordPress and open source projects? And I think that's a good question. And I think everybody has the right to have a different answer. So I thought it was a very thought provoking article.

So that was my first pick there.

Robert Jacobi: Even if I may, you snipe me. That was my number three pick, but I actually came at it from a different way. It was the Jeremy Keith blog post about resigning from the amp advisory committee.

David Bisset: Okay. That's another good one. Yeah. And what did you think about what stood out from you on that one?

I'll throw you a bone.

Robert Jacobi: That's what I think I've been I'm not an eight amp. Let's just call it an amp because that's what everyone else calls it. I'm not an amp fan in the first place. I don't like public content being made proprietary. And I think for Justin, all the reasons that he left are the exact reasons no one should be using amp in the first place.

I think it's bad tech for band.

David Bisset: It's a shame too. Cause I know some people that were, you had some people [00:17:00] for and against it, but in the end that I think that article combined with Sarah's excellent evaluation of it. Just really it's hard to get a lot of positive. Again, this is my opinion.

This is not an opinion of anybody else. So that was my pick. I thought it was very thought provoking and it went beyond the WordPress industry. Ruba. What is your second we're in the second round pick? What's your second pick?

Aurooba Ahmed: So I had a different second pick, but then something happened today that made me change my second pick.

And that was frost being acquired by WP engine. So the reason I had to choose this as my pick is because as a developer and as a person who use WordPress a lot and seeing all these acquisitions happen, I am wary of acquisitions. I wonder how good these bigger companies are going to be as stewards of these plugins and where are they going to take it next?

And when co when plugins and smaller companies get acquired, I tend to think, oh, okay, now this is going to [00:18:00] be more profit heavy, more money-making, less contribution, less being part of the community. But then WP engine did this thing where they acquired a commercial thing and they made it open source.

And it reminded me that big company, big money doesn't have to mean only more profits and more sales. And in fact you can have big money that brings big contributions back to the community as well. If they choose to. And it made me look at WPS. In a more positive light. So I think that was a great marketing move on their end.

David Bisset: In fact, I didn't have a chance to absorb it a lot, but I know they refunded. Everybody bought a copy, so yeah. Which in all honesty, no, I probably that was jumped, changed the engine, but I think that's a Goodwill, both there.

Robert Jacobi: Who created frost again?

David Bisset: Brian Gardner

Robert Jacobi: and Diego. That's it. Where does where's Brian work [00:19:00] now

Aurooba Ahmed: at WP engine?

Jason Cosper: Where does Nick also work now

David Bisset: WP engine.

Daniel Schutzsmith: There's something to be said too, though, for Brian Garner has a formula down for doing this because before he had studio press, that also went to

Robert Jacobi: WP engine. Oh, and PS. I love Brian Gardner he's. He's a local. WordPress supergroup because he's in the Chicago community. So that's amazing.

But you know, I don't think it's an accident that frost followed Brian to WP engine. . If you know Brian up at some other place, frost may have wound up at that other place. That's all I'm saying

David Bisset: Frost isn't even a year old or is it, I think it's barely a year old or,

Robert Jacobi: yeah, I I don't if it came out.

Yeah. I thought it came out in 21. Yeah.

David Bisset: Yeah. Okay. Well, good. That's another great acquisition picks. So new off the presses. So new and [00:20:00] still at time, Daniel. Let's see. What's your round two.

Daniel Schutzsmith: Yeah, mine's more an editorial.

David Bisset: Thank goodness. So,

Daniel Schutzsmith: so this was Paul Lacey had done rather lengthy post about his stance on WordPress, how he was going to leave in the community for a little while.

You know, I think he'll probably come back, but but it was also, you know, truly about his feeling of Gutenberg and the dichotomy between WordPress foundation and automatic and reflections on him, fishing with his father. I mean, it took you for a roller coaster and it's probably one of the most beautiful reads I had of the year in the WordPress space, which was really odd because usually we're talking about technology more than anything, and this was a little bit more human felt.

So it, you know, in, you know, everyone should really take a look at it and he voices some really good concerns. You know, concerns of again, of, what's the role of different companies and what we're doing, what's their own Gutenberg and kind of pushing forward and how that's going to reflect, you know, making websites in the future.[00:21:00]

And how do we bring people into the fold that might be having more difficulty with adopting Gutenberg or, traditionally want to be able to use page builders more often and feel like they're getting neglected or pushed out of the community? Personally aside, I mean, I think page builders are here to stay.

I don't think it's a, this or that. I think it's just an added additional kind of quality aspect that people can use, you know, to use an element or use you know, ocean's WP or something like that or oxygen. But it was a really good article and it spread like wildfire through the community.

So you actually saw a lot of people doing blog posts or other posts that were reflecting similar things and, you know, referring back to the specific posts they're over on the WP minute.

David Bisset: Okay. Great pick. Yeah. And that's why we have the people we have here tonight, because I didn't, I w I was hoping to get diverse collection of articles and not just a name, as many acquisitions as we can in the next hour.

So, but yeah, it's the heart of, and if it impacts you in a heart impacted a [00:22:00] lot of people emotionally, then that's definitely a good pick. So, Jason, what's your outreach around to here? Yeah.

Jason Cosper: I'm maybe gonna pull a Babe Ruth pointed the bleachers and call the shot that round two is going to be pretty Gutenberg heavy because my second pick is a theme dot Jason shipping with WordPress five point eight.

I think this is a really a huge deal for folks. I know that you're kind of when it comes to custom CSS and stuff like that you can either wear in CSS or json it's not really necessarily the easiest switch to make. Like if you present somebody who is a little less experienced with code however I just think that the impact of this or the amount of things that it can control with blocks is going to be massive.

And the next few versions of WordPress when five nine finally drops when you know, as [00:23:00] things mature. I just think that theme json really is going to make a huge impact on how themes are built, how child themes are belts, how like all of that basically

David Bisset: Who's doing the theme. I know that more than one person is doing it, but who's is David. Somebody is doing the theme .Json generator. Has anybody seen that? Yep. Yeah. David, what's the last name I keep forgetting. Yeah. I mean, it's looking pretty good, remember when. We had themes and then the underscore generator came out and there was another generator whose name escapes my mind right now, but it seems once we get these generators going, things accelerate.

But I think that's a really great pick because obviously theme .json is something that can be turned into a builder or tool or a companion there's so much you can do because Jason's practically human readable. That's the point of it. So I think that's, yeah, I think that's an excellent technological we'll, we'll look back in a couple of years and say, is it, you know, if we [00:24:00] have a thousand themes or variations, is it because of the theme .json and I would venture a guess.

It's going to have a heck of a lot to do with it. So that's an excellent.

Daniel Schutzsmith: And it's also setting itself up for good expansion in the future, too, of what the capabilities will be

like.

David Bisset: So it could have been hopefully extensibility. Yeah, because it could have been that could have gone a different way and not a easily readable editable, text file kind of way either.

So in fact, there's probably some things in Gutenberg that are, you know, that you have to know some deep knowledge on that. I wish they could just make it like that magically somehow as easy as adding a file. So. Excellent. Excellent pick. Okay, Robert, you're up. What's your round number two pick.

Robert Jacobi: I'm going with the, I want to extend the extensibility with open verse.

Welcome to the open verse. Now we're not adding just the code. We're extending all the media that comes in contact with work. And the acquisition [00:25:00] technically by automatic of CC search. I think part of the state Matt's state of the word is going to insanely impact what every single, you know, day-to-day user can do with audio video and who knows what else will wind up in the open verse?

David Bisset: Okay. So what is the difference between for our listeners and for maybe me, but our listeners? What is the difference between open verse and wordpress.org/photos?

Robert Jacobi: wordpress.org/photos will be a curated, subset of open verse. As I understand it from the state of the word and that'll, you know, have audio and video at some point, but let's not say it's going to be tomorrow.

So that'll be. Family-friendly the open-source friendly, the community friendly version of what open verse is because open verse will probably encapsulate a lot more content than probably wp.org can. [00:26:00]

David Bisset: Well, yeah, it's spot from creative comments. Right? So creative commons looks like they didn't have the support financially or structurally to be able to have that library automatic acquired it, brought it into the open source.

Robert Jacobi: Correct. So the library technically still exists. The creative comments, it's the whole search engine and all the infrastructure around that, because that's the hard part. Right. I could have a billion photo albums that are creative commons license zero. But if you can't find the folder, you're looking for, if you're looking for that flower or that bird, you know, you can't find it unless there's a tool to do it.

And that's the one that takes all the you know, the hit on performance. Yeah, just getting stuff done. So, I mean, that's the bigger deal at the end of the day. And I think that's where they were creative commons was having problems running that on a day-to-day basis. And you know, I'm going to give automatic and frankly, Matt kudos for that.

I mean, I think that really changes the conversation [00:27:00] about what open source means. Now it's not a geeky code thing, like GPL this GPL that now it's like, oh, I can put up a website and I can click the photos button and I'm not going to get sued for, you know, this picture of a walrus.

Aurooba Ahmed: Keep in mind that creative con open verse still has non CC zero images as well.

That's the difference between slash photos and open verse because the one on photos will only have

Robert Jacobi: CTCs. Exactly. Thanks so much Aruba. Yup. Yup. I mean, that's a huge difference. So yeah, on the open verse side, Deal with the licensing voodoo, whereas photos that's done, you can use it. Commercial pers personal edit, no attribution, whatever.

Yeah. You can do whatever you want with it. So it's become the free version of of Getty for all intensive purposes. Oh,

David Bisset: and we all know how the, how another site that rhymes with bee splash started that. And Matt likes to, [00:28:00]

Robert Jacobi: the good part is it's not being called WP slash

David Bisset: Unsplash.

Robert Jacobi: I trust Matt and automatic with what he said, state of the word, you know, about making sure open is open

David Bisset: and automatic had to be involved because they're the ones with the money in the infrastructure.

So automated the actual acquisition. And I think they had to, because it's not, it can't be just mad. It has to be in it. It needs to be a company privately.

Robert Jacobi: Well, there is a WordPress foundation, but they don't have the money to acquire anything.

David Bisset: Then you're starting to get into, there's probably reasons why legally and why it did, why I did what I had to do, but I'm just glad it's back the word they just said it was contributing it back to the, you know, they use the words contributing back to the open source project.

I mean, for all intents and purposes, I like you, I trust Matt and I trust them that the fact is they're not trying to make a buck off of this. They're not trying to take what Getty did with that certain website and turn it into something it wasn't originally intended for.

Robert Jacobi: Oh no, everyone's going to make a buck out of this.

This is the best part about of [00:29:00] even photos. It's the fact that any one can integrate this. It's Matt said it stated the word. It is open. It's an open API. Wix can use this.

David Bisset: Careful. We can only say that three times.

Robert Jacobi: What if I use the alternative, if I say Squarespace and Weebly.

David Bisset: Oh crap. There, it goes two more.

No, but you're right. Anybody can use, and they are the ones, but it's not it's like creative commons, like you said, they can do anything with it. They're just ones to maintaining the database. So I can't wait to see what like with apple, I can't wait to see what your, what you'll do with it.

And I just feel the only thing I don't like about open versus that it sounds like something else, but Matt Mullenweg thought of the name probably before mark Zuckerberg did announced it anyway.

So anyway, Leslie let's get to your number two pick. We've got some great choices here. I have you been sniped.

Lesley Sim: I have not I feel like I actually picked my picks to avoid being sniped. So I hope

David Bisset: your'e so [00:30:00] smug, I like that, it's going to be easier to take you down next round.

Lesley Sim: So my next pick is a podcast. It's called the founder's field guide and they interview met Mellon wig. The host is Patrick O'Shaughnessy. And it's it's just I'm not sure how many, sorry. I'm like flipping between zoom and the sites. I don't know if any of you listen to the podcast, but it's super cool.

And it talks. So, basically it's an hour long interview and we learn about Matt's kind of approach to WordPress. And, you know, he's talked a lot about this in the past, but it was nice to just kind of hear it in one hour long podcast. He talks about one day to work on WordPress for the rest of his life and his approach to making WordPress the open source platform or operating platform that also happens to be open source for the web and how he sees, you know, kind of the law [00:31:00] of platforms being.

As a company that's building a platform, you can only profit 5% off of the platform being built. And that's kind of like a good gauge of a thriving platform. So he uses Microsoft as an example, like he says that Microsoft benefits 5% and the platform that they built, you know, everyone else that builds on top of it gets the 95% yeah.

Profit. And I thought that was a really cool approach. I never heard him talk about that before and that, and you know, it really kind of expands your mind in terms of what he thinks is possible and what he wants, you know, like it's not going to be a cash grab, you know, at the end of the day, which and that kind of, I guess, leads into what he's doing with open verse and what we just talked about.

It really, you know, Makes you feel like you can trust the future of WordPress because he's trying to build it towards this 5%. I'm trying not to like [00:32:00] add into many different you know, the salsas as well, because then I'm going to accidentally snake other people. But you know, he's always talking about avoiding the tragedy of the comments and he's always talking about Firefox for the future and how you know, he wants more people to contribute.

And I think understanding that this is kind of where he's coming from, like wanting work has to be a platform I want to only ever have take 5% of the profit of the platform. I think that's like, yeah, just like a really good once you understand that you can make a lot of business decisions from there and be comfortable in those decisions.

David Bisset: Didn't he say and say to the word that ratio is that 5% ratio is how five of the future was five. I got that. I- if we accidentally sniped someone's specific article on that specific mention of the ratio, then I guess we've done that. But, there's, if somebody still has something to share for five for the future I'll I'll hear it, but that's yeah.

I think that's a great pick two and I haven't [00:33:00] had a chance to listen to the podcast, man. To do now, if everybody's comfortable with it, I'd like to go through one more quick round, which means share your pick and maybe give a minute explanation.

And then once we go through that, we're basically we're basically at that point going to just share real quickly in a fourth round, just basically throwing out. At that point, you don't need to explain them. They were just going to blow through it. So we're going ever perpetually faster toward the singularity rubella.

You're up next? What is, what quick now is your third and third pick and real quick, why?

Aurooba Ahmed: Oh, okay. This is not from a news place, but it's something that made a really big impact on me. I'm going to post this. It's a Twitter thread by Nicole Sullivan, where she's talking about how she doesn't want to be erased when talking about a utility classes and you know, tailwind, for example, is like a library of utility classes.

And it made me think about in our own community and we're press who we choose to [00:34:00] amplify who are the kinds of people that we choose to listen to and share more from and how that impacts. What we understand about the kind of work everyone's doing. So for example, Nicole is talking about this because people were asking, Hey, who started this whole trend?

And people are playing to all these men. And it's like, hi, I was doing this before the men, but nobody went, nobody's sharing that because lots of people chose to amplify the men and not the women doesn't mean the women aren't doing good work. It means that they're just not being amplified. It made me think a lot about like, there was a thread also on Twitter about, Hey, who are all the people like involved in all of these acquisitions?

I don't remember who put out this post Leslie matting but it was like all men. It's like, you know, there's women involved in this situation too. Let's talk about and be more mindful of who we're thinking of and who we're involving and sharing about. And that's you know, it's a topic close to [00:35:00] heart.

Cool.

David Bisset: So two things first you gave out a Twitter thread. I did not think of that. I'm we're going to go for it. It's it's I think Twitter is news it's okay. Twitter is news. And second of all, I forgot about me. I skipped myself. So real quick, remember I was at the world with that,

Robert Jacobi: Dave. We're all good.

David Bisset: Yes. But like my wife, you still have to endure me so real quick.

I'm just going backwards a little bit. I actually have a brand new pick that actually has been ma it's only been online since December 21st. So it's only been online for two days and it actually took an acquisition. I had an acquisition pick ready, but it's moved it down in terms of it's. It's a thought piece.

It's actually, I think it's a thought piece. Cause I don't he did talk with Matt, but it's not an interview. It is from protocol written by David Pierce called, and this has a click baity title, but it's the only thing that I didn't like about the article. It was. Can Matt Mullenweg [00:36:00] save the internet?

I think it's a really catchy I can see now probably the more I get into it, like sometimes writers don't get to pick their titles. Sometimes the editors or whatever's do. I thought it was a little click baity. Dan David responded by Twitter. He says, yeah, that's I, you know, I'll take that judgment then that's fine.

But as you go through that, this is not just another profile on Matt Mullenweg. At least I don't think so. The more I get into it, it is about, it does start in the beginnings where Matt was a young guy, they have a photo of him. He did upgrade parties instead of whatever kids his age were doing at that time.

And which I thought was really cool, but it really kind of lays the impression that, you know, we're in this phase right now of such closed walled gardens from Google, from Apple, from Microsoft, from all the big players, right. And even the stuff that is coming up front of all the web three technologies and the promises of that being open and ownership, there's still some controversy in that regarding how that's going.

I didn't, you know, once you realize [00:37:00] that automatic has been buying, basically one of everything it's been acquiring it, I'm going to forget some names here because I'm being put on. I didn't put, I put myself on the spot, but it's acquired that journal app. It is a quiet. Yep. It has. We talked about already how the creative comments things was basically acquired slowly, but surely it seems like Matt through automatic is acquiring one, like one piece of something that should always remain open source from various different kinds of categories.

I'm trying to remember, there's an analytics. If you go to poststatus.com/acquisition, she could probably just look at the automatic parsley. Yeah. So that's an acquisition type of fleet. So it looks like he, if you look at it and this article mentions that, but it hides it in like a history and talks about Matt and how he uses WordPress and how he will continue to use WordPress for his full-time career, or at least that's how he hopes.

But once you start reading this, you begin to realize what, and I [00:38:00] think Matt's state of the word kind of hinted that more this year than any other year, In terms of where WordPress is like Gutenberg, he says going to be bigger than he considers Gutenberg bigger than WordPress. Not just because it's a product, but because of the openness at other people can use it.

Gutenberg in of itself is in my mind. Now I'm thinking of it more like a parsley or more day one is a day one, the app I'm thinking of, it's another piece of this family of products that kind of cover what you would want to maintain an open presence on the web. Maybe social network is one thing that it hasn't been touched yet maybe, but I think maybe wordpress.org could be that too.

Who knows? But if you, so anyway, that was my more lengthier number to pick. I think that if you give it a good and fair read sometimes articles really put Matt on a pedestal in terms of things. But I think if you take a step back and realize the and tumbler too. Yes. Somebody mentioned tumbler.

Yes. That's a big one too. And we may not see all of the pieces right away, but once you read this and appreciate the acquisitions automatic [00:39:00] has been doing, I think it starts to give you at least a little bit of a different perspective. And that's why I liked it. It wasn't just another interview piece about Matt.

It was really well done. So anyway, that was my number two, epic. Sorry I got skipped. Daniel, what's your quickie number three? Oh, God, don't get it. Don't take that out of context either. All right, thanks. Sorry, go ahead.

Daniel Schutzsmith: I gotta tell you, you're making me nervous. I'm sweating bullets over here.

Cause he just started rattling off all the different acquisitions. Oh no, we got a good one. I think I got a good one.

David Bisset: You can mention some

Daniel Schutzsmith: pocket casts being acquired by automatic. To me, this was a pretty big one. This was actually on the nine to five Mac blog slash easing. That's just, you know, podcasts is a great podcast application kind of a competitor to apple podcasts and things like that.

So, you know, that's literally what I listen to on my podcast, but but they have a nice web interface to which most don't have. And so that's really, you know, been a key thing for me, being able to kind of listen to those while I'm working and during the day.

David Bisset: Okay. Yeah. And that's another thing.

Yeah, [00:40:00] like you said, that's just adding to all these, like the article I was previously talking about. Yeah. That even adds even more to it. Robert, which. At this point,

Robert Jacobi: Mr. Cassper is ahead of me.

David Bisset: Oh, I'm sorry. I'm sorry. Jason, do you switched zoom? I had my zoom windows set appropriately. Go ahead, sir. I mean,

Jason Cosper: I had to mute my video for a second to get my standout and on my apple watch.

David Bisset: I'm very sorry. Oh God, we're going through hell right now, sir, but what's your quickie?

Jason Cosper: So yeah the quick one I have is Google's flock and the federated learning of cohorts. Yeah. So, flock was a fairly large thing back in. I wanna say April may that had the electronic frontier foundation up in arms, a lot of privacy advocates up in arms.

Basically like we're replacing cookies with this like federated learning cohorts. There've been a few other proposals as well. But [00:41:00] the interesting and the WordPress spin on this is that there was a post up on the make blog about basically like, Hey, let's treat flock. Like it's a security concern.

We, we don't want people who visit our sites to be tracked. So, it seems like Google took its foot off the gas a little bit in part because of large projects like WordPress saying, Hey, hold

David Bisset: up. Yeah. And WordPress, I mean, that decision is not made by one person. Right. So Google would have, or at least Google views that as a decision made by a committee or a party or the project or the contributors.

So it's kind of hard to predict if that will go through. It's kind of hard to push that through. Right. So, yeah, I think that's an XII I've actually forgotten about that. I forgotten about flock. How can I forget such an acronym? It was a long year it's. Okay, man. I had some flock last night with my chicken was delicious, but to Google's flux just [00:42:00] doesn't need to go.

Robert, what is your, what's your quickie three.

Robert Jacobi: Gosh. I'm so like jealous of Jason's pick for flock. I even wrote about this in April and I, how did I miss that one? I called it flock. Is cash a centralized analytics of segmented humans because that's really what it was. It was just another, no, I gotta write that

David Bisset: down.

Robert Jacobi: My number three is. It's technically not a WordPress thing. Oh, that's a loud, I'm gonna, you know, upset the apple cart. I want to talk about the American airlines lawsuit of open source matters and an associated hosting company open source matters is the holding company for JeWella. As we know from the state of the word, the second largest, and really the only other top five content management system [00:43:00] you know, that's being really utilized out there.

American airlines ha earlier this year, sued open source matters because someone slash someone, created a fishing site with a joomla.com name. Because that was being light. You know, it gets an all into all that.

David Bisset: Am I drawing a blank on this? Oh my goodness.

Robert Jacobi: Oh, that's, you know, draw, it happens, you know, the WordPress space, but

David Bisset: my medication, it's not a hundred percent,

Robert Jacobi: but this is a big deal actually, because this will impact how, you know, I think at the end of the day, what happens when you license a domain name to a third party to utilize for revenue or whatever, and this is where this comes to.

So yeah, this happened the lawsuit was announced in August of this year, but actually I think some of the nitty-gritty was happening much earlier.

David Bisset: Wow. That's an, oh, well, I'll be reading this right [00:44:00] afterwards. This is news. If I saw this man, I went right by it. This is pretty, very good pick. Very good pick.

Robert Jacobi: Well, I'll be doing a deep dive of it next week.

David Bisset: Okay. Well, come up for air. Let me know when you come up for air, let's save Leslie. You're at the bottom of the three here bef before me anyway, what's your third quickie. I got to stop saying that.

Lesley Sim: My pick is broadly the introduction of the F S E outreach program that started this year. I think it was talked about last year, but it started for reals this year. And yeah, and McCarthy's been doing an amazing job. One of the things that I find constantly interesting and maybe a tiny bit irritating is how many millions of people use WordPress, but like, think of WordPress as something that happens to them, like

David Bisset: a traffic accident?

Lesley Sim: Like, you know, like when Gutenberg comes up and they're like, oh, I hit it.

You know, this [00:45:00] sucks and all that. Right. But like it's open source so everyone can have their say even, I mean, I get the people who have their essay and then get ignored. But the people who just kind of sit back and just wait for Gutenberg to happen to them or for stuff to happen to them. I'm not such a fan of that.

And so I like the FSE outreach program because it kind of goes out and tries to get people involved. It does a much better job at communicating the things that are happening next. It encourages people to do testing, like the amount of times I've seen and kind of reach out to different people in different platforms.

Just trying to get someone, anyone to come and test the next video. This is like, I don't ever want to do her job. And I'm always constantly surprised by how few people come and help tests. I think 10, definitely under 20 people is the kind of typical number which is, [00:46:00] it said right. So, so hopefully, you know, me talking about this gets more people interested in going to do it.

But yeah it's a cool thing. I like Alex seeing the livestream she's been doing and like, seeing it, like she puts out the first time I tried to do on the tests following all the instructions was it was tough. Like I realized it wasn't actually that easy to test. And I think like that's gotten better over time as well.

And yeah, so it's just kind of a cool project that I hope to see it continue next year as well.

David Bisset: Great. Well, I agree. I, like I said, I'd like to see more testing as well. So my third quickie pick is actually an acquisition one. Very quick. It was basically Awesome Motive acquired

sorry, dribble. I'm sorry. Do a blank. I wanted to make sure I got this right. It got easy digital downloads some out of acquired WP, simple pay affiliate WP. And it basically grabbed all those assets and I'm dropping the actual article is from DVB beginner, but there's also another article. A few there's few people covered this as well, but [00:47:00] I thought it was just if I had to pick one acquisition, I think this was the biggest one.

I think Sand Hills development, I know was another with bread not on Pippin, sorry. With Pippin basically short term retiring and or another old school, one there all of those products going to automotive I thought was probably the biggest shift. If I had to pick one acquisition that had a big shift, that would be definitely in my top three.

Somebody already picked one and somebody probably will also pick the other one I have in mind too. So, yeah, a lot of products underneath one, one company. I thought that was significant on multiple levels, which I won't have time to go into. So that was my third round pick. Now comes our last round, which has been called by other podcasts and I'll stick with it and see if it sticks for our first round here, it's called the, bring out your dead round, where we are not going to give any explanations.

Just simply read what you have left and let us know if anybody, if including, if you got sniped by anybody else, if you haven't mentioned already Ruba, what have you got left [00:48:00] real quick listed out for us.

Aurooba Ahmed: I got a snipe when you talked about Pippin retiring. The other thing I had was MailChimp's sail and the public draft release of cascade layers, which is going to be really big in CSS.

The gravity forms 2.5 release, which was, and ECF being acquired by delicious brains and the element tours, pricing update.

David Bisset: Oh, yeah, you got lots of good ones in there. I can't pick just one to critique on Daniel. What is your-

Robert Jacobi: element or cloud or whatever they're calling it today.

Daniel Schutzsmith: Let's see. I got sniped on the protocol article about Matt. Also got sniped on the uh amped thing there. The ones I had left were let me just bring it up. Yeah. Oh, I got snapped on the frost one too. That's right. And the man I got,

David Bisset: you got sniped a lot for being somebody who was number two on the list.

Daniel Schutzsmith: I do have a good one here though, which was our future together at post status, which was coordinator's post about taking over post status. And I had just joined Post Status, I think maybe a month before that. [00:49:00] And so that was a pretty transitional thing for me.

David Bisset: Right. Pretty good. Yeah. That obviously had impact for me for me as well.

That seemed like so long ago, but a yes, at the beginning of this year, Brian Cross guard was still owner of Post Status. So, Jason, I have, I think you're up next.

Jason Cosper: That's correct. Yeah. So, let's just get through my small handful of other articles automatic acquiring frontier. And having their founders working full-time on Gutenberg, like, Hey fantasy, like, you know, you're a cool looking project, but get out of here.

We need you for Gutenberg.

David Bisset: Yeah. They gave up their rest. They gave up what they were working on to the open source community, which basically means this is your problem then.

Jason Cosper: Yeah. It dead.

David Bisset: Well, I'm not going to say dead. Well, I mean, they gave it up to the open source community. It's kind of like leaving food out for the bears.

It's like, just don't look back and you'll just pretend the bears had a. [00:50:00]

Jason Cosper: Well, I guess to keep in the theme with the, bring out your dead it's, I'm not dead yet.

Aurooba Ahmed: It's just a fresh of stewards and they're gone and there's no transitioning team. It's dead.

Jason Cosper: So, also dropping support for internet Explorer 11 that happened this year.

Wow. Yeah. Out of self-interest WP, watercooler turned nine years old this year. 400 episodes. You know, we've been at it for awhile. I came along within the past, like four or five years. So I've only been a row along for part of that ride, but you know, it's just you run into a lot of WordPress podcasts that don't stick around that maybe only put out like 10 or 20 episodes

David Bisset: or 300 episodes is only that much, but yeah.

Right.

Jason Cosper: And the last one, a weird pick Matt Mullenweg backing open insulin open source insulin back in July. And he kind of, put his money behind [00:51:00] that. And I think that is, I mean, it's not necessarily a WordPress thing for the people who are in the WordPress community affected by type one diabetes.

It's a huge thing. But just the fact that he did that I thought was super cool.

David Bisset: Yeah. I think I remember hearing about that, but yeah I, it just, so went along with Matt personality and his view of the open web, that it wasn't a surprise when I heard about it, even if it wasn't WordPress related, but it is so nice to hear something when it comes to man, and it's not WordPress related because sometimes that's rare when it comes to our radar.

Robert bring out your dead.

Robert Jacobi: I'm going to lead with open source is broken by Christine. Daughdrill this, I liken the shaking the up and down nods of approval on this one. It I've been in the open source space for almost 20 years. And I know that open [00:52:00] source contributors are treated less than dirt until something completely explodes, cough log for J.

Then the folks all like four of them who are supporting this thing for free get yelled at for destroying the internet for like three days. And that's ridiculous. What is the, you know, the mindset of, you know, folks who have worked their tails off to make this stuff. And yeah, it's their fault because no one wants to pay them to make sure that, you know, there's, you know, syntax error somewhere keeps running.

Yeah. So look at it, look at our lives, everyone here, certainly on this calls. And certainly everyone listening to this is wholly dependent on a million billion pieces of code written by [00:53:00] folks who did it for fun for dinner, for, you know, testing the bounds of tech trying to solve a bigger puzzle, WordPress Linux, Apache, DNS, every, I mean, we could go on and on.

And the support for these communities is crap and yeah, that, you know, that's going to be. Whether it's the it's a story that no one cares about because if they cared about they'd already paying into it. So yeah. Support your open source project. Yeah, I like it. Cause it runs every minute of your day.

David Bisset: I got, when I tweeted something, once it was about like a company saying we have, we make tons of money off open source. We linked to support the open source community and the open source community says pay us. And the company says, but not like that. I like that.

Robert Jacobi: Yeah. I mean that, that's the problem.

David Bisset: All right.

Well, very good. We'll just, I'll put a pour one out for the open source contributors tonight, ladies and gentlemen, [00:54:00] as we move to our final. Leslie, what's your bring out your deads or mostly dead.

Lesley Sim: So I'm going to piggyback on what Robert just talked about. So one of my picks is Nadia. I'm going to pronounce her last name, wrong her book called working in public, the making and maintenance of open source software.

I think that might have come out last year, but let's pretend the chemo this year.

Yeah. So it's kind of, the same as what Robert talked about. It looks into open source, how it's all structured, the, you know, tiny bits of code that, that run so much of our platforms today. And interestingly, it talks also about the communities that maintain it and how different open source projects have different, have evolved to have different styles.

So for example, some. Some [00:55:00] maintainers like to be contacted on Twitter, for example, and others such as WordPress express, the city don't ever contact us on Twitter because that's not how we're able to communicate. And it just talks to about the size and the scale and the scope of open source projects and how they're all so different.

And it, it kind of actually sent us around, get hub and talks also about how much get hub has changed, how open source is run and operated any team these days. So yeah, a really good book. How do you recommend it? So that's one of my picks and I'd quickly just go through the other two. The next one is Wix.

David Bisset: The second one here, second mention. The

Lesley Sim: WP Tevin article title is “Wix takes a jab at WordPress with bewildering new marketing campaign,”.

David Bisset: I got you. Snake me, sniped him. One of my, when my, my, one of my dead ones here.

Lesley Sim: Yeah. So wix going taking a snipe at [00:56:00] WordPress. It's those army headphones though in know a bunch of people who've got them and we were just really confused.

And the last pick that I had was the white house. So I'm not American, but the white house.gov website being rebuilt in like crazy short amount of time maybe a month and completely rebuilt going from Jupiter back to WordPress and being built in Gutenberg, which I thought was really cool.

So yeah, those are my picks.

David Bisset: Yeah. And Helen actually gave a pretty good presentation of how all that went down during the word camp Europe know WordCamp US a couple of months ago she gave the full story. Well, as much as she can reveal, and the fact that they turned it around that fast was mind-boggling. That was also a snipe.

You, you pretty much slept the rest of my dad. Leslie there I had white house runs on WordPress. I also had things like proposed WordPress performance team gets Greenlight that was also taken I had the Wix one as [00:57:00] well, the marketing campaign. How could you forget that? I think the only one I have left that wasn't touched by anybody here is the WordPress economy drives more than half a trillion revenue, which was a report reported, or it was a report authored by WP engine.

And since our WordPress market share Alexa is being not the Alexa the device, but Alexa company, they supply the numbers for w three texts, market share numbers, which is where we get all of our 43%, 40%, were a little over 43% right now that shuts down in may. So if that shuts down, our ability for that market share number is going to be, I don't know if anything will take its place, but in my opinion, relying on the market share number, especially when it's going to stop.

Eventually at some point it's not a good way to, it's not a good, real quick way to tell WordPress is a success in terms of growth, in terms of all of this, we ha we relied on that number because of as easy. And, but I think what we should start doing now is looking at other places [00:58:00] to determine the strength of a WordPress the community and all of that.

And one of it is money. I thought this article really kind of, it was the first time I've think I've seen half a trillion in revenue in terms of the entire WordPress space, not just somebody like Automattic is we're 7.4. Or some which also I think was news this year. So I thought that was a pretty critical article that other people now can start to build off of and, or add to their collection of how they can tell how the WordPress ecosystem is moving along because market share, it was kind of a poor metric to begin with.

And it's, you know, the closer you get, the higher you go up, whether we're presses growth slows or not in terms of market share, it's kind of like the iPhone market share doubled every year. You know, I phoned for so more than all the I-phones previous years put together iPhone five, the same thing, but eventually that iPhone market share slowed.

But it's still making record profits. It's still doing all of these wonderful things today. And I think that's where the WordPress economy [00:59:00] is going to be. You won't see that market share number, go up, even if we have a market share number, but you're going to see all these other factors. And that's why I think the.

Article from WP engine is a good article to start thinking like that. Well, that was fantastic. Thank you everybody. I I think we had a very wonderful, diverse set. Some surprises, some things I never even read before. Let me see if I can look in slack right now. This may be Barra, edit something out.

Okay. So if you can go ahead right now and just paste the, I only need the top three. I'll get the others later. If you haven't put your top three in slack, just all you need to do is just drop the link. I'll be able to figure it out from there. And then what I'll do is I'll go through everyone, read it off, and then we'll be done.

Since I'm editing this part out anyway, and I'm waiting for Jason and Daniel, you put it in there. So we're rating waiting on Robert. Leslie. Ruba needs to just update slack real quick. This podcast episode will probably be out next [01:00:00] week. It's hard to say near the end of the year, cause we have a lot of end of year stuff going on, but I'll let you know about that.

I need a picture from every one of you at some point in the next couple of days to put in graphics for promotion for this. And I'll try to keep you updated in terms of anything else I might need from you. But I think that's basically it because we should have all the links in slack. I can order them and all of that.

If this goes well, we were hoping to get a second episode out of this with some other people who couldn't make it for this time zone too, but you are the first congratulations, no longer a draft versions, as they say, well, I should probably shouldn't use that word. Okay. Strike it. New word, newbs noobs.

There we go. This is why I have, this is why I have producers. They have poo-pooed my ideas so often. And I didn't really, I didn't say poopoo in the beginning, but they told me to say that word instead. I'm calling

Robert Jacobi: Corey right now.

David Bisset: Oh, you can come, please. It probably thinks of

Daniel Schutzsmith: you. Oh, also too. If you want to spice [01:01:00] up the podcast, you should throw in some more combat stuff like bonus round

David Bisset: finish. Well, that's why you, we should deal with the end. We should just finish it. Alright. Let's see what we got. All right. Jeff is still alive that he's only in slack. We should've just brought him on. He could have just listened. All right. So here we go. Running through the top three here. Ruba.

Yours is up there we go. Yours was the WordPress 5.9 release. It was frost being acquired and made open source and stubborn Nella utilities classes, Twitter thread. That was your three picks. Excellent picks. Daniel, your picks were you w the WP user avatar tobacco with profile press.

That was how Gutenberg has divided WordPress. That's what the article was titled. Remind me of the author again on that.

Robert Jacobi: Let

Daniel Schutzsmith: me see. I

David Bisset: don't remember. It's a long night. I'll edit this. Hopefully [01:02:00] don't worry. It's from the WP minute. I'm just remembering who policy. Okay. Thank you very much. He deserves the credit and then finally podcast app podcast acquired by automatic again, another great one of those. Acquisitions that you may not have thought of at first in 2021, but I think definitely fits into a grand scheme of things.

Let's see Jason, your top three, the WordPress performance team. That was an excellent one. The theme digests on another great one with 5.8 and Google's flock and WordPress they're pretty good. Solid picks. Robert yours were the Yoast joins the new phone, digital acquisition, the open verse announcement and the American airlines, Susan sues online publisher and host over fake website involving Joomla, which is something I'll be reading right after this.

And Leslie you're top three was the marketing machine blog post from the get elliptics.com. It was the the article about the past, the present of the future with Matt mullenweg's. And that was from my [01:03:00] podcast. Joined Colossus that the name of the podcast, or that's at least the URL where we're pointing out.

And then your last pick was the waking of, excuse me, working in public, the making in maintenance of open source software. I won't try to pronounce the author's name, but it is a book on amazon.com published in August of 2020. I thought that was a very excellent pick as well on our first book pick. So,

Lesley Sim: and also the FSC outreach program.

David Bisset: Yes. And that too, I don't know. I can't remember if that was in your quickies or your deads definitely need to be renamed. My, my final three or my big three was the amp was, has a rapidly damaged publisher's trust. And half of the credit goes to the subject matter. Half of it goes to Sarah Gooding's writing on that piece.

Ken saved the internet from the David from the protocol. Article written by David Pierce and the acquisition of automotives acquisition of easy digital downloads, [01:04:00] WP, simple pay affiliate WP, and all of that stuff from Sandhills development as well. I think that was my one acquisition pick, which I I'm surprised nobody got to Pagely, but that's fine.

They'll they? I managed

Robert Jacobi: chat, but it's just, you know, it happened so recently. And there's just so many other things that

David Bisset: I have to say it once, because it'll show up in the transcript. It'll just make everybody feel good. Yeah. We've only said Wix twice. Oh, crap.

Robert Jacobi: Well, let's say go daddy mode. What happens when you say GoDaddy three times?

David Bisset: I get a coupon in the, in my email for free months. I was thinking, so why do so ever? I know what I do on the first of.

Robert Jacobi: It's like a Sinatra. I'm going to give him a shout out for that.

David Bisset: It should, he should. It's a lots of companies did a lot of hard work this year. I will. So I want to thank my panelists and I'm going to go on the order of which they were delivered.

And please let me know as you're closing off here, where people can find you on the internet, let's start with Aurooba.

Aurooba Ahmed: I'm a [01:05:00] Aurooba.com or twitter.com/aurooba, Aurooba. Thanks for having me.

David Bisset: No, thank you for having us. I think you were one of the first people that said yes. It's very rare. Yes. When it comes to this podcast.

Yes. At least anyway Daniel where people can find you.

Daniel Schutzsmith: Yeah. Danielschutzsmith.com. You know, I do a lot of different projects, but really just find me on Twitter. So it's S C H U T Z S M I T H.

David Bisset: Great. And Jason Cosper, where can we find you? Yeah.

Jason Cosper: You can find me at Jason.Cosper.ME or on Twitter at B as in boy, O G as in girl, a H

David Bisset: like, Ooh.

Yeah, it sounds like I, yeah, something I should yell in the middle of the Costco's and see what happens. Robert trying

Robert Jacobi: to spell Jason's Twitter handle. Hold on. I'll be there. I'll be back in a minute. When I figure out all

David Bisset: the letters well, admire your a mustache in the meantime. [01:06:00] Go ahead.

Robert Jacobi: You can always reach me somewhere at cloudways.com but on Twitter at Robert Jacobi spelled like it's sounds except it's an I at the end and Robertjacobi.com.

Well, there's Jason, you know, we've got triple J who's got the Jacoby with the.

David Bisset: Yes. Yes.

Robert Jacobi: It's really supposed to be an eye.

David Bisset: I'm just telling you, we don't want to get you too mixed up. That's right. Definitely not different facial hair at the very least. And finally, Leslie, my darling, Leslie, where can people find you?

Lesley Sim: You can find me on Twitter. I'm there too much. I'm only second to you. And your means stated you can find me on Twitter at lesley_pizza, L E S L E Y underscore pizza. And you can find my plugin at newsletters new.

David Bisset: Yes, that's right. And if you need a newsletter and a plugin form, put her on the list and definitely I [01:07:00] want to thank you all for coming this evening.

This was the first time we did this first time I've done this. I think it went really well. I, we there's a lot of people doing into the year roundups. In about two weeks, you'll see everybody doing the predictions for 2020 twos. That's your, if I'll be able to do anything differently there, but I wanted to close out the year what our best picks were in a format.

That was we'll show these off on post status.com as our, as kind of like our teams, you know, this is, these are the picks that represent us and what we thought. And I think we got a really great mixture. Thank you for not turning this into acquisition. Allie, really appreciate that. I probably will be our invite by five VCs on next time.

And, you know, I'll just sit here and just, you know, watch Seinfeld or something while they rattle off all their acquisition acquisitional hires. But thank you very much for coming. And I hope you guys have a good night and I wait a minute. Let's back up. Let me re edit that. I hope all you people have a good [01:08:00] night.

All right. Thank you.

by Olivia Bisset at December 30, 2021 05:30 PM under Post Status Podcasts

WordPress Foundation: Looking back at 2021

As 2021 is coming to an end, it is time to look back at the year that was. 2021 was a challenging year for the world due to the continued spread of the COVID-19 pandemic. However, despite all the challenges, the WordPress Foundation was able to make excellent progress in its mission of educating the public about open source software and serving the public good – thanks to our global team of spirited volunteers and contributors.

Read on to find out about our various programs in 2021.

do_action charity hackathons

One of our focuses this year was to revamp our do_action program. Thanks to our hard work, do_action organizers now have a dedicated [email protected] email ID powered by Google Workspace for Non profits, which will help them in their initiatives. We also kick-started discussions to organize a global do_action charity hackathon held fully online, and we are all set to execute this idea in 2022. We also announced the return of in-person do_action hackathons after nearly 18 months of online events!

We had two do_action charity hackathons planned this year: do_action Karnataka and do_action Nigeria. do_action Karnataka was held in August 2021, where 12 volunteers worked hand-in-hand to create websites for three non profits. You can read more about the event here:

While do_action Nigeria had to be canceled due to unforeseen circumstances, the local WordPress community – led by WordPress Community Deputy Mary Job, is doing a phenomenal job on the ground by uplifting women and children through their own charitable initiatives using WordPress.

Introduction to Open source workshops

Last year, during the COVID-19 pandemic, we brought back our Introduction to Open source workshops as a way to re-engage the community and to reinforce our core mission of promoting open source software to the community. At the start of this year, we announced our plans to continue these workshops in 2021.

At the time of writing this post, we have had 11 Global Introduction to Open source workshops, which have had a total of 233 RSVPs so far. We also have our final Introduction to Open source workshop for the year scheduled for tomorrow (December 31) as well!

Learn WordPress

Learn WordPress (learn.wordpress.org) – a cross-team initiative led by the Make WordPress Training team was launched in December 2020. The initiative serves to democratize and support WordPress learning by providing high-quality WordPress learning content in different formats. At the time of publishing this post, the platform had published the following content in 2021 alone:

The contributor teams working on this project have some amazing plans for the project, and the WordPress Foundation will continue to support their work in the best way possible.


Several individuals contributed generously to the WordPress foundation this year. We would like to extend our heartfelt gratitude to all our donors who supported us in sustaining the foundation this year. Special mention to the following individuals who went above and beyond in supporting us in 2021:

Sustainer – $1000 per year

  • 10up
  • Human Made
  • Jetpack
  • Matt Mullenweg
  • Multidots, Inc
  • Sujay Pawar
  • Wordfence
  • InMotion Hosting

Sustainer – $200 per year

  • Donavon Guyot
  • Eric Kuznacic
  • Ellen and Karl Olinger
  • Pippin Williamson
  • W4
  • René Hermenau / WP Staging

The WordPress Foundation has several ambitious plans for 2022, none of which would be possible without your help. If you would like to support the WordPress Foundation and contribute to our mission of serving the public good and educating the public about open source software, please consider donating to the WordPress Foundation. Your donation goes a long way in keeping the web open. Please use the link below to donate.

Thank you for your continued support of the WordPress Foundation. Here’s wishing you all an excellent holiday season and a happy 2022!

by Hari Shanker at December 30, 2021 12:48 PM under report

WPTavern: A Throwback to the Past: Retro Winamp Block

In mid-November, I happened upon a block plugin called Retro Winamp Block. As many of our readers know, I am always on the lookout for those WordPress extensions that remind me of the era when I first started using computers and exploring the web.

The plugin seemed to fit the bill. It had “retro” in the title, so it had already piqued my interest without even installing it. It had been years since I used Winamp. The media player was first released in 1997 for Microsoft Windows and grew in popularity through the early 2000s. By the time I arrived on the scene, it had already built a massive user base. It was the best option available for creating music playlists at the time, and it was skinnable.

Winamp was popular back when the world wide web felt more alive. I still look upon it as the golden era of user creation and the blossoming of fandom. Where else could you find a collection of Brad Pitt skins for your computer’s media player? Or, One Piece? Even Super Mario?

I did not hesitate to install this throwback plugin. Unfortunately, it errored out whenever I attempted to add an audio file. So, I set it aside with a note to look at it down the road.

A few weeks later, I read WordPress lead developer Helen Hou-Sandí’s goodbye announcement to 10up, the company she had been with for a decade. With the help of Mel Choyce, co-workers Jeff Paul, Darin Kotter, and Tung Du created the Retro Winamp Block in her honor.

I checked back in on the plugin. There was an update, and the change log noted a fix for the error I had encountered. In minutes, I was able to once again experience the glory of one of the first media players I had used on my old Gateway laptop.

Retro Winamp Block in the editor.

Retro Winamp Block has does not have many options. Actually, it only has one customization that users will be interested in: the player skin. They can enter any URL for it, and over 83,000 are available via the Winamp Skin Museum.

Winamp Skin Museum.

The museum is hosted by Webamp, a project that implements an HTML5 and JavaScript of the old Winamp 2.9. 10up used it for its own Retro Winamp Block plugin.

Since installing the latest version 1.0.1 of the plugin, I have only hit one issue. The live preview in the editor is partially broken. The player floats in the same spot instead of scrolling with the page..

If I had one wish for this plugin, it would be to see the addition of Milkdrop, the popular Winamp visualizer add-on.

Winamp with Milkdrop add-on.

Mostly, I simply enjoyed this jaunt down memory lane. I even went as far as installing the latest Winamp on my computer. The original player still has a thriving community if its forums are any indication. The UI is practically unusable on my laptop, so I dropped it after listening to an old Ashlee Simpson album.

While I enjoyed the nostalgia of the old player, I want to see modern-day implementations of these types of features for WordPress. Instead of a throwback to Winamp, where is the skinnable audio block?

I put together a quick pattern to test out some ideas (code on Gist):

Cover + Audio + Social block pattern.

The background is by Jeff Golenski from WordPress Photos (this directory is already coming in handy). A few adjustments later, I had a custom-styled audio layout. However, I could not modify the audio player itself. It is just the browser default. There is no equalizer, track info, or visual flair. Just a clean, boring player that longs for someone to sprinkle a little pizazz on it.

by Justin Tadlock at December 30, 2021 02:43 AM under 10up

December 29, 2021

Post Status: Post Status Excerpt (No. 39) — WordPress 5.9: Delays, the Customizer, and Contributing

“Too many things were interrelated and we didn’t have enough people who were looking across…” —Anne McCarthy

In this episode of Post Status Excerpt, David has an informative chat with Anne McCarthy. Anne is a Developer Relations Wrangler for Automattic and (among other things) has been responsible for many of the recent videos showcasing the features of Full Site Editing and WordPress 5.9. David and Anne talk about what decisions led to the delay of WordPress 5.9, her start with Automattic, COVID's effect on core contributions, and how polished Full Site Editing might be by the end of January 2022.

Also: David asks Anne what the future of the WordPress Customizer will be in a world of Full Site Editing.

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: Gravity Forms

Gravity Forms is the easiest and most trusted advanced forms solution for your WordPress website. Packed with time-saving tools and features, Gravity Forms is the only WordPress form management plugin you will ever need. Stop losing valuable leads and grow your business with Gravity.

Transcript

David Bisset: I didn't go to the state of the word, obviously, w it was, it would take too much time away from me, tweeting fun, little memes and remarks. So I decided to stay home and it hurt your

Anne McCarthy: Twitter

David Bisset: game. Yeah. Twitter didn't ban me. So, you know, I must be on the good list. But yeah, it was, I thought it was you.

Did you did you watch it?

Anne McCarthy: I did watch it, but I will admit that I was helping with the slides that day. So what I did actually watch, I was pretty fried by the time I actually watched it.

David Bisset: How did you help with the slides?

Anne McCarthy: Just from afar. There were some demos that needed some voiceovers and designers had done two wonderful demos, but there was just no con like voiceover to explain what was actually happening.

So I jumped in to do some of those and just kind of fill filling gaps with the

David Bisset: bar.

I knew that voice sounded familiar.I mean, not every voice cause I'm like, wow, you must have had a lot of cigarettes that day for that for that voice. But no I forget his name, but we, there was a voice that I remember for one of the [00:02:00] demos that previously did, like a whole bunch of WordPress demos and he has an accent and I can't think of his name right now, but I will later…

Anne McCarthy: Oh, you're probably thinking Michael Peck.

David Bisset: Yes, that's probably

Anne McCarthy: yes, he did the 5.9 voiceover demo. And that's actually like, I don't know if you've seen a YouTube video, but there's a awesome YouTube video. That group has worked on. A WordPress YouTube channel. And he did the voice over for that. And it's like a really cool kind of throwback to the early days where he would do release videos and he like knocked it out of the park.

Pretty sure.

David Bisset: What does he do besides does all he do is voiceovers. What does he do?

Anne McCarthy: No, he works for automatic. Now. He's mainly focused, I think on a combination of probably. Brand and design stuff or a purse.com. So

we got them on loan.

David Bisset: I said, he must have, you must have been in some virtual cafeteria, regular cafeteria back then in the here.

And you're like, oh, that voice, I must have that voice.

Anne McCarthy: It's very impressive. I have a friend who has a really good radio voice. I'm always really [00:03:00] jealous. I want him to record my voicemail at some point.

David Bisset: Oh yes. Anybody with an accident? I wanted to be good. I want it on mine. My parents said I always had a great face and voice for books.

So let's talk about, let's actually talk a little bit, the videos. How did the I know you're involved in them now. I, you seem to be in the. We're going to have our IC a video. Most of the time, outside of the state of the word, it looks like you, that you are pushing them. Are you primarily the one that makes those.

Anne McCarthy: Yeah, for the YouTube videos. I have some on my personal channel that I do, I did help with the 5.9 video, mainly from a logistics wrangling, like figuring out script actually did an initial voiceover that got nixed and be like, Michael police come in here. I was very sick and Michael very graciously hopped it at the last minute, but mainly I just kind of help out in terms of.

Coming up with ideas. So sometimes with learn WordPress folks, I'll also share some like review what they're working on, but a lot of the YouTube videos on my channel are [00:04:00] just things that I find interesting or that I anticipate with the next release. We just need to get some content out there and I'm fortunate to be so.

So the project that I can share things early and from there I can then send them to folks who actually have real followings and be like, Hey, I know you're probably going to create content, but the navigation block, here's like a rundown of all the features. Here's how I'm presenting it, like do your thing.

So it actually started that way where I was just creating content as a way to actually demonstrate something for other people to kind of just. Get the word out about something new that was coming and it was easier to communicate, especially from afar using videos. I had no aspiration. It helps a lot.

Yeah. And I have zero aspirations to be like a YouTuber. I just like, I don't think I'm, you know, have the equipment or the ability to be very good at it. Like some folks are in the WordPress community, but it is fun. It's cool. I guess to have it's very visual.

It's very visual. I know a lot of people really appreciate the, like, just give me the heads up [00:05:00] in two to three minutes.

Cause I remember when I think after Gutenberg was launched, we really appreciated those two or three minute demos that was at Marcus did during the state of the words or during presentations at work camp us or something like that, where you sat down in two minutes or three minutes when you got basically.

All you needed to know. And it was, there was a wow factor there. They, you know, they look at time and space by doing this. I think that's a very good idea and I hope you continue. Yeah, I plan to, so

yeah, I appreciate that because I've got a lot of encouragement from Paul AC and Nathan Wrigley, and they were both like, you should do it, but you'd be fine.

And I was like, I don't know, like, I don't think I have the time or I don't think it's like saying that I would be very good at. And I've gotten good feedback where people are kind of like what you're saying was like, I need to see the visual and also. Who is so close to the project on a day-to-day basis.

It's like, give me the little details. Like, I don't want to just see it at a high level. Give me the like bells and [00:06:00] whistles. So it's kind of a, it's a cool, neat way to connect with folks too. I've gotten this just this week. I had like three or four people reach out and my contact form, like, Hey, I watched your video about this.

Like, can you help me with facts?

David Bisset: Oh great, I'm a support person now! Yeah. Now. But it's, you know, in the beginning was so easy to see the mess because there were massive changes or adjustments happening to Gutenberg, but, and there still are, but now things are being tweaked and being refined. And over a post status, Courtney produces like every week she produced.

So this is the list of things that are happening in core. And of course, a lot of it's Gutenberg related. Yeah. And, you know, share, feel free to share with me your thoughts on this is it. I think it's becoming a little bit harder now to gauge a lot, unless it's a big headline feature and full site editing.

We can get into that unless it's a headlined feature that you've been hearing about. I think, you know, when I do the summaries and do the post for post status and what little time I have to review the text, which is in a [00:07:00] make.wordpress.org document. It's kind of hard to visualize a lot of that.

And therefore it's kind of hard for anyone outside of maybe two or three dozen people to really communicate and train, you know, translate that excitement to other people or to show how much progress is being made. Because you read a bullet list and it's, you don't know, you don't know how much work is happening behind those bullet lists for starters.

And then, you know, something could do something very cool visually, but if it's just on a bullet list on make.wordpress.org, the public not gonna see that.

Anne McCarthy: Yeah, no, I think you're right about that. And that's one of the things I don't know if you've noticed, but in the last year or so the designs and like the visuals that had come with the what's new in Gutenberg posts have definitely been upgraded because of that exact problem is it's like, show me the value, show me how it actually connects, how it makes my life easier.

And there's also a series of posts. I do the core editor improvement posts. Yeah, that also seeks to even highlight that more. And it started out as like highlighting individual things. And recently I've [00:08:00] actually had to switch to not have to, but it actually makes sense to switch to like a collection of improvement.

So I have a post right now that I'm working on with a couple of folks. On like performance at 5.9. So let's talk about the performance enhancements. Let's run through it in one place so you can see it. Yeah.

David Bisset: You've given me a topic to talk to you about. Thank you. But to some somebody's credit though, and I think when they do the Gutenberg plugin, Release posts.

They do offer him graphics and they've gotten better with videos. I just wish everything was an animated GIF so I could share it. That's a lot easier. Thank you very much. So those existed, but like, I think for what you're doing and for some of the things that I think flying under the radar, you know, that, you know, not again, not the headline features.

I think the there's nothing. Then a short video. Yeah.

Anne McCarthy: And the connecting the dots. Like I started that connecting the dots series, just kind of on a whim because I found something that I was like, you can do this. If you combine these different tools, you can then do this crazy thing. Like I think [00:09:00] that's also, I actually, that's the series I'm probably most excited about.

Like, it's fun to do these headline, like explore navigation blockers from 5.9 or the query look like that. Those are fun videos to do, but the connecting the dots. It feels more exciting. Like I'm like, gosh, yes, get this major feature in your head. But then also like, let's talk about like the weird things you can do and the cool things you can do when you actually combine these things.

Cause that's, what's really powerful is it's not like cool. We added dimension controls to this thing, but like what does this actually allow me to do? Okay. This.

David Bisset: Practical application right? Yes. Cause those are the videos I'd like to show off from the meetup groups. And a lot of times meet up organizers, just say, this is cool.

And then the media bargain meet up organizers. If they're good meetup organizers say, and this is how it could apply to you person, that's running an agency out of there out of a phone booth or whatever it is you do. Let's transition from weird to WordPress 5.9, because you could say something [00:10:00] happened a little bit weird on that.

Oh yeah. It's supposed to be out or right around this time of rigidly, right? I think it was before the holidays. Yeah. You mean the same date as the state of the word? Really? Yeah. I didn't put those dots. Yeah. That, that, that would yeah, that's a coincidence. So it didn't happen.

Can you tell me a little bit about what happened and what was involved in making the decision? No spoilers, but to push that into charity.

Anne McCarthy: Yeah, it's a really tough decision. And I'll preface this by saying I wrote a post that on why I voted to delay it. So I won't go into hyper detail cause there's a lot of detail on that post that I try to make it very practical.

Here's how you can enact a lot of videos and like images being like, this is why. But yeah, this is my first time on a really squad too. So I don't have the historical knowledge that other folks bring to the table, but from my point of view and from my experience. Which program, which really is where I'm coming from too many things were interrelated.

And then we didn't [00:11:00] have enough people. Who were looking across basically is the long and short of it. So, you know, 2022 is relying on you know, certain things get in place with styles, but at the same time, those working on styles aren't necessarily solely focused on 2022. So like, it was kind of, there was a weird tension there of bringing a lot of unrelated things together,

David Bisset: ultimately, I'm sorry, was it like the sunny from Philadelphia meme where the chart is. I think it's Charlie, he's looking at the board behind him and then the oldest red strings going everywhere. And he's trying to explain something was a kind of like that a

Anne McCarthy: little bit. Yeah. There is a little element of that, but almost imagine. That if you were to remove one of the strings, like that feature wouldn't make as much sense anymore.

So remember how we were just talking about connecting the dots and how things working together is actually where the value like hyper value goes. That's what basically was going on, where it was like, if we ship these things independently, we could in theory, remove some of the stuff. But it's going to be, it's just the value kind of isn't as exponential when they're all together.

And I was [00:12:00] looking at the issues. I test it every day, like, especially leading up to release for 5.8, 5.9. I've been testing every single day in this stuff all the time. And a lot of it was refinements. It was like, there were a couple of things that, some big decisions. So one I can tell. There was stuff around the navigation block, how to reuse it across Wakim's.

So originally there was a thing called navigation areas that was a new block that got reverted. That was I think, the right call. And then there the browsing. So when I talk about browsing, it's like, how do you navigate between your homepage, your templates and your template, parts and styles? Like what does that system look like from an information architecture perspective?

And there was a weird combination of. Technical constraints that came up as well as like design, so design and the technical constraints. We're kind of dancing with each other. And at a certain point, it just got to a place where. Fortunately like a middle ground could be found. And I think the solution they have right now is excellent.

Originally that, that seemed to be not viable. So kind of by having the delay, we've [00:13:00] had like a better solution, I think, than what was originally in place. That's been tested a lot with the outreach program, so it's a lot of it. Yeah.

David Bisset: Am I correct in understanding you that you were the one who initially brought something up?

Anne McCarthy: I was not necessarily, there was a team.

David Bisset: Yeah, everybody started getting the idea around the same time. Maybe.

Anne McCarthy: Yeah, it was one of those where I think enough people kind of paused and like, I can tell you leading up to the release. I was like, okay, are we really feeling good about this? Like, I had some moments, but I also wasn't like confident and being the person to say like, we can't ship this, we can't ship this.

Like, I'm definitely not one of those decision makers, but I mean, I'm filing, I was filing tons of issues and getting, and with the outreach program, obviously, like I'm seeing the complaints, I'm writing a summary post. So like I knew what the pain points were. And then at a certain point, it becomes a decision for the designers.

Like what design direction do we want to go in? And that's kind of where we landed, where it was just like a last minute kind [00:14:00] of Too much to figure out. And a lot of it's like little things too. So I'm talking about these big decisions. If there were a lot of small things that need to be sorted out that thankfully were more refinements.

And so I felt really comfortable delaying and voting to delay because of that, because I was like, the value will be exponential. If we can ship these altogether, everything I'm seeing right now can be figured out like at first. And I think this is where the confusion really started. There was this like long list and it was all seen as blockers.

So originally there was like this get hub issue that Someone did there. I think it was Rob who's, the corridor tech lead, who has been doing an excellent job. All the lease lead folks have been doing amazing work and he wrote all the issues out and gathered all of them that people were flagging.

But they were seeing all his blockers and that wasn't the case. Really from that list, there were like a subset of blockers that were truly like, we need to delay this. And that's part of the chaos of, you know, working remotely. Yes.

David Bisset: You had a translated into a sound. It would be mostly that. So yeah, I would imagine the [00:15:00] holidays.

It didn't help that the fact that we have this, let's be honest, the last two weeks of the year or the last week of the year, the first week in the new year, however you want to slice it really for me, three weeks, really, or two and a half at best, but sometimes three weeks for everybody to get.

Even if they're staying home, even if they're not traveling, it's your brain is kind of in a reset mode. Yeah. Like I need, listen, I may not be leaving my house, but I'm taking a vacation, so you're not talking to me. Regardless if you celebrate any of the holidays or not, there's enough mass people taking time off visiting family, or just staying at home or away from computers that I would imagine productivity would've hit a dive there and, or you didn't want to, nobody would want it have taken the chance.

You know, we don't want to make Matt Mullenweg into Scrooge because he's to he's the lead. Right. He's the lead. Right. So that would be, yeah, that I'm correctly associating the[00:16:00] fictional character with the appropriate reference. Thank you. Case. I get an email later. So when is a WordPress 5.9 coming up?

Anne McCarthy: It's going to be released January 25th. And as you were saying, like originally the beta was only pushed by two weeks, but then we had to add extra time because of the end of the year period and beginning of the year. I mean, it's just a chaotic time. And I think that is also the right call. I don't think it'll hyper disrupt any other releases.

I think there's a ton of stuff for 6.02. It's not like, oh, by delaying, we're going to have a really light 6.0 release. I think it's gonna be. How's that going to change as

David Bisset: well? Is that going to be a little bit compressed then in the first part of the year, you think, or is different people working on different things?

Anne McCarthy: Yeah, I think at a certain point it might compress it a bit, meaning like there might be a release in like March or something like that, but they actually didn't release the schedule for 6.0 yet. So I'm not really sure how that's going to impact. Things I will say part of the discussion that's come up amongst score contributors when I've checked in with a lot of them, when this was going on to make sure everyone was doing okay.

And a lot of them were like, man, this is when I wish [00:17:00] we had more releases. Like I wish we could have this like more of a release cadence where it's more frequent. So we're not like needing to do with delay. Cause like the options were not fun, but that's the constraints of the current system. And, you know, ideally in a future world, it isn't as Yeah.

Each release. You can kind of say like, it's okay. We can ship this because we have another release coming in a month rather than like three months.

David Bisset: Yeah. Is that possible though? I mean, is that possible at least where we stand right now, because we just talked about how. And like how integrated are, how one piece is related to this.

And, you know, you know, maybe this is just one of those junctures in the four stages of Gutenberg or whatever timeline you want to pick where yes, it all is intersecting together. Cause it's full site editing. I mean, it's the words are in there. It's full side. Right. And then maybe down the road with when he gets to collaboration and translation, maybe things will go a bit easier, but regardless it's like.

I know there's so many, there's so many ways you can look at it. I hear about a lot of time in other technology groups, in terms of first, you have people say, well, why [00:18:00] don't you just release every month? It's no worries. Any automatic updates. It's fine. And then that happens. And then you say, why are we getting so many updates?

I have to keep updating.

Yeah. Which, which, you know, is another subject in of itself because in theory, You shouldn't have update fatigue, if you have automatic updates turned on and you know, that's another thing too. You know, in some situations that's not possible. So you're going to have people, whether it's a real problem or something that someone projects into their mind, like some sort of ghost but it's still a legitimate thing to deal with.

So I see. So yeah, you have this, you it's a bunch of. All not the code, but the responsibilities and the dependencies is a bunch of, you know, a bunch of well cooked, fine high quality spaghetti.

Anne McCarthy: And yeah, it would be really tricky to do. Like, I don't necessarily think that's like a viable thing right now, or I don't, I can't speak to it in the future, but I do [00:19:00] think it is a result of, you know, the circumstances that we're in.

Like we're all impacted by the same constraints. And I think that's one of the things where. You know, for example, there are, I don't think it was fully scoped out even like, what would a dependency plan look like where it's like, or contingency plan? Sorry, look like where if let's say we had to remove some of these things, would we, excuse for example, we could do things like remove browsing entirely, which is one of the things that was, I think, shipped at some point.

We're instead you have, you know, your appearance menu, you have templates, simpler parts, the editor styles. And so you have no sort of browsing in the sidebar. You could also like say, you know what, the navigation block isn't ready or counting it to another release. You could also say like, you know what, you can't actually create new templates.

You can only just view the ones that come with your theme. Like there's a lot of ways that could have been pulled back. But thankfully what shipping is very comprehensive. Like I think that's the good thing with this delays also.

David Bisset: I don't think anybody's looking at it going on, man.[00:20:00]

Anne McCarthy: Yeah. And I mean, I also think the good news is ultimately these features that we're talking about, which get a lot of attention are going to impact a small subset of people. Like this is not going to be five point where all of a sudden it takes over your site and you have to use it like this is it.

It's very much. So in line with the gradual adoption, where if you want to use these features, you have to literally hyper opt-in. You have to switch your theme. You have to like seek it out. Like it's very much something that. That also gave me confidence where it's like, I know these like full siting and all the collection features that go along with that.

You get a lot of attention. But even if you upgrade, you're not switching to full site editing, you're still gonna get a ton of value in this release. And that, that to me is what's really exciting is it's almost like, because this is a smaller subset. The features are more high impact exponentially when they're working together.

I think it was just the right call, but I'm really excited to see people get their hands on 5.9. And speaking of police health tests, the Tesco lead, I'm like, please help test. It'd be a huge help.

David Bisset: We'll get through testing in a second, because I [00:21:00] do want to, I do want to get, like, if you had the opportunity.

To make it to make a pitch for you. You did mention 5.0 though. When that first came out, I think there was a there's a number of people that, and you know, that the circumstances behind that you know, around the state of the word time, everybody was busy or give Ghana was one of those. I think it wasn't November.

So, I mean, it was approaching a holiday season or something or something like that, but it was, I would be, I don't know, a lot of people said it was around rough around the edges. I'm not going to argue with him about that when it came out but over time that the improvements on it have been, I think in my opinion, pretty good.

Pretty, pretty tremendous. In fact, do you think and you may, I think you touched on this already, but do you think with a full site editing, we're going to see not what 5.0 is. Cause I think you just said that, but do you feel comfortable with the level of Polish that will be out at the end of January?

Anne McCarthy: Oh,

that's a great question. There's a lot of nuance here, so it depends [00:22:00] upon someone's skill level. If you were brand new WordPress user, I would, I'd say very beta. So like, I think it's literally going to ship with a beta warning. So in terms of, is it hyper polished? I would call it functional kind of empowering.

But I wouldn't necessarily be like, oh, it's delightful. And you can, it's completely intuitive. Like I think, and I say this partially because especially if someone, maybe if someone was new, they might actually have an easier time, because there's a lot of concepts built within full that are really hard to grasp.

For those of us who've been in WordPress for a long time. Things

David Bisset: Can they get those videos in there? That would probably help.

Anne McCarthy: Yeah, no, I think that's part of, so I actually am also helping with the user support docs for this release. So I'm co testing it and then helping with the user docs. And that's one of the things that's really difficult to communicate simply.

So like, how do you explain to someone, what template parts are. And how do you explain when to use them? So, like one of the, I just opened an issue for this yesterday, but it's like, we probably need to explain the difference [00:23:00] between template parts, reusable, blocks and patterns. And when do you use each? So I probably need to write a doc on that.

So there's a lot to be explained there in a way that's very simple so that people can make good decisions. And right now their, what is being shifted doesn't necessarily have guardrails to nudge someone in the right direction. If that makes sense. So you'd have to have some level of knowledge in order to write.

Put it together, but do I think it's a polished V1 for someone who likes to tinker? Definitely. Like, I, for sure think that's the case. The only I can tell you my major sticking point, which is driving me nuts right now is right now. Are you familiar with the template editing mode?

I launched.

I've played with it.

Yes. Yeah. So right now let's say I have a block theme activated and I'm using 5.98. I can go in and I'm using a theme with template mode. I can go in and I can like add a new post. And then under the posts kind of sidebar, I can select and create any template. And from there I can have a fresh new template that I can then assign to the post.

However, if I'm in [00:24:00] the site editor and I'm navigating through the templates, I cannot create a new generic template. And there's an issue open for this. I can create an archive when I complete a search warrant. I create a new front page one, but there's not a. I want to create a new template and I want to sign this poster page or this category to it.

So there's a lot like that basic infrastructure you can, it's a workflow thing. So it's like in one place, you can do this thing, but in the other place that feels more intuitive. You can't. And then on top of that, obviously for this release, some stuff is constrained. So this was one of the decisions that had to be made.

So you can't have. If you wanted a category to use a specific template, you'd have to actually add it to your blocking files rather than like being able to do it in the interface. So the good news is it'll ship, but then there's some really common. Possibly common use cases where people are going to be like, oh, but I want to do this.

And that's where I think 6.0 6.1, like these future releases will continue to deliver on the promise to pull siding. And I think right now what is in place is really powerful. And I think it'll [00:25:00] actually jumpstart. People's excitement into everything that you can do. But there are just some. I don't know.

I think Justin Tadlock had a good description where he's like, it works, but then as you're getting involved in it, there's like some common things that you're not yet able to do. And I'm like, yeah, that's very true. Like there are some things that I can imagine. I'm like, I would love on my personal site to have a specific template for.

All my posts that are tagged with WordPress resources so that I could just send people there and I could have a different header. I could have a different contact form, like have a completely different experience with that. I think it'd be really cool.

David Bisset: But you know, I was like, it sounds like something in the old days before Gutenberg, that would be like a WordPress plugin.

You would have to find

Anne McCarthy: correct.

David Bisset: Which in the defense of Gutenberg, in terms of that, I mean, You know, you're, it seems like a lot of the, you know, a lot of the major work being done, but also some things that are being done in Gutenberg. Like duotone, for example, maybe it's the one that jumps out at me. It's like, [00:26:00] like before it was just, you had to go find a plugin for that.

I mean, you're you and birds taking off. Lots of cool and interesting things that were before with maybe with, or with maybe with a page builder, with an add on with a page builder or just a plugin that those were just like little thrills that you would just find in the plugin stuff, getting Berg's incorporating this in the course.

So Gutenberg, I mean, it's not just a, it's not just the blocks anymore. You're incorporating all these like, you know, fun stuff that like, maybe. Not even the majority of people might even use some time, unless there's a big, duotone a fan group out there. In other words,

Anne McCarthy: the only thing that I think is cool is that you can add it on theme level.

I think that's part of it. It is very much a design tool in that sense. And I think that. To me where I've seen it really come to life is when I've seen some theme authors. I think some automatic female author is released. It's skate park is a theme, but it has like do a twin filters baked in. So like, if you change the [00:27:00] background of your theme, the images were also like a doc, the duo tone.

David Bisset: Oh no. My F my life is a French film to atone anyway. So I'm full of that. Did you happen to hear. I think when it comes to block themes, Matt said something about wanting 3000 a year or so. Was he exaggerating there a little bit? I

Anne McCarthy: think he's serious. And like, I also, this sounds wild, but I think it is very much so, like he actually thought it was interesting that he said it in that way, because how do I explain this?

Like, You could take one block theme, like let's take 20, 22. For example, the announcement post showed this and any announcement posts, it shows like four or five different style theme Jason files and switching between them. And it looks like a completely different theme. And I think that's where it's like, you could literally take the base of one theme with the same patterns, all that sort of stuff, and create.

20 different theme, Jason files to switch [00:28:00] between and have a complete different experience. And to me, that's, what's really cool. And then once you start integrating with the pattern directory even more, I think that unlocks some really cool stuff. So when he says that, I'm like, yeah, I understand what he's saying, but I actually, I think that's a way to connect with like the.

FIM world that we have come to know to last however many years. Yeah. But I think the future with block themes, things are going to be wildly different. I think rich table were asked a question about, you know, could there be a directory for different style? And I'm like, yes, like that to me, I think is a really cool model and there's work being done to enable.

And json switching within a block theme,

David Bisset: so definitely would make it competitive with you know, like, like a Wix or Squarespace in terms of like you could have, this is a completely customizable experience. Speaking of customizable, I do have a question for you. When it comes to the full site editing, what happens to the customizer?

There's numerous people that use that there's people that use that and granted they use that for their theme settings and maybe. And [00:29:00] for other things, and in addition to the normal customization, so what's going to happen to the customizer?.

Anne McCarthy: Yeah. So this is actually something that I'm so glad you're asking me this, because this is a thing I've seen, brought up a ton.

I've gotten, especially in the span of like, it felt like two weeks, I was getting a ping, like every other day being like customizer. And I'm like,

David Bisset: I know like a bot on Twitter about the customizer, but I've figured that ask you.

Anne McCarthy: So basically the customizer, if a plugin or theme happens to look into it the customizer will be available to actually it'll direct you to it.

So it's not like it's going away forever. Is it removed from the menu item? Yes. If you're using a block theme, you will not see it unless you are using a plugin that somehow hooks into the

David Bisset: customizer, but you have to switch to a block theme and then at the official

Anne McCarthy: blocking the lose, the customizer only superior.

Correct. And it would only disappear if you don't have a plugin that happens to look into

David Bisset: it as well. Right. I'm sure somebody will come up with that in a few seconds, but

Okay. Then I, you know, initially [00:30:00] here, I mean, I've, haven't had my coffee yet, but it sounds like to me, that makes sense where in terms of, you know, you're not going to need it. You may not need it. Now, if anybody has anything in there, there's probably something developers that have put something in there that shouldn't be in there then, you know, get out, get it out of there.

But okay. That answers that question pretty well, because it makes sense. With a block theme on there shouldn't be anything in the customizer left.

Anne McCarthy: There is a universal theme. I don't know if you've heard about universal themes, but they're also a combination. So there's like, let's see there's black beans hybrid themes, universal themes, and classic themes is like theme paradigm.

We're about to enter and blockings are like fully built in with full siting. Like you're not, you know, using the customized or anything

David Bisset: like that. You don't need the, you don't need the additional CSS. The one thing that sticks out in my mind is the additional CSS thing in the in the customizer and you and I both know.

That if I don't usually use that, I use, I, I add the CSS some other way. It's usually through a plugin or through the style sheet, in the theme [00:31:00] or something like that, whatever. That's the only thing that kind of concerns me a little bit, because I've seen people put CSS in there that relate even to plugin, not even the theme directly, because that's just one place that they're able to put CSS.

They know it they've seen it, or some webpage told them to put it there, that they don't have to like dig into any code to, they can just put the additional CSS. In fact, it wouldn't surprise me if some WordPress plugin support people have told people, oh, in order to resolve this issue with our. You just need a CSS tweak with your theme going here.

But again, you're saying that it's still going to be there unless they switched to a block theme. So the only danger there is if you switch to a block theme, but if you're somehow using the plugin, is that, does that, it's just hiding it. It's not removing it.

Anne McCarthy: It's just hiding it. It's not removing it. So

David Bisset: sorry.

I had to work that out. Yeah,

Anne McCarthy: no I totally understand. Cause I used to work on Jetpack a lot and that was one of the things. It has an additional CSS part of it. So I understand what you're describing. [00:32:00] Yeah, it's very, I also want to advocate actually for universal themes, because if someone is like, I'm curious about this world, but I don't want to jump in universal themes are basically designed so that you can use blocking functionality, but then also the customizer.

So it basically bridges. Which is why it's called universal

David Bisset: either that or the movie company bought you the rights.

Anne McCarthy: Did you not hear about the new acquisition?

David Bisset: I was going to go to the theme park in Orlando and see all the new Gutenberg blocks, right? The ride, the Gutenberg ride. Oh my God.

Anne McCarthy: You say that.

But I did. I was getting beer the other day at a store and there was a thing called gluten berg. Which is a form of gluten-free beer. And I was like, oh my God. And I was off work. So I was like, am I tripping right now? Like, what is happening, dude, bird everywhere.

David Bisset: I made a slip on Twitter, I think yesterday morning.

And I said something about like, I'm having a state of the word hangover, a hashtag Gutenberg. And I left it in there and I just said, Gutenberg is just you [00:33:00] trying to contribute to the project, but you haven't figured out yet how to be sustainable. So you're, and you're not above begging. So, you know?

Yeah. So I left Gutenberg and I left good Megan, there let's talk about at least two more things before I leave you to. Fantastic video editing work here. One thing is about testing. What is the number one way? What's the number one? What's number one thing you advocate regarding testing. And you're going to give me symbol links to put in the show notes for this.

So we're not going to worry about that, but how does that work and what do what's the qualifications and what are you looking. In terms of testing.

Anne McCarthy: It's a great, so like the beta posts on, I'm going to drag people to the beta posts on your research backslash news, because there's actually a link under like a testing instructions to a post that I did that gets very detailed.

So if you just are comfortable testing, go for it. If you're someone who needs more instruction or. Exactly. Like what to test, how to test. I have a post that's it's titled help test 5.9 features, and it [00:34:00] goes step by step through the different features with like a brief description of what they are, how to find.

And as well as like, if you want to get even more detailed steps, a lot of them link out to calls for testing that were done through the outreach program. So you can even get like a step-by-step description of what needs to be done. But yeah, right now, if you can, I highly recommend testing both 5.9 in terms of, without a block.

But then also take the 2022 thing first, then it is a very cool expansive team.

David Bisset: Hey, Matt gave us the bird on Tuesday and my wife looked at me like I was, should report it to the. Yeah, but it's in, that's also another, that's another complication layer too. It's not just the five nine release. It's it's the new default WordPress theme. It looks fantastic. It is the, it looks fantastic.

I'm more excited. I can't remember the last time I've been more excited about like a default theme coming up because it really looks like it's using the art state of the edge [00:35:00] stuff, plus, you know, the birds well, good. Well, thanks for you. Share those links with me. I'll make sure to add them.

I make them in there. So here's one thing that's been. I was scratching my noggin the other day and trying to figure out the best way to describe this. So I've been told by multiple sources that thanks to COVID thanks to the lack of in-person work camps. The contributions contributors have been, they've been low for the past 16, 18 months, two years, something like that.

And then. Do you think that first of all, do you think that's true? And if so of it's true. Do you think it's, is it impacted the project because Matt, I guess I'm just gonna finish my sentence and let you speak at the end, because I don't know when to shut up, but I did see, I saw Matt slides on Tuesday.

He did highlight. I mean, there are lots of circles in the slides, right. And then there was lots of new contributors. Yes. Circles. I work in [00:36:00] shapes. But there were, and there were lots of new contributors to that. We don't know what they worked on. I mean, new contributors, that's awesome in there.

And there was definitely a lot of circles on there, but do you think that COVID has had an impact on the contributions or contributors over the past two years?

Anne McCarthy: I mean, yes, both. And I will say, I think it's like a. Multi-directional so I think it's everything from, for example, the outreach program, I've given out 70 badges for a test contribution, which is probably more than has been given in a long time, you know?

So it's like, in some ways we've had more contributors, probably in some spaces and have brought in. And I've had the chance to work with folks who have gone out into their local communities or held things online with their local communities to help people test and explore that. So there's like, it's both right.

Like I think in some cases it really burns some people out. I think it burned a lot of folks out were just dealing with like trying to survive day to day. You're probably not going to want to jump into open source and contribute. [00:37:00] But at the same time, I think suddenly the community had to become a lot more accessible.

So actually I started this role in April of 2020, so right when things were really like in the U S it was. Getting really serious, like in lockdown, all this sort of stuff. So it's been very interesting. I, when I first started the job was told like, oh yeah, one of the first things we'd probably do is send you around a bunch of word camps and word cancer, where people get onboarded and like all this sort of stuff.

And I was like, okay, well that's not an option. So what are we going to do about this?

David Bisset: Yeah.

Anne McCarthy: And this is where we're all kind of delusional about like, oh, maybe this will pass. And so it's been very interesting and like, I can tell you speaking personally, a very anecdotally I have spoken at probably 10 or 11.

Events, maybe more in the last year I do not like public speaking. If I had to go up on stage and do it, it would be way less successful for me. Like it causes way too much anxiety. And then on top of that, like, you know, I just gave the word camp Taiwan recorded or camp Taiwan keynote at [00:38:00] like one 30 in the morning of my time where like, normally I would have to travel to Taiwan.

I would have to, you know, be jet lagged pregnant. There were a couple of days early, like all this sort of stuff. And then it. Being able to connect with brand new contributors and brand new folks has become way easier. And so I think that's like one of the things that makes me really excited is like, you can travel the world from your apartment.

So I often [email protected] and just see what people were talking about. And we'll just jump in. Either a 5% or 50% meetup

David Bisset: group. Oh, I love her. I love virtual stuff. I talked to my kids. That's how I talked to my kids all the time. My kids still live with me, a side note. So do you, so,

Anne McCarthy: yes, I do think it's also caused a decrease.

I think there's an over-reliance on On people who are sponsored contributors. And I think, but I think it also, at the same time, new pathways have been built. So I'm both encouraged that like new pathways are being built. New folks are being brought in and things like the photo directory, the pattern directory even blockchains are way easier to build.

[00:39:00] I think we're going to see an influx of more folks coming in.

David Bisset: Yeah.

The onboarding process. Right? I would imagine. Yeah, like you said, it's harder for any individuals with present condition. So I, you know, companies like, like, and Matt was showing those, the other bubble slide where there was automatic.

I imagine there's like you said, you were doing one thing now you're doing another, it sounds like there's automatic made some adjustments there to. I'm not putting words in your mouth, but if it wouldn't surprise me, if some companies made some adjustments to compensate for the fact that, you know, there is less of certain kinds of contributors out there just because of oral conditions.

And we just finished. I don't know if you've been following this log for. She fought with J or something.

Anne McCarthy: Log4jI.

David Bisset: Mean, everybody's talking about it. I mean, nobody's rewriting my software yet. Thank goodness. I'm unpopular now. And it's an advantage but I mean, there, you have, like, I think two people, one [00:40:00] person working on that and the guy had a side job too, and now everybody's kind of relying on it and you know, that makes you sit back and watch.

Well, a lot of people rely on WordPress. Obviously things are going to slip through the cracks, but overall it's nice to have, even if there was a major world event and this has been a major world event, then I think things from a feature standpoint, from a bug standing standpoint, it could, I guess it depends on your experience.

You can either say it's been fantastic that it's managed to be as uninterrupted as it has been over the last two years. Or you can just say, Hey, it could have been worse. It, you know, WordPress runs 43% and the train has to keep moving. The show must go on. And some adjustments, I guess, have to be made.

I'm looking, I do want to see more independent or at least other companies enter into that bubble space. Just like Matt had. I mean, at one point it was a bubble's commercial, but I mean, you know, that second slide with just more independent bubbles on it. So it sounds it's, but it sounds like for [00:41:00] me talking with you here, that of all the challenges that's happened, both ones that I think everybody could imagine in some of the ones that you're not telling me, because we don't want to get into the weeds on it.

It sounds like, from stability-wise I th the decision. To bump it. I think it was only a little bit controversial for a moment. At least from the outside. I can't speak within the inside of a group. I imagine there was a lot of talk and maybe there was some tradition or precedent there, but obviously that would have didn't sound like that lasted very long if there was any, and it was only controversial out here, like, you know, weirdo land where I live, you know, there was news, but it was.

Okay, fine. You're bumping it from December. I think I'd rather have that been bumped. And so it sounds like,

Anne McCarthy: And that was part of why I wrote the post to be honest, because I was like, man, this is going to be so confusing and people who aren't just like knee deep in this, like it's going to be seen in a light.

That's like really hard to parse. And so that was really part of my aim and writing [00:42:00] like, Hey, this is why I voted. And this is the details. If you really want to know Of course, Matt, I don't know if you saw Matt's comment where it's like, this is the actually information I want. Like that's a different post that Matt. Like, I can't, I don't want to write it.

David Bisset: Let me do my work. Cool.

Anne McCarthy: I know I got that comment on Sunday and I was like, oh, okay, cool. Like I, where do I need to write out a post about this? I was like no. We have to do a retro for the release. Like, this is a really good, but he's right. I was like, oh man, I should have included some stuff about like, here's what I think we can do going forward.

You know, it was chaotic. I wrote it, I think, within a week of the decision. And it was doing it on top of other stuff. So

David Bisset: yeah, next time it's a long story, but next time I have to get you to get him to say banana milkshake and the state of the word I have. If you don't know what it is, I'll try to put a link in the show notes, but anyway.

Yeah. But th the thing about the bingo card is we put some obvious ones there, and then we put some less obvious ones. Like there's like, like NFT. He said NFT. Okay. How about metaverse? You said metaverse.. Okay. Now it's like, everybody's doing bingo. Bingo, and going, oh, crap. I could have made [00:43:00] this harder, except everybody has a one random generated word.

It's like I was saying to myself, what's the antifree square. It's what's on a bingo card. What's one thing he would never say. And then everybody says, well, we can't get bingo. And he says banana milkshake. And I'm like, all right, people put on your big person pants. And we're going to see if we can get someone there.

But anyway, besides that way, we'll edit this all out. It's boring. but anyway, and what you do, but. To end on a good to end on a very good note here, because I'm talking to you and you do very good things. So this is going to be very, it'd be very you're very much appreciated in. And even if the resources, even if the testing, you know, is, you know, we could always use more testing.

We can always use more contributors. I think the job that you're doing, the videos is doing two things really well, everything that you do, it's not just the videos, but the videos, just making things a lot easier to consume. Especially in this Tik TOK world we live in don't do tick. I didn't say the tick-tock

world.

Anne McCarthy: I mean,

David Bisset: here, my kids don't either [00:44:00] I'm that I'm not going there, but two it's also about the transparency for something like this, I think because it wasn't such of a talking point, partly was because you and the team were so transparent. And the minute that we read, the minute I read the report, I'm like, yeah, this sounds like the way you're presenting it.

A it's a, no, it sounds like a no-brainer and B we can wait another month. I can wait another month.,

Anne McCarthy: I really credit folks like Tonja and Mary and Rob. And like, there's a lot of folks who made that transparency. This is tough decisions, Jonathan to Rogers. Who's not even on release squad was like giving advice about timing.

Like it really was a team effort to operate in that way. And I loved seeing the liveliness of the 5.9 release leads channel, and it folks are curious about how our release works. And you can literally watch us talk. And there is no back channel. Like it's like, I have a question I'm going to that channel.

David Bisset: Yeah. I need that. I need kind of that for my, from my marriage. Cause it'd be nice to have some texts. You didn't say that will [00:45:00] let me do a little search here. And where are you going to your mother's? Okay. I'll catch you later. All right. So, and tell us where we can find you on the web and where people can reach out to you, especially if they have questions.

Anne McCarthy: I'm at an Zazu and an E Z a Z U on we're personal work slack. And then I have a block like I'm very I know shocking nomad dot block.

David Bisset: Make sure to throw that into the show notes or give that to me and I'll put in the show. Yeah. Yeah,

Anne McCarthy: I will. And like, I honestly am not, you can find me on LinkedIn, but I'm off of Instagram. I activate and deactivate quite frequently. It's the one that I seem to be, I do too, but that's in

David Bisset: real life, but yes.

I know you're not on Twitter and you're sometimes on Instagram. That's why I wanted to get a few links for you because I'm in post out a slack and there's posts at a slack there's WordPress slack. Thank you very much for sitting down and talk to me about this. I think

Anne McCarthy: thanks for the opportunity.

There's so much, I feel like we could talk about, which is always such a great feeling is it's like, gosh, I could just talk for hours about these different things, because I think so much about them and you [00:46:00] really hit everything that I want to talk about. So it's awesome.

David Bisset: Yeah. Why didn't I have this skill when I was young and single, I have no idea.

That gives me food for thought later, but anyway, I really appreciate it. And I will I'll definitely be checking out the betas for 5.9. We can't wait for January.

Anne McCarthy: Awesome.

by Olivia Bisset at December 29, 2021 11:18 PM under The Excerpt

Akismet: How to Stop Contact Form Spam on WordPress

Are you getting useless contact form emails in your inbox? Contact form spam is a problem every website owner deals with at some point. Spambots target websites of all sizes, regardless of the amount of traffic you get. 

Sifting through hundreds of messages to separate spam from genuine inquiries is time-consuming and frustrating. Luckily, there are some easy and effective ways to protect your WordPress site from spam and take advantage of the benefits of contact forms. Let’s discuss! 

What is contact form spam? 

Before solving this common issue, you’ll need to understand what contact form spam is and how it affects your website and business. 

Contact form spam is exactly what it sounds like: unwanted messages that are submitted through the contact forms on your site. Since these forms have blank fields, an individual spammer (or bot) can fill these out however they’d like. 

You might just get one or two occasional messages with irrelevant promotional material or even offensive language and links. Or, you’ll sometimes receive hundreds or even thousands of form submissions to your inbox. You’re left sifting through the spam so that you don’t miss real messages from interested followers or potential customers. Worse yet, all of these submissions can hog server resources, resulting in a slower site or errors when you try to make changes. 

Spammers target contact forms in one of two ways:

1. Manual spammers

Manual spammers are humans who navigate to your website, fill out your forms, and submit them personally. They typically use false information, often copying and pasting to spam your site quickly. In most cases, these spammers are trying to promote specific websites. But they can also spread malware and funnel traffic to malicious sites. Manual contact form spam is more difficult to overcome because spammers can get past many anti-spam solutions like CAPTCHAs. 

2. Spambots

Spambots are the most common sender of form spam and often the most dangerous. These programs automatically search the internet for forms and, depending on how spammers program the bots, they leave junk text and phishing links that appear in your inbox. 

Spambots threaten the integrity of your website when programmed to perform more malicious activities like taking personal information, spreading malware, or taking control of your website. These automated programs can leave a larger number of form submissions at once. But they’re easier to stop because they can’t combat specific anti-spam solutions. 

Why do bots and human spammers target contact forms? 

With all the advances in technology and increased security options, it’s hard to think that this type of spam still exists. But bots and human spammers still target contact forms because they can, and it works. 

Here are several reasons spammers look for loopholes and vulnerabilities in your website forms: 

  1. They want to send you spam. Most spam includes links to phishing sites or revenue-generating ad sites.
  2. They want to exploit your contact form to spam others. Spammers use your contact forms to relay email spam messages to others. When these emails land in people’s inboxes, they typically look like an email you sent. Unaware that it is spam, users open these emails and click links that lead them to another website. This increases website traffic and engagement to that site, rewarding the spammer. 
  3. They’re searching for vulnerabilities to access the backend of your website or server. This is typically where malicious intent comes into play. When spammers target your contact forms to look for vulnerabilities in your website, they often want to attack it. Spammers can install malware that leaves your website and visitors at risk. They can also steal personal information, a significant risk for eCommerce sites with sensitive customer data. 

How to identify contact form submission spam

Keeping a close eye on your contact form submissions makes it easy to identify spam. Watch out for the following signs that indicate spammers are targeting your website:

  • Phishing links. Spammers use phishing URLs to obtain sensitive information for malicious use. This includes usernames, passwords, or banking details. Phishing links appear to direct to a legitimate site, but it’s really a fake one meant to steal this valuable data. 
  • Irrelevant messages. Another typical indication of spam is unsolicited or irrelevant messages. Spammers send these messages out in large numbers for advertising, phishing, or spreading malware. 
  • Submissions with no real name. If you get submissions with no real name or a fake name, you’ll want to look into blocking form spam. 
  • Grammatical errors or typos. Most spammers don’t take the time to proofread their submissions or check for grammatical errors. Instead, they work hard to send as much spam as possible in the shortest amount of time. Therefore, if you notice messages or comments with a significant amount of typos or grammatical errors, your website is likely under attack. 
  • An offer that’s too good to be true. Like everything in life, an offer too good to be true also indicates a problem. Don’t fall for this easy trap. 

Once you notice a spam issue, it’s vital to find a fast and effective solution. While it’s both annoying and potentially dangerous, spam can also damage your brand reputation. Let’s explore some ways to prevent contact form spam on your website. 

How to block contact form spam

1. Install the right WordPress anti-spam plugin

The easiest and fastest way to combat contact form spam is to install the right anti-spam WordPress plugin. Anti-spam plugins work independently from your forms by comparing submissions to blocklists of words, names, IP addresses, and email addresses. They use both global and local learning to identify spam. Some also give you the ability to manually mark items as spam (or not spam), so it learns what you like and don’t like on your site. 

With several options available, it’s critical to pick the right anti-spam plugin. Akismet is an excellent option used by millions of websites to filter out hundreds of millions of spam comments and form submissions. It will check all comments and form submissions for spam and filter out any that look suspicious. You can review all filtered submissions directly in the WordPress dashboard. 

An option like this frees up your time to focus on the more critical parts of your website. It also gives you the peace of mind that your site, visitors, and reputation are safe. While there aren’t many disadvantages to this method, you’ll need to make sure you update the plugin as recommended to avoid any security issues in the future. 

How to set up an anti-spam plugin:

Installing a WordPress plugin is easy. In your WordPress dashboard, go to Plugins → Add New. Search for the one you’d like to add, then click Install → Activate. Then, follow any specific instructions for the tool that you chose. For example, Akismet provides a great how to activate tutorial with easy-to-follow instructions and visual cues. 

2. Add a custom CAPTCHA

Custom CAPTCHAs are another way to target and resolve spam problems. You can add a custom, word-based code or random math question to your website that visitors must answer to submit forms successfully. When users attempt to add a comment or submit a form, they’ll need to answer the question or type what they see above the submit button to proceed. You can add several custom word-based questions that users cycle through randomly. 

While CAPTCHAs are a great way to combat spambots, they aren’t effective with human spammers. They can also be frustrating and time-consuming for legitimate site visitors who struggle to answer the questions or answer them incorrectly. If you choose to add a CAPTCHA to combat spam, you’ll also need to think about users with limited sight or other challenges. 

How to implement a CAPTCHA:

To add a CAPTCHA to your website, you’ll need to choose a service provider. Google is the most popular CAPTCHA service, with essential functions offered at no cost to website owners. You can find your options in the Products part of the Google Developers page. Make sure to sign in to your Google account. Next, you’ll read through a short overview before clicking on Sign up for an API key pair. You’ll need to fill in your website information and follow the prompts to complete the process. 

3. Use Google reCAPTCHA

Google’s reCAPTCHA is a more advanced option than custom CAPTCHAs. Initially introduced to overcome the user frustrations of custom CAPTCHAs, reCAPTCHAs require users to answer more straightforward questions to submit forms. reCAPTCHAs also work by detecting user behavior while visitors navigate your site and assigning each user a “spam score” based on what the tool considers suspicious activity. 

The most common form of reCAPTCHAs is the picture puzzle you’ve seen on many websites. Instead of typing a word or answering a math question, users answer an image-based question. Visitors must select all the squares in the picture with a specific object like a car or a traffic light. Once all images have been selected, the button switches to allow the user to submit their form response. 

Here are some other types of reCAPTCHAs:

  • Checkbox reCAPTCHA v2 is a simple box that users must check to submit a form. It’s the popular option you see on many websites accompanied by the “I am not a robot” text.  
  • Invisible reCAPTCHA v2 does not display any visible fields to human users. Instead, it monitors user behavior for suspicious activity to identify potential spammers. Invisible reCAPTCHA also adds an extra field into the code of your form. Since most spambots use code to submit responses, these spammers automatically fill in the fake fields before being flagged. Human users never even notice the spam control as they submit answers directly on the form. 
  • reCAPTCHA v3 is an advanced option that uses JavaScript to detect human visitors. It is the most advanced form of reCAPTCHA, so you should only use it if you’re a WordPress expert. 

reCAPTCHAs can still prevent genuine visitors from submitting forms, but they’ve improved from the earlier custom CAPTCHA options. Most come with the ability to add an audio option for those with visual impairments. The visible option they offer is also a solution for the hearing impaired. 

Photo © Google

How to implement Google reCAPTCHAs:

You’ll add reCAPTCHAs to your website following the same steps listed above for CAPTCHAs. Google reCAPTCHA is also a free service for basic functionality, but you can purchase the Enterprise solution for more advanced options. You’ll need to sign up for an API key pair for your site and follow the prompts to proceed.

4. Use an IP access list

If you notice a lot of spambot action on your website coming from specific sources, you can use an IP access list to block spam. With this method, you add IP addresses to a list that restricts access to your website from that location. You’ll do this by adding IPs to the Comment Blacklist section of the Discussion settings page in the WordPress admin. 

Using an IP access list is an excellent option for blocking specific people. But it takes a lot of work to block a more significant number of spammers and requires constant maintenance. You can also accidentally block legitimate form submissions from the IP addresses you list, so make sure you’re confident before using this method. 

How to implement an IP access list: 

If you want to block an IP address, navigate to Settings → Discussion → Comment Moderation in your WordPress dashboard. Then, simply add any IP addresses you want to block and save your settings.

5. Take advantage of the honeypot method

If you’re not a fan of CAPTCHAs, try the honeypot method. Honeypots are little bits of code used to catch spambots. The code creates a hidden field in your form that’s invisible to human visitors but visible to spambots who are usually looking at the code of your form. Spambots automatically fill out the hidden field and submit the forms. The additional information flags these submissions and rejects them, saving you time and effort. 

One advantage of honeypots is that they stay hidden from human visitors. Your visitors don’t need to deal with the inconvenience of CAPTCHAs. Some WordPress form plugins even allow you to add the honeypot method in their settings. 

How to implement honeypot:

Some plugins allow you to quickly check the option to add honeypot to your forms. But if they don’t, you’ll need to add a hidden field to your form manually. Once you add the form to your site, use the CSS style “display: none !important;” to make the field hidden and tabindex=”-1″ autocomplete=”false;” to ensure the field is empty by default. 

Protect your WordPress contact forms

Contact forms are a great tool to connect with your audience and enhance your website’s user experience. But they can also be a problem when spammers attack. Don’t be the target of human spammers and spambots that reduce the effectiveness of your website forms. Use the six steps listed above to successfully stop spam from your WordPress site so you can focus your time and effort on more essential tasks. 

by Simon Keating at December 29, 2021 12:28 PM under Spam

December 28, 2021

WordCamp Central: The first in-person WordCamp Europe in 3 years is coming!

WordCamp Europe organizing team has shared what we are planning for the first in-person WCEU in 3 years.

It’s taking place in Porto, Portugal, on 2-4 June 2022.

With all safety measures, our beautiful spacious venue, Super Bock Arena can hold up to 4000 people, and we can’t wait to welcome you there.

Call For Sponsors and Call For Speakers are already open!

Subscribe to WordCamp Europe Newsletter to get to know about all WordCamp Europe 2022 updates first!

by Sabrina Zeidan at December 28, 2021 12:52 PM under wordcamp europe

December 24, 2021

Matt: Saving the Internet

David Pierce wrote a deep profile, over 4,000 words, for Protocol and asks the question in the headline, Can Matt Mullenweg save the internet?

Which brings to mind Betteridge’s law of headlines (née Hinchliffe’s rule), “Any headline that ends in a question mark can be answered by the word no.”

I can’t save the internet. But you know who can? A movement. A community of like-minded individuals, unified by a common philosophy, and working together to create tools of freedom.

It’s a human right to be able to see how that technology works and modify it. It’s as key to freedom as freedom of speech or freedom of religion. So that is what I plan to spend the rest of my life fighting for.

Working together we’ve created something special, unlike anything the internet has seen before, and I’m excited to continue.

Thank you to David Pierce for taking such an in-depth look at the history of WordPress and Automattic and talking to dozens of sources. Thank you to the people quoted in the article: Scott Beale, Om Malik, Toni Schneider, Russell Ivanovic, Deven Parekh, Paul Mayne, and Anil Dash. Thank you to Arturo Olmos for the photos, and Odili Donald Odita for the amazing painting behind me.

by Matt at December 24, 2021 01:07 PM under WordPress

WPTavern: Multiple State of the Word Attendees Test Positive for COVID-19

State of the Word 2021 in NYC

Matt Mullenweg’s 2021 State of the Word address was held in New York City nine days ago with a live studio audience. On Sunday, December 19, all in-person attendees were notified by email that they were possibly exposed to COVID-19 after one of the attendees tested positive.

Although proof of vaccination was required at the door, multiple people have reported recent infections after traveling home from the event. Aaron Jorbin tweeted about his case today, and four more have been reported in a private channel on Post Status Slack.

There’s no way to know for certain whether the attendees who contracted COVID-19 caught the virus at the State of the Word, as many of them traveled from far away places and had meetups with other attendees outside of the main event.

Concerns about the lack of masks and no requirement for rapid tests began popping up prior to the event. From the perspective of viewing the livestream, masks were scant and attendees were quite close together in a small space.

The day before the event, the WHO warned that evidence suggested the new Omicron variant could escape prior immunity and would lead to surges with a high transmission rate. Studies were already showing reduced effectiveness of existing vaccines against the variant. On December 13, New York governor Kathy Hochul announced a new temporary indoor mask mandate for public spaces, which could be bypassed by requiring vaccines for entrance.

When asked how the State of the Word’s coordinators decided on the precautions, WordPress Executive Director Josepha Haden Chomphosy said the event met the local guidelines while allowing attendees to make their own choices for anything beyond the requirements.

“We followed the guidelines as laid out by the city,” Haden Chomphosy said. “Masks and hand sanitizer were liberally available throughout the venue, and we encouraged attendees to make informed decisions about their health.”

It has been well-documented that indoor masking can significantly reduce transmission, so it was curious that the event did not require them at this pivotal time when governments are taking more stringent measures to stop the spread of the virus.

Fortunately all those who were recently infected have reported mild illnesses, but the incident raises an important question for onlookers: Is this an indicator of how in-person WordCamps are going to go in 2022? There are already several on the schedule.

Whether or not attendees’ infections originated at the State of the Word or in outside gatherings is going to be impossible to pinpoint, but the nominal safety protocols sends a message to all those considering attending in-person events in 2022.

Since receiving the notification of possible exposure, many State of the Word attendees have been monitoring their health with tests. One attendee reported in Post Status Slack that she has had difficulty getting tested and is still waiting for one in the mail. In the meantime, she has opted out of a family gathering for Christmas as a safeguard.

“As someone who wants nothing more than to be able to attend WordCamp Europe or WordCamp US in person next year this doesn’t give me much confidence,” Gravity Forms CEO and co-founder Carl Hancock said. “With such a small event the COVID protocols could and should have been super tight to test things out for larger events. The lack of masks and social distancing at an indoor event without added protocols such as rapid testing for entry was disappointing to see.”

WordCamp organizers will need to consider how they can protect attendees beyond simply meeting the basic, local requirements, which may not fully acknowledge the nature of the current threat. They will also need to be responsive to the rapidly changing pandemic landscape and be ready to implement more safety protocols at the last minute, if necessary. If the State of the Word is any indication, future WordCamp organizers will need to have a plan for sending exposure notifications to attendees, in case the events become the source of an outbreak.

by Sarah Gooding at December 24, 2021 04:38 AM under News

December 23, 2021

BuddyPress: BuddyPress 10.0.0-beta2

Hello BuddyPress community!

🎶 All BuddyPress wants for Christmas🧑‍🎄 is you 🎵 … to test this new pre-release!

If you haven’t tested our first 10.0.0 beta release, here’s another opportunity to help us put the final touches on our next major release so that we make sure it will fit perfectly into your WordPress-/ BuddyPress-specific configuration.

Beta testing is very important, and we need you all, whether you’re a novice or an advanced user, a theme designer or a plugin author. Please contribute 🙏.

What has changed in 10.0.0-beta2?

  1. Custom Group Extensions: if you activated one or more plugins adding a new tab to your groups or if you built one or more plugins playing with the Group Extension API. It’s very important you take some time to make sure everything is working as expected in this area.
  2. Contribute to WordPress 5.9 beta tests as well! Let’s all check that BuddyPress pages are getting along well with Twenty Twenty-Two, the next WordPress default theme.
  3. The Private Messages component just got a new feature: messages thread exit. Users can now remove themselves from a conversation.

How to get 10.0.0-beta2?

The final release is slated for early January and we need your help to get there: please test 10.0.0-beta2. If you find a bug, please report it on our Trac or as a reply to this forum topic.

The BuddyPress core team is wishing you all: Merry Christmas 🎄

by Mathieu Viet at December 23, 2021 10:14 PM under releases

WPTavern: WordPress 5.9 Beta 4 Fixes 20 Bugs, Polishes Workflow for Switching to a Block Theme

WordPress 5.9 beta 4 was released this week with fixes for 20 bugs since beta 3. There are a few important changes to note in this release regarding how the WordPress admin will direct users who are exploring block themes.

Prior to a fix in beta 4, it was possible for users to switch to a block theme within the Customizer. This has been changed so that users will see a banner notifying them that the block theme is incompatible, if they try to switch within the Customizer. Here’s the commit message:

Starting in 5.9, block themes are not compatible with (do not support) Customizer; rather, they use the Site Editor. Viewing installed themes in Customizer, this commit adds an overlay message to alert users and give them a way to activate the block theme. Clicking on the “Activate” button activates the block theme and redirects back to the Appearance > Themes interface, where the user can then enter the Site Editor for customization.

Non-block themes are not affected by this change and continue to work in Customizer.

Having themes work only in the site editor or the Customizer, depending on which they support, is likely to be a confusing workflow for users when testing themes. This incompatibility message and redirection is necessary but not ideal for the long term. Streamlining the customization workflow will depend on how quickly the WordPress community is able to produce and adopt block themes.

Some testers also reported that the Site Editor doesn’t allow users to edit or preview non-active block themes. The preview only works with active themes. This isn’t necessarily a bug but rather a feature that needs to be discussed for the future. A ticket is open in the Gutenberg repository, recommending the implementation of a Live Preview for non-active block themes.

Featured patterns from the pattern directory should be displayed under Patterns in the the block inserter, but for some reason this wasn’t included in 5.9. It has been backported in beta 4.

This beta also adds a filter that allows developers to disable the login screen language switcher, which is a new feature coming in 5.9.

The release team has determined that a fifth beta will not be necessary, as of yesterday’s core dev chat. The revised 5.9 release schedule has RC1 shipping on January 4, 2022, and the official release on January 25.

by Sarah Gooding at December 23, 2021 06:42 PM under WordPress

WPTavern: WP Engine Acquires Brian Gardner’s Frost, Opens It to the Public

Brian Gardner announced today that WP Engine has acquired his latest project, Frost. In an email sent out to all customers, Gardner said his team had issued refunds to all current customers. The business model is changing, and Frost will be a freely-available project going forward and focus on full site editing.

Frost is a WordPress theme that Gardner released earlier this year as the main product of a new startup business. The original version was shipped as a child theme of Genesis, the StudioPress theme framework he had spent much of his WordPress career working on. WP Engine acquired StudioPress in 2018, and Gardner stepped down from his role in October 2019. It did not take him long to find his way back into the WordPress theme development game, bringing his personal style back to the theming world with Frost. Then, he landed a new job within WP Engine’s ranks in September.

“I am leading the WordPress Developer Relations team at WP Engine,” he said. “We have a simple mission: Accelerate innovation in WordPress and help the community transition to the block editor and Full Site Editing (né Gutenberg). In addition, we want to cultivate an interactive and immersive community resource that serves as a treasure chest of knowledge and operates as a conduit between the WordPress project and its users.”

I asked if there was something concrete he could share, maybe what form that would take, but he did not go into any other details. In general, the more resources the development and design community have around the block system, the faster the ecosystem can evolve. Only time will tell what Gardner’s team within WP Engine creates.

“When I joined WP Engine in late September, it was evident to me [WP Engine] saw the value in building relationships with designers, developers, and creators — within our Atlas product line, as well as with WordPress,” said Gardner. “While there was interest in Frost when I came on board, it wasn’t until my vision for our team became clear did an acquisition enter the picture. I recommended bringing Frost into the company and hiring Nick Diego.”

Diego is the creator of the Block Visibility and Icon Block plugins. He also began working on Frost in late September.

“In alignment with WP Engine’s core value of ‘Committed to Give Back,’ Frost is transitioning from a paid product to a free one,” said Gardner. “Given the change in business model, we issued full refunds to all active customers. By open-sourcing Frost and focusing on Full Site Editing, we hope to encourage a community of builders to experiment with the expanding capabilities of the block editor. We believe in its potential and look forward to helping it grow.”

Frost is open to everyone via the WP Engine themes repository on GitHub.

Leaping into Block Theming

When Gardner sold StudioPress in 2018, several factors played a part in the decision. Among them were the uncertainty around the Gutenberg project and WordPress’s future.

“It took some time for me to put the pieces together, but when I did, I saw just how powerful the block editor has become,” he said. “In particular, I am excited about block patterns, global styles, and building themes that folks can use to create beautiful websites with little effort.”

The result of his newfound enthusiasm around the block system was Frost. I have had the opportunity to tinker around with the theme. It has Gardner’s signature minimalist design style, a focus on readable typography, and ample breathing room for the content.

Simpler designs almost feel par for the course with any block theme these days, regardless of the theme author. What is likely to set Frost apart is its block patterns. It currently ships with 38 of them. The layouts should allow users to quickly set up their sites, along with the theme’s custom block styles.

“I am a huge fan of block patterns and see their potential when paired with the growing support of design/style elements within theme.json,” said Gardner of the things he is excited about. “Additionally, the site editor is something I feel, once mature, will be a game-changer for WordPress and those who build for it.”

The Block Pattern Explorer plugin was initially a part of the Frost library plugin, but Gardner and Diego pulled it out and make it available to everyone. They also wanted to serve the Frost patterns through it. The hope is that the enhancements already in place via the plugin find their way into core WordPress.

Frost theme patterns via Block Patterns Explorer

The design is a bit more polished than core. It includes category types, a feature the theme uses to separate its own pattern categories from others. The experimental explorer plugin allows users to preview patterns via desktop, tablet, and mobile views. And, it has a clear “Add Pattern” button for inserting a block pattern into the post.

Eventually, they plan to sunset the plugin once its features make their way into WordPress.

WordPress theming has come a long way since Gardner first dove in over a decade ago. Back then, users had to open template files to customize bits and pieces of their homepage. As we move toward WordPress 5.9, users will have that same power. However, they will modify Frost via the WordPress site editor instead of PHP files.

“Yes, I feel we are circling back to some degree,” he said. It was in response to a question of his early days designing themes for WordPress in comparison to now.

“While WordPress will never be solely a blogging platform ever again, it seems like the software is shedding its skin. The irony here is that we see WordPress used in sophisticated ways that — to be honest — I never thought would be possible. As for me, I believe in the power of simplicity. That has become my north star for everything I create and has allowed me to navigate the ebbs and flows of an ever-changing software and industry.”

by Justin Tadlock at December 23, 2021 03:35 PM under wp engine

Akismet: Do CAPTCHA and reCAPTCHA Protect WordPress Sites from Bots?

If you’ve used the internet anytime in the last decade, chances are you’ve had to pass a CAPTCHA or reCAPTCHA test. You may have done so many of these little quizzes that you groan just seeing one on a form.

There are quite a few different versions, but they all can help protect your WordPress website from spambots and make your life simpler.

In this post, we’ll cover the evolution of CAPTCHA and reCAPTCHA. We’ll also go over the different versions and the pros and cons of each one. Then, we’ll show you how to enable reCAPTCHA on WordPress and explore additional security measures you should implement.

What are CAPTCHA and reCAPTCHA?

CAPTCHA and reCAPTCHA serve the same purpose: protecting your website against bots and other security threats. They’re typically found on contact, comment, login, and password reset forms. But there are some key differences between the two safety checks. Let’s take a look at each one in detail. 

What is CAPTCHA?

The acronym CAPTCHA stands for Completely Automated Public Turing Test to Tell Computers and Humans Apart. It’s a mouthful, but the name says it all — it can decipher the difference between a human and a computer operator. Still, the specifics are important.

In the early 2000s, when it was created, CAPTCHA used a distorted text (letters and numbers) test to prevent bots from compromising websites.

When faced with a CAPTCHA, users needed to decipher broken text correctly to prove that they were, in fact, human. If they couldn’t identify the letters and numbers, the test wouldn’t submit their requests. 

This was revolutionary because most humans could pass it easily, but computers couldn’t solve it themselves. 

What is reCAPTCHA?

reCAPTCHA follows a similar principle, but instead of just utilizing meaningless text to see if the user is a real human, it was designed to help computers digitize old books and newspapers. The test was essentially split into two parts shown side-by-side — one traditional CAPTCHA to determine the humanity of the user, and a second image of letters from a piece of text the computer was trying to digitize. If the human could pass the first part, it would accept the user’s input for the second part as an accurate translation. 

Photo from http://www.captcha.net/

The point is that reCAPTCHA added a second part to the test to put millions of human users to work — a few seconds at a time — to digitize historical text for ongoing record keeping. Now sites were protected from bots and users weren’t totally wasting their time. 

Google purchased the technology in 2009 and improved upon it over the years. You see, artificial intelligence (AI) eventually became sophisticated enough to read and decipher even the most challenging text with 99.8 percent accuracy. By doing so, they could pass the test and trick it into thinking bots were humans. 

To deal with this new issue, reCAPTCHA made things even more challenging, introducing new options like the famous “I’m not a robot” check box. 

Today, reCAPTCHA is a widely-used security measure that protects websites from various spambots and cybercriminals by helping to ensure that comments on blog posts or in forums, and submissions on forms come from real people. 

What are the different versions of reCAPTCHA?

There are technically four different types of active reCAPTCHAs. Instead of text, some tests may use images, audio, or even math equations. They also utilize some variation of  “No CAPTCHA reCAPTCHA”, which determines whether a user is suspicious simply based on their behavior on a site.

If you’re setting up WordPress website security, you may have the option to choose between different reCAPTCHA types. For example, you can select a checkbox or background verification:

Here are the different types of reCAPTCHA:

  • ReCAPTCHA v2 (“I’m not a robot” checkbox): This is the simplest and easiest test to add with limited coding knowledge. Sometimes it passes or approves users right away and prompts them to check a box. Other times, it asks them to verify that they’re human with a puzzle challenge.
  • ReCAPTCHA v2 (Invisible reCAPTCHA badge): For this version, there’s usually no checkbox. It simply uses an existing button on your site or a JavaScript API call for verification. You’ll see a badge that says Protected by reCAPTCHA. Essentially, verification happens in the background. Only the strangest behavior will prompt a test.
  • ReCAPTCHA v2 (Android): This version utilizes a reCAPTCHA Android library that’s part of Google Play’s SafetyNet APIs. This validates requests from within an Android app, so it’s not the right choice to use for a WordPress site. 
  • ReCAPTCHA v3: This is the most advanced and discreet of all the versions. Visitors won’t even know it’s happening. It uses a JavaScript API and automatically assigns a score to each user to approve or deny them. This version also gives more advanced developers extended flexibility for integrations with other security measures to dictate the level of site security. 
  • ReCAPTCHA Enterprise: Like v3, this runs in the background. It gives each site visitor a score based on their behavior. If a visitor is deemed suspicious, it may require them to verify their identity through custom options determined by each site — two-factor authentication or email verification. As its name implies, this is typically for enterprise-level sites and requires advanced customization.

What should I consider when choosing a reCAPTCHA version?

Since reCAPTCHA Enterprise is reserved for larger companies, it’s safe to say that most websites will need either reCAPTCHA v2 or reCAPTCHA v3. Still, it’s important to know what you’re getting into with each one. 

What are the pros and cons of reCAPTCHA v2? 

The most significant advantage of reCAPTCHA v2 is that, whether you choose to include the “I’m not a robot” checkbox or leave it discreetly running in the background, it protects you from spam while offering humans the opportunity to prove that they’re real. 

With the invisible version, if it detects suspicious behavior, it will require a test. If it doesn’t, the user can proceed none the wiser. 

However, any reCAPTCHA v2 test can seriously hurt the user experience for site visitors. To combat increasingly smart AI technology, tests have become so tricky that many real humans have trouble passing.

The test’s difficulty may leave users frustrated, wondering why they fail when they are actual humans. In fact, the situation has become so bad that popular tech magazines give people tips on passing these tests.

Plus, it’s also important to consider the accessibility of reCAPTCHAs. A graphical puzzle, for example, would be inaccessible for people who have vision impairments. So, if you do decide to use reCAPTCHA v2, it’s important to present other options, like audio or text-based tests.

What are the pros and cons of reCAPTCHA v3?

reCAPTCHA v3 was specifically designed to improve the user experience. With no verification tests to complete, it’s seamless. Website visitors are happily unaware of the entire process. 

It also gives administrators much more control. With reCAPTCHA v3, you have advanced options to customize your interaction with Google’s API to adjust scoring thresholds and define what is considered suspicious behavior. 

Some may consider this added control a good thing, while others may find it a weighty and cumbersome responsibility. Additionally, some critics believe that reCAPTCHA v3 may pose a privacy risk because it provides Google with too much data. 

In addition, reCAPTCHA v3 can deter good bots from doing important work. People tend to remember the villains like spambots, but forget about their positive counterparts. Good bots deal with things like SEO and performance monitoring. If you get in their way, your overall website success could suffer. 

A final downside is that, since spam scoring happens in the background, there’s no alternative test provided to suspicious users (like with the invisible reCAPTCHA v2 badge). Visitors who are wrongly flagged as bots don’t have an opportunity to prove their legitimacy. This means that you could turn away real customers, clients, and followers.

Can bots bypass reCAPTCHA?

This is the big question. Unfortunately, the answer may not be straightforward or definitive.

The many versions of reCAPTCHA are evidence that malicious spambots evolve quickly.

They’re constantly adapting to outsmart reCAPTCHA. When the original CAPTCHA was introduced, it was revolutionary in its ability to decipher between real users and bots. But it didn’t take long before the bots caught on. People have even started using human labor to get past tests manually. 

Computer scientists are regularly working to increase the effectiveness of reCAPTCHA, however. Some have proposed new challenges, like puzzles that require a user to maneuver pieces or nursery rhyme completion games based on the location of site visitors.

That’s one major reason tests have become so frustrating for real users — difficulty has had to increase to stay ahead of computer learning. Unfortunately, it seems we’re at a point where to continue to outsmart computers, we have to make tests that are sometimes too difficult for real users to solve — a major problem. 

It’s gotten so bad that Amazon now owns a patent for a new kind of CAPTCHA-esque test that is so difficult to solve that only a computer can do it. Meaning… if you pass, you’ve actually failed because you’ve proven that you can’t possibly be human. 

So can reCAPTCHA stop bots? 

Yes, it can stop many of them. But it can’t stop them all. And the percentage of bots that make it through is increasing by the day. This means you can’t simply rely on reCAPTCHA to prevent spam submissions. You’d be signing up for a highly imperfect, temporary system that’s only going to get less effective. 

So what should you do? 

Other security measures to protect your website from spambots

1. Lock down your comment forms

The best place to start is by configuring your WordPress comments in a way that protects your site against bots. Navigate to Settings → Discussion in your site dashboard and and consider requiring:

  • Comment authors to submit a name and email
  • Users to be registered and logged in to comment
  • Comments to be manually approved before publication
  • Authors to have a previously approved comment to submit a new one

In the Comment Moderation box, you can also flag a comment that contains a certain number of links — lots of links is a common indication of spam. Or, if you’re getting a lot of spam that contains certain words, email addresses, IP addresses, and other characteristics, you can ban them entirely.

2. Protect your login forms

To lock down your login forms without using a CAPTCHA, you can implement two-factor authentication. This requires a user to have both login details and a physical device to access your site. When someone logs in, they’ll have to enter a username and password as well as a one-time code that’s sent to the mobile device on file. This is virtually impossible for bots to get past.

3. Use honeypot

Honeypots are an option for protecting contact forms. Think of them as a mouse trap for bots. They essentially create a hidden field in your forms that isn’t visible to site visitors but that can be seen by spambots. If the field is filled out, the bot is stopped in its tracks.

Many contact form plugins allow you to implement this feature in their default settings.

4. Protect your comment and contact forms with Akismet

Akismet is hands-down the best way to eliminate the headaches of bots (or even real humans) spamming your comments or sending unwanted messages through forms on your site. 

With millions of users, Akismet has blocked over 500,000,000,000 spam submissions at the time of writing this article. With each one, it learns a bit more. So while bots might have AI to get past reCAPTCHAs, Akismet’s AI is working to protect your site in an entirely different way. 

Akismet can accurately identify spammy behavior and keeps a blocklist of words, IP addresses, names, and emails to prevent pests. Plus, it gives you control to provide feedback about any spam it misses or real comments that it accidentally flagged. Then, it customizes its spam-fighting solution just for your site. Amazing. 

You can get a free version of Akismet for your personal blog. In addition, there are three paid plans for commercial sites starting at just $10 per month. 

Win the fight against spam bots

Spam bots and less-than-ethical cyber actors are always trying to take advantage of visitors and the sites they love (like yours!). They can cause annoyance or even do real-world damage.

CAPTCHA and reCAPTCHA have evolved many times over the years and continue to be one trusted way to prevent bots from flooding sites. But these solutions aren’t perfect, and sites need other measures to prevent spam from causing trouble. Consider protecting login forms with two-factor authentication, deploying WordPress best-practices, and using Akismet to filter comment and contact form submissions automatically. 

by Simon Keating at December 23, 2021 10:25 AM under Spam

Post Status: Post Status Excerpt (No. 38) — In Person For State of the Word

“I believe our community can make significant contributions to Gutenberg and the Block Editor.” —Cory Miller

In this episode of Post Status Excerpt, Cory shares his experience among the 30+ individuals who attended the State of the Word in New York in person. David and Cory talk about how Matt presented himself, his views on the necessary ratio of community contributions to open source projects, Five for the Future, the next generation of leaders, and what it means to give back to the community and WordPress core.

Also: Cory hints at what Post Status will be doing in 2022 when it comes to giving back — along with how Post Status will encourage and assist people in contributing to the WordPress community.

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: Yoast SEO

Yoast is SEO for everyone. Yoast SEO Premium gives you 24/7 support and extra features like internal linking, social previews, a redirect manager, tutorial videos, and integration with Google Webmaster Tools. Get on board today with the premiere SEO plugin for WordPress — Yoast.

Transcript

David Bisset: [00:00:00] Since I wasn't there because as I was telling somebody earlier, I couldn't, hurt my Twitter game by being there. I had to be in front of my computer with with my keyboards and making a bingo games and hashtag 

Cory Miller: that's my fondest memories of you, David is like going to these events and somebody live tweeting.

It's like, here's this dimension media person. And it's like, holy crap. 

David Bisset: Yeah. They used to call me dementia media. So. 

Cory Miller: Signature though is still in the lodge waiting. And I remember when Twitter kind of first came out and it was a thing to live tweet a lot. And but I always like yours because you always summarize what.

The takeaway is like you're starring the cool quotes along the way. And that's part of what we're trying to do at post status is give you the too long, didn't read content, the inside analysis commentary for the stuff that matters to you. So that's your claim to fame or friend? 

David Bisset: Yeah. Yeah.

Well, that's how I took notes and I really didn't care who listened. I that's how I just took [00:01:00] notes. It kind of knocked off a couple of killed a couple birds with one stone, but enough about me. Let's. Let's talk about you being there in person. And can you tell me where this place w what was this place like?

Was it in like a tall building or like, I hear it was tumblers all the offices or something. 

Cory Miller: So my understanding was it's the automatics new event space in New York city. And of course, some of their investors in New York city and things like that. And it was incredible space. I would try to guess how big of a space it was.

David Bisset: I couldn't tell, the camera angles were just, they did the camera angles just right. So you never got a true dimension of the room on the live stream

 yeah, that's 

Cory Miller: what I just said. I do more tell me I bet you it's about 15,000 to 20,000 square feet in there that I saw really great space. And it's a whole floor of a billion is my understanding, but it was gorgeous.

And then there's the sunset of New York city out the window rep for state of the word. And it was really good, but I. I, you know, I got to see [00:02:00] Matt about a month ago and San Francisco, we got to talk and he mentioned inviting you David, to stay the word. And also he'd love to have Post Status there. So I was like, yes, we're going to make that happen.

I know you had things that come up, you couldn't be there. But you know, I want to guess there's about 25 30 people there in person. And it was a really nice night. I mean, automatic. Rolled out the carpet for all of us, which is super nice. Matt as always is a charming, elegant presenter and host and did a fantastic job.

I thought it was normal. You know, I want to give him kudos, but like, he's really good on stage. 

David Bisset: Well he was different this time and I realized I wasn't in the room, but I almost had, I have a 30 inch monitor. So I saw a lot of him and I saw a lot of his facial expressions pretty clearly. There was there was something different about them in a good way.

And I can't, I think he, you know, not just not to put emotions on a person, I'm pretty sure he was nervous in some regard. I think anybody is nervous to some extent of public speaking, but he definitely had some sort of [00:03:00] energy that he was releasing. And you know, me, I record animated gifs all the time.

I decided not to post, I don't know what I decided to post, but in the very beginning before he was kind of. He was almost dancing a jig right before way before the state of the word started up on stage. So he was really excited and really, you know, anxious maybe, but you could just see the energy even before he spoke anything.

You could just see the pent up energy that he had, which was reflected later, by the way. 

Cory Miller: And not trying to speak for him, but if for me, I go, I haven't done this in two years. There's some cool people here that I have invited to be here and I'm talking about the thing that I want to spend all of my life doing.

And so. Yeah, totally. I spoke a couple of weeks ago at our three recurring revenue retreat. And I remember getting feeling nervous cause I'm like I was rusty, you know? And there was this quote and I'm trying to remember what it was, but it's basically turning fear, the anxiety into [00:04:00] energy and excitement.

And that's what I tried to do is like channel that's now Matt doesn't need my public speaking tips, but those are my thoughts. What I. As long as I've known him. And it goes back to 2008, where camp DFW in Frisco, Texas. There's one thing that's always standard with Matt and that is his passion for the WordPress open source project.

Yeah. So, you know, and it just has never wavered. And I think he mentioned on state of the word that he wants to spend the rest of his life. He's 38 rest of this. On WordPress project. And I totally believe this. This is his contribution to humidity, you know, and at Post Status makers of the open web WordPress, this 42% of this big number that he shared out there, I think we should all take a moment, take a big deep breath and go.

The web is still in its infancy. I don't know, life-stage wise where it would be comparatively to like a human, but it's still early, like in history of all that's going to happen in this world. In the future, the web is [00:05:00] still kind of an infant. And if you think about it, our place is WordPress makers.

People that build on WordPress, extend WordPress, teach WordPress, all that stuff people have. Post-test the business to WordPress is this is historic and what we've been doing. I started with WordPress, my first blog in 2006. That was just me using this amazing platform called WordPress, but, you know, history historically sake and going through.

42%, that number, it just keeps getting bigger. And that's exciting for us, those of us that make our living with on for WordPress. 

David Bisset: Yeah, he did. I got a couple of quotes out of them and it was, you know, livestream is a little bit easier. Cause you can pause and rewind a little bit just to make sure, because you want to get it as close as possible. Regarding the The WordPress space.

He did say the court word press belongs. Just, you know, just to anybody it's not just you or me it's regardless of economic or political situations. And he said something about WordPress can't be [00:06:00] created by just one company and people adding a line of code is like giving that, give a penny, take a penny and I feel like there's quite a number of people that thanks to five for the future that are giving that he was, he actually said he actually gave a quote or something about, I don't know if you caught it. He was studying other CMSs. And he said for every dollar that has made $20 has made in the ecosystem.

And that's ratio is how they came up with the five for the future. Did you know that. I did not. 

Cory Miller: You know, I don't know how long, far, because the future has been out, but there's two things I wanted to highlight. Part of State of the Word you've just put a square in this one, which is contributing back to core five for the future.

I don't know how long that's been going, but, you know, I know our Post Status members. I mentioned this to Matt. They, you know, like me and I themes, we had, let's say at her height, I want to say 27, 28 people or something like that. And you go, okay, how do we, excuse me, our team or company contribute to core.

We don't have the profit bandwidth, all that stuff to take a full-time dev for instance 

David Bisset: right

Cory Miller: [00:07:00] off. And I mentioned this because I know there's so many giving hearts in WordPress and founders and entrepreneurs and people that lead companies. That benefit from WordPress that want to do five for the future.

It's tough. I get it from your standpoint of how do we meaningfully contributed, even though we believe we are contributing to the ecosystem or what we're doing. And I grant that a hundred percent, what we want to do at Post Status though I did tag on the contributions that push to continue to contribute to core. 

I think that's the reflective I dunno, KPI for the ecosystem too, by the way. But, and I know there's companies that do it, even if it doesn't fall under the strict banner of farm from feature or whatever it is that like, they're doing it just like, we felt like we were contributing to WordPress for years.

What I want to do is translate that help that better for our Post Status crowd to, to actually meaningfully contribute. So Courtney Robertson on our team, who is also great, awesome person at Go Daddy pro is really [00:08:00] taking the banner for the contributor days for post status. So next year, we're going to be talking about enrolling out contributor days, but that's one thing to say, we're going to do a contributor day, right?

That's nothing new. This is where Courtney's idea was. Let's go to the team leads and ask for their wishlist. Things they would love for people of post status to contribute. And from that gives us something that we can go. Let's say we take that day eight hours. And we're going to show up for contributor today. at Post Status, were gonna, make it a contribute and then pick something off the board.

So we're already trying to help you do a little thinking in the stuff that's going to be most valuable to the core team, core teams that are doing things, and then say pick one off the list and try to get as far as you can. You know, and I'm excited about that. I know it's very meaningfully and for good reason to Matt, both as CEO of automatic, but also the leader of the WordPress open source project.

And that was one thing that for sure came out, you know, to me in that call.

David Bisset: Yeah. There, [00:09:00] there was quite a bit talk about, there was talk about the contributors earlier in the live stream. And then afterwards it was how to get new and especially young people involved and you know, young people, they have so many distractions these days, but they have more time and they more energy.

Then we do cause we were running, families were running businesses and so forth like that. And I liked the question that Allie posed about. How can these people learn WordPress? But contributing I, you know, I, I lost my thought there for a second, but I really wanted to. I was hoping that the five for the future was going to spark some more ideas.

And I think it will, because if you have people that are, if companies are being sponsored or sponsoring people to work on contributing and there should be. Like an on-ramp in there somewhere for people who want to get into it too, because you know, like many people have pointed out. You have to, unless you're a young person within, [00:10:00] with an inordinate amount of time, you don't have the time to do that.

So even for a couple of hours, and I think part of five for the future, and some people have brought this, you know, written about it after state of the word. And about that five for the future, maybe someday five for the future can be expanded a bit to help some people not only contribute, but also kind of help them find people are willing to cover them so they can contribute whether that's financially or some other means.

Or maybe it's just some sort of internship if somebody is brand new and needs to be exposed to anything in WordPress. So I think five for the future is a great thing now, and I think it has got room to grow, but you know, it needs that it needs. Momentum of support right now and whether that's the repost status and all these other methods, I think we're still seeing the early stages of a comprehensive program for contributing.

Cory Miller: And I understand the apprehensions from companies and founders and leaders. You know, you have to make a [00:11:00] profit for sure. And you're like, okay, I want to give back, but I, can't just, I'm not a nonprofit, I'm a profit in enterprise and everything, and I want to help with them and contribute to these.

But something you mentioned just a second ago was pinged for my second thought. And when you said next generation, the no, our intern Here and has helping to post that by the way. But I also know your passion, heart for next generation with WordPress too. And it, that just brings up, well, one Sandy Edwards work with kids camp.

Talk to her about that a couple of weeks ago at our three, how post-test wants to contribute to that. But the other thing, the second theme is Gutenberg. You know, you can't probably talk to Matt about WordPress without hearing Gutenberg and for good reason, here's the thing. I was not a vocal advocate at all of ruling out Gutenberg in the way we did 

David Bisset: I like how politically, that was so eloquently put, but yes. 

Cory Miller: Yeah, I thought it was way early and everything, and it took me a year or two to finally [00:12:00] okay. You know, use Gutenberg and but it here's the reality situation, no matter what, the way we feel about the past, it is here and it's not going away.

So you hear this over and over from Matt and for good reasons, there's some cool stuff coming. That he talked about the styles, some of the typical libraries. I see that as a very similar innovation and direction, that themes as a whole went when I started, I think back in 2008, There's so much innovation to do.

So first and foremost, it's here. We've got to accept it and move on. And I think what his plea here was too, and again, probably my nuance. It's not, I'm not going to play, but I'm just saying my nuances. It's not going away. We should accept it and embrace it. And then the question becomes, how do we improve that?

And I think our community can make considerable contribution. To the conversation and the actual implementation of Gutenberg, the block editor for WordPress. I'll tell ya, I'm looking, I'm going to redo my [00:13:00] personal site cause I want to start blogging every day. And I say blogging, it's going to be just sharing my thoughts.

Not just on Twitter, but you know, my site and I'm probably going to pig blank canvas. I'm still up in the air and I want to use. And I want to really like embrace using it and see what I, what my takeaways are. And I did that back in August with the click publish. I want to use Gutenberg because I've criss cross the threshold.

And for me, I'll tell you the big benefit David was used to because no one even believes I'm ever been a developer. I'm not, but I was like 

David Bisset: Don't be ashamed. I'm a programmer. I do websites. I do plug-ins. I do all of that. And what does Matt say to everybody that I am during state of the word?

I tweet a lot. So that's my claim to fame. That'll be on my tombstone where the developer, but you're not a developer, but 

Cory Miller: I was looking for, I wanted to do a buy now button or something. You know, I just wanted to button and I can't, I can [00:14:00] figure it out. I mean, I don't want to figure out how to write a button coordination, or, CSS or whatever.

So I, what I normally would have done is went look for a plugin. I can't remember. I want to say max plugins or something was that max buttons was out there as a plug in. Well, and I can't remember what might've been AGA again. But it was like, that's a block that was a game changer for me to go.

You don't have to get something extra to do things you want to do in the post. That was pretty cool turning point for me. It's not there. It's getting better, this awesome people working on it. And I think we should. We can and should contribute to the conversation and the implementation once it gets going, because it's not going away.

And back to your point about next generation Syed Balkhi that if you WP Beginner and awesome motive, I remember asking him a couple of years about Gutenberg. I was like I kind of expect he's going to get on the bandwagon. Let me it's like, we don't like it. It shouldn't be out there. And Syed was like, I love it.

I was like why? And he goes, because the next generation look at how people are [00:15:00] publishing today and it's changed from what you and I learned now. He's like, he's over 10 years, 15 years younger than me. But like even young kids like Olivia and like the platforms have changed in the way to express yourself change.

And that always stuck with me what Syed said. And so I really have high hopes for Gutenberg. Yeah, again, now that I am in strong, like of it. 

David Bisset: So another thing Matt talked about which I'm actually a little bit surprised he did bring it up. I'm wondering who, by the way, Tuesday was when WordPress 5.9 was supposed to be out before they pushed it to January. So I talked to Anne McCarthy today. And first of all, I mentioned to her, like you mentioned, like 5.0 release when Gutenberg first came up, was rough around the edges. And she has assured me that the full site editor coming out in January with 5.9 is it may not have the entire kitchen sink, but it is very stable and doable. So I can't wait to share that [00:16:00] interview with everybody, but Matt did call out acquisitions and I like, and I thought is this one of the things that if 5.9 was out, would he gone over more quickly? I don't know, but they got on one slide. He started with 42 logos. And I thought there were more acquisitions than that.

I'll have to go back to our Post Status tracker. But he had 42 logos up there and then he proceeded with, and I'm not a finance person. I'm just going to take his word for it. , his charts were taken from other people's analysis. He gave proper credit to them, but he says the number of the deals that are happening in the tech space, he says there were 10,000 transactions in the first nine months of 2021 alone.

Which is up 24% over the last year. And then he brought out another chart that was called inflows to stocks. And I couldn't even, I don't even know what that was. I was, but all I know is there was a big bar at the end with the, with our year in it though. And I guess what he was trying to prove is that [00:17:00] don't panic.

The acquisition space is not unique to the WordPress space right now. This is all going, you know, bonkers. And it's not just WordPress. So I, you know, with you being a business person, how did you feel, do you feel that was properly delivered or delivered? Well, do you think he got the message.

Cory Miller: But the question I think about that is what prompted him to even do the slides, you know, and that's the bigger question we always want to be thinking about here, you know, for our people is what is the founder co-founder of WordPress, the movement of open source project. Fill the need to say that. And we have some sense of the people that are like change sucks.

Nobody likes change, you know, and the fact of the matter, if you bullet down these acquisitions, why would anybody even care? It's because it could potentially change something that I'm used to doing. And I'm not saying it's good, right? Bad, wrong indifferent. I'm just saying, you know, I think change is [00:18:00] tough and I've heard some sentiment from the WordPress community about, I don't even recognize it anymore and all this stuff.

And then I just go down, like, here's my comparison for it is when I left.iThemes and started this new journey and Post Status . It was over a year before I became a partner and it was probably nine months before Brian and I even started talking about me becoming a partner. There was a big gap there and I was like, I didn't know what I was going to do next and trying to figure that out.

But I did one simple thing, which was, I'm never going to say publicly privately, I'm leaving WordPress. I joked all the time. I'm going to be a WordPress user a blogger, which I was still am. But the important thing is I didn't want to lose or even think all the amazing friendships I've made over 15 years being in the space.

To say, I'm saying goodbye to you. That's not it. You heard Pippin Williamson when he left Sandhill dev that he was like, I'm not saying about a difference, but I need to step away from the project. [00:19:00] And I just go that sentiment to me comes back to this acquisition. Like things are changing, all that stuff.

I, I totally get that. I'm not trying to change your emotion. My way of thinking about it though, is the people are still here and that's what matters. I've known you David for God. Has it been 10 years since 

I've known you for 10 years? 

David Bisset: Since the first conference in Arizona whose name is escaping my. I think that's where we may have known.

We may have known each other prior to that. That's the first time we met in person, I think officially, 

Cory Miller: but you know, the premise of all, this is like, the people are still here, for the most part. Now you're always going to get people leaving the ecosystem, leaving it, you know, and coming in new people, coming in, who I met, one of our post-test members was when Stina and I'd love to hear her story.

She was there. Got invited to State of the Word we got to talk Post Status member and That's a new person, I didn't know, a year ago or two years ago, you [00:20:00] know? And so some may leave and you're always going to have that in some, and cause there was even a picture. I think one of those slides, David of Kim. Oh, you know, and you think about people who have left and for instance, this world Kim back in the day but I saw her picture on one of those slides, you know, and it made me smile, but all that to say, WordPress is not about code it's about the people.

And that is what I hang on. I'm not trying to change your heart, your feelings, but I'm just saying, if you think about it, go it's about the people. No matter if it's a team, if it's outside of WordPress, whatever it is, it's like, what matters are the people there? And are we growing together and all that?

So that's the way I think about that, but that the merger is that it's I it's right for people to go and question what's what the heck's going on here. Things are changing on that space, but I still go the Michelle Frechette. Actually as a team member of people, some of my best friends and my former team and I themes now, is that interesting?

Well, I've known Michelle for a long time and now she's a part of the scene. That's cool. You know, that, that change happened where gives, [00:21:00] got by. And cellar rolled out and she moved over roles and now we get to work with her Post Status too. And again, I just call back to, if you're worried about that, just go back to the people now there's other worries, but I just, the heart of it is about people.

David Bisset: Yeah. And 

I also, I have also have a motto too, in terms of you don't let the people that are leaving a community, distract you from who is coming into the community or who they should, or who should be invited into the community and vice versa. But don't let one side distract you from who's coming in versus who's going out and that sort of thing.

And I think we're doing a pretty good job with that. What happened after state of the word after it ended what happened. 

Cory Miller: Well, so there was about, I can't remember how many, but at least 20 of us, I could probably adapt touch straight back to Post Status and we all kind of stayed at the same hotel and had a little, two day fun before the event and all that stuff.

And so a bunch of us went back to our hotel and we're at the restaurant, the hotel restaurant bar, [00:22:00] and just kinda talking, you know, and I got to meet great people. I've just met in like Robert. Who runs OSTP training there? I got to see again for the third time, Robert Jacoby of cloud waves. The hero press couple Kate, and Tofor, I'm trying to think of othersAC Morse was there? Gravity forms. 

David Bisset: Aaron Campbell was there. 

Cory Miller: The Aaron and I laughed. He lives in Oklahoma. Like me, he's literally an hour away. I bet it'd take me 45 minutes to be on his doorstep and vice versa. And we're like, we had to laugh. So we're sitting in New York city Soho, somewhere in the coffee shop. We're like, isn't it funny how we have to either go out of the country or to go across the states to see each other when we live like that close to each other.

And I love Aaron. He has such a great. For WordPress, all things WordPress and I love what he's doing. 

David Bisset: Bob was there too. Of course, he traveled by train. He traveled by training the width of the Wu train clan. And it was, I think one of the best moments of the night was when he got up to ask the question and he had the simplest of questions, which was like, he [00:23:00] like, what's up for WooCommerce or in the next year I traveled 2000 miles to ask this question.

And how did Matt respond 

Cory Miller: that's all the bingo card and slack Post Status slack light up because Bob asked it, you know, finally he got the invoke. Woo. Yeah. I love Bob. Bob does and has been around for a long time too. And what I said about him personally at the vent was the one thing I admire about him is he has just consistently showed up.

And get work in this space and has mad respect from everybody because of it. So we sponsored his train trip out because we wanted to I mean, Bob is such a vital member of the WordPress community and then specifically WooCommerse. So Bob did all of that kind of community logistic, wrangling there, in addition to being like, and he was trying to record, he set up a studio in his room and I got to be with Robbie and Robert and Bob and

do the woo podcasts there. So, it was a great time for that on the note of getting people together. And Post Status [00:24:00] specifically we're right now getting our in person. Camps together for Post Status Brian and intended to do it last year. And you know what, two years ago, and you know what happened, right.

But this year we're putting some plans in place to get together in a small way to talk shop, to do life together as a community. I would love for everybody to be there next. December 22nd for, it's going to 

David Bisset: say, as we wrap up here, what is the schedule look like for our post status members?

What do they, pay attention to?

Cory Miller: So we're doing a year in, remember huddle. We're going to be doing these next year, by the way, in which I'll be talking about, but our member huddle you're in next Wednesday, December 22nd, 11:00 AM central time. There'll be zoom links in slack and all that.

And so. We're going to do our, that member huddle. How-to it's going to be one part like reflective review last year, thinking about next year. So look back, look forward, and then we're going to do some fun stuff. I want you to meet the Post Status team. All the people that are doing all this crazy awesome [00:25:00] stuff behind the scenes that you don't all see.

And then talk about some of the things we got in store for our Post Status community. A couple of times I've heard people say energy with post status and it is, and it ain't just me, by the way, it's people like David who had been here faithfully for years, Michelle Frechette, Courtney Robertson, Taleesha, you'll get to meet her.

She's our new director of operations and all kinds of people in between. I can't wait to do that. And then laugh together. Our theme for the ongoing, I hesitate to say it's going to be 2022, because I just want it to be forever is give. Together. 

David Bisset: What was that again?

Cory Miller: Give, grow together. It's part of what I want to be our member mantra.

The thing we come to post to us and say, I'm here to give of myself my time, talent, treasure, all that stuff. Not true necessarily, but like give up myself in the spirit of open source to the commuity. To each other. Second is I'm here to grow. I want to grow myself. I want to grow my business.

I want to grow my career. We've got specific plans for the growth side and then together, it's [00:26:00] just the thing that wraps everything together. It's not I. It's not you. It's always, we at Post Status. It's not just me. I happen to be on, you know, I had my face out there and stuff like that. But if this is truly a community and truly a team too, and I want us to just emphasize those three things, give in spirit of WordPress, same thing, just give to each other in the community business of WordPress second is to grow commit. You want to be here, let's grow yourself, grow professionally, grow your business, whatever it is, come here to grow. And then to do it together do it all of us together. So, even our products, like, as you will know David is called and that's a Portuguese word for probably mispronounced it, but together we're together.

So it's been a theme of my life even before clinical campaigns and the COVID time. But I really mean it next year as I'm going to do these things from in-person camps, how we do slack, how we do some of the cohorts, we're going to be rolling out. And I hope you'll show up next week and we can talk more about that and get your feet.

David Bisset: What was the date again?

Cory Miller: [00:27:00] December 22nd.

David Bisset: So December 22nd, Wednesday, are we going to see any sign of a state of post status with you in a suit? Is that something we can look forward to? 

Cory Miller: You're probably not the second 

David Bisset: the people that are listening for the people that are listening at home.

Cory shook his head so quickly that I thought his neck was about to snap. 

Cory Miller: Yeah, I think we should do these types of things where as our leader of post, as getting in front listing talk, discuss, put things out there that help you learn and grow and all that with postdocs, for sure. And I always want to get to Canada.

So maybe to the first to the second one, the suit, you know, I mean, I've got two suits. I probably don't fit currently. So. I think you're more likely to see me in a Chewbacca outfit than a suit, but no shady. Anybody else? It's just, 

David Bisset: no, you have to stand up. You gotta make yourself stand out with all these other state of the blah-blah-blah.

I mean, if Matt does a [00:28:00] suit, I think. Any, if you're going to wear a hairy Chewbacca outfit, I think that's a good countermove. But anyway, 

Cory Miller: Somebody is gonna remember this and come back and say, Cory memory, you say you do that. 

David Bisset: Oh, people will remember it. I might have a little bit of a night terror about it. I've got a thing against Wookiees. But other than that, I think it's a fantastic idea. Well, it sounds like you had a blast and it was a blast watching. I see you in some of the photos. Sometimes you're in the background You're in the background photo bombing. It's fantastic. I'm glad that this happened and I'm glad to see Matt so open.

Maybe it was because it was a smaller venue or it was the fact that there wasn't a word campy west surrounding Matt. You know how draining that is even to, just to be at a work camp us and then, and that WordCamp us with a talk in front of a thousand, 2000 people, it would look like a really nice event with a ton of energy, but.

Personable intimate. And I'm glad you all in this, in the few got to experience that. And I, of course, next year though, [00:29:00] or next time this happens, hopefully it will be under different circumstances and we'll have more people. In fact, think he said, if all goes well, San Diego is going to be the work camp spot for 20, 22.

Have you ever been to Sandy? Oh, really? I've never been. So it'll be interesting for me. Was there anything else that you wanted to share? I think we, it was good seeing you. It was good seeing you. I'm glad you're home safe. And then it sounded like they do all the safety precautions and everything, which was fantastic.

I'm glad they did that. And it was good to see Josepha and the others there as well representing so great. So next time. Let's it sounds like we're going to talk about wrapping up our thoughts about the year with the biggest news stories that you think Corey or the most influential to you personally.

And we've asked the same question to our post status members, this awesome service zip message. I want to say zap message, but that sounds more painful. Zip message. It's zip message. And we're encouraging people [00:30:00] to go in there and just leave a brief clip about what story to them was the most influential for WordPress this year.

And to them personally, and maybe by the time we talk next time, we will have a couple of us to talk about and share our own as well.

Cory Miller: Thanks, david. And thanks everybody.

by David Bisset at December 23, 2021 04:32 AM under The Excerpt

WPTavern: Gutenberg 12.2 Focuses on User Experience Improvements

Some Gutenberg plugin releases feel like heavy-hitters with new user-facing features. Others, such as today’s version 12.2 update, smooth over problems and create a more well-rounded experience.

Switching between the site editor and templates is smoother. The color picker is no longer a hot mess. And, border controls now use the tools panel approach of allowing users to enable or disable the options they want.

Contributors have made progress on updating the Comments Query Loop block, which will eventually be the backbone of displaying comments in block themes. One of the tallest hurdles was making nested comments work. With that now fixed, moving forward with other comment-related components should be less problematic. The latest release also introduced the Comments Pagination Numbers block for handling paginated comment lists.

View Templates Without a Page Reload

Templates view in the site editor.

When Gutenberg 12.1 launched two weeks ago, I was happy to see the new and much improved slide-out panel in the site editor for viewing templates. My primary complaint: it was slow. Switching between the editor and template view required a page reload.

In the latest 12.2 release, this has all changed. Thanks to client-side routing in the site editor, the transition between the editor and templates feels fast and smooth.

Changes like this are one of the reasons I have welcomed the postponement of WordPress 5.9 until late January. Some of these little wrinkles needed ironing before showing the site editor to the world.

Improved Color Picker

Color picker popup.

Gutenberg 12.2 introduces a much-improved color picker. The previous iteration was unwieldy, bulky to the point of being an annoyance. Users would have to scroll and scroll and scroll some more just to jump between changing a block’s text color and its link color. This was especially true if the theme showed both its colors and those from core.

The latest iteration tightens up the UI to the point where users can see the text, background, and link color options all at once. If they want to customize any of them, they can click on one to pull up the color picker popup.

Perhaps this change will open the door for other color options in the future, such as one for link hover/focus. It would have been far too messy in the old UI. However, the new minimalist design leaves ample room.

I would love to see the border-color control get the same treatment. However, there is a separate ticket that offers more fine-tuned control.

Font Size UI Change

Numbered-style font-size selector.

The font size control for supported blocks looks much different. It shows a list of numbered buttons for themes with five or fewer custom sizes. The font-size name appears when one is selected. Otherwise, it is simply a list of numbers with no context.

I have generally liked the progress made toward updating the block options UI. But, I am not a fan of this change. As a user, what do these numbers even mean? Is the “1” size small or medium? There is no way of knowing without testing it. Plus, the context will change from theme to theme. A UI change like this may have been OK on the back of a standardized naming scheme. However, that will be tough to implement after three years of usage.

In general, clicking a single button feels like a better experience than clicking a dropdown, followed by a second click of making a selection. I am just not sure that it works here. However, I am open to seeing where it goes upon further iteration.

There is also no visible way to clear the current selection and return to the default size. If the theme supports custom sizes, users can switch to the “Custom” field and clear it out. This is not obvious unless you stumble upon it. Users could also hit the “Reset All” button, but doing so resets all typography options.

The easiest way to avoid this UI change is for theme authors to register at least six custom font sizes. The option will automatically revert to its former dropdown select field. Fortunately, I have 13 in the theme I primarily work on, so it is a non-issue for me.

Block Template Part Hooks

Theme and plugin developers now have additional action hooks around the block template part system. These should be handy for debugging or other complex use cases.

  • render_block_core_template_part_post fires when a part is found from the database.
  • render_block_core_template_part_file fires when a part comes from a theme file.
  • render_block_core_template_part_none fires when no part is located.

by Justin Tadlock at December 23, 2021 01:19 AM under gutenberg

December 22, 2021

WPTavern: WordPress Contributors Discuss the Possibility of 4 Major Releases in 2022

Last week, WordPress Executive Director Josepha Haden Chomphosy opened a discussion on how many releases the project will aim for in 2022.

“Given that we have a release in January already, I wonder if we might be able to use 2022 to attempt four releases,” Haden Chomphosy said. She proposed three different release schedules:

  • Quarterly releases: January, April, July, October
  • Trimester-ly releases: January, May, September
  • Known release and then evenly spaced targets?: January, May, August, November

When she brought it up in the #core Slack channel, a few contributors said they would like to see the project move towards more frequent releases. They were optimistic that it can be done, since a January release is already on the schedule.

Responses to the post on make.wordpress.org were markedly different. A few commented that they would be comfortable with a quarterly releases as long as they avoid major holidays. Several participants in the conversation have urged WordPress to slow down to two or three releases. Others suggested WordPress simply wait to release new features until they are ready, with no schedule. This particular suggestion makes it difficult for various stakeholders, like hosting companies, agencies, and WordPress product businesses, to plan effectively.

In 2021, WordPress released version 5.7 in March and 5.8 in July. A third major release planned for December was postponed due to critical blockers and decreased volunteer availability. A jump to four releases next year seems overly ambitious without a change in processes.

“Is it realistic to plan four releases for 2022 right after three releases per year plan was not fulfilled?” Oleg Kharchenko asked in the comments. “I don’t get what’s the benefit of having more releases just for the sake of number. It looks good in business reports but it has no real value for WordPress users as frequent releases lead to half-baked features which are hard to use.

“Also plugin and theme authors will have to put more time into testing instead of their product development. Finally, there are many tickets on Trac with ‘early’ keyword which are punted for years just because everybody is too busy to find time to include these tickets in the upcoming release, making the release schedule tighter would worsen this situation even more.”

Jessica Lyschik, a developer and an active member of the German WordPress community, said she would prefer two releases for the future.

“As several people already mentioned, planning more releases did not work out in the past, so why should it work now?” Lyschik asked. “5.9 got postponed to have refined features included so it can be actually used. The complexity of the new features is huge and trying to split that up in smaller releases is not something I see to work in the future.”

The roadmap for 2021 originally planned for four major releases but was scaled back to three in February. At that time Haden Chomphosy cited a lack of automation and the necessary personnel to execute the plan without risking contributor burnout and update fatigue.

WordPress core committer John Blackbourn commented on the discussion, urging Haden Chomphosy to elaborate on why she is proposing the potential of more frequent releases. He also requested she summarize the original list of challenges and needed changes and the progress that has been made towards improving them.

In a post titled “Why I Voted to Delay WordPress 5.9,” Anne McCarthy explained a few of the factors and blockers that caused the release to be postponed to January 2022.

“What I’d like to understand better is what are we going to do to make sure this doesn’t happen again?” WordPress 5.9 release lead Matt Mullenweg commented. “There could always be more polish, more bugs fixed, and I would challenge you to pick a year in the past decade that didn’t have its share of human issues. I’d like us to really understand and agree what went wrong, particularly in the first months of 5.9, and what we’re starting now to make sure 6.0 is effortlessly on time.”

McCarthy responded, citing the following reasons:

  • lack of contingency plans around the interrelated features
  • lack of clarity around scope for various individual features (particularly the browsing feature)
  • lack of a comprehensive check in early enough ahead of feature freeze
  • a need for more decision makers who have a high level view of where the work is headed

“Personally, I’d love to see the Go/No Go meeting overhauled to be less aspirational and more concrete as to where things stand as I think that’ll set the tone early enough in the release cycle to avoid some of these problems again,” McCarthy said.

A few of these challenges with 5.9 correspond to the items Haden Chomphosy identified in February as needing to change in order to make WordPress releases easier and more frequent: better testing, more seasoned core developers available with time focused on core, better handoff in design/dev iterations, and shifts in collective philosophies towards continuous development.

In the absence of a comprehensive 5.9 retrospective, it may be difficult to plan the next year’s release schedule based on the reality of what contributors experienced most recently. Moving to four major releases will be a tough sell after closing out a year where WordPress could not post three major releases. It will require significant changes to how the work is scoped and managed as it is in process. The topic will be up for discussion again during today’s weekly core dev chat at 20:00 UTC.

by Sarah Gooding at December 22, 2021 07:50 PM under WordPress

HeroPress: Living Well and Enabling Success For Others Through WordPress

Pull Quote: Success is a life well lived.

From a very young age, I can remember dreaming about a business I would one day own. It would be a restaurant named “The Comfy Chair.” Serving mainly breakfast and light lunch, I pictured a funky space with a mix of unique, comfortable chairs. Patrons could choose the chair that fit their mood of the day.

I’m sorry to report that my childhood dream never came true.

Instead, I now lead a 15-person remote team that develops open source software on WordPress, our primary product is the membership plugin Paid Memberships Pro.

The road that led me to WordPress didn’t begin with a passion for the web, or democratizing publishing, or coding, or anything technology-related.

I began my career in WordPress through my passion for entrepreneurship. A passion to control my earnings, “be my own boss,” and maybe more specifically, work when I want, on what I want, and for the price I choose.

That is the most kickass thing about WordPress—people can enter our community and leverage WordPress for free, from anywhere, anytime, for any reason.

From Craigslist to Plugins

Throughout college, I freelanced doing simple brochure websites, graphic design, and a lot of print work. I used Craigslist and word of mouth to get projects, taking nearly any job that a) paid and b) I could handle on my own or with some help from my “high school sweetheart, husband, co-founder, and best friend” Jason.

After graduation, my parents were cautiously enthusiastic about my decision to start a web design business. I knew I had many months of runway and felt it was a no brainer. Starting a business is a risk. The bigger risk was missing the opportunity to create my own business in the “carefree” days of youth.

Business ownership teaches you a ton—I was learning not just about emerging web technologies like WordPress. I had to learn every aspect of small business: sales and marketing, project scoping, invoicing and accounts receivable, taxes, healthcare…everything.

In Fall 2006, Jason left his job at Accenture and joined me full time. I had my projects and clients, Jason had his. He led the projects that were more development-focused, I led the more design-focused projects.

By 2007, we started doing WordPress sites almost exclusively. WordPress was about four years old at the time. The community was starting to take shape. Meetups and WordCamps were becoming a thing, but the events were very different back then.

I didn’t identify with the early WordPress community. Events were primarily attended by developers and coders, who were primarily male. So I stayed on the periphery of the community.

Jason and I continued operating Stranger Studios as a two-person team. In an agency, there are two main ways to grow revenue: charge more per hour or bill more hours (grow the team). I couldn’t picture myself managing other people. Life and business was good just the way it was. So we regularly raised rates, focused on high value clients, and tried our best not to keep too many clients on maintenance plans.

The WordPress “CMS” helped us increase the number of clients we could serve by giving them more independence in managing their own sites.

Then, life decided to push me into my next chapter with an event that happened when we had our first child, Isaac.

A Building Block For Change

Isaac had a rough start to life 13 years ago and needed surgery a day after his birth. We are endlessly grateful to St. Christopher’s Hospital and The Philadelphia Ronald McDonald House for supporting us through his first two weeks.

And while going through those heartbreaking, chaotic, and hopeful weeks, we still had to work. I remember waiting in our hotel room for Jason to wrap up an urgent call with a client so we could go see our days-old baby. It’s a ridiculous scene to reflect on.

I thought I was living life my way. In reality, I was financially tying myself to a handful of long-term clients. And what’s worse: there was no one to hand things off to when my personal life needed attention.

Consulting work felt like being on call 24/7.

That event changed my life in more ways than I could ever put into words. For the intention of this essay, let’s just say that our business needed to change dramatically, quickly.

When I talk with other entrepreneurs and business owners, we often break down the differences between a services company and a product company. You may have heard a WordPress talk on this very topic: the move from “consulting to products”.

It’s an appealing path for many WordPressers. And now that I’m on the other side of the transition, I can’t deny it is an awesome space to be in—even with the product space going through some major shifts with all the acquisition activity. But that’s a topic for another conversation entirely…

The biggest turning point in my WordPress journey was the decision to create a product. By moving to a product company, I could make more money without working 24 hours a day or (immediately) having to hire people and grow as an agency.

But what kind of product should we build? What untapped market could we serve? What was missing in the WordPress ecosystem?

We found the answer by looking at our history of proposals and projects.

A growing number of our freelance projects had a “membership-type” component. People wanted to protect access to features of their site (content, tools, applications). People wanted to get paid through their WordPress site. More specifically, they wanted to “make money while they sleep” and get paid on a recurring basis. Sell once, get paid over and over again.

Jason and I recognized this trend and the lack of a leading WordPress plugin for memberships. We focused only on freelance projects for “membership-type” sites built on WordPress. These projects helped us bootstrap the development of what is now Paid Memberships Pro.

Open Source Products Are Better Products

I believe in open source. I believe open source products are better products.

We release all of our products with an open source license, just like WordPress. We make our code publicly available on GitHub in a format that removes barriers to collaboration for internal and external contributors. And we make a very good living for ourselves and our team by building a business on top of our open source products.

The decision to be open source has made an overwhelmingly positive impact on the growth of our business. But there’s another major reason why we’ve made it in the WordPress product space.

Paid Memberships Pro is a success in large part because we release the full version for free in the WordPress.org Plugins repository.

Putting my beliefs in OSS aside, the repo makes your plugin available for every WordPress site. That’s 43.1% of websites that exist today. The repo is an amazing resource for every site using WordPress and also for every business building a WordPress product. Not only does the repo facilitate installs and updates, it also builds in a layer of security for WordPress users.

I am deeply grateful for the WordPress community members (the Plugins team) that maintains, reviews, and supports the repository. Without you, I wouldn’t be sitting here today writing an essay about my WordPress journey.

Building a Team That’s Diverse In Many Ways

I’ve always been a woman business owner in a male-dominated field. But I can’t say that my being a woman was something that limited or, on the flip side, catapulted my career forward.

I say this because there are many people in the WordPress community that speak intelligently and openly about important topics like diversity, inclusion, and the serious problem of underrepresentation. I have not devoted enough time to educate myself on their efforts.

But as a person who has interviewed and hired people for a variety of roles, I do have some perspective on the value diversity has brought to our team.

Nearly half of our team are women. And we are diverse in other ways including age, geography, physical ability, and experience.

I value diversity as I value any other positive trait that an employee brings to the table.

When I am interviewing another woman, I recognize that they bring a woman’s perspective to the team, which is valuable. When I am interviewing someone with very little experience, I recognize that I can teach anyone that’s willing to learn and grow, which is valuable. When I am interviewing someone that lives a 20-hour plane ride away, I know that we work remotely and don’t have to overlap for our entire work day.

The diversity in our team has changed my worldview. I have learned endless things about other cultures, such as the troubling issues that a Nigerian mother has faced to find a safe and enriching school for her daughter. I’ve learned about the lasting effects of apartheid in South Africa, about the progess has been made to unify the country and where there is work to be done.

As a parent of “tweens”, I’ve learned valuable lessons from people with adult children. And on the flip side, I’ve shared my stories with people at an earlier stage in the parenting journey.

WordPress is an open, free, accessible tool used by the whole world. Getting involved in WordPress doesn’t require a special form of education, grasp of the English language, or boatloads of money.

I wouldn’t have been able to build a diverse team if the WordPress community, itself, wasn’t diverse.

Live Your Way

Live your life your way. Do more of the things you want. Do less of the things you don’t want.

I am extremely grateful that I am safe, comfortable, and able to live my life, my way. I know that many people are in a place where this type of thinking is not possible.

But even people with everything can have a feeling that something is missing. For me, that feeling is influenced by what other people want for me, when I feel pressure to live out someone else’s dream.

Jason tells me (and others) that my skills are wasted on this product. He boosts me up with encouragement and praise. He says that I am capable of bigger, grander things.

The message I take from this is that I can do anything. So I will do what I want to do. I will do more of the things I like to do, and less of the things I don’t.

In work, that looks like filling senior roles on our team to do things I am currently responsible for. Freeing up my time to nurture the next big product. Or, freeing up my time to spend in ways that my kids need me. Or, I could get another dog.

What I want to leave you with here is that you don’t have to feel pressured to go after someone else’s dream. I’ve watched companies like mine get acquired. Their founders take extended vacations and are living semi-retired lives. I think “is this what I’m supposed to do next?”

Then I join my team on a call and I think “I never want to stop working with these people. This is my family.”

I’ve had opportunities to swing for the fences. To push harder. To get bigger, faster. To be wildly successful.

This is a monetary measure of success. This is feeling successful because other people think you are.

To me, success isn’t measured by dollars or ego. Success is a life well lived. I want to energetically pursue living well. I want to build products that help people find this success. I want to grow a team that has the same freedoms in life that I humbly enjoy.

I want to keep pursuing success with WordPress.

by Kim Coleman at December 22, 2021 01:00 PM

WPTavern: Ask the Bartender: Will It Become Easier To Create Block Patterns?

Do you know if WordPress FSE is working to make it easier to create block patterns? Templates and Parts need to just click a button to download them. But patterns are very manual, and you need to register all of them programmatically.

Thiago

You are not the first person to ask this question, and it is something that I have been mulling over for a while. With theme development quickly encroaching a point where it could almost exclusively be done via the site editor, it makes sense that block patterns follow along with their template counterparts.

The feature has not been given any sort of official green light. I am not aware of a specific ticket for it, but it seems like it will be a part of the natural evolution of themes and patterns. I encourage opening a new ticket via the Gutenberg GitHub directory.

Two core features need to precede it:

  • A standard folder for storing patterns in themes.
  • A way to save patterns in the database.

Fortunately, there are tickets for both of these. Last month, Gutenberg lead Matías Ventura opened a new issue for standardizing how themes are organized. WordPress 5.9 will see the introduction of /templates and /parts folders for templates and template parts, respectively. These will be the officially-supported locations in block themes.

That same ticket proposes future enhancements of a /styles folder for global style variations and /patterns for block patterns. Having a standard location for these things is vital because the exporter in the site editor needs to know where to put them in the exported ZIP file.

A side benefit of this feature is that theme authors would no longer be required to register their custom patterns via PHP. They could merely drop the files into their /patterns folders and move on. The format of this is nowhere near official at this point. There is an unmerged pull request that implements this by searching file headers.

The second piece of solving this issue is figuring out how to allow users to save patterns via the UI similarly to reusable blocks. This is a more complex issue. There are existing plugins that already do this, such as my own Block Pattern Builder, which sorely needs updating, and BlockMeister, a more robust solution. Reusable Blocks Extended even allows users to convert reusable blocks into patterns. So, there are already folks who are trying to solve the problem.

There are still questions about the implementation before it can be officially supported. Are saved patterns a subtype of wp_block, which is currently the post type for reusable blocks? Are they something separate? Then, the project must also decide whether it wants to allow custom pattern categories via a new taxonomy.

There are also other considerations before adding another feature into core, such as adding a design library for components in the global space.

We are not quite to the point where you want, but we are on the path. The /patterns folder alone would remove the code-writing requirement. If it lands in WordPress, you could copy and paste block HTML over. It is not the same as exporting them alongside templates, but I hope the platform arrives at that destination one day.

by Justin Tadlock at December 22, 2021 01:36 AM under Ask the Bartender

December 21, 2021

WordPress.org blog: WordPress 5.9 Beta 4

WordPress 5.9 Beta 4 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 4 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, 2, or 3 to Beta 4 on a case-insensitive filesystem, please use the following command sequence:

Command One:

wp core update --version=5.9-beta4

Command Two:

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

The current target for the final release of 5.9 is January 25, 2022, which is only five weeks away. 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 3, 20 bugs have been fixed. Here are a few of the changes you will find in Beta 4:

  • Bundled Theme: Fixed duplicate CSS rules in Twenty Twenty-One theme (#53605).
  • Customizer: It’s possible to switch to a block theme from within Customizer (#54549).
  • Themes: Provide guidance to users seeking to preview block themes on WordPress versions below 5.9 (#54575).
  • REST API: The get_theme_item method should respect fields param (#54595).
  • Editor: Block Patterns: “Featured” category & patterns missing from inserter (#54623).
  • Login and registration: Add a filter to allow to disable the Login screen language dropdown – (#54675).

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. 

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

Got questions? Here are some answers

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

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

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

by Jonathan Bossenger at December 21, 2021 09:17 PM under beta

WPTavern: WordPress 5.9 to Introduce Language Switcher on Login Screen

More than half of all WordPress sites (50.5%) are using translations for non-English speaking locales. It’s only natural that these users would want the ability to register, log in, and reset their passwords in their own languages. A new language switcher on the login screen has finally made its way into core, four years after the ticket was opened.

WordPress 5.9 will introduce a new dropdown on the login screen that will display all the languages that are currently installed. (New languages can be added under the Settings > General screen in the admin.)

In a dev note for the new features, WordPress Core Committer Jb Audras demonstrated how developers can filter the default arguments for the languages dropdown. This might be useful for sites that have dozens of languages installed where administrators only wish to display a handful in the dropdown.

WordPress 5.9 beta 3 was released last week. In addition to the new language switcher, the latest beta also includes the following:

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

RC1 is expected January 4, 2022, which will bring a code freeze for both Gutenberg and core and a hard string freeze. Contributors are also aiming to have the field guide with dev notes published at this time.

If you have time to contribute during the upcoming holiday weeks, the 5.9 release team welcomes more testing for bugs. Anne McCarthy has published a detailed guide to testing the full-site editing features that are anticipated in 5.9. Testers should check against the list of known issues before reporting bugs on Trac or in the Alpha/Beta forums.

by Sarah Gooding at December 21, 2021 04:23 AM under WordPress

WPTavern: The WordPress Photo Directory Is the Open-Source Image Project We Have Long Needed

In last week’s annual State of the Word address, WordPress project lead Matt Mullenweg announced the WordPress.org photo directory. Officially, it has not yet “fully launched.” However, it is live on the site, and anyone with an account can submit their photos.

Thus far, the directory has 103 submissions and are under the CC0 license. Unfortunately, there is only a single photo of a house cat. Perhaps I will need to contribute to the commons that this project has made possible.

This is a separate project from Openverse, a search engine for finding open-source media, launched before the State of the Word event. Eventually, images from WordPress Photos should be discoverable via the Openverse search.

Earlier this year, I was already envisioning what Openverse could be. However, what I really wanted was a WordPress photo directory. Actually, I wanted a WordPress media directory, but starting with images is easier:

Openverse must become more than a media search engine. It needs to be a project where the Average Joe can upload a nice nature picture he took over the weekend barbecue. A place where Average Jane can share a video clip of the ocean waves hitting the shoreline from her beach trip. And a place where professionals can pay it forward to the world.

When Jeff Chandler of WP Mainline shared his first photo, I quickly turned it into a block pattern that wrapped the image in a wooden frame (pattern and image links available via Gist). When the WordPress pattern directory opens its submission process, I would love to submit it or some variation.

Wooden frame block pattern around Chandler’s image.

My customization was not anything special. I wanted to showcase how vital CC0 photos are to those building WordPress extensions like patterns and themes. Having a reliable image resource is invaluable to our creator community. It also gives non-developers another way to contribute to the project.

I also like seeing the faces of people I know listed in the directory. It very much feels like a photo directory made by the people of WordPress. One of my favorites is this one from Topher DeRosia (he has already submitted five):

Single image posts provide additional photo information, categories, and tags. Each photo also has multiple download sizes.

The front page and search could still use a little work. Being able to at least search for images based on orientation (e.g., landscape vs. portrait) would be helpful. A nav menu with all of the categories would be handy too.

The Space Needed Disruption

The stock imagery space needed to be turned upside down. More and more, creators from the WordPress community have stepped away from some of the sites they once loved.

Unsplash. Pexels. Pixabay. They have all had an opportunity to become the most significant open-source photo website in the world. They are places for snagging a quick photograph for free. And, for the most part, they have allowed people to give back with their art.

However, these stock photo sites that previously distributed images in the public domain began adding restrictive licensing terms. It started with Unsplash in 2017. Pexels soon followed, and Pixabay was in lock-step with the others by 2019.

Most of these restrictions disallow users to build similar “collection sites” with those same images, essentially creating a competing service. However, they all have other restrictive terms on selling photos, especially unaltered ones. Note: Pexels still allows its contributors to choose between the Pexels License and CC0 (public domain).

Many photo-sharing sites built their empires on top open source, only to turn their backs on it down the road. The open-source spirit embraces competing websites. The art itself is meant to be shared. That is kind of the point. To be fair, the aforementioned were not the only such sites. They were just the most prevalent in the WordPress ecosystem.

WordPress theme authors were often champions of those sites in years prior. However, they saw service after service disappear before their eyes as they were banned from use on WordPress.org. Themers could not distribute the images because the users who downloaded them would not have the same freedoms as promised by the GPL. It was a loss for open-source.

Now that WordPress has a pattern directory, the issue has become more evident. In the coming months and years, creators will need high-quality photos to showcase their patterns.

The easiest path was to leverage the millions of people who use WordPress and build our own thing. WordPress Photos could very well become the de facto standard of open photos on the web, and that is something we should all welcome with open arms.

The project is necessary. WordPress.org has the resources to make something remarkable: a photo-sharing site that is 100% open and will never change.

by Justin Tadlock at December 21, 2021 01:43 AM under Opinion

December 20, 2021

WordPress.org blog: WP Briefing: Episode 22: A Carol of Thanks

In this last episode of 2021, Josepha Haden Chomphosy takes the time to appreciate those who make the WordPress project a success and offers a carol of thanks.

Have a question you’d like answered? You can submit them to [email protected], either written or as a voice recording.

Credits

References

Have yourself A Merry Little Christmas

Transcript

Josepha Haden Chomphosy  00:10

Hello everyone, and welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project. Some insight into the community that supports it and get a small list of big things coming up in the next two weeks. I’m your host Josepha Haden Chomphosy. Here we go!

Josepha Haden Chomphosy  00:39

So, ages and ages ago, when I first started this podcast, someone basically requested that Matt and I do a duet for the last podcast of the year. A Christmas carol duet; him on the saxophone and me on voice. I obviously did not get that coordinated I don’t even know why I said obviously. I’ll tell you right now I did not get that coordinated. I was a very busy lady this year. So I don’t have a Matt on saxophone. Still, I did think that maybe it might be nice just for me to sing a teensy little Christmas carol for you all just because it seems especially poignant the words this year, especially after the 2020, 2021 COVID, all the things and trying to get back in person. So I’m going to sing you all one little verse from Have Yourself a Merry Little Christmas.

Josepha Haden Chomphosy 01:35 Singing  

Have yourself a merry little Christmas

Let your heart be light

From now on our troubles

Will be out of sight

Have yourself a merry little Christmas

Make the Yuletide gay

From now on our troubles

Will be miles away

Here we are as in olden days

Happy golden days of yore

Faithful friends who are dear to us

Gather near to us, once more

Through the years we all will be together

If the fates allow

Hang a shining star upon the highest bough

And have yourself a merry little Christmas now

Here we are as in olden days

Happy golden days of yore

Faithful friends who are dear to us

Gather near to us, once more

Through the years we all will be together

If the fates allow

Hang a shining star upon the highest bough

And have yourself a merry little Christmas now

Josepha Haden Chomphosy  03:34

Alright, my friends, that was from my heart to yours if you happened to listen. If you skipped a few seconds to get through it, which I would totally understand, that is also fine. But I did want to just kind of wrap up the year to let you all know that I am so incredibly grateful for all of the people who show up for the WordPress project to make it a success. I have made so many friends and wonderful acquaintances throughout my time here with the WordPress project. And especially in my three years as the project’s Executive Director. You all have put a lot of trust in me and a lot of faith. And I know that we have gotten so much done together in the last few years. And I am equally sure that we’re going to get so much done in the years to come. And so thank you all so much for your continued work with WordPress and the way that you just bring your best at all times. 

Josepha Haden Chomphosy  04:32

One other little thanks I want to give. Over the course of this year, I’ve had an excellent team that works with me on this podcast. I have editing and design folks and people who’ve joined me here and there, folks who helped me with my production. So big thank you to Dustin, Bea, I realize your name is Beatriz in the actual credits, but I call you Bea, and so thank you. Also, a huge thank you to Chloé, who does all of our production and wrangling every couple of weeks. A big round of applause and kudos to that tiny but tough team that helps me get this all done.

Josepha Haden Chomphosy  05:10

That’s to go on top of the general thanks to the WordPress project. And if you all are celebrators, I hope you have a wonderful holiday season. If you are not celebrators, I hope that you have a wonderful end to your year and that everything you wanted to get done, you did get done, and that you can start 2022 with a fresh slate. Again, this is the WP Briefing. Thank you so much for listening. I’m your host Josepha Haden Chomphosy, and I’ll see you again in 2022.

by Chloe Bringmann at December 20, 2021 07:22 PM under wp-briefing

December 18, 2021

Gutenberg Times: Charts & Memes Blocks, State of the Word, and more Weekend Edition #197

Howdy,

Wow, this is already the fourth year-end message, I send out with this newsletter. There isn’t much, I have been doing so consistently then this weekly newsletter. It’s been such an inspiring journey, thanks to you and the WordPress contributors, extenders and users. Your creations, questions, comments have been wonderful, especially when in-person contact have been sparse and zoom-fatigue set in.

For Gutenberg, the block editor the best is yet to come.

In his State of the Word presentation, Matt Mullenweg mentioned for next year Full-Site Editing in WordPress 5.9, which he called the MVP, minimal viable product, Openverse and WordPress Photos, maybe four WordPress releases and in-person meetings. Work on Phase 3, Collaborative editing, won’t come until 2023. This was not all and below you’ll find an array of Recap posts and media for your perusal.

This is my last edition of the year 2021. I wish you a great time with family and friends and a Happy New Year. I am excited to connect with you again around January 9th with the next weekend edition.

Yours, 💕
Birgit

PS: 2129 users voted at the WPAwards produced by Davinder Si ngh Kainth. It’s all in good spirit and a fun activity. In the category of Page builders, Gutenberg landed on second place behind Elementor and before Beaver Builder. 🙂 Thank you, for those who voted for the Gutenberg Times and the Gutenberg Changelog. Seems we need to do some more community outreach and lobbying next time around. 🤔

PPS: To bridge the gap until the next edition, I sprinkled some Gutenberg highlights of the year sprinkles among the links below: starting with the recordings of Gutenberg talks from WordCamp US 2021 on WordPress.TV.


Table of Contents

 “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

State of the Word and Q and A

My longtime Webdev friend, Deborah Edwards-Onoro shared her thoughts in Takeaways from State of the Word 2021.

The Posts Status team collected voices from the community after the State of the Word & Q & Two ways.

Courtney Robertson, WordPress Training team, sponsored by GoDaddy, also wrote a Recap of both Mullenweg’s presentation and the Q & A.


The Feedback for the 11th Call for testing from the FSE program is in, and Anne McCarthy published the Site Editing Safari Summary.

“As folks dug in, there were numerous enhancements that quickly came to mind as awesome nice to haves. These desired enhancements not only underscores the potential of various full site editing pieces when put together, but also highlights the frustration around the current limitations” McCarthy wrote. She also created a list of GitHub Issue for those feature requests. Check them out and comment if you are interested in those features as well.


Building Custom Blocks and developing for Gutenberg

Before you start thinking about building a custom block, read Tammie Lister‘s Block patterns are better than blocks, published on the Extendify‘s blog.

The Team at Learn.WordPress.org has two workshops for developers and more are coming.


Ari Stathopoulos posted a WordPress 5.9 DevNote on Using multiple stylesheets per block

“Blocks will now be able to register multiple stylesheets, and load styles from other blocks when needed. Themes will be able to add styles on a per-block basis instead of loading monolithic stylesheets that are force-loaded anywhere. This has a greater impact on block themes where stylesheets loading is optimized based on the page & layout contents, but can also be used by classic themes.”, Stathopoulos wrote.

He continued: “This change can benefit both block developers and theme developers, further reducing the total page-weight by only loading styles for blocks that exist on a page.”


Justin Tadlock reviewed a new plugin providing chart blocks in this post: Hello Charts Launches a Native Chart-Building Experience for the Block Editor. In the article, he also lists other block plugins that allow you to create charts. There are actually four:

Hello Charts is not available in the WordPress repository, only from their website. It’s the first block-based product site, I noticed, that sells single block features.


In his last stream before the holidays, Ryan Welcher took his viewer through extending the meme block he created last week, to use images from the Media library. You can watch it on YouTube: Expanding the Meme Generator plugin.
If you prefer not to watch the programming part and just look at the code, you can see all code from the Twitch stream on GitHub. Be aware they are educational and not meant to be used in production.

Need a plugin .zip from Gutenberg’s main (trunk) branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.

GitHub all releases

Block Themes for Theme developers

Maggie Cabrera published the Gutenberg + Themes Digest for this week. She highlights PRs and discussions on four topics:

  • Typography supports for group and row blocks
  • Nameless font sizes
  • Approach to global padding
  • Default font sizes renamed
  • Template parts in child themes

I suffered from serious flashbacks, when I noticed that Riad Benguella recreated the Kubrick Theme as a block theme. Matias Ventura tweeted a short video on how to change the header color gradient with the site editor. You can study the block theme on GitHub. It might even show up in the WordPress repository.

Justin Tadlock also has a few more thoughts and screenshots Yes, a Block-Based Version of the Kubrick WordPress Theme Exists

Post’s Featured Image: “Building blocks, color, abstract, international, global, corporate, colorful” by Wonderlane is licensed under CC0 1.0


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.

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

WPTavern: Disable Over a Dozen WordPress Features With the No Nonsense Plugin

One of the best things about WordPress is the hundreds of ways of turning things off. There are likely dozens of plugins for disabling various items, each with its own unique set of options. No Nonsense is no different. It is a plugin that allows users to control whether they want to use over a dozen features.

The plugin was developed by Room 34, a Minneapolis-based web development and creative consulting studio. No Nonsense is the team’s 11th free plugin available through the WordPress.org plugin directory.

The team’s plugin caught my eye because it has options for features that I routinely disable on WordPress site builds, such as emoji JavaScript, individual dashboard widgets, and the toolbar. Today’s update (version 1.2) even added an option to permanently remove the Hello Dolly plugin.

Before anyone asks — someone always asks —, the plugin does not disable the block editor. However, it does have an option for turning off the block-based widgets editor.

Room 34 released the plugin on Tuesday, so it has fewer than 10 active installs at the moment. It also does not have any reviews. I suppose this post will suffice as the first. Based on my experience and a peek at its code, the plugin looks solid.

Plugin settings screen.

I tested each feature and did not find any issues, so it gets a 5/5 for doing what it says on the tin. I would love to see a few more options. One example that immediately comes to mind is the the “Posts” screen. Since users can remove the “Comments” section in the admin, it makes sense to have a similar setting for posts. Both are related to blogging, and not all WordPress websites need them.

No Nonsense includes one of my favorite admin-access limitations. It can redirect logged-in users to the homepage when accessing anything other than their user profile in the WordPress admin.

Its toolbar options are all things I have lying around in my code toolbox. The plugin has settings for hiding it for users without editing access, removing the WordPress logo, and ditching the “Howdy” text.

The plugin includes options for many commonly-disabled features, but a new one that I had not thought about was the core update email. When managing sites for several family and friends, those “your site has updated to WordPress x.x.x” emails can become irritating. The plugin allows you to disable those except in cases of an error.

If someone has not already done so, I would love to see a deactivation plugin to end all deactivation plugins. It would feature a complete list of things that a site owner can turn off, disable, deactivate, remove, or whatever you want from a WordPress website.

No Nonsense looks like a good starting place, but there are always other things that I might remove from an install. I almost always give the ax to the theme and plugin editors. As well as the plugin works, there’s always just a little something more I need to get rid of, depending on the site in question. So, I am still looking for that behemoth plugin that gives me that one-click access to disable anything. For now, I can see myself deploying this on a few sites.

by Justin Tadlock at December 18, 2021 12:20 AM under Reviews

December 17, 2021

WPTavern: Free Software Foundation Adds a Code of Ethics for Board Members

The Free Software Foundation (FSF) announced it is implementing a new Board Member Agreement and  Code of Ethics that is meant to guide members in their responsibilities, decision-making, and activities. The documents, which FSF says were “designed to help make FSF governance more transparent, accountable, ethical, and responsible,” were created as part of a six-month long consultant-led review.

In March, FSF founder and GPL author, Richard Stallman, announced that he was returning to the board, after resigning as director of the board and president of the FSF in 2019. His resignation followed a series of controversial remarks on rape, assault, and child sex trafficking, along with two decades of behaviors and statements that many have found to be disturbing and offensive. He was subsequently ousted by GNU project maintainers from his position as head of the project.

Stallman’s controversial return was supported by the majority of FSF’s board, with the exception of board member Kat Walsh who resigned after voting against his reinstatement. The organization’s executive director, deputy director, and chief technology officer also resigned in protest. 

At that time, the FSF’s board published a statement saying they “take full responsibility for how badly we handled the news of his election to a board seat. We had planned a flow of information that was not executed in a timely manner or delivered in the proper sequence.” His reinstatement took FSF’s staff by surprise, as they were not informed or consulted.

Mozilla, the Open Source Initiative, Red Hat, the Electronic Frontier Foundation, and other prominent tech organizations also opposed the decision in published statements and removed their support for FSF and critical funding.

The WordPress Foundation, which previously listed FSF among the project’s inspirations, quietly removed the link from the website following the controversy. WordPress’ executive director Josepha Haden Chomphosy published a statement, saying she did not support Stallman’s return as a board member, and confirmed to the Tavern that this is also the WordPress project’s official stance.

In what appears to be an attempt to claw its way back to a semblance of accountability, FSF’s newly approved Code of Ethics is targeted at preempting future incidents of board members acting on behalf of the organization without permission. A few relevant ethics in the document include the following:

  • Members of the board of directors will not undertake an activity that substantially hurts the FSF. When acting as board members, they will work toward the success of the FSF.
  • Board members shall all avoid placing–and the appearance of placing–one’s own self interest or any third-party interest, including the interests of associate members, above that of the organization as a whole.
  • Board members shall not speak on behalf of the FSF unless given explicit permission. Directors must not represent that their authority as board members extends any further than it actually extends. The board speaks as a whole, not as individuals.

New governance is a positive step towards transparency and accountability, but after all the damage done during the botched rollout of Stallman’s reinstatement, it’s not likely that opposing organizations will settle for anything less than his removal from the board.

by Sarah Gooding at December 17, 2021 09:45 PM under Free Software Foundation

Post Status: Post Status Excerpt (No. 37) — WordPress Community In Africa

“You shouldn't be the one to always take, you want to be the one to always give.” —Mary Job

In this episode of Post Status Excerpt, David chats with special guest Mary Job. Mary is a remote, “nomad” worker in Africa who travels from city to city. She is an engineer with Paid Memberships Pro but also spends a large amount of time growing and stimulating the African WordPress community. Mary has helped start WP Africa, a site devoted to the community of WordPress users on the continent. She talks about challenges they face, compares the WordPress presence with Google in Africa, and looks forward to the day when there can be a WordCamp Africa.

Also: Mary shares how she got involved in WordPress, and how appreciative she is of the giving nature of the WordPress community. David will have to figure out how to get Mary's invite to Matt.

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: 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!

by David Bisset at December 17, 2021 01:00 PM under The Excerpt

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 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

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:

January 02, 2022 03:45 AM
All times are UTC.