WordPress 7.0 shipped this week, and within a day I had three messages that all asked the same thing in different words: are we okay? None of them came from people who follow release notes. They came from a department manager, an editor, and an office administrator who had heard the number ‘7’ somewhere and felt a small cold drop in their stomach. That is what a major version actually does to the people who pay me. Long before it is a feature event, it is a confidence event. Somewhere out there a sentence with a big number in it made them wonder if they had quietly fallen behind overnight.
So the week was not really about the launch. It was about getting those people a straight answer before they had to ask for one, and then making sure everything I teach from still told the truth the day after the platform changed underneath it.
The job on launch day is the calm answer, not the hot take
For a few days after a release like this, the whole community talks at once, and the temptation for anyone who does this for a living is obvious: post the take, ride the attention, treat a version number like a holiday. The buyers I work with do not need another excited voice in that pile. They need someone to sit down and tell them, in plain words, what 7.0 changes for their specific site and what it leaves exactly as it was.
I have learned to write that answer more than once. The same explanation went out three different ways, because the version that landed for an IT director was not the one that landed for the department manager who approved the update, and neither of those reached the editor who only wanted to know whether her publishing day was about to break. The platform changed a single time. The explaining had to change with each person who read it.
That is the work I put out: WordPress 7 is here, and here is what to do. Not a tour of every new toggle. A short reply to the only question a site owner really has on launch day, which is some flavour of ‘do I need to touch anything, and if so, when?’ The honest answer for most of them was ‘not today, and I will tell you the day it matters,’ and saying that out loud was worth more than any feature list.
Teaching materials date the moment the version number changes
A version jump ages your course the instant it lands. Every screenshot wearing the old admin chrome, every ‘click the button in the top right’ that now points at empty space, goes quietly stale while you sleep. So the same week 7.0 went out, I shipped the teaching to match it: the third revision of the WordPress 7 Update course, and the finished video pipeline for WordPress 101.
Those two courses are built for opposite ends of the room. The Update course assumes you already know your way around and only need to learn what moved. WordPress 101 assumes you have never logged in before in your life. My test reader for that one is my mother. If she gets stuck on a step, the step is not finished, full stop, and I rewrite it until she sails through without phoning me. Both courses had to reflect the platform as it stands now, not as it stood three weeks ago when the old recordings still looked current.
This part travels well past my own desk. Any time you teach people to use software, whether a team, a client, or a paying course, the curriculum is part of the product, and it goes off at exactly the speed the software does. The discipline is updating it on launch week while the change is still in front of you, not next quarter when you have forgotten which screenshots are lying to you. The same timing trap caught me last week from a different angle, so I went into this one already watching for it.
A blunt little plugin, and the door it had to keep open
I also put a new free plugin on GitHub this week: Admin Notice NoMore Thisismyurl Dashboard Notice Control. It does one blunt thing. It hides every admin notice in wp-admin, from update nags to ‘please rate us five stars’ banners, for teams that already track updates and security somewhere other than the dashboard.
Building it taught me something I keep relearning. A tool that hides everything is a dangerous tool, because the day you finally need to see a notice is the same day you have completely forgotten you switched them off. So the design question that actually mattered was never how to hide the notices. It was how to guarantee the person a 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 touching the saved setting. Teams that run their sites from code get constants and filters that do the same job.
What stayed with me from the build is small and stubborn. If you ship something that takes a capability away from a person, you owe them the door back in, built at the same moment, one click wide, and safe to reach for when they are already in trouble. I will say on the download page exactly what I will say here: this is a sharp tool for a controlled environment, not a default-on convenience. It hides the high-priority warnings right alongside the noise, which is precisely why the way back has to be there.
One more piece, for buyers across the table
One other thing went out this week that is not a fix or a ship: 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 instead of flattering it. Different audience, same instinct as everything above. Hand the person the thing that helps them decide, before they know to ask me for it.
Why I joined post status
The last thing I did this week was the only one with no deliverable attached. I joined Post Status, the professional community for people who build WordPress for a living. I have been on the web since 1996 and in WordPress since 2007, and the easy mistake after that long is to assume you have already met the room. You have not. The craft compounds when you are around people who hold it to the standard you hold it to, and it quietly erodes when the only people you ever talk shop with are paying you to talk.
That is the same instinct that ran through the whole week, only pointed back at myself for once. All of it, the calm answer I owe clients, the courses I keep current, the small free tools I hand people, comes from one stubborn belief that staying useful to the people who rely on you is not a project you finish. It is a thing you keep doing, every release, every launch week, for as long as you do this. I joined Post Status because that work goes better in company than it goes alone, and because the next stretch of it is long. If you would rather hand that keeping-current to someone whose job it already is, that is what I am here for.
Leave a Reply