 Hello, everyone, and welcome to the WordPress briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and you get a small list of big things coming up in the next two weeks. I'm your host, Josepha Hayden-Champosie. Here we go. And today I have with me, Nick Diego. Welcome, Nick, to the WordPress briefing. Thank you so much for having me. Yeah. Before we get started, why don't you tell me a bit about yourself, just kind of your history with WordPress, and then what it is that you've been doing with the WordPress 6.1 release squad? Yeah, so I'm actually kind of new to working with WordPress full-time, up until about June of last year I was in the hospitality industry at a career of 10 years, but I always loved doing WordPress on the side. And after the long pandemic, I figured it was time to kind of pursue my passion and work with WordPress full-time. That ultimately led to my current role as a developer advocate at WPNJ, where I focused primarily on WordPress and contribution to core itself. And then I guess it was maybe March or April this year, when Anne McCarthy, who I've worked with a ton, she asked me if I'd be interested in helping out on 6.0 as an editor triage lead, which is an awesome experience. And now I'm back for 6.1. That's excellent. I always like to hear about people who are coming to do repeat tours of duty. I probably shouldn't refer to working on WordPress releases as a tour of duty. However, I find that releases are so large and complex. And there are so many people in there now that working on them, it takes an entirely different skill set now than it used to take when WordPress was like 1% of the web. And so I think it's a really, really big task. And I think it's great when people were like, that was either so good that I would do it again, or I would like a second go because I could do it better, whichever way brings people to it. So yeah. No, I was just going to say that's a great point because the editor triage lead, which is the role that I currently have, was a brand new role for 6.0. The project kind of got so big that it kind of made sense to have a triage lead focus specifically on Gutenberg. Gutenberg is such a big part of WordPress now. And so that's where that role kind of came from. And now we've carried it over to 6.1. As the project grows, we need more people to come in and help make sure the release is smooth as it can be. Yes, because of that promise of backward compatibility and all the things. Can you do that? Cool. So by the time this releases, if I recall correctly, we will have passed RC2, or RC2 is coming the next day, something like that. We're right around release candidate two. So you have been doing this for quite some time on this particular release. So far, what is the feature that you're most excited about that's going out in the 6.1 release? So this is going to sound really boring, but it's actually incredibly exciting. So the most exciting quote unquote feature that I'm excited about is the improved consistency and standardization of block controls that are coming in 6.1. So things like typography and color and border and dimensions. These are things and tools that we've had in a lot of core blocks, but it hasn't been consistent throughout. And a ton of work has been done in 6.1 to establish that consistency. We're not 100% there, but typography I think we're at like 85% of all core blocks now support all the typography controls. And with each release as we head to 6.2 we'll improve on that. But it's really great for theme builders, theme designers, users to be able to control the look and feel blocks consistently throughout the editor. I was going to immediately answer you earlier with like a there are no boring answers, there are no boring improvements. And as you were explaining why it is that you kind of thought it might be considered boring, I think it's fair to say that anytime that you're increasing the consistency and you're increasing the confidence between like what you saw in the back end and what you actually shipped on the front end, anytime you're doing that, I think that that is exciting in the prove the negative way. Like if you think about the negative excitement that occurs when you have published something and it looks one way in the back end and it looks totally different on the front end and the panic you feel when you have to fix it, like not having that is a really big step up, I think. And so anything that provides more consistency for people who are using WordPress, people who are building with WordPress, I always find exciting, but also like, I'm an office person. And so I would find office things exciting, right? It creates a more delightful experience. I do a lot of work on the training team doing educational things and we teach people how to change typography and change color. Once they learn how to do it in one block, if they can take that same skill set and apply it to any other block, it's that blight bulb moment, they understand, they know how to manipulate and use WordPress to its fullest. So having that consistency really helps to level up abusers. Yeah, I'm going to take us off track a little bit and just ask a general question here. I remember the first time that I was working with what was a site, I guess, qualified for a site at the time. And I remember the first time that I discovered that I could change the look and feel with HTML and CSS. And I did that and also was like, well, I accept my fate. Whatever happens, if I kill everything I've ever written, that is just how it will be. The sheer terror of all of that is so different now. Do you recall that first moment where you're like, oh, I do have some power over this. I have some control over this. And whether you also found it scary? So I came to WordPress kind of as a hobby and website development kind of as a hobby. So I was kind of always in that tinkering phase where I wasn't building something for anyone else. I was in a safe place to destroy whatever I was working on with my tinkering. So I never really quite had that fear, but I can definitely see it from the perspective of building something for somebody else. But you're right, the editor and the controls that we have in, you know, now make it a lot easier to kind of manipulate and exert your creative desires on in WordPress than it was before with CSS. I love the phrase, I was safe to destroy things. And if I can figure out a way to make it a tagline for something, I will. All right. So during your second time around here on the release squad with 6.1, what have been the bright spots of that experience? And have there been any unexpected challenges of being on the release squad? Again, I come to WordPress from, you know, from a different career. It's kind of a passion of mine to be working with WordPress. So I can have a unique experience and maybe some others. And when I approach WordPress, there's always that tendency to say, why doesn't it do this? Or why don't they do this? And I'm always been the person, well, it's open source. We can do it. And so that's the kind of how I approach things. Now, of course, you know, I have the privilege of time to do that. Not everybody does. But one of the unexpected bright spots about working in a release squad is understanding how it all works. How does WordPress actually get built? What is the process that it goes through? It was just eyeopening to me. And I really got a shout out and for inviting me to be on 6.0. It brought me in. I learned so much about it. And now I'm just excited to keep working on these releases. But a release is hard. WordPress is huge. There's a lot of moving parts. There's a lot of things going on right now. We're trying to get everything ready for the first release candidate. So being on the release squad is not an easy job, but it's exciting. It's fun. And you really feel like you're part of that. And we really helping to build WordPress. Yeah. One of the things that I hope that people have learned from any time that they spent working with me is that we understand here in the WordPress open source project, and I believe that all open source projects must understand this. But every change that you make, if there are things that are dependent on it, which is going to be true for most of us, will have intended consequences and also unexpected consequences and unintended unexpected consequences. And so I've always felt like the thing that really makes the biggest difference about how we do open source in WordPress is that for the most part, we have a concept of where the most likely changes are going to happen across our entire ecosystem. We have a better understanding, at least compared to when I got here, a better understanding of how interconnected it all is. And so you've got this change here, and it looks small, but it's going to have this positive or negative impact as you work your way out from it. And so I think that that is an interesting thing. And certainly, you get a really clear concept of it in the release squad, I think. Oh, absolutely. If you were to build something like the block editor without caring at all about backward compatibility, you'd be done by now, right? I mean, so much of what we do is concerning ourselves with making sure that everybody who's on a classic theme or hybrid theme or whatever it might be, you continue to use WordPress in a safe and stable way. This is part of being such a large content management system. So you already told us the feature that you're most excited about. And so now I'm going to ask you about what feature or what bug fix has the most notable improvements that are coming to 6.1. This is a little different as in like, there's a thing you're excited about, which is an office thing, but like a thing that is maybe not new, but has the biggest delta, the biggest change to anyone's experience of it. Yeah. So obviously in 5.9, we introduced full site editing and 6.0 is a natural progression from that we're more and more features. Now, it's safe to say that there's only a small fraction of websites are using the whole full site editing of our block themes, all that kind of stuff. One of the hangups about that was managing templates inside of the site editor. You could add the files into your theme, which would then show up in the site editor, but there wasn't a direct way to add more complicated templates within the site editor itself. That is changing in 6.1. So now you actually have the functionality to install something like 2023, which is the new core theme and build out all these very complicated templates within the UI of the site editor that you could not have done before. I personally think that the biggest benefit of full site editing is really to empower no-code or low-code users, and the ability to add these templates directly in the UI really levels them up because now you can do all that complicated stuff that you normally would need to be adding to theme files and jumping into the code. You can do that within the site editor now, which I think is fantastic. That's great. And just a general caveat anytime that we talk about anything that's very developer-y or very no-code-y, I think it's always worth mentioning. Yes, a lot of what we're trying to do with the block editor is to just give some power back to folks who cannot find the time to become a developer or don't have the inclination. They don't want to do that, but that does not mean that no code is ever involved in WordPress. It's still a software. You can still do very complicated things with it. And if you are a developer, you should not think to yourself, oh, now that it's being available to low-code, no-code users, that means you don't want me. Like, that's not at all what's happening. You can do very complicated things still. 100%, 100% absolutely. All right, so that brings us to our final question here because we like to stay as true to the name as possible here on the WP briefing. If someone were wanting to get involved with the next release, so WP 6.2, how would they do that? So, talk to Ann and she'll get you set up. So after each release, there's a posting that goes out that lists all the different release teams. And you can just put your name out there and ask for consideration to be part of the team. However, I will say that the best thing you can do right now is help with 6.1. You don't necessarily need to be a release lead to do that. Testing, helping bug fixes, and reach out to me, reach out to other release leads, and we'll get you involved and engaged with the release. That'll give you a really good framework to start working and become a release lead for 6.2. Yeah, I think we talked maybe two or three episodes ago, or it could be more than that. I'll never know about the release squad, like the group that's doing that. In the event you think to yourself, there's no way in a million years that I'm going to just show up tomorrow and be part of the release squad. I heard what they said in the first question answer moment. That's fine too. As Nick mentioned, you can always get involved with testing. You can get involved with triage. Those are areas where any feedback at all is valuable, because we can get better information about what worked and didn't, what was expected, versus what happened. And that type of information is where all of our co-creators of the WordPress software really we rely on what you all are pointing out to us. If you're not shining spotlights on the most painful parts of your experience, sometimes we don't necessarily know that that's a pain point for anyone. And so yeah, that's a great place to start. If you are more of a writer, technical or pros, there are different spaces you can go to like keep our docs up to date, or make sure that people know that changes are coming at all in WordPress, because that's a thing. If you are a backend developer, we have a million things you can do, because that's just all day, every day for WordPress. It's just all the deep backend work. So yeah. Yeah, I did I did want to mention that, you know, being on the release team does not necessarily mean that you're incredibly technical. We have a documentation lead, we have a design lead, you know, communication lead. So there's a lot of different roles on the team that, you know, across all disciplines. So don't think if you're not a hardcore developer that precludes you from being on the team. Yeah. And if you're real good with common sense and working fully remotely, you can be the release coordinator. I can tell you, because I did that for 5.0. It was a big job. It was our it was the first time we had a release squad as opposed to just like the release lead, because there was just so much that was going into that and so much writing on it. And like you said, in some other answer that you gave, like if you were to just be like, we're shutting everything down and rewriting this in six months. And I hope you can come with us on it. Like a lot of open source projects do it that way. And that is a choice. And we made it the opposite choice. And so we're bringing all of our our co conspirators with us all of our co creators of WordPress. That's the hope all the time, making sure that they have enough information that they feel safe to destroy things enough information and skills about how to get out of it that they always feel some high confidence in what they're trying to do versus what they actually did do. So yeah, excellent. Nick, do you have any final thoughts for our listeners? Nope, I just hope everybody goes out and downloads 6.1 and enjoys it as much as I am. Go check it out. That brings us now to our smallest of big things. And actually, it is a pretty big list today, but still pretty big things too. So first up, we have a call for testing that is out and it is for our Android users. There is a call for testing for WordPress for Android 20.9. And I feel like we don't get a lot of calls for testing for Android devices. And so if you have been feeling left out or just like we don't always have that kind of mobile testing available, this is the opportunity for you. The next thing is that tomorrow we have RC to release candidate two for WordPress 6.1. That's coming out October 18th. There will be a link in the show notes, but that means if you write a plugin or a theme or have anything that kind of extends the core of WordPress, now is the time to start testing anything that might be a bug or represent a breaking change and make sure that you file those bugs so that we can get things as settled and excellent as possible. And speaking of WordPress 6.1, not WordPress 6.1, I actually have three changes that I think are going to represent some pretty big changes for folks. I will have links to all of these in the show notes. If you don't know where the show notes are, it's on wordpress.org slash news slash podcast. So the three things that I think are going to be big worthwhile things. The first one is multi-site improvements. The second one will be the style engine that's block styles generation tool, which will ship in core and I think is really important for y'all to take a look at. And then also there are some changes coming to the block editor preferences. Like I said, links to all of those are going to be in the show notes. And so they should be pretty easy for you to find. But also if you want to just get a general look at everything that's coming in 6.1, we did a walkthrough that I will link to in the show notes as well. And you can get a full understanding of what is going to be coming early in November. And that, my friends, is your smallest, big list of big things. Thanks for tuning in today for the WordPress briefing. I'm your host, Joseph Hayden Champosie, and I'll see you again in a couple of weeks.