Transcript — Episode 0006: WordPress 7: Better Interface, Careful AI
Who’s speaking, and how. Christopher hosts in a professional clone of his own voice. The named guests — Frances, Walter, and Owen — are AI-synthesised personas built from ElevenLabs library voices, each one written by Christopher Ross. About the cast: https://thisismyurl.com/stances/i-disclose-every-use-of-ai/
Christopher: I’ve been publishing on WordPress for almost twenty years, and I can count on one hand the releases that made me stop and notice the software actually getting out of my way.
Christopher: WordPress 7 is one of them. And I mean that as a compliment, which is not where I expected to land.
Christopher: There’s a new AI layer in this one, and the easy story is that it’s either magic or it’s the end of the open web. Neither of those is true, and honestly, neither of those is interesting.
Christopher: The question I actually care about is whether WordPress 7 made the work better, or just made it faster. And this is the first release in a while where I think the honest answer is both.
Christopher: Let me start with the part that’s just good news, because there’s a lot of it. The interface is calmer. Better hierarchy, cleaner panels, less distance between writing a thing and seeing how it’ll look.
Frances: I’ll back that up. My team noticed inside a week. We spend less time fighting the screen and more time actually shipping.
Christopher: Right? And if you publish every day, those tiny frictions add up to something real. Saving someone four seconds a hundred times a day is a gift.
Walter: This is what a mature release is supposed to feel like. Not loud. Just fewer little interruptions between you and the thought you were trying to finish.
Christopher: Walter, that’s exactly it. That’s the line I’ve been reaching for.
Frances: Here’s the only place I’d slow us down. People bundle the whole release into one feeling. “WordPress 7 is great” quietly turns into “every new thing in it is equally trustworthy.”
Christopher: And they’re not. They’re not even the same kind of thing.
Walter: A cleaner panel and an AI that writes a paragraph for you sit in completely different risk categories. One changes how far your mouse travels. The other can change what you actually say.
Frances: So let me push, Chris, because I think the room’s being a little precious about the AI. If it gets my team from a blank page to a usable draft in half the time, that is value. Full stop.
Christopher: It is. No argument from me — I use it that way myself.
Frances: Then why are we treating it like something to be careful around?
Christopher: Because — okay, let me back up, that came out more cautious than I mean it. I’m not careful around it the way you’re careful around a stove. I’m careful with it the way I’m careful with a really fast intern who’s eager and occasionally confidently wrong.
Frances: Ha. Okay, that I recognize.
Christopher: The speed is the gift. The judgment is still the job. When you ship a draft you didn’t actually read, the rework shows up later wearing a disguise.
Walter: And the old WordPress lesson holds here. Anything that helps you make more, faster, also makes more of whatever you fed it. If the care doesn’t scale with the speed, the speed turns on you.
Frances: Sure, but “governance” is usually where momentum goes to die. Every team I’ve watched bolt a process onto this ends up slower than before.
Christopher: Only when the rule is vague. A vague rule is just guilt with extra steps.
Walter: So make it specific. Here the rule can be one sentence: the AI is allowed to draft the structure, and a person has to own the meaning.
Frances: That’s cleaner than most of the policy docs I’ve actually paid for.
Christopher: And it protects the thing that’s hardest to get back, which is voice. Left alone, this stuff drifts toward the middle of the language. Toward fine. Nobody remembers fine.
Walter: Especially when you’re writing to repair something. An apology, a correction, a hard update. The nuance is the first thing that gets sanded off, and the nuance was the whole point.
Frances: Okay. So you’re not anti-AI. You’re anti-shipping-it-unread.
Christopher: That’s the whole stance, yeah. Use it boldly. Just read it before it goes out with your name on it.
Owen: Can I make this something a team can actually do on Monday?
Christopher: Please. That’s the part I always want.
Owen: Put every WordPress 7 feature into one of two buckets. Bucket one: anything that reduces friction — the panels, the navigation, the layout tools. Trust those by default. Turn them on and move on with your life.
Owen: Bucket two: anything that generates words or claims on your behalf. That bucket gets one rule. Nothing leaves it without a human read.
Owen: Let the machine save you the hour. Don’t let it spend your credibility.
Frances: Oh, that’s good. That’s deployable.
Walter: It keeps everything you gained, and it fences off the one place you could quietly lose something.
Christopher: And it gives a manager a single sentence they can hand their team tomorrow morning. I put the two buckets on a one-page sheet you can keep next to the keyboard.
Christopher: So here’s where I’ve landed, and it’s a genuinely happy place to land.
Christopher: WordPress 7 made the daily work better where it counts — focus, flow, the feeling of the tool being on your side. That’s not a small upgrade. That’s the kind that earns loyalty.
Walter: Useful assistant. Not the author.
Frances: Right — and the honest final pass is the whole game. That’s what I was missing.
Owen: Build that habit once, and the whole release turns into a clean win.
Christopher: There’s a thing that came up when a few of us talked about the WordCamp talks a while back — the tools change every single year, and the judgment is the part that lasts. WordPress 7 is a genuinely good tool. The judgment’s still yours, and honestly, that’s the best part of the whole release.
Christopher: Better interface. Careful AI. Mostly, though? Better.
Christopher: Thanks for spending this one with me.
Christopher: This is Sites I’ve Never Seen. Next time, we take that one-sentence rule and run it through a real editorial workflow, on a live site, and see where it bends.
Christopher: Glad you were here.
End of episode.