 Alright, welcome everybody. My name is Nick Diego. I'm a core contributor and sponsor contributor by automatic. We are going to be chatting today around about 6.3 which is coming up. Originally on like the meetup schedule we're going to talk about some ways to extend the editor from like a theme perspective. I'm going to be presented by my colleague Justin Tadlock unfortunately he is in the middle of a storm down in Alabama and doesn't have power so if you won't be able to join us today. But I think we still have plenty to talk about and you know, I'm going to present a little bit about 6.3 and then we can just have kind of a casual discussion around block theming things that people are seeing things that people want to see in WordPress, maybe things that are preventing them from adopting block themes that sort of thing. I think we'll still have a good discussion even though we're missing Justin, which means for our July hallway hangout we're probably going to focus pretty much exclusively on how to extend the editor from a theme perspective and Justin had and I'll share some work that he's doing to give you a sneak peek at that later. But he has some really interesting ways of providing some really neat UI within the block editor for those that are building themes which is which is pretty cool so save that save that for the next one. But what I was so I am currently I'm one of four but I'm one of four editor triage leads for 6.3 6.3 is the next WordPress releases coming out. So I'm going to drop in just for those that aren't familiar with the kind of the timeline we have. So this is the timeline for WordPress 6.3. So, even though the release isn't until the beginning of August. The release goes through numerous steps to in order to make sure that it's ready to distribute to 43% of the world or internet. And so the first step in that process is what's called beta one, the first beta for 6.3. So that's actually happening next lesson two weeks from now on Tuesday the 27th. And so, in these last kind of week and a half, it's kind of the mad rush to get as many enhancements as we can into 6.3. Yeah into 6.3, because as soon as beta one starts really no new enhancements can go into 6.3 now there are some exceptions if there's an enhancement that's really tied to a new feature and all the core contributors agree that it should be in there. It's known as blessed and brought into the release but for all intents and purposes, new functionality new features really stop once we get to beta one and then from beta one all the way until the release it's bug fixes making testing making sure everything still works fixing bugs fixing regression that sort of thing. So like it was a good month or so to make sure the release is in order. So, what I wanted to do today is kind of showcase some of the stuff that is coming in 6.3 to kind of give you an idea of what's changing and fair amount is, especially when it comes to the interface of the editor, how you work with, you know, especially block themes obviously that's the main focus of everything right now. And so that hopefully you know the folks in this room here are the more, I guess in franchised WordPress users than most people using WordPress right and so you were the you were the bleeding edge of WordPress and so being able to install the latest version of Gutenberg test some of these new features find bugs there will be bugs and help us get WordPress in the best spot possible. If you if anybody is willing to do that that would be awesome so one of the, I know many of you have already participated in this. But we run a call for testing. And so there is the current call for testing right now covers a lot of some of this new functionality. And some of you in this room have already participated and shared your feedback. Thank you for that. And there, you know, a lot of this is new, it's and we'll dive into this so we have a visual look at it but there's a lot of different editing flows happening in the site editor now and new flows new functionality introduce some maybe wonkiness maybe confusion. This is where you know we have that next month or so to kind of sort some of the stuff out. But if you're looking for an easy way to help test the call for testing which I just linked in the chat is a great way to do that. And so, kind of back to the timeline. So, again, 6.3 beta one is going to come out on two weeks from Tuesday, past Tuesday. Yesterday, we release Gutenberg 16.0 and Gutenberg 16.0 is the second to last Gutenberg release and I'll put the release post in the chat. This is the second to last Gutenberg release before the beta one. So we have 16.1 with the which will start going out the release candidate will go out next week. So if you're looking to test like what's going to be in 16, 6, 6.3 what are the things that I'm going to be fading contend with testing, you know, 6.2 the current WordPress release 6.2.2 with Gutenberg 16.0 or soon 16.1 will give you a really good look at what's coming for 6.3. And then obviously once the beta comes out, you can also install and use that as well. So, let's just dive in I want to show you some of kind of the top level improvements or enhancements or changes that are coming in 6.3 and then we can kind of open the floor to discussion things that people are excited about worried about with like to see chain added whatever we can have a nice conversation about that. But I wanted to kind of kind of set the stage for those maybe who haven't explored some of these new features yet, just to kind of see see where we're at. So I'm going to share my screen. And here we have a nice blank WordPress install. So I'm going to make this a little bigger. Okay, so whenever I share my screen I like to make sure people are very clear on what's being used here. So I am using just a blank. Stock WordPress install 16.2.2. And for plugins, I'm just using Gutenberg 16.0.0 I'm not using Gutenberg trunk or anything like that I'm just using the version of Gutenberg you can download right now from the plugins repo. And I'm just going to be using the 2023 theme. I do have a child theme here, just for some added functionality it's not going to pertain to this, this talk here. It's like my child you might build all my examples off of so but it's just 2023 into the hood with some minor tweaks. So, right off the bat, they're the biggest changes I think from a visual perspective, come in the site editor. So let's just head on over to the site editor and see what this looks like. I'm actually going to go back. And we're going to watch this again, because one of the big changes is actually the loading state. So if you're familiar with the site editor in 6.2.2 it's a mouthful. Whenever you would load the site editor it would sometimes like, it would like stagger into existence like parts of it would load at different times. And it kind of creates like a jarring experience for folks. And so what changed in it will change in 6.3 what changes now if you're using the latest version of Gutenberg is when you load the editor you'll get this loading black screen with a little spinner. Now I will, I, this is a seemingly very small thing, but for folks that have fairly large WordPress installs especially if you're using a lot of, you know, third party plugins or extensions. Simply testing this is really helpful because we've heard some reports of folks who have really big websites, you know with hundreds of users that that loading screen all this refresh again takes quite a bit to look. And so that's something that we're keeping a close eye on. So if you have like a big demo site or even a site that you is using a block theme and you feel comfortable testing this, that would be helpful. I personally have had a hard time replicating that really long load time, but it has been reported so, but that is one of the small changes that's been made to the site editor. And what you'll start to see is, in a lot of different places like a, like a polish or refinement on a lot of some of this functionality. And it's just to try and make, you know, the site editor has been in existence for a long time it's gone through numerous iterations and 6.2 we remove the data tag, obviously a lot of improvements are still coming. But the goal kind of for 6.3 is to try to tighten it up, make it feel a little bit nicer, instead of like coming into existence and pieces now there's like a loading screen that sort of thing. The other thing that you're going to see is a lot more functionality in the sidebar. So recently we have styles now so you can change the styles, your style variations right from the sidebar panel. And you also notice that there's a bunch more icons here. So you can jump right to the storybook and you can see your storybook right from within you know this panel you don't need you can of course go into it here like you did could before, but you can do a lot more right from the styles panel. So again you can edit styles and back and forth so this this kind of flow of, you know, allowing people to change their style variations without, you know, having to dive into the actual editing come over here browse styles and change them. It's just trying to make me a little bit more user friendly, especially for new users. So this even, you know, there's going to be a lot that's coming in 6.3, and there's going to be even more that's going to be coming in 6.4. So some of this is not the one 6.3 comes out it will be. I hesitate to say this but good enough, and then it will be improved on in the future, and one of the big areas is pages so this actually just came out, what came out previously, but a lot of improvement here was made in the last 16.0. Now you can see all the pages on your site. And this is pretty handy, especially if you have individual page designs that you know are pretty unique instead of having to go to the pages section of your site and edit those designs and then jump back to the site editor maybe to make a global styles change. All of that within the site editor. Now this flow is brand new, and I expect that there's going to be some bugs that are going to be fixed in the next month. But you can do a lot here, you can add a new page, which is pretty cool. Now note that this adds it as a draft. This adds it as a draft so there isn't like a published flow like you would have in the normal post and page editor where you could you know create a page and publish it. You know functionality a post and page editor you can add a featured image yet you can't. There are no meta boxes you know it's a fairly limited editing editing experience the idea behind it, is it really is focusing on that global styles site editing, where you can make changes to the page, make changes to global styles and kind of design at your site all within one place so let's just add, you know a sample page so. Let's do a draft page. And now you can see that now we're in the page. And so if we go over to this panel here, you know the normal settings panel. Now you'll see that this is broken out where we can see we can. The biggest challenges with content editing within the site editor is knowing what you're editing are you editing the pages content or you're editing the template. And this is something that's being explored on how do we know how do we make this. People understand like what are you editing. And so one of the iterations of this now is right now I am editing. You can see over here, it kind of shows me what I'm editing here I'm editing the post featured image now that the title and post content. If I, but I can't click on the header, and I can't click on the footer. It's not letting me do that, but I get this little pop up this says, do you want to edit the template that you know that this page is using. And you can also click over here and click edit template and when you do this. Now you can edit the template for the any generic page that that page that we just created was using. Getting used to this flow is going to it takes it takes a bit and there also might be some improvements based on community feedback so again if anybody has time to test it. Share their feedback, you know that's really helpful. But now that I'm in this template. It's like well how do I get back to my page. There's a back button here. Once you know it's there. It's easy to remember but if you don't know it's there you might be figuring out how to make it back to where I was right so you can click back and then you'll go back to your page and now you're back in your page and you can, you know, add your content, like so. So this is again a brand new flow for how to manage content and manage design within the site editor when it comes to content editing. And if you click on back on the sidebar you can see some meta information about the page for example there's no featured image, the status the slog and so forth. There's some very few limited things like delete the draft page, but you can't publish. You can add that featured image. I expect in the future that that will come at least as far as I've seen that isn't quite in the roadmap for 6.3. Basically it's around stabilizing this flow making it show you can at least do some editing with pages within the site editor. So, I'm going to stop there I see we have a lot of comments and chat. Let's see what we got here. So is this stuff for editors and admins only. I could be wrong. I always hesitate when I say this, but it's the site editor is is you need to have admin level permissions for the site editor. So this right now is just restricted. 39% share please someone correct me, you have to be an admin to access the site editor. Now you could of course have so this is it's powered by permissions. So whatever I always forget whatever the permissions that an admin has, if you have like a, like a role management plugin that allow you to create additional roles user roles, you could theoretically create like designer and give them access to the site editor as well. So this is the site editor is quite locked down. This is something that I've heard from a lot, you know how do we allow people to edit, you know, an editor, allow them to edit like just navigation or just the footer and nothing else. That doesn't exist yet. But it's, it's like one of those really common, commonly requested things that I think we're going to need a solution for the future at some point. Okay. Thank you, Justin for sharing that. So it is a whole lot better now I encourage folks to really get in there and try it because it's at least for me, it, it was, it's such a different editing experience, especially for those of us that have been in WordPress forever. You know, I usually like my, you know, you go to your page you edit your page like everything is very disjointed right where the site editor is trying to pull everything into one place. And with that there are going to be some issues I was chatting some people this morning about how like, well now that I have pages. Why don't I have everything else. Why can't I do my future damage why you know why can't I do all the stuff that I normally do on a page in the site and it's just a lot to bring into the site editor right now, and to think about that flow. It takes some thoughts so understand that the 6.3 is going to be kind of the first iteration of this like bringing everything together. Because phase three is we're basically finishing up phase two now phase three of the Gutenberg project is really around like workflows and collaboration and it's really around like this editing flow stuff. So, you know, it's a big it's a hard thing to solve but also a very exciting thing because I've been starting to use this more so now where I can just edit all my pages right in the site editor I can change the global styles. You can do a lot of the design work that you would normally do in one place and you're not jumping back and forth from from page to page. There's some exploration around templates like sometimes like templates are kind of confusing like the 404 page on a site. You think of it as the page but it's actually a template. So that's why you're seeing 404 and search in the pages section, because for a user. Under the hood we know there's a differentiation there, but like from a user perspective, or even my own perspective. I want to edit my pages. I want to edit the 404 here like I'm in this section. I'm kind of in that flow of editing. I want this to be in one place. So that's why some you see some of these templates surface under pages. This is the home icon. This is to indicate that this page called home is actually using the front page template. I can show you this more example so let's let's create a post page. Create a draft here. Save that. I'm going to go back to my settings and we're going to go to reading and we're going to set the home page. This is to blank page and we'll do post page. I was not published sorry I need to publish the page before it will let me do it. Everything. All right so this post page will be our blog. So I'll come back over here into reading. We'll change that to post page. I'll go to the site editor. You'll see okay this is a little hard to see but see how there's like a little icon here and there's a there's a there's a home and then this little icon for posts. So it's very subtle. Once you know what it means. Again, it's a little hard to know what it means, but you can see which page has been designated as your front page and as your blog page your post page. So, again, little things and I think this might be improved you know making it a little bit more clear. Again, if we click on posts. Yeah okay so over again this is hard to tell but here you see that it says the home, this is using the home template, or if I click back over here on blank page. This is using the blank template because that's what I had set up there. Anyway, we'll trick you to understand how we surface this information and make it clear I think is going to be a big thing this actually comment came up in the in the call for testing so you'll notice little things here and there, related to how these pages work What else do we have the next big thing is the library. So you'll notice here that there's no template parts, template parts are now part of what's being called the library. The library is pretty cool but it's also in development. So the library is where all your template parts are, but eventually this is also be a place where it can be stored in reusable blocks will also be stored. So you can see right here that there's a link for manager usable blocks. Currently, this links to the old hidden page reusable blocks. Eventually they will be pulled into this library. There's also conversation around patterns being able to pull save patterns automatically that will get pulled in here as well. So the library the libraries this kind of the library it's going to contain a lot of different stuff and temple parts patterns reusable blocks. Now there's one thing I want to mention about reusable blocks and patterns, and this you will have, you may have seen on the roadmap for 6.3. So I'll drop this in the chat. Very, I will admit a very ambitious roadmap for 6.3. Zoom in a little bit. There we go. Okay, so one of the things that was called out here if you scroll down a little bit is the evolve the WP pattern block. And what this means is so those familiar we've had the reusable block, and we have patterns. And there's been a lot of community hope for what are called partially synced patterns. So the problem with a normal pattern you insert it. And then if you ever want to like update that content like the design of it later, you can't you'd have to go into every instance of where that pattern is and update that design. The other kind of synced pattern is that you could update the design of the pattern but the content would change. So if you put the pattern a bunch of different places and change like the heading and the image in this pattern. Those would say the same but if you change the design of the pattern, you know, change the color or whatever, those will be updated across all the pattern so it's like partially sync patterns. So you have reusable blocks where it's fully synced right if you have a reusable block in many places you update it, they all change. So you see how we have like these three different things, not synced partially synced and synced. So this effort to evolve the WP pattern block is to bring all that functionality into one thing. That has kind of three different states, not synced partially synced fully synced which will be reusable blocks. So that's why you're seeing this library idea come together because it's a place to house that one thing that has these three different states so normal pattern partially sync pattern reusable block. That work is still being done. People are folks are working in earnest to try and get that ready for 6.3. It's a very complicated thing to handle. We all have fingers crossed that that will make it in. But if you want more information about it you can come to the roadmap and check out this evolved WP patterns block for a lot more information around this, this, this approach. But either way this kind of consolidation instead of having like all these different things to talk about. It's really one thing with three different states, much cleaner approach. When implemented and when handled correctly, especially within this library is going to be really, really cool, you know you can create a reusable block or the temple part, create a pattern, save them all manage them all. So very exciting to see that but that's what you're seeing with this library that's kind of a vision, moving forward with the library. Right now it's just a place as a 16.3 to how is your template parts, kind of set the stage for for the future. See here if anybody has any questions. If anybody does have questions feel free to raise your hand or just say stop and say something this is supposed to be relatively casual so you know feel free to just speak up. Okay, so Jeremy saying a very good point I actually commented so commented in this earlier. So the problem with reusable blocks in the editor is you have a wide width cover block or whatever you put it inside of reusable block and now it's constraint. That is part of this process right to figure that out and that that's been a long standing issue forever. And I think that for whatever reason it's been kind of ignored because it's been a very hard problem to solve. But as soon as you have this discussion of pulling everything into one will now you need to solve that problem. So I fully expect that part of this process is maybe some of these long standing issues the reusable blocks will get fixed because now they have to be because we're pulling everything into one thing so there is an issue with for sure with with the current user we use a lock implementation. Let's see here. Yeah footnotes is another big one footnotes is another big one let's see is that on here. I will there's a lot on this on this roadmap and I think we're getting it's ambitious we're getting pretty close, but I fully expect some of some of the stuff to get punted. So that's such as the way with an open source project and and how we move forward. All right, let's see here so that's the library. Okay, so now I want to talk about questions. Yeah, go for it. Justin. Justin, you're the top of my screen so why don't you go first. Okay, thank you. So I think you did gloss over it for briefly but I was just wondering about how if there were any plans to kind of. You've got a lot of great content functionality building out within this site as so. So I'm just wondering if there was any future plans to kind of fine tune the access because at the moment it's a very catchable with just the edit theme options permission and that's it really. At our agency, we kind of need to have editor access to the site editor but only certain bits. So at the moment what we're doing is we're having to kind of filter the rest API callbacks to kind of like give editors only certain access to certain template parts and things like that. So just, I was just wondering if there was any, any thoughts about kind of being able to fine tune, maybe not permissions but at least hooks or something that we can hook into because I'm aware there's already kind of like that with blocks where you can filter the available blocks or you can add, you know, remove, insert a support for certain blogs that you don't want users to be able to directly insert and things. Absolutely, so I think that I'm going to do a shameless plug here. So this might be interesting for you this does not solve your problem, but this might be an interesting article if your terms of like permission so there's a lot of cool. So there's a lot of cool client side filters like at least for the post editor that allow you to restrict functionality whether it's setting or styles all that kind of stuff for blocks so just as an aside. My biggest concern is where you're concerned. We were at this, you know, a year ago, the site editor was nothing compared to what it is now, you know, we didn't have any of this stuff and so it's really great that we've gotten this far. So now we need to address the concerns of folks like yourself who want to use this in a bit more of an enterprise is the right word but a bit more of an advanced setting where you need to now that we have like the basics there and everything kind of works. We now need to start being able to conditionally control certain things, especially for much permissions, and that's it. So, I'm kind of beating my own drum, and this is not just me I think there's a general consensus among my contributor community that as we look at 6.4 extensibility and configurability needs to be a cornerstone. Because how do you use this functionality for, you know, in a client setting right now you have to give them access to everything. And that's not really what you want to do. And so, unfortunately for 6.3 there's not much function, there's really little when it comes to extensibility, but that is really hopefully there's a bunch of us pushing for this going to be a really focused part of 6.4. This is not promoted yet but we're actually going to hold a developer hours very similar to this hallway hang on, but a little bit more, a little bit more developer-y at the end of the month last week of the month to talk specifically about extensibility, talking about like what do we have now and what do we need to for an agency setting for an enterprise setting. I fully hear you, it's everyone very well aware of that I think a lot of the focus in the last year has been just getting some of the basics in here. How do we edit margin and padding on content, you know, things like that, but we're at this point now or the site editor is going to be adopted more broadly, it needs the tools like you're saying. All right, thank you very much. Someone else had their hand up but now I'm not seeing it. You did have your hand up. Brian answered my question in the chat. Oh, perfect. Okay, cool. Brian doing good work there. Okay, so I want to I want to show you some things that are not as important as a site editor, but I think are really cool. So, maybe they're not, but the first thing, which is something that we hear a lot. I want to add a new page. When we have a new WordPress release. It can be scary for people who have been building with a block editor and building with block themes from the last year, because they were building on a bit of a shaky foundation because things are changing things are being improved. There are implementations that they made if they had custom CSS maybe they had custom code to make blocks work the way they needed to in their workflows with each new big WordPress release things change. And that can be problematic, especially implemented this custom stuff and I need to figure out is my custom stuff still working what changed. I want to call out this because this is something that most people, not most but a lot of people who use the query loop block, probably have custom code on it, especially CSS because here's my custom here's my query query loop. So if you have your, your query loop. Previously there was no way to control the space between each of the items in your query loop. And furthermore, under the hood, the, the way that the layout for the query loop was done was a little bit funky. And so I myself, as an example, had custom CSS to handle it and make it look better desktop versus mobile that sort of thing. Well a lot of improvement was recently made. And now you can control the space between the elements using block spacing. So this is really cool because this makes it consistent with something like your columns block has block spacing this can also be controlled and themed up Jason, which is great. So this little minor change I wanted to call out because I know I had to update some custom CSS, you know on my query loops for the impending 6.3 so know that this functionality is here now. It's great from like a use case perspective, but you may because you can so easily now just configure all of this. But know that you might need to change some custom code if you have it. The other thing about the query loop query block is that settings have changed a little bit so you'll notice here that we have our listing grid view. This these settings used to live on the pick and open the list here. They used to live in the query loop itself they used to be here. All that has moved down to the post template. So the post template is like the template for the posts. And this is where that stuff lives now. And so just if you're looking for certain settings know that that has changed. So the query loop all the settings for the query loop are very specific to controlling the query itself, whereas the post template is more about controlling the style you'll notice that there's no styling elements on the query loop. All of that live on the post template itself. Well, the one exception is the layout settings are on the query itself because that's kind of the outer container and that's what's going to control wide size, you know none so forth. I am seeing an interesting situation here where my images are overlapping testing folks, figuring out why that's happening. I think it's because the aspect ratio is set on these featured images here. So aspect ratios. Yeah, it is. Okay, so aspect ratio is another thing that's being worked on currently 46.3. So that's why we're seeing that here, because I have forced it to be square, even though it is not a square area, and it's not being constrained because I have it set to 400. So little things like that, which, once you know why it's happening are easy to fix but you know a little drawing for for for users. So I want to call that out, because it's a it's a subtle change but one that can be highly impactful. The other thing that I want to show you here is changes to dimensions. So this one I've been clamoring for for a long time, because let me go to a simpler blog let's just go to a heading. So, before, if you wanted to have like all your margins all your paddings, it would just like extend like it would be like this tall in the dimensions in the dimension panel. So this entire dimension settings have been overhauled, and this will take it all works the same so it's nothing like will break or you know there's nothing you need to do in terms of like adapting to this change is just a really nice change that might take a little bit to get used to but I think it's great. So you can now control if you wanted control just horizontal and vertical so you can see here in little, let's zoom in the little bars tell you what you're doing top and bottom, right and left. And you can do just top, you can do you know obviously just bottom, and then if you want fully custom you can do custom, but again it's a much more condensed interface and it was previously. It's a very small minor thing, but something that I think is nice to see as part of that polishing effort that we're seeing where there's a dedicated group focusing on just how do we improve these little things improve the experience so it's easier to use. What else here. See if there's any questions. Any navigation updates. Lots. So navigation I think it's interesting navigation has been like one of the most complicated things ever to build for better or worse. And let's go into the editor here. I am not very well versed on all the changes to navigation, but let's add a menu here. I have a simple menu. One of the things that you're going to see, which is so I forget if this was in 6.2 or how much of this was in 6.2, but you can do a lot now within so we now have this additional list view panel, and you can do a lot with managing your menus in this sidebar. So we have our list view here, but the benefit of this approach is that adjusting this stuff was always very hard like hitting the right thing was always a challenge. And so there's been a lot of refinement to how this all kind of functions. When you click on the link itself you're going to get all the settings over here. So the big improvement is, and this is this was part of 6.2 was the ability to see your navigation over here. So this is not terribly new, but there have been a lot of refinements to it. So you can see when I go to my navigation and I click on a page, how. That was interesting. Navigation menu is missing. I'm wondering if this is not actually linked to anything. Oh, maybe the page got deleted. Interesting testing folks testing. But anyway, so, you know, unfortunately, Justin's not here for those that maybe came later, Justin was going to attend as well. He's a co host, he was going to show some ways to extend and talk about like building out additional functionality for teams. When it comes to navigation this is an area that I think is kind of a big topic because navigation is something that I this is my personal opinion I don't reflect. The project as a whole. I think that navigation is a really hard thing to get right in given how many different ways websites implement navigation is going to be incredibly hard for this singular navigation block to account for everything. And so I think that the changes that are being made are done to improve the navigation make it clear for relatively simple navigation. I think once you get beyond simple navigation to things like mega menus and you know things like that. You really need to step outside of the navigation block in kind of classic WordPress where you have that navigations menu and you had all your net menu areas and that sort of thing. Menus were very much more closely tied to a theme. And depending on what you're trying to do again this is just my own opinion, depending on what you're trying to do, you may be better serve to build a custom block and build your own implementation. So one of the interesting approaches to this is, I'm calling out WordPress VIP because they wrote I don't know I don't have the article handy, but their mega menu here, this kind of approach. This is all blocks, but it's custom. It's a custom block. And these are custom template parts that kind of slot in here. So, it's an approach that I would imagine the developers working on the navigation block would pull their hair out trying to how do you build this type of thing into the navigation block. But it's actually, you know, with if you're familiar with building blocks which I know not everybody is but if you're familiar with building blocks it's actually not challenging to build something like this. So, I think navigation the core functionality around navigation like simple navigation making sure it works making sure you know some, you know, the majority of sites that just need simple navigation are serviced by that navigation bar. Once you get to something more complicated. I think this is where you can do something custom with a custom block and custom functionality, the benefit. Yep, go for it. We have a question from Lisa. Yeah, go for it. I'm just saying, how do you save multiple navigation types like if you have different types of menus, you know, a mini menu versus a full menu. Because this only shows one navigation, right. At least from the sidebar, I'm seeing only one. So, oh, that's, that's because I just have one. So, the, so you can create, let's come back over here. So if you're creating just like another one, another variation just so we can just see what happens. I can do afterwards but I just thought it asked. Yeah, so if you want to create a new menu, you can care will you want to create a new navigation menu. There's more than ones that are saved, but you can create a new menu and build out, you know, whatever you want in the navigation menu. I'm actually curious what you're talking about with like the mini menus and that sort of thing. Can you expand on that. Because with this you could build like a header menu and a footer menu and a sidebar menu that sort of thing. And then how will they be represented in that black sidebar where it says navigation. That's what I wanted to know. Gotcha, got you got you. Thank you. So this is something that is still being worked on. So, again, personal personal opinion zone. I think that this section should pull in all your menus. Let's just say I think it will. I think it will. I think it will show. Yeah, perfect. Okay, because previously would only show your most recent one. So I think that this did change recently. So, Nick, you can also show how to rename. Navigation, because that's kind of tricky. You have to go into the section. Very good point. So we are renaming menus is hard and I put in an issue this morning to change this. But right now, you can if you're on your menu, you have to go over to settings, and then down to advance and then you can change the name of your menu so let's change navigation to or something like that. There's no interest for that as well, because we kind of discussed that earlier, but they didn't really know where to put naming, and it's kind of still up in the air. They don't really know where to put the naming of it because that would be kind of like, it would be also affecting other blocks that also have some kind of naming in it. So they're kind of having that consideration as well. Absolutely. And things like this were in this and this is kind of where like the sidebars. It's just a current implementation more functionality to come. So when you're in here, you can't, it would be great if you could come in here and maybe change the title of this. Like once you start seeing some of this, like, oh, can I change the title right here, right now you only can move up down or move page. Things like that. In the future, you can, you might be able to add, you should be able to add more functionality. Right now it's a fairly basic implementation. I am not the most up to date on all the navigation changes, but I do know that the team has been working very hard with all sorts of improvements around navigation. And one more comment in relation to navigation and when you're in a page and you want to switch from the navigation as possible just kind of go into the chain, the three dots to create a new menu you can also switch navigation to another navigation. Oh, right. Yeah. So, because here you can basically switch between menus. So let's say if you're on a unique page or something you want another type of menu, you just go into that area in switch navigation and you just save the page. And by the end that you have for this page or that template you will have that you'll be using that navigation. So that kind of goes back to some of the stuff that Lisa was talking about as well. Yeah, yeah, yeah. So like for example if you had like a header menu and a footer menu. And you were creating a brand new page. This is, let's get rid of this. This is a brand new page and you had, you know, some content. And you wanted to add the menu at the bottom. So you created that footer menu by default is just going to add the first menu in your thing. You can just change that over your footer menu and I have your menu. I'll add the latest menu that's been modified into whatever has been worked on. Yeah, these flows are still being worked out but it's, it's getting much better and much more powerful and I think that let's just quick a quick look here. Let's look at pages. See how we have some of these icons this allows you to draft a new page. You see the three dots here to delete. And this is to edit. You can imagine that functionality also coming to navigation. So for example, perhaps you could add a navigation right from this panel, or when you're in the footer menu maybe you could delete it or you could change it that sort of thing. So now that we have these pieces in place you can start to iterate in your mind like forward or like what could come. It's relatively new but the goal for 6.3 is just to get it to a point where everything that is there works well. New functionality can come but everything that is here works well without any without any issues. Let's see here. Is anybody okay so we only have 10 minutes left is anybody have anything that they're excited for or a question about want to see. I want to say that doing a call for testing is a really good way to actually just see the new features because you go through step by step instructions. So it is a good way of learning about what is coming. And as a reminder, here's the link again for the call for testing. Oh, so I think we're going to save this for the next hallway hangout but I can give everybody kind of a sneak peek at the additional functionality I think is kind of interesting so. When we look at core. And I think my apologies. For getting the gentleman's name who is talking about being able to control accessibility or who can access the editor. There's a lot more functionality around. You know, how do you. So let's come in here. If you're looking at a block, you have all the different tools over, you know, on the sidebar here, you can turn some of the stuff on and off in theme that Jason. Controlling how this looks or what the defaults are may seem very minor but if you're trying to set up a site for a client or set up for yourself, maybe you won't control over this functionality. So core has done a really good job of adding the functionality, you know, making sure that we have padding and margin on paragraphs that sort of thing. Now, we need to showcase how you can either turn that off or configure it. So that was an article that I wrote recently. And then Justin has done some really interesting explorations into adding really niche functionality that maybe core will never add itself. So this is he's actually going to he's planning to write an article about it for the developer blog, but he also has and you can see what this kind of looks like, drop it here and also put it in the chat. So this is he's calling it when block styles are not enough. So he has a lot of design functionality and core, you know, color and whatnot, but it doesn't do everything. So he has some explorations here around things like text shadows, and a visual interface for changing markers and bullets on lists. Again, that's something you could do a CSS, but wouldn't it be cool if in your theme, or in the editor, you could provide that functionality. So we've done some really interesting explorations that under the hood are actually quite simple. I don't want to, I don't want to cut him short, like it's, it's simple in concept and the code to implement it is not overly challenging once you understand how it works. But once you do, you can start to think about how you as a, you know, if you're building a theme for somebody or you're building it for a client, how you could add a little bit of niche functionality, where, instead of having somebody put in a class or something, they actually have a UI to change the, you know, what a list looks like. And he also has some really interesting explorations around color variations and colored groups. So I just want to provide a little sneak peek at this. I think next hallway hangout we're going to talk more about basically, how do you take, use the editor is your foundation I use WordPress for is your foundation. How do you go beyond that or niche functionality when it comes to block themes, because, as we all know WordPress core only goes so far and that's why we have a plug plug in ecosystem themes so on and so forth. So a lot is in core, but I think that as we transition to kind of this workflow phase. We're really going to be focusing on workflows, you know, editing pages, you know, editing navigation, editing functionality as opposed to adding tech shadow for blocks that sort of thing some of the stuff might get included. But it's really more about improving the editorial workflow of WordPress making things work more appropriately. As far as like niche functionality. So that might still come but a lot of it might go into the realm of plugins or extensions or something like that. And so we wanted to show you how you can do that with themes in a pretty elegant way so that should be an exciting one in July, hopefully Justin's powers back on by then. And yep. There's a list block PR from Glenn Davis and hopefully we will see additional style options for the list blocks coming into WordPress 6.3. I saw that. So yeah, so that'll be great. Yeah. So we have five minutes left so what I wanted to do is I wanted to give go back to talk about 6.3 just really quickly and kind of do a behind the curtain thing. So I only really got involved in core. And then half ago, all of this stuff is completely foreign to me, like how do these, how does this stuff get in how does release work. So I want to spend like few minutes just kind of showing what the process is going to look like, as we head into 6.3. So there is a project board. It is the 6.3 editor tasks project board. As we head into, so as we head towards beta one, I would put this in the chat too. So as we head into 6.3, the beta one, this project board is going to get very busy. This is where we triage all of the issues and enhancements everything that needs to go into 6.3. So it already kind of looks like a lot. So we have this triage column so this is where we're collecting issues that are really impacting 6.3. It's a new feature coming into 6.3 and it breaks something. That's where the stuff is coming in. Once we triage them and we really haven't started this yet because we're still a few weeks from beta one. But once they start getting triage they get started getting moved through this process. They go into in discussion, they go into to do, then they go into in progress needs improvement or needs review so on and so forth. So if you're running into an issue. And you're like, what the heck, this is a really good place to see if that issues already been surfaced and already is in this process. If you do not see your issue on this board. So I highly encourage you to either add an issue on GitHub. If you've never added an issue before you don't feel comfortable doing that. Please reach out to me. Or beer get polyhack. Let's see here the. So this road map. Sorry, that's not what I wanted. There we go. So on this the core 6.3 release. This is tells you who's involved in the release. So the editor triage leads are and McCarthy beer get polyhack for us. I apologize for us. Subalia and myself. So if you run into issues you're not comfortable creating an issue. Please reach out to us. We will help through that process. We want to make sure every critical bug gets flagged and gets on this board. As we head into 6.3 because this is what the engineers and contributors are going to be working off of to make sure the releases goes as smoothly as possible. So, but it's also a good way to check if you're running into an issue and you see it here as well. And I think it's also interesting just to see what's happening in kind of kind of a command center behind the scenes. All right, we have a minute left anybody have any last thoughts are they are you scared are you excited about 6.3 all the above mixed emotions. Yeah excited for the high coups exactly. Yes. It is pretty crazy it's already June and we're already looking already starting to think about 6.4. So, well thank you everybody for attending. Justin couldn't join us. Very valid reason storms in Alabama, but we will see you next next month in July we don't have a set date yet, but we will get that published relatively soon. In the meantime, if you can you have time please do that the call for testing. And again if you in test and check out Gutenberg 6 point 16.0. If you have any time issues. Reach out to any just shout shout and and we'll we will get that flagged and hopefully taking care of so. Thank you all so much, and we will see you on the next one. Thank you.