 What are we doing? Should we go for it? I think we can answer it. Why not? The recording has started, so let's get cracking. Hello, welcome everybody to the WP 6.2 Live demo outline. I'm Nathan Wrigley. I do a few things around the WordPress community, mainly to do with video and podcasting and things like that. But it's not about me. Today we've got two fabulous guests. We've got Anne McCarthy and Rich Table and they're going to do a full-on product demo. It's a little bit unlike things that you may have seen because in the more recent past, lots of new features have been added and so Rich and Anne are going to spend the time on the screen in a moment and they're going to show you all of the bits and pieces that you may find dropping into a WordPress install near you. Let's hope. There's been a lot that's been happening. So there really will be probably 20 or 30 minutes of live demo. So look forward to that. I've got to get them to introduce themselves in a couple of moments. Just before that though, a little bit of housekeeping. This is going to be recorded, so if you have to drop out halfway through and go elsewhere, completely fine. It's going to be posted at the Makecore website, but it will also come fully complete with a transcript as well. So if that's something that you're looking for, that will all be there. Also to say that if you want to post any questions, we'd love that. In fact, there's a whole portion at the end when Rich and Anne have finished speaking, where we're going to field questions toward them. Now there's really two places to do that. If you're live with us on Zoom, then if you hit the Q&A button at the bottom of the screen and post your questions in there, I guess, specificity, whatever that word is, be specific. Help us out. Tell us exactly what you want to know and we'll get the questions to them. The other way to do that is to go into Slack and there is a channel in there, hashtag walkthrough. And if you want to post any questions in there as well, that would be great. So yeah, just to recap, Q&A button if you're in Zoom and use the Slack hashtag walkthrough channel if you are in the making WordPress Slack. Okay, right. I think we'll take you guys one at a time if that's all right. First off, a little bit of an introduction from both of you. Let's begin with Anne McCarthy. Shall we? Hello, Anne. Hello, hello. It's so good to be back on literally any sort of live stream with you. I appreciate that you're part of this. I'm Anne McCarthy. I'm a product wrangler at automatic. I live in Seattle. I also run the FSC outreach program, which is basically dedicated to testing a lot of the latest and greatest WordPress, which is part of why I'm so excited to be a part of this demo is because so much neat stuff has come through this that I've had the privilege of going through a little bit early with the outreach room calls for testing. So that's a little bit about me. I'll pop it over to Rich. Yeah. So Rich, if you want to take the baton there. Yeah. Hey everyone, I'm Rich Tabor. I'm a product manager at automatic and I work on WordPress and Gutenberg in particular from a little bit south of Atlanta, Georgia in the U.S. and I've been building and tinkering with WordPress for I think close to 11 years now. So it's been a good run and I'm super stoked about where things are heading. Yeah. And things definitely have been moving in a very much a forward direction WordPress 6.1 and WordPress 6.2. There's so much clear blue sky between the two of them. I think probably the best thing at this point is if we can have it, I don't know what whose screen is coming on. I think it might be Rich's or maybe it's Hans. If we can get that screen shared, then I will slide my way out of this call and say Rich and Anne, it's over to you. I'll be back as soon as you've finished for any Q&As. Awesome. Awesome. Thank you. All right. Can everybody can see my screen, right? Yes. Rich did an excellent job designing this. I do want to call this out. I will absolutely love this. Thanks, Anne. Yeah, this is actually running 2023. So it's kind of showcasing some of the things you can do just with the core theme and some of the design tooling that is being built into 6.2. So this view here is the site editor. So I'm going to orient you here. There's one big change here in particular I want to call out visually is this idea of the frame here on the right. And this will pull up the local template. So I'm looking at my home page of the site right now. If I navigate into other templates, I can pull those up here on the right as well. And then you can also navigate template parts. This part's not very new to 6.2, but the idea of zooming in on different template parts and templates and having them appear here in the frame is. And that's important because of this concept of browse mode. And this is where you could dive into an actual page from the site editor. So here I just pulled up the about page of the site and I can click into it and actually start making changes. Now, the changes here within the post content block are going to be relative to this about page, but I can also modify the template, which then changes the about or changes the page on any instance of this particular template. So it's a new concept on how we can browse the site, but it's a very powerful and really the first iteration of that way of managing a site. You're also lightly introduced content editing in the site as you mentioned. So it's a kind of an emerging of the two worlds, which I know folks have long been wanting to see that unified. And same with the frame, it kind of adds a nice layer where instead of just being dropped in, like before you kind of are given a more zoomed out view, which I think helps address a lot of the feedback that we saw around the orientation when you're entering the site editor. Yeah, exactly. And really, if we think a little bit further out than 6.2, this could also house setting to use. So we do have, you know, one view here that is relative to 6.1 where you can see all of your different templates. But imagine if we had any other different types of settings and controls and different pages loaded within your doesn't have to be just the front end templates and and renders of your site. Yeah. All right. So I'm going to dive into this here so you can go into it just by clicking on the frame or do that one more time just to show you just click on it. And now you're entered right into it. You can edit it right off so we can make changes just as if we zoomed into it and run the other way and 6.1. And then we have a bunch of styling tools that have been added to 6.2. So I want to kind of hone in on these like this panel itself is not new. We have styles, style variations, you can zoom in here, we've got this new zoomed out view where you can apply different ones at a time. And then we also have this icon here, which triggers the style book. Now the style book is a very interesting tool here that really lets you customize the themes style guide, essentially. So I can go through each of these tabs, which are relative to the block categories and see all of the blocks loaded on this particular site. So right here, I've got like the button blocks and columns block and whatnot. So if I click on one of these, it'll pull up the style panel of that particular block. And then when I make changes over here, these are applied globally throughout my entire site. So if I want to change the way this button looks, I say we do some smaller tags, maybe we'll add a little bit of letter spacing and maybe make it capitalized. See, it's getting applied everywhere that the button is used. Also do some changes here to padding, perhaps, maybe we'll do something custom here. I think that looks nice. And now you're quick while you're doing this, I wanted to note that like this is something that folks have really struggled with for use of the site editor where if you're editing a block that isn't in the template already, you're not able to see this. So it's just showing you can actually look at any block that's being used on the theme and see how the changes you're making in styles will impact that. Where before, if the block wasn't present in the template that you were editing, it was hard to know exactly what was happening. And so now you have both the style book and this inline preview that you see in the style section to rely upon, which is pretty neat. Yeah, exactly. And really you could theoretically go in and design your entire theme with the style book. Now, I know there's some, there's some advantage to designing it in context of pages and whatnot. And I'll go into that in a bit. But the idea is that you really can't quickly browse through all of the different blocks and tighten up what you want to within these controls. And it's not limited to the standard variation as well. There's also these style variations of each block that you can now manipulate as well. So we're going to go in, disable, change the radius of this one. So we want it to be sharp like our other button. But we have these new controls like this is a shadow control we've added in 6.2, where you can apply, say like this shadow here might be nice, this one here. And there's some fallback shadows within core that a theme can provide as well, its own values. But this now will apply for every single variation of the outline on my site here. And you'll notice that it's not in the style book right now. And that's just part of the future feature development is showing the variations of blocks as well. Exactly. Yes. I would imagine that this would this would show up the variations of the button block. Yeah. Which is a nice way to really customize these like it used to be only CSS would be used to to manipulate these variations here. And now it kind of abstracts out of way and you can do it within the editing experience. It's really nice. There really is. There's also this idea of block CSS. So you can add custom CSS that is scoped to a particular block. So if I add CSS here, it'll be applied for the button block, wherever it's used. Now, I wouldn't recommend using additional CSS. In most cases, I would, I would suggest using all the different controls that we've built that are built into 6.2. But the idea of using CSS to add a little pizzazz to this particular button block is fine. But just with that caveat that you wouldn't want to use it exclusively, like I wouldn't apply a background color via CSS. I would rather use the background elements color here. There's also additional CSS, which emulates what was previously in the customizer. So we do have site-wide CSS that can be applied within the site editor and also on the front end of your site. Again, I wouldn't emphasize using this exclusively as there are a lot of new design tools that I would explore first from the top level styles here where you can apply colors to the background text and buttons. But if there was anything extra you wanted to add, you could do so within the style sheet here. And I'll note we'd love to hear feedback if there are certain things that you're repeatedly adding custom CSS for. So either commenting on a currently open issue or if you don't find one opening an issue would be super helpful because it's neat to see what folks are using for CSS so we can fill those gaps. Yeah, exactly. So that's the global style panel here. But there are quite a few other improvements along with styling. So the first is the idea of pushing styles globally. So if I'm in here and I'm designing, let's say I want to add a radius, I want to do some different typography. Let's do appearance. I like this bold italic look. And then we'll also... Thanks. We'll also maybe make the letter spacing. Maybe we'll make it a little bit bigger, actually. And then... I think that'll work. I can do these changes here and see I've just styled this one particular block, this button up here. And this button down here is still using the global styles that we designed earlier. But now I can go through my settings panel here and hit apply globally. And I'll go down here so we can see it happen. The styles are now pushed globally to all the other blocks. So this is really helpful for when you're designing in flow and you don't necessarily want to abstract out into the style book. And you want to push your changes that you just did here. Because you like the way the button looks and you want those applied everywhere all at once. This is a really powerful way to quickly design within the editor. Another tool that is quite useful. And I'm going to take this heading here and manipulate this. It's the idea of copying and pasting styling. So we're going to use that same bold italic look. Maybe we'll make that a little smaller. We can even manipulate this size a little bigger. Now we go here to copy styles. And then I can come all the way down here to this other heading that's very similar and paste it in. And there we have that style applied just to these two headers. And you would do this when you don't necessarily want every single heading to have this effect. But perhaps there are like elements on this page that you want to push those changes to specifically. So copy and pasting allows you to be very granular, whereas applying styling globally lets you be more of a holistic design experience for pushing styles. Another neat... Oh, real quick. I just wanted to note. I think one of the things that's interesting is as we've added more design options to blocks, like this is part of the experience of scaling things and making it easier to use. So we think about like intuitive and delightful. Some of these tools coming in 6.2 really take the tons of design tools that we've added over the last couple releases and makes it easy so you can actually tweak things and then reuse. So I think that's one of the things I want to cloud is it's kind of this crescendo where now the tools that are coming in 6.2 really ease the experience and allow you to do a lot of neat stuff. Rather than having to retweak everything through every single heading block, a lot of stuff is eased. Yeah, exactly. WordPress is moving towards a design tool in less of what you see is what you can only have. It's more of an expression of creativity and it really does open up the doors for designing beautiful pages on the web. I think it's really powerful. Another cool bit that we've added is the idea of sticky positioning. So headers would be nice sometimes if they stick to the top. So for top-level group blocks, this is a group block here. There's this new position attribute where you can assign it to sticky. And as you can see right in the editor, it's already showing me that this is sticky on the front end and also here as well. It's only available for top-level blocks for now. There's still some odd stuff to figure out on how we communicate when something is not going to stick due to the parent height of the elements around it. But for top-level, it's still fine. So we have it here, but there are some iterations that are already happening for the next release that will kind of bring this into more, bring some more capabilities to this particular feature. Yeah, and I'm very excited because one of the things I wanted to briefly call out was the how the header, the template part, has that purple. So another neat thing coming to this release that was a big part of feedback for the outreach program was having template parts and reusable blocks, having a different coloring because there are different kinds of blocks that are synced across the site when you make global changes and it impacts everything everywhere. So that's another neat thing that's coming with this release is that you can kind of see those a bit differently in the list view as well as when you're in the editor. I see Nathan has his hand raised. Is that intentional? Oh, it's removed. Okay. It was not intentional. That's my mistake. I'm sorry. Yeah, it helps you see quickly too, like what is the template part, particular for headers and footers. It makes it easier to browse quickly. So speaking of template parts and patterns in particular, so headers and footers are new patterns added within WordPress 6.2 and they're loaded actually from the pattern directory, which is kind of neat. And I'm going to show you how to replace a footer with one of those other patterns. So if you have your footer template part selected, you can go up to replace footer. Now, this flow is not new to 6.2, but it's going to call out these other improvements. And then you just click one there and you have it loaded here. That's the site logo that I'm using up here as well. And you can modify this text without having to do any any funky PHP filters or removing actual templates. And if you want to change it again, you go back to replace. Let's pick this other one. Let's try this one. It's kind of nice. And there's this focus view where you can zoom in to just the footer itself. You can even check the responsiveness of it and see how it reacts on mobile. And make any of your changes here and have those persist over to the actual template whenever you close it out. It's a nice way to really kind of clean up the editing experience. So you're not seeing this entire group of groups. And instead, kind of focus in on what you're actually wanting to do the same for the header as well. Yeah, as Rich mentioned, there are some new patterns that are being bundled from the directory, which I think are really exciting. So regardless of what theme you're using, there's going to be some patterns through patterns that help democratize design where you can use them at anything. Yes, that's all right. All right. So navigation. Navigation has gone underway quite a bit of work the last couple of months. And really, this is all about trying to make it easier to manage your site's navigation and also add pages and links and even styling. So there's this new dedicated list view for the navigation block. So it's essentially emulating a little bit of what's available over here, except for you had to kind of get down to it. Now it brings it top, top of mind in the surface area here, you can drag them around, move them up and down, even add submenu links and remove them as well. And then you can style it like normal and now apply different styles via the styles tab to the block itself or even individual page links and whatnot. You can dive into them and manage them all from here instead of having to only manage them from up here. This really kind of abstracts the complexity from this particular canvas interface into a more familiar interface here on the sidebar. It's really a great effort and it's taken some time to refine, but it's getting there and it feels a lot nicer. Yeah, there's been a lot of good feedback about this as well, just as it kind of is meant to marry the classic experience with bringing blocks into it. So it is an addition to being editing on canvas. So if you really want to continue to edit as an average block, you can continue to do that, but it does add a nice interface in the block settings where you're able to do it. And I'll briefly call it here the split settings, which we'll probably talk about later, but you'll see here for more complex blocks, there's some nice split settings making it a little bit easier, more intuitive to go through. Yeah, that's right. And if you take a look at navigation here, this is very similar to this component added here. And that's not this purposeful. We wanted to look and feel a familiar either way or manage your navigation. So you can also add some menu items here, remove them and drag them around and reset them here, as well as browse into the individual pages. All right, so that's what I have for the site editor portion of the demo. And did you have anything else you wanted to add to this, Ann? Could you resize the browse mode frame? I just love the resizing. I think it's kind of cool. This is just like a fun thing to call out, but maybe you won't notice, but you can resize it. So as you're quickly going through your site, if you want to see how it looks in different ways, you can also do that. So that's the final thing. I'll shout out. Yeah. So then, yeah, exactly. There's a lot of fine touches like that. Well, we can't, obviously can't call them all out today, but it is really getting tightened up overall as an editing experience for the site. That's such a great foundation for the future, for sure. Exactly, exactly. All right, so if we press this back button here, it goes right back to the dashboard. I'm going to go ahead and leave. And that back button was a big piece of feedback people had. They would get into the site or not know how to get back out. So I appreciate you calling that out. Yeah, exactly. It's been through a number of iterations. And I think we have settled on something that feels nice and does feel nice. I agree. Ah, yes, the removal of the Bay Label. Do you want to talk to this, Ann? Yeah, I would love to jump in on this actually. So you'll notice that the Bay Label is removed for this release. And part of why you wanted to show it now is to see how all the features, how the experience has changed, how much more you can do, and all that has led to the removal of the Bay Label. And that doesn't mean the future development is done, that it's like, you know, going to stay this way forever. It just means that it's in a place where we invite you all to try the site editor. It is out of beta and a lot of development and work has gotten into testing this. So we've had almost, I think, 20 calls for testing with the outreach program. It's been through multiple major WordPress release cycles. There is still more work to be done. But I'm very excited to see the Bay Label removed. I think the features that are coming to 6.2 and the foundation that is set with 6.2 really marks a level of maturity that is pretty exciting. So consider this an invitation to try out modern WordPress and to check it out. 100%. Good to set it better. All right. So another neat part that's added recently for 6.2 is this idea of distraction-free mode. And so it's not turned on by default, but I have it on so we can see the result here. So you can go in and type right here, and then actually I'm going to throw in some what I'm here so we can see it in action. So this feels more like a text editor and less like a block editor whenever distraction-free mode is on. Even the multi-block selection feels really nice. It doesn't, there's not this idea of blocks even. It's kind of abstracted from here. There's less noise, there's less distraction. And the idea is that it's just you and your words. It's just writing and publishing. And if you want to publish it, you cover over here, you'll see the toolbar come down. You can hit publish or draft. And then this is how you would turn it off and back on right here. And then you still have control of all the existing tool and it's just a much simpler streamlined interface. And you do have access to blocks. You can still add them if you'd like to. But the idea is just being able to write without the distractions is really powerful and a really nice publishing experience overall. And this is for everyone. So this is like a lot of stuff we're coming to say are using a block theme. This is available for anyone who's sitting block editor. And to be honest, I use this for basically all of my writing now. And it's especially for any post or page. I typically will go into this mode. So I'm very excited about this. And I hope folks feel the same way. Yeah, exactly. I've been using it too for quite a bit. But the thing is, it's also not only for post editing. So I have a page here that I've created and I have distraction free mode turned on, which kind of removes all the extraneous tooling and really lets me focus in on the actual blocks here. So I can manipulate them to an extent. I can even drop in different imagery for these images here and modify the buttons and whatnot and even add more blocks. But the idea is it's almost like a simplified editing experience for pages as well, not only for post. And here I'll come up here and turn off distraction free mode to see it all in real time. And this isn't yet available for the site editor, but I have a feeling a number of folks are going to be keen to see that put in there as well. Exactly. Yeah, I don't see why I wouldn't work in the site editor as well. I think it'd be very nice. Yeah. All right. So we have some other improvements here that are fun. So this insert here has gotten a couple of changes here. So blocks looks familiar. It's still the same, but patterns is where we start seeing some changes. Instead of having some featured patterns loaded and a block category selector, we've split them out individually as their categories here. You're going to load up some of the different header patterns that are loaded in WordPress 6.2. So you can load them here and see them in this tray and then click to add them to your site. And which is really nice. It's a nice way to kind of go through them quickly. And see a bunch of different ones. We also have the media tab up here, which is new, which splits out the images from your media library videos and audio as well, including the open-verse library. So this is a catalog of, I believe over 600 million free openly licensed stock imagery. And you could search for it right here in the inserter. So let's type in birds and click on one. And it will add an image block with the image already added to it. We have got the caption down here. And if you don't want the caption, you just turn it off right here, this little control that was added. And now you can manipulate it right off. So let's drop it into here. Maybe we'll make these about the same size and move it over to something interesting. And I'll note that there was a GDPR concern around the images being properly uploaded rather than hotlinked. And I wanted to just note that that's been addressed. So the images are uploaded to your media library as well. So in case anyone has a question, sorry, continue. Yeah, no, that's a good point. It's very important. A key benefit too of this flow here is that instead of having to add an image block and then open your media library and then pick an image and then you'll have it here, it's really this one flow of searching visually. And searching here as well. And then having it added as an image block already. So we're kind of skipping all the extra steps that you always have to do anyhow. It's really, it's really, it's really nice. And we have a couple of interface changes. So there's the settings icon up here that used to be a cog. And now it represents the sidebar itself. So when you open it, the sidebar is triggered. If not, it's closed. And that's changed for a couple of reasons. But one of the bigger reasons is, as I mentioned earlier, this idea of split tabs. So we have the cog for settings. And that's when a block has additional settings that are not per the norm of the styles that are available within WordPress, then you'll have a new settings tab pulled out here. And that's to keep the density nice whenever you're editing. And it feels, it feels good instead of having everything kind of in your face all at once. And now for other blocks, like the paragraph block, there's not additional settings. So it will automatically not include the tabs up top. It'll just be everything top level. But when a third-party plugin adds a different settings panel, or even if you extend one of these core blocks that does not have one, and it detects one, it should be auto-added as well. So it's kind of just like a nice fluid way to continue improving the experience of editing within WordPress. Yeah. So plugin authors can also kind of make sure they want settings and styles to show that it shows it correctly. And there's a dev note about that as well. Yes, that's right. You can, you can decide as, when you're extending or adding your own inspector controls, that's what these are called here, whether or not they're included within styles or settings as well. Yeah. Then another smaller change that's kind of nice is this idea of pulling the outline from its own toolbar item up here into the list view. It's because they're very relative, you know, lists of all the blocks on your page and also an outline of what's going on. So they're combined now into this one view. We also have, you know, time to read word count and character count here, which is nice. And then this little guide here that just helps you understand the structure of, the importance of the structure of the document and making sure that it is properly structured. All right. Was there anything else that we wanted to add, you think, Ann? I'll add one last call out just because I'm trying to think about like little dev tidbits. If you want to disable openverse, there is a way to disable openverse as well. I know that's always a concern when we add something. It's like, okay, how do we get rid of it? Because I don't want the client getting into it. There is a way to disable that is documented as well. The other thing is the pattern. So there's new categories, the patterns. And so query is now post, a couple of things were merged. There's now call to action. And there's also some lovely, which I'm going to brag on rich again, some new text-based query loop patterns. So we have a lot of visual patterns for the query loop. And now there's some wonderful, more text-focused ones, which I think is really exciting. And just another great way where patterns has evolved. And patterns is obviously a huge part of the future of building with WordPress. So I'm very excited about those and keen to see just more variation with query loop. I think it's really powerful block to make easier to use. So I'm excited to see it. Otherwise, I think that covers a lot of what we were trying to go through. Yeah. And there's certainly more. There's a lot of interesting minute details that are quality of life improvements around editing and designing. And we can't cover them all today. But there's a lot of exploratory ideas and cool, interesting pieces that have been the result of lots of feedback and lots of testing. Like I mentioned earlier, it's really a testament to open source and contributing and really working together as a team to make this thing we call WordPress ours and making it a brilliant publishing experience. So I just thank you to everyone who's put in time, ideas, effort, code, design, marketing, copy, all of that and more to making this what it is. It wouldn't be possible without you. Totally agree. And thank you, Rich, for doing such an excellent job building this site and demoing all of this. Yeah, indeed. Thank you, Rich. Thank you, Anne. Just to let you know that in theory, there's possibly up to about 25 minutes left. If anybody wishes to pose a question, we're going to do our best to get them answered directly from Rich and Anne, whether that means putting the screen back on. I don't really know. But we've got a few that have come in. The place to put those, it would appear that some people have figured out how to do that in Zoom. But if you go to the walkthrough channel in the making WordPress Slack, you can post some questions in there and all things being equal. We'll get them raised as quickly as we can. So we've got a few in all honesty, because they've been copy and pasted from various different places, I can't necessarily say who the name of the person is that sent them. But first question I've got over here for either of you. It says, when you save globally under the advanced tab, does this change the style sheet? Interesting. So this will change the attributes of the blocks. So in that example there, I pushed the attributes of that one block globally. So they're applied to every block. So it does affect some styles, but not writing any style sheet or writing to the core style sheets. Can I ask a question? It's not something that's been submitted by anybody else, but it would just occur to me that as you were clicking the global button, I just wondered if there was a get out from there. In other words, if you inadvertently click the global button, is there an undo option in there? In other words, can you back away from all of the buttons suddenly changing or all of the H1s? You do have to hit save after it. Like you can't just hit apply globally. You have to hit save and that's where the multi-entity saving pops up. I, the multi-entity saving is kind of strange in that it's not good at discarding changes. So you basically would just have to like leave. Like it would be like, you probably also hit the undo. Like those are the two kind of options. So yeah. Yeah, the undo is like a global, it works there as well. Yes. There's a reason that feature is hidden like under advanced and it collapsed. It's not necessarily for everyone, but for folks who do like to tinker, it is available. Right. And it's also only available in the site editor as well. So it's the more, the global view of editing your site is where you can access that. Perfect. Okay. So I have a question from Zoom. Is copying and pasting styles as demonstrated just for core blocks? They go on to say more, which I'll read out. Some blocks collect, some block collections have their own C and P. And I'm curious what might carry over if anything, then there's a follow up. Also, if CSS classes are assigned to a block, will applying global styles to a block be to all of the same block, i.e. H2 or hopefully, will a custom class allow for a more granular global CSS? There's a lot in that question. But if we just start with the, start with the, is copying and pasting styles demonstrated just for core blocks? So it works for blocks that have leveraged the block support system within core. So if you have opted your block into using background color and text color, link color, any of the layout settings, anything that was in the styles tab, that all of those would get copied or pasted or even pushed to the global application of styles as well. Now, if a block has done its own sort of background color attributes, I don't know that those would persist as well. But if you use what's available in core, it's really one or two lines of JSON will get you the background color support that you need. Anything to add to that? No, just another reason to rely on course building. So I think it's a good, another great example of how these features will work together and how adoption helps whenever these new things come out. Okay, so we'll go on to the next question then. So this is from Zoom and apologies, I don't know your name. Can we have, this is a feature request. Can we have sticky sidebar block for some groups next release, please? Yeah, it was a separate block, I'm guessing. It's just, yeah, Rich, I don't know. Yeah, I would say we wouldn't need a sticky sidebar block. Right now the group block in top level only does support position sticky. And the only reason it was turned off, like we did have it on for one of the Gutenberg releases for everything, for every group block, but it was turned off just because there was too much confusion around if you had a sticky element that wasn't, didn't have enough space to stick for, you know, enough height to stick. So it wouldn't actually be sticking. You wouldn't see a result of you applying a sticky position to it. So I think we can figure that out with some, some UX to really clean that experience up so that you do expect and understand what's going on when you apply that to a block that's not the root level of the document. So it'll be there, it just takes a little bit more iteration. Okay, okay, another question this time from Slack. When there are changes made in the site editor, are the templates still marked with the blue dot to indicate that the changes are in the database? Yes, from that managed templates view that I shared in the canvas, it will show up just like it did previously when there are changes to one of the templates provided by the theme. Yeah, and you can revert the changes as well as you, as you're used to doing. Okay, thank you. Anne's shared a link related to the question that we just posted. I don't know how Zoom works well enough to whether or not we can share that on the screen. I can briefly share my screen. Yeah, that'd be great. Show us the, let me try that. I just wanted to mention this in case people want to follow on in the follow-up tasks related to this. I love to look at links. I'm a nerd like that. So in case anyone else is, this is a lot of follow-up tasks and a great issue to chime in on or just follow if you're interested in this, because there are some improvements to be made, but this is a neat leap forward for now. So it's, oh, I just copied and pasted it. So it's issue number 47043 in the GitHub repo. So 47043 related to the question that we just had. Okay, so another one from Zoom. This is Robin who asked the question. Can you, oh, it's just moved on my screen. There we go. Can you show us how to trigger the focus mode to view, say, for example, the footer on its own? So I guess we're back on the screen again. Sure. Everyone can see. Yep. So when you have a template part selected, you just hit the edit button here and then it's focused into that as well. And then you have the, again, the responsive controls here. All the existing controls is just localized to this template part. Okay, hopefully that answers your question. Thank you, Robin. Just for anybody who's kind of lurking who has a question but hasn't yet posted it, please do. What are the chances that you're going to get rich and on the phone in the next few weeks? Pretty minimal, I'd say. So make use of them while they're here. Ellen has done just that. She's in Slack. Ellen says, is there a plan to allow no title templates in the block editor, as they are still included even in header and footer only templates? No title templates. Like templates without a title? I'm not quite. Can you just remove the block? You can, yes, you can remove the post title block from a template. I'm not quite sure if that's, if that's what the question's asking. Yeah, Ellen, if you're still in Slack and watching this, if you, if you heard Rich and Anne querying that, then if you can give some more clarity, we'll endeavor to get that answered. Knowing Ellen, she knows exactly how to remove things. So I'm like, I'm curious. I'm definitely, we're misinterpreting saying because she's very not showing the title in the editor. Not showing. Yeah. Not showing the title in the editor. She says she's here. Like, say more. Yeah, give us more. Give us more, Ellen, and we'll get right back to you. Well, let's all back up on that because Ellen always has some good questions and good feedback. All right, we'll do just that. Again, another question from Zoom. This is posed by some anonymous person. Will the list views icon get the same treatment as settings? I don't think there are plans. Yeah, I don't think there are plans to change that. The list view icon is, it's, it's always the list view. So when you talk that on and off, it's relative to what it is. Whereas on the other side, the settings can be block settings, page settings, template settings, global styles is in that same area. So it's a little bit more context for the list view to stay a list view icon. Okay. And I know that question, it came up because the settings icon looks like there's that sidebar. And so there are people who have been asking, like, will that same thing happen over here? Just for context, that was part of a discussion and a different GitHub issue. Okay. Thank you very much. I appreciate very much those people who are posing questions. That's really great. Again, just to prod you once more. Feel free to add your own questions in no matter how big or small they are. We're here to help. So now we have a question on Zoom from Abdullah. Any, oh, it coincides beautifully with the question I've written down. Any good resources to learn FSE-based, theme-based development? Can you either of you point to a particularly good resource that you know of? Yeah, Learn WordPress. There's tons of stuff on Learn WordPress that I would recommend. I also, Daisy Olsen, who's the developer relationship in her automatic, has a Twitch stream going and some YouTube videos around blockchain development. But I would recommend going to Learn WordPress. There's also some contributor-led initiatives. Carolina, who's one of the theme folks, has, I think it's like full-citing.com. And that was kind of like the original go-to resource. And she's done an incredible job working on that and keeping it up to date. So yeah, there's tons of resources. I will spare you from sharing more. I don't know, Rich, you have more hands-on experience there. Like what's the most helpful for you? Yeah, there's some really great tutorials and guides on Learn that are relatively new, that are really helpful. And I see the team there has been really cranking it out on the last year or two, like really putting a lot of effort into this. So I would start there. So if you're not familiar with that, I guess it would be apropos to say go to your browser of choice and type in learn.wordpress.org and go and explore. Basically, there's a ton of materials that are getting updated on what feels like a daily basis at the moment. So once more, learn.wordpress.org. Go and check that out. But also, Ann, in the chat that we've got going on here, has a link to Daisy Olson's Twitch channel, which I'm just going to read it out, but hopefully it'll make it into the transcript. Twitch.tv forward slash daisy on WP, and it's all as one word, D-A-I-S-Y-O-N-W-P, daisy on WP. So there's two great places to go, but the learn.wordpress.org is perfect. I've got to add one more thing, which is if you're not fully ready for block things, one of the big things that I feel it needs to be emphasized more is you can gradually adopt. So all of these pictures are being done, but maybe you want to only give access to a client to edit the header. You can do that. Maybe you want to use, you want to leverage theme JSON in your class theme. You can do that. And if you want to expose a template editor, but use the rest of your themes across, you can do that. So I want to also encourage folks to look into resources around gradual adoption, because it makes sense that this stuff isn't from day one. There has been a focus on that, of adopt what you want when you want, and it's going to make sense to different people at different times. Matias wants to add that to me, and I think it rings really true. And so now that we're at this level of maturity, I think we're looking again and revisiting again, like, okay, what can I use? What do I want to use? I think this is really important to mention. So if you're not ready to go all in, I encourage you not to just wipe it all away, but to think about how you can gradually adopt and also what would help you gradually adopt. So there is actually a label in GitHub, started a couple months ago around, it's called blocks adoption. So if there's something that you see that you're trying to gradually adopt the site editor and it's preventing you from doing so, like we want to know about that. And you're welcome. I'm going to just put this out here at A-N-N-E-Z-A-Z-U, is my GitHub username. Feel free to just, like, add Anzazoo. This is blocking me from using the site editor. Like we want to know these things. Open issues, please share, because that is also part of the phase of this work is making sure people can adopt as they can and that this will, they're are robust. And there's a ton of resources as well. There's a page in the theme handbook around using, you know, gradually adopting to blocking. So I just wanted to call that out, but like the right time. And just one more time. What was that? Give us the username again. A-N-E-Z-A-Z-U. So like Zazoo from like The Lion King, it's an inside joke from middle school, so. Okay. Okay, possibly the shortest question we'll get. Can Lotties, this is from Sandy, I should say. Can Lotties be added to 6.2? I would say that I did a quick search a few minutes ago and there are various blocks built by the community, which do allow you to add or embed Lottie files to your site. I haven't tested any myself, but feel free to dig into those. And if they're open source, you know, can contribute ideas or feedback on those GitHub repos. Thank you very much. And Eagle has posted a question. When there are changes made in the site editor, are the templates still marked? Well, did we have that one? Are there templates we have, right? We've done that one. Yeah, we answered that one. Yeah, I think we did. Okay, moving on directly then to Ian. What is, oh, okay. What is the philosophy for mobile in the editor? Are there any plans to have a mobile view? That's part of the dragging and sizing. And there's a lot of work being done around intrinsic design. And you can see on the developer that we're first up, gosh.org, what is the blog? I think it's backslash news. Do you hear audio? I hear only your audio. I don't hear anything. I don't wish. Okay, sorry. Something just started playing in the background. I don't know where. And that just scared me. Okay. Sorry. It's like all of a sudden I was like, whoa. Where was I? So we were talking about mobile views. Sorry, mobile view. Yes, intrinsic design. There is a developer blog that if you're not following that you definitely should, that addresses this around basically showing that the mobile viewpoints have exploded over time. It's now really not sustainable to try and have CSS and all this sort of stuff. Mobile queries lining for each different view. So instead, how can we think about intrinsic design? And so that's like the best answer I can give. And for now, there is this nice resizing that you can do to kind of see how things scale. 6.1 introduced fluid typography, which is really exciting and part of this larger intrinsic design setup. And I think we'll expect to see more of that over time. Sorry for the brief mental break there. It's always nice to get some music, I suppose. Just a quick reminder, we've probably got five, six, seven minutes or something like that before we start to wrap things up. So if you've got any questions, please, please do post them in here. We have one from Paul who asks, is there any more work planned for pattern management in the future? And then WP Engine has released a plugin allowing easier management of patterns recently. Yeah, I believe that was yesterday. It would be good to know if we should wait for core or assume that nothing else is coming soon. Yeah, I would say that pattern management is an important part of this new WordPress experience and having a way to create and manage local patterns, but also maybe push them to the pattern directory. And then on top of that, having a functionality built in where it's kind of like a component-based system where you have patterns where the design is the same across patterns, but content can change. Like all of that kind of falls into the same category of work and that is something I believe WordPress will eventually do as well. Okay, we've got no more questions on the screen, so I'm going to ask a question if that's all right. You were demonstrating the distraction free mode there where you could move things up, move things down and resize and pictures and images and so on. I was just wondering what the constraints on that are. So in the case of images, I could see that you could resize things and with the text I could see that you could highlight things and start typing wherever you wish, but I just wondered how the decisions have been made to set those parameters and those only. So yeah, around that, what's available in distraction free mode? What limitations are there? I would say generally what's available is what happens when you click on a block and what tooling is there available on the canvas before. Resizing was available on the image but not the toolbar. So the resizing is still available when you're in distraction free but maybe not adding the caption piece or those other toolings. It's almost like the content locking or content only locking API. It's very similar to that in a sense but a little bit more tightened up where just text and dropping in images. You can't necessarily open the media library from there unless you dive out of it, but you can drop another image onto that existing image to replace it, some things like that. It looks like a really excellent interface for people who just want to concentrate on their writing. It sounds like Anzol in on it. I use it every single time. It's amazing. Yeah, it almost felt like a Google Doc minus all the bits and pieces at the top. Yeah, really, really nice. Okay, so we have some more questions. Weston is asking, what about optimizing the experience of editing using a mobile device on the web? So I guess that's a little bit maybe of the question that we had earlier. How can we do things on an actual mobile device? Yeah, that's a great question. There are mobile apps. So there is the mobile team and using the mobile apps. I personally don't use the mobile apps and sometimes we'll edit things from Safari on my iPhone SE 2. I actually was talking to someone, their username is NomadScapeboarding. And from what I understand, he only builds client sites from his phone. And so one of the things I said to him was I was like, give us your feedback. That's really cool. It's really unique. That's fantastic. Like what pain points are you running into? What can we improve? Because there is obviously like, we are in a mobile first world. My phone is sitting right next to me. I would love to hear particular pain points folks have when trying to edit in that way. You can obviously use the apps. There are some quirks with the site editor right now that I know is partially being looked into and resolved. But yeah, I think there are probably, what we're building now should always translate back. And there are teams trying to sync back and forth. And there was a recent post from the mobile team talking about what's the future of mobile editing. And so I would recommend, it's somewhere on Make Core. I recommend digging that up and getting involved and honestly sharing your feedback. Because I don't think that is an experience that we talk about enough personally. It's a great question. Rich, anything or should we move on? I think that was great. Okay, perfect. Okay, we have an anonymous question. It says, as page speed is a big challenge, how are we optimizing the blocks for better LCP score? There are some interesting... Sorry, Rich, I don't know if you want to jump in. I was going to start wink-dropping. Yeah, you go ahead. Yeah, there's some interesting work from Andre. Part of it involves actually adding tracking and making sure there's really good front-end metrics. So there's kind of a two-fer going on where in one fell swoop, we're focusing on better tracking and improving the tracking that we have for performance, particularly on the front-end. And then at the same time, also work is being done to optimize and to optimize style sheets. There's been some really neat stuff in previous releases that I bet I can pull up. He'll give me one moment. Yeah, whilst you try to find that, and I think it's probably important to say that if there are any questions which you wish to have answered, which don't somehow get answered in the next few moments, then there will be posts created around this piece. So anything that goes missing, any question that is unanswered, there will be endeavors to get them answered. Right, okay, show us what you got, Ann. Yeah, so this was a post I did for 5.9 in conjunction with a whole ton of folks who contributed and actually did this work. I just was kind of gathering it up. But you'll see sections here on block style sheets and CSS loading. And honestly, a lot of the work with the styles engine, which is part of the global size project, can help give a lot of opportunity to actually improve this. I recommend checking out this post to see some of what's already been done. And then in the future, one of the discussions that we had recently was some folks across the community from Google, from automatic, turn up all over the place, including our lovely performance lead, Felix. We talked about some of this stuff and about how to talk about particularly themes and also just blocks in general, and thinking about some performance improvements and develop education and automated testing and all sorts of stuff. So I won't go too far into this, but I think a lot of work can be done and some of it is being done around measuring more front-end metrics. And very recently, LCP was added and started to be tracked here, which I think is pretty exciting. So, yeah, I think following the performance team and Felix, Ann, in particular, would possibly get you quite a long way towards your answers there. Okay, a couple more. Firstly, there's a few people helping out in the Slack channel. So I appreciate that. We've got Matthias answering questions and so on. So that's really amazing. Thank you. Another anonymous question. Any plans to support CSS Grid? I think it's something worth exploring. Probably not the major priority coming up, but definitely some interesting aspects that we've seen other building applications do that we can learn from for sure. Okay, we're very short on time now. I think we've got to round it off at the top of the house. So we've got about four minutes left. I've got to wrap it up a little bit. So try to get these last two done if we can. This is from Mary. What are the typography options? As of 6.2, we have Google Fonts and Self-hosted. Any plans for solutions like Adobe Type and Monotype? There's a Fonts API that got booted from 6.2 and is hopefully planned for 6.3. So I would just follow that effort. So right now, 6.2 is not introducing anything new or different there. Things are as they were. There's a private API that folks can use with anything JSON. That's as nice as I can be. Thank you. No, that's perfect. And I think with three minutes to go, that's probably the best time to wrap up the Q&A. Apologies if you had a question and it didn't get answered. As I said, there will be a whole load of things created off the back of this. We will make sure that there's a transcript available and I've just read something in the comment. Hopefully, any questions that have been asked but are not answered will be answered approaching that. Just very, very quickly, I have to say thank you to Ann and Rich in particular for taking the time out of their busy schedules and demoing what 6.2 can do. It really looks like a transformational release. But also, thanks to Chloe and Jonathan and Lauren and Mary who are on the call but you haven't necessarily seen them right now so I appreciate them. That's really great. Following up off this, I've got three points to mention. Following the 6.2 release on Make Core for development updates and calls, there's going to be a post. It's make.wordpress.org forward slash core forward slash six dash two. Also, if you've been keeping a close eye on the beta releases, I say beta. I know it's hysterical. The beta releases, we've got version four. Beta four has just been released and anybody who wants to test that out would be most welcome. The URL for that is far too long for me to say out loud but you can Google it, I'm sure, and find out how to test for that. And also, if you are keen to follow WordPress, it's all over the social networks and you can follow basically if you try to just follow at WordPress then you'll get somewhere. So for example, on Twitter, it's WordPress at WordPress. On LinkedIn, it's forward slash company forward slash WordPress. Instagram is forward slash WordPress. And guess what? On Facebook, it's forward slash. What do you think it would be? It's WordPress. So it's available all over there. And I think that's it. I think that's everything that we've got to say. We're about one minute away from closing. So particular thanks to Rich and Ann, but thanks to everybody in the background making all of this happen. Thanks for showing up. If people don't show up, the work never gets done and the project never moves forward. So I fully appreciate anybody who's given up their time to ask questions today and watch this presentation. And thank you, Nathan. I want to call you out as being an excellent moderator and creating a safe space for us to talk about. Very, very welcome. I enjoyed doing it. I would gladly do it again. All right. I don't know how to end this call so I'm just going to wave and say goodbye. Bye everyone. Thanks for coming. Bye-bye.