It was a treat for me to see some folks in-person and online at Matt Mullenweg’s State of the Word on December 14th. For me, the thrill of his annual keynote is hearing his perspective of the year and what questions it raises in the community. Unfortunately, we didn’t get to all of the questions! We only had a handful of pre-submitted questions which I’ve included along with their answers in my post below. After those, I’ve listed all the questions that were received during State of the Word (with the exception of the banana shake questions 😉
How do we do this?
All unanswered questions have been assigned reference numbers (Q1, Q2, Q3, etc) and any corresponding answers that come in the comments will be labeled similarly (A1, A2, A3, etc). Just like twitter, but slower! 🙂
Matt, me, and my team are building a decentralized publishing infrastructure to bridge WordPress users to Web3. We hope to help content creators leverage blockchain to reach the end goal of democratic publishing. Especially for heavily censored places where people don’t have the freedom to distribute and access information. What do you think WordPress would evolve in the Openverse/metaverse, and how could we deliver the right tool to the WP community? Thanks for answering my questions, and if there’s a chance, I would love to get in touch for a follow-up conversation with you or the team. – Phoebe Poon
Web3 is currently a collection of ideas, aspirations, and technologies and, in this context, refers to a decentralized web built on cryptocurrencies and the blockchain.
It’s important to note that decentralization is not exclusive or inherent to the blockchain and crypto. Solid, a project from Tim Berners-Lee and MIT, is an excellent example of this. Self-hosted, open-source WordPress sites are already a great example of decentralization on the web, where users already own their data. The blockchain itself may be trustless and decentralized, but the gateways to access it and abstract it for users might not be. Openverse is an open-source, centralized tool to enable the discovery of openly-licensed media that challenges proprietary libraries of stock photography, licensed audio, and more. – Zack Krida, Openverse project lead.
I’m curious how many people use WordPress Block Editor vs. Classic Editor, raw numbers, and percentages. I’m looking forward to tuning into the event on Dec. 14th. – Mathew Wallace
The Gutenberg plugin has over 300,000 active installations, while Classic Editor plugin has over 5 million. It’s hard to draw any specific conclusions from these numbers since each plugin serves a different purpose. Having the Classic Editor plugin provides users and clients with a choice of how to create their content, so folks who have that plugin installed could still be publishing primarily with the Block Editor.
My question is about the plugin review team: This is a very special team. It is closed, has only two members, and although we have nearly 60k plugins now, 100+ more coming every week, the team never got more members. The team has power (reject plugins, closing plugins, ban users, etc.), and it has no rotating policy, although the work is very stressful. WordCamp organizers have a rotating policy; why do we have no rotating policy for the plugin review team? And/Or how can we prevent misuse of powers here? – Torsten Landsiedel
Great question. We have had several people on the plugin review team at various points. Unfortunately, there have been cases of legal threats and illegal harassment against the team’s members, and I will not expose community volunteers to that. That said, there are other community teams involved in reviewing disputes about blocked accounts, and there are plans in place to automate any checks we can, so humans are involved in the parts humans do best. – Josepha, WordPress Project Executive Director
I am afraid that the block editor is dividing the community we are so proud of. As a long time community member, many people come to me as a “representative” person (WordCamp & meetup organizer, speaker, moderator, GTE, etc.) and complain about Gutenberg. Devs are complaining about the fast moving target, the incomplete documentation, and the changes. Users complain about full screen mode and UX problems (especially with older themes). How can you help us volunteers or the people in general to have a smoother transition? – Torsten Landsiedel
Although the recommendation is to build themes as block themes and migrate existing themes to blocks, older themes are still supported. In this direction, the Widgets Editor was released in 5.8 to support Legacy Widgets in the Block Editor and add native blocks in Widgets Areas. However, it is recommended to implement migration paths from Widgets to blocks.
With the advent of FSE in WordPress 5.9, the new Site Editor will supersede the Customizer, hidden by default. Still, whenever WordPress detects hooks that need the Customizer in themes and plugins, it will be available automatically. Further, companies participating in the Five for the Future initiative are increasing the number of sponsored contributors focused on developer advocacy and documentation to help smooth this transition. – Matías Ventura, Gutenberg project lead
PHP is a foundational language for WordPress, so many people in the ecosystem already know it deeply. That said, it’s always smart to know your software’s tech stack well. The WordPress project has benefitted so much from the PHP project and community. This sponsorship is giving back in the way that I hope companies in the WordPress ecosystem give back to our project—think of it as a proactive Five for the Future contribution to PHP. – Matt Mullenweg, WordPress project lead