![\"\ud83c\udf89\"](\"https:\/\/s.w.org\/images\/core\/emoji\/17.0.2\/72x72\/1f389.png\")
Announcing GT Changelog Podcast Episode 128: Deep Dive Into Gutenberg 22.7 & WordPress 7.0 Dev Notes! <\/p>\n Announcing GT Changelog Podcast Episode 128: Deep Dive Into Gutenberg 22.7 & WordPress 7.0 Dev Notes! <\/p>\n
We\u2019re back with another packed episode of the GT Changelog Podcast! In episode 128, host Birgit Pauli-Haack welcomes JavaScript developer and full-time WordPress contributor Maggie Cabrera for an insightful conversation about all things Gutenberg and WordPress.<\/p>\n
In this episode, we unpack the highlights of Gutenberg 22.7, with a special focus on the latest features coming to WordPress 7.0. From the innovative navigation overlays\u2014earning plenty of \u201coohs\u201d from the community\u2014to the long-awaited pseudo selectors in theme.json, our speakers share behind-the-scenes perspectives on development.<\/p>\n
Birgit Pauli-Haack and Maggie Cabrera explore game-changing updates like the new breadcrumbs block, PHP-only block registration, and the emerging real-time collaboration features. They also discuss the vision for my.wordpress.net\u2014WordPress running right in your browser for ultimate digital sovereignty.<\/p>\n
Show Notes<\/a> \/ Transcript<\/a><\/p>\n Show Notes<\/strong><\/p>\n More to come. Get the full list<\/a>.<\/p>\n Tabs: Restructure Tabs Menu and inner blocks<\/a><\/p>\n Stay in Touch<\/p>\n Transcript<\/strong><\/p>\n Birgit Pauli-Haack<\/em>: Welcome to our 128th episode of the Gutenberg Changelog Podcast. In today\u2019s episode, we will talk about Gutenberg 22.7 version and dive a bit deeper into the dev notes for 7.0 that have been published as we record this on March 12th, 2026. I\u2019m your host, Birgit Pauli-Haack, curator at the Gutenberg Times and a core contributor for the WordPress open source project sponsored by Automattic. And today, I\u2019m very happy to say Maggie Cabrera joins me on the show. Maggie is a JavaScript developer and theme builder and is contributing full-time to the open source project and also sponsored by Automattic. So welcome to the show, Maggie. How are you today?<\/p>\n Maggie Cabrera<\/em>: Hi, I\u2019m really good. Thank you for having me again. Really excited.<\/p>\n Birgit Pauli-Haack<\/em>: It\u2019s been a long time. So maybe a year and a half or even two years. Yeah. Since I\u2019ve been on the channel.<\/p>\n Maggie Cabrera<\/em>: At least one year. Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. Oh, and I forgot to mention in the intro that you are also a co-developer. You were a co-developer on the Twenty Twenty-Four theme, which was one of the first full-featured block default themes. And has gotten a lot of workout through the WordPress community because I think that started when, when people started with a default theme and just adjusted things and created that for client work or for private projects. And the others were okay. And I, I really like the Twenty Twenty-three part where we, there was a community push to get more style variations in. That was really cool.<\/p>\n Yeah. I think I need to go back to them to look at those. Again, to get some ideas there.<\/p>\n Maggie Cabrera<\/em>: Yeah, I think it\u2019s funny looking back at them and how each of those themes and Twenty Twenty-Five too have like different things from it that you could, you would want to reuse today because they haven\u2019t gone out of style really. And hopefully soon we\u2019ll be able to do that kind of thing where you can, you can have multiple themes installed, be able to reuse like patterns or style variations and stuff like that. Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: And I know that people are actually working on it. There was an idea to have the template management a little bit more safe for people. Ella, I think, was working on it. And she switched the priorities to revisions for 7.0. Yeah.<\/p>\n Maggie Cabrera<\/em>: Hopefully, maybe 7.1.<\/p>\n Birgit Pauli-Haack<\/em>: I also think that that\u2019s part of it, that you can have multiple templates for the same slug. We talked about it on the show when we talked about 6.9 and what was coming from the Gutenberg. It\u2019s still in Gutenberg, but it\u2019s experimental now and you have to open it up through the experiments tab. But yeah, I\u2019m, I really like that. And then you can reuse patterns. That\u2019s definitely something. Yeah, we\u2019ll see what\u2019s coming down the pipeline. <\/p>\n So for WordPress 7.0, you worked on several features, for instance, bringing the pseudo selectors to the theme.json and patterns for the navigation overlays.<\/p>\n Maggie Cabrera<\/em>: Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. And the navigation overlays were really a got a few oohs when I demoed it last night at the meetup in Munich. And it was really cool to see. There were also some tiny things where I said, oh, I didn\u2019t know that they were getting so much excitement out of people. Revisions, of course, was one. And the other one was that you can have a paragraph now create columns. So you have just one setting and you switch it on and then you can have a paragraph display in 2 or 3 columns depending on the site.<\/p>\n Maggie Cabrera<\/em>: Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: And that is really cool. Yeah.<\/p>\n Maggie Cabrera<\/em>: Well, anyway, so yeah, the overlay work has been in the making for so long and I\u2019m so excited that that finally made it and I\u2019m really happy with how it ended up looking by the time, like the deadline of the release. I think there will still be follow-ups and stuff, but I think it\u2019s really, really nice. Now I not only worked on the patterns, but I also worked on the whole setup for themers to extend that. So a theme, a themer, but that, that was like previous work, I guess, but it all made it to the release. So a themer will be able to create a template part for the overlay to set up as a default, and also patterns. So you can have your theme will have maybe 5 different overlay patterns and then you\u2019ll select, well, this one is going to be the default and you\u2019ll assign it to the navigation block you want it to have it and you\u2019ll instantly have it as soon as you activate the theme, which is really nice. <\/p>\n I\u2019ve also been tinkering with it on my personal blog. I was like, now that I can have it, I have, because I have Gutenberg on it, I will, yes, yes, I need to put it on and change the colors and center it and put the site logo on it and all this kind of thing. So yeah, I\u2019m really excited about what other people are going to be able to do with it. I think it\u2019s quite flexible and I think it\u2019s, there\u2019s still more work to make it more flexible. Like things we want for people to be able to do something like if they want to make their overlay, like maybe always on, not just on mobile and not have it be full width, maybe only have like half the viewport, in the future, they will be able to do that. Right now there\u2019s only one thing where you can\u2019t really close it by clicking outside of it, which is the thing that we need to fix. But once we have that, the sky\u2019s the limit.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. Yeah. There was Nick Diego, a year and a half or so ago, wrote a tutorial on the developer blog about how to create mega menus.<\/p>\n Maggie Cabrera<\/em>: Yes, I remember that. Yeah, yeah, that\u2019s the next step too.<\/p>\n Birgit Pauli-Haack<\/em>: And he had this idea with template parts and then push it into the navigation bar, but of course it wasn\u2019t wired up from core, so he had to do some, some interesting workarounds. And then Mike McAllister with his Ollie Theme Builder, he had a plugin called the Menu Builder and it\u2019s in the repo. <\/p>\n Maggie Cabrera<\/em>: I think that was a big inspiration when we were working on the navigation overlay.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah, that\u2019s what I thought. Yeah. And there was a conversation between Mike McAllister and also Matt Mullenweg on Twitter and yeah, how to get this into core and I\u2019m glad it\u2019s now there and it can be, of course, everything can be improved, but\u2014<\/p>\n Maggie Cabrera<\/em>: Oh yeah, this is V1.<\/p>\n Birgit Pauli-Haack<\/em>: It\u2019s phase one. Like I explained yesterday. It\u2019s phase one. It\u2019s baby steps. It can\u2019t be fully featured.<\/p>\n Maggie Cabrera<\/em>: We iterate.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah, absolutely. Yeah. <\/p>\n So, but today, completely a different thing was an announcement. No, it was yesterday actually that your browser becomes your WordPress. It\u2019s the announcement of my.wordpress.net. It\u2019s a browser-based, signup-free WordPress built on WordPress Playground. And those of you, dear listeners, who know Playground wouldn\u2019t be all surprised how this is gonna work. But it\u2019s just, the site is private across visits because it\u2019s automatically saved in your browser. But it also offers an app catalog and one-click installs for personal CRM and RSS reader. And it\u2019s kind of a prototype for maybe seen as a WordPress democratizing digital sovereignty because you can, you don\u2019t have to put it on a central place. <\/p>\n You have it all on your browser, on your machine, and you can interact with your machine with it. It also has a hook into an AI assistant if you want to, and also some other apps. But the plugin and the WordPress still is what it is. But Matt also posted about it on his personal blog, Matt Mullenweg, under ma.tt, and he calls it the WordPress Everywhere. And outlines the strategy as well. And he can see that this one thing that\u2019s in your browser and only for you can have peer-to-peer sync with another person\u2019s MyWordPress, could have version control and also cloud publishing, which means pushing it to a host or pushing segments of it like single posts to another public website or any way you wanna kind of think about it. But it\u2019s a kind of atomic container, composable units. And you can fully roll back. You can just say, okay, I don\u2019t want it anymore. And then it\u2019s gone. But it shifts. One of the hopes, it shifts from WordPress for millions to WordPress for billions. We\u2019ll see. We\u2019ll talk about it in the next 20 years about it. So, again, so AI will enhance it. And it\u2019s the open source power is really coming to life in that vision. We\u2019ll see if we can get the product also to fulfill all those promises. <\/p>\n I got a chance to try it out in early stages. It\u2019s mainly built by Alex Kirk and he published it and then went on sabbatical. So it\u2019s kind of\u2014 what\u2019s this little baby? Yeah, took a little break and it\u2019s a, I think it\u2019s a wonderful proof of concept. It\u2019s a rough experiment, definitely. But I love the app launcher instead of plugins because it\u2019s kind of a different metaphor. Yeah, kind of if you can have this single install additional apps in WordPress, that would be so much more approachable than plugins that need to be installed and find and everything. And it\u2019s a personal note-taking app with many others out there. But this would let you connect your personal ideas with what you\u2019re doing out on the web and bring it in, in certain ways or other. So it kind of, you can kind of put it together. Say if you have a chat with your AI, you can copy paste it into your private WordPress and think about it some more and write about it or add it with other information and resources and just keep your own learning process private. But it\u2019s not in a Google Doc, it\u2019s just out there in the browser. Easy to use because it\u2019s in WordPress. But yeah, there\u2019s so many ideas that I all of a sudden had with that. So I really liked it. It was announced yesterday, so you probably haven\u2019t gotten an opportunity.<\/p>\n Maggie Cabrera<\/em>: Yeah. Yeah. I\u2019m gonna definitely check it out. Sounds really interesting.<\/p>\n Birgit Pauli-Haack<\/em>: Definitely do that. Yeah. TechCrunch also had, and I will share all the links in the show notes. TechCrunch also had a little report about it. So yeah, check it out. Of course, it\u2019s the first version as always in WordPress and it\u2019s baby steps, right? <\/p>\n Now with WordPress beta 4 being out, the first dev notes appear on the Make blog. And there are quite a few that are about the block editor. The first breadcrumbs block is coming to WordPress 7.0. And the dev note talks about the block filters. Yeah, learn how to use it with two PHP filters or customize it. And with the trail terms and also the taxonomy terms, the interface is actually more like, okay, we will, we will find out where your page is. Is it a subpage of a page section or is it a post in a category? And we put the things that we know about it into the breadcrumbs. And there\u2019s a, you can have a home link in there and you can have the current page also in the trail if you want to. But that\u2019s kind of, so yeah, I share the dev notes in, in the show notes, like we\u2019re talking about all 6 or 7 of them. So yeah. But, um, have you worked with the breadcrumbs block?<\/p>\n Maggie Cabrera<\/em>: No, I had a time when I was working on WooCommerce theme development for a little while. And I knew that that was needed and I think Woo had its own little solution. So I\u2019m really happy to see that there\u2019s something coming to core. That definitely helps for any use case, not just the commerce side. So yeah, definitely need it. Will help SEO and everything. Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. There were quite a few plugins out there. I think SEO had it already in there. So, but I\u2019m not quite sure they were all block-based. So having a block in there and you can actually put \u2019em on any page. Yeah. You don\u2019t have to put \u2019em in the template. So yeah, you can connect with. Have the visitor not getting lost so much on your big, big, big website. The next one, we already mentioned that that\u2019s the customizable navigation overlays. And see developers learn how to register and bundle the new navigation overlay and customize that. That\u2019s what you said for the mobile navigation. Yeah, the overlay, when I demoed it yesterday, it had always used as overlay. As a navigation, so the default navigation will never show. You always show the overlay, but that\u2019s kind of full page and then you have to close it. Yeah, you mentioned that already. Yeah. So how would theme developers register and bundle then?<\/p>\n Maggie Cabrera<\/em>: So there\u2019s, there\u2019s a couple of options. So they can just do patterns and tag them as core slash, I think navigation overlay. I think it\u2019s on the dev note. And that would have those patterns show on the sidebar when you create a new one. And right now you, we only have the ones that are coming from core, but if a theme bundles a few patterns more, you\u2019ll see them too. But you can also, as a themer, decide, well, I want to not only bundle patterns, but also decide right away that the header that I\u2019ve designed will have a specific overlay and they can decide which one and link it.<\/p>\n By having the attribute to the navigation block specifically. And if you want to have 4 headers for a website, for a theme, and each one of them is going to have a different overlay, you can absolutely do that. So it\u2019s, you\u2019re not tied to just one for the whole website. You can decide on a per-block basis. So it\u2019s really nice.<\/p>\n Birgit Pauli-Haack<\/em>: Awesome.<\/p>\n Maggie Cabrera<\/em>: If a theme doesn\u2019t want to do that, or you\u2019re using a theme that it\u2019s older than this feature, but you still want to use the navigation overlay, you can only need to click on the navigation block. And go to the settings and click on the\u2014 there\u2019s an overlay on this, on the inspector on the sidebar. You can create a new overlay and it will automatically give you the simple one. That\u2019s just your navigation block and the close button with a white background. And you can customize it or use one of the bundle patterns that came with the feature.<\/p>\n Birgit Pauli-Haack<\/em>: Is it possible to switch out those patterns?<\/p>\n Maggie Cabrera<\/em>: Yeah, the same way you can for when you create a new page and it will show you all the, on the sidebar or this popup that tells you all the different patterns that come with your theme, you can completely replace them.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. Okay.<\/p>\n Maggie Cabrera<\/em>: Same that you do with the query block and all these kinds of things.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. Yeah. Awesome. Yeah. So I think a lot of theme developers are going to try it out and maybe have an update to their themes.<\/p>\n Maggie Cabrera<\/em>: Yeah, I can\u2019t wait to see what they come up with.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. So the next dev note is about the changes interactivity API. And that\u2019s pretty much a new watch function, or that\u2019s implementing a new watch function for the server-side state URL and populate cleaner patterns for side effects and navigation tracking. And there\u2019s also the state.navigation is going to be deprecated. So watch out for those deprecation notices in the console log. Another dev note covers all the changes on the data views, the data form, and the field API. And there are some substantial updates in the API with new layouts, validation rules, grouping options for the table, and then picker improvements. And yeah, the whole package, I think it\u2019s now in the version 13 or so for the data views. So it\u2019s pretty great to use for plugin pages.<\/p>\n Maggie Cabrera<\/em>: Yeah. Oh yeah.<\/p>\n Birgit Pauli-Haack<\/em>: And sites. So you don\u2019t have to make any of the design decisions and keep up with\u2014 Yeah, yeah, yeah.<\/p>\n Maggie Cabrera<\/em>: Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: Your components, those are really stable.<\/p>\n Maggie Cabrera<\/em>: Yes, they are.<\/p>\n Birgit Pauli-Haack<\/em>: And it is really fun and Claude code can really work with them. Just need to make sure that it\u2019s kind of looking at the right version. So, and then there is a PHP only block registration. A lot of people, PHP developers\u2014<\/p>\n Maggie Cabrera<\/em>: Yeah, very excited about this.<\/p>\n Birgit Pauli-Haack<\/em>: Are excited about this. Yeah. Yeah, it has all the, all the details in the dev note about auto-register and also how you can with the auto-registration, you also can get all the inspector controls on the sidebar. If you enable the support for that. And I will share this also in the show notes. Brian Welcher has on his private or personal blog, wrote a whole tutorial on how to create a block like that and kind of walk you through step by step. I\u2019m sure he also did a live stream on it. Or multiple, but I think that\u2019s both of them. You can kind of look at the livestream on YouTube. So a lot of developers are really excited about that.<\/p>\n Maggie Cabrera<\/em>: Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. And the next one is about the pseudo-element support for blocks and their variation in theme.json. And Maggie, you worked on that. How does it work?<\/p>\n Maggie Cabrera<\/em>: Yeah. So this is basically just working on top of what we already have, like The theme developers can already define via theme.json support for hover, focus, focus visible, and all of these states for their blocks, like the buttons block, uh, on theme.json. But we have variations for blocks, and in particular on the buttons block, we have like the outline variation. And you could, on theme.json, change the background color for hover on your default button block, but if someone decides to use the outline, there is no way without using manually CSS to change the hover for the outline. So this, this little change adds that feature, but I think I wanted to talk about what\u2019s coming up that\u2019s not making it to 7.0, but we\u2019ll make it for the next one, which we\u2019re finally Hang on.<\/p>\n Birgit Pauli-Haack<\/em>: I have a question to the hover block theme.json. So I could do hover and focus changes also to other blocks than buttons? Is that what you\u2019re selling? Or only to the button style variations?<\/p>\n Maggie Cabrera<\/em>: Only for the way it worked before is you could do it for button blocks and elements and links, blocks and elements. Well, there\u2019s no link blocks, so the link element. You could do that. Now you can also do it on the variations. So if you have a variation that\u2019s created by core or one that you create yourself, you can also add hover for it. That\u2019s what\u2019s coming up.<\/p>\n Birgit Pauli-Haack<\/em>: So what\u2019s coming up now?<\/p>\n Maggie Cabrera<\/em>: Yeah, what\u2019s coming up is we\u2019re finally merged, I think it was yesterday, the UI for controlling adding that hover using the editor and not only theme.json. So if you, if you have your button block. You just go on the site editor, go to global styles, and you\u2019ll have on the top right, you\u2019ll have a dropdown that will let you see all the different states that your button can be in.<\/p>\n And you select from that dropdown, like hover, and then change anything, change color, change typography, change font size. You can even, we\u2019ve even tested that you can change and put it on your hover.<\/p>\n You can change the right mode and put it so it\u2019s vertical instead of horizontal. When you hover your button, it suddenly flips and it becomes horizontal.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. Wants, wants my attention. Wants my attention. Yeah.<\/p>\n Maggie Cabrera<\/em>: Don\u2019t follow that advice. Probably very not accessible.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. Yeah. But that\u2019s cool because a lot of people are just designing with the site editor and having all that UI is really important to have that. Yes.<\/p>\n Maggie Cabrera<\/em>: I think it was one of the issues that had more comments in Gutenberg, the issue, the pattern issue that I was asking for those controls.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. Yeah. I imagine. Yeah. But that\u2019s not coming in 7.0. Just clarify.<\/p>\n Maggie Cabrera<\/em>: That\u2019s, that\u2019s coming on the next Gutenberg release. So you will talk about this on the next changelog.<\/p>\n Birgit Pauli-Haack<\/em>: Yes. Yes. It will come to Gutenberg 22.8. Yeah, it\u2019s already merged, so it\u2019s in the milestone. So yeah, you have to wait another 2 weeks, but yeah, okay.<\/p>\n Maggie Cabrera<\/em>: Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. And the next dev note is all about real-time collaboration, the block editor. It\u2019s essential reading for plugin developers and to learn how the classic Meta Box disabled the collaboration mode by default and how to use the sync providers filter to customize your your transport layer, because right now it\u2019s all on HTTP and it\u2019s kind of reduced to just, I think, 2 people or 3 people just to make it also available to shared hosting. But if you have VS Virtual Hosting or Virtual Boxes or your own servers, you can actually switch out the providers and have more people being on there in collaboration. And there are some pitfalls or unintended block insertion side effects that need to be kind of looked at, not only for plugin developers, but also for site owners and agency developers. So that\u2019s definitely a very important dev note to read. Speaking of side effects, have you done any collaborative editing yet?<\/p>\n Maggie Cabrera<\/em>: No, I\u2019ve not.<\/p>\n Birgit Pauli-Haack<\/em>: On your website?<\/p>\n Maggie Cabrera<\/em>: Yeah, no.<\/p>\n Birgit Pauli-Haack<\/em>: It\u2019s really cool, but I got into some trouble yesterday. When I was demoing. Of course, live demo is always the interesting part, right? I got the notification that I lost the connection to the server. And although it was only me in there, so it couldn\u2019t have been. And so it was a little bit, I need to track it down for maybe a bug report, but could also be the technology in the room because we had some Beamer issues and it wouldn\u2019t show up, wouldn\u2019t show the dropdowns. It was interesting. <\/p>\n Yeah, I was trying to show off the aspect ratio dropdowns for the gallery block, and it would only show the active one, but not the rest of it. It\u2019s kind of very weird. I was talking and sooner or later they let me know that they don\u2019t see anything, but it was kind of weird. <\/p>\n But anyway, so, and then the iframed editor changes for WordPress 7.0. There wasn\u2019t a post earlier that 7.0 brings automatic iframing post editor, but that has been moved to 7.1. So you have a little bit of a grace period, plugin developers, because those blocks that are in version 1 or version 2 of blocks.json trigger that the post editor is not iframed. And the iframed version is actually really helpful when you want to separate concerns from the block editor and from the rest of the admin. But the big part is also not only meta boxes is not this problem there, but it\u2019s the version. And we have not seen all the things that may go wrong are actually only theoretical. We have not seen it yet. So, but we still need to do some more testing. And if it\u2019s now in the Gutenberg plugin, so if you want to test it, that would be really cool to see if your site or some of the blocks that you have from earlier block collection. <\/p>\n That are still on your website, make sure you test it and see if anything breaks. And if it does, let us know wherever you can. You can comment on the Gutenberg times, you can comment on the Make.blog or on GitHub, anywhere you want in the Slack channel. There\u2019s an outreach channel is a good place to post those as well. So yeah, we definitely need some wider testing with the Gutenberg plugin and what happens with the blocks on the earlier version of blocks. And I will do. Some testing when I get back from my travels. <\/p>\n And that\u2019s probably what I\u2019m going to do at Contributor Day in WordCamp Asia is testing some of the old plugins. I have still on my website somewhere on the Gutenberg times, I have a list of 100 plugins and some of them, I think 40 of them were block collections. So I\u2019m going to install them all and see if they break or maybe have Playground write some automation for that. Yeah, we\u2019ll see how that works. But that\u2019s definitely what I\u2019m gonna aim for. Yeah. <\/p>\n Dev notes, we are, we are kind of a little bit in the know. There are 7 more dev notes coming to, for WordPress 7. They will all be released for the field guide, which is coming out with the release candidate 1. Not the same day, but maybe a day later. And that\u2019s about the block visibility and the pattern editing. Who knew we are now supporting Unicode in email addresses? And then some simplified HTML5 tags in WordPress, then the new block support for text indent.<\/p>\n Maggie Cabrera<\/em>: Oh yeah.<\/p>\n Birgit Pauli-Haack<\/em>: Which is kind of nice too. And then the custom CSS for individual block instance in WordPress 7.0 and the dimension support enhancement that come to WordPress. So those are dev notes coming up. <\/p>\n And we are now going into what\u2019s released. And this week was a little bit of a release galore. So there was WordPress 6.9.2 that came out as a security release. And that had one bug that kind of for a few sites had a whitespace, a blank page on the front end. And that was fixed within hours to 6.9.3. But that coincided with having a release for 7.0 beta 4.<\/p>\n Maggie Cabrera<\/em>: Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: And that was kind of all one after another. And once it went out, it was found out that there were 3 security, 3 of the 10 security fixes that were in 6.9.2 didn\u2019t actually make it into 6.9.3. They made it into beta 4. So that\u2019s kind of when you have these clashes of versions, something happens. And so they had to create another 6.9 point release, the number 4. But it\u2019s really amazing how much goes into some of the releases.<\/p>\n Maggie Cabrera<\/em>: Yeah. They work so fast too. It\u2019s amazing. It\u2019s really impressive.<\/p>\n Birgit Pauli-Haack<\/em>: And how you can do this one after another. There were 2 a day and then it\u2019s really amazing. Great work for the other contributors.<\/p>\n Maggie Cabrera<\/em>: Amazing. Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: Into the night and they were handing it off from one person to the next because the time zones changed.<\/p>\n Maggie Cabrera<\/em>: <\/p>\n No stress.<\/p>\n Birgit Pauli-Haack<\/em>: It\u2019s like a release relay.<\/p>\n Maggie Cabrera<\/em>: Yeah, yeah. Like a well-oiled machine.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah, it was, yeah. But still some hiccups in there, so.<\/p>\n Maggie Cabrera<\/em>: Yeah, always.<\/p>\n Birgit Pauli-Haack<\/em>: All right, so now we come to Gutenberg 22.7. We were all waiting for that, right? <\/p>\n So the enhancements are starting not with block library. Right now, the first thing on the changelog is that phpMyAdmin is now supported by the wp-env Playground runtime. So you can then have access to the database right from your Playground wp-env local environment, which is really cool because then, yeah, you have the whole thing. It still is SQL, but it\u2019s the phpMyAdmin, what we all love and used to for the last 20 years. Yeah. To connect with the database. What\u2019s also in 22.7 is the connectors screen. That has been backported already to WordPress 7.0. And that is the single place where you can connect your website to external services. It starts with AI provider, but it\u2019s not going to stop there. It\u2019s any service that you have to connect to to get data in or get data out. You can put to the connector screen and also plugins can use it to organize the handoff of keys, API keys and connectors, security, no, we have public keys and all that, or securities. And what also happens is that the providers that are connected with prefix with AI will also register with the WP AI client. So then a plugin can push prompts to an AI that is connected if there is one available. So it\u2019s really interesting how that comes to pass. I have on my list to do kind of how you write a plugin to connect to an OpenWeather app. Just get the free key and then have your, the weather around be displayed on a website. I think that\u2019s a nice example tutorial that we could do. Yeah. And the next one?<\/p>\n Maggie Cabrera<\/em>: Yeah, the next one\u2019s a playlist block, which is ramping up, it\u2019s getting the waveform player visualization where Benny has been implementing this open source visualizer instead of creating one that we need to maintain and applied it to the playlist block, which is, I think it\u2019s, I don\u2019t know if it\u2019s going to make it. No, it\u2019s, it\u2019s going to be for 7.1 then.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah.<\/p>\n Maggie Cabrera<\/em>: Yeah. And it\u2019s looking really, really nice. I can\u2019t wait to. To have this for themes. I was just looking into the original playlist because I kind of like to do this kind of thing, which is look at all the issues that we\u2019re closing our\u2014 and it\u2019s from\u2014 it\u2019s, uh, issue 805. Oh wow, 2017. So we\u2019re doing that in 2026, which is great. Honestly, I like it. Yeah. So yeah, and it\u2019s looking so good. I love it. I can\u2019t wait. I have a bunch of friends from the Sevilla community who are podcasters, and I can\u2019t wait to see what they can make with it.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah, and I\u2019m definitely going to put it also on the Good Mythical Times. Oh yeah, for sure.<\/p>\n Maggie Cabrera<\/em>: For sure. You let us know if it fails or\u2014<\/p>\n Birgit Pauli-Haack<\/em>: Oh yeah, of course. I have opinions. I travel. Go for it. Yeah. I also know that, so our team, which is Justin Tadlock, Ryan Welcher, Jonathan Bossinger, Juan Margarito, we are all working on a showcase for a band website. And I know that Justin does the theme for it and he has already built with the playlist block and it looks amazing on those band websites when we have albums and all that. I don\u2019t know when we will release it, but it\u2019s definitely going to be for education of developers to kind of see how interactivity API works, how some of the theme features work with that. And yeah, it\u2019s going to be really cool. Just as a side note there. Yeah, there were a few blocks that hadn\u2019t had a text-align block support added to it, or they had their own implementation. And there was a big push in Gutenberg to make it available for all the blocks that have text in there. To, to do the text align things.<\/p>\n\n
Special Guest: Maggie Cabrera<\/h2>\n
\n
My.WordPress.net<\/h2>\n
\n
WordPress 7.0 Dev Notes<\/h2>\n
\n
\n
What\u2019s released?<\/h2>\n
\n
What\u2019s in active development or discussed<\/h2>\n
\n\n\n
WordPress 7.0<\/h3>\n
Announcements<\/h3>\n
Dev Notes<\/h3>\n
What\u2019s Released<\/h3>\n
Gutenberg 22.7<\/h3>\n
Enhancements<\/h3>\n