© Capturas de Video
Hi there,
This week I realized, I have been building websites for 30 years. from Notepad and hand-coded HTML to HomeSiteX over Coldfusion to WordPress, Nodejs and ReactJS to Python and Claude. It’s been a fantastic journey. It never gets old. I still learn new things every single day. I cherish most the friends I made along the way. I also found my notes about the WordCamps I attended, spoke at and organized. The first one was WordCamp Tampa in 2014. In 2026, I will probably attended my 30th WordCamp as well, Athens in December 2026. It’s a bit out, so let’s see if it works out.
Back to the here and now: It’s finally here the WordPress 7.1 Source of Truth with all the big and small changes coming to a WordPress instance near you. It’s again more like a book. Digest in small dosis.
Have a fabulous weekend!
Yours,
Birgit
On the WPBuilds podcast series At the Core, Anne McCarthy and I talked with Nathan Wrigley about WordPress 7.1. We cover responsive styling, the persistent admin bar, and richer inline notes, plus why the new image crop modal and customisable viewports change your day-to-day editing. You’ll also hear how community feedback saved the Classic Block, where the collaborative editing outreach stands, and which developer changes to test now.
Responsive styling finally lands in the block editor, and The WP Minute+ podcast has release lead Anne McCarthy demoing it with Eric Karkovack. You’ll also get the reasoning behind what didn’t make 7.1, including collaborative editing, plus how Classic Block deprecation is being paced. Anne talks about her first turn as release lead and points out hidden gems like the ‘On This Day’ widget and custom icon registration for the Icon block. The episode Why WordPress 7.1 Will Improve Your Workflow is also available as video.
More Devnotes:
There are still more to come and they will be published next week, together with the WordPress 7.1 Field Guide.
A list of all the dev notes can be reviewed from the Make Core blog
Anne McCarthy gives a candid account of the punted inherited styles indicator and its design dead ends. If you’ve ever watched someone style a template expecting it to apply site-wide, that’s the problem she’s chased since the FSE Outreach Program. Blue dots, diamonds, tooltips versus infotips, two competing reset paths — none settled, and summer holidays thinned the reviewer pool. She’s aiming at 7.2.
Last week, Gutenberg 23.6 was already released. The WordPress 7.1 tech co-lead. Aki Hamano highlighted in his post What’s new in Gutenberg 23.6? (July 22, 2026)
This week on the Gutenberg Changelog podcast, my guest was Faith Imokol from Uganda. We began with the wonderful work of the WordPress community there, who have put together a series of events — WordCamps, Campus Connect, and a website competition — bringing WordPress to schools, colleges, and universities, and to thousands of students and users. Then we turned to the latest release and had a great time going through the details. As always, the episode drops in your favorite podcast app over the weekend.
No PHP template, no shortcode, no custom block — Meta Box fields can now feed core blocks directly through block bindings for custom fields. Lua Nguyen shows the setup: select a Paragraph, Heading, Image, or Button, open Attributes in the sidebar, pick a Meta Box source, choose your field. Sources cover post, term, author, and settings-page fields, and an image field binds URL, alt, title, and caption separately. WordPress 6.5+, though the Attributes panel needs 6.9.
Coming to the Site Editor from Elementor or Divi means learning new vocabulary, and Ollie’s ground-up guide to the WordPress Site Editor by Gina Lucia covers it: templates, template parts, patterns, global styles, navigation, the Font Library, and each toolbar button, starting at Appearance → Editor. A comparison table weighs both approaches on performance, flexibility, and portability. Ollie-specific tips sit alongside the core explanations, so you can read past them if you use another theme.
A typical Elementor page ships 200–400 KB of extra frontend assets, three to five times a native block build — the number behind Bikash Pun Magar‘s case for custom Gutenberg blocks over page builders on client sites. You get conditional per-block asset loading, HTML you control line by line, and content stored in native block grammar rather than a proprietary format. He’s fair about where Elementor still fits: prototypes and solo builders wanting pixel control without code.
The theme.json schema resolves to more than 40MB across hundreds of nested properties, which is why Sérgio Santos built a form-driven visual editor for theme.json as a VS Code extension. Fields come from the official schema rather than hand-written forms, and a weekly scan of core and Gutenberg adds experimental properties with honest badges. The feature Santos says changed his workflow: every preset shows the CSS variable name it will generate as you type the slug.
There’s also a companion WordPress plugin that mounts the same editor under Appearance. There will be dragons though: Santos flags it as an experiment as it overwrites theme.json in place with no revisions or backups.
“Keeping up with Gutenberg – Index 2026”
A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test, and Meta team from Jan. 2024 on. Updated by yours truly.
If your custom blocks touch the global window or document, WordPress 7.1 will break them. Ryan Welcher walks through the forced iframed post editor canvas, landing August 19th with no flag to check and no opt-out. Five demos cover viewport detection, click-outside handlers, editor styles, admin body-class CSS, and unmaintained third-party libraries, with fixes using ownerDocument, defaultView, useRefEffect, editorStyle in block.json, and patch-package. His demo plugin ships broken and fixed versions of each.
Welcher also published a detailed tutorial: The post editor is going full iframe: what block developers need to know before WordPress 7.1
Some people still assumed every Playground was temporary. Persistence, multiple sites, Blueprints, file editing — all already there, just easy to miss, which is what the new WordPress Playground interface sets out to fix. A customizable Dock gathers those tools into one bottom toolbar: New, Playgrounds, Blueprint, Site Settings, Database, Files, Logs, Export. It’s navigation, not new capability. The design came out of the Playground table at WordCamp Europe Contributor Day, after Adam Zieliński used AI to explore 400+ variations.
Point a coding agent at WordPress Playground and it reads an instruction file first. The wp-playground agent skill now splits that file into a 52-line router plus focused references, so your agent loads the CLI details only for a local run and the sharing rules only for a share link — encoding, CORS, public hosting. Fellyph Cintra‘s four-scenario benchmark scored 24/24 against 22/24 for the old version, one run per prompt. All this is explain in more details in the post One Playground, three workflows: Consistent agent guidance across surfaces in the team’s Make Blog.
In a third post, Fellyph Cintra walks you through programmatic site management in WordPress Playground: from DevTools you can list, create, save, rename, and switch sites, change PHP or networking, and run PHP inside a site to check active plugins. Order matters — temporary sites must be saved before you can rename or reconfigure them.
One caveat worth knowing if it runs alongside the other Playground item: this API belongs to playground.wordpress.net only. It isn’t in the @wp-playground/client package, the CLI, or embedded Playgrounds via /remote.html — those need the JavaScript API instead.
Carlo Daniele‘s guide to the Abilities API for plugin developers stays on fundamentals: the input schema, output schema, callback, and permission check that together form an ability’s contract, and the WP-CLI commands that let you inspect one. A fresh install ships three — site info, user info, environment info. His example registers an audio-to-blocks process from an existing plugin and triggers it over the wp-abilities/v1 REST route.
Where Carlo Daniele registers a single ability, Jonathan Bossenger composes three into your first AI-powered WordPress plugin. Two call the AI Client, a third orchestrates them via wp_get_ability() and execute(), turning an image URL into a draft post. The same ability then answers over curl, from a React settings page, and from Claude Desktop through the MCP Adapter. Gotchas included: base64 data URIs for vision providers, stray markdown fences, and request timeouts.
One rule for this stream: no hand-written code. Ryan Welcher takes a full WordPress site build with Studio Code end to end for his son’s hockey team, and you watch a custom post type, a teams taxonomy, an Advanced Query Loop roster, and junior/intermediate/senior tabs come together by direction alone. The highlight is the agent reaching for block bindings unprompted. The lowlight: rogue PHP metaboxes, and a PHP-first answer where he wanted a SlotFill.
Need a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.
Now also available via WordPress Playground. There is no need for a test site locally or on a server. Have you been using it? Email me with your experience.
Questions? Suggestions? Ideas?
Don’t hesitate to send them via email or
send me a message on WordPress Slack or Twitter @bph.
For questions to be answered on the Gutenberg Changelog,
send them to changelog@gutenbergtimes.com
Featured Image:
© Redes Sociales
Login
