WordPress 7 Quick-Reference guide

Christopher Ross

3 min read

WordPress & CMS engineering · Fort Erie, Ontario

I put this together for site owners navigating the May 2026 WordPress 7 release. I’ve worked through releases like this with publishers and local businesses alike, and the questions I get most are about what actually changed and whether it is safe to update. This guide answers both, and I designed it to be printed and ticked off during your actual upgrade window, not read once and forgotten.

A two-page PDF cheat-sheet covering the seven things every WordPress site owner should know about the May 20, 2026 release, plus a 14-day safe-upgrade checklist you can print and tick off as you go.

What is inside

Page 1: Seven things every site owner should know about WordPress 7

  • The Command Palette (⌘K / Ctrl+K): the single biggest quality-of-life change in the release
  • AI Connectors: what the new screen is, what it is not, when to skip it
  • The new “Modern” admin colour scheme
  • Visual Revisions: the side-by-side compare view that finally works
  • The dedicated Fonts page: the plugin you can probably uninstall
  • PHP 8.3 or higher recommended: the version check you do once a year
  • The feature that got pulled: real-time collaboration removed on May 8

Page 2: The 14-day safe-upgrade checklist

Day-by-day, from the PHP version check on day one through staging tests on days three to five, fix-anything-the-clone-surfaced on days six to eight, the production update on days nine and ten, and the four-day health confirmation through day fourteen. Designed to be printed and physically ticked off, or used as a screen reference.

Who it is for

Site owners who manage their own WordPress install and want a one-page reference instead of a three-thousand-word read. Equally useful for the procurement-buyer who needs to brief their team on what changed, and for the small-business owner who took WP101 and wants the upgrade discipline written down so they do not have to remember it.

How to use it

  1. Print page 1 and keep it on the wall near your computer for the week after release.
  2. Print page 2 the day before you plan to start the upgrade. Tick each line as you complete the action.
  3. Hand a copy to anyone else on your team who logs into your WordPress dashboard, so the muscle memory builds in more than one head.

Want the long version?

The full three-thousand-word read on what changed, what matters, and what to actually do about it is at thisismyurl.com/wordpress-7-whats-new.

Want the upgrade done by someone who’s already run it on a dozen sites?

The checklist tells you what to do. If you’d rather have someone who has already worked through WP7 on a range of plugin and theme combinations handle the staging test and production update for your site, that’s a small, scoped engagement. A discovery call will tell you whether your site is a straightforward upgrade or whether there’s something in your plugin stack that needs attention first.

I put this together for site owners who need to know what changed before their next maintenance window. Not for you if you have already upgraded and worked through the release notes. This is a quick reference for site owners who need to understand what changed before their next maintenance window, not a deep-dive into the new APIs or developer-facing internals.

Download the guide

Working through something on your own site? Get in touch →

Leave a Reply

Your email address will not be published. Required fields are marked *

Your rating (optional)

Your name and email are stored with your comment; only your display name is shown publicly. See our privacy policy.