WordPress Guidelines keeps agent memory, skills and instructions in an ordinary custom post type, and it’s headed for Core. Here’s what that means for plugins with their own memory stores, which permissions to test first, and when a separate table still makes sense.
WooCommerce’s beta AI Product Advisor ranks your catalog and suggests copy fixes. The ranked queue and revert log are the useful parts. The WordPress.com connection and the lift math are where it bites, so stage it, clear stray output first, and apply in small batches.
WordPress.com shipped Write, a minimal editor that still saves ordinary block posts. I compare it with distraction free mode and the Classic Editor, note what it hides from writers, and say which kind of site should get which.
The media editor modal is now the default way to edit images in the block editor. Its Save button changes the block instance, not the attachment or its generated sizes, and that matters a lot on a WooCommerce store.
WordPress has retired the “beta” label for PHP 8.3, 8.4 and 8.5 support, and 7.0 no longer runs on anything below PHP 7.4. Here is what changed and why it is time to stop treating PHP 8 as experimental.
WooCommerce.com now runs its production store on Nightly WC Core. An AI-assisted pipeline handles patch replays and diff reviews, and the setup has already caught a dropped 15GB index before it could ship in 10.8.
WordPress 7.1 is planned for August 19, 2026, with a smaller release squad that leans on the Make Team Reps. Here is the schedule, how to test the alpha with WP-CLI, and which lead roles are open.
The WordPress AI plugin 1.0.0 adds Request Logging and Connector Approvals, which give site owners real control over which plugins use AI and what they spend. Here is what changed and what developers should do about it.
The latest WordPress.com sprint brought Jetpack Podcast, the WordPress Workspace Mac app with an AI agent, and a Blueprints Gallery in Studio. The common thread is local-first development and less repeated setup work.
WordPress 7.0 ships on May 20, 2026. Here is what the dry run and the 24-hour code freeze actually involve, and what I’d test (IIS, older PHP, multisite) before the release party in #core Slack.