WordPress.org

WordPress Planet

December 14, 2018

WPTavern: WordPress 5.0.2 to Bring Major Performance Improvements, Scheduled for December 19

Processed with VSCOcam with c1 preset

WordPress 5.0.1 was released yesterday as a security release with fixes for seven vulnerabilities that were privately disclosed. It includes a few breaks in backwards compatibility that plugin developers will want to review.

WordPress 5.0.2 will be the first planned followup release to 5.0 and is now scheduled to be released December 19, 2018. Gary Pendergast posted a summary of this week’s dev chat that includes the schedule and scope for the upcoming release. It will include Gutenberg 4.7, Twenty Nineteen bug fixes, and a few PHP 7.3 compatibility fixes.

Slow performance as compared to the classic editor has been a commonly-reported issue with Gutenberg. The project has a label for it on GitHub with 26 open issues. 140 performance-related issues have already been closed so the team is making progress on speeding it up. 5.0.2 will bring major performance improvements to the editor, particularly for content that includes hundreds of blocks.

“The cumulated performance gains are around 330% faster for a post with 200 blocks,” Matias Ventura said in an update on the editor. “This might be even bigger for certain setups and plugin configurations — seeing the same test post be 540% faster with Yoast, for example.”

These changes are already in version 4.7 of the Gutenberg plugin, which users can run alongside WordPress 5.0.1 to test the latest.

RC 1 for 5.0.2 is planned for today and RC 2 (if necessary) is targeted for December 17. The official release is scheduled for December 19.

Gary Pendergast also outlined the scope and schedule for WordPress 5.1, which will be led by Matt Mullenweg. Pendergast proposed a relatively short release cycle with an official release February 21, since there are already more than 200 tickets fixed for 5.1. Focuses for the release include the REST API (particularly authentication solutions), core JS, and core themes. Beta 1 is planned for January 10, with RC 1 following February 7.

by Sarah Gooding at December 14, 2018 04:52 PM under performance

WPTavern: WPWeekly Episode 341 – Recap of WordCamp US 2018

In this episode, John James Jacoby and I recap WordCamp US 2018. We discuss what’s new in WordPress 5.0.1 and when users can expect to see 5.0.2.

We also chat about the new path that WordPress is on and where it may lead. John shares his perspective on what the atmosphere was like at the event and compares it to last year.

Near the end of the show, we explain why the Question and Answer process at the end of the State of the Word will likely undergo changes.

Stories Discussed:

WordPress 5.0.1 Security Release

WPWeekly Meta:

Next Episode: Wednesday, December 19th 3:00 P.M. Eastern

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #341:

by Jeff Chandler at December 14, 2018 01:59 AM under WordPress 5.0

WPTavern: WordCamp US 2019 to be Held November 1-3 in St. Louis

photo credit: Wikimedia Commons

Dates for WordCamp US 2019 were announced today, less than a week after wrapping up a successful camp in Nashville. Unlike all previous years held in December, next year’s event will take place November 1-3 in St. Louis, Missouri.

For the most part, community reactions to the new dates were positive. Early November dates place the event well ahead of the end of the year holidays that attendees had previously bemoaned.

“I love this date set better than the previous one. It’s so much easier to attend/speak pre-Thanksgiving,” WordPress developer Mitch Cantor said.

There is always a conflict for some demographic of attendees. This year the hardest hit are parents of small children who will likely miss taking their kids trick-or-treating due to traveling on or before Halloween in order to make it to the event. WordCamp US is a family-friendly event but bringing children to a WordCamp can be extraordinarily challenging, even when the event includes childcare. (This particular event doesn’t.) For a few attendees, missing Halloween with their children is a deal-breaker.

One possible solution for the parents who feel they have to miss WordCamp US because of their kids, might be for the organizers to schedule the contributor day as the first day of the camp. That might enable people to fly in on an early morning flight and still get to experience part of the contributor day and all of the main event.

In a community this large, with many other holidays and WordCamps already on the calendar, it’s difficult to find a date for WordCamp US that doesn’t have conflicts. This is a good problem for the community to have. Matt Mullenweg shared during the State of the Word that the community has experienced 50% year over year growth with more than 350K members in 687 meetup groups and more than 5,000 meetup events. With this rate of growth, the community can expect more regional and local camps to spring up in the coming years, which means more conflicts but also more options for getting together in the future.

by Sarah Gooding at December 14, 2018 12:43 AM under wordcamp us

December 13, 2018

WPTavern: WordPress Plugin Directory Now Features a Curated Section for Block-Enabled Plugins

If you visit the plugin directory, you will notice a new section at the top featuring block-enabled plugins. WordPress 5.0 has been downloaded more than 8 million times, just one week after its release, and users are looking for blocks to extend the new editing experience. WordPress.org is highlighting plugins to push the block ecosystem forward and will soon be doing the same for themes.

There are currently 94 blocks in the featured section. In a post on make.wordpress.org/plugins, Samuel (Otto) Wood invited developers to email the plugins team at plugins@wordpress.org if they have a block-enabled plugin that they want to be included. The basic requirements are a plugin that introduces or improves blocks.

I asked Otto how they select from submissions. He said the plugins team is curating the list manually and adding those they think are good or interesting.

“It’s not a high bar; if it has a neat block, we’ll add it for now,” Otto said. “We may raise the bar depending on how big the section gets, and the section is not final by any means. We’ll change the inclusions according to how it works out. The goal is to promote neat and cool integrations, but there aren’t a lot of those yet. It’s new.”

Assigning a tag to block-enabled plugins that authors could opt into would eliminate the need for manual approval on the section, but Otto said they are currently handling it more like a showcase.

“Letting the plugin authors just add a tag would reduce the available tags (it’s already limited to 5) as well as reducing the value of curation,” Otto said. “We may change that as well in the future, somehow. Nothing is set in stone right now, we just want to see people making cool blocks and see what happens with that.”

A directory devoted entirely to blocks may also be coming to WordPress.org next year. In a recent post, Matt Mullenweg identified 9 Projects for 2019, including “building a WordPress.org directory for discovering blocks, and a way to seamlessly install them.” This is a much larger task and requires WordPress to answer a few questions: Will plugins continue to be the primary delivery mechanism for blocks? Or will WordPress.org implement a system where users can download JS-only blocks, similar to the Gutenberg Cloud project?

Three months ago, Otto commented on a post about Gutenberg Cloud, saying that js-only blocks are likely only suited to frontend enhancements.

“I remain unconvinced that js-only blocks have a place which is meaningful other than the trivial layout based things that blocks can do,” Otto said. “Yes, you can build great looking blocks with JavaScript only, and since it’s an editor, that is a really big deal. But without any actual support on the backend to ‘do stuff of substance,’ it is just visual glitter.”

Offering JS-only blocks through WordPress.org might also complicate block discovery if users don’t know whether to look for blocks in a plugin or via the JS-only block delivery system. There are a lot of unknowns in the block era that will require WordPress to make some decisions. Meanwhile, the ecosystem of block-enabled plugins will continue expanding as more users adopt the new editor and especially as widgets and menus are ported to blocks in phase 2 of the Gutenberg project.

by Sarah Gooding at December 13, 2018 09:32 PM under gutenberg

Dev Blog: WordCamp US 2019 dates announced

Save the date! The next WordCamp US will be held on November 1-3, 2019, in beautiful St Louis, Missouri. One of our largest events of the year, WordCamp US is a great chance to connect with WordPress enthusiasts from around the world. This is also the event that features Matt Mullenweg’s annual State of the Word address.

We’d love to see you in St. Louis next year, so mark your calendar now!

by Andrea Middleton at December 13, 2018 07:47 PM under WordCamp

WPTavern: Interview with Rachel Cherry: Automattic Pledges to Fund WPCampus’ Accessibility Audit of Gutenberg

While at WordCamp US, I had the opportunity to catch up with WPCampus director Rachel Cherry, who is coordinating an audit on Gutenberg for the organization she leads. WPCampus launched its crowdfunding campaign at the end of November and more than $10K has come in towards the $30K goal.

The day before WordPress 5.0 was released, WPCampus announced that Automattic has pledged to ensure WPCampus’ accessibility audit of Gutenberg is fully funded.

“I think that they [Automattic] see that it is important,” Cherry said. “Even when they said they weren’t going to do it, I don’t think it was ever ‘We’re never going to;’ it was just ‘Not right now.’ For us, we couldn’t necessarily wait for ‘maybe we’ll do it later,’ so that’s why we jumped on it and got the ball rolling. I think they saw an opportunity where they could step in and have the means to move this along even further. They see the value and I think that’s why they wanted to jump in. They also saw all the community effort going on.”

In the interview below, Cherry discusses how leaders in the WPCampus community rallied to get the audit in motion. The organization has received seven responses from vendors and is currently in the selection process. She also shared a little bit about her conversation with Matt Mullenweg during his community office hours and their discussion about how WordPress is used in higher education.

Cherry’s strategy in advocating for accessibility is to focus on slicing through the confusion surrounding accessibility problems with an emphasis on education and communication. Although WordPress has set accessibility standards, the project has fallen short on enforcing them. In addition to putting automated accessibility testing in place for core, Cherry said she would also like to get more support for helping theme and plugin authors meet accessibility standards. This would help ensure that the code WordPress.org puts on the web is more accessible for those who are creating customized sites.

by Sarah Gooding at December 13, 2018 04:29 AM under wpcampus

Dev Blog: WordPress 5.0.1 Security Release

WordPress 5.0.1 is now available. This is a security release for all versions since WordPress 3.7. We strongly encourage you to update your sites immediately.

Plugin authors are encouraged to read the 5.0.1 developer notes for information on backwards-compatibility.

WordPress versions 5.0 and earlier are affected by the following bugs, which are fixed in version 5.0.1. Updated versions of WordPress 4.9 and older releases are also available, for users who have not yet updated to 5.0.

  • Karim El Ouerghemmi discovered that authors could alter meta data to delete files that they weren’t authorized to.
  • Simon Scannell of RIPS Technologies discovered that authors could create posts of unauthorized post types with specially crafted input.
  • Sam Thomas discovered that contributors could craft meta data in a way that resulted in PHP object injection.
  • Tim Coen discovered that contributors could edit new comments from higher-privileged users, potentially leading to a cross-site scripting vulnerability.
  • Tim Coen also discovered that specially crafted URL inputs could lead to a cross-site scripting vulnerability in some circumstances. WordPress itself was not affected, but plugins could be in some situations.
  • Team Yoast discovered that the user activation screen could be indexed by search engines in some uncommon configurations, leading to exposure of email addresses, and in some rare cases, default generated passwords.
  • Tim Coen and Slavco discovered that authors on Apache-hosted sites could upload specifically crafted files that bypass MIME verification, leading to a cross-site scripting vulnerability.

Thank you to all of the reporters for privately disclosing the vulnerabilities, which gave us time to fix them before WordPress sites could be attacked.

Download WordPress 5.0.1, or venture over to Dashboard → Updates and click Update Now. Sites that support automatic background updates are already beginning to update automatically.

In addition to the security researchers mentioned above, thank you to everyone who contributed to WordPress 5.0.1:

Alex Shiels, Alex Concha, Anton Timmermans, Andrew Ozz, Aaron Campbell, Andrea Middleton, Ben Bidner, Barry Abrahamson, Chris Christoff, David Newman, Demitrious Kelly, Dion Hulse, Hannah Notess, Gary PendergastHerre Groen, Ian Dunn, Jeremy FeltJoe McGill, John James Jacoby, Jonathan DesrosiersJosepha Haden, Joost de Valk, Mo Jangda, Nick Daugherty, Peter Wilson, Pascal Birchler, Sergey Biryukov, and Valentyn Pylypchuk.

by Ian Dunn at December 13, 2018 03:13 AM under Security

December 12, 2018

Post Status: Interview with Matt Mullenweg on Gutenberg, WordPress, and the future

Welcome to the Post Status Draft podcast, which you can find on iTunes, Google Play, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Brian Krogsgard.

In this episode, I am joined by Matt Mullenweg, the co-founder of WordPress and CEO of Automattic.

Just after releasing WordPress 5.0, and on the heels of WordCamp US, Matt and I review the event, the release, and discuss how he thinks things went, what could have gone better, and what he sees ahead.

We also dig into WooCommerce, various plans around core development processes, Automattic, and more. I hope you enjoy.

And an audio version.

Full transcript is coming soon.

Episode Links

Sponsor: iThemes

iThemes makes great WordPress plugins, themes and training to help take the guesswork out of building, maintaining and securing WordPress websites. I talk to iThemes CEO Cory Miller during the break to hear about what they are working on, and excited about for the coming year.

Thanks to iThemes for being a Post Status partner.

 

Full Transcript

Brian Krogsgard: Hello and welcome to Post Status Draft. I hope you enjoy this interview with Matt Mullenweg. It lasts for a while, but I think that it’s worth catching the whole thing. We cover a whole bunch of topics. I want to thank iThemes for being our partner for this episode. iThemes has been in the WordPress space for so, so long and they make many great products, whether you’re looking to secure your website, manage your plugins and themes and so much more. Go to iThemes.com to learn more and thanks so much to the team at iThemes for being a Post Status partner. Now here’s the show. So hello and welcome to Post Status Draft. Fresh off of the release of WordPress 5.0 and WordCamp US, I’m here with Matt Mullenweg, the co-founder of WordPress. Hey Matt.Matt Mullenweg: Howdy, howdy. It’s good to see everyone again.

Brian Krogsgard: Yeah, it’s great to see you. You look comfortable. You must be somewhere that is something like home.

Matt Mullenweg: Yeah, I’m in actually New York City this week. I had a few meetings after the WordCamp and it’s also just one of my favorite cities to be especially this time of year. The lights and everything around Christmas time are just gorgeous, so it’s fun.

Brian Krogsgard: Yeah. I’ve never been to New York City in the Christmas season, but it’s one of those bucket list type of things. So let’s start off with just how are you feeling post-release, post-event? How do you feel like things went overall?

Matt Mullenweg: Super energized. I’d say like day before the release was pretty nervewracking, but it went better than I think almost anyone hoped, including myself. There was a great energy at WordCamp of we were able to kind of … I think instead of arguing about whether we should do a release or not, should it be Thursday or Tuesday or next month or never, or all these sorts of different options, everyone would say, “Okay, it happens. The world didn’t end and what can we do next to make things better?” That kind of making things better conversation is where I find the WordPress community is most productive. It’s where you can really get all sorts of different ideas and you can really get to the point where it does make things better for our users.

Brian Krogsgard: Yeah. And I tend to think generally people cool down when they’re in person versus when they’re online. So all the energy, the pent-up energy from working through all the things that have to do with the release over the course of two years and it finally comes on you, sometimes it just feels good to get it out at the end of the day. You let those bygones be bygones.

Brian Krogsgard: I felt like it was actually a pretty drama-free release and event. I didn’t see any major bugs come across. I asked some of the big hosts and some of the big plugin companies, I was like, “What are you all seeing? Are you seeing a bunch of stuff come through?” And I didn’t get much. Have you heard much feedback in terms of, are there a lot of bugs coming up? Are there are a lot of issues or has it been fairly smooth?

Matt Mullenweg: Well, what I’ve been telling you all year, that it would be anticlimactic, I was half right. The software was anticlimactic. Everything around the software was pretty intense.

Brian Krogsgard: Very climactic, yeah.

Matt Mullenweg: But yeah, I actually didn’t realize it before I got on for State of the Word, but host site GoDaddy, others have already upgraded over a million sites. They’re seeing normal support loads, things like that. It’s like I said, ultimately what drives a release day is, is the software ready? And the software was ready and all the inputs, all the data, all the sort of normal things we look at were there. It was just one of these things where the people, we didn’t seem ready and that’s much harder to navigate. Sometimes getting it out there helps a lot, but it’s one thing that I’ve seen throughout my entire professional software career is the longer you go between releases the harder they are. I’ve seen this in small teams, big teams, public, private, inside automatic, outside, whatever it is. If you can get to where you’re releasing more frequently, it just removes a ton of stress and burden on each individual release and I think makes for ultimately a much better process for everyone involved.

Brian Krogsgard: Yeah, and I want to dig into more about the process. I was really surprised. I don’t think I saw a single person share your old blog post about the version 1.0 and the importance of shipping 1.0. Maybe we’re just getting really old. So referencing a blog post that’s that many years old is harder now. But yeah, I’ve been in the camp for a while now that it just seemed like you’ve got to get it out there. I felt like we always had an advantage in the WordPress landscape and this is one of the things I was worried about when you announced the big feature release style. Here are our three goals and we’re going to make the releases strategic to that. We had the benefit of iteration when we had the regular releases. So overall do you feel like the tradeoff of losing the regular major releases was worth it in order to get the big thing shipped?

Brian Krogsgard: I think of like Drupal, the struggles and the boundaries they had going from 6.0 to 7.0 to 8.0 and it was almost like a whole new thing. This was really our first time, in a really long time at least, maybe ever, that you feel like you update and it’s in some ways a whole new thing, and it was a long release cycle that led up to that. So do you think that tradeoff was worth it or do you think there was a tradeoff? Is my assumption a poor one?

Matt Mullenweg: Well, there was in that we didn’t do a major release for a year. We did slip some things that would previously be in major releases in the minor releases, in the 4.9.X kind of releases, so that helped. That’s a good question. I think that in 2019 we can do both. So we can keep some really super rapid public iteration and the feature plugins, and who knows, I’d actually love to see a few more kind of areas of WordPress that we want to innovate in or expand in, take more of this plugin approach. And then we also have a lot of great stuff in the hopper for some major releases. I think we’ll be able to do … there was a lot of talk at contributor day as we were looking at it.

Matt Mullenweg: It actually slipped my mind that we did that whole code reformatting and JavaScript reorganization in trunk, and that’s not in 5.0, right? Because we branched off 4.9.8 to make it as stable and as few changes as possible. So we’ve got actually, I think there’s another 200 patches already in trunk that weren’t in 5.0. So we’ve just got a lot of good stuff already in there, including the whole reorganization that you kind of put that together plus maybe ServeHappy and the white screen protection and some really cool stuff that’s kind of more like small stuff. That could be a 5.1 right there. I could see that going in the beta January, RC in February.

Brian Krogsgard: Yeah, talk about ServeHappy. I mean, for I don’t know, five, six, seven years, people have wanted, demanded PHP upgrades and it was a footnote in this state of the word.

Matt Mullenweg: I should have done it as one more thing.

Brian Krogsgard: One more thing, yeah. Had to really get all the developers on your team for that one. So you made a commitment to in 2019 have a staggered upgrade process to mandate certain versions of PHP. Remind me if I’m incorrect, 5.6 in the Spring and 7.0 next winter. Is that basically the timeline?

Matt Mullenweg: Yeah, that’s the idea and we’re just going to go through. And again this is, just like with Gutenberg, it’s not about changing a version number or something. It’s really about bringing the whole community along for the ride, so we need to scan all the plugins. For 5.6, I think we’ll actually be able to update them or send patches to maintainers, even update and maintain plugins, because those changes are pretty easy. Seven is tougher and I think that is, we’re targeting December for that. I could see that slipping, just depending on whether host in the meantime and everyone else is able to get there, but even getting to 5.6 opens up a ton of possibilities, including with things like OAuth and GraphQL and namespaces, and there’s some pretty cool features. 5.6 is ancient at this point. It had a lot of improvements over 5.2.

Brian Krogsgard: And a lot-

Matt Mullenweg: And we still have a lot of folks on these older versions, so part of the reason we’re giving ourselves time as well is to, if we can run some analytics to figure out which host these old sites are on Ron and reach out to them, try to work with them.

Brian Krogsgard: Do you think a part of the reason why you even think this is possible, for a long time, I mean, people were running WordPress across a huge spectrum of versions of PHP. Do you think part of the reason why you even think this possible is the hosting relationships that had been made between the community and the hosting companies over the past few years? Because that’s something that I’ve felt like has been quite significant. The efforts that, if you look at the big ones, the GoDaddy and the Bluehosts of the world, the amount of commitment they’re giving to the community, do you think that’s a big part of it? And how hard is the long tail going to be to capture, do you think?

Matt Mullenweg: That’s a big question. First, I’ll say that the improvement of hosts, particularly the big ones in becoming kind of like WordPress first, providing a really first-class WordPress experience from security updates, everything, it’s probably been the biggest change in the WordPress ecosystem over the past five years. And I have huge admiration for them because they’re doing this for millions of sites, thousands of support folks. They’re really moving some really, steering some really large ships and the results have been fantastic. We got, I think it was up to 68% of our WordPress was on 4.9 by the time 5.0 come out.

Brian Krogsgard: Yeah, that’s great.

Matt Mullenweg: But in terms of what’s going to make the PHP upgrading easier, it’s really a combination of everything, including time, including some of this white screen protection stuff that we’re doing. If we can back port that, you know we still backport to 3.7 all of our security updates?

Brian Krogsgard: Mm-hmm (affirmative).

Matt Mullenweg: Which is kind of wild.

Brian Krogsgard: It is. It’s great for security of the Web broadly, but it’s quite something.

Matt Mullenweg: Yeah, if we can do that for some of this, maybe we can put some of this white screen upgrade protection into those old versions, so that way we can kind of protect people who might be doing plugin and theme or core updates from breaking their site in programmatic way. Um, it’s also the work that’s gone into updates. We know we migrated to a new data center this year for WordPress.org It’s like, I forget the exact or something like five or 10 times more powerful than the old one.

Brian Krogsgard: Wow.

Matt Mullenweg: Almost no one noticed. But you notice that there’s no more 503s when we run the updates, and things can go faster. This means we can do auto updates better, which means that we’ll be able to do opt-in for core and plugin and theme auto updates and then maybe move that to opt-out 2020. These are all just things that have been going on that represent thousands of hours of work from hundreds of people that set the stage so we can do stuff. It’s part of the reason I think that we will be able to move a lot faster in 2019. We had to stop core ,essentially freeze it for Gutenberg, because we were building a new foundation and you can’t build the house on top while you’re also pouring the concrete, right? Things will sink. They’ll get off center. I’ve never built a house so I don’t know this analogy all the way, but now we’ve got the foundation. We’ve got this framework and things being built on top of that framework. We’re already starting to see the benefits to things like keyboard navigation and accessibility when they’re built using Gutenberg fields that already have this kind of baked in.

Matt Mullenweg: So I think that we have the opportunity to do just a massive upgrade not just of the editor but of every single plugin, every single theme, every single person’s experience with WordPress because think about it. No one just runs core. Cool if we do Gutenberg in core? Ultimately it doesn’t matter. Everyone’s got five, 10, 20 different plugins. They’ve got their theme which might implement who knows how many additional features baked into the theme? Probably dozens, if you think about all the customization options, that’s all going to be able to be reimagined now and already is. We see some of this, over 100 themes in the plugin directory. You might have noticed we put the Gutenberg-ready plugins at the very top, even above featured. We’re really trying to get everyone on this train.

Brian Krogsgard: Do you think there was a messaging gap in a trying to get across the idea that Gutenberg is a foundation rather than a window dressing or wallpaper or whatever other nonstructural housing component we want to compare it to?

Matt Mullenweg: Well, I think it’s easy to say that there was a messaging gap and that communication could have been 10 times better or whatever, because there are obviously some people who wren’t on board and still aren’t on board. So now, is there anything that could have gotten everyone 100 percent?

Brian Krogsgard: No.

Matt Mullenweg: I don’t know, but I think we will always strive to do better. And ultimately, I mean, one of the things that made me pretty confident about the release wasn’t that Gutenberg is perfect. It’s not. By the way, it’s still not right for a ton of people, but that’s okay. You know WordPress, unlike almost every other SaaS service or software use gives you control. And the fact that we have classic editor as a first party supported official thing and that anyone for whatever reason, literally any reason, can still use the old experience instead. That’s what I meant when I said 5.0 was going to be anticlimactic, not that it meant Gutenberg was perfect or ready for everyone, but that forever was not wordy. They’re just a click or two away before or after the release from having the experience that they used to.

Brian Krogsgard: Yeah, one of the things I like to remind myself of is that neither was TinyMCE perfect or right for everyone.

Matt Mullenweg: Well, no.

Brian Krogsgard: And that’s why it was being replaced. So I think sometimes we do have to look at what are we trying to replace and what do we have right now? Is that worth getting out into the world and iterating on?

Matt Mullenweg: Did you see those user tests videos?

Brian Krogsgard: I did. Unfortunately my wife said, “Do you want to go see the Harlem Globetrotters?” And I was like, “Absolutely.” And I didn’t have WordCamp US on my calendar yet.

Matt Mullenweg: Oh, don’t worry, don’t worry.

Brian Krogsgard: So we double booked, so I re-watched the whole State of the Word, including the user tests, the Q and A, the whole thing, and it was pretty amazing seeing those user tests. I’ve seen people do user tests before. They’re often really terrible.

Matt Mullenweg: Painful.

Brian Krogsgard: That’s why for years I’ve tried to make my own message that we need to continually support things that make WordPress easier to use, so I think that was a good thing to highlight in the State of the Word.

Matt Mullenweg: And by the way, I probably would’ve picked the Harlem Globetrotters over me as well, so o need to apologize.

Brian Krogsgard: It was the first one I’ve missed since like 2012.

Matt Mullenweg: That’s awesome. That’s great. I’m an average live experience. The Harlem Globetrotters are amazing live.

Brian Krogsgard: They are.

Matt Mullenweg: You can always catch State of the Word on vide later.

Brian Krogsgard: They are. I may as well use the opportunity too to thank [David Bisset 00:15:39], because he did a fantastic job with both tweeting things and just generally keeping people that follow along with Post Status up to date and it turned out to be a good outlet for him because twitter banned his personal account because they thought that he was tweeting so much.

Matt Mullenweg: Wasn’t that wild?

Brian Krogsgard: Yeah.

Matt Mullenweg: I know. That guy is a national treasure of WordPress.

Brian Krogsgard: He is. He is. If there was a community spirit award, he should win it.

Matt Mullenweg: Absolutely.

Brian Krogsgard: So he stood up to ask a question during the State of the Word and unfortunately ran out of time, so I would-

Matt Mullenweg: Right, I felt so bad that we didn’t get to … There were a lot of people in line, but just some of those earlier questions were a bit longer and I could tell the room was starting to, like I think we were already like an hour 45. We were pretty far into it, so …

Brian Krogsgard: Yeah, and maybe we’ve put a 30-second clock next year for people to ask a question.

Matt Mullenweg: I’ve been thinking about that, like there were some definitely things in the room this year, like it was very dark in the audience so it was a little harder to see. I think that also subdued people. There was a little more distance between the stage and the people which looked a little more theatrical, but I think also made the audience a bit more disconnected. And even, there was a funny thing. You saw the spotlight on the question askers?

Brian Krogsgard: Yeah.

Matt Mullenweg: It was so bright and at an angle that it was shining in the eyes of everyone sitting next to them. So after the first or second question there, there was a huge hole in the audience next to the mic because we were just getting like it had this crazy spotlight on it. I think we can figure out some different ways of doing lighting or doing the questions in the future that might be a bit a bit easier.

Brian Krogsgard: Well, you’ll have that opportunity in St Louis, right, for the next two years.

Matt Mullenweg: Woo hoo, St. Louis. I’m very excited about that.

Brian Krogsgard: Yeah, I’m excited about that too. I haven’t been there in a long time, and what David-

Matt Mullenweg: I love that we’re doing the opposite of Amazon. They had the opportunity to pick any city in America and they go to D.C. and New York.

Brian Krogsgard: I know.

Matt Mullenweg: They’re both amazing places, but not really shining a light on places that don’t get as much love already.

Brian Krogsgard: Yeah, I think my-

Matt Mullenweg: And we’ve had Philly, Nashville and now St. Louis, I really dig the WordCamp US thing.

Brian Krogsgard: Yeah. I have feeling that Amazon may have been including some political reasoning and in their strategy for that, but that’s okay. WordPress doesn’t have to do that. We can go wherever we want.

Matt Mullenweg: We can go to Canada, which was one of the questions, which I thought was kind of cool.

Brian Krogsgard: Including Canada, which was a good question. I actually had that brought up to me before WordCamp about the U.S./Europe thing and whether we can learn from that and have WordCamp Americas or something.

Matt Mullenweg: Yeah, what’s your thought on Central America in that equation?

Brian Krogsgard: Yeah, I mean I think that there’s a lot of cultural differences, but I think anything Americas, there’s some common themes of people that work hard, people that explored many centuries ago. So I don’t know, I’m probably not the best person to answer that type of question, but …

Matt Mullenweg: I’ve been thinking about it a lot, like what are the logical divisions and because we do have some rules in the WordCamp world around like what could be … I’d love to see a WordCamp Asia, for example. Asia is obviously geographically, culturally and language-wise, incredibly diverse.

Brian Krogsgard: Right, I think the lingual differentiation would be a challenge, so I don’t know what the best regions would be but perhaps-

Matt Mullenweg: But then look in Europe.

Brian Krogsgard: Yeah.

Matt Mullenweg: It has a ton of languages [inaudible 00:19:08] English.

Brian Krogsgard: I always envy friends in Europe because they all speak like five languages plus, and some of them speak better English than I do.

Matt Mullenweg: Oh, for sure. Have you ever seen a map of the lower 48 overlaid over Europe?

Brian Krogsgard: Yeah, it’s very, very similar in size, so-

Matt Mullenweg: Yeah, it’s actually, you forget how large actually the lower 48 of the U.S. is that it covers kind of like into Europe, pretty far into Russia and Turkey and Middle East.

Brian Krogsgard: Yeah. We think of Alabama and Houston or Birmingham, Alabama and Houston, Texas as pretty close, but that could be different countries if we were in Europe with different languages and culture. It’s a reminder of the diversity in our space and how serving different cultures and people from different backgrounds is extremely important. All right, so David’s question was, what are the dates for WordCamp next year? Do we have any idea?

Matt Mullenweg: Oh, I think we know them. I’ll put them out later. They’ll be in a blog post or something.

Brian Krogsgard: Okay, he will be disappointed again.

Matt Mullenweg: Well just, I don’t know if I could tell you the day of the week of my birthday or something. I’m pretty bad at dates.

Brian Krogsgard: No, that’s fine.

Matt Mullenweg: As you might guess from-

Brian Krogsgard: Is it going to be in December again, though?

Matt Mullenweg: I believe so. Don’t hold me to anything there. I will officially find something.

Brian Krogsgard: But late in the year still.

Matt Mullenweg: Yeah, yeah, so I think that we’ll put up like a placeholder site for 2019, and there will definitely be some tweets and some official stuff saying the dates.

Brian Krogsgard: Okay.

Matt Mullenweg: But to your earlier point, I actually feel what you just described of going between countries in Europe, I feel that when I’m, excuse me, on the East Coast of America because I can actually drive eight or 10 hours and still be in Texas. I can drive two hours over here and cross through three different states. And that was one of the points that I tried to make. This was actually I think one of my weaker Q&As. I had two answers that were two of the worst answers I’ve given probably the past few years, and one was what people heard me say, which I wasn’t trying to say, to Morton’s thing.

Matt Mullenweg: Which I was trying to make the point that in a distributed organization or where we have people working across things, you can read into someone’s language and it might not be their first language, so it’s really good to give the benefit of the doubt and realize that we’re not all speaking our native tongue. And so things might come across as harsh or worse or rude or things, when it’s just not at all. It’s certainly not the intention of the person to communicate that way. And the other was the answer, I think it was Birgit’s question about being hired to work on things.

Brian Krogsgard: Yeah, corporate sponsorship for WordPress work.

Matt Mullenweg: Yeah, neither … I think my brain was just a little fried by the end of the day.

Brian Krogsgard: So what would you adjust in terms of, I think that question was around how to … I was actually with you with Morton, that I didn’t notice the issue. It seemed like you were pretty clearly speaking about broader communication things, not specifically with his communication, which is-

Matt Mullenweg: I would never make fun of Morton’s or anyone’s skills speaking another language.

Brian Krogsgard: Yeah, and that one was pretty clear to me. But the one about corporate sponsorship, do you think there’s a place for … How do you encourage independent work on the WordPress community, nonprofit side of things? Is there a place or a way that that can be done without corporate sponsorship? Because I know, I mean I’m self-employed and I can personally understand if I suddenly gave 10 or 20 hours a week or whatever amount of time to the core project in a non-revenue generating way that would be felt. So is there a way that that can be done, or do you think corporate sponsorship of community work is really the only way to go about it right now?

Matt Mullenweg: Well, let me take a second crack at this one. First and foremost, I never want to downplay the contributions of people doing it in their spare time.

Brian Krogsgard: Yeah, and it is, I mean it’s astonishing and I could be that person, too. I don’t choose to be that person in this stage of my life, but yeah, it’s amazing what people are doing completely outside of work time.

Matt Mullenweg: Yeah, and I also don’t want to understate how big an impact on the WordPress project, two to four hours a week out of the 168 can have a really huge impact on some big areas. Even a single hour a week, if put in the right place, can move mountains. And WordPress was largely built by volunteers and people doing it in their spare time, and I worry to say, to ever get to a point where we’re saying we only value people who are doing it full time, or it’s only possible to make a change if you’re doing it full time. So that’s one point I was trying to make, that let’s never downplay the value that people can do with just a little bit of contributions. Five for the Future is just two hours a week in a work week, right?

Brian Krogsgard: Right, yeah, and that was the question [Daniel Bock Huber 00:24:12] had was if you had plans or iterations that you thought would be good for Five for the Future?

Matt Mullenweg: Oh, for sure. The second is that the WordPress Foundation is not designed to be an employment entity. Now, there’s no employees. There’s no HR. There’s no benefits. There’s no payroll. There’s no anything, and going from zero to one there is actually a pretty big thing. It is designed to give grants. We can give money to other organizations. By the way, I think that there’s also a big opportunity for other nonprofits to be part of this. There’s no reason to say only for-profit corporations can sponsor people that work on WordPress. I would love to see more nonprofits that by the way have a lot more expertise in some of the areas that we want more contributions in, including design, accessibility, privacy, internationalization.

Matt Mullenweg: These things, there’s full nonprofits dedicated to that have often sometimes very large staffs and pretty large budgets, journalism. These I think are really fruitful areas, and in fact one of the things that, I don’t know if you saw Morton’s talk, a lot of people I thought misread it. Maybe I misread it as well. When he was talking about open governance, my take was that he was talking about getting WordPress a seat at the table, and discussing these regulation changes and et cetera happening. I think the example last year was, there was this meeting at 10 Downing Street. Who was there? Was WordPress represented?

Matt Mullenweg: And he started talking about the Web Foundation, and I began thinking. I was like, “Wow, well, WordPress only represents a third of Websites, and not even, really. It’s a third of the top 10 million. Another foundation like the Web Foundation actually might be a better vehicle to try to advocate on the open Web as a whole, versus just the people who happen to be using a single CMS.

Brian Krogsgard: Yeah, and I don’t want to speak for him in terms of which audience he was trying to, or which group he was trying to represent in terms of within WordPress, or WordPress within the broader Web. I do think that there are often questions about governance of WordPress. You have long been the central vision of the project, and then delegated the execution of that vision to many other people who then lead this project, which is massive at this point. One of the things I’ve always asked you for several years now was, how many people do you have directly reporting to you?

Brian Krogsgard: Because one of the things I find to be important is under this model, where your vision is required, then if you’re spread out so thin it requires these sprints to focus towards WordPress, rather than always being able to have kind of a constant flow, even if it’s a minority of your time, going towards that, establishing that vision for WordPress. So, how have you evolved in that regard? I know you’re-

Matt Mullenweg: What was the number last time you asked me?

Brian Krogsgard: It was high.

Matt Mullenweg: What is high? There was one point it was like 26 or something.

Brian Krogsgard: Yeah, it was in the 20s. It was in the 20s last year I think when we talked about it.

Matt Mullenweg: Yeah, it’s under half that now.

Brian Krogsgard: That’s great.

Matt Mullenweg: So, that’s been really good. There’s been a lot more leaders, but I would actually argue the point that WordPress has always been sort of my vision being set, or even my direct leadership. There was a good four or five years there where the leadership structure, because we’ve experimented with lots of different, we don’t call it governance, but essentially leadership structures in WordPress. For a while, we had kind of the … It wasn’t a committee approach, but essentially like the lead developers consensus approach. We did that for a few years.

Matt Mullenweg: Even from the beginning it wasn’t just me. It was me and Mike Little, so it’s never been solo. Then we went to where the release lead was the final decider, including over me, so that was probably, I don’t know, 3.9 to 4.7 maybe, that including could overrule me as project lead for what was in the release or not, and that was to try to give a little more autonomy and flexibility to release leads. But the big change was a few years ago I said, “Okay, I’m going to take back over core WordPress development,” and that was to try to provide a … Try to make some of these big changes happen. So right now it is much more of a benevolent dictator model, although both of those words are questionable. But, I don’t see that as the permanent forever structure, you know? [crosstalk 00:28:54]-

Brian Krogsgard: One problem with that is-

Matt Mullenweg: I don’t know if I can sustain this forever. I mean, this is a pretty intense period and we’re doing some pretty intense work, and I’ll need a break at some point, too.

Brian Krogsgard: Yeah, and how do you, or do you think there’s merit in opening that up in some way to certainly have more community input, but sometimes that’s not good, you know? Sometimes the central vision idea can be more productive, but when you bring that into open source software versus running a company, maybe there’s different consequences. So have you given any thought to what does WordPress look like after this phase in terms of a governance structure?

Matt Mullenweg: It’s hard, because I haven’t seen any models where anything resembling voting works, you know?

Brian Krogsgard: Yeah, for running software, you mean.

Matt Mullenweg: Yeah, and for choosing a direction. It’s not that many models for consumer-facing software. There’s some for server-facing software, where sort of like a committee approach works, you know? It seldom creates great user experiences. You kind of want, I’m not saying it always has to be me, but what I want is a strong, opinionated, thoughtful leader doing, setting a bold direction, taking experiments and being willing to fail, comfortable with failure, is I think what you need to create great software.

Brian Krogsgard: So how do you-

Matt Mullenweg: And that’s tough, and by the way, we’ve had lots of those leaders in the history of WordPress, and I think that’s been the success. It’s not just because I’m doing anything.

Brian Krogsgard: Sure.

Matt Mullenweg: It’s that we have lots of folks and we have, as a community including myself, invested that authority and power in them, and that trust. It doesn’t mean that it’s always been right, like we’ve definitely done things that we might undo later or that were mistakes, but the ability to make those mistakes is what you need for an innovative organization. When you look at any organization, private or public, it’s too afraid to fail, that’s when you get this kind of incrementalism. That’s when you get this kind of fear of change. That’s when you essentially stagnate, and if you were to point to any place that software goes poorly, whether that’s in government or companies that don’t innovate or get disrupted by smaller upstarts, anything, it’s because one of those happened or probably all of those things happened. They got too successful and then they were afraid to fail, because it was too embarrassing and they had too much to lose, and then they stagnate.

Brian Krogsgard: All right, we’re here to take a quick break and I want to thank our partner, iThemes, long-time supporter of Post Status. I’ve got Cory Miller on with me to talk about what they’ve got going on. Hey, Cory.

Cory Miller: Hey, Brian, thanks for having me on.

Brian Krogsgard: Yeah, it’s my pleasure and I appreciate your support over the years. I was hoping that you could just tell me maybe what’s a big success iThemes had in 2018, and what you’re looking forward to next year?

Cory Miller: Yeah, as you know in January of 2018 now we were acquired. iThemes was acquired by a great hosting company named Liquid Web, so this year has been spent integrating. We are almost done with the first round of integrations for our key product, iTheme Sync, which promotes site management for freelancers and agency WordPress Websites, BackupBuddy, our long-time popular plugin, and securities. So we’re almost done with the final round of that. You know in any transition there’s always bumps, but it’s been a really good ride so far.

Brian Krogsgard: Yeah, have you been getting good feedback from LiquidWeb customers so far, or I guess are you looking forward to seeing iThemes products more integrated with LiquidWeb’s stuff?

Cory Miller: Very much so. We saw hosting as the future for WordPress. All of the big hosting companies making significant investments in WordPress, and this was a way to join forces with a great hosting company and for our products, our team, to live on into the future doing really good things in WordPress.

Brian Krogsgard: Cool, and iThemes products are still available outside of LiquidWeb as well. You can use them on any host that you choose, or a naked VPS if you want help managing a server that you want to pull all the lever, you can still do that but you can use all the iThemes tools to help you manage the day, and [inaudible 00:33:31] out of your WordPress Website. I’m really excited for you guys and what you have going on, and look forward to hearing more as next year comes along. Thanks for being on real quick, and if people want to learn more about what you’ve got going on, where do they go?

Cory Miller: iThemes.com, best place to click some links and see if we are offering something that you’re in need of. We’d be happy to serve you.

Brian Krogsgard: Awesome, well, thanks for being such a big part of the WordPress community these last 10 years plus, and a partner of Post Status for as long as Post Status has existed.

Cory Miller: Yeah, we love Post Status. Keep doing what you’re doing, Brian. Thank you.

Brian Krogsgard: Thanks, buddy. Bye. We’ve got another question from Ant in regards to giving people a seat at the table in a governance structure, which was seeking an update on the growth council, whether that was productive this last year, whether it happened. How can it happen going forward? I don’t know anything about what’s happened in the last year, so what have you learned there, and what’s happened?

Matt Mullenweg: Yeah, so we created these two growth councils, one consumer one and one enterprise one, and we did these monthly meetings, video chats. And my goal with creating it was one, to bring some people together, so there are direct competitors in these meetings. It’s enterprise agencies that are bidding on the same clients. It’s Web posts that are advertising on the same key words and everything. And so you’d have like that as part of the discussion, and one of the goals also was to produce, improve essentially the WordPress experience.

Matt Mullenweg: Some parts were successful, some parts weren’t, so I was amazed and humbled by how people came together. I think it really showed something I’ve tried to demonstrate with Automatic in the past, that you can both compete and work together for a greater good. People were both able, because it was a safe space, they were able to share things that were going on in their companies, things they were hearing from clients that they couldn’t talk about publicly, things they were seeing, experiences, in a safe space that generated some amazing discussions. I’ll also say selfishly that I learned a ton being part of these meetings, so it was really, really valuable for me.

Brian Krogsgard: And that’s about how their organizations work and what’s important to them, or what kind of stuff?

Matt Mullenweg: And the people they’re talking to, whether that’s consumers, kind of the more mass market side particularly with Web posts, but also with people doing trainings, people building small Websites, which is my kind of mental model was like, if it’s people spending under $100,000 a year for a site that’s the consumer group. If it’s over $100,000 a year, that’s the enterprise group. Not exact, but that was kind of like a rough mental model. And on the enterprise side, what are they seeing? It was so interesting as well, like most of the big agencies started building sites with Gutenberg kind of like February, March, and were launching them over the summer. Now at this point, they’re basically building everything. They’ve been building everything new with Gutenberg for the better part of a year.

Brian Krogsgard: Yeah, I actually spoke with Tom Wilmot from Human Made and Jake Goldman from 10up both, and they’ve both expressed that they had an early embrace of Gutenberg and seen success with it. Somebody was telling me, I think it might have been Tom, that they showed off a demo of Gutenberg and instantly blew some Adobe experience manager style feature out of the water. Some company had spent gargantuan sums of money on the alternative experience, and they did a couple customizations with Gutenberg over the course of a couple weeks and showed them this as a prototype. It was already far superior to what their competition was putting forward, so from those-

Matt Mullenweg: There’s got to be so much of that.

Brian Krogsgard: Yeah.

Matt Mullenweg: At Gutenberg, people have written bad versions of what Gutenberg is, including myself, for five years now. And now we’ve got this standard we can all build on. I actually had it right here. Human Made had this really cool white paper. I don’t know if you’ve seen this.

Brian Krogsgard: Nice, yeah, they printed it.

Matt Mullenweg: It’s glossy, it’s pretty … I mean, these are the types of things that for enterprises are really important. PDFs, white papers, case studies, and enterprise section of WordPress.org, important for that user group. For a consumer, a lot of things that that team talked about was the importance of talking about different use cases and allowing users to self-segment over the job they want to get done, and having some guides for that, some recommended plugins, essentially hand-holding them through the process of it.

Matt Mullenweg: So I talked about what was successful about the councils. I’ll tell you what didn’t go as I hoped, producing things. I think because it was all often the CEOs of their companies or kind of the head folks, it was difficult for them to get time other than the meetings, in between the meetings, to just do work to produce for example a new enterprise section of WordPress.org. So actually on Saturday morning, I officially dissolved the councils.

Brian Krogsgard: Okay.

Matt Mullenweg: What I told the folks was, we’re not going to schedule out these meetings for the rest of the year. I left the Slack channels up so people could keep chatting if they want, and of course I said if anyone wants to keep meeting on their own, they’re happy to, or to continue the projects, and both groups said they would like to. The enterprise group wants to get the enterprise subsection of WordPress.org out. The consumer group wants to continue shipping some things, but it was a year and we didn’t ship these things, that honestly probably any … It could have happened within a month or two if it had had a lot of focus from any of the people involved. It illustrated to me actually the difficulty of a committee approach.

Brian Krogsgard: Yeah, it makes me think of-

Matt Mullenweg: One of the things that came up was the enterprise. We did drinks on Saturday as a kind of ending thing. It was a combined consumer and enterprise, and one of the things is they were like, “Hey, if you had just chosen one person to be in charge of this, that person could have said, ‘You do this, you do this, you do this,’ it would have shipped probably pretty quickly.” But because no one knew who was in charge and who could tell other people to do things, I think it was Jake who said, “I’m not sure if I can tell Tom, ‘You need to finish this page,’ or ‘You didn’t edit it.'” Who’s in charge? And so that’s I think unintentionally illustrated an alternative group and management style that, because if it wasn’t adjusted and set up correctly, which is my responsibility, my fault, and not getting the results that we wanted. So, great experiment though, and I’m really, really glad we did it.

Brian Krogsgard: Yeah, I wonder, you see movies or you see a senate hearing or something, and you have the primary people at the center table and then you have all their deputies on the outside. They’re still in a safe space, but they’re the people that actually go out and do things afterwards. It’s not like the senator or the CEO on that council necessarily that’s implementing, but they bring other people from their organization in to help the implementation component.

Matt Mullenweg: I was kind of hoping more of that would happen. It’s true, some people on the councils were contributing individually, and some lead larger organizations so they can shepherd a lot of resources as well. So, I think there’s some of both that’s needed in the WordPress world. Yoast and myself are probably good examples, Yoast the person, not the company, of a leader who’s really passionate about areas, who also brings along a lot of their company to work on it.

Brian Krogsgard: Yeah, they have a lot of manpower there.

Matt Mullenweg: Oh, yeah.

Brian Krogsgard: That they’ve got dedicated to core.

Matt Mullenweg: Person power.

Brian Krogsgard: Person power, thank you.

Matt Mullenweg: Yoast had an incredible effect on Gutenberg and the 5.0 release, even though they’re smaller than all of the hosts, all of everything else. I think it’s a great example of Five for the Future.

Brian Krogsgard: So I have one more process question, and then I want to dig into phases two through four, but Darren Ethier I think is how I pronounce his last name, he asked what were your thoughts process-wise on using GitHub for probably the most ambitious-sized project yet with WordPress from a feature plugin or feature point of view? Do you think it was encouraging enough to potentially start moving off track in SVN? I do know there was a make WordPress post that was about this, but I’m curious your personal experience, whether you liked being in GitHub day to day or using Git in the process, or if you missed track in terms of that development?

Matt Mullenweg: I mean, I’m an early adopter of GitHub. My user name is literally the letter M, to show you how early it was, and I really like it. I think it’s a great product. Having kind of a parallel process, where I’ve now been involved pretty heavily in something on TRACK, involved pretty heavily on something on GitHub, there’s pluses and minuses. I wouldn’t say either is a panacea. The thing that actually makes the real difference is much more your engineering management. It’s your triage. It’s your process. It’s the testing. On both GitHub and TRACK, we made mistakes and had tickets that sat for weeks without anyone responding to them.

Matt Mullenweg: That doesn’t have to do with the software. It has to do with the people, and I do worry the distraction of effort and time that switching source control and issue trackers and just also all the work that needs to be done to migrate all the tooling at the same time, if it would distract us from what’s actually most important in 2019, which is to tighten up some of our loose parts of the software. So that’s the only reason I’m hesitant to commit to saying that we’re going to do anything, particularly in 2019.

Matt Mullenweg: Also, I am a big fan of GitLab, obviously. I see a lot of, I noticed a lot of comments on Helen’s post for actually advocating for GitLab. All of these things are getting better pretty rapidly. GitHub was slow for a while, and now they’re really picking it up. Time is kind of on our side if we switch later, because whatever we switch to will be six or 12 months better than it is today, and probably provide perhaps more of a compelling step function and user experience than is currently there, which is yes, I totally agree the interfaces are more modern and there’s better tools, and I do strongly prefer Git for branching and all these other things. There’s almost nothing you could tell me about either way that is an argument I haven’t heard or made myself. But it’s more just about a community focus thing, and what is the issues most urgently impacting WordPress users, both current and potential, today?

Brian Krogsgard: I like what you say there in terms of the urgency factor, because I think I agree with you. Personally, if I were to do something to try to actually make code changes in SVN, I would always have to go remind myself, how do I patch something, and do I have the tools on my modern MacBook to do so? Whereas by … Go ahead.

Matt Mullenweg: I was just going to say, we’ve built a lot of bridges between them as well. WordPress is synced to Git. You can do things both ways. We have tools for migrating patches between them. We’ve got official GitHub for WordPress. There’s a lot of stuff out there, but there is a point when I really want to focus on the developer experience and really invest some serious, serious time into that, but we’ve got to get the user experience right first.

Brian Krogsgard: Yeah, I think I’m with you in terms of that priority, but long-term bringing on new people to be comfortable developing on the software, most people in their day to day are in GitHub or in Git more broadly, so even the self-hosted Git version or GitFlow I think in the long run would be good, but I like what you said there about the urgency component.

Matt Mullenweg: Well, that’s one of the things I was looking at a lot, because that is one of the I think better arguments for using something centralized like GitHub, is that a lot of people have GitHub accounts.

Brian Krogsgard: Mm-hmm (affirmative).

Matt Mullenweg: Basically there was a while, I’ve reviewed probably over 10,000 engineering applications for Automatic. Every single one of them has a GitHub link. There’s definitely something to be said for that. I didn’t notice that big a difference in type or number of contributions, so it is a barrier to entry to make a WordPress.org account. It doesn’t appear to be the most salient factor in determining whether people submit patches or are active in TRACK or not-

Brian Krogsgard: Interesting.

Matt Mullenweg: Active in [inaudible 00:46:57] TRACK or not.

Brian Krogsgard: I’d be curious how that ends up working if it was officially there, but nevertheless let’s move on to-

Matt Mullenweg: Well, just look at the numbers, because Gutenberg was as official as anything, and the numbers of contributors to that versus the number of contributors that we have in any given core release, kind of similar. I think that the hard part is actually deciding that you’re going to dive into the code. The hard part is saying like, “I’m going to take this code. I’m going to figure out the problem and then submit the patch.” And once you’ve been through that, making an account one place or another, I think it’s probably something you’ll do one way or another.

Brian Krogsgard: So phase one of Gutenberg mostly complete, or at least out the door, and you’re going to be iterating on this every two weeks like you told me before. Let’s talk about phase two through four, and let’s start with just why do you think that the order that you established things in is the right order? Why do you think this is the right direction, I guess, overall?

Matt Mullenweg: Yeah, some of it is sequential and some of it is not. Are you familiar with the Kubler Ross Five Stages of Grief?

Brian Krogsgard: No, I’m not.

Matt Mullenweg: It’s like anger, denial, depression, acceptance. You’ve probably seen these before.

Brian Krogsgard: Yeah, I’ve seen this in terms of markets. It’s the same stages of grief are identified in market cycles, so like in the stock market it’s a very similar thing, but I didn’t know it was called that.

Matt Mullenweg: I don’t have one on my desk, but I actually have some glasses that I often use for drinks that have little markers on them, and it actually has the five stages.

Brian Krogsgard: Nice.

Matt Mullenweg: We could put that in the show notes for the podcast, a link to those.

Brian Krogsgard: Yeah.

Matt Mullenweg: A common misperception, I ended up actually reading one of her books called On Grief and Grieving, and it was actually finished posthumously, so she actually passed away in the process of it. This is I think Elizabeth Kubler Ross, or I forget the exact name, but amazing book. Good to read even if you’re not going to go through grief or grieving, because we all do at some point. One of the most fascinating things I took from that book was people think of those stages as sequential, and actually they can happen out of order, and they can happen simultaneously. In fact, you can go through anger and denial and acceptance and everything all in the same kind of 10-minute period.

Matt Mullenweg: That was a really fascinating insight to me just of the human condition, because we are often more complex and less sequential than sometimes our simplified systems would like to say, or we’d like to think. Development is the same way. Phase one is not stopping where phase two is starting, and I think bits of phases one through four have already happened and will continue to happen as we go through it. It’s just more about priorities. We’ve gotten the editor experience to the point where I think it’s pretty darn decent, especially for new users. Now people, if you look at people who started using WordPress in a post-Gutenberg world, of which there are now hundreds of thousands, so they’ve only known Gutenberg. This is that example of the support person who said, “Bring me back the simple editor,” and they meant Gutenberg?

Brian Krogsgard: Yeah.

Matt Mullenweg: What is the new barrier that they’re running into? What’s the new wall they’re hitting? It’s the rest of the site. It’s customization. It’s widgets.

Brian Krogsgard: So for those that don’t have these phases locked down in their brain, phase two is customizing outside of the post content itself as the next point of emphasis. So this could be widgets, menus and miscellaneous content. David posted a funny picture on Twitter where you looked like you were in deep thought during the State of the Word and he said, “I wonder what Matt’s thinking about right now?” You said it was probably the process of transporting menus to Gutenberg.

Matt Mullenweg: Oh, yeah.

Brian Krogsgard: Moving, I feel like this is something that’s happened every few years [crosstalk 00:51:12] in WordPress, it’s like the old menu system, then the new menu system, then the customizer menu system. Now we’re talking about menus here, and also not calling it menus but reshaping to navigation.

Matt Mullenweg: And navigation block, I think is probably a good way to put it.

Brian Krogsgard: Yeah, it seems like we’ve got some debt in regards to spending time on things that then we don’t use for a super long time, so how can we do the Gutenberg way of site customization and content and try to be efficient and long-lasting with that effort?

Matt Mullenweg: Well, I mean first we’ll start doing it in plugins, in the Gutenberg plugin actually, just like we did for the editor. And so we can have, one of the reasons Gutenberg is where it is is because we did do a lot of user testing along the way, and it wasn’t just testing mock-ups or ideas. We had the actual working plugin on actual working WordPress sites so they could run. That makes a world of difference, so we’ll be able to do that for the customize, replacing widgets.PHP, piece of cake. That’s just taking over the page. The customizer is a little trickier, but we can do it because all of Gutenberg was designed to be responsive.

Matt Mullenweg: Essentially, the customizer side bar is very similar to a mobile view, a narrow screen. It’s kind of like instead of a wide version, it’s a narrow version of that interface, so I think we can slip in there. Mainly it just requires a lot of rethinking, and there are some tough concepts that currently blocks don’t have, like the idea of widget visibility, which is [crosstalk 00:52:49].

Brian Krogsgard: Yeah, I was about to say conditionality, or like show it here but not there. That’s one of the experiences that seems like it could get really confusing, because someone’s on a post and they change a sidebar, and therefore they think they changed it just there but they changed it everywhere, vice-versa. There’s a lot of UX things that seem like they could get complicated.

Matt Mullenweg: Yeah, so we’ve got to figure that out, to be honest. I don’t have the answer right now. We’ve got to experiment and test our way into what works there, because there are some powerful and complex concepts that I think we can maintain, but just make a lot more intuitive and also make not so in people’s face. So if they don’t need to have widgets or blocks that only show up on the sidebar of search pages, it’s not kind of in their face and making them think about things. It’s that whole thing, making it more powerful and more intuitive at the same time.

Matt Mullenweg: But currently, blocks don’t have a concept of that, but if we solve it for sidebars, widget areas, whatever you want to call it, perhaps we could solve that for blocks everywhere they’re used. Showing different headers on different pages is not something that is currently supported by most themes on different types of templates, but why not? That would actually be pretty cool, different footers on different types of pages. I could easily imagine different types of sites that would do this.

Matt Mullenweg: It also raised a good point, which is kind of what has always been one of my bugaboos about front end editing, is that when I’m writing, I want to focus. I don’t want to see my header and footer and sidebar and all this other stuff, much less edit them. I think, I mean I’ve always talked about zooming in and zooming out, Gutenberg essentially being like a new 3D interface for WordPress. I think we want to make it very easy to kind of zoom in and out, including focus on one single area or even one single block, if you really want to work within that.

Brian Krogsgard: And that means in some ways potentially front end editing too, right? When I think about Gutenberg, the one beef I have with writing in WordPress is all the other stuff beyond the editor. Whether it’s TinyMCE or Gutenberg, I write mostly text and a few images. I’m not doing a lot of page layout, and I love the tools that Gutenberg’s brought in. For instance, you brought up some of Nick Hamze’s blocks. I talk to Nick sometimes, and he’s got so much creativity and I love that it empowers that. But for 90% of the things I’m going to do, I’m just writing. A clear, focused writing area is what I like, so I actually just don’t like the fact that I can go into the appearance editor and the plug in screen. Those are all one click away, rather than just saying, “Here’s the page.”

Brian Krogsgard: The best Gutenberg interact I’ve had yet was actually WordPress.org/Gutenberg, because I was experiencing Gutenberg. It’s a live demo of Gutenberg. I was able to experience Gutenberg, and none of the other stuff was there. It was just a column of content, and I really enjoyed that, so is that a part, a way that you think we can focus on how to get to writing and not worrying about everything else?

Matt Mullenweg: We can support both. I mean, you currently have a version of this in Gutenberg where it can show the menu or not, or you can go to the mode which is my preference mode, where Gutenberg takes over the whole screen so you don’t have a sidebar menu there, even minimized. I actually strongly prefer that.

Brian Krogsgard: See, I didn’t even know that. I’ve missed that.

Matt Mullenweg: Oh, yeah, yeah, so go in Gutenberg to the top right, the dots. I’m trying to think exactly where it is. Are you opening your WordPress as well?

Brian Krogsgard: I am.

Matt Mullenweg: We’ll go through this together.

Brian Krogsgard: I might take over my screen share here, but that’s okay.

Matt Mullenweg: Oh yeah, do you want me to screen share?

Brian Krogsgard: No, I mean I’m recording us.

Matt Mullenweg: Oh, got you, got you.

Brian Krogsgard: So people, this might end up on YouTube or something.

Matt Mullenweg: So in the three dots, there is three kind of options there.

Brian Krogsgard: Oh, yeah.

Matt Mullenweg: Tool bar, spotlight mode and full screen mode. I actually am in full screen mode. I strongly, strongly prefer it.

Brian Krogsgard: Neat.

Matt Mullenweg: Top tool bar I don’t think is that useful, but they know that. This was basically, there was a huge kind of fight earlier. If you look at Yoast’s original post about the plan for Gutenberg, there alternative UI is basically all about the top tool bar. Then spotlight mode I also don’t love, but some people really like it. It kind of grays out the other blocks and then makes the current block you’re in more visually prominent.

Brian Krogsgard: Cool, and for anyone that happens to be watching this, I just popped it up onto the screen where you can see exactly where that is, so that’s really cool. I learn new things every day.

Matt Mullenweg: Yeah, and so even this menu, like I’m looking at this menu right now. Do you have it open?

Brian Krogsgard: I do.

Matt Mullenweg: I want to talk through some things that could be really improved here. So for example, originally we didn’t have this descriptive text under each of these three views.

Brian Krogsgard: Mm-hmm (affirmative).

Matt Mullenweg: Well one, the text should be views, not view, and I think that there is, we can improve that text. Under editor, I don’t know if visual versus code is actually very intuitive, and two, under code editor, I think it’s a beautiful place to expose that you can actually go into the code editor on a per-block basis, so just a little bit of text there that says, “Hey, also per block you can go into this.” Manageable reusable blocks needs the square and the little pointy thing that shows that that’s going to take you out of Gutenberg, and I think it does open a new window.

Matt Mullenweg: And I think that we should put some sort of star or cool icon next to keyboard shortcuts, because once you learn those, you are off to the races. So just a good example that as far as we’ve come with Gutenberg, you can look at a single screen and immediately think of four or five things that are very improvable and that are certainly worth testing and getting out there.

Brian Krogsgard: Yeah, that’s neat.

Matt Mullenweg: I always joke I’m the unhappiest WordPress user in the world. It’s hard for me to look at anything in WordPress and not see all the things that could be made better, and just be terribly impatient to get them better as soon as possible.

Brian Krogsgard: So, speaking of impatient, you’re going to have to … Well, you might be able to work on some of these things at the same time but also there is a phase, a priority, and number three was about collaborative editing. For me, I think of this not even necessarily like me and you might collaborate on a post, but sometimes I want to collaborate with myself. My favorite tool from Automatic that you guys have built is probably Simplenote, because it’s like the only to-do app-ish thing, and it’s very unstructured, but it’s the only to-do app type of thing that I’ve ever really used in depth, because it’s really easy to open. It’s really easy to start writing, and it’s instantly on my phone. So for me, collaborative editing in some ways is just this simple process back and forth.

Matt Mullenweg: Across devices.

Brian Krogsgard: Yeah, across devices.

Matt Mullenweg: Totally.

Brian Krogsgard: Because I do a lot of stuff through my phone, but your collaborative editing is much more than just cross-device. It’s also cross-individual, and people building things together. Why do you think that’s an important thing to be in core WordPress experiences?

Matt Mullenweg: Hmm, that’s a good example of something that there’s not a bajillion people asking for right now. But just like post revisions, which is one of my favorite things I’ve forced to be in WordPress that I think is really fundamental to have the entire system works, this-

Brian Krogsgard: Yeah, a lot of people have been saved by revisions.

Matt Mullenweg: Yeah, I think this idea that when you’re editing in a post, the post is almost like an object and people from different devices, different things, can all come and be simultaneously working on that same object, is a mental model that is technically extraordinarily difficult. But if you get it right, it’s just a magical user experience. Even simple stuff, like do you remember when Netflix started saving where you’d watched up to across devices?

Brian Krogsgard: Mm-hmm (affirmative), yeah, that’s great.

Matt Mullenweg: Magical, and it’s so simple.

Brian Krogsgard: Yeah, I use that a good bit. We use that a good bit with our son, because the easiest way for him to be happy in a car is to have somebody’s phone. You can pull up Super Wings or whatever, right where he left off, so yeah, I do agree. And even when Google Docs came out with that, it was revolutionary in a way but people didn’t realize how much it would transform the way they write documents, so …

Matt Mullenweg: Totally, and we’ve got, the Web now supports technologies like WebRTC, that will perhaps enable us to do this even without centralized service, which is super cool, too. Because before, I was … Conspiracy theorists won’t believe this but I was actually really disappointed that it looked like the only way we could do this was in Jetpack. Now, it looks like we’ll actually be able to do this in a much more distributed fashion.

Brian Krogsgard: Interesting. Funny enough, I didn’t even think about that conspiracy theory and everything. As delightful as that sounds to think about, I didn’t consider the centralization aspect of it.

Matt Mullenweg: Yeah, so it’s definitely, there’s some stuff out there that’s possible. By the way, there might still be something where Jetpack can enhance it, or maybe we use Simperium, which is the engine behind Simplenote, to do something even fancier, but we can do a lot without that. But this also requires us to rethink our user flows around what versions, what it means to edit something. Because right now, you and I can kind of be on different paths, and we can save each other and merge over each other. And what is the relationship between what’s on the edit screen versus what’s live? That also is going to apply now to the entire site, so maybe what you and I are working on together is the new version of Post Status, and you’re changing the typography and I’m moving the widgets around and things like that, and then we’re setting that to go live at 12:00 pm on a Tuesday.

Brian Krogsgard: Yeah, that’s really cool. Another element of that that is a quirk in WordPress I guess, but you could publish a post and now I want to update it, but I don’t want to update it right now, but I want to save what I’ve updated.

Matt Mullenweg: Mm-hmm (affirmative).

Brian Krogsgard: Right now it’s either, it’s all about your current session. Once it’s published, you either update it or those changes are basically gone. You don’t kind of save a draft of an update, so a work flow like this would inherently basically have to solve a problem like that, so that would be nice.

Matt Mullenweg: Basically, we’re going to reimplement Git in the post-content table, in the WP Post table.

Brian Krogsgard: Yeah, that sounds like no problem.

Matt Mullenweg: Piece of cake.

Brian Krogsgard: Yeah, on that note, do you think there are underlying architectural changes that WordPress is going to have to go through to enable both this experience, because this is Gutenberg, but also I mean you’re probably faced with some of the problems that a tool like WooCommerce has in terms of scalability and being the right tool for the job for that next level of application. These aren’t blogs anymore, but we basically have the same data base, the same data base structure. You can extend it. You can change things, but do you think there’s rethinking that needs to be done in that regard?

Matt Mullenweg: Sure, and I actually think that [inaudible 01:04:12] is I think we have the opportunity to readdress and in a very backwards compatible way provide a path for people to upgrade some data structures, some things that have been hanging around for a while. An obvious one is widgets are a serialized array. Now we can move that to being JSON. There’s the native structure, data structure that Gutenberg uses behind the scenes. For some reason, we have to store this as like HTML plus comments, we can just store it in the native data format, which is pretty cool.

Matt Mullenweg: By the way, as we increase the MySQL version, we can actually query and get things out as JSON objects directly from MySQL. We don’t have to take them in and out of strings, so there’s just some clean-up, some fun stuff we can do. When we get higher PHP versions, we can name spacing doing different things. J-Trip’s been talking about doing some pretty cool composer stuff. All of this is, we’re getting the user part back on track and so that also means we can start to invest a lot more in that developer experience, which I think is crucial. Also I feel, I have a ton of empathy for, I actually for better or worse, I interact every day a lot more with developers than I do with users, so I really try to get out of my way to interact with users, but you can imagine the gripes and pains of developers is something that is more of my daily experience.

Brian Krogsgard: So we’ll have time to talk about all these phases over the next few years, but quickly what do you see in terms of the number of sites where having a multilingual setup, and this is around the focus of phase four, how often are you encountering Websites like that, and how much do you think that this being a part of the WordPress experience would be empowering for people to actually support more languages and more language versions of their site?

Matt Mullenweg: I think it would be a really big fundamental concept. The Web is global. English or single language is actually I think a small minority. People who speak one language is a small minority of the seven billion people in the world. This is obviously very prevalent in places like Quebec, where there’s officially French and English, and of course all over Europe. This is why I get the question every year for Camp Europe. I am monolingual, ashamedly so.

Brian Krogsgard: Yeah.

Matt Mullenweg: But the world is polyglots, and that’s why I named the mailing list WP Polyglots, not WP translate or WP anything, when I set that up almost 15 years ago now. Even for monolinguists like me, I got someone contacted me the other day saying, “Hey, can I translate this Gutenberg FAQ into Japanese? Do I have your permission to?” And they put it on a different site. How cool would it have been if I just could have said, “Hey, by the way, collaboration and work flow, here, you now have access to make this post into Japanese,” and now at the top it’ll have a little link to it, to the Japanese version, and there will be sort of a neural structure in a canonical place for the MA.TT version of the Gutenberg FAQ translated to Japanese by this volunteer, where anyone in the world could live. And by the way-

Brian Krogsgard: I was about to say, what if it was permissionless, like just if someone wants to make something on my site in other languages, do it. As small as Post Status is, I’ve had people that want to recreate the members side in Dutch or something.

Matt Mullenweg: Cool.

Brian Krogsgard: I’m like, I can’t do that, but that sounds amazing if you want to do that. But I’d be totally down if the structure was there for it to say, translate this post, and it’s almost like forking software, or almost the way language packs and plugins work. You don’t have to be responsible for every language pack if you’re the plug in author. Someone can just come and do it, and I think that’d be really cool for posts.

Matt Mullenweg: That would be so cool, and by the way, layer that in with other plugins. Layer that in with membership, so you only allow members to translate things, or layer that in with one I’d love to re-evaluate which is [Blickey 01:08:23]. So there is public revision history and sort of moderated submissions, so maybe I have, maybe my colleague [Nalco 01:08:34] can moderate Japanese translations, but maybe she doesn’t have time to translate every single one of my posts herself. But when people submit one, she could take a few minutes to just read it through and make sure they’re not having [crosstalk 01:08:47].

Brian Krogsgard: Yeah, translate my post and make it sound completely different.

Matt Mullenweg: Yeah, I think it’s actually WordPress.com.

Brian Krogsgard: Assuming good intent is part of the thing there.

Matt Mullenweg: Do you remember the Happy Birthday incident?

Brian Krogsgard: I don’t.

Matt Mullenweg: Someone, because when we opened up kind of like more totally community translations on WordPress.com and made it easy for anyone to do it, someone changed where it said comments, like leave a comment, into Happy Birthday! I forget what language it was, Italian, so all Italian sites under every single post would say Happy Birthday!

Brian Krogsgard: Just Happy Birthday!

Matt Mullenweg: Which I think is kind of like the most brilliant, if you’re going to troll or vandalize us, that was a really lovely way to do it.

Brian Krogsgard: Yeah, we could probably learn some things from Wikipedia’s own editorial flows and how to implement something like that. I do think that would be really neat. Do you think that still leaves room for other plugins that are doing various multilingual things? Does it leave room for them, or do you think it kind of eats them up and makes that business model go away? Because there’s been some good-sized businesses in that realm.

Matt Mullenweg: It leaves room for them 100%. In fact, I think it increases them a ton. Same thing with page builders. If you look at where the business model is for a lot of these translation plugins are going, they’re actually helping you do the translation. That makes total sense. If I’m a business, I might want my site in five languages. If I can click a button and just say, “Hey, I’ll pay you $1,000,” and by the way the plugins can be in the middle of that or there can sort of be an API for that. I mean, this is kind of incredible, but the downside of them is very similar to page builders, which is each kind of has its own way to do the data and the storage.

Matt Mullenweg: Some put it all in post content. Some put it in custom post type. Some put it in meta fields. Some put it in separate tables, so you essentially have actually each of the possible ways you could kind of logically do this exists. So now, if I’m building a plugin that wants to work with multilingual versions of the site, how do I do it? There’s no common foundation. Exact same issue we had with blocks. There were blocks on WordPress for years now, but every single visual composer and Beaver Builder and Elementor and Avada and Divi, they all did blocks in a different way.

Brian Krogsgard: Matt, there’s like 100 business questions I want to ask you but we’re over an hour already, so I will-

Matt Mullenweg: Can we take a few more minutes, like maybe wrap it in like, say 10?

Brian Krogsgard: Yeah, sure. If you’re down, I’m down.

Matt Mullenweg: You’re one of my favorite people to talk to.

Brian Krogsgard: Well, I appreciate it. I love talking to you as well, and I appreciate your openness.

Matt Mullenweg: Between you all, honestly you all and the Tavern folks, these are so much fun. I actually listen to a lot of these podcasts. It’s really enjoyable for me, so I appreciate you doing it. My ask of you for 2019 is, I’d love to see a bit most Post Status on the scene, you know?

Brian Krogsgard: Yeah, that’s a task for myself as well, so I did a relatively personal update recently.

Matt Mullenweg: I saw that.

Brian Krogsgard: One of the things that I’ve struggled with is I haven’t been in the thick of things in about four years, so I’m actually not spoiled, but I’m doing some part-time work actually being in WordPress, and back into doing stuff.

Matt Mullenweg: Cool.

Brian Krogsgard: It’s actually on the product side, not the service side. I’ve worked in an agency. This is going to give me a chance to do some part-time work on the product in SaaS side of things, so I’m excited about that. I know from history, when I’m working hard on something, whether it’s building my own site or working in the industry, it gives me much more to say, so I’m excited about being inspired by working within our space more, and within the experience more. Because it’s been four years of not doing that, and over those years I’ve tried to rely on other people to have a voice more as I felt like mine was fading. Kind of like what you were saying, you’re around developers all the time and not, like you want to be around more users. I was looking at the industry a lot, and not being in the industry I felt made it more difficult to have good things to say.

Matt Mullenweg: Although I would say the outside perspective is really valuable as well.

Brian Krogsgard: Yeah, I think at least for a season I need, it’ll be really beneficial for me.

Matt Mullenweg: I can’t wait to see, and by the way, as a member of the Post Status community, include us along for the ride. I’m sure after that personal update you got a ton of people contacting you [crosstalk 01:13:14].

Brian Krogsgard: I did, which I was very thankful for.

Matt Mullenweg: It’s one of those things, I think what was beautiful about that is you opened up about the struggle, not just about the good stuff. It’s really scary to be vulnerable like that, publicly. It was scary of me to put the things we learned and did wrong in the State of the Word, right? I just wanted to talk about all the good stuff, but it’s like it’s important for us to talk about what I messed up on. People help when they see that.

Brian Krogsgard: Yeah, that was very-

Matt Mullenweg: And I think the most valuable thing you built is like overall a pretty positive community that cares about WordPress deeply, so that’s awesome.

Brian Krogsgard: Yeah, and thank you, and I was very appreciative of the various responses that I got between feedback and ideas and job offers. But I’m excited to do some work within the space, and you know actually it did give me, it was beneficial because I got my head kind of out of the space a little bit, which I needed. I’ve been thinking about WordPress a whole lot since 2010, with basically no break, and I can’t imagine how you feel at times. But for me to still have a focus on WordPress but at least spend part of my week thinking about other things, doing other things, it gave me some personal benefits I think, and allowed me to look at WordPress things with a bigger picture. So I’m excited for 2019 and I think it’ll be a lot of fun. Now for you, just-

Matt Mullenweg: Well, I often tell people if you’re ever feeling not inspired or burnt out, go to a museum. Watch a show. All of my best ideas for WordPress have always come from the intersection of different fields, different areas, and I think that’s true of most great art, most great software, most great anything. So if you can get out there and keep, the WordPress stuff or whatever you’re working on will be in the back of your mind anyway, so if you can kind of focus on something else for a little while, actually really it’s fun.

Brian Krogsgard: It is.

Matt Mullenweg: I can’t wait to see what you do. As always, let me know if I can ever be of help.

Brian Krogsgard: Well, thank you very much. So a couple of business-y things. One is, what’s your biggest product right now, from an Automatic perspective? Are you guys seeing a lot of growth in the WooCommerce space, or is dot com still the main revenue driver? What are you seeing there?

Matt Mullenweg: Sure, let me just think through what I can say publicly.

Brian Krogsgard: When are you filing your S-1, Matt?

Matt Mullenweg: Yeah, we make the same joke in Automatic that they made at Apple, which is we’re a ship that leaks from the top.

Brian Krogsgard: Hey, I have to commend you, as someone who doesn’t like it but I can appreciate that this is the case. You guys are pretty good about being tight-lipped on the leaky boat side of things, so it’s a tight ship. I don’t get near as many of the leaks as I would like out of Automatic.

Matt Mullenweg: Well, I think a big part of that is just most of what we do is in the open. If you want to see the pricing tests we’re running on the new blogger and e-commerce plan that we just launched on WordPress.com, it’s in the Calypso GitHub so you can see which prices we’re charging which people, and how the test is going, and what percentage it’s going out to. Kind of, it’s all out there. WordPress.com is still the largest, and it’s still growing like a weed. I think in 2018 WooCommerce will actually grow faster in a year over year percentage, which is kind of what I started saying. We’re starting to see what I predicted when we actually first brought WooCommerce in, which is that the e-commerce opportunity has the potential to be bigger than all of the rest of Automatic’s businesses combined.

Brian Krogsgard: Yeah, what’s Shopify, like eight billion plus market cap, maybe 15? I don’t know. I think they doubled their size in 2018.

Matt Mullenweg: Yeah, market cap is just vagaries of the market, but revenue, they’ll be about a billion dollars this year. So I think it’s always good to look at kind of, when sort of comparing companies, look at the revenue not just the market cap.

Brian Krogsgard: Sure.

Matt Mullenweg: So they’ll be at a billion dollars and still growing at a really, really good rate. Now, the other reality is that nothing that we do is completely disconnected. A lot of the WooCommerce growth and increasing user experience is sort of amplified, I think, because we’ve been doing it in Jetpack, which is also amplified by running Jetpack code on WordPress.com and having that sort of stream of new users that are coming there, and so we see the problems that they’re having, and the struggles, or we build the infrastructure.

Matt Mullenweg: You asked about data structures earlier. I think one thing that we’ll start to see a lot more of in WordPress, and actually a very common feature of Jetpack that people don’t know about, that the Jetpack business plan, you can have full Elasticsearch version of your site. So there are certain use cases for which I don’t think MySQL is the best medium with which to address or query your data, and Elasticsearch is pretty much the cat’s meow. So the fact that we can in real time, create real time Elasticsearch indexes for every single Jetpack business site, which only costs $300 per year. Before that, it used to cost … Actually, I think VIP used to charge $5,000 or $10,000 a year for this, maybe even a couple grand a month, actually. Now we can do it for $300 per year.

Brian Krogsgard: Wow.

Matt Mullenweg: And that’s just one of the features in Jetpack Business. That’s in addition to the real time backup and the activity log and all the other things, the security restores. It just shows that we’re really surfing the outer edge of Moore’s Law, and I think that the stuff that we’re going to be able to do over the next few years is going to be pretty amazing, and I’m excited about Automatic. We also just moved DNS Perf, we moved back into second place for fastest DNS service, so by the way, way ahead of Amazon, way ahead of Google, and second only to Cloudflare, which Automatic’s network is tiny but mighty. Cloudflare invests I think over 100 million dollars per year in capex, building out their data centers in their kind of points of presence. We’ve reached a number two performance ranking with a fraction of that investment, so very proud of that team, very proud of all the folks at Automatic that are really building this out. By the way, then that benefits all the users of Jetpack Photon, the CDN, just so much cool stuff happening.

Brian Krogsgard: That’s awesome. I heard recently that you all have also been able to lower some of your prices for VIP as you’re deploying like VIP Go and some of that stuff with scalable Websites. Back when I had my hands in a few VIP sites I think the lowest pricing back then was maybe $3,000 to $4,000 a month, and now you can do it as low as $1,000 a month and you all provide a lot for that, so that’s impressive.

Matt Mullenweg: That sounds about right, yeah. I’m not up on the latest there, but fundamentally my business philosophy is to get the best stuff in the hands of as many users for as low a price as possible, and we’re just relentless in kind of cutting the costs, bringing things down, trying to leverage the best and newest technology to do so.

Brian Krogsgard: How are you attacking the very high end, so that a store that may grow up on WooCommerce doesn’t feel like they have to leave WooCommerce once it hits a certain scale? One of the things that I feel like people have been, I’ve been hearing from consultants especially, is that they get to a certain size and then they’re really struggling with WooCommerce, and then something like Shopify ends up being the answer. How is WooCommerce going to compete in that realm to be the platform for Macy’s or who knows what? Some big company with lots of orders and lots of stuff, so that you can keep them throughout the life cycle?

Matt Mullenweg: Yeah, I think my take on that problem, because ultimately what we want to do is be more scalable in Shopify and also a better user experience, and right now I would say they’re ahead in both. There hasn’t been as good a feedback loop. The thing that made WordPress so scalable was there was a tight feedback loop between the host, the agencies building the biggest sites, WordPress.com itself being a big site, and the core development. So that meant that when we had bottlenecks, we were able to solve them often in core in ways that were ultra scalable in Webscale.

Matt Mullenweg: WordPress.com is on its own one of the largest sites on the Internet, so that’s the same software that you can download and use, which is kind of wild. For WooCommerce, that loop isn’t as strong so one of the things I’ve been encouraging the team to try to do myself is get a tighter loop between the host and the people building the big sites and the WooCommerce core team, so that they can figure out versus having five different plugins that try to address the scalability in different and often subpar ways, really get that built into core, with the sort of Web scale, knowing everything we’ve known in 15 years of building WordPress, what’s going to make it so it can scale to thousands of orders per second, hundreds of millions of rows.

Brian Krogsgard: Two more questions, real quick.

Matt Mullenweg: We can do so, by the way. It’s a very tractable problem. We will solve that. Solving that is something that will happen within the next six to 18 months. Solving the user experience to catch up with Shopify is also improving the user experience, or BigCommerce rather, I think will take longer. That’s more of a five to 10 year goal.

Brian Krogsgard: I personally think that gives both the WordPress ecosystem, the WooCommerce ecosystem and Automatic directly a massive value proposition, if that can be accomplished. I think WordPress now people, you never feel like you have to leave WordPress because you got too big.

Matt Mullenweg: Yeah.

Brian Krogsgard: And as that can be accomplished, and that was a massive accomplishment for WordPress. For a long time that wasn’t true, and now that, if that can be done on the e-commerce side of things, or commerce broadly not just necessarily WooCommerce, I think that will be fantastic for everybody involved.

Matt Mullenweg: By the way, I just want to point that out, just to pause. Think how little, how many other examples of software you can think of that the consumer version also works when you run it at an industrial global scale?

Brian Krogsgard: I have no idea. I’m not very-

Matt Mullenweg: It’s not very common. I think it’s one of the things the WordPress community should really be proud of, because that is highly unusual. And as we’re one of the only ultra-successful consumer open source startups, projects, communities, whatever, I think pointing to that sort of scalability is a big thing as well.

Brian Krogsgard: So, one question is Automatic has investors. We just saw Slack, Lyft and Uber all file for becoming public companies. When I think, what’s the option for Automatic, one of however many successful startups where you have investors, they know you’re a successful startup. They know that there’s opportunity for them to succeed in that. That’s long-term revenue stream, remaining a private company. It’s private equity. It’s going public, or it’s acquisition. Do you have any thoughts in terms of what makes you happiest as a company and as a business owner, and what do you think is best for the way Automatic interfaces with the broader WordPress community?

Matt Mullenweg: It’s hard for me to imagine being a public company CEO, any harder than leading an open source project.

Brian Krogsgard: I’ve thought about that a great deal. I think you actually fit the mold for what Wall Street might like in terms of the leader of a public company. I will say, that’s my bet. My best is one day Automatic would go public, and we figure out how that works in terms of all the private, public components and the open source side of things. But yeah, I’m curious-

Matt Mullenweg: I think it’s actually a possibility. By the way, I could see other WordPress companies going public, probably WPEngine is the closest to the gates there.

Brian Krogsgard: Well good, GoDaddy and EIG are public.

Matt Mullenweg: They are, yeah, so there will be other open source WordPress either based or WordPress will be a part of their business public companies, likely before Automatic as well. I think that’s a great path for us. Automatic has investors. They are minority investors, so the sort of existential future of the company is in the hand of myself and the other people who own the majority of the shares of Automatic. I think there’s lots of options. The people you point to, Uber or Lyft, Slack, et cetera, to varying degrees have built some pretty impressive things. I admire some more than others, but also have reached a scale that’s kind of far beyond where companies generally go public.

Brian Krogsgard: Yeah, they really have. It’s been-

Matt Mullenweg: What that illustrates is that the private market is actually a lot more liquid and has a lot more capital available for when and how that needs the company or the ecosystem or whatever to grow.

Brian Krogsgard: So I could surmise from that that you don’t feel like there’s a rush?

Matt Mullenweg: I won’t even speak to my own personal things, but say just in the industry there’s less of a rush, so that is the plus and minus of so much capital moving from the public markets into the private markets. So people like Fidelity, T. Rowe Price et cetera that used to only do public companies now invest in private companies. That’s great for the companies, because by the way as a private company, you don’t have the kind of quarterly scrutiny that you do when you’re public, and I think it’s actually easier to out-innovate and out-flank public companies when you are private, which is one thing I personally like. But that said, it does keep more of that growth in the hands of only sophisticated investors.

Brian Krogsgard: I completely agree.

Matt Mullenweg: So there is a lot more of that upside that is no longer in the hands of what is commonly referred to as the retail investor. I would love for anyone who loves Automatic’s products to be able to own a share of the company, even if it’s just one share. That’s not really possible under the current sort of regulatory frameworks, and for good reasons, by the way. As we saw with the kind of ICO craze, there’s a reason all these protections for consumers and public market, public company standards exist.

Matt Mullenweg: But in the meantime, at Automatic we will continue to hold ourselves to public company standards, but really build in an extremely long-term way. If there’s an idol there, I’d say it’s Amazon, and try to make the best possible user experience, best possible products. If we continue to do that, I think from a business point of view we will have an array of options available to us and any number of choices.

Brian Krogsgard: And as a leader yourself of the WordPress community and Automatic, what’s one big thing that you learned this year that you hope to improve upon in 2019?

Matt Mullenweg: Hmm, I know you’re probably thinking about like a big thing, but I’m actually going to say a small thing.

Brian Krogsgard: It can be small.

Matt Mullenweg: It’s really important, which is how much you can … What is the one thing everyone listening to this is doing right now?

Brian Krogsgard: Focusing, I hope?

Matt Mullenweg: Breathing.

Brian Krogsgard: Oh, okay.

Matt Mullenweg: And you probably weren’t thinking about it, but now you are thinking about it. You’re breathing right now.

Brian Krogsgard: I am.

Matt Mullenweg: And it is amazing how much you can influence your mindset, your state of mind, your mood, your everything, through breath. Just as an exercise, where everyone puts their hand on their belly and takes a big breath and pushes your hand out as you take it in, Brian, are you doing it?

Brian Krogsgard: Oh, sorry. I do. I feel good.

Matt Mullenweg: It has an immediate effect on you.

Brian Krogsgard: It does. You know, actually that’s how we discipline our son often. A three-year-old is a very emotional being, so if they’re upset one of the first things that you can do with them is just tell them, “Let’s take a deep breath together.” So you take that deep breath and the response is also very immediate, the way they calm down and settle down and think more clearly because they took that breath, so that’s interesting.

Matt Mullenweg: That’s all of us, and also by the way, this is not something new. This goes back thousands of years.

Brian Krogsgard: You didn’t just invent this?

Matt Mullenweg: No, no, you know there’s so many, there’s so much prior art here, but I’d encourage people to check it out. Also check out, when the videos go up, the Joanna Barsh talk, and Alexis Lloyd both had sort of almost like guided meditations and exercises. I think this is one of the next big areas for people who aren’t familiar with to discover. They’re actually really, really powerful, and it’s been huge for me. In an extraordinarily busy and what might otherwise be seen as extremely stressful year, it was actually one of my best years of my life.

Brian Krogsgard: Awesome.

Matt Mullenweg: I do have to watch a clock, and I do have to run now.

Brian Krogsgard: That’s fine. I’m happy to hear that. Thank you for spending so much time with me. It was great talking to you, and we’ll catch everybody next time.

Matt Mullenweg: Thank you. I’ll see you all, and thank you to all Post Status readers.

by Brian Krogsgard at December 12, 2018 02:45 PM under Planet

December 11, 2018

WPTavern: State of the Word 2018: WordPress Embraces the Block Editor

photo credit: WP Tavern

WordCamp US kicked off in Nashville over the weekend, following the release of WordPress 5.0. In the first 48 hours, 5.0 had been downloaded more than 2.8 million times. It passed 3 million Saturday night.

“There’s been a lot that’s been going on, so I’d like to allow WordPress the chance to re-introduce itself,” Matt Mullenweg said during the preamble of his State of the Word address. He invoked the four freedoms as the project’s constitution and called the community back to its roots.

“It’s the reason we’re here,” Mullenweg said. “WordPress isn’t a physical thing; it’s not a set of code. It’s kind of an idea. WordPress is backed by the full faith and credit of every person and company that depends on it.”

He reiterated the project’s mission to democratize publishing and recast his vision for advancing the open web.

“Like I said a few years ago, we’re building a web operating system, an operating system for the open, independent web and a platform that others can truly build on,” Mullenweg said.

WordPress’ 32.5% market share and its commercial ecosystem, which Mullenweg estimates at $10 billion/year, give the project the resources to make a powerful impact on the future of the web.

Mullenweg Builds a Compelling Case for the Block Editor

photo credit: WCUS Photography Team

Mullenweg drove home the necessity of Gutenberg by showing a selection of videos where new users struggled to accomplish simple tasks in the old editor. Their experiences were accompanied by painful commentary:

  • “This feels like writing a blog back in 2005.”
  • “This was very finnicky; this does not work.”
  • “How would I add a caption? I have no clue.”

Mullenweg described how he used to effortlessly switch back and forth between the visual and HTML editors prior to WordPress 5.0 but realized that not all users are able to do this.

”This has been our editor experience for over a decade now and many of us have learned to deal with it,” he said.

He followed up with a video demonstrating how much easier these tasks are in the new block editor and identified blocks as the way forward for WordPress.

Some attendees commented after the fact on how the user testing videos, paired up against an expert using Gutenberg, seemed unbalanced and they would have liked to see videos of new users attempting the same tasks in the new editor. The goal of that segment, however, seemed to be more aimed at communicating the need for Gutenberg and the possibilities it opens up once users have had the chance to grow into it.

Mullenweg Urges Attendees to “Learn Blocks Deeply”

Millions of early adopters have already embraced the block editor during phase 1 of the Gutenberg project, which closed out with 1.2 million active installs and 1.2 million posts written. There have already been 277 WordCamp talks on Gutenberg, 555 meetup events focused on the new editor, and more than 1,000 blog posts discussing it.

Blocks are taking over the world of WordPress. Version 5.0 shipped with 70 native blocks and there are already more than 100 third-party blocks in existence and 1,000 configurations related to that.

“Blocks are predictable, tactile, and can be simple like a text block, or as rich as an e-commerce interface,” Mullenweg said. He described them as the new DNA of WordPress, from which users can create anything they can imagine.

Mullenweg showcased two sites built using the block editor, the Indigo Mill and Lumina Solar. These beautiful sites open the imagination to what Gutenberg is capable of bringing to websites.

WordPress.org will be highlighting plugins and themes to push the block ecosystem forward. There are also more than 100 Gutenberg-ready themes available to users on the directory and a new Gutenberg block tag that is currently live for plugins. It will also be available for themes soon.

Mullenweg highlighted tools like the create-guten-block toolkit, Block Lab, and Lazy Blocks that are making it easy for developers to create their own blocks. Block collections and libraries are also emerging. He said one of the priorities for 2019 is to build a WordPress.org directory for discovering blocks and a way to seamlessly install them.

Building on the homework he gave to WordPress developers in 2015, to “Learn JavaScript Deeply,” Mullenweg urged the community to “Learn Blocks Deeply.” Blocks provide a host of opportunities to improve the user experience beyond what Gutenberg’s creators could have imagined in the beginning.

Gutenberg Phase 2: Navigation Menu Block, Widget blocks, Theme Content Areas

Mullenweg announced the next phases for the Gutenberg project. Phase 2 has already begun and focuses on site customization, expanding the block interface to other aspects of content management. This includes creating a navigation menu block. Reimagining menus is will be challenging, and Mullenweg said they may even get renamed during the process.

Phase 2 goals also include porting all widgets over to blocks and registering theme content areas in Gutenberg. An early version of phase 2 will be in the Gutenberg plugin so anyone wanting to be part of testing can reactivate it.

During the Q&A time, one attendee asked a question about how this phase seems to include very little about making layout capabilities more robust. He asked if Mullenweg plans to let those the marketplace handle those layout decision or if core will define a layout language. Mullenweg responded that it may be more prudent to see what others in the ecosystem are doing and cherry pick and adopt the best solutions. He also remarked that it would be exciting if users could switch between different page builders in the future and not lose their content.

Gutenberg Phases 3 and 4: Collaboration and Core Support for Multilingual Sites

Mullenweg announced that Gutenberg phase 3, targeted for 2020, will focus on collaboration, multi-user editing, and workflows. Phase 4 (2020+) is aimed at developing an official way for WordPress to support multilingual sites. When asked what that will look like from a technical standpoint, given the many existing solutions already available, Mullenweg said he didn’t want to prescribe anything yet, as it’s still in the experimental stage.

Other major announcements included a highly anticipated bump in the minimum PHP version required for using WordPress. By April 2019, PHP 5.6 will be the minimum PHP version for WordPress, and by December 2019, the requirement will be updated to PHP 7.

WordPress releases are going to come faster in the future, as Gutenberg development has set a new pace for iteration. Mullenweg said he would like WordPress to get to the point where users are not thinking about what version they are on but instead choose a channel where they can easily run betas or the stable version.

Mullenweg Acknowledges Mistakes Made and Lessons Learned in the 5.0 Release Process

WordPress 5.0 was one of the longest and most controversial release cycles in the project’s history. Those outside the inner circle of decision-making endured a great deal of uncertainty, as dates were announced and then missed, with secondary dates thrown out in favor of pushing 5.0 out with just three days’ notice.

“We were scared to announce a new release date after missing our previous one,” Mullenweg said, acknowledging the controversial release date. He said this seemed to create a lot of fear and uncertainty until they announced a new date. The dates seemed to come out of the blue and were stressful for the community.

Mullenweg highlighted the lessons they learned in the process of releasing 5.0:

  • Need the various teams across WordPress working together better
  • Need to keep learning JavaScript, even more deeply
  • Importance of triage and code freezes
  • Always announce release dates

Mullenweg noted that WordPress 5.0’s beta releases were tested 100 times more than other releases, which he said contributed to Gutenberg becoming more robust before landing in 5.0. However, these positives seemed to be overshadowed by several critical breakdowns in communication that many feel betrayed the community’s trust.

He noted that people used the plugin review system as a way to vote on Gutenberg and that perhaps the community needs a different medium for expressing those kinds of things. Users did this because they felt it was one of the only feedback mechanisms where they had a voice. Negative reviews piled on in the early days of the plugin’s development but they continued steadily throughout the feature plugin’s journey into core. After 5.0 was released, negative reviews on the Gutenberg plugin have continued to pour in, and its rating has fallen to 2.2/5 stars.

Growing Pains and a Call for Transparency

photo credit: David Bisset for Post Status

Mullenweg said that Gutenberg development happened entirely in the public eye, surfacing many challenges associated with developing open source software in public. The code was public, but the most important decisions were made behind closed doors. This was compounded by the developer community voicing frustrations during core dev chats and on social media.

During the Q&A segment, several audience members called for more transparency in the release process, noting that most of the posts and announcements regarding 5.0 came from Automattic employees. Morten Rand-Hendriksen, who has become somewhat of a community firebrand at WordCamp Q&A’s, received applause for his question regarding the use of the word “we” in connection to posts on the make blogs. He pressed Mullenweg for more insight into where these decisions are made.

Mullenweg said the “we” he meant in regards to 5.0 release dates referred to a private channel where the release leads discussed it. He said with so many people showing up to the dev chats, the discussions became difficult.

“I don’t just go in a cave and come up with these things,” Mullenweg said. “A lot of people were showing up [to dev chats] who had never contributed to WordPress before and were crowding out the discussion of the core team.” He also said the private conversations were “every bit as feisty as the public one,” except there weren’t any drive-by opinions.

To those on the outside, these meetings appeared to be secret, as they were never referenced or summarized on the make blogs. This left the developer community wondering where these decisions were coming from and whether or not they had a voice.

During the Q&A, Mulllenweg said he listened to vigorous discussion and diverse viewpoints from release leads coming from different companies, while gathering as much information as possible from reading reviews, blog posts, and comments from the community. He described this process as part of the art of trying to make sense of all the different things people are saying and balance that.

Supporting a BDFL-led project requires a certain amount of trust that the leadership is listening. Over the past several weeks Mullenweg has made a strong effort to keep the channels of communication open.

The painful user testing videos Mullenweg shared demonstrated how desperately WordPress needed to grow out of its old editor. It isn’t often that core makes changes that affect nearly every corner of the WordPress ecosystem at the same time. This experience came with its fair share of growing pains. Despite communication missteps during the 5.0 release process, Mullenweg has successfully navigated the project through this rocky transition. Although WordCamp US attendees seemed road weary after 5.0, they were united by a shared desire to move forward and continue working together with the leadership that has kept WordPress on the course of growth and improvement for the past 15 years.

by Sarah Gooding at December 11, 2018 04:23 PM under wordcamp us

Matt: State of the Word 2018

Over the weekend I was in Nashville with over a thousand other WordPress enthusiasts. I met a ton of people, learned a lot, and was able to share the annual State of the Word address with the audience, which is a big summary of what WordPress has been up to and where it’s going. This year we covered user testing, Gutenberg, 5.0, the future phases of Gutenberg, all the latest and greatest blocks, new minimum PHP requirements, the adoption of 5.0, and some event and community updates. You can also see just the slides. The Q&A is here in a separate video.

If you’d like a text summary and commentary on the speech, Post Status and WP Tavern both have good write-ups.

by Matt at December 11, 2018 05:00 AM under Asides

December 10, 2018

Post Status: Matt Mullenweg’s State of The Word, 2018

Matt started by “reintroducing WordPress” and the four freedoms, stressing that “WordPress isn’t a physical thing or code, it’s an idea.” Additionally, a “robust commercial ecosystem” supports WordPress, and Matt noted that current estimates indicate WordPress generates about $10 Billion (USD) annually.

After two years of development and just after WordPress 5.0 officially launched, it’s not surprising the focus of Matt’s talk was on Gutenberg. “We’ve gotten a lot of questions about why we are doing certain things… why we are working on Gutenberg. And it’s good to return to users to find that,” Matt acknowledged.

Enhancing editor usability

A video of new WordPress users testing the classic editor (WordPress 4.9) was shown projected on the big screens over the stage. These clips primarily showed people having difficulties with relatively simple tasks in the editor.

Matt’s point was that we’ve become accustomed to the custom editor’s quirks, but blocks offer a better experience — from copying and pasting from Microsoft Word and Google Docs into WordPress to quickly creating a responsive website.

Community Gutenberg adoption

Matt continued with a summary of how Gutenberg has performed in Phase 1 of its release. Before the WordPress 5.0 release, 1.2 million active installs and 1.2 million posts were published, with about 39,000 posts written daily. Phase 1 had 8,684 commits and over 340 contributors. The ‘Gutenberg’ tag is already available for plugins in the WordPress repo, and it will be “coming soon” for themes.

Notably, over 100 Gutenberg themes are already present in the WordPress repo — including the new Twenty Nineteen theme. Matt highlighted two websites — The Indigo Mill and Lumina Solar — as examples where Gutenberg blocks have been used well to create effective layouts. Matt riffed on the “Learn JavaScript Deeply” mantra by repeating “Learn Blocks Deeply.” Blocks are the DNA of the new editor. Currently, 70 native blocks and over 100 third-party blocks exist for Gutenberg.

Community Gutenberg development

He highlighted some of the third party blocks in the wild:

Matt mentioned several block libraries and frameworks that have appeared:

Mobile Apps

Matt gave the audience an update regarding the WordPress native mobile apps: In the past month, app users published 1.3M posts and uploaded 3.1M photos and videos. Gutenberg will be going into the mobile apps, with a beta release expected in February 2019; I heard February 22nd is the current target date for a beta release.

The Next Phases of Gutenberg

Matt highlighted the next phases of Gutenberg’s evolution, which included new information about Phases Three and Four:

Phase One

Fundamental blocks for writing and editing in the backend editor. These are complete now, although Matt later said that work on the editor would continue.

Phase Two

Customizing outside of the page/post content will be the next point of emphasis. It may include widgets, menus, and miscellaneous content. Matt notes that menus “will need a bit more experimentation”. “2019”.

Phase Three

Collaboration, multi-user editing in Gutenberg, and workflows. The target for this to phase to be complete is “2020+.”

Phase Four

“An official way” for WordPress to support multilingual sites. Also slated for “2020+.”

Other Announcements

There were several non-Gutenberg tidbits of note:

Auto updates on major versions of WordPress

On a list of items to work on in 2019, Matt said he wanted to make it a goal to add optional auto-updates for plugins, themes, and major versions of WordPress.

Updated minimum PHP versions

A proposal written by Gary Pendergast makes a case for WordPress to start updating its minimum PHP versions. The proposed plan is to move to PHP 5.6 by April 2019 and to PHP 7.0 by “as early as” December 2019. Notably, security support for PHP 5.6 expires in a few days, and the “end of life” for PHP 7.0 just passed.

After Matt mentioned this proposal, it received an enormous amount of applause — far more applause than most of the Gutenberg news that came earlier, and Matt noticed. It is definitely welcome news!

WordPress release adoption

During the life of the WordPress 4.9 branch, there were over 173 million downloads with 68.4% of all known WordPress installs running 4.9.

Matt notes that the early adoption numbers for WordPress 5.0 were very similar to WordPress 4.7, which was also a December release back in 2016.

Lessons learned in 2018

Matt took time to summarize the lessons he learned in 2018, starting with the need for teams to improve how they work together: “There should be no reason for accessibility, testing, and other teams not to be working together since these features should be a feature of everything we develop from the very beginning.” No doubt this came as a response to the concerns about accessibility in Gutenberg that surfaced before WordPress 5.0 was released.

Community Update

Matt offered some community-related data as well:

  • WordCamps: In 2018 there were 145 WordCamps in 48 countries, with over 45,000 tickets sold. A total of 1,300 organizers (a 33% increase!), 2,651 speakers, and 1,175 sponsors made it all possible.
  • Meetups: This year saw 50% member growth in meetup attendance, with over 687 meetup groups and 5,400 meetup events.

And with that, he began Q&A.

You can view the State of the Word on YouTube in full, and it should become available on WordPress TV very soon.

Photos by Brian Richards, for Post Status.

by David Bisset at December 10, 2018 03:45 PM under WordPress Core

December 07, 2018

WPTavern: AMP Plugin for WordPress Version 1.0 Introduces Gutenberg-Integrated AMP Validation

Version 1.0 of the official AMP plugin for WordPress was released on the eve of WordCamp US, after two years in development by contributors from Automattic, XWP, and Google. This first stable version has a massive changelog with 30 people credited for their contributions. The plugin is now considered ready for production and is active on more than 300,000 sites.

Version 1.0 interfaces with the new editor that landed in WordPress 5.0. It will display warnings for AMP-invalid markup on a per-block basis, so users don’t have to guess what content is generating an issue.

This release also introduces a compatibility tool that offers detailed information on AMP validation errors. It functions like a debugging page where users can see which URLs are generating errors, along with the site component (plugin, theme, or core) where the markup originates.

Version 1.0 includes granular controls for selecting which templates will be served as AMP. This allows for a more gradual adoption across a site. Users can also opt for Native mode to have the entire site served as AMP.

The plugin has been updated to support four of WordPress’ default themes, including Twenty Fifteen, Twenty Sixteen, Twenty Seventeen, and Twenty Nineteen. The documentation for how AMP was added to these bundled themes serves as an example for how theme developers can make their own themes AMP-compatible.

WordPress users who opt to use AMP on their sites will have a more successful experience with this version, thanks to the improved UI for handling AMP validation errors and the new interface for limiting AMP-support to certain templates.

The AMP for WordPress project is also sporting a new website that features a collection of AMP-ready plugins and themes and a showcase of sites using AMP. It also has extensive documentation for implementors, site owners, and developers. The site provides a central place for news and resources related to the project and its expanding ecosystem of compatible extensions.

by Sarah Gooding at December 07, 2018 06:51 AM under amp

December 06, 2018

WPTavern: WordPress 5.0 “Bebo” Released, Lays A Foundation for the Platform’s Future

In 2016 at WordCamp US in Philadelphia, PA, Matt Mullenweg announced to the world that a new post and page editor would be coming to WordPress. “The editor does not represent the core of WordPress publishing,” Mullenweg said.

His vision of the editor was geared towards a more block-based approach that unifies widgets, shortcodes, and other areas of WordPress. Today, that vision has become a reality with the release of WordPress 5.0 featuring project Gutenberg.

The New Editor in WordPress 5.0

Instead of a large blank canvas, content is broken up into a series of individual blocks that are independent from the content as a whole. For example, you can edit the HTML of one block without it affecting other blocks.

The editor comes with more than 16 blocks to add content. You can add more blocks by installing and activating plugins.

Some of the Blocks That Are Available in WordPress 5.0

Each block typically has two areas where you can manipulate its content. The Toolbar, which displays when hovering over a block, and the Inspector located in the right-hand sidebar. The Inspector houses less-often used settings that require more screen space.

Between the top toolbar, block toolbar, inspector, block mover, and hidden elements that don’t appear unless hovered over, there are a lot of user interface buttons. I suggest spending time crafting a test post to get familiar with what each button does.

To see the new editor in action, check out the following demo video.

A Short Demo of The New Editor in Action

If you’re not ready for the new editor or discover incompatibilities with themes or plugins, you can install the Classic Editor plugin. This plugin will disable the new editor and replace it with the one in WordPress 4.9.8 and below. The WordPress development team has committed to supporting the plugin until December 31st, 2021.

Those who use assistive technology and experience accessibility issues with the new editor are encouraged to install the Classic Editor plugin until the issues are fixed.

Twenty Nineteen: A Fully Compatible Default Theme

WordPress 5.0 comes with a new default theme called Twenty Nineteen that is fully compatible with the new editor. It includes front-end and back-end styles to provide a What You See Is What You Get experience. It also supports the Wide and Full image alignment options.

Twenty Nineteen Front-End on the Left, Back-End on the Right

You can see the theme in action on Matt Mullenweg’s site.

What Happens to Existing Content?

Content not created in the new editor is placed into a Classic block. This block mimics the old editor and provides users a choice to migrate it into blocks. However, migrating content into blocks is not required. Most content shouldn’t be affected by updating to WordPress 5.0.

Where to Get Help Using the New Editor

For new users, the editor might be an intuitive experience but for many WordPress veterans, it introduces a steep learning curve. After all, the previous editor has existed for more than 10 years.

At the moment, there is a Gutenberg handbook for Developers and Contributors but not for Users. Work is underway by the Docs team and other volunteer contributors to put together an initial document to release in 2019.

Until the official handbook is published, you’ll need to seek help and education elsewhere.

WordPress 5.0 Essential Training

Morten Rand-Hendriksen, an educator for LinkedIn Learning has published a course that walks users through the new editor. It’s available to view for free for the next three weeks.

Gutenberg Times

Birgit Pauli-Haack has been keeping tabs on Gutenberg’s development for more than a year. Gutenberg Times contains relevant information about the editor for users and developers.

WordPress Support Forums

Volunteers are standing by ready to answer your questions. If you think you’ve discovered a bug, incompatibility, or are experiencing trouble with the new editor, please post it in the support forums.

WordPress 5.0 Field Guide

The WordPress 5.0 field guide provides important links and information for developers and users related to this release.

WordPress 5.0 Is the Beginning of A New Journey

While WordPress 5.0 introduces a new editor, it also lays the foundation for what’s to come. The first phase of project Gutenberg was the editor. The second phase is the Customizer with a focus on full-site layouts. The third and fourth phases will be shared and discussed by Mullenweg at this year’s WordCamp US.

The new editor is part of a long process to reinvent WordPress. Matías Ventura, Co-lead of the Gutenberg project succinctly explains why the need for Gutenberg exists.

WordPress has always been about the user experience, and that needs to continue to evolve under newer demands. Gutenberg is an attempt at fundamentally addressing those needs, based on the idea of content blocks. It’s an attempt to improve how users interact with their content in a fundamentally visual way, while at the same time giving developers the tools to create more fulfilling experiences for the people they are helping.

How can such a vision happen without dismantling, rebuilding, fragmenting, or breaking the WordPress ship that for over a decade has been carrying the thoughts, joys, and livelihoods of millions of people and more than a quarter of the web?

The ship, like Theseus’, needs to continue sailing while we upgrade the materials that make it. It needs to adapt to welcome new people, those that find it too rough to climb on board, too slippery a surface, too unwelcoming a sight, while retaining its essence of liberty. This is not an easy challenge—not in the slightest.

Indeed, we called it Gutenberg for a reason, for both its challenges and opportunities, for what it can represent in terms of continuity and change. It is an ambitious project and it needs the whole WordPress community to succeed.

Matías Ventura, Co-lead of the Gutenberg project.

As the new editor makes its way across the world, it will be interesting to see what the reactions are from users who experience it for the first time. It will also be interesting to see what the developer community builds that takes the editor to new heights.

WordPress 5.0 is the beginning of a new journey for the project. One that will have bumpy roads, new discoveries, and plenty of opportunities to learn. So saddle up and keep your hands and arms inside the vehicle until it makes a complete stop.

WordPress 5.0 is named after Bebo Valdés who was a Cuban pianist, bandleader, composer and arranger. The release was led by Matt Mullenweg with Allan Cole, Anthony Burchell, Gary Pendergast, Josepha Haden Chomphosy, Laurel Fulford, Omar Reiss, Daniel Bachhuber, Matías Ventura, Miguel Fonseca, Tammie Lister, Matthew Riley MacPherson as co-leads. At least 423 people contributed to the release.

by Jeff Chandler at December 06, 2018 09:38 PM under WordPress 5.0

Dev Blog: WordPress 5.0 “Bebo”

Say Hello to the New Editor

We’ve made some big upgrades to the editor. Our new block-based editor is the first step toward an exciting new future with a streamlined editing experience across your site. You’ll have more flexibility with how content is displayed, whether you are building your first site, revamping your blog, or write code for a living.

Building with Blocks

The new block-based editor won’t change the way any of your content looks to your visitors. What it will do is let you insert any type of multimedia in a snap and rearrange to your heart’s content. Each piece of content will be in its own block; a distinct wrapper for easy maneuvering. If you’re more of an HTML and CSS sort of person, then the blocks won’t stand in your way. WordPress is here to simplify the process, not the outcome.

We have tons of blocks available by default, and more get added by the community every day. Here are a few of the blocks to help you get started:

Freedom to Build, Freedom to Write

This new editing experience provides a more consistent treatment of design as well as content. If you’re building client sites, you can create reusable blocks. This lets your clients add new content anytime, while still maintaining a consistent look and feel.


A Stunning New Default Theme

Introducing Twenty Nineteen, a new default theme that shows off the power of the new editor.

Designed for the block editor

Twenty Nineteen features custom styles for the blocks available by default in 5.0. It makes extensive use of editor styles throughout the theme. That way, what you create in your content editor is what you see on the front of your site.

Simple, type-driven layout

Featuring ample whitespace, and modern sans-serif headlines paired with classic serif body text, Twenty Nineteen is built to be beautiful on the go. It uses system fonts to increase loading speed. No more long waits on slow networks!

Versatile design for all sites

Twenty Nineteen is designed to work for a wide variety of use cases. Whether you’re running a photo blog, launching a new business, or supporting a non-profit, Twenty Nineteen is flexible enough to fit your needs.


Developer Happiness

Protect

Blocks provide a comfortable way for users to change content directly, while also ensuring the content structure cannot be easily disturbed by accidental code edits. This allows the developer to control the output, building polished and semantic markup that is preserved through edits and not easily broken.

Compose

Take advantage of a wide collection of APIs and interface components to easily create blocks with intuitive controls for your clients. Utilizing these components not only speeds up development work but also provide a more consistent, usable, and accessible interface to all users.

Create

The new block paradigm opens up a path of exploration and imagination when it comes to solving user needs. With the unified block insertion flow, it’s easier for your clients and customers to find and use blocks for all types of content. Developers can focus on executing their vision and providing rich editing experiences, rather than fussing with difficult APIs.


Keep it Classic

Prefer to stick with the familiar Classic Editor? No problem! Support for the Classic Editor plugin will remain in WordPress through 2021.

The Classic Editor plugin restores the previous WordPress editor and the Edit Post screen. It lets you keep using plugins that extend it, add old-style meta boxes, or otherwise depend on the previous editor. To install, visit your plugins page and click the “Install Now” button next to “Classic Editor”. After the plugin finishes installing, click “Activate”. That’s it!

Note to users of assistive technology: if you experience usability issues with the block editor, we recommend you continue to use the Classic Editor.

This release is named in homage to the pioneering Cuban jazz musician Bebo Valdés.


The Squad

This release was led by Matt Mullenweg, along with co-leads Allan Cole, Anthony Burchell, Gary Pendergast, Josepha Haden Chomphosy, Laurel Fulford, Omar Reiss, Daniel Bachhuber, Matías Ventura, Miguel Fonseca, Tammie Lister, Matthew Riley MacPherson. They were ably assisted by the following fabulous folks. There were 423 contributors with props in this release. Pull up some Bebo Valdés on your music service of choice, and check out some of their profiles:

Aaron Jorbin, Abdul Wahab, Abdullah Ramzan, Abhijit Rakas, Adam Silverstein, afraithe, Ahmad Awais, ahmadawais, Airat Halitov, Ajit Bohra, Alain Schlesser, albertomedina, aldavigdis, Alex Sanford, Alexander Botteram, alexis, Alexis Lloyd, Amanda Rush, amedina, Andrés, Andrea Fercia, Andrea Middleton, Andrei Lupu, andreiglingeanu, Andrew Duthie, Andrew Munro, Andrew Nevins, Andrew Ozz, Andrew Roberts, Andrew Taylor, andrewserong, Andy Peatling, Angie Meeker, Anna Harrison, Anton Timmermans, ArnaudBan, Arshid, Arya Prakasa, Asad, Ashar Irfan, Asvin Balloo, Atanas Angelov, Bappi, bcolumbia, belcherj, Ben Lowery, Benjamin Eyzaguirre, Benjamin Zekavica, benlk, Bernhard Kau, Bernhard Reiter, betsela, Bhargav Mehta, Birgir Erlendsson (birgire), Birgit Pauli-Haack, bobbingwide, boblinthorst, Boone Gorges, Brady Vercher, Brandon Kraft, Brandon Payton, Brent Swisher, Brianna Privett, briannaorg, Bronson Quick, Brooke., Burhan Nasir, CantoThemes, cathibosco, Chetan Prajapati, chetansatasiya, chetansatasiya, Chouby, Chris Lloyd, Chris Runnells, Chris Van Patten, chriskmnds, Christian Sabo, Christoph Herr, Claudio Sanches, coderkevin, Copons, courtney0burton, Crisoforo Gaspar Hernandez, Csaba (LittleBigThings), csabotta, Daniel James, Daniel Richards, danielhw, daniloercoli, DannyCooper, Darren Ethier (nerrad), davemoran118, David Cavins, David Herrera, David Kennedy, David Ryan, David Sword, Davide 'Folletto' Casali, davidherrera, Davis, dciso, Dennis Snell, Derek Smart, designsimply, Devin Walker, Devio Digital, dfangstrom, Dhanendran, Diego de Oliveira, diegoreymendez, dingo-d, Dion Hulse, Dixita Dusara, Dixita Dusara Gohil, Dominik Schilling, Donna Peplinskie, Drew Jaynes, dsawardekar, dsifford, Duane Storey, Edwin Cromley, ehg, ElectricFeet, Elio Rivero, Elisabeth Pointal, Ella Iseulde Van Dorpe, elrae, enodekciw, ephoxjames, ephoxmogran, Eric Amundson, ericnmurphy, etoledom, Evan Mullins, fabiankaegy, fabs_pim, faishal, Felix Arntz, Florian Simeth, foobar4u, foreverpinetree, Frank Klein, fuyuko, Gabriel Maldonado, Garrett Hyder, Gary Jones, Gary Thayer, garyjones, Gennady Kovshenin, George Olaru, George Stephanis, georgeh, gnif, goldsounds, Grappler, Grzegorz Ziółkowski, Gustavo Bordoni, gwwar, Hardeep Asrani, hblackett, Helen Hou-Sandi, Hendrik Luehrsen, herbmiller, Herre Groen, Hugo Baeta, hypest, Ian Dunn, ianstewart, ibelanger, iCaleb, idpokute, Igor, imath, Imran Khalid, intronic, Ipstenu (Mika Epstein), Irene Strikkers, Ismail El Korchi, israelshmueli, J.D. Grimes, J.D. Grimes, Jacob Peattie, jagnew, jahvi, James Nylen, jamestryon, jamiehalvorson, Jan Dembowski, janalwin, Jason Caldwell, Jason Stallings, Jason Yingling, Javier Villanueva, Jay Hoffmann, Jb Audras, Jeff Bowen, Jeffrey Paul, Jeremy Felt, Jip Moors, JJJ, Joe Bailey-Roberts, Joe Dolson, Joe Hoyle, Joe McGill, joemaller, Joen Asmussen, Johan Falk, John Blackbourn, John Godley, johndyer, JohnPixle, johnwatkins0, jomurgel, Jon Surrell, Jonathan Desrosiers, Jonny Harris, Joost de Valk, Jorge Bernal, Jorge Costa, Jose Fremaint, Josh Pollock, Josh Visick, Joshua Wold, Joy, jrf, jryancard, jsnajdr, JulienMelissas, Justin Kopepasah, K.Adam White, Kallehauge, KalpShit Akabari, Kat Hagan, Kelly Dwan, Kevin Hoffman, khleomix, Kite, Kjell Reigstad, kluny, Konstantin Obenland, Konstantinos Xenos, krutidugade, Lance Willett, Lara Schenck, leahkoerper, lloyd, Loïc Blascos, Lucas Stark, LucasRolff, luigipulcini, Luke Cavanagh, Luke Kowalski, Luke Pettway, Luminus, lynneux, macbookandrew, Maedah Batool, Mahdi Yazdani, mahmoudsaeed, Maja Benke, Marcus Kazmierczak, Marin Atanasov, marina_wp, Marius L. J., mariusvw, Mark Jaquith, Mark Uraine, Marko Andrijasevic, martinlugton, Marty Helmick, mathiu, Matt Cromwell, Matt Mullenweg, MattGeri, Matthew Boynes, Matthew Haines-Young, maurobringolf, Maxime BERNARD-JACQUET, Mayo Moriyama, meetjey, Mel Choyce, mendezcode, Micah Wood, Micah Wood, Michael Adams (mdawaffe), Michael Hull, Michael Nelson, Michele Mizejewski, Migrated to @jeffpaul, Miina Sikk, Mikael Korpela, Mike Crantea, Mike Haydon, Mike Schroder, Mike Selander, mikehaydon, Mikey Arce, Milan Dinić, Milana Cap, Milen Petrinski - Gonzo, milesdelliott, mimo84, mirka, mmtr86, Monique Dubbelman, Morten Rand-Hendriksen, Mostafa Soufi, motleydev, mpheasant, mrmadhat, mrwweb, msdesign21, mtias, Muhammad Irfan, Mukesh Panchal, munirkamal, Muntasir Mahmud, mzorz, nagayama, Nahid F. Mohit, Naoko Takano, napy84, nateconley, Native Inside, Ned Zimmerman, Neil Murray, nic.bertino, Nicola Heald, Niels Lange, Nikhil Chavan, Nikolay Bachiyski, nitrajka, njpanderson, nshki, Okamoto Hidetaka, oskosk, Paresh Radadiya, Pascal Birchler, Paul Bearne, Paul Dechov, Paul Stonier, Paul Wilde, Pedro Mendonça, Peter Wilson, pglewis, Philipp Bammes, piersb, Pieter Daalder, pilou69, Piotr Delawski, poena, postphotos, potbot, Prateek Saxena, Pratik K. Yadav, Presskopp, psealock, ptasker, Rachel, Rachel Baker, Rahmohn, Rahmon, Rahul Prajapati, rakshans1, ramonopoly, Rastislav Lamos, revgeorge, Riad Benguella, Rian Rietveld, richsalvucci, Riddhi Mehta, rileybrook, Robert Anderson, Robert O'Rourke, robertsky, Rocio Valdivia, Rohit Motwani, Ross Wintle, Ryan McCue, Ryan Welcher, ryo511, Sagar Prajapati, Sami Keijonen, Samuel Wood (Otto), Sang-Min Yoon, sarah semark, Scott Weaver, Sergey Biryukov, SergioEstevao, Shahjehan Ali, Shailee Sheth, Sharaz Shahid, Shaun sc, shaunandrews, Shawn Hooper, shenkj, sikander, Simon Prosser, siriokun, sirjonathan, sirreal, Sisanu, skorasaurus, Slushman, Sofia Sousa, SOMTIJDS, Soren Wrede, spocke, Stagger Lee, Stanimir Stoyanov, Stephen Edgar, Steve Henty, Store Locator Plus, strategio, stuartfeldt, tacrapo, talldan, Tammie Lister, ThemeRoots, Thorsten Frommen, Thrijith Thankachan, Tim Hengeveld, timgardner, Timmy Crawford, Timothy Jacobs, Tom J Nowell, Toni Laakso, Toni Viemerö, Tor-Bjorn Fjellner, Toro_Unit (Hiroshi Urabe), Toshihiro Kanai, Towhidul Islam, Travis Lopes, truongwp, Tunji Ayoola, twoelevenjay, Ulrich, Vishal Kakadiya, Vitor Paladini, Walter Ebert, warmarks, WebMan Design | Oliver Juhas, websupporter, Weston Ruter, William Earnhardt, williampatton, Willy Bahuaud, Yahil Madakiya, yingles, Yoav Farhi, Yusuke Takahashi, zebulan, and Ziyaddin Sadigov.

Finally, thanks to all the community translators who worked on WordPress 5.0. Their efforts bring WordPress 5.0 fully translated to 37 languages at release time, with more on the way.

If you want to follow along or help out, check out Make WordPress and our core development blog.

Thanks for choosing WordPress!

by Matt Mullenweg at December 06, 2018 07:28 PM under Releases

Post Status: WordPress 5.0 marks a new era for the world’s most popular CMS

WordPress 5.0, “Bebo,” is a shift of the highest order for the platform. Block-based editing, under the name of “Gutenberg,” is an entirely new way to publish content. It adds a world of flexibility when writing, and it opens the gates for transforming much of the broader WordPress experience moving forward.

TinyMCE has been the core of the WordPress writing experience for, well, forever. Users will be able to continue using TinyMCE with the Classic Editor plugin, which will be especially useful for those web applications with significant amounts of structured content that will take time and reprogramming to fit the new editing experience.

The need for a new editor has been a wide-held concern in the WordPress community for a long time. Gutenberg has been more than two years in the making, and it involved dozens of full-time or near full-time contributors at times. Automattic, the company behind WordPress.com and other popular WordPress products, has invested a great deal in Gutenberg’s development, as have many other companies and individuals — but the bulk of development and decision-making has been by Automattic employees.

There have been critiques that the process for decision making has been too closed off and rushed toward the end of the development cycle for the purpose of delivery by WordCamp US despite ongoing concerns, particularly around accessibility.

5.0 had to ship eventually, and the process has been a long one. It was a complete shift from the traditional development cycles, which I discussed with Matt Mullenweg at WordCamp US two years ago.

I have personally held the view that now is as good a time as any to release 5.0, though the exact timing is a burden on folks traveling to WCUS, particularly considering that it was just a few days notice; it is putting a kink in the plans of many.

Timing aside, Gutenberg is, I believe, an important step and a big test for WordPress. It is imperative that the platform evolves to be both more powerful and easier to use — an enormously difficult dual challenge that I have advocated as an important feat to accomplish for several years now.

WordPress is the easiest full-featured content management system to use. But it is more difficult than many alternative publishing platforms — particularly hosted ones. Drastic changes, like Gutenberg, are necessary to continue being a preferred platform for end users. Being easy to use and customize got WordPress to the dominant position it is in today, and I believe it is extremely important to continue in that trajectory to maintain that position.

At the same time, as WordPress is being used in ever more advanced applications, developers need powerful, scalable solutions. WordPress has made great strides over the years to accommodate this use case, from various APIs to assist in new data structure creation, to the REST API. Gutenberg offers much promise to continue this trend, as it is quite extendable and also flexible for deployment on the web, in native apps, and on both front-ends and backends.

I believe 5.0 is a huge step forward for the platform. The journey is not without its issues, and there is much work to do, but WordPress needed and continues to need big changes and advancements to maintain its position at the top of the content management food chain.

People are using WordPress for all sorts of things, whether traditional publishing, eCommerce, application frameworks, and much more. I’m excited to see what Gutenberg brings to further these applications. Strictly as an editor, it’s far from perfect, but it’s an important step in the right direction.

Get familiar with WordPress 5.0

Here are some links to places to learn more about the new editing experience and WordPress 5.0.

by Brian Krogsgard at December 06, 2018 05:31 PM under Everyone

WPTavern: WPWeekly Episode 340 – Twas the Night Before 5.0

In this episode, John James Jacoby and I are joined by Matt Mullenweg, co-creator of the WordPress project. We discussed a number of topics that have been making the rounds across the community such as:

  • The WordPress 5.0 release strategy and how it will evolve once it’s released.
  • Whether or not Gutenberg is ready and what ready means.
  • Having Automatticians in project leadership roles and what roles WordPress core contributors can or will have going forward.
  • ClassicPress, Publicious, and other forks.
  • Gutenberg and Accessibility.
  • Communication, feedback mechanisms, and trying to make sure everybody can participate in the conversation.

We also talked about the long-term vision of Gutenberg. Near the end of the interview, Matt described some of the innovative things he’s seen built with the new editor.

To round out the show, we sent shoutouts to Alex Mills who recently discovered that he will need to battle through leukemia again.

WPWeekly Meta:

Next Episode: Thursday, December 13th 3:00 P.M. Eastern

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #340:

by Jeff Chandler at December 06, 2018 03:32 AM under WordPress 5.0

December 05, 2018

BuddyPress: BuddyPress 4.1.0 maintenance release

Immediately available is BuddyPress 4.1.0. This maintenance release fixes 3 bugs related to last week’s 4.0.0 release, and is a recommended upgrade for all BuddyPress installations.

For complete details on the release, visit the 4.1.0 changelog.

by Boone Gorges at December 05, 2018 04:18 PM under 4.1.0

Matt: Interview on Gutenberg and Future of WordPress

Yesterday I was able to have a great conversation with Adam from WP Crafter, a popular Youtube channel with over five million views. Adam said it was his first interview but you can’t tell, we had an excellent conversation that covered Gutenberg, the 5.0 release, why WordPress has done well so far, and what’s coming in the future. If you’d like more context than text or tweets can give for what’s happening in WordPress today, check it out.

Of course Friday and Saturday are WordCamp US, which returns to Nashville this year. Everything will be live-streamed for free, including my State of the Word presentation on Saturday, you just need to pick up a free streaming ticket.

by Matt at December 05, 2018 02:16 PM under Asides

WPTavern: WordPress 5.0 Targeted for December 6, Prompting Widespread Outcry Ahead of WordCamp US

During last week’s core dev chat, Matt Mullenweg urged developers to consider WordPress 5.0 as “coming as soon as possible.” Nevertheless, his decision to set Thursday, December 6, for the new release date has taken many by surprise.

Official feedback channels and social media erupted with largely negative feedback on the decision, as the new release date has 5.0 landing the day before WordCamp US begins. This is a travel day for many attending the conference. It also means both of the planned follow-up releases will be expected during the upcoming weeks when many have scheduled time off for major world holidays.

Yoast CEO Joost de Valk, one of the most vocal critics of the 5.0 timelime, posted a public message of dissent that resonated with many on Twitter:

We vehemently disagree with the decision to release WordPress 5.0 on December 6th, and think it’s irresponsible and disrespectful towards the community.

However, we’re now going to try and support the community as well as possible and we hope to show everyone that Gutenberg is indeed a huge step forward.

Although Gutenberg as a project has strong support from many large companies in the WordPress ecosystem, much of the current uproar is rooted in a communication published in early October that indicated 5.0 would be pushed to January if it missed the first set of planned release dates:

We know there is a chance that 5.0 will need additional time, so these dates can slip by up to 8 days if needed. If additional time beyond that is required, we will instead aim for the following dates:

Secondary RC 1: January 8, 2019

Secondary Release: January 22, 2019

Should we need to switch to the secondary dates, this will be communicated as soon as we’re aware.

Companies made plans based on this schedule, but after those dates passed Mullenweg was unwilling to commit to honoring the previous communication. The plan from the outset may have been to “play it by ear” and incorporate new information as it became available, but the developer community had been counting on the published deadlines to be definitive.

“This decision was made in disregard to earlier specific timelines and promises, and does not take the realities on the ground into account,” Morten Rand-Hendricksen said. “I agree with @yoast it is both irresponsible and disrespectful.”

Although reactions on Twitter run the gamut from unbridled optimism to full on outrage, many of those commenting on the schedule have fallen into resignation, convinced that community feedback never really mattered when it came to scheduling the release.

Mullenweg’s rationale behind announcing the release date with three days notice is that Gutenberg and/or the Classic Editor are already active on more than 1.3 million sites. Users do not have to upgrade to WordPress 5.0 until they are ready. If they opt for the Classic Editor, the editing experience “will be indistinguishable from 4.9.8.”

Users who are informed enough to make this choice will be well-prepared when they see that 5.0 update in their dashboards. However, one of the chief concerns is that millions of WordPress users will update without testing. Plugin developers are scrambling to ship compatibility updates and support staff will need to be on hand to help users navigate any incompatibilities or bugs in the new editing experience. Hundreds of WordPress professionals will be traveling to WordCamp US when 5.0 is expected to ship, which poses challenges for supporting users who experience problems with the update.

“I do not think the attendees of WCUS are more important than much larger portion of the WordPress community who does not (and cannot) attend, and there are numerous ways to deal with 5.0 before or after the 6th if that particular day is inconvenient for someone, regardless of the reason,” Mullenweg said in response to comments regarding the date conflicting with travel plans.

The release date announcement has well over 100 comments from frustrated contributors and developers expressing concerns, and Mullenweg has been responsive in the comments. He has recently ramped up communication ahead of the release, regularly attending core dev chats, adding dedicated office hours to connect with the community one-on-one, and answering some of the most pressing Gutenberg questions on his blog in a lengthy but inspiring FAQ post.

Despite these communication efforts, contributors who are not employed by Automattic have said they feel this release has been plagued by a lack of transparency regarding decision-making. Many WordPress core committers, core contributors, and former release leads have pushed back on releasing before January to no avail. Their concerns and disappointments during the process hang like a dark cloud over what should be an exciting time for the future of WordPress.

“No matter how bad the process around WordPress 5.0 might have been, finally setting a release date was the only right step following the RCs,” WordPress core developer Dominik Schilling said. “Let’s see if it’s also the beginning for doing it better to get back on releases which everyone will love.”

John Teague, who runs an 11-person operation, managing 210 enterprise hosting clients, summarized how many are feeling ahead of WordPress 5.0 shipping out this week.

“I so want to be supportive of this release,” Teague said. “But between the top down, heavily Automattic managed process, poor release communication, super short RC2, RC3, punting on accessibility, and now this two-day notice to 5.0 release – it reminds me of an old Air Force saying when instructors sent barely trained pilots up for their first solo:

‘Send em up and let God grade em.'”

by Sarah Gooding at December 05, 2018 07:37 AM under WordPress 5.0

HeroPress: WordPress made me walk 700km to Berlin

Pull Quote: Nothing happens in your comfort zone. Go beyond and find the magic.

Since the year 2000 I was employed at a big IT hardware/software/services firm. After about 9 years I was not feeling quite happy about how things went. Let’s say that the plans the company had with me did not really line up with the monthly reward. So, I quit and started my own company, nostromo.nl in June 2009 (Tweetproof). The goal was to serve customers by designing/developing and maintaining websites.

A new beginning

Now the challenge begins. Where do I start, who do I call? “Hello, do you need a new website? I just started my company and I can help you”. Why would I be the right person to help this company with their new website? The first thing I learned was to be sure of myself. I know what I can do and the customer needs help, probably because they are not so skillful in building websites.

After a month I was talking with a potential customer, my first one (!), and I got the quotation signed. I was going to build my own CMS, and I soon realized (the hard way) that was not the way to go. I had to do a CMS comparison and WordPress won.

Here comes WordPress

The ease of use and the extensive documentation for developers convinced me. After having built numerous websites, and offering maintenance services to customers, I wanted  to know who the people were that built WordPress. Why? Well, because I was using free software and I was making money with it. That didn’t feel right, I wanted to give something back.

Browsing support forums and IRC (that’s something like Slack, but without the GIFs) I quickly became aware of the WordPress community and felt I wanted to get to know these great people.

WordCamp – how it changed me

It was 2010 when I learned about a thing called WordCamp in The Netherlands. The entrance ticket was cheap and I could attend talks by inspiring people. On November 6th 2010, I was waiting in line at the registration desk. It was my turn, and someone from behind the desk said; “Hey, nostromo!”. It was Remkus de Vries, he recognized me from my avatar on Twitter and those two words made me feel welcome immediately. This moment I remember very vividly and it marks the point where my enthusiasm for the WordPress community was sparked to life.

I volunteer – a lot

Giving back to the community got defined. Translating, helping out in the Dutch official WordPress support forum, organizing meetups/WordCamps (The Netherlands, the first WordCamp Europe, and WordCamp Rotterdam) and helping others join and be active in the WordPress community. These were some of the things I did, and yes, I had to push the brake on voluntary jobs sometimes, because I also needed to be productive and profitable in my business. Since that first WordCamp I have met amazing, inspiring and skillful people (in random order). I haven’t met new people, I met new friends.

Volunteering – taking it to the next level

It was June 4th 2018 when I got a weird idea. Yeah, that sometimes happens. Impulsive as I am, I tweeted it:

Little did I know, there was a body part that had a big objection. While planning to go to Belgrade for WordCamp Europe 2018 this happened:

And yes, I had to cancel our trip (my wife was going to join) and ended up laying in bed for about a week with an inflamed knee. I received antibiotics from the doctor and gladly the pain and inflammation disappeared. That aside, at the end of WCEU 2018 it was announced that WCEU 2019 was going to be in Berlin. I was happy, since that’s really close (about 700 km) to where I live.

Currently I am training, I’ve planned my route and I am looking for places to sleep in Germany. Please see this website walktowc.eu for more information. Since this hike is probably going to gain some attention in the community, I had another idea. Why not use this as a means to raise money, for a good cause. Walking 700 km in about 30 days is a challenge, and if I can get enough attention, raising money might work out. Now I just had to find a good cause to raise money for…

Raising funds for DonateWC

I have known Ines van Essen for a few years now and in September 2017 she started a thing called DonateWC. After a successful initial funding campaign they sent their first recipient to WordCamp Capetown in October 2017. Seeing this made me believe this is another sign of how friendly and supporting the WordPress community is, to make sure that people are able to attend WordCamps, while they do not have the financial means to do so. The community supports community members, and that’s the reason why I chose DonateWC as the cause I’m going to raise funds for. And as a side effect also raise awareness of the existence of DonateWC.

My message to you

Don’t feel obliged to do things you don’t like.

Do things you like.

Start volunteering.

Build your network.

Enjoy the community.

Step (or walk) out of your comfort zone.

The post WordPress made me walk 700km to Berlin appeared first on HeroPress.

by Marcel Bootsman at December 05, 2018 07:00 AM

December 04, 2018

Dev Blog: WordPress 5.0 RC3

The third release candidate for WordPress 5.0 is now available!

WordPress 5.0 will be released on December 6, 2018. This is a big release and needs your help—if you haven’t tried 5.0 yet, now is the time!

To test WordPress 5.0, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip).

For details about what to expect in WordPress 5.0, please see the first release candidate post.

This release candidate includes a fix for some scripts not loading on subdirectory installs (#45469), and user locale settings not being loaded in the block editor (#45465). Twenty Nineteen has also had a couple of minor tweaks.

Plugin and Theme Developers

Please test your plugins and themes against WordPress 5.0 and update the Tested up to version in the readme to 5.0. If you find compatibility problems, please be sure to post to the support forums so we can figure those out before the final release. An in-depth field guide to developer-focused changes is coming soon on the core development blog. In the meantime, you can review the developer notes for 5.0.

How to Help

Do you speak a language other than English? Help us translate WordPress into more than 100 languages! 

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


WordPress Five Point Oh
Is just a few days away!
Nearly party time!
🎉

by Gary Pendergast at December 04, 2018 07:07 AM under 5.0

December 03, 2018

WPTavern: New Block Gallery Plugin Offers a Suite of Photo Gallery Blocks for Gutenberg

The new Gutenberg editor has basic support for galleries with a few nice features, such as the ability to set the number of columns and automatically crop thumbnails for a more uniform appearance. If you need more control over your galleries, Rich Tabor’s Block Gallery plugin is currently the best option made specifically for use with Gutenberg and WordPress 5.0+. It offers a suite of photo gallery blocks with minimal, tasteful styling that fits unobtrusively into virtually any site design.

Block Gallery currently offers three different blocks, including masonry, fullscreen stacked, and a carousel slider. Each block has its own settings that offer more customization for the specific gallery type.

The plugin also makes use of Gutenberg’s block transform utility to allow users to seamlessly transform galleries from one style to another with one click, as demonstrated in the video below.

A demo of the new Block Gallery WordPress Plugin

“I built the Block Gallery plugin originally as a proving ground for exploring how my portfolio WordPress themes at ThemeBeans will interface with Gutenberg,” ThemeBeans founder Rich Tabor said. “I do not particularly like the idea of disabling the block editor on portfolio custom post types, so I wanted to find a clever way for folks to use different sorts of galleries to showcase their art, illustrations, photos, etc. Block Gallery was born out of that exploration.”

Tabor said that although the core gallery block is much more robust than the classic editor’s gallery system, he wanted to give users more flexibility in how they display media. His favorite feature of the project is the ability to morph gallery blocks into different types.

“That means every image, settings, display option, and color selection are each migrated instantly — if a user swaps out a selected gallery for a different type,” Tabor said. “For instance, folks can morph from a masonry gallery to a carousel slider in a single click, without having to re-upload/assign images or select any options. It’s all done behind the scenes, automagically.”

Tabor’s Block Gallery plugin is a major leap forward for galleries in terms of usability. It offers a beautiful implementation of features that would have been difficult to imagine before the block editor. Block Gallery currently has more than 400 active installs after a little more than month in the official directory. Watch for that number to jump as more people begin using the new editor when WordPress 5.0 is released.

by Sarah Gooding at December 03, 2018 10:29 PM under gutenberg

Dev Blog: The Month in WordPress: November 2018

WordPress 5.0 is almost ready for release, including an all-new content editing experience. Volunteers all across the project are gearing up for the launch and making sure everything is ready. Read on to find out what’s been happening and how you can get involved.


WordPress 5.0 Close to Launch

The release date for WordPress 5.0 has not yet been set, but the second release candidate (RC) is now available. The final release date will be determined based on feedback and testing of this RC. The Core development team has been posting daily updates on the progress of their work on v5.0, with the number of open issues for this release decreasing every day.

The primary feature of this release is the new editor that will become the default WordPress experience going forward. A number of people have been seeking more direct feedback from the release leads about the progress of this release, which @matt has facilitated by hosting one-to-one discussions with anyone in the community who wanted to talk with him about it. He has also published an extended FAQ covering many of the questions people have been asking.

Alongside the development of the new editor, the Mobile team has been working hard to bring the WordPress mobile apps up to speed. They plan to make a beta version available in February 2019.

Want to get involved in developing WordPress Core in 5.0 and beyond? Follow the Core team blog and join the #core channel in the Making WordPress Slack group.

New WordPress Support Platform Goes Live

WordPress user documentation has long been hosted on the WordPress Codex, but for the past couple of years an ambitious project has been underway to move that content to a freshly-built WordPress-based platform. This project, named “HelpHub,” is now live and the official home of WordPress Support.

There is still plenty of content that needs to be migrated from the Codex to HelpHub, but the initial move is done and the platform is ready to have all WordPress’ user documentation moved across. HelpHub will be the first place for support, encouraging users to find solutions for themselves before posting in the forums.

Want to get involved in populating HelpHub with content, or with its future development? Follow the Documentation team blog and join the #docs channel in the Making WordPress Slack group.

Spanish WordPress Community Pushes Translations Forward

The WordPress community in Spain has been hard at work making sure as much of the WordPress project as possible is available in Spanish. They have recently translated more of the project than ever — including WordPress Core, WordPress.org, the mobile apps and the top 120 plugins in the Directory.

This achievement has largely been possible due to the fact that the Spanish translation team has over 2,500 individuals contributing to it, making it the largest translation team across the whole project.

Want to get involved in translating WordPress into your local language? You can jump straight into translations, follow the Polyglots team blog and join the #polyglots channel in the Making WordPress Slack group.


Further Reading:

If you have a story we should consider including in the next “Month in WordPress” post, please submit it here.

by Hugh Lashbrooke at December 03, 2018 05:43 PM under Month in WordPress

WPTavern: WordCamp Europe Opens the Call for Host City 2020

WordCamp Europe has opened the call for a host city for 2020. Previous editions of the event have been held in Leiden, Sofia, Seville, Vienna, Paris, and Belgrade, and the next on deck is Berlin in 2019. Organizers are always working ahead for an event this size. In fact, the team plans together for the better part of a year before attendees arrive for the three-day event. The upcoming WCEU is currently being planned by a team of 66 organizers from 15 countries.

Teams applying to host WordCamp Europe are required to have organized at least one or more successful WordCamps in a European city, with at least one recent one held in 2017 or 2018. The core organizing team will work with all applicants in the open to help them prepare the best applications possible, as detailed in the announcement:

To guarantee total transparency during the process, all applicants receive the same help in the appropriate public channel of the WCEU Slack workspace. No question is considered or answered in a private message.

Three weekends in June 2020 are available to applicants as potential dates. Teams interested to apply are encouraged to begin filling out the 7-page survey (which can be started and completed as information becomes available). It includes questions about the local community, previous WordCamps, possible venue(s), cost of living in the city, and other data that will be important to the selection committee.

A preliminary online AMA session will be held December 13, 2018, to assist teams in answering questions about the application process. The deadline to apply to host the event is February 28, 2019. Applicants will receive a decision by March 15, 2019, and the final selection will be announced during the closing remarks in Berlin next June. Check out the call for host cities announcement for more information.

by Sarah Gooding at December 03, 2018 04:45 PM under WordCamp Europe

December 01, 2018

WPTavern: Mullenweg Ramps Up Communication Ahead of WordPress 5.0 Release, RC2 Now Available

WordPress 5.0 RC2 was released today with 15 notable updates, including improvements to block preview styling, browser-specific bug fixes, and other changes. RC2 was released simultaneously with Gutenberg version 4.6.

The official release date for WordPress 5.0 has not yet been announced, because it depends on feedback from RC2 testing. Contributors’ uneasiness with not having an official release date seemed to reach a critical tipping point during this week’s WordPress dev chat, as many participants pressured Matt Mullenweg, who is leading the release, to give more information on when they can expect 5.0.

“It is very important that we have a release date to aim for,” ACF founder Elliot Condon said. “I’m finding the current ‘waiting game’ quite stressful, and I suspect a few other developers will share the same feeling.”

Tensions were high as contributors cited various reasons for wanting a date, including companies needing support staff on hand, upcoming holidays, documentation planning, and the importance of user trust.

“We’re determining the release date based on the open issues,” Mullenweg said. “Please consider it as coming as soon as possible, when everything is resolved.”

“I hope it’s clear we’re trying to get this out as soon as possible, but don’t yet have enough data to announce an official date. As mentioned last week we have done a number of December releases in the past, and may this time, but don’t have enough data to announce a new date yet.”

Mullenweg also urged dev chat attendees to keep in mind that any site administrators can install the Classic Editor plugin to keep the current editing experience, regardless of the 5.0 release date. He said the date will be announced via a P2 post, not during a dev chat.

“If you want to know what to plan on, please don’t hold anything back based on expected dates, please test or deploy the RCs, that’s what they’re for,” Mullenweg said.

In the meantime, Mullenweg is spending the weekend taking questions from the community during 24 office hours slots. He also published a lengthy post titled “WordPress 5.0: A Gutenberg FAQ,” which reaffirms WordPress’ mission in the context of Gutenberg. It answers questions like “Why do we need Gutenberg at all?” and “Why blocks?”

“I knew we would be taking a big leap,” Mullenweg said. “But it’s a leap we need to take, and I think the end result is going to open up many new opportunities for everyone in the ecosystem, and for those being introduced to WordPress for the first time. It brings us closer to our mission of democratizing publishing for everyone.”

The stats Mullenweg cited about previously having 9 major WordPress releases in December (34% of all releases in the last decade) indicate that a December release may still be on the table. His post addresses the perceived urgency behind getting Gutenberg out the door and into the hands of users. In evaluating WordPress 5.0’s readiness, he said it’s important to differentiate between the code being ready and the community being ready.

“In the recent debate over Gutenberg readiness, I think it’s important to understand the difference between Gutenberg being ready code-wise (it is now), and whether the entire community is ready for Gutenberg,” Mullenweg said.

“It will take some time — we’ve had 15 years to polish and perfect core, after all — but the global WordPress community has some of the world’s most talented contributors and we can make it as good as we want to make it.”

The post also offers a preview of where Gutenberg is going in the next site customization phase and how it will change the way users build their sites.

“The Editor is just the start,” he said. “In upcoming phases blocks will become a fundamental part of entire site templates and designs. It’s currently a struggle to use the Customizer and figure out how to edit sections like menus, headers, and footers. With blocks, people will be able to edit and manipulate everything on their site without having to understand where WordPress hides everything behind the scenes.”

Mullenweg said he plans to talk more about the next phases following site customization during the State of the Word address at WordCamp US. If you have questions about Gutenberg and where it’s headed, the comments are open on his post.

by Sarah Gooding at December 01, 2018 03:15 AM under WordPress 5.0

WPTavern: Let Us Know If You’re Hosting a WordCamp US Watch Party

WordCamp US is next weekend and if you’re unable to attend, you can watch from home via the free livestream. However, some WordPress meetup groups host watch parties. These parties generally include food, beverages, and a large projection screen.

If you’re hosting one of these parties, please let us know about it in the comments. Tell us the location and what attendees can expect.

by Jeff Chandler at December 01, 2018 01:11 AM under wcus

November 30, 2018

Dev Blog: WordPress 5.0 RC2

The second release candidate for WordPress 5.0 is now available!

This is an important milestone, as we near the release of WordPress 5.0. A final release date will be announced soon, based on feedback from this release candidate. Things are appearing very stable and we hope to announce a date soon. This is a big release and needs your help—if you haven’t tried 5.0 yet, now is the time! 

To test WordPress 5.0, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip).

For details about what to expect in WordPress 5.0, please see the previous release candidate post.

Significant changes

  • We stopped rendering AdminNotices compatibility component, as this previous attempt at backward compatibility was bringing in numerous incompatible banners and notices from plugins.
  • An update to the parser to better deal with malformed HTML that could cause a loop. We’re only aware of this in the wild being triggered once in the over a million posts made with Gutenberg, but it caused a loop so we wanted to fix for RC2.

Cosmetic and minor changes in RC2

  • Accessibility: Simplify sidebar tabs aria-labels.
  • Make the Image Link URL field readonly.
  • Internationalization: Merge similar text strings that differed only in capitalization.
  • CSS: Improve block preview styling.
  • CSS: Fix visual issues with Button block text wrap.
  • Fix getSelectedBlockClientId selector.
  • Fix Classic block not showing galleries on a grid.
  • Fix an issue where the block toolbar would cause an image to jump downwards when the wide or full alignments were activated.
  • Move editor specific styles from style.scss to editor.scss in Cover block.
  • Fix modals in Microsoft Edge browser.
  • Fix Microsoft IE11 focus loss after TinyMCE init. Add IE check.
  • Fix Microsoft IE11 input when mounting TinyMCE.
  • Change @package names to WordPress.

How to Help

Do you speak a language other than English? Help us translate WordPress into more than 100 languages! 

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


RC bittersweet.
We welcome in Gutenberg,
Vale Gutenbeard.

by Gary Pendergast at November 30, 2018 11:16 PM under 5.0

WPTavern: Gutenberg Times to Host Live Q&A with Gutenberg Leads on Friday, November 30

Birgit Pauli-Haack, curator of the Gutenberg Times website, is hosting a Q&A session with Gutenberg’s phase 1 design and development leads on Friday, November 30, at 2pm ET (19:00 UTC). Matias Ventura, Tammie Lister, and Joen Asmussen will join Pauli-Haack to discuss their journey “Creating Gutenberg” over the past two years.

If you have any pressing questions about Gutenberg’s architecture, design, or the future of the project, this event is a good opportunity to speak to members of the team who have been building it full-time. The Q&A is free to watch but attendees who want to participate with questions will need to register. There are 100 seats available. Pauli-Haack will also be live-streaming the session to the Gutenberg Times YouTube channel.

by Sarah Gooding at November 30, 2018 12:48 AM under gutenberg

November 29, 2018

Matt: WordPress 5.0: A Gutenberg FAQ

Update: On December 6th we released WordPress 5.0. It was definitely the most controversial release in a while, but the usage and adoption metrics are looking similar to previous releases. I’m looking forward to continuing to iterate on the new block editor!

We are nearing the release date for WordPress 5.0 and Gutenberg, one of the most important and exciting projects I’ve worked on in my 15 years with this community.

I knew we would be taking a big leap. But it’s a leap we need to take, and I think the end result is going to open up many new opportunities for everyone in the ecosystem, and for those being introduced to WordPress for the first time. It brings us closer to our mission of democratizing publishing for everyone.

I recently visited WordCamp Portland to talk about Gutenberg and WordPress 5.0, which will also include the new default theme Twenty Nineteen, which you’re seeing me test out on this very site. There were some great questions and testimonials about Gutenberg, so I’d urge you to watch the full video and read the WP Tavern recap. I’ve also visited meetups, responded to review threads, kept an eye on support, and I’m in the middle of office hours with the core community.

As we head toward the release date and WordCamp US, I’ve put many questions and answers into a Gutenberg FAQ below. For those who have other questions, I will be checking the comments here.

It’s an exciting time, and I’m thrilled to be working with y’all on this project.

Not the ship of Theseus

What is Gutenberg?

Gutenberg, for those who aren’t actively following along, is a brand new Editor for WordPress — contributors have been working on it since January 2017 and it’s one of the most significant changes to WordPress in years. It’s built on the idea of using “blocks” to write and design posts and pages.

This will serve as the foundation for future improvements to WordPress, including blocks as a way not just to design posts and pages, but also entire sites.

The overall goal is to simplify the first-time user experience of WordPress — for those who are writing, editing, publishing, and designing web pages. The editing experience is intended to give users a better visual representation of what their post or page will look like when they hit publish. As I wrote in my post last year, “Users will finally be able to build the sites they see in their imaginations.”

Matías Ventura, team lead for Gutenberg, wrote an excellent post about the vision for Gutenberg, saying, “It’s an attempt to improve how users interact with their content in a fundamentally visual way, while at the same time giving developers the tools to create more fulfilling experiences for the people they are helping.”

Why do we need Gutenberg at all?

For many of us already in the WordPress community, it can be easy to forget the learning curve that exists for people being introduced to WordPress for the first time. Customizing themes, adding shortcodes, editing widgets and menus — there’s an entire language that one must learn behind the scenes in order to make a site or a post look like you want it to look.

Over the past several years, JavaScript-based applications have created opportunities to simplify the user experience in consumer apps and software. Users’ expectations have changed, and the bar has been raised for simplicity. It is my deep belief that WordPress must evolve to improve and simplify its own user experience for first-time users.

Why blocks?

The idea with blocks was to create a new common language across WordPress, a new way to connect users to plugins, and replace a number of older content types — things like shortcodes and widgets — that one had to be well-versed in the idiosyncrasies of WordPress to understand.

The block paradigm is not a new one — in fact many great plugins have already shown the promise of blocks with page design in WordPress. Elementor, one of the pioneers in this space, has now introduced a new collection of Gutenberg blocks to showcase what’s possible:

Why change the Editor?

The Editor is where most of the action happens in WordPress’s daily use, and it was a place where we could polish and perfect the block experience in a contained environment.

Additionally, the classic Editor was built primarily for text — articles have become increasingly multimedia, with social media embeds, maps, contact forms, photo collages, videos, and GIFs. It was time for a design paradigm that allowed us to move past the messy patchwork of shortcodes and text.

The Editor is just the start. In upcoming phases blocks will become a fundamental part of entire site templates and designs. It’s currently a struggle to use the Customizer and figure out how to edit sections like menus, headers, and footers. With blocks, people will be able to edit and manipulate everything on their site without having to understand where WordPress hides everything behind the scenes.

What does Automattic get out of this?

There have been posts recently asking questions about Automattic’s involvement in Gutenberg compared to other contributors and companies. There is no secret conspiracy here — as project lead I was able to enlist the help of dozens of my colleagues to contribute to this project, and I knew that a project of this size would require it. Automattic aims to have 5% of its people dedicated to WordPress community projects, which at its current size would be about 42 people full-time. The company is a bit behind that now (~35 full-time), and the company is growing a lot next year, so look for 10-15 additional people working on core and community projects. 

In the end, Gutenberg is similar to many other open source projects — Automattic will benefit from it, but so will everyone else in the WordPress community (and even the Drupal community). It’s available for everyone under the GPL. If the goal was purely to benefit Automattic it would have been faster, easier, and created an advantage for Automattic to have Gutenberg just on WP.com. That wasn’t, and isn’t, the point.

Is Gutenberg ready?

Absolutely. Our original goal with Gutenberg was to get it on 100,000 sites to begin testing — it’s now already on more than 1 million sites, and it’s the fastest-growing plugin in WordPress history. There is a lot of user demand.

The goal was to both test Gutenberg on as many sites as possible before the 5.0 release, and also to encourage plugin developers to make sure their plugins and services will be ready. With everyone pitching in, we can make this the most anti-climactic release in WordPress history.  

In the recent debate over Gutenberg readiness, I think it’s important to understand the difference between Gutenberg being ready code-wise (it is now), and whether the entire community is ready for Gutenberg.

It will take some time — we’ve had 15 years to polish and perfect core, after all — but the global WordPress community has some of the world’s most talented contributors and we can make it as good as we want to make it.

There is also a new opportunity to dramatically expand the WordPress contributor community to include more designers and JavaScript engineers. With JavaScript apps there are also new opportunities for designing documentation and support right on the page, so that help arrives right where you need it.

Someone described Gutenberg to me as “WordPress in 3D.” I like the sound of that. Blocks are like layers you can zoom in and out of. The question now is: What are we going to build with this new dimension?

Do I have to switch to Gutenberg when WordPress 5.0 is released?

Not at all. When it’s released, you get to choose what happens. You can install the Classic Editor plugin today and when 5.0 is released, nothing will change. We’ve commited to supporting and updating Classic Editor until 2022. If you’d like to install Gutenberg early, you can do that now too. The Classic Editor plugin has been available for 13 months now, and Gutenberg has been available for 18 months. Both have been heavily promoted since August 2018, and more than 1.3 million .org sites have opted-in already to either experience, so nothing will change for them when they update to 5.0.

How can I make sure I’m ready?

Before updating to 5.0, try out the Gutenberg plugin with your site to ensure it works with your existing plugins, and also to get comfortable with the new experience. Developers across the entire ecosystem are working hard to update their plugins, but your mileage and plugins may vary. And you can always use the Classic Editor to address any gaps.

As with every new thing, things might feel strange and new for a bit, but I’m confident once you start using it you’ll get comfy quickly and you won’t want to go back.

The release candidate of 5.0 is stable and fine to develop against and test.

When will 5.0 be released?

We have had a stable RC1, which stands for first release candidate, and about to do our second one. There is only currently one known blocker and it’s cosmetic. The stability and open issues in the release candidates thus far makes me optimistic we can release soon, but as before the primary driver will be the stability and quality of the underlying software. We made the mistake prior of announcing dates when lots of code was still changing, and had to delay because of regressions and bugs. Now that things aren’t changing, we’re approaching a time we can commit to a date soon.

Is it terrible to do a release in December?

Some people think so, some don’t. There have been 9 major WordPress releases in previous Decembers. December releases actually comprise 34% of our major releases in the past decade.

Can I set it up so only certain users get to use Gutenberg?

Yes, and soon. We’re going to be doing another update to the Classic Editor before the 5.0 release to give it a bit more fine-grained user control — we’ve heard requests for options that allow certain users or certain roles and post types to have Gutenberg while others have Classic Editor.

What happens after 5.0?

We’ve been doing a release of Gutenberg every two weeks, and 5.0 isn’t going to stop that. We’ll do minor release to 5.0 (5.0.1, 5.0.2) fortnightly, with occasional breaks, so if there’s feedback that comes in, we can address it quickly. Many of the previous bugs in updates were from juggling between updates in the plugin and core, now that Gutenberg is in core it’s much easier and safer to incrementally update.

What about Gutenberg and accessibility?

We’ve had some important discussions about accessibility over the past few weeks and I am grateful for those who have helped raise these questions in the community.

Accessibility has been core to WordPress from the very beginning. It’s part of why we started – the adoption of web standards and accessibility.

But where I think we fell down was with project management — specifically, we had a team of volunteers that felt like they were disconnected from the rapid development that was happening with Gutenberg. We need to improve that. In the future I don’t know if it makes sense to have accessibility as a separate kind of process from the core development. It needs to be integrated at every single stage.

Still, we’ve accomplished a lot, as Matías has written about. There have been more than 200 closed issues related to accessibility since the very beginning.

We’re also taking the opportunity to fix some things that have had poor accessibility in WordPress from the beginning. CodeMirror, which is a code editor for templates, is not accessible, so we have some parts of WordPress that we really need to work on to make better.

Speaking of which, CodeMirror was seeking funding for their next version — Automattic has now sponsored that funding and in return it will be made available under the GPL, and that the next version of CodeMirror will be fully accessible.

Finally, Automattic will be funding an accessibility study of WordPress, Gutenberg, and an evaluation of best practices across the web, to ensure WordPress is fully accessible and setting new standards for the web overall.

After WordPress 5.0, is the Gutenberg name going to stick around?

Sometimes code names can take on a life of their own. I think Gutenberg is still what we’ll call this project — it’s called that on GitHub, and you’re also seeing it adopted by other CMSes beyond WordPress — but for those outside the community I can see it simply being known as “the new WordPress editor.”

With the adoption of React for Gutenberg, what do you see as the future for React and WordPress?

In 2015 I said “Learn JavaScript deeply” — then in 2016 we brought the REST API into Core. Gutenberg is the first major feature built entirely on the REST API, so if you are learning things today, learn JavaScript, and I can imagine a future wp-admin that’s 100% JavaScript talking to APIs. I’m excited to see that happen.

Now, switching to a pure JavaScript interface could break some backward compatibility, but a nice thing about Gutenberg is that it provides an avenue for all plugins to work through — it gives them a way to plug in to that. It can eliminate the need for what’s currently done in custom admin screens.  

The other beautiful thing is that because Gutenberg essentially allows for translation into many different formats — it can publish to your web page, it can publish your RSS feed, AMP, it can publish blocks that can be translated into email for newsletters — there’s so much in the structured nature of Gutenberg and the semantic HTML that it creates and the grammar that’s used to parse it, can enable for other applications.

It becomes a little bit like a lingua franca that even crosses CMSes. There’s now these new cross-CMS Gutenberg blocks that will be possible. It’s not just WordPress anymore — it might be a JavaScript block that was written for Drupal that you install on your WordPress site. How would that have ever happened before? That’s why we took two years off — it’s why we’ve had everyone in the world working on this thing. It’s because we want it to be #WorthIt.

And WordPress 5.0 is just the starting line. We want to get it to that place where it’s not just better than what we have today, but a world-class, web-defining experience. It’s what we want to create and what everyone deserves.

Was this post published with Gutenberg?

Of course. 😄 No bugs, but I do see lots of areas we can continue to improve and I’m excited to get to work on future iterations.

by Matt at November 29, 2018 11:56 PM under gutenberg

WPTavern: WPCampus Seeks to Raise $30K for Gutenberg Accessibility Audit

WPCampus is seeking funding to conduct an accessibility audit of WordPress’ Gutenberg editor. The non-profit organization is dedicated to helping web professionals, educators, and others who work with WordPress in higher education. Educational institutions often have stricter legal obligations that require software to be WCAG 2.0 level AA compliant and many European institutions set the bar even higher at WCAG 2.1.

WPCampus moved to spearhead an audit after Automattic decided to forego Matt MacPherson’s proposal for Gutenberg to undergo an accessibility audit. Results of the audit will help WPCampus determine any potential legal risk for institutions upgrading to WordPress 5.0 and will also identify specific challenges that Gutenberg introduces for assistive technology users and others with accessibility needs.

“A professional accessibility audit is a large expense for a small nonprofit like WPCampus,” WPCampus director Rachel Cherry said. “Accessibility is important to all of us in the WordPress community. We’re asking for your help to fund the audit and ensure this important research is completed.”

WPCampus is still evaluating proposals from vendors and will announce its selection soon, along with an updated timeline for completing the audit. The organization has set its funding goal at $30,000, an amount that falls in the mid-range of the proposals the selection committee has received. If the campaign raises more than the amount required, WPCampus plans to designate the funds for other accessibility-related efforts, such as future audits and live captioning at conferences.

Two days after launching the campaign, WPCampus has received $3,692 (12%) towards its funding goal. The organization plans to share the results of the audit and any supporting documents on its website.

The comments published on the donations page demonstrate how strongly supporters feel about getting an audit and using that information to make Gutenberg a tool that anyone can use. The topic of accessibility is close to the heart for many donating to the campaign.

“When I was navigating stores with three small children, stores which helped me with automatic doors, wide aisles, and shopping carts for a crowd often made the decision for me as to whether I could shop at all,” WordPress developer Robin Cornett said. “As we create content and build tools for the internet, we should be doing all we can to ensure the best online experience we can for everyone.”

WordPress co-founder Mike Little also donated to the campaign, with comments on how important accessibility is to fulfilling the project’s mission.

“As the platform that democratizes publishing, we can’t allow new features in WordPress to take that away from users with accessibility needs,” Little said.

“Accessibility matters to everyone — injured, encumbered, distracted, disabled, everyone,” WordPress consultant Adrian Roselli said. Accessibility in WordPress matters to my clients because some of their people require it in order to use the tool and therefore stay gainfully employed.”

The audit proposed months ago has evolved to become a community effort funded by passionate supporters working in various capacities throughout the WordPress ecosystem. If WPCampus is successful in funding its campaign, this particular approach has the benefit of making it a more cooperative effort with more people invested in the process than if it were funded by a single company. WPCampus aims to release the audit report to the community by January 17, 2019 but the dates will depend on the arrangement with the vendor.

by Sarah Gooding at November 29, 2018 10:03 PM under gutenberg

Follow our RSS feed: 

WordPress Planet

This is an aggregation of blogs talking about WordPress from around the world. If you think your blog should be part of this site, send an email to Matt.

Official Blog

For official WordPress development news, check out the WordPress Core Blog.

Subscriptions

Last updated:

December 17, 2018 01:00 AM
All times are UTC.