The block editor finally lets editors set per-viewport styles without CSS — and the August 19 release date makes this a planning conversation to have with clients now.
The call comes in from a content editor at a health system client: the homepage hero looks fine on desktop and broken on mobile, and nobody wants to touch the CSS. The usual answer has been a custom stylesheet, a page builder, or an ACF field wired to a conditional class. WordPress 7.1 Beta 1, released July 15, changes that answer — and not in a way that should cause either panic or a shrug.
The headline feature in 7.1 is native responsive styling in the block editor. Editors can now set per-viewport values for font size, spacing, and block visibility directly in the editing interface, without writing a line of CSS. Theme authors can define custom breakpoints in theme.json. On the same release: interactive state styling (hover and focus controls on blocks), inline editorial notes with @mentions, a dedicated media editor with HEIC support, new Tabs and Playlist blocks, and a persistent editor toolbar. Real-time collaborative editing was deferred. The final release is scheduled for August 19, timed with WordCamp US.
For clients in health systems, higher education, and nonprofits — the kind of institutions we work with at daylit — responsive control has historically meant one of three things: a page builder with its own sprawling abstraction layer, a custom CSS file that only a developer can safely touch, or ACF-driven layouts where a field value controls a class. None of those are friendly to a content team trying to move fast. Native responsive styling in core closes that gap in a real way, for straightforward layout work.
Studios that haven’t already moved clients to modern block themes will face pressure to do so. Those that have can speak with authority about what this unlocks — and what it still doesn’t replace.
What it doesn’t replace: complex multi-brand theming, ACF-driven conditional layouts, and anything where the responsive logic is genuinely tied to data or user role rather than viewport. Those patterns still live outside core, and will for the foreseeable future. The 7.1 release is a meaningful capability gain, not a platform that has outrun the need for considered implementation work.
The August 19 release date is a useful hook. Clients on older themes or page-builder setups who are due for a refresh have a concrete milestone to plan around. We are already walking those conversations through what a block-theme migration looks like in practice — what it unlocks on day one, what requires a phased rebuild, and where custom work remains the right call. If your organization is on a WordPress site that still depends on a page builder for responsive control, now is the right time to scope that.
WordPress 7.1 is a genuine step forward for the platform. The work of deciding exactly what it means for a given site — that part still takes someone who knows the site.