July is the month the WordPress 7.1 cycle gets real. Beta 1 lands on July 15, betas follow weekly through the end of the month, and the final release is scheduled for August 19, 2026, timed with WordCamp US. If June was about wrapping up WordPress 7.0, July is about deciding what you need to…
If you’ve been watching the Core AI projects land and wondering how the pieces fit together in a real plugin, then this post is for you. We’re going to build one together, step by step, focusing on how to implement each of the three AI building blocks.
Build a branded maintenance mode for WordPress block themes: add one small hook, then manage everything—design and activation—in the Site Editor.
Stop duplicating WordPress block theme templates just to load different sidebar content. Learn how to use the render_block_data filter to dynamically swap template parts based on post category, page context, or any conditional logic — no extra templates required.
WordPress 7.0 is out, and the 7.1 cycle is already asking developers to test media processing, React 19 compatibility, collaborative editing, theme style states, and Playground workflows.
Learn how to use the WordPress AI Client to build a provider-agnostic plugin that generates images directly within the Media Library.
Stay up to date with the latest Gutenberg and WordPress 7.0 developer updates for May 2026, including the evolving content types system, new grid package, block improvements, API changes, and key fixes impacting themes, plugins, and editor workflows.
Learn how to set up Playwright for WordPress E2E testing and write tests using real-world examples so you have a solid foundation to adapt for your own project.
Learn about all the new updates coming to WordPress for developers, covering plugins and tools, theme updates, and the new Playground MCP Server.
@wordpress/build replaces webpack and Babel with esbuild, auto-generates your PHP script registration from package.json conventions, and requires zero config. It already builds all 100+ Gutenberg packages. The plan is for it to power @wordpress/scripts under the hood — so wp-scripts build stays the same, but gets faster and drops the hand-written PHP. The API is…