A renovation week that started with a version number. WordPress 7.0 shipped, and the real work wasn’t the launch-day noise; it was getting the people who pay me a straight answer about what changes for them and what doesn’t. The teaching had to move the same week the platform did. I put a small free plugin on GitHub that does one blunt thing and hands you a one-click way to undo it. And I joined Post Status, which is less a task than a decision about where this work happens for the next stretch. Three of the things below map onto problems I see on other people’s installs. The last one is about why I keep showing up to do this.
WordPress 7.0 landed, and the work was the calm answer
WordPress 7.0 is out, and for a few days the whole community talks at once. The temptation for anyone who does this for a living is to talk along with it: post the hot take, ride the launch-day attention, treat a version number like an event. The buyers I work with don’t need another excited voice. They need someone to sit down and tell them, plainly, what this changes for their site and what it doesn’t.
So that’s what I wrote: WordPress 7 is here. Here’s what’s new and what to do. Not a feature tour. A short answer to the question a site owner actually has on launch day, which is some version of ‘do I need to do anything, and if so, when?’
A major version is a confidence event before it is a feature event. The people running the sites I maintain were going to hear ‘WordPress 7’ somewhere and wonder if they were suddenly behind. What they needed from me wasn’t enthusiasm. It was a calm, specific ‘here is what it means for you,’ before they had to ask.
The teaching had to move the same week the platform did
A version jump dates your teaching materials the moment it lands. Every screenshot with the old admin chrome, every ‘click the button in the top right’ that now points somewhere else, quietly goes stale. So the same week WordPress 7 shipped, I shipped the teaching to match it: the third revision of the WordPress 7 Update course, and the finished video pipeline for WordPress 101.
The WordPress 7 Update course is built for people who already know their way around and just need to know what moved. WordPress 101 is for the person who has never logged in before; my own test reader for that one is my mother, and if she can’t follow a step, the step isn’t finished. Both had to reflect the platform as it is now, not as it was three weeks ago.
The lesson travels past my own desk. When you teach anyone how to use software, whether a team, a client, or a course, the curriculum is part of the product, and it dates exactly as fast as the software does. The discipline is updating it on launch week, while the change is in front of you, not next quarter when you have forgotten which screenshots lie.
A new free plugin, and the one feature that makes it safe to use
I put a new plugin on GitHub this week: Admin Notice NoMore. It does one blunt thing. It suppresses every admin notice in wp-admin, from update nags to ‘please rate us’ banners, for teams that already handle updates and security somewhere other than the dashboard.
A tool that hides everything is a dangerous tool, because the day you need to see a notice is the day you have forgotten you turned them off. So the design question that mattered wasn’t how to hide the notices. It was how to give the person a guaranteed way back. The plugin ships with a one-request bypass: a ‘Show Notices Once’ link on the Plugins screen and a matching shortcut in the admin bar, both nonce-protected, both putting every notice back for a single page load without changing the setting. Teams that manage their sites in code get constants and filters to do the same thing.
What I want a reader to take from this: a plugin should never trap the person using it. If you build something that takes a capability away, build the door back in at the same time, make it one click, and make it safe to use under pressure. I will say plainly what the download page says: this is a sharp tool for a controlled environment, not a default-on convenience. It hides high-priority warnings along with the noise, which is exactly why the way back matters.
I joined Post Status
I joined Post Status this week, the professional community for people who build WordPress for a living. It is the one item on this list that isn’t a fix or a ship. I have been working on the web since 1996 and in WordPress since 2007, and the easy thing after that long is to assume you have already met the room. You haven’t. The craft compounds when you are around people who hold it to the standard you hold it to, and it quietly erodes when you only ever talk to clients. I didn’t join for leads. I joined because the next stretch of this work is better done in company than alone.
Also this week
- Published a piece on the WordPress government discovery call — eight questions a senior buyer should ask when they get twenty minutes with each shortlisted vendor and need the ones that actually sort the field.
The through-line this week is timing. A platform moved, and everything downstream of it — the answer I owe clients, the courses I teach from, the small free tools I hand people — had to move in the same few days or quietly go stale. That is the part of this work that never shows up in a portfolio screenshot. Not the building, the keeping-current. Joining Post Status was the same instinct turned on myself: the work of staying useful to the people who rely on you does not finish, and it is easier done in good company than alone.
Last reviewed May 23, 2026.
Rate and review this content
Be the first to rate this. Submissions are reviewed before they appear.