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 Studio 1.9.0 ships a Blueprints Gallery, so you can browse, preview and launch pre-configured local sites without hunting for JSON files. It works from the Studio CLI too.
Gutenberg 23.2 adds experimental per-breakpoint block styles in Global Styles, motion design tokens, bottom-sheet modals on mobile, and fixes for race conditions in real-time collaboration.
WooCommerce is rebuilding the All Products screen on top of WordPress DataViews and DataForms. Here is what the proof of concept changes, where it still falls short on performance, and why extension authors should test it now.
WordPress 7.0 RC5 is the fifth release candidate before the May 20th launch, and it exists to catch the bugs found after RC4. Here is how to install it on a staging site with WP-CLI, the Beta Tester plugin or Playground, and what to check in your own hooks.
WordPress 7.0 development lost real-time collaboration this month over race conditions and load concerns. What’s left for the May 20 release: a native content types system, the @wordpress/grid package, and HEIC and per-block CSS fixes.
WordPress 7.0 RTC has been pulled from the release. Race conditions and TTFB regressions from bypassed persistent caching drove the call, and RC3 now moves back toward a beta state while the core team focuses on stability.
WordPress 7.0 brings real-time collaboration, and it asks a lot of the database and object cache. The Core team wants host test data by May 4th, so here is what the suite checks and where hosts usually get bitten.
WordPress wants to build Block Editor Handbook pages straight from block.json at build time. That would kill doc drift and give core blocks a reference that matches the code you are actually running.