July 1, 2026 — Gutenberg 23.5 shipped July 1 with three threads that pull the editor closer to being a real design surface: a canvas that resizes to any width so responsive styles finally preview where they’re authored, cropping precise enough for a photo desk with the Cover block now inside the same modal, and a governance lever that switches real-time collaboration off per post type. Where the last two releases hardened the plumbing — uploads, sync, React runtimes — this one is about control and visibility: seeing what a layout does at every width, and deciding where features apply.
Key Themes
- The editor canvas can now be dragged to any width, with blocks appearing and disappearing at their breakpoints live — the responsive preview that per-block styles have needed since 23.2.
- Responsive style states expand to aspect-ratio, flex-alignment, and text-shadow, so more of a design system can vary by viewport instead of shipping one fixed treatment.
- The media editor’s cropping got precise — a magnified canvas, pixel-snapping handles — and the Cover block finally opens the same in-place cropping modal.
- Real-time collaboration can be disabled per post type, handing publishers a governance lever to keep co-editing off sensitive content.
- DataViews’ configuration API and REST endpoint moved core-ready, and Grid shipped as an installable npm package — both signs of platform pieces hardening for reuse.
Jump to: 📱 Design at Any Width · 🖼️ Cropping & the Cover Block · 👥 Collaboration’s Kill Switch · 📊 DataViews · 🧱 Platform Packages · 🔧 Smaller Updates · 💡 Takeaways
📱 Design at Any Width
The editor canvas is no longer locked to Desktop, Tablet, and Mobile presets. It can be dragged to any width via resize handles, while the device-preview dropdown still offers preset jumps for the common breakpoints (#75121). As the canvas narrows, blocks respond dynamically — appearing and disappearing at their configured breakpoints — and a new responsive-editing toggle in the preview dropdown turns that behavior on. Alongside the canvas work, responsive style states extended to aspect-ratio, flex-alignment, and text-shadow (#78795), and text-shadow arrived in Global Styles proper (#73320). ThemeProvider added corner-radius presets (#78816) and became a public export from @wordpress/theme (#78664).
Why this matters: 23.2 introduced responsive styles keyed to the viewport; 23.3 made them per-block. Both shipped without a way to see the result short of saving and loading the front end at different sizes. The resizable canvas closes that gap — a designer can drag the width down and watch a Columns package collapse, a hero swap aspect ratio, a caption’s text-shadow soften, all in the editor. For a design-system team governing dozens of templates, that turns responsive review from a front-end QA pass into an authoring-time check. The expanded style states compound it: the more properties that can vary by breakpoint — now including aspect-ratio, which decides how a lead image reflows on mobile — the less a newsroom hands off to CSS a developer maintains outside the system.
🖼️ Cropping Gets Precise, and the Cover Block Joins In
The media editor modal introduced in 23.3 kept sharpening. Cropping gained a magnified canvas for fine adjustments (#79044) and crop handles that snap to source pixels (#79139), and keyboard resizing now works correctly for locked aspect-ratio crops (#79207). The bigger reach: the Cover block can now open the media editor modal to crop its background image in place (#79258), where before cropping a Cover image meant editing it in the Media Library and swapping it back. The modal also gained loading and error states (#79101), and the current post is now always included in the initial media options (#79467).
Why this matters: 23.3 gave photo desks the cropping modal, 23.4 hardened the upload that feeds it, and 23.5 makes the crop itself exact and extends it to the block most publishers lean on for hero and section headers. The Cover block is everywhere in feature layouts — a background photo with an overlaid headline — and until now its cropping lived outside the editing flow. Pulling it into the same modal means an editor building a homepage feature composes and crops in one place. Snap-to-pixel handles and keyboard resize are the details that separate a toy cropper from one an art director will actually use on deadline.
👥 Collaboration’s Kill Switch
Real-time collaboration can now be disabled per post type (#78984). Separately, the code-editor cursor no longer jumps to the end of the document when a remote change syncs in (#79005). Both land on top of the persistence-and-sync split and CRDT fixes from 23.4.
Why this matters: The collaboration arc has been about earning trust through reliability — 23.3 and 23.4 were both maintenance-heavy. 23.5 adds the first real governance control: turning co-editing off for specific post types. That’s the lever a publisher’s legal, compliance, or standards desk asks for. Co-editing suits the newsroom’s article and feature types; it’s the wrong default for a legal-review CPT, an embargoed-financials post type, or anything with a single accountable author. Per-post-type disabling lets the platform team enable collaboration broadly and carve out the exceptions instead of facing an all-or-nothing switch. It’s a small PR with outsized governance weight — the piece that lets co-editing ship inside a regulated newsroom.
📊 DataViews Edges Toward Core
- The DataViews configuration API and its REST endpoint were made core-ready (#79347), with view-config requests able to fetch a property subset via the
_fieldsparameter (#79355) and endpoint changes brought back from core (#79438). - The Revisions screen adopted the picker-activity layout (#77333), and block bindings gained list-item support (#78947).
Why this matters: DataViews is the framework WordPress is standardizing its admin list screens on — the posts table, media grid, and pattern browser all trend toward it. A configuration API that’s core-ready, plus _fields to request only the columns a screen needs, is the groundwork for custom admin experiences built on the same primitive rather than bespoke tables. Publishers running custom editorial dashboards — assignment desks, content-audit views — should track this as the supported path those screens will eventually sit on.
🧱 The Platform Ships as Packages
@wordpress/gridwas prepared for an experimental 0.1.0 npm publish (#79071), turning the Grid work from 23.4 into a distributable package.- The dashboard rebuild continued its extraction into standalone packages:
@wordpress/widget-primitives(#79134) and@wordpress/widget-dashboard(#79268) were pulled out, with widget primitives decoupled from a hardcoded endpoint (#79322).
Why this matters: The experimental dashboard is now a five-release arc, and its parts are becoming consumable packages rather than admin-page internals. Publishing Grid as 0.1.0 and extracting the widget packages is how the platform team turns in-progress features into pieces a custom build can adopt. For anyone sketching a newsroom home screen — the editorial-calendar-and-publish-queue vision the dashboard arc keeps gesturing at — packaged widget primitives are the first sign that becomes buildable outside core.
🔧 Smaller Updates
The minimum requirement moved to WordPress 6.9. Gutenberg 23.5 requires WordPress 6.9 or later (#79196) — a compatibility floor to confirm against production before updating the plugin.
Client-side media processing advanced. VIPS bumped to 0.0.18 for high-bit-depth AVIF support (#79179), the VIPS WASM binary was inlined as compact UTF-8 instead of base64 (#79188), and uploads gained an error taxonomy with localized messages and diagnostics (#74917) — the continued build-out of in-browser image handling and the resilient-upload work from 23.4.
The File and Icon blocks picked up polish. File combined its audio, video, and image transforms into one path (#79242); Icon gained flip and rotate controls (#77017) and now inserts a default icon instead of an empty placeholder (#79111).
Performance and accessibility. The Markdown converter migrated from showdown to marked (#77953); the Dashboard H1 reverted to “Dashboard” with a corrected heading hierarchy (#79251); media fields avoid losing focus when the current parent detaches (#79468); and PHP unit tests now run on 8.4 and 8.5 (#79260).
Bug fixes. Fixes resolved a pattern-override bindings crash (#79092), pasted images stretching when their dimensions were preserved (#79067), nested lists being lost when binding list-item content (#79346), and crop-canvas pinch zoom (#79332).
💡 Takeaways
- Pilot responsive authoring on the resizable canvas. Put a designer on a live template, drag the width down, and confirm your per-block responsive styles — now including aspect-ratio and text-shadow — behave the way the front end does before relying on it for review.
- Move Cover-block cropping into the editor flow. Test the in-place crop modal on your hero and feature layouts; if it holds up, retire the Media-Library-and-swap-back workaround from your editors’ routine.
- Decide where co-editing does and doesn’t belong. Use per-post-type collaboration disabling to enable it on articles and features while carving out legal, embargoed, or single-author post types.
- Confirm the WordPress 6.9 floor before updating. Gutenberg 23.5 requires 6.9 — check your production version and any managed-host schedule before the plugin update.
- Keep watching DataViews and the packaged dashboard. The config API going core-ready and the widget packages being extracted are the trajectory toward custom, supported newsroom admin screens — inventory what you’d want there.
The full changelog is available on Make WordPress Core.