When Matt Mullenweg announced last year that Josepha Haden and Joost De Valk would take significant new roles in WordPress leadership, I was excited. My excitement with Josepha is in evidence in a post about some of her public work from February. What I hoped would happen is that the stepping in of two independent people with annointed roles would be the creation of something resembling a leadership structure. Clearly, per Joost’s testimony, that isn’t quite what happened (for his part). I’ll lead you to get the full details from his very good and honest (seeming) post.

I received with great interest this latest post from the folks over at Delicious Brains. They successfully highlighted the most compelling part of their data to me: how much money people who identify as WordPress developers make. But more than that, they also captured a number of other interesting facts and figures about the roughly 400 people who answered their survey.

It looks like the WordPress.org plugin review team (which often means “Mika Epstein,” who is without a doubt the most dedicated and prominent member of said team) is looking to clarify and extend the guidelines about plugin admin notices in WordPress. You know those things that clutter up *a lot* of screens on *a lot* of the Dashboards of WordPress sites clients, friends, etc show you? Yes, let’s celebrate Mika’s pushing to clarify the rules and make these a little less common.

I’ll be honest: Since Gutenberg launched, I’ve used the Classic Editor plugin to disable it on every site I work on. I do this for a few reasons:

If you’re neither worried about PHP internals nor PHP 8, skip this.

Next Thursday, I’m giving a talk at SiteLock. If you’re a person who has thought about learning how to develop WordPress themes for a while and never really gotten around to it, this is the perfect talk for you. We’ll cover things that make the whole of WordPress theming make sense. The idea is that we’ll essentially cover the prerequisites so that you’ll be better able to make sense of the next steps and maybe ever dive right in.

The WordPress Governance Project working out who we are.

When putting together WordPress Security with Confidence, one of the best sources about actual WordPress site comprises was the Sucuri hacked website report. While a lot of WordPress security content (including my own) is informed by a small number of real and important first-hand exposures to WordPress security issues, in a given year Sucuri has literally thousands.

“Expert roundup” on what’s next.

I’m not a WordPress core contributor. I don’t write the code, and I don’t make it a priority in my life to be contributing to the Marketting, Accessibility, WP-CLI, Support, Themes, or any other of the volunteer teams that keep WordPress a healthy ecosystem. And I don’t know enough of the people who do that work to claim to have my finger on the pulse of what’s going on for them.