Hi,
We are sprinting towards a new WordPress version, and the two months until the final release will pass quickly! The Roadmap to 6.7 is now available.
If you’ve got a ton of websites to manage, whether you’re a product owner, agency dev, or consultant, it might be a good idea to get that testing schedule lined up. The release cycle schedule for WordPress 6.7 helps with that, for sure.
I just looked at the latest on Data Views in the site editor—super exciting stuff! It’s going to be a big part of the WordPress admin redesign, and you’ll be hearing and reading more about it soon.
For now, have an awesome weekend and soak up the last bits of summer. I can’t wait for the fall colors to start in Bavaria!
Yours, 💕
Birgit
PS. If you house your products on the WordPress repositories, this post is for you. Upcoming Security Changes for Plugin and Theme Authors on WordPress.org. Set-up 2FA now. Don’t procrastinate!
PPS: And if you have the feeling that this edition is too short, I bet, you haven’t read all the articles listed in last week’s edition. 😝
Developing Gutenberg and WordPress
The design team published the first update of a series on the progress of Data Views in Data Views Update #1. “This update is the start of a series to provide more frequent information about the latest and greatest, so folks can follow along, provide feedback, and explore using this component. It builds on the initial update shared in June and will share biweekly updates going forward as it remains helpful.”
If you are moved to start exploring the Data View component for your plugin, you get a head start reading through JuanMa Garrido’s Using Data Views to Display and Interact with Data in Plugins, where he explains how to add a React app to a plugin page and use the Data Views component to display a data list.
Thanks to the effort of release leads, Tonya Mork and Vicente Canales, the release candidate 1 (RC1) for WordPress 6.6.2 has been available since September 4th. The final release will be on September 10. It entails 15 fixes in Core and 11 fixes for the Block editor. Quite a few commits and PRs were dealing with issues caused by the lowered CSS specificity. It also fixed the bug around the derivative state for the Interactivity API and the post editor connected to iframe rendering. The list of all fixes are available in the RC 1 release post.
🎙️ The latest episode is Gutenberg Changelog #126 – Gutenberg Releases 22.3, 22.4, 22.5 and WordPress 7.0 with special guest Carolina Nymark, author at fullsiteediting.com and long time contributor.

Joen Asmussen outlines a cross-team effort, that’s on the way to Advancing the WordPress Design System. “The goal, specifically, is to bring together existing tools like @wordpress/components, the new Figma library, and Storybook into a unified design system reference site that anyone can use to contribute back to WordPress or extend WordPress in line with a shared design language. ” he wrote. Asmussen also pointed to the Storybook of car manufacturer Audi, to illustrate how something like this could look.
Jyolsna JC at WPTavern reports on the WordPress 6.7 Roadmap Includes New Default Theme, APIs, and Media Enhancements. “Anne has cautioned that the new features mentioned in the post are being actively pursued, but doesn’t necessarily mean each will make it into the final release of WordPress 6.7.” she wrote.
Reminder: Live Developer Hours will take place on September 10th at 15:00 UTC. A First Look at the Template Registration API in WordPress 6.7 Join Justin Tadlock and Nick Diego to discuss the feature and how to use it. Tadlock published a tutorial on the WordPress Developer blog last week, that might give you a head start. Join the Developer Hours to get your questions answered.

Upcoming Online Live WordPress Tutorials
The training team has added a few more online tutorial on the roster on Meetup:
September 10, 2024, at 9:00 am UTC: Setting up a WordPress blog
September 11, 2024, at 12 am UTC: Creating Your Own Contact Form Plugin
September 12, 2024, at 14:00 UTC: Exploring the Query Loop block
Plugins, Themes, and Tools for #nocode site builders and owners
Colin Newcomer take First Look at the Upcoming Twenty Twenty-Five Default WordPress Theme. “Looking at the preview images, it kind of makes me think of Ikea – and that’s a compliment! I like its minimal looks and I think there are some great-looking patterns that users will be able to play around with.” he wrote.
Bud Kraus of JoyofWP posted a valuable tutorial on how to create a simple style guide for your WordPress website on Hostinger blog. While big companies have designers for Style Guides, small business owners or freelancers can use the WordPress Site Editor, respectively the Style Book tab as their tool. The tutorial helps you make choices on color combinations and block styling to ensure a consistent look. Documenting your decisions ensures you’ll know how to update your site in the future. Kraus has notes for you depending on if you’re working within a block theme, a classic theme or with Elementor page builder.
Press This: podcast is back and host Brian Gardner discussed with his guest Rich Tabor how WordPress as a design tool empowers users to create unique designs using the platform’s versatile tools. Tabor emphasized how important user-friendly feature are for a flexible design.
Theme Development for full Site Editing and Blocks
Anne McCarthy invites you to help testing the Block Bindings UI, that’s still an experiment in the Gutenberg plugin. She shared on her personal blog all the information you need, including a demo video and the Playground link to a test site

Building Blocks and Tools for the Block editor.
In the upcoming Developer Hours: A First Look at the Template Registration API in WordPress 6.7 Justin Tadlock and Nick Diego will demonstrate will default front-end output demonstrate the basics of registration and how to integrate custom fields, block variations and more. Your questions will be answered in the Q & A portion of the event.
Nick Diego published on his personal blog how it enabled linked Group blocks in WordPress and took a slightly different route than Damon Cook in his post on the developer blog. Diego walk you through his thinking on implementing his vision on what’s necessary for the block editor view as and how he tackle the challenge on the front end. The final result is quite intriguing.

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