Tyler Lau has his finger on the pulse of CBD and cannabis industry. There is a lot growth and opportunities for developers.
A responsive, mobile-first, and customizable Bootstrap-based theme.
In the thirty-second episode of the WordPress Briefing, WordPress Executive Director Josepha Haden Chomphosy shares her open source reading list for that post-WordCamp Europe downtime.
Have a question you’d like answered? You can submit them to firstname.lastname@example.org, either written or as a voice recording.Credits
- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Santana Inniss and Chloé Bringmann
- Song: Fearless First by Kevin MacLeod
- Producing Open Source Software, Karl Fogel
- Working in Public: The Making and Maintenance of Open Source Software, Nadia Eghbal
- Collaborative Ownership and the Digital Economy, ed Rishab Aiyer Ghosh, Roger F. Malina PhD, Sean Cubitt
- Humble Inquiry, Edgar H. Schein (Author), Peter A. Schein
- WordPress Milestones
- WordCamp Europe 2022
- 2022 Annual Meetup Survey
[Josepha Haden Chomphosy 00:00:00]
Hello everyone. And welcome to the WordPress Briefing. The podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it. As well as get a small list of big things coming up in the next two weeks. I’m your host Josepha Haden Chomphosy. Here we go!
[Josepha Haden Chomphosy 00:00:40]
With the approach of various mid-year breaks and the prospect of wandering off for some safe, restorative travel, I’ve been updating my to-read and re-read list. As I was looking at the queued books for my Northern hemisphere summer, there were some common threads, mostly around leadership, but there’s also like a chunk that’s about cross-cultural group theory and economics, and then like some beach reads, but there’s one group in particular that you all might find interesting.
And that’s a group that’s sort of like a back-to-FOSS basics list. So I’ll share my top few with you in case you want to pack a copy for your next getaway.
The first one on our list is called Producing Open Source Software by Karl Fogel. I think everyone who contributes to FOSS projects has received this as one of their first recommendations. Like, y’all are building open software? Excellent, you need to read Producing Open Source Software. Like, that is just a sentence that comes out of everyone’s mouths. So this was one of the first open source books that was recommended to me when I joined the WordPress community. It was freshly revised in 2020, and I haven’t given it a read since then, which is why it is on my reread list this year.
[Josepha Haden Chomphosy 00:01:54]
However, it shaped the early days of the WordPress project’s leadership, and their lead developers, and some of WordPress’s basic philosophies. It’s all available online, under a creative commons, ShareAlike license. And so it’s worth the read. I’ll put a link to it in the show notes so it’s easy for everyone to find in the event that is your preferred beach read.
The second one on this list is a book from Nadia Eghbal. She wrote the excellent Roads and Bridges report that also is probably not light beach reading, but you know, this one is on my list to read this summer because Eghbal always delivers truths about the reality of maintaining popular software, popular, open source software, in a way that’s easy for me to access and process rather than getting paralyzed by the enormity of it all.
For what it’s worth your mileage may vary on that. I realized that, like, I live and breathe open source stuff. And so just because I am not paralyzed by the enormity of her explanations of things doesn’t necessarily mean that you will have a similar experience. And so I’m just going to claim that elephant in the room for all of us.
However, if you only read one book on this list this year, I think that this should be the one that you read.
[Josepha Haden Chomphosy 00:03:14]
The third one is called Code: Collaborative Ownership and the Digital Economy. It was edited by Rishab Aiyer Ghosh. I am certain that I butchered that name. And so I apologize on my own behalf to everyone that knows whether or not I said it correctly.
This book focuses on intellectual property rights and the original purpose of having anything like copyright in the world. So, right up my alley! The writers who contributed to this work promise exploration of the plight of creativity in the commons, the role of sharing in creative advancement, and a concept of what it would look like if intellectual property were to mean the second closing of an ecosystem versus a triumph of the commons.
I mean, obviously, this one is very light reading. You can take this topic to high tea and everyone will not know what you’re talking about. However, this one looks like a really interesting book to me and I am just super ready to read it.
[Josepha Haden Chomphosy 00:04:19]
The second to last one on the list is a book called Humble Inquiry.
This is a new-to-me book that seems right in line with one of my favorite books to recommend to leaders in the open source space. From reviews of it, I have gathered that it takes a hard look at the value of listening and asking for clarification in a world that puts a high value on an unsolicited hot take.
It puts the importance of high trust relationship building, which is at the heart of any cross-culturally aware organization. And for folks who’ve been working with me for a while, you know, that relationship building is an important part of my leadership expectations for myself. So it puts relationship building at the front and center with a promise of practical applications for everyday life.
And if you ever have tried to tackle a complicated topic like this, you know that practical applications are really hard to come by and it’s often hard to understand it if you don’t have those practical applications. And so that is why this one is on my read and reread list this year.
[Josepha Haden Chomphosy 00:05:24]
And then finally the WordPress Milestones book.
So this sounds like a shameless plug for WordPress. And on the one hand, this whole podcast is about WordPress. And so, yes! But on the other hand, I actually am reading this for two specific reasons. I’m rereading this actually. I read it when I first joined Automattic. And so the first of the two reasons that I’m rereading it this year is that volume two of this is, like the second decade of WordPress currently, being researched and written in preparation for WordPress’s 20th birthday next year.
So I am rereading this to kind of get that all back in my mind as that work is getting done. And the second reason is that I honestly like to remind myself of how far we’ve come sometimes. I talk about our work frequently. And I talk about what we’re working on right now, all the time.
I talk about what we’re looking at three years from now, five years from now. The biggest concerns of today, tomorrow, and the future-future. And it’s very easy to forget how much success WordPress has had and how much growth the contributors that support us have had over the course of our long and storied history.
[Josepha Haden Chomphosy 00:06:40]
And so I like to go back to that just to kind of give myself some grounding in our progress, as well as get some concept for how we can move forward together. So that one is also available online. Also under a creative commons ShareAlike license and it is also worth the read. I will share a link to that with the other one in the show notes as well.
That brings us now to our small list of big things. Let’s see what we got in the old lineup today.
So, firstly WordCamp Europe is happening this week and it’s possible to watch the live stream from the comfort of your own home. There are some smart and talented speakers at the event. So I encourage you to catch a few if you have the time. I’ll include a link to the live stream information in the show notes below, and then also you can always keep an eye out on Twitter.
There will be a lot of discussions, a lot of conversation there. And so you can engage with folks that are there at the time and catch up on those conversations, catch up on those presentations in your own time, as it fits into your day.
[Josepha Haden Chomphosy 00:07:50]
The second thing is that WordPress’s community team is preparing the annual meetup survey right now. So if you participate in meetup events, keep an eye out for that because your feedback helps us to make plans to improve that program so that it works better for you. And it helps you to learn WordPress better and feel more confident with what you are taking out into the world that way.
But, if you are wanting to use this as a chance to contribute, we actually will need folks who are able to translate the surveys as well. So I’ll leave a link to some information about that in the show notes. If all of that stuff about contribution didn’t make any sense, then just like keep an eye out from your meetup organizer and they will make sure that you have that survey so that you can have your voice heard.
[Josepha Haden Chomphosy 00:08:33]
And then item three is less of an item. I mean, it’s an item cause it’s in this list, but it’s less of, like, a thing to know and more of a general thing to be aware of. It’s a general awareness item. There’s a lot going on in WordPress right now. I can see how hard it is to keep track of some of these things these days.
And I know as someone who’s looking at this all day every day that, yeah, it’s a lot. And it’s hard to get your bearings. So if you have a team that you contribute to already, don’t forget to reach out to each other, just to check-in. Sometimes we don’t think to ask for help. Sometimes we don’t think to offer help and you know, if no one needs any help from you at that moment, a little hello also can brighten someone’s day.
And that, my friends, is your smallest of big things. Thank you for tuning in today for the WordPress Briefing. I’m your host, Josepha Haden Chomphosy. And I’ll see you again in a couple of weeks.
Birgit Pauli-Haack and special guest, Grzegorz Ziolkowski talk about WordPress 6.0 release, Gutenberg 13.2 and 13.3 and interesting discussions happening on the Gutenberg Repo
Show NotesWordPress 6.0
- WordPress 6.0 “Arturo” Release post
- WordPress 6.0 Field Guilde with all DevNotes and changes
- Video: Release announcement
- Building a site with WordPress 5.0 vs WordPress 6.0 w/ Anne McCarthy
- New Video Explores Site Building Progress From WordPress 5.0 to 6.0
- What to expect from WordPress 6.0 by Birgit Pauli-Haack via Pantheon
- What’s new in Gutenberg 13.2? (May 11)
- Gutenberg 13.2 Adds Persistent User Preferences and a Visualizer for Margin and Padding Controls (WPTavern)
- What’s New in Gutenberg 13.3.0 ( May 25 )
- Gutenberg 13.3 Introduces Experimental Table of Contents Block (WPTavern)
- Focus: Blocks Adoption (Label on GitHub)
- Allow usage of block based “template parts” without using block based “templates” (#37943)
- Site Editor & Templates Roadmap
- Global Styles Ongoing Roadmap
- Tracking: Add a Style Engine to manage rendering block styles (Updated May 20th, 2022)
- Pattern as Sectioning Elements
- Add a zoomed out view to the site editor (#41156)
- Improving FSE for the Agency Use Case #41349
Stay in Touch
- Did you like this episode? Please write us a review
- Ping us on Twitter or send DMs with questions. @maryojob and @bph.
- If you have questions or suggestions, or news you want us to include, send them to email@example.com.
- Please write us a review on iTunes! (Click here to learn how)
Birgit Pauli-Haack: Hello, and welcome to our 67th episode of the Gutenberg Fran Podcast. In today’s episode, we will talk about Gutenberg 13.2 and free WordPress 6.0 and discussions that are taking place and would need your opinion. I’m Birgit Pauli-Haack, curator at the Gutenberg Times and WordPress developer advocate.
Grzegorz Ziolkowski: I’m great. I’m so happy that the release went out. Everything works, the work didn’t collapse, so that’s great. Also, want to thank you also for being part of the release team and also, I need to mention that I was also a co-lead for the editor with Adam Hevinski, his help was so important to making that happen, because that was a lot of work to bring all the changes from the editor to WordPress core and making sure that everything works.
The group that helped was so huge. There was, I don’t know, 20 people, at least helping all the time with different type of tasks, which was an amazing experience to see how everyone cooperates.
Birgit Pauli-Haack: Yeah.
Grzegorz Ziolkowski: And also the release team was much bigger. You and the documentation team also having a core lead like Milana, right?
Birgit Pauli-Haack: Yeah, yeah.
Grzegorz Ziolkowski: Oh yeah. So it’s really interesting to be part of the team and see how it works. Also, the team was bigger than ever, as far as I know, and I think that it still could be bigger. In my opinion. We have so many tasks that are necessary to make all that happen.
Birgit Pauli-Haack: I was on the release course now as a rookie and of course I needed co-leads because as a rookie, you don’t know what to get yourself into. But there are so many pieces that go into this release and it all has been a mystery and most still are mystery to me. Yeah. But I learned a lot. I learned a lot from all of the people on the release squad. But it’s also the more I know, the more I know what I don’t know.
And so it’s kind of that really overwhelming feeling that, okay, I have watched so many times, but I still had no idea what is really behind it in all the different pieces that are there. So, and as you said, I’m in awe of all the brilliant people that make these run smoothly and are always there to help each other out. It’s an amazing experience.
Yeah, absolutely. I’m glad I did it. It was a lot of work and, but wrangling dev notes, it’s a unique experience anyway. But yeah, congratulations that you helped bring it over the finish line.Announcements
So yes, WordPress 6.0, Arturo was released this week named after the contemporary Latino jazz musician, Arturo O’Farrill with a good Irish name. And there are many features and enhancements that are rolled out with a new version. We talk probably about all of them during the months, leading up to the release on this podcast, we will share again, of course, the release post, and then the field guide with the dev notes. And we will also share two videos with you. One is the release video by the design team. If you haven’t seen it yet on the about page or in the release post, watch it.
It’s a great design and cutting from screen to screen, to highlight all the features that are in there. It’s a great piece of art, so definitely watch it. And then the second video is by Anne McCarthy and she covered the site building process between WordPress 5.0 and WordPress 6.0. 5.0 was released just to repeat that December 6th, 2018. So it’s three and a half years ago. And in that video, you’ll see how it changed from the early versions to how you build sites now. It’s a great, interesting video to watch. If you haven’t tried out the block editor yet, if you’re one who hasn’t started using it yet, I think you will be surprised, or it’s eye opening to see how it really changed and maybe it intrigues you to start using it again.
Grzegorz Ziolkowski: Yeah. It’s a huge change. How it all has evolved from starting small to edit only the content that’s post and pages. And throughout all that time, how data change itself, by bringing more tools that are supported and allow you to do more and more things with the content to add some styling and create beautiful designs without using a single line of code. And now even you can create the whole experience. And there’s many block themes that empower users to edit everything without ever opening and edit or code the detail where you need to deal with PHP files, CSS, and all that big stuff that are becoming more and more complex every year.
Birgit Pauli-Haack: Yeah. And I think the biggest piece that helps a user to one part be in control, but on the other hand, not have to think about too much about design or the block patterns. And I think they have come really a long way from the first idea of a reusable block that people used this kind of templates or block patterns, but then they were changing it and then they changed it over the whole page site. But now combining just core blocks into this amazing designs and design system, it’s really remarkable. Yeah.
So that’s definitely part of that show notes today is that video. And we also shared the article that the WP Tavern posted about that. And then just today I found that Pantheon published an article by yours truly like what to expect from WordPress 6.0. And it goes a little bit more on the developer side. And apart from the enhancements, talk about the enhancements for the writing experience. It’s more about develop oriented, how to code, with code examples for the new pattern features on pulling in patterns from the directory wire theme, JSON Slug, or also create page layouts on the create page action, and then some block locking examples, and also how to establish those style variations in the theme, JSON. So it’s a little bit different than the release post on WordPress.org. So, Greg, what are the most intriguing features that you found for WordPress 6.0?
Grzegorz Ziolkowski: So you already mentioned them, from the coding perspective, you covered how to integrate them on, on the owners of the site. And I think for the user, very exciting possibility is to use style variation when they are provided with theme because everyone have different taste and style variation allow you to quickly change colors, fonts have presets that you can quickly pick one and another, and another until it’s something that clicks with you and you don’t have to go and change every setting on the website yourself is just, you have bigger chance to… The other thing block locking. I think it’s great and it has a lot of value, but it’s still missing much more detailed control because everyone can lock and unlock now, which is nice, but you can change that.
Yeah. But the idea is that in the future, you could have permission-based rules. So, as a site admin, you could just block everything you want for everyone else or whatever else you would like. So this still needs some development, but it’s the step in the right direction. And also all the work on patterns that how it evolves. You mentioned that how it was limiting and the beginning, and it was introducing with classic themes in WordPress 5.5. And it didn’t have so much power because for the content of the post, you don’t use design so often, but with templates, it’s just so powerful having a way to insert a footer, a header. And now this is even integrated more contextual. If you use this in line inserter and you are on the bottom of the page, it’ll propose you some footer patterns in other places, it will propose other patterns.
So it tries to be smart and help you to do the right choice. So it’s no longer, only core blocks in those inline researcher, but also patterns. And yeah, in general, I really like how all the concepts that we already know, they build on top of each other that you mentioned reusable block. So you can now do sort of magic things. You find the block pattern you like, you convert that to reusable block and suddenly you have something you like, and it syncs with all other places the same applies with template parts.
You can pick from the block directory pattern of footer and just magically it’s there and synced suddenly with all other places. So I’m looking forward to seeing more and more things like that, so people no longer have to worry that they open a new template or new post and they see blank canvas and they don’t know what to do. Now they open an inserter. There is so much inspiration in there and that you… it’s just a different experience. It’s so much easier to create the same website that you see on the themes demo side than it was before.
Birgit Pauli-Haack: Yeah, well said, Greg. That said, I also like the writing experience. So the favorite feature that I have, it’s not a big deal, but it’s actually helping, when you are doing a lot of in-line linking you have the two square brackets, and then you get a list of all the latest posts or pages that you’ve had. And then you can do in in-line linking for your site. And before you had to kind of look for that and search for it, and what’s the name of it? And you had to go out and then you had this. Yeah, so this is really nice. And I liked all those keyboard shortcuts that make it, I don’t have to change from keyboard to mouse and have a very smooth experience yeah. So 6.0 is out.
Grzegorz Ziolkowski: It’s definitely for experienced users because there are lot more gems like that. Once you discover you never want to go back and you use all the methods. But it takes time, but…
Birgit Pauli-Haack: Yeah. And then the same, what trips me up. So the WordPress had this for a long time that when you have a highlighted text, and if you have a see a link on the browser and you copy the link and you highlight text, and then you can just Ctrl V you can actually, it uses the URL as a link on that highlighted text. That trips me up everywhere else.
Grzegorz Ziolkowski: Yeah.
Birgit Pauli-Haack: Especially, so I know that GitHub took it over. Yeah, now when you want to highlight, or have a link there, you highlight the text on that. You have to URL Ctrl V works. Yeah. That’s really cool. And I use a user note taking app called LogSync. They have taken that on too, but the Google docs, every link I put in Google logs, I have to do twice because it just over click. I can’t do it anymore. It’s just so interesting. Yeah.
Grzegorz Ziolkowski: Another experience.Community Contributions
Birgit Pauli-Haack: Google docs get on it. We need that there too. Yeah. So another experience that I had during the WordPress 6.0 release cycle, during the beta and release candidates, I used a great plugin that I want to do a shout out for. And it’s called the Core Rollback Plugin. And it was created by Andy Fragen, who is a long time contributor to WordPress and also part of the beta tester plugin crew. And it allows me to select all the WordPress versions back to 4.0 and install it on a test site. So I was able to test the upgrade from 4.0.23, to 6.0, and does it work or does it bomb?
And then at first I was a bit disappointed because when I started it, I had a block theme enabled. And of course, then I can only have a WordPress version that actually can handle block theme. So I was only rolling back to 5.9, which didn’t help me much, but then I realized that, okay, I needed to change the theme. So I changed it to Twenty Ten theme. And then the other part was, how do I get to 4.0? I also needed to change the PHP version to 5.6 and I lose local WP. So that was really interesting. And then it took me maybe a minute or two to install the old version and then upgrade was WCLI to the next version. And that was so fast to test. And then I just went into the site again and did a comment or something like that, just to make sure it works. But that is really, it was very helpful.
So I’m sad that I didn’t know about it before, because sometimes when you had a WordPress install and the new version came out and you were way on the cutting edge, you had a plugin conflict or something like that. And then how do you roll it back to the previous version? And this plugin will save you so much time and headaches. So just make it sure that’s in your toolbox when you manage other people’s websites, because it can really help you with that, go back to the safe version within five minutes or so. And wait, the next two weeks till the next version comes out from workers. Yeah.
Grzegorz Ziolkowski: Yeah. It’s also fascinating that warper still supports some old version that to get it working, you need to use PHP version that is no longer even developed like 5.6. But still, if people have that, they can use WordPress, which is mind blowing.
Birgit Pauli-Haack: Yeah. It totally is. And I think Serge is watching that percentage of users that still use PHP 5.0 very closely, because I think it’s going to be real soon that WordPress is going to skip it and say, “okay, yeah, from now on, we are not supporting 5.6 anymore. You got to have to be on 7.4” or something like that, but it’s that promise of backwards compatibility and not kicking users out just because they don’t know they are hosting environment that still uses these old PHP variations.What’s Released
All right, but this were two interesting weeks. So we had not only WordPress 6.0 come out, but in the last two weeks, we also had two plugin releases. One was 3.2 and the other one was 3.3 and we will cover them both today. So let’s get started. So Gutenberg 3.2 was released on May 11th and it had a few new features in there.
One was the new preference, persistence API, and we are also happy that it’s there. Now. It saves now the editor preference in user meta, not in local storage anymore for that the preference handling needed to be revamped before. So we talked about it a little bit in the last episode, but now it’s here in Gutenberg 13.2. So you won’t see the welcome guide. You dismiss the welcome guide and it will remember on the site. If you prefer the top toolbar, it will remember. And if you don’t like the full screen anymore, it will remember, but only on a site basis. So you can access the same site over and over again. And the user settings will be there for you.
Grzegorz Ziolkowski: Yeah. It might be also per editor screen. I mean, if you are on the edit site page might be different and on edit post page or widget page could be different. I don’t know, because I didn’t play with that, but I would expect that to happen this way, because in the past, those changes were independent, but it’s a huge change. We waited for so long to make it happen. It wasn’t a trivial task, but we finally have that. And it’s a huge improvement for all users.
Birgit Pauli-Haack: Yeah, definitely for new users and long time users. Yes. I probably will miss the welcome guide popping up once in a while…
Grzegorz Ziolkowski: And you can always enable it. There is a setting.Enhancements
Birgit Pauli-Haack: Yeah. So in that version also received a visualizer for the panning and margin of all blocks. So when you use the dimension settings of your block, blue outline appears on the screen around the block and expands and contracts, depending on the width of your padding and your margins. And that is really helpful for people that don’t know what padding and margins are, but they know they want the distance and they want the distance inside or outside. Yes.
Grzegorz Ziolkowski: The other change was for the comment query loop. So there is a new block, which is post comments form. And the idea was to reach the alt experience. When on the post page you would have comments section, which usually is a list of comments and there is also the form. So the form was missing. And now inside the editor, you have something that isn’t interactive, but just presents a preview of what you will see on the front end. So it’s on the front end, of course, there will be interactive form that you can use to comment on the website, which is a great change. And that brings the feature priority with the old approach that we had in WordPress 5.9 with the post comments block that is now hidden from the insert it’s still there.
But the idea is just to combine those blocks together in the future. So depending on what you use, what the team prefers, whether the new version of the comments log which allows you to move all the pieces around the rapid with group blocks, with all the blocks you can imagine within its template. And the old one is still based on PHP functions that all team authors know from the past, you can provide your own template with template PHP file. There is a lot of hooks, all the things. So I’m looking forward to see that combined to have a full experience for all the use cases we have for the classic blocks and for the new blocks.
Birgit Pauli-Haack: No, it’s wonderful. And I, there were about 10 new blocks coming to 6.0, with a common section. And this one, unfortunately it didn’t make it, but it’s coming then in 6.1.
Grzegorz Ziolkowski: No we made it, it was so important to bring the same experience that we added that, that was still during beta phase because, the release happens, but that change was already one or two weeks ago so that there was still time to include that.
Birgit Pauli-Haack: Oh, okay. Excellent. So there’s a full common suite. Suite of blocks for, for the common settings for themes and templates.
Grzegorz Ziolkowski: Yeah. It also came from user testing during beta phase that people were complaining that they cannot replicate, their old designs without this block.
Birgit Pauli-Haack: Yeah. So makes sense to backboard it to 6.0 yes. So we talked about the next version of the quote block and the next version of the list blocks are in experimental stage and you have to switch them on through the experience menu item on the Gutenberg plugin. And now with this release, the quote block version one now has the feature that you can exit the block just by hitting enter we know this from other blocks that works here with the list you have to hit enter twice, out of the block and then a paragraph block and the code block has now too, before you actually had to physically get out of the block by using the mouse or hitting tab or something like that. Yeah. So that’s really good. So explain to me, Greg, I’m glad you’re here. Explain to me, so I’m at the block API section where now it’s allowing the custom domain path for the view scripts, assuming that’s through register that’s for blocks and that you can have a different path than before.
Birgit Pauli-Haack: Excellent. So I know there was something important, but I couldn’t explain it. Thank you. What’s also in 13.2, is that the style engine now added typography and color to the back end for the editor so you can, can add it to the block styles and is it for the blocks, Jason, right?
And I think that’s the biggest win for this whole refactoring.
Birgit Pauli-Haack: Yeah. There’s a whole discussion about, is of one of the implementation about standardizing, how themes interact with the styling of the blocks and as well as plugins. And I think that’s also necessary to standardize that in terms of when, when plugins want to introduce new blocks, they need to be able to use the variables that are introduced with the theme JSON file to just seamlessly integrate with, with an existing theme. Yeah. So what’s, I’m really sad to see that go. But what was removed was the experimental PWA support for the WP admin, which pretty much was playing around with the idea that you might get an offline and still would be able to write your post and manage your site. There was an experiment by Ella Van Durpe I think. And I think it was a good experiment, but it wasn’t pursued any further because of course, had other priorities.
Grzegorz Ziolkowski: But there is PWA plugin from Google and you can also check it out and it has a lot of similar functionality but for the front end, which is also a nice thing.
Birgit Pauli-Haack: Excellent. Yeah. And I will dig that up and show it in the show notes link in the show notes, the Google PWA plugin.
Grzegorz Ziolkowski: Yes. And one interesting, I think from the release and being on the team, so together with Adam Janinski, we work on several improvements to the workflow of bringing code from the Google plugin to WordPress core. And we are using NPM packages as a way to share code from Gutenberg and use that directing core. And we introduce a change in workflow that is automated with GitHub actions. So if someone is using GitHub and actions that they know how powerful those tools are. And now we are tagging for the WordPress major release those packages and we can easily update all of them, by using only the distribution tax, little change in the code, but it simplifies so much things inside WordPress core and how the code is shared between those two code bases, which is quite interesting. Someone wants digging into strategies for managing deep projects. I recommend that reference.
Birgit Pauli-Haack: Yeah. you should write about those little tools or little ideas that make such a difference on the release of WordPress, because I can see.
Grzegorz Ziolkowski: Oh yes.
Birgit Pauli-Haack: That other people can really benefit from that. But I think it takes a little bit more strategic approach than just a PR that it has been in the release. Yeah. And the Gutenberg release. So that would be really great.
Grzegorz Ziolkowski: Yeah, it’s interesting because usually the code you need to write is the easiest part because all the tools are so advanced these days, Github has APIs tools for that. And so it’s not an issue to code something. The issue is to come up with all the steps, what needs to happen after what, so it works together. So we definitely will be updating documentation for the release team for future releases, how we use the tools we improved and yeah, also for NPM packages, that’s also something I plan to write to describe how the process has changed with this release and to benefit everyone.
Birgit Pauli-Haack: Yeah, definitely. So I found with the release that quite a few things have been done by the same people over and over again. Yeah. So the documentation is kind of the shortcuts for them, but if a new person would step in, then it kind of needs a little bit more flesh and strategy kind of yeah. High level information in there. Yeah. So what’s again, is there anything else in Gutenberg 13.2, we wanted to talk about? I guess that’s it for 13.2 and we are going right into Gutenberg release 13.3, that was released yesterday. Ryan Welcher wrangled the release over the finish line and posted the release notes. There are comments from 55 contributors among them with their first time contribution. Yay.
That’s really good. I was really amazed at the 6.0, sorry. Just digress again. Those WordPress 6.0 release was interesting that there were also 25% of the 500 plus contributors when new contributors, they had never done this before. So it was very interesting. It wasn’t, as I think previous releases 5.8 and nine were a little bit higher, but still, that’s a very high number of new contributors and…
Grzegorz Ziolkowski: Yeah, the number of contributors is really interesting thing we know for Gutenberg about people who contributed with scope. It’s now over 900 people and, it’s only code and there’s so many more people that help with testing with finding issues, trying to, provide designs, documentation. That’s a lot. And for core, we don’t know the exact number for all releases because we have core commuters. So which is a smaller group, like 60 or 70 people only. But I would love to do to get the exact number of people who ever got props for WordPress core, that would be a huge number.
Birgit Pauli-Haack: Yeah, must have been in the tens of thousands of people there.
Grzegorz Ziolkowski: Yeah.
Birgit Pauli-Haack: Yeah, and you said it right. It’s not only those people that commit code, but it’s also those who, who argue about the best features, how to approach it. Yeah. and comment on things or review PRs or patches. So yeah. It must be a huge number and it’s still a huge number if you also consider the people that write documentation, the people that organized meetups, the people, they alone, 780 meetups in the world. Of course, the last two years, they were a little bit crippled because of the pandemic situation, but they will come up again and organizing months over months of meet up Wordcamp meet up, Wordcamp organizers that it’s just really amazing, people that test things. There are 20 different themes on make.wordpress.org that people could join and see what they can do.
So if you want to do something, just a little pitch here, it’s the end user documentation team still needs writers. They triage a lot of things and all in GitHub now where you can look for the first night issues, good first issues that you could start writing and help beef up the documentation. And if you are interested in doing just that, feel free to write to me or ping me on slack or on Twitter. And I’ll have you get onboarded on that.Gutenberg 13.3
Well, let’s dive into 13.3 release. So the first thing is you can now transform a cover block into a media text block and keep most of the design too. And that’s fantastic. Because sometimes you want to do that and you couldn’t. So you had to delete the cover block and start all over again.
Grzegorz Ziolkowski: Yeah. It’s really intriguing how far you can go with transform these days and also how block adjust, because now it’s not only content, but also a lot of styles and those styles are also, taken from one place from version to another, which is quite a complex thing to do.
Birgit Pauli-Haack: Yeah. I tested it in WordPress 6.0 there is this feature where you can transform from a paragraph into a quote block or a list block. And it also keeps background color and text color. And it is really amazing. Yeah. And this transformation from cover to media text did not make it, but it’s now in the Gutenberg plugin,
Grzegorz Ziolkowski: I’m a little bit surprised to see that, but also it’s a great news that table of contents block is back in the Gutenberg plugin. I mean, it was disabled at some point because it’s hard to sell. I mean, it wasn’t ready for pride time for some reasons, but now it’s back and it’s still experimental. So that means it still needs some testing, but it’s really nice, especially for posts where you have a lot of headings because it automatically generates tables of contents, how the name says. And because of that, you will have a nice overview of what’s inside the post. And it’s also super handy to be able to go to the section when the post is very long. So that should have a lot of usage on some websites.
Birgit Pauli-Haack: Yeah. And it automatically detects your headings and creates if they’re not already in there anchor links for them. That’s how it works. So you could also use the same anchor links if you want to link from outside of the post, into the post to a certain section. So that’s definitely a nice side effect for that. And it also does it, if you have on page breaks, it detects the heading over all the pages. And it also can jump from two headings that are on subsequent pages for that post. So it’s quite sophisticated in the feature set. One feature set that I’m actually missing is that it automatically creates the table of content as a numbered list. And I have never used a number table of content on a website. So it was always in a bullet list, but I cannot change it back into a bullet list.
What you have to do is to kind of create a static block out of that. And then it does a bullet list. But it does not update anymore when you add a heading. So then you have to delete it and start all over again. So that’s a little bit cumbersome, but I think I will file a feature request for that to have it as a real feature I advocated for it, but it didn’t make it in the first version. So what’s also interesting actually in this release is that the post terms, you can now add dynamic variations for custom taxonomies. So when you have the post term block, it kind of also lists every taxonomies that are registered with your site. And then the other part, what I really like is that query loop block now has a parents filter.
So when you’re working with, with a page, you can now use the parent filter to display content from the children of a particular parent page, which eliminates the need for a plugin again. Yeah. I think I need to count all the plugins that I have that I won’t use anymore because work has it built in, and the place on a list of the sub pages, or you can, even if you have featured images with it, you can even make some nice cards with that on the parent page and show up the next subsequent pages. At the agency. We had quite a few requests for that because some people couldn’t rock the post kind of post page thing and they always want the pages that’s so static. They never change, but you want them a different path of discovery and not just through the navigation menu, but also through imagery on the page where it can say, “okay, now you go here, then here and here and here,” it’s really interesting.
Grzegorz Ziolkowski: Yeah. It’s also, the way query loop evolves and how many new features gets with every plugin. It’s really interesting to follow.
Birgit Pauli-Haack: So let me ask you this, are teams working, or is a team working on the idea that you have a developer ahead who wants to kind of modify the query a little bit more granular than just what you offer through the interface, kind of handled SQL statements or something like that.
Grzegorz Ziolkowski: So to also support SQL, I don’t think that it’s on the roadmap mostly because it’s way too complex and you still can go and code yourself something very custom if you want to right? So it wouldn’t be that hard to replicate, maybe let me put it this way, replace the server implementation of the query loop, the wrapping block and provide your custom query from that. That’ll be much easier in my opinion than allowing users to start filling with as well and all the square injection, vulnerabilities and stuff like that.
Birgit Pauli-Haack: Yeah. I hear you. It’s a small thing, but in the new version, you now have tool tips on the split border radios control. So when you’re in the sidebar work on the border radios, you actually get tool tips where you are actually working on it. Is it the top part of the border or is it the left or the right part or the bottom part? And that’s really some quality interface and you can actually have a radio separate. And I didn’t know that, it’s kind of here now. You can have a radius control just for the left border. Yeah. It’s a little round, but the other three, they don’t have a radius at all. And it makes for nice, interesting forms. Now you can do this with Gutenberg in there.
And I also like the color controls are now merged with a dropdown component that is a little bit more helpful. It shows when you change the background color to a gradient, it now also shows you in the sidebar when you just open it, what is the current color? And it also shows the gradient instead of just the breakdown color. And you surprised that’s not the background color that I had. It’s a gradient. And now you see it all. But the color panel has gotten quite complicated as well. With the same with you click on it and then it comes out and then you have two tabs on there, one the solid color, then the gradient color. And then in the gradient, you can then change the radius and it’s gotten quite complicated. And I can see that certain things take a little longer or need to be tested first with one block before it’s rolled out to the other blocks yeah. But that makes also for sometimes it’s not consistent over all the blocks.
Grzegorz Ziolkowski: Yeah. But it also makes a lot of sense to combine all those related tools into one. So the sidebar is not so overwhelming for users. So before we had many colors, if you would open that, a year ago, that would be all those things that you see now in this tool table dropdown, they were inside the sidebar, it’s just the necessary step to organize all that better.
Birgit Pauli-Haack: Yeah. I like that curation of settings, then there is for each section heading for the color there’s on the right end side, sometimes a little too subtle, the three dot menu where you can also switch on and off some features. Yeah. By default, you only see the color for the text for the background, but when you click on the three dot menu, you also see that you could actually manage the link color, but it’s not offered for every block, but you can switch it on if you need it, for instance, for a quote block or for a list block. But sometimes you need to kind of really go beyond the obvious and click on that three dot menu to find additional features that you knew were there before, but now are a little bit hidden. Yeah, that is…
Grzegorz Ziolkowski: Yes, but if you are a new WordPress user, I’m curious how it works, because it might take some time for people to discover that the three dots actually allows you to enable more controls or remove the controls that are there, but they don’t like.
Birgit Pauli-Haack: Yeah. So the same…
Grzegorz Ziolkowski: Feeling of similar changes, there is one, I would say big change because the block list, the thing you see on the sidebar, but the other side, the one we were talking was on the right side. But on the left side, you can see all the list of all the blocks that are on a given page or template. And that’s very important for the editing experience, especially for templates where there’s a lot of nesting involved. And now there is an option in your settings to show openly view as default. So before you have to click a button to open that list, but you can just dock it and it’ll be there all the time.
Birgit Pauli-Haack: Yeah. I really like that, especially. Yeah, you’re right. The list view is such an integral part working with templates with all the nested blocks. Yeah. So having that open all the time really cuts down on the load time of the editor and your work workflow when you work quite a few templates or even in, on a normal post. Yeah. But I don’t think that setting is available for the post editor. I think it’s only for the site editor.
Grzegorz Ziolkowski: Yeah. I don’t know about that.
Birgit Pauli-Haack: Yeah. It’s only for the site editor it’s post editor. Well, has that too always open list view. Yeah. So I looked at the preference tables that were in the screenshots. It’s for both the post editor and for the site editor. Yeah. A lot of people ask me about that when I demoed some of the new features. So what else do we have?
Grzegorz Ziolkowski: There’s there is still no official post with all the change lock files. So we are using something that was prepared earlier. And so we might need to jump a little bit.
Birgit Pauli-Haack: Yeah.
Grzegorz Ziolkowski: To find other items that we have highlighted today. And one of the change is for the heading block. And now we have font family support there. So it was available in other places now it’s been enabled there for future party.
Birgit Pauli-Haack: Yeah. And a lot of people have been waiting for that our user can now change the font family for the heading block and not just the theme developer. And there’s also a enhancement for the gallery block, but especially for converting a classic block gallery into a gallery block to also include the image caption up until now it didn’t come over with it. So that’s definitely a plus for those who converting galleries to gallery blocks. Yeah. And the other two things that are highlighted here are actually part of the table of contents block. And we already talked about that. So I think we are through with that. Was there anything in the three 13.3 that you wanted to point out
Grzegorz Ziolkowski: There is a lot of items as you rule in the change logs from two releases. And also we discussed work 6.0. So I think we covered a lot today.
Birgit Pauli-Haack: Yeah. But we didn’t cover all and we never cover all. So dear listeners, definitely check out the change log that will be on the make.Wordpress.org blog when it comes out as a what’s new in Gutenberg 13.3. Yeah.What’s Discussed and in the Works
And we are at the section, what’s discussed and what’s in the works that hasn’t been released yet? But it’s definitely top of mind and or discussed quite a bit. So there were some discussions on what keeps theme developers or agency developers who build themes for on taking, for instance, block themes or other features of the site editor.
So those issues come up quite a bit, not quite a bit, but once in a while, and to have some ideas on what would be good for an agency. So one of them was that made it into WordPress 6.0 was for instance, that themes could register blocks. And I think Grzegorz, you were quite instrumental in that to get it fixed or get it implemented that although the recommendation says that blocks are the territory of plugins. But we heard from agencies that we are building custom themes just for that one site implementation that had additional cost also to deploy a theme as well as blocks in plugins to make it available for them. So that was one of the discussions that came out of…
Grzegorz Ziolkowski: Yeah, also the use case was that sometimes themes require some very custom design and this is a way for them to bundle a block that just is targeting that specific theme. And it wouldn’t make sense in all, all other places. And, but yeah, it’s not the recommendation blocks belong to plugins.
Birgit Pauli-Haack: Yeah, but just because it’s technically possible, doesn’t have to be, you have to use it, but it’s available for those who really, really need it. Now, before they had each agency or each freelancer who needed it, came up with their own hacks to make that. And now it’s just the standard way of using register block type on the theme PHP theme.
So to alleviate some of the adoption hurdles or blockers for adoption there’s now a new label on the Gutenberg rebuild called focus blocks adoption. And it’s used on the Gutenberg repo to identify those specific issues that if they would be solved, they could remove the blockers from adopting blocks or block themes. And I think it’s an interesting concept now to highlight those one of them is one issue. He got that label is by Fabien who has issues C7943 titled allow the usage of block based template parts without using block based templates. And that’s an interesting idea for classic themes that want to gradually adopt what’s possible now with the site editor also for their themes and how to implement that.
And part of it is already Grzegorz told me, and Ari has it in the issue is already available since 5.9. But what this particular issue is talking about that it also activate the site editor to edit those template parts without editing any other templates or sections.
Grzegorz Ziolkowski: Yeah. So idea was that if you have a classic theme, you can also provide a template part HTML file that will contain this template particular template part, and that worked, but you wouldn’t be able to edit that. But the proposal is to open the UI for the same, that is inside in block themes for classic themes, which is an interesting way might be a challenge. But the more we open those solutions for classic themes, the better everything becomes.
Birgit Pauli-Haack: Yeah. And it follows the narrative that Matias actually had when he joined us here at the show, after he published the preliminary roadmap of 6.0, when he said that all the things that come with the block theme are not there necessarily to replace how themes work. It’s more to expand the reach that classic themes can offer to their users or the site owners. And I really like that narrative because it kind of, has that new can come in, but in piece and bits and you don’t have to adopt it completely, it’s a gradual adoption. And even in two or three years, you still have a need for classic themes, but there might be a need to open that up for some of the user controls or for the site owners controls. So yeah. Block themes are not replacing or making themes totally redundant. It’s actually opening up the whole place for new things.
Grzegorz Ziolkowski: It also opens an interesting world where you have a block theme, but you’ll like it, you could switch to the classic block and still retain template parts that you build in your previous theme, it’s WordPress, everyone can do whatever they like.
Birgit Pauli-Haack: Yeah. And now you can do even more and you didn’t know that you liked it. Yeah. Like gradients.
So then another discussion that came up now that 6.0 is out Matias Ventura, the lead architect also updated already some of the tracking issues. And I’m sure there is a new blog post in the making in outlining the roadmap for 6.1. But he already has a site editor and template roadmap tracking issue about 19 tasks. And that’s about the site editor and how to create template and template parts changes to the interface or updates to the interface to make it for impossible, to edit a template part properties and focus mode. What is a focus mode? It’s another way of seeing the editor. There’s also a browse mode coming to the site editor that you look at it from, you just browse the designs, but you’re not editing.
So yeah. And other things like restricting block editing capabilities, we talked about the block locking at the beginning of the show that comes in 6.0, and that is now that needs to be expanded on. You mentioned that it needs to be role based of course, but also you probably want to lock down the editing part of a footer or header that people can edit it. Not just remove it or move it, but also not edited that is still missing.
So there are quite a few in this tracking issue, hints of what’s to come. And if you’re curious, we of course share the link in the show notes and what he did for template for the site, edit 10 templates, roadmaps Matias Ventura also published a global style, ongoing roadmap that he updated. And that covers some of the style engine that we talked about. If you want to learn more about it, also the main interface for making changes to the global styles, browsing styles, without having to edit things, web fonts that would just have the web fonts for the style variations right now. But the big part of the web funds API didn’t make it into 6.0, but it will hopefully make it into 6.1.
Grzegorz Ziolkowski: Yeah. Also interesting discussion on Twitter where Matias were involved about the future of web phones that maybe openverse could host some web phones and having those open source version of phones, integrated with the WordPress for everyone. That’s also interesting perspective and general openverse opens so many new ways of reusing content created by other people, which is images, videos, music, and whatever… Phones. That would be another way.
Birgit Pauli-Haack: Yeah, and color palettes would actually be also quite interesting. Yeah. So you can swap out the color palette of your theme and just by bringing it in from the openverse. Yeah. Oh, did you see that there’s a new contributor batch if you added photos to the openverse, to the WordPress photo directory, you can now see that on your profile. Open verse open so many different things for WordPress. It’s amazing, yeah.
Grzegorz Ziolkowski: I already have this batch. I just checked.
Birgit Pauli-Haack: Yeah me, too
Grzegorz Ziolkowski: I Uploaded two photos.
Birgit Pauli-Haack: Yeah. I think I uploaded four or so but yeah, it doesn’t matter. It’s a contribution and it will be honored. Yeah. So you have the site editor, the template, the global styles tracking issue. And then the last one is pattern as the section elements. That’s kind of the next phase for patterns and interesting proof of concept there’s first a tracking issue. And then James Costa has quite a few little videos and what he kind of considers as a browse mechanism for where you can browse through certain block patterns for the header, for instance, but you see the full page and that will make working on their site so much easier when you’re actually not only just looking at that section, that’s visible in your screen, but you can see the full page. And that’s also available for posts, for instance, or for pages that you create. So there are quite a few things in the works that hopefully make it.
Grzegorz Ziolkowski: It, the idea for those sectioning element is really interesting. You mentioned that you can just have the recent exploration is to have zoom out mode. So, you focus on the header and then you get ways to quickly switch the versions of this header by using block patterns or maybe pre-existing template parts, and you just use arrows or something else depending, or how you use that. And how’s going to maybe implement, and it just quickly switch to another version. Another, until you find something that clicks for you, but it’s inside the page. It’s not that you open a model, then you see only just some preview of these things, but you exactly see how it fits to your website.
Birgit Pauli-Haack: Yeah, and so we will share the links to those comments and PRs in the show notes. And if you’re interested in where things are going, definitely look at those and see what it does for you. And if you have ideas, how it’s made better or what does not look right or how it can be augmented. Yeah. Chime in now is the time because now people are working on it. And the last discussion that I wanted to point out is that during the FSE program Anne McCarthy did a hallway hangout to talk about the FSE programs and how it works and all that. And then there’s an issue created or it’s not an issue, it’s a discussion post on the developer experience category on the GitHub discussions. And what the full site editing for agency use case is what are the existing features that work that are available and then what are missing features.
And then as well as the features that can be improved, for instance, as a missing features, it identifies the robust permission system for the template editing, as Grzegorz mentioned earlier, or another one is allow editing for only template parts or only specific template parts, but not other parts or other templates that is much more granular. Another interesting thought was that WordPress inland CSS does not always respect the editor font sizes. That might be a bug, but it could also be that some of the mechanics don’t work as well.
But that comes all out of a hangout meeting, which is a hallway hangout meeting is kind of an informal meeting of brains, people that discuss certain things. And this came out of it. I shared the hangout notes, hangout recap, post by Anne McCarthy, as well as this discussion at the GitHub repo. So for all you interested people. All right. So Gregorz, we are at the end of our show. I’m so glad that you were able to jump in for Mary Job this week and walk us through some of the things. Thank you so much.
Grzegorz Ziolkowski: That was a pleasure to meet with you again and talk about Gutenberg.
Birgit Pauli-Haack: Yeah. And as always the listeners, the show notes will be published on Gutenbergtimes.com/podcast. And if you have questions and suggestions or news, you want us to include sent them to firstname.lastname@example.org that’s email@example.com. So this was it from me. Thank you for listening. Thank you for stopping by. I’m glad you were here and I will talk to you in two weeks. I say goodbye and goodbye, Greg, to you until I see you again.
Grzegorz Ziolkowski: You for having me, Birgit. It’s always a pleasure. See you goodbye.
Birgit Pauli-Haack: Yes. And come see us all at Wordcamp Europe. Bye bye.
Update to BP Rewrites 1.2.0 today in your WordPress Dashboard, or by downloading from the WordPress.org plugin repository.Many thanks to 1.2.0 contributors
Today marks 19 years since 19-year old Matt Mullenweg partnered with Mike Little to release the first version of WordPress based on the b2/cafelog software. The blog where he shared his thoughts on life and tech was starting to get more traffic and he wanted to ensure its future after the b2/cafelog’s main developer disappeared.
Mullenweg had the vision for what WordPress should be, even before it had a name. It centered on extensibility, a hallmark feature that has made the platform as popular as it is today:
What should it do? Well, it would be nice to have the flexibility of MovableType, the parsing of TextPattern, the hackability of b2, and the ease of setup of Blogger.Matt Mullenweg – The Blogging Software Dilemma, January 24, 2003
Although Textpattern, the interesting new publishing tool at the time, had everything Mullenweg might want in a blogging tool, he wasn’t sure about its licensing at the time. He decided to fork b2/cafelog, which lives on today in a different form as WordPress, thanks to its GPL licensing. Mike Little joined the effort and the rest is history.
The highlight of this year’s anniversary celebrations is the wp19.day website created by David Bisset and his daughter Olivia Bisset, who also managed the project. WordPress users and contributors from all over the world left their heartfelt greetings to celebrate the occasion. Reading through, it’s easy to get a sense of the tremendous good WordPress has done for the world, giving so many a voice, a livelihood, and a chance to live their dreams.
The wp19.day website also featured video submissions from WordPress enthusiasts. Although many first came for the software, the common thread among those who have stayed is the value of the community that has grown up around the project and the leadership it has cultivated. WordCamp and meetup organizer Joe Simpson said WordPress empowered him to take a leadership role in his local community.
“Our community here is nurturing – it’s a family,” Simpson said. “I’m excited to see where we go from here. Happy birthday, WordPress.”
Matt Mullenweg also joined in the fun of celebrating the milestone by contributing his own greeting to the wp19.day project. In his video submission, he said it’s very rare for a 19-year-old software project and its community to not just still be surviving but actually thriving and “doing better than ever.” He thanked contributors of all kinds who have helped people find their way with WordPress.Matt Mullenweg on WordPress’ 19th Birthday – video source: wp19.day
“That is a testament to every single person who has ever told a friend about WordPress, participated on the forums, had a translation, contributed code,” Mullenweg said. “Anything that’s been part of the WordPress ecosystem is part of why WordPress is transforming the web and making it into a place that is more open, more inclusive, more democratic, and a place that we want our future generations to grow up in.”
Gutenberg 13.3 was released this week with support for an experimental new Table of Contents block. It is perfect for longform content that is organized by multiple headings within the document. The block automatically detects Heading blocks within the content and will display them with anchor links that jump to each section.Table of Contents block – video credit: Gutenberg 13.3 release post
Users may select the block without knowing how it works with headings. If the post or page doesn’t contain any headings, the block inserts a message prompting users to start adding Heading blocks in order to display a Table of Contents.
For sites that have registered custom taxonomies, Gutenberg’s Post Terms Block now automatically generates a block variation for each term. That means users can select a block to display all the terms associated with that custom taxonomy.
Other notable additions in 13.3 include the following:
- Query block now supports a “parent” filter that will display content of children from the defined parent
- Heading block now supports Font Family controls
- Save Block List default view preference – allowes users to set a preference for having the Blost Lick view open or closed by default
- New transforms between the Cover and Media & Text blocks
The latest release also brings dozens of enhancements and bug fixes to preferences, border controls, error messages, tooling, accessiblity, and performance. Check out the release post for the full list of changes.
WordPress turns 19 today. And as I did my first draft of this podcast, I found myself redoing it. I have it all wrong.
After a lengthy discussion, the Community Team has decided to make it easier for organizers to apply for regional in-person WordCamps. These are events that pull in a community from a geographical area larger than one city or metro area.
In past years, WordPress Community Support (WCS) saddled regional events with numerous additional requirements beyond regular WordCamps, such as preparing a proposal and a minimum of three cities in the region hosting local events, with at least one having hosted a WordCamp.
“The Community Team has decided to simplify the guidelines for regional in-person WordCamps,” Automattic-sponsored WordPress.org community manager Hari Shanker said.
“Moving forward, regional WordCamps will not need to go through additional steps (such as writing a proposal), and can directly apply to organize a camp for their region using the regular WordCamp application form.”
Shanker asummarized community feedback that influenced the decision to ease up on the requirements and move towards using common sense as guide for hosting regional WordCamps:
- Regional WordCamps could be beneficial in restarting events in a region in a post-pandemic situation. It would be a great way to revive the community.
- WordCamps should be evaluated on a case-by-case basis, with conditions such as the region, geographic size, country, etc.
- Successful Country-based WordCamps were held in the past, and the community team should not police event organizers based on the region. The event organizing process could be simplified.
- City-based events could be difficult to organize because it’s difficult for a small group to organize a big event. It also causes repetition and a lack of repeat value for sponsors. Regional WordCamps might be a great way to solve this problem.
Shanker emphasized that while guidelines are being simplified, it’s imperative that local meetups are presesrved when regional WordCamps are organized.
“Local communities offer more accessible ways to connect over WordPress, and more supportive pathways to participation in larger, more complex events,” he said.
Organizers who are interested in starting up regional WordCamps are encouraged to continue developing local leadership and will be required to impose a strict, two-year term limit on lead organizers.
More simplified guidelines for these events is particularly beneficial in Europe where many smaller countries find that regional WordCamps have a strong unifying effect for their WordPress communities.
“There is a reason that a ‘small country’ like The Netherlands is now in the top of WordPress contributors and companies,” WordCamp organizer Dave Loodts commented on the previous discussion. “It all started in the lap of all the previous WordCamp The Netherlands. Never underestimate the power of these kinds of events.”
Shanker is requesting feedback on the proposal, particularly on what metrics should be in place to determine the health of regional communities. The proposed change has already started receciving positive feedback.
“Switzerland is like the Atlanta metropolitan area in term of population (8 millions vs 6 millions = ‘similar’) and about 10 meetup groups,” Geneva meetup organizer and WordCamp Switzerland co-organizer Patricia BT commented.
“Since we had to rename Switzerland to city name after 2015, we knew it was unrealistic to have more than one per year in the country (like if you asked people of Atlanta to have one WordCamp per meetup group) so we moved it from city to city year after year, which was awesome to onboard new organisers, but still missing a ‘united’ event.
“It’s really cool that we can now go forward with WC Switzerland next year, as I feel we had lost a bit of the ‘Swiss community momentum.’ We will recreate that feeling again next year.”
Learn new skills and build your knowledge to enhance your career in WordPress! Post Status Upgrade is an ongoing series of live workshops centered around a particular skill or learning activity.
Post Status' motto — Give, Grow, Together — is more than just a phrase we repeat a lot. We live our motto. This training will give you key insights into how to facilitate group conversations with an eye to giving and growing together.
This is a training workshop for anyone who wants to be a facilitator or a participant in the small groups that Post Status will be rolling out soon for its members.Group Facilitation Skills with Corey Wilks.
Corey Wilks is a Licensed Clinical Psychologist and Executive Coach. His mission is to help founders, creators, and entrepreneurs build an Intentional Life using evidence-based psychology.
“How do I define an Intentional Life? Spending your most precious resource—time—doing meaningful, purpose-driven work that fulfills you. It’s about clarifying your Core Value, embracing your authenticity, and reaching your potential by building your life, and your business, around what resonates with you on a fundamental level.”Dr. Corey Wilks
StellarWP is a collective of WordPress innovators empowering business owners and creators with plugins and tools to help them thrive. We build great plugins, but we don’t stop there; we continually challenge ourselves to keep innovating and improving. Our solutions include the most trusted names in WordPress, with more than 2.5 million installs. Since 2021, we’ve grown to encompass seven brands and dozens of plugins. StellarWP is part of the Liquid Web family of brands.
Zach Stepek, Till Kruss and Carl Alexander have a conversation on how and if you can define a WordPress developer.
>> The post Woo DevChat, What is a WordPress Developer with Zach, Till and Carl appeared first on Do the Woo - a WooCommerce Builder Community .
WordPress.com announced a new “Starter” plan today for customers that bridges the pricing gap between the free plan and its $15/month Pro plan. The Starter plan is $5/month and includes a custom domain name, along with 6GB storage, and the ability to use payment collection blocks (Donations Form, Premium Content, and Payment Button).WordPress.com Pricing – 5/25/2022
When WordPress.com rolled out major, unannounced pricing changes on April 1, slashing free storage limits, users took to the forums to express their profound disappointment in the controversial update and the company’s lack of communication around it. After receving overwhelmingly negative feedback, WordPress.com increased traffic and storage limits on the free plan before officially announcing it.
Seven weeks after WordPress.com began testing the waters with pricing changes, the company has responded to feedback about the wide gap between the free and Pro plans. Many customers were diappointed to learn that they would have to pay $15/month to have access to custom domain names, even though they do not need the commercial themes and plugins included in the Pro plan. Some users expressed that they felt “trapped in the net” with the pricing updates and planned to shift their sites to new platforms.
The new Starter plan solves some of these customer issues but it is still partially subsidized by advertising. Customers on this plan and the free plan will have ads displayed on their sites. This is different than the legacy Personal plan, which was $4/month for no ads, a custom domain, and the ability to collect payments. The fact that the new Starter plan costs more but doesn’t remove ads is a point of contention customers mentioned in the comments on the announcement. It does, however, include Google Analytics integration, which was previously limited to customers on the legacy Premium plan and higher.
“The Starter plan is not meant to be a replacement for the old legacy Personal plan,” WordPress.com CEO Dave Martin told the Tavern. “Our goal with every additional pricing iteration that we launch will be to learn something new. The Pro plan and the Starter plan are two of many future iterations that we plan to experiment with.”
Martin also reiterated that customers on the legacy Free, Personal, Premium, Business, or eCommerce plans are able to continue on them.
“[If] you are happy with your current plan, we have no plans to force you to change,” Martin said. “You can stay on your current plan.
“Finding the right balance between the value that we deliver to our customers and the price that we charge in exchange for that value is something that generally has to be iterated towards. We plan to do just that.”
Moving forward, Martin said WordPress.com is aiming to do a better job at communicating important updates to customers.
“I made a mistake with how we communicated the pricing changes with WordPress Pro,” Martin said. “We listened to feedback from our customers, I took responsibility for it, and then we worked to correct that with this next phase of our pricing change. We’re constantly working to be better at communicating updates.”
It’s interesting to see how WordPress.com is evolving its pricing in response the market and WordPress’ changing capabilities. Whereas the legacy plans leaned heavily on selling access to commercial themes, full-site editing has changed the game, giving users more customization power than before.
The company is still planning to introduce a range of add-ons for the Starter plan to give customers more flexibility. It’s possible there will be add-ons for removing ads and adding more storage, but the company still hasn’t announced what they will offer.
On the podcast today we have Mark Root-Wiley.
Mark builds WordPress websites for nonprofits in Seattle, Washington, USA with a focus on accessibility and usability. He’s a long-time WordPress community member in Seattle and has previously helped organise WordPress Seattle meetups and WordCamp Seattle speakers.
He’s on the podcast today to talk about why he thinks that it would be useful for WordPress to adopt some CSS standards.
Over the years, as WordPress has evolved, the way that you implemented CSS was very much left to the individual user, themer or developer. You could do what you like, and that worked very well, after all, we all have preferred ways of doing things.
Now however, the reach of WordPress has outgrown those early roots and some 40+ percent of websites are using it. Projects that were built by one agency are often taken over by another. Users are often swapping themes to reflect their brand. Extra work is created for those inheriting sites as they try to unpick the way that the CSS is built and implemented.
Mark thinks that it’s time for WordPress to lay out some simple standards which are easy to understand, and if they became universal, would save us a lot of time and head scratching.
He’s not proposing anything radical, just some basic advice for the most commonly used CSS, and it’s quite a compelling idea which would need a lot of community buy-in, and possibly some top-down approval if it were to move forwards.
It’s very much the kernel of an idea at present, but thought provoking nonetheless.Useful links.
[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox has a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, creating standards for WordPress’s CSS.
If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to WPTavern.com forward slash feed forward slash podcast. And you can copy and paste that URL into most podcast players.
If you have a topic that you’d like us to feature on the podcast well, I’m very keen to hear from you, and hopefully get you all your idea featured on the show. Head over to WPTavern.com forward slash contact forward slash jukebox, and use the contact form there.
Before we start, I thought that I’d let you know that there won’t be an episode of the podcast next week. This is because I’m hoping to be going to WordCamp Europe. I’ll be there with my microphone, recording episodes for the coming weeks. If you’re going to be there too, it would be lovely to meet up.
So on the podcast today we have Mark Root-Wiley. Mark builds WordPress websites for nonprofits in Seattle, Washington with a focus on accessibility and usability. He’s a long time WordPress community member in Seattle and has previously helped organize WordPress Seattle meetups and WordCamp Seattle speakers.
He maintains NonprofitWP. A free guide for people building WordPress websites for their nonprofits. And has a few free plugins available on wordpress.org.
He’s on the podcast today to talk about why he thinks that it would be useful for WordPress to adopt some CSS standards. Over the years as WordPress’s evolved, the way that you implemented CSS was very much left to the individual user, themer or developer. You can do what you like, and that worked very well. After all, we all have preferred ways of doing things.
Now, however, the reach of WordPress has outgrown those early roots and some 40 plus percent of websites are using it. Projects that were built by one agency are often taken over by another. Users are often swapping themes to reflect their brand. Extra work is created for those inheriting sites. As they try to unpick the way that the CSS is built and implemented.
Mark thinks that it’s time for WordPress to lay out some simple standards, which are easy to understand, and if they became universal would save us a lot of time and head scratching.
He’s not proposing anything radical. Just some basic advice for the most commonly used CSS. And it’s quite a compelling idea, which would need a lot of community buy-in, and possibly some top-down approval if it were to move forwards. It’s very much the kernel of an idea at present, but thought provoking, nonetheless.
If you’re interested in finding out more, you can find all the links in the show notes by heading over to WPTavern.com forward slash podcast, where you’ll find all the other episodes as well.
And so without further delay, I bring you Mark Root-Wiley.
I am joined on the podcast today by Mark Root-Wiley. Hello Mark.
[00:04:02] Mark Root-Wiley: Hello. Thanks for having me.
[00:04:04] Nathan Wrigley: You are really, really welcome. I always like to begin the podcast with a bit of orientation. I think it’s very important that the audience gets to know a little bit about our guests. Who they are, what their journey with WordPress is and so on.
So although the question is a little bit generic, I’m going to ask it anyway. Please, just give us a little bit of a history about yourself specifically in relation to your WordPress journey.
[00:04:28] Mark Root-Wiley: Awesome. Yes, let’s see. It’s been a pretty long one at this point. I am a child of the web almost. So, even back in the middle grades, I was learning to make websites. And so, it’s always been my hobby and my passion. And so when I, when I went off to college and got a degree in sociology, of course, that was much less employable than web work.
So, I looked around at all the systems and I had some jobs and internships where I was working with Joomla and Drupal. And so of course I ended up landing on WordPress. So since 2010, I’ve been here in Seattle, Washington where I build WordPress websites specifically for nonprofits most of the time, and so, my journey has really been that about serving clients, building custom themes doing some custom plugin work, but really like, deep in the world of WordPress for well over a decade now. And, I got to say, I love it and I’m not considering going anywhere anytime soon.
[00:05:19] Nathan Wrigley: Oh, that’s excellent news. Now the topic under discussion today is going to be CSS and in particular, we’re going to reference right at the beginning, an article, which was published by Justin Tadlock on February 22nd on the WP Tavern website. And it was called the case for a shared CSS toolkit in WordPress.
And we’re going to get into the nuts and the bolts of that in a moment because Mark, I think it’s fair to say, would like to see some kind of overhaul in the way that WordPress handles CSS. And as I say, we’ll get into what that means in a moment. But Mark, I know that you may not be able to lay out the history of CSS in WordPress perfectly for us, but clearly you believe there’s a problem.
I’m just wondering if you could give us any insight that you’ve got into the way that the legacy of CSS in WordPress has meant that we’ve got a problem where we are right now. What has been going on and where are we at now?
[00:06:15] Mark Root-Wiley: It’s such an interesting question, and I think if I had to boil it down to just one sentence answer, you know, it’d probably be there used to not be very much CSS in WordPress and now there’s a whole lot more. To really expand upon that, I think what has happened is, you know, it used to be that WordPress really only had a little bit of front-end markup that it would put out. There were things, HTML for menus, HTML for the search form, HTML for widgets and themers just sort of applied their own CSS to that.
Maybe in some limited cases, WordPress had a little bit of CSS that they were adding to the front, but really very little. And with the block editor, we saw the project looking to really empower users to be able to control much more design of the sites they build, through the WordPress editor interface.
And if you want to give people more control over the design, you’re going to be, at the end of the day, you have to do that with CSS. CSS is the language we use to make design on the web. And so it has just become much, much more complicated. And I think all software, you know, to some extent, right, it’s always evolving, but I think in our world of open source, that development process can be much messier and much more organic. And I think that that can be a benefit sometimes. But I think that maybe this is one of those instances where, right now there’s a lot of different ways for accomplishing, you know, similar types of CSS on the front end. Certain blocks handle their CSS in different ways.
And I think we’re just seeing that, you know, it’s been what, three or four years now of the block editor and there still isn’t really a strong opinion of sort of, this is the way that the block editor handles CSS and that has made it really hard for, people in my chair. I’m trying to make themes that are going to work every time I hit the update button on WordPress.
There’s just more complex CSS. There’s more of it. It’s done in varied ways. With more code comes more complexity and, it’s time to try to bring some order to that complexity.
[00:08:20] Nathan Wrigley: So it’s a case of the project being older than it was 15 years ago. There’s more that’s been added on top. It’s like a layer cake. We’ve had update after update, after update and things have been added in and fiddled with. We’ve had complete turnarounds in the way the interface has been put together and so on Gutenberg and all of those kinds of things.
And, essentially we’ve now got something which you, I think it’s fair to say, you would like to have a bit of a reset. You’d like us to rethink the way that the CSS is handled. And you’ve got some ideas around that.
Could you give me, before we get into the weeds of it, could you give me examples of pain points that you believe need solving? And you can be as specific as you like, you could describe a particular website that you built and a particular moment where you realized, ah, there’s things that I wish were different. So pain points that illustrate well what the problem is.
[00:09:12] Mark Root-Wiley: Yeah, that is such a, such a good question. I think that in some ways, the WordPress 5.9 release gave us a brief set of examples that I think made things hard for a lot of us themers. What probably looked like fairly small changes to for instance, the HTML and CSS of the cover block.
There was I think one class that was removed from buttons that told you about the orientation of the buttons, how they were vertically aligned. But when that was removed, suddenly all these themes that had written CSS styles where they needed to know the alignment of buttons on their site, they just stopped working because that class had been removed.
So rather than even really an overhaul, I think it’s a lot more about refining the practices and making a public commitment to, in the future, we are going to include classes in all of these circumstances, so that you can rely on them.
We are going to output all of our CSS rules with a certain specificity. It’s time for the CSS to sort of be better, organized, more consistent, and just communicated better. Which is not really an issue of code, it’s more matter of having standards for the project. If anything that’s really what I am hoping to see.
[00:10:24] Nathan Wrigley: You’re not the first person to suggest that this would be a good idea. It feels in the article, at least anyway, you, you make the point that you are standing on the shoulders of giants, really. And do you just want to give a shout out to some of the people who in the past have elucidated what it is that you’re trying to do? There’s several of them, but I think it might be nice to give them some credit along the way.
[00:10:46] Mark Root-Wiley: Absolutely. Yes. I completely agree. I hoped that when I wrote my big blog post, this proposal that I know we’re going to talk about. What I see as one of the strengths is that there’s very little original thought in it. It’s really trying to bring together all these other great ideas from other people.
I think it goes back to, and I think you can still find it, the theme user experience standards, or TUX that came from Automattic’s theme team. And I think they have an example we should talk about in a little while. So, I owe a lot to them. Rich Tabor, I think about two years ago had some really awesome posts about what it would mean if we could standardize how we named font sizes, how we named colors and how we handle spacing and WordPress.
I think that’s a critical thing that we really do want to make happen. That’s something that I would love to see. And then, I think if you’re just tooling around on GitHub and following, you know, people who are filing issues and the Gutenberg repository, or writing about it. I certainly think Matias, one of the lead developers of the Gutenberg project has written really, really smart stuff about CSS.
And there were also I think, a couple of like small folks I want to give shout outs to. Louis herons on Github, talked about having a theme block contract. Things that themers can count on for blocks, making that contract. I love that phrase. I think that is super important. And I think also, uh, Andrew on ocean has written about needing different layers of CSS. And I really liked that idea too.
[00:12:11] Nathan Wrigley: Well, thank you. Hopefully, they’ll be listening in and they’ll acknowledge your acknowledgement, which is nice. So the idea really is you want there to be some sort of overarching structure. You want there to be some sort of consistency in the way that things are handled, and that WordPress Core would make moves towards that.
Now this is probably something that you’re going to have an opinion on, but there are out there already, all sorts of different ways of handling CSS. Frameworks, and what have you, you know. Just off the top of my head written a couple of down here, you know, you’ve got CSS Grid and Bootstrap and so on, but I’m pretty sure that that’s possibly not the approach you want us to go down. You don’t want to bolt those into WordPress Core?
[00:12:52] Mark Root-Wiley: Definitely not. Yeah. I think that WordPress has never taken a really strong position on like, this is how your theme code has to be written, and if you’re going to pull in an entire CSS framework like Bootstrap or Tailwind, that’s way more opinionated. That would be very limiting to anyone who didn’t want to do things that way.
So, I think, when I sat down and really thought about like, what is it that I as a themer want. What it was is really baseline standardization more about just making sure that all block HTML and block CSS are done in a similar way. So that they’re, they’re sharing styles, they’re sharing CSS classes.
I think that there is also a ton of power if we can just standardize key styles that every site is going to need. So colors and font sizes. The amount of space between elements, things like that. But certainly not going as far as something like Bootstrap where there’s, gosh, sliders and drop down menus and modal dialogues and all those things.
It’s not at all about that. It’s really, I think the word I really settled on is it’s, it’s a toolkit. It’s providing more tools that all theme developers, all plug in developers, we can all use and share, but we still get to choose how we use them and how much we use them. So that, if we want to play nicely together, you know, those tools are available, but we can still choose to do things in our own way where it makes sense.
[00:14:18] Nathan Wrigley: We mentioned at the start that there was a WP Tavern article, which in turn was written because of something that you wrote and I’m going to include everything that we talk about today as far as possible in the show notes. But if you wish to pause this podcast and go and read Mark’s piece, it’s called standardized design tokens and CSS for a consistent, customizable and interoperable WordPress future.
You’re going to find that over at There’s no, no hyphens or anything like that. It’s just M R W web.com. That outlines everything that Mark is talking about. And so that really frames the conversation that we’re going to have from this moment on.
Now you mentioned that you wanted some sort of standardization. Presumably if that’s the case, you believe that the standardization at the moment is lacking. It’s messed up. It’s a muddle for people to create things. Everybody’s using their own different ways of doing things. Just kind of outline the specific problems about fragmentation versus standardization. What is it that you’re trying to overcome? What are the problems in Core that we’ve got at the moment? Things that need amending. Things that possibly need creating or uncreating?
[00:15:35] Mark Root-Wiley: Yeah. I’m going to answer your question and I think I want to like start us maybe five years in the future and then walk backwards to get there. in five years, I think we’re going to see a lot of sites that were built with the early years of the block editor.
Like now suddenly they’re needing to move to new themes. And so what does that look like? And, right now what we have are a lot of what I think of as kind of in the moment decisions that have been made. Both by the themer and the editor. Let’s take the theme or example first.
So, the block editor from day one has always allowed themers to define named font sizes, right? So, they can call them whatever they want. A lot of themers have something like small, medium, large, extra large, I know. Justin Tadlock on the Tavern posted his extensively researched list of font size names that he likes. Definitely worth a read for anyone who hasn’t seen that.
But I think the critical thing is that you can call them whatever you want. You can call them broccoli, apple, bicycle. You can call them seven forty, two ninety six, even if that has nothing to do with their sizes. And so what this means is that if we’re going to switch to a new theme in the future, if we switched to a theme that uses different names, all those font size settings that were set on the last version of the site are just gone. There is no bridge.
And so if we could agree to some like naming schemes, whether it is small through large, or even just 0 1, 2, 3, 4, 5, 6, 7. Now, when you move from one theme to another, you’re going to inherit, the choices that were made by the editors of the site, and be able to keep content as intact as possible. And right now I think the systems that the block editor is giving us are not really encouraging that consistency.
And it hasn’t really bitten us yet. The problems I think are coming. And so when I talk about portability of content. That’s what I’m talking about is how, what happens when we move from one theme to another. And I think that when you make that process smoother, it’s because you have good standards and that’s going to benefit everybody, working all the time.
[00:17:41] Nathan Wrigley: So the idea then is that things would become more standard and hopefully the community as a whole would adopt some standards.
Now, although we haven’t discussed this in our conversation prior to clicking record, I’m curious about your thoughts about this. Do you have any expectation that this would be something that would be, if you like, top down, in other words, would this be something which you would like to just be reflected in documentation?
And it’s a thing that you could use, or are you looking for a framework for CSS where really there are standards, which must be adhered to. In other words, you don’t really get to choose. If you want to be a WordPress theme in the repository, then you must do it in such and such a way. And over time, you mentioned five years in the future, we slowly encourage people to become the writers of CSS in that way.
[00:18:38] Mark Root-Wiley: That is such a tough question. I think that I guess I’ll say a few different things. I mean, I think that whenever possible, it’s better to use carrots than sticks. And I think that, right now in fact, I think the theme dot json standard is a great one where, if you’re building, what we’re now starting to think of is like classic themes.
Like you can use the theme dot json it’s on, it’s up to you and you also get like a ton of benefits by doing it. So I think that if we had standards like this, there would just be tremendous benefits to anyone who uses them, because themes would sort of work more similarly and even, there would be ways where plugins could suddenly sort of start referencing theme styles.
I would like to think that maybe this could bubble up, and be, you know, a community standard that people want to buy in, but aren’t forced to buy into. At the same time, I don’t know what it’s going to take to get this moving. Standardizing semantic names is something, we could talk about it forever.
And so I know that I personally, like I put out, in my blog post, a bunch of suggestions for the names. I thought really long and hard about them. I have my reasons. And honestly, like if someone said, nope, we’re going to use this really weird naming scheme that I don’t really care for anyway, I would use it in a heartbeat. I think having standards is more important than the specific names of them are. And so I do think that, there could be some room for some top-down decision-making here. As long as it’s a fairly simple thing, and we’re not going to punish people for not using it.
In WordPress land, you know, maybe that means we’re going to maybe throw some errors on occasion if you’re not using, some warnings, excuse me, not errors warnings. But no errors, nothing’s going to actually quit working.
[00:20:21] Nathan Wrigley: You mentioned in the piece that there are some recent issues They were obviously some kind of catalysts for you, where you thought, okay, these kinds of things are happening and it makes it pretty obvious that we need to rethink this. I’m just going to read them out, and maybe this will give some context to somebody listening to this.
You say to quote, recent issues make the need for a consistent, transparent approach, clear. Classes that were previously present and used by theme authors have been removed in favor of inline styles. Okay, we’ll get onto why that’s bad. Inline styles are redundant, hard to override and remove valuable selectors for theme authors. New instances of important, let’s just say that, CSS rules catch theme authors by surprise. Markup changes to Core blocks were only announced after the fact.
Now, I don’t know if you want to take all four of those or just riff on generally why you think these are the core things which need to be addressed, but yeah, there’s obviously something in there that sparked your interest and made you want to create this framework, if you like. Let’s just talk about that for a minute. Have you got something to say around that? What is it that you’ve found problematic?
[00:21:27] Mark Root-Wiley: I certainly have things to say. I suspect that honestly, maybe it was just random, how many, how many issues in 5.9 there were that sort of just got my goat as it were. I think that this is maybe one of the areas where there has already been a little bit of movement actually, which is wonderful. So yesterday, was this day when sort of all the dev notes for WordPress 6.0 showed up on the make.wordpress.org/core blog, and it included a lot of announcements about some changes to things, that are coming in WordPress 6.0. And I think that that advanced notice, already feels like, maybe some of what I’ve been saying has been heard and, and that, that is really great to see.
So, you know, there’s going to be some changes to like how images get aligned, the quote blocks CSS, some changes around the group block in the block editor. And, I’m really happy to see that communication. So I do think that some of these smaller things were addressed, but I also think that the fact that some classes disappeared and some markup changed and nobody knew about it, and like important CSS got added. If you ever want to like really get a bunch of people worked up about CSS, just start talking about important.
I think the fact that those all happened at once, I think more than any one specific issue, it just felt like, okay, there’s a lot of people changing a lot of things all at the same time and there’s no cohesive vision for we’re trying to take CSS in WordPress.
[00:22:47] Nathan Wrigley: Yeah. So essentially you want there to be far less surprises in the way that things are released and also to have some cohesive framework that everybody can dip into and everybody understands because it’s been well-documented and everybody can buy into it. As you said, carrot, not stick, because it just makes sense.
The article on the WP Tavern website had a very large amount of commentary on it. More so than anything I’ve seen in quite a while, to be honest, a lot of praise for the idea of what you’re doing. A lot of people saying, yes, we need this, we need this right now. And to develop it a little bit further, you are, you’re keen to get involved in a semantic approach.
Now that might not be obvious to everybody. So what does that mean? What is it you hope would come out of this? We may have a different vocabulary, in use in the end, but the idea is that we’re going to be substituting words or not as the case may be. So talk to us a little bit about that.
[00:23:43] Mark Root-Wiley: Yeah. I when I’m talking about semantics here, it’s really about can we establish shared meanings for some naming conventions within our CSS? So, back to the font size example earlier, if we can all agree that every time we name our font sizes, we’re going to call them small, medium, and large.
And every time we create our color palettes, we’re going to start with a primary color and a secondary color and maybe an accent color. Having that shared meaning, that’s what semantics are, is going to just provide so many benefits, and it’s also going to speed things up.
There’s going to be less mental overhead, fewer decisions that themers have to make. There’s just tons of value there. Thinking back I had mentioned that the theme user experience standards were maybe the best spiritual forbearer to this kind of point of the proposal. One of the things they recommended is when you’re naming your menu positions to call them menu one, menu two, menu three, menu four. Maybe that’s not what I would have chosen, but I started doing it and I’ve done it ever since.
And what it means is that any time I switched one of my themes to another themes that uses that same menu naming convention, like, the same main menu just popped up in the header, right where I would want it to be without me having to update any settings at all, just because, our themes knew how to talk to each other.
So it’s really about, can we make our themes and plugins talk to each other better and, ironically or, or appropriately, I think that just means we all need to do a bit more communication together in the project.
[00:25:10] Nathan Wrigley: Let’s get into weeds of the areas you think ought to be covered off, with some kind of framework. I keep using the word framework. I hope that’s okay. So for example, you mentioned fonts and you mentioned that the fonts might have things like small, medium, large, and that could probably extend up and down.
But also there’s obviously other things in CSS that we would like to cover. So before we get into nomenclature of what those things might be, let’s just talk about the things that you want to cover aside from fonts. What other things do you think are so essential that we need to have a standard that everybody just understands?
[00:25:47] Mark Root-Wiley: Great question. So in terms of those kinds of like standard things that we should name, I think beyond font sizes, including font weights, because if you’ve ever used a font, you know, that some have nine or now in infinite number of weights. So we need a way to sort of have a standardized font scale. Colors and gradients I had mentioned.
And again, that’s something where WordPress already lets us name our colors and gradients. So let’s just agree to always call them the same things. I think font families. So what are you using for your copy versus what you’re using for your heading? And then I would love to also see maybe some border widths, and probably the biggest one that I am most excited about is let’s agree on one or a few named scales for spacing.
So the space between blocks in a post, also the space between columns. The space between a gallery. If we can all agree on those names, then we can have a gallery with small space, a gallery with large space. And that’s just always going to look good from theme to theme, even though those values are going to be different and up to the themer.
[00:26:53] Nathan Wrigley: So aside from the fact that you would like to take into account things like font sizes and weights, colors, gradients, font, families, borders, spacing gaps, and so on columns and what have you. There would obviously need to be things that are associated with those, and you, you mentioned font sizes, small, medium, and large. Do you have some sort of insight into how far each of these go? Let’s for example take font sizes or weights? Well, let’s go for font sizes just for illustrative purposes.
How far would you like to take that, and do you have a system for making it so that it can be extendable indefinitely? So an example might be, one dash large or something like that, or XL large or something like that. Just give us a flavor of how far that scale would go down as well as up.
[00:27:39] Mark Root-Wiley: Yeah, that’s a good question. So I think, if it were up to me, if I were making a top-down decision, I think I would just pick a scale of numbers. Either, you know, starting at zero or going up, or maybe even centered around zero with positive and negative numbers. I like the fact that you don’t need to know English to use a scale like that, and it is infinitely scalable.
I think the other scaling systems that a lot of people really like is what’s often called a t-shirt sizing. So instead of small, medium and large, we would just have S M and L. And the nice thing about that one is you can infinitely go in either direction.
So XL, XXL, XXXL. It gets a little silly after a while, but you can do it. Some people like to say like three XL instead of XXXL. And you can do the same with XS, extra small. I will say that I think that when it comes to what WordPress should be standardizing, I don’t think it makes sense for us to say that every theme needs to have a 15 point scale for font sizes.
Some themes are gonna want three or five and that will be fine. I like to think of, of the 80 20 rule. 80% of needs out in the world can be satisfied by only 20% of the possible names in this case, that we could come up with.
So I think that for something like font sizes, a seven point scale, maybe would probably meet everybody’s needs in terms of switching from site to site, and keeping things looking pretty good. Again, to go back to sort of like why I like to think of this as a tool kit. I wouldn’t want to ever say that themes can only have seven font sizes. Right. It would just be that if they want more than that, they’re on their own to go figure that out.
I will say that I did, I did a lot of thinking about this even after my blog post. And there’s, there’s a demo I put together that was showing how maybe we could even have a way of having really big scales that could kind of shift down to only a three point scale, or maybe you want to have a five point scale, but it skipped 0.4. I think there’s some clever things you can do with CSS custom properties that could allow that to happen. So you can find that demo in the blog blog post.
[00:29:38] Nathan Wrigley: Yeah. I ran that demo. That was really useful to look at that. But let’s move on to colors and much, much more constrained there. You just want a handful really unlike font sizes, which there’s definitely more scope with colors. You just want a few basic standards that will satisfy most websites I guess?
[00:29:56] Mark Root-Wiley: I think that’s right. And I think that the more colors that we defined, probably the more disagreement there would be. What purpose does the fifth most important color in your palette have versus what purpose does the primary or secondary colors have in your palette?
And so I think that, especially for colors, I think it’s the best example where if you had a bunch of standards, they probably wouldn’t actually be that useful. So let’s just, let’s keep it simple, right? Let’s not, over-complicate this. Let’s make as few things we all need to agree on as possible. So hopefully we can actually agree on them and move forward.
[00:30:28] Nathan Wrigley: The font weights and the font size is obviously really dramatically changed the way a website looks. And if you switch from theme to theme and those get messed up, it really can look remarkably different. And you mentioned spacing, so gaps and columns and padding and margin and all that.
Again, it can really catastrophic effect things. What was a very small space can become a gigantic gulf, given a change in theme and so on, and so I was just wondered let’s ask the basic question again. What kind of constraints are you placing on that? How many different things do you think you need regarding spacing and gaps and all of that? Are we looking at dozens of different options or just three or four?
[00:31:06] Mark Root-Wiley: My first thought was, we probably only need maybe five, and I think that that probably would be about enough. If someone wants to do a few more than that, that would be fine. I think that spacing is maybe a really good example of the other key reason why I would love to see themes like shifting to these scales, because right now, for the most part, when an editor wants to change the spacing, of something in their posts, they can, you know, set a specific margin value or a specific padding value.
They can say, I want the top margin of this image to be 24 pixels. And they’re making that decision based on how their content looks in that moment, on their screen with that specific theme. Let’s say design trends again in five years are like really into white space. Maybe that 24 pixels is going to look super tiny all of a sudden. So if we can allow editors instead of having to pick a number and on the next page, they forget that they entered 24. And so they entered 20. And like now there’s just chaotic numbers all over the place. If we just say like, well, at the top of this image, I want to have a large margin.
Now, when they move to their next theme, it’s going to be not 24 pixels, it’s going to be whatever that is in the next theme. It’s always going to look cohesive. And so I think it’s really important to point out that it’s not just about standardizing the scales for theme developers, but I think if we provide these scales as options for customizing post content, we’re going to see editors just having to like not think so specifically, and that’s actually going to enable them to be more consistent, both in the moment and in the future, when they need to sort of switch their design.
[00:32:43] Nathan Wrigley: In a sense, you’ve read my mind because my next question was really about that because obviously your doing this for a living, you can probably come up with some naming system, some framework that works for you, and just keep executing that over and over again. But, that’s not the world. We live in the world where you’ll probably take over a website in a few years’ time that somebody else built, and it will be littered with CSS classes and CSS styling, specific to that exact one little thing on that one page and how on earth did that happen?
But it did. And so you need to go back and unpick all of the problems. So there’s that. The developers amongst us have probably figured out a system for themselves over the years, and they’ve got something which works. But when you swap a website, when you go and take on somebody else’s work, the fact that there’s consistency and stability in the naming of things would really help.
But then you mentioned the bit, which I thought was really interesting, about the non-technical users and having things in easy to understand, non-technical language that somebody can just get a hold on and okay. All right. It would appear that that thing, okay, might not be the most obvious name in the world, but right, it does that. And it seems to do that consistently over the site. That just makes sense for end users.
You described them as editors, but it could be anybody touching the website who has the capability to edit things. They, they really don’t want to get involved with CSS. In fact, that’s probably their worst nightmare that they need to think about CSS. They just want a handful of things, easy to understand. A minimal array of choices. The styling decisions were made months ago, and I’m just happy to stick with them.
[00:34:17] Mark Root-Wiley: You probably described that bit better I ever could. And, I think it really gets to this, there are lots of strong feelings about, is WordPress maybe becoming more like a site builder? Is it forgetting about being a content management system?
I truly believe that I think it can be both. And I also think that a lot of the work, especially around full site editing right now, like it has that more site builder mindset. And so I do think it’s important to remember that not every person with a WordPress site wants that super, super, super fine-grained control.
You’re right. I work with folks that just, they are busy professionals in nonprofits in particular. A lot of the organizations I have, you know, whoever is updating the website that is a teeny tiny part of their job. It’s probably not even in their job description at all sometimes.
They don’t want to be thinking about pixels or ems or if they don’t even know what MSR right. Can’t I just have some large space. That’s all I want, right. And so I think that not only are there these like huge technical advantages behind the scenes, but I really do want to just call out that I think this could actually like, just bring some simplicity to the editor and like help people make good decisions without constraining them.
[00:35:25] Nathan Wrigley: It also provides some kind of muscle memory options as well, in that if you have been working with a WordPress website, let’s say you’re working for company A over here, and you’ve been working with a WordPress website, and you go to interview for another job and they say, have you any experience with WordPress website?
Yeah, that’s fine. I can do that. Then you don’t need to relearn it over on this site though. That thing does. Okay, that wasn’t quite expecting that. That’s a lot bigger than I thought. It makes the whole process of editors moving from one website to another easier as well. So it just seems like a bit of a win-win.
Now having said all of that, we’re 15 years plus into the project. Everybody in the comments on the Tavern article seemed to think this was a cracking idea. You seem to think it’s a cracking idea, the likes of Rich Tabor, they think it’s a cracking idea. And yet here we are talking about it as an idea.
What’s holding us back? What is stopping this gaining momentum if it’s such a sensible idea? Are we, is the project too limited in time? Are we concentrating on other things? You may not have the answers, but you may have some intuitions.
It feels like it’s sort of working the opposite way. If we’re worried about what is the settings interface going to look like? And then like, we’ll figure out what the code, to make it actually work on the front end is going to be last. I do think that maybe working backwards a little bit more frequent. What CSS do we want, and now how are we going to make sure that it can be created in a sensible way? I wonder if that would help, because at least to me looking, somewhat from the outside, it doesn’t seem like folks are working that way.
And now having said all of that, I think it’s mostly a people and a communication problem. And I think that’s just harder than tech problems, right? Give someone an infinite amount of time and by themselves they could build the block editor on their own, but they certainly could not organize an entire community to agree on what to call font sizes.
That just requires folks coming together. And honestly like making compromises and, and trying to think about what’s best for the community and not just best for themselves. I think that’s really hard. I think we can do it. I think things like that have happened in the past. I do think that’s the fundamental issue and so I don’t, I don’t know exactly what’s needed though.
Again, that’s why I do wonder, could someone maybe make a, a bit of an executive decision on this one and, and just try to say this is happening and we’re going to be taking comments for this long, and then we’re going to make a decision and roll with it because we think the advantages to having a system are bigger than the disadvantages to any sort of, in the weeds decision that might make it through.
[00:38:47] Nathan Wrigley: I wonder if it’s because CSS, of all of the different parts of WordPress. The HTML and the CSS bits, they’re the easy building blocks, aren’t they? They’re the bits that a lot of people can get hold of really quickly. And with a quick flick through some kind of 1 0 1 tutorial, you can get yourself up and running with the basics of font sizing and padding and margins and, and quickly gain an understanding of it.
And so everybody’s been left to their own devices on that. The theme may very well take care of all of that, of all of that for you. And you may need to adjust absolutely nothing. You’re entirely happy with the theme and you don’t dabble. But if on that one particular occasion, you just wished to change that one particular thing you want the, I, don’t know, the, the heading to be slightly bigger, you just fiddle about and locate the CSS for that and modify it, add something to a style sheet, so on. And it’s fairly straightforward and it can be done by more or less anybody on their own, but it doesn’t require any consistency. Naming what you like so long as it works.
But your approach is, is slightly different. And yeah, it feels as if maybe it’s not got the momentum at the moment, but it feels like, you know, maybe with things like this happening, your initiative happening, people talking about it more, maybe somebody could take this on. And as you say, maybe at some point it does need somebody on high to make a decision executively and say, okay, we’re going to concentrate on this and it’s going to become important. But I don’t know that any of that is in the roadmap right now. So you may need to keep banging the gong for a little bit longer I think.
[00:40:23] Mark Root-Wiley: I actually, you know, I, I played a lot of percussion growing up, so I love banging a good gong. One thing I noticed is, you mentioned the number of comments on the Tavern post, I certainly got a few comments on my blog post and I published a, sort of a Github issue that the sister of the blog post and it got a lot of comments and, and I do think people are listening.
I’m not sure what’s required to sort of get some action steps. But, I will say that, what really made me think that, yes, I, I do think people are listening at this moment is there was a blog post, at this point, I think about a month ago, on the make wordpress.org/core blog called core styles and theme customization, the next steps.
The gist of that post is basically like here’s a bunch of links to get hub issues, please go read them and leave your feedback. The speed of change in an open source project is never going to be what we want it to be. And I really do try to always remember that when I’m feeling impatient, which is certainly why I wrote this whole thing.
But I do think that, it is important for folks to always be paying attention, always be sharing their mind, because I do think, at some point, especially if a lot of us keep talking about this, like some decisions will get made. And so, you know, make sure if you’re interested in this, make sure to go leave some comments on, on these issues and keep bumping them up so people can see that they are high priority for a lot of us in the community. I know it’s not just me.
[00:41:42] Nathan Wrigley: Yeah, it was quite interesting. The article that you mentioned, the core styles and theme customization, the next steps I was highlighting the bits that were basic replications of everything that you were saying. And quite a lot of the article got highlighted. Let’s put it that way. So it would seem that, on some level, there is movement here and people are definitely in agreement with you.
Do you have any insight into how this might get revved up and get more interest attached to it? In other words, are you willing to put your best foot forward and become somebody in the vanguard? Like I said, banging the gong. Or do you find that there’s probably a better way of, have you got any insights into where people could go if they agree with you and want to get involved to make this happen?
[00:42:25] Mark Root-Wiley: Gosh, it takes everyone in the community weighing in, I think that. One thing I’ll say is that, you know, I tried to get a lot of people to review my blog post and, even gives me advice on like, how should I publish it and who should I let know about this?
Cause I think that if it’s just me it’s ineffective. It does need to be a community. And so, you know, I would say I would love to see other people sharing their own proposals even. I don’t know. I don’t even know if you want to include this part, I don’t think it can just be me.
I it’s pretty silly actually. I published this blog post and then 24 hours later, we had a new baby. I definitely had to fall off the face of the earth and disappear for a while, but I was so thrilled to see other people, saying like, yeah, this is awesome. And here’s the couple of things I have to add.
[00:43:08] Nathan Wrigley: There’s a whole lot towards the end of the article where you outline the different problems that your solution may solve. I won’t list them all now, but all of it kind of makes common sense to me. One can only hope that the ideas that you’ve suggested go forwards and that people, as a community, can coalesce and come up with an idea.
And as you said, you’re not bound to any one particular way of doing it. It’s just the mere idea of standardizing things, whether it be named this or that is not important, it would just be nice to have some standard documented that everybody can adhere to and therefore make it a lot easier for all of us to make websites, whether we’re building them for clients or we’re just editing and tweaking them ourselves.
One of the concerns that we may have is the stability of WordPress CSS in the future. And I know that you have possible concerns that in the future, for example, Gutenberg blocks, there’s no requirement for the CSS, the classes, and so on to be the same today as it will be tomorrow or indeed yesterday.
So in other words, is that a problem, do you think? Is there any problem of consistency where let’s say that you build something and you ship It, and it goes out to your client. It’s using blocks, but suddenly unbeknownst to you, the blocks CSS classes all get modified, perhaps ever so slightly, but enough to break things. Is that a concern that you have?
[00:44:36] Mark Root-Wiley: It really is. And I think that this is one of the biggest things I sort of learned from this intense period of engagement I’ve been having with the project is that, in discussing this with other people and really closely going through, uh, lots and lots of issues and the Gutenberg Github repository. I found some core development team members really saying that they viewed the HTML markup and the classes and how the CSS has written as essentially like non-public, which is to say you can’t count on this stuff not changing in the future.
That was really shocking to me. And I think for a couple of reasons, I mean, th the first is that, you know, that’s never how it’s been in WordPress in the past. The HTML for the comment forum, the HTML for the search forum, like those weren’t always seen as, you can count on this, there are ways to change it if you need to, but if we’re going to change this stuff, it’s going to be a huge deal and you’ll hear about it in advance, and we’re really gonna try to avoid that.
And so it felt like, uh, that was a departure from how things had previously been. And also as I’m someone who I think follows the project, like more closely than average, even though I, you know, I’m certainly not like a day-to-day contributor, or anything, but this was huge news to me as someone who’s been working with the block editor for years now.
At least to me, I don’t even really know that it’s reasonable to just say that like, well, here’s a bunch of HTML and CSS. Themers I know you have like your job to do and you need to make changes to this, but like, you can’t count on it. That doesn’t really seem fair.
And I certainly don’t think people are really aware of that. They’re not going to go in and one day, you know, completely change the image block or the block quote block drastically. I don’t really think they mean we’re going to just completely change everything. But I do think it just highlights the need again, to really spend some time focusing on what is the HTML that can serve as best going forward. So we don’t need to change it.
What are the CSS classes and the ways of handling CSS styles that we want to commit to now so that we can all just know what’s coming in the future. And so that when there are changes made, they are a big deal, and people are given lots of advance warning and they can, they can react.
And so I think I’m seeing more advanced warning in WordPress 6.0, which is awesome. It’s time to have that conversation about how can we just reduce the number of times we need to make big changes like that. Cause people are going to style HTML, no matter what.
[00:46:58] Nathan Wrigley: Yeah. I wonder if it’s a product of the fact that the block editor is now basically a conduit to put in lots and lots of little components. So you might have a paragraph block and you might have a, an image block or a cover block or whatever it might be. You’ve got all of these different blocks and the functionality of that is not yet a hundred percent certain. In other words, aspects of it could change. And so I wonder if them communicating CSS will change is a product of that. They’re just not sure exactly what those blocks will look like in a few years time. And if they become radically different, maybe the functionality changes. Let’s hope it doesn’t. I’m sure it won’t, but if it did, some of the CSS may need to change. I don’t know.
[00:47:42] Mark Root-Wiley: I think you’re right on the money there. I mean, the block editor is so much more powerful and I want to be really clear that like, that’s awesome. Like the folks I work with generally, like love that they can do more complex things like columns, or like finally putting text on top of an image for the cover block.
Those are good things. And we had to have a more complex system to make that possible. So I’m not against the complexity, but I just think it’s really important that the folks who are building the product, don’t forget about those of us in the real world who, you know, have to make things work every day. And we have, we have new sites we’re constantly working on, the impact of even what can seem like a really tiny change can be really big.
To bring it all back around, I really do think that if we can have just a few more standards and right, if we can have that kind of contract between themes and blocks, I think we can reduce the amount of times that those kinds of changes happen.
I totally acknowledge that they’re going to have to happen every once in a while. If we want to have this like big, nice thing, we’re going to have to put up with probably more changes. Cause there’s more things that can change, but, let’s really, let’s take a minute and figure out how we can make that as infrequent unpainful as possible.
[00:48:51] Nathan Wrigley: Yeah. It’s interesting your language there. You described it as a big, nice thing. And in a sense it’s a big, nice thing made up of lots of smaller little nice things. Each of those little nice things is completely independent. And you may not use those on your website, but you may.
And if there’s modifications made to the CSS classes and what have you, the downstream effect could be pretty catastrophic. You know, if you’ve just built 50 websites and they’re all using the exact same block and some tiny little change affects you 50 times, that’s suddenly created a lot of work for you that potentially was not even thought about elsewhere.
[00:49:27] Mark Root-Wiley: It has. In some extreme cases, this is maybe the reason why some people are often building custom blocks that really they could just be using the core block, but I’ve, I’ve at least anecdotally heard that folks do that sometimes because they know that their block isn’t going to change, even if they don’t want to have to take the time to build it.
[00:49:44] Nathan Wrigley: If people Mark wants to find you. They want to actually reach out to you. You may wish to share a Twitter handle or a website or an email address. Totally up to you. Yeah, any place that you could be found if people are inspired to join you?
[00:49:58] Mark Root-Wiley: Yes. I am M R W web pretty much everywhere. So that’s, uh, MRW web with two W’s, uh, I’m MRW web.com. I’m M R W web on GitHub and Twitter and in the WordPress Slack and Post Status Slack. All these other places. I have a highly Googleable namee. If you want to come find me, I would love to hear from you I’m. I am not that hard to find.
[00:50:23] Nathan Wrigley: Well, Mark, thank you very much for being on the podcast today. I really appreciate.
[00:50:28] Mark Root-Wiley: Thanks so much for having me. This was a blast Nathan. Great, great questions. I got to say.
Although as a WooCommerce builder, you likely don’t sell fish, but here is a story to get you thinking creatively about follow-up emails.
>> The post dev_life snippet: Timing the Perfect Follow-up Customer Email appeared first on Do the Woo - a WooCommerce Builder Community .
WPTavern: WordPress 6.0 “Arturo” Adds More Templates and Patterns, Style Switching, and Block Locking UI
Check out the official release video for a quick overview of some of the most important changes.
This release introduces sweeping improvements to the block editor and its utilities and design tools. Most notably, users can now select text across multiple blocks, manipulating the highlighted portion as a group while keeping the rest of the content blocks in tact.image credit: Gutenberg 13.0 Release Post
The List View has been updated to offer a more intuitive display that helps with navigating blocks on a page. Select multiple blocks using keyboard shortcuts, make changes, and drag-and-drop inside the list. List View is closed by default but will expand to the current selection when a block is selected.image credit: wordPress 6.0 About Page
WordPress 6.0 also introduces a new interface for locking blocks, which allows useres to prevent blocks from being moved or removed. It is useful for preventing accidental edits but also for theme developers who want to prevent users from removing blocks inside templates, preserving more complex layouts.image credit: WordPress 6.0 About Page
Other block editor improvements include the following:
- New Blocks: Avatar, Post Author Biography, Read More, Comments Query Loop, and Stack block
- Type two open brackets [[ to quickly access the link menu
- Improved support for preserving unrecognized content in the editor
- Preserve existing styles transforming blocks from one kind to another—from a Paragraph block to a Code block, for instance
- New block style transformation options: Tag Cloud > Categories, Calendar > Archives, Paragraph > Code, and Group > Row
- Create customized buttons and any new buttons will retain the style customizations automatically
- New drop-down based color picker UI
- Make tag clouds and social icons more appealing with updated settings and controls, and a new outline style for the tag cloud
- Instant block style previews
- Featured images now available in Cover block
- New border controls for more precise control when setting borders
- Transparency levels for colors offers more creative control
WordPress 6.0 also introduces a gaggle of new layout controls for page building. Users can now control gaps, margins, typography, and more on multiple blocks inside a Group block. Creating layouts is easier with the ability to position groups of blocks by quickly switching between stack, row, and group variations. The Gallery block is now more flexible with gap support for custom spacing.
Biggest stuff is in the editor itself, and there are many minor but big updates facing the end-user like how:
– we no longer have to rely on group block for block spacings
– we now have row block for horizontal stuff
– visual aids getting better and better.
Patterns are now available in more places and better integrated with the Site Editor. Gutenberg 12.7 brought major improvements to the patterns experience by making them easier to discover. The block inserter has been updated to display patterns, as opposed to blocks, when users are editing a template in the post or site editor. It also favors showing patterns when the inserter is at the root level or the content being inserted is between other blocks. WordPress will now show existing template parts, as well as block patterns in the template creation process.image credit: WordPress 6.0 About Page
Theme authors can now register patterns from the official Pattern Directory using theme.json, so that users have quick access to patterns the author has highlighted.
WordPress 6.0 introduces five new template options for full-site editing: author, date, categories, tag, and taxonomy.
One of the most anticipated features of this release is the Style Switcher. It allows userse to apply quick style changes within the same theme, and includes the ability to further edit the font weight, style options, and color palette.
Theme authors can create multiple different theme.json style variations and place them into their themes’ /styles folder. Users will then see the styles under the Styles menu in the top toolbar of the site editor.
WordPress 6.0 is the product of collaboration from more than 500 contributors in 58+ countries. It introduces more than 1,000 updates and bug fixes, including many that make the platform more performant and accessible.
Say hello to “Arturo” and WordPress 6.0, inspired by Grammy-winning jazz musician, Arturo O’Farrill. Known for his influence on contemporary Latin jazz, Arturo has pressed more than 15 albums spanning a body of work across five decades.
Take some time to explore WordPress 6.0, built to help you unlock your creative aspirations and make your site-building experience more intuitive. And check out some of Arturo’s inspirational sounds that span Afro Cuban jazz, contemporary Latin jazz, and so much more.
Site owners and administrators should upgrade to take full advantage of the many stability, performance, and usability enhancements today. WordPress content creators will enjoy a suite of new features geared toward improving the writing and designing experiences.
Expanding Gutenberg into a full site editing experience in WordPress means that all of the problems the community had to address were complex and far-reaching. WordPress 6.0 is an example of the community’s commitment to tackling these tough challenges together. With thoughtful updates to the writing experience, building better block functionality, and adding a new intuitive style switcher, I’m really proud of the work that’s been done in this release to make a great site editing experience.Josepha Haden Chomphosy, Executive Director Download WordPress 6.0 What’s Inside Enhanced Writing Experience
Writing improvements abound, whether you’re writing a brand new post or adding elements to an existing page. Explore more ways to streamline your content creation process, including:
- Select text across multiple blocks for easier copying and pasting.
- Type two open brackets `[[` to quickly access a list of recent posts and pages.
- Keep existing styles when you transform some blocks from one kind to another—from a Paragraph block to a Code block, for instance.
- Create customized buttons and any new buttons you make will retain the style customizations automatically.
- Make tag clouds and social icons even more appealing with updated settings and controls, and a new outline style for the tag cloud.
Block themes now include the option to contain multiple style variations. This expands the new Style system even further and enables shortcuts to switch the look and feel of your site all within a single theme. In block themes that support this feature, you can change both the available settings, like the font-weight, and the style options, like the default color palette. Change the look and feel of your site with just a few clicks.More Template Choices
WordPress 6.0 includes five new template options for block themes: author, date, categories, tag, and taxonomy. These additional templates provide greater flexibility for content creators. Tailor each with the tools you already know or with the following new options in this release:
- Featured images can be used in the cover block.
- New featured image sizing controls make it easier to get the results you want.
- While editing a template, at the root, or between blocks, the quick inserter shows you patterns and template parts to help you work faster and discover new layout options.
- The query block supports filtering on multiple authors, support for custom taxonomies, and support for customizing what is shown when there are no results.
Patterns will now appear when you need them in even more places, like in the quick inserter or when creating a new header or footer. If you’re a block theme author, you can even register patterns from the Pattern Directory using `theme.json`, enabling you to prioritize specific patterns that are most helpful to your theme’s users.Additional Design Tools
Design tools grow more powerful and intuitive with each release. Some highlights for 6.0 include:
- A new color panel design saves space, but still shows your options at a glance.
- New border controls offer a simpler way to set your border exactly as you like it.
- Transparency levels for your colors allow for even more creative color options.
- Control gaps, margins, typography, and more on a collection of blocks, all at once, in the Group block.
- Switch between stack, row, and group variations to position groups of blocks with more layout flexibility.
- Use the gap support functionality in the Gallery block to create different looks – from adding spacing between all images, to removing spacing altogether.
New keyboard shortcuts enable you to select multiple blocks from the list view, modify them in bulk, and drag and drop them within the list. List View can be opened and closed easily; it comes collapsed by default and it automatically expands to the current selection whenever you select a block.Block Locking Controls
Now you can lock your blocks. Choose to disable the option to move a block, remove a block, or both. This simplifies project handover, allowing your clients to unleash their creativity without worrying about accidentally breaking their site in the process.Improved Performance in WordPress 6.0
This release includes several updates focused on improving the performance of WordPress. These enhancements cover a range of performance areas including improving the page and post-load speed, reducing the execution time of various query types, caching, navigation menus, and much more. The performance team working group is an important focus area of the core development team. For more information on this group’s work, please follow their work on Making WordPress with the #performance hashtag.Enhancing WordPress 6.0 Accessibility
Accessibility is an integral part of the WordPress mission of fostering an inclusive community and supporting users of all types around the world. With this in mind, WordPress 6.0 includes more than 50 updates specifically focused on enhancing the accessibility of the platform. You can read about these updates and learn more about the accessibility initiatives that are ongoing.Learn More About WordPress 6.0
See WordPress 6.0 in action! Watch a brief overview video highlighting some of the major features debuting in WordPress 6.0.
Developers can explore the WordPress 6.0 Field Guide. It is overflowing with detailed developer notes to help you build with and extend WordPress.
Read the WordPress 6.0 Release Notes for more information on the included enhancements and issues fixed, installation information, developer notes and resources, release contributors, and the list of file changes in this release.The WordPress 6.0 Release Squad
The group listed below tirelessly supported the release, from conception to ship date, and beyond:
- Release Lead: Matt Mullenweg
- Release Coordinators: Héctor Prieto and Anne McCarthy
- Core Tech Lead: Peter Wilson
- Editor Tech Leads: Adam Zieliński and Greg Ziółkowski
- Core Triage Leads: Ahmed Chaion and Colin Stewart
- Editor Triage Lead: Nick Diego
- Documentation Leads: Birgit Pauli-Haack, Milana Cap, and Abha Thakor
- Marketing & Communications Lead: Dan Soschin
- Test Leads: Piotrek Boniu and Brian Alexander
- Design Lead: Channing Ritter
WordPress 6.0 would not have been possible without the contributions of more than 500 people in at least 58 countries. Their asynchronous coordination to deliver hundreds of enhancements and fixes into a stable release is a testament to the power and capability of the WordPress community.
Aaron Jorbin · Aaron Robertshaw · Abdullah Ramzan · Abha Thakor · Adam Silverstein · Adam Zielinski · adi64bit · Adil Ali · agepcom · Ahmed Chaion · Aki Hamano · Akira Tachibana · Alain Schlesser · Alan Jacob Mathew · alansyue · Albert Juhé Lluveras · albertomake · Alefe Souza · Aleksandar Kostov · Alex Concha · Alex Lende · Alex Mills · Alex Stine · aliakseyenkaihar · Alkesh Miyani · Alok Shrestha · Amanda Giles · Andrea Fercia · Andrei Draganescu · Andrei Surdu · Andrew Dixon · Andrew Nacin · Andrew Ozz · Andrew Serong · Andrey "Rarst" Savchenko · André · Andy Fragen · Angelika Reisiger · Anh Tran · Ankit K Gupta · Anne McCarthy · Anoop Ranawat · Anthony Burchell · Anthony Ledesma · Anton Vlasenko · antonrinas · Antony Booker · arcangelini · Ari Stathopoulos · Arne · Arpit G Shah · artdecotech · ArteMa · Arthur Chu · Asaquzzaman mishu · atomicjack · Aurélien Joahny · Aurooba Ahmed · Barry · Barry Ceelen · Bartosz Gadomski · Beda · Ben Dwyer · Benachi · Bernie Reiter · BettyJJ · Bhrugesh Bavishi · binarymoon · Birgir Erlendsson (birgire) · Birgit Pauli-Haack · Blair Williams · BlogAid · Boone Gorges · Brandon DuRette · Brandon Kraft · Brian Alexander · bronsonquick · Brooke Kaminski · Brooke. · Bruno Ribaric · caraya · Carlos Bravo · Carlos Garcia · Carolina Nymark · cbigler · Chad Chadbourne · Channing Ritter · charleyparkerdesign · charlyox · Chintan hingrajiya · Chloe Bringmann · Chouby · Chris Lubkert · Chris Van Patten · chriscct7 · clonemykey · Colin Stewart · conner_bw · Cory Hughart · Courtney Robertson · Crisoforo Gaspar · Dan Soschin · Daniel Bachhuber · Daniel Richards · danieldudzic · darerodz · Dat Hoang · Dave Smith · David Baumwald · David Biňovec · David Calhoun · David Gwyer · David Herrera · David Shanske · Deb Nath Utpol · Delowar Hossain · denishua · Dennis Claassen · Dennis Snell · Dhanendran · Dharmesh Patel · dhusakovic · Dilip Bheda · Dion Hulse · Dominik Schilling · donmhico · drago239 · Drew Jaynes · dromero20 · Eddy · ehtis · Eliezer Peña · Ella van Durpe · Emmanuel Hesry · Enrico Battocchi · eric3d · Erik Betshammar · espiat · Estela Rueda · etaproducto · EverPress · Fabian Kägy · Fabio Blanco · Faison · Felipe Elia · Felix Arntz · Femy Praseeth · Florian Brinkmann · Florian TIAR · FolioVision · Francesca Marano · Francisco Vera · frankei · furi3r · gadhiyaravi · Garrett Hyder · Garth Mortensen · Gary Jones · Gary Pendergast · genosseeinhorn · George Hotelling · George Mamadashvili · George Stephanis · Gerardo Pacheco · Glen Davies · Grégory Viguier · Grant M. Kinney · Greg Ziółkowski · gregoiresailland · Guido Scialfa · gumacahin · gvgvgvijayan · Hareesh · Hasanuzzaman · Hasnain Ashfaq · Hauwa Abashiya · Haz · Helen Hou-Sandi · HelgaTheViking · Henry Wright · Hilay Trivedi · Hitendra Chopda · HristoK · Hugh Lashbrooke · Héctor Prieto · Ian Belanger · Ian Dunn · ianatkins · ianmjones · ImanGM · imokol · Isabel Brison · ishitaka · itsamoreh · Iulia Cazan · Ivan Lutrov · jadpm · Jake Spurlock · jakeparis · James Koster · Jamie VanRaalte · Jan Weiss · janh2 · Jarret · Jason Johnston · Jason LeMahieu (MadtownLems) · Javier Arce · Javier Prieto · Jay Trees · jazbek · Jean-Baptiste Audras · Jeff Bowen · Jeff Matson · Jeff Ong · Jeff Paul · Jenny Dupuy · Jenny Wong · Jeremy Felt · Jeremy Herve · Jeremy Yip · Jez Emery · jhned · jhnstn · jigar bhanushali · jiteshdhamaniya · Joe Dolson · Joe McGill · Joen Asmussen · Johannes Kinast · John Blackbourn · John James Jacoby · John Regan · John Watkins · Jon Brown · Jonathan Champ · Jonathan Desrosiers · Jonny Harris · Jono Alderson · Jorge · Jorge Costa · José Arcos · Josepha · Josepha Dambul · Joshua Fredrickson · Joy · jrivett · jsnajdr · juanlopez4691 · JuanMa Garrido · Juliette Reinders Folmer · Junaid Ahmed · Justin Ahinon · Justin Busa · Justin Tucker · KafleG · Kai Hao · Kajal Gohel · kapacity · Kapil Paul · karolinakulinska · Kaspars · kbatdorf · Kelly Choyce-Dwan · Kemory Grubb · Kerry Liu · Kev Provance · Kharis Sulistiyono · Kirtan Gajjar · Kjell Reigstad · KMix · Knut Sparhell · Konrad.K · Konstantin Obenland · kpegoraro · kubiq · Kukhyeon Heo · Lauren · Lena Morita · lenasterg · leskam · Lew Ayotte · linux4me2 · Lisa Schuyler · lkraav · Louis · Lovekesh Kumar · Lucas Karpiuk · Luis Felipe Zaguini · luisherranz · Luke Cavanagh · Lukman Nakib · M. van Dam · macbookandrew · Maciej · Maggie Cabrera · maguijo · Mahbub Hasan Imon · malthert · manfcarlo · Marcelo de Moraes Serpa · Marco Ciampini · Marcus Kazmierczak · Marin Atanasov · Marius L. J. · Mark Jaquith · Markus Kosmal · marv2 · Mary Baum · Mat Lipe · Mathieu · Matias Ventura · matiasbenedetto · Matt Chowning · Matt Martz · Matt Mullenweg · Matt Royal · Matt Stoney · Matt Wiebe · maur · Mauriac AZOUA · Max Kellermann · Mehedi Foysal · Meher Bala · mgol · Michael Burridge · Michal Czaplinski · Miguel Fonseca · Mike Auteri · Mike Schroder · miken32 · Milan Dinić · Milana Cap · Minal Diwan · Mirco Babini · MMDeveloper · Mohadese Ghasemi · Mohammad Ahsan Habib · Mohammad Rockeybul Alam · MohammadJafar Khajeh · Morten Rand-Hendriksen · moushik · mqudsi · Muhammad Faizan Haidar · Mukesh Panchal · Mustaque Ahmed · Nabil · Nagesh Pai - a11n · Nalini Thakor · Nathan · Nayana Maradia · Nicholas Garofalo · Nick Ciske · Nick Diego · Nicolas Juen · nidhidhandhukiya · Nik Tsekouras · Nil · nmschaller · Noah Allen · oakesjosh · oguzkocer · Oliver Campion · Omar Alshaker · opr18 · Otshelnik-Fm · overclokk · ovidiul · Paal Joachim Romdahl · Pablo Honey · Paolo L. Scala · Paragon Initiative Enterprises · Pascal Birchler · Paul Bearne · Paul Biron · Paul Ryan · Paul Von Schrottky · paulkevan · Pavan Patil · Pavlo · pbking · Pedro Mendonça · Petar Ratković · Peter Smits · Peter Westwood · Peter Wilson · petrosparaskevopoulos · Petter Walbø Johnsgård · pgpagely · Phil Johnston · Pieterjan Deneys · pikamander2 · Piotrek Boniu · Pooja Derashri · Pooja N Muchandikar · Pravin Parmar · Presskopp · presstoke · Priyank · pypwalters · r-a-y · Rachel Baker · Rafi Ahmed · Ramanan · Ramon Ahnert · Ramon James · Ramona · Ravi Vaghela · ravipatel · Razvan Onofrei · Rehan Ali · Remy Perona · Riad Benguella · Rian Rietveld · Rich Tabor · Richard B. Kreckel · ricomoorman · Rob Scott · Robert Anderson · Rolf Allard van Hagen · Rolf Siebers · Rostislav Wolný · Rufus87 · Ryan Boren · Ryan Fredlund · Ryan McCue · Ryan Welcher · Sébastien SERRE · Sören Wrede · Sabbir Ahmed · Sabbir Hasan · Sami Falah · Sanjeev Aryal · santosguillamot · Sarah Norris · Sarah Snow · sarayourfriend · Sathiyamoorthy V · Sayedul Sayem · sbossarte · sclayf1 · Scott Buscemi · Scott Reilly · Scott Taylor · Segayuu · Sergey Biryukov · sheepysheep60 · Shital Marakana · Shreyas Ikhar · siddharth · Siddharth Thevaril · silb3r · Simon Blackbourn · Simon Prosser · simonhammes · Siobhan · Smit Rathod · snapfractalpop · socalchristina · Spencer Cameron-Morin · stacimc · stefanfisk · Stefano Lissa · Stefano Minoia · Stefanos Togoulidis · Stephen Bernhardt · Stephen Edgar · Stephen Harris · Steve Grunwell · Subrata Sarkar · Sumit Singh · Sumit Singh · Sumon Sarker · SunilPrajapati · sunyatasattva · Sven Wagener · Sybre Waaijer · Synchro · Takashi Kitajima · Tammie Lister · tharsheblows · Theo H · Thimal Wickremage · Thomas McMahon · Thomas Patrick Levy · Thomas Pike · Till Krüss · Tim Blankenship · Tim Nolte · Timothy Jacobs · tobifjellner (Tor-Bjorn Fjellner) · Tom · Tomasz Tunik · Tomek · Tomoki Shimomura · Tony Tahmouch · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · Tracy · trex005 · tszming · tumas2 · twstokes · Tynan Beatty · tzipporahwitty · Uday Kokitkar · ugljanin · Ugyen Dorji · Ulrich · Utkarsh · valer1e · versusbassz · Vicente Canales · Vishal Kumar · vlad.olaru · Volodymyr Kolesnykov · vortfu · WebMan Design | Oliver Juhas · Wendy Chen · Wes Theron · Weston Ruter · whoisnegrello · Will Skora · wpmakenorg · wpsoul · WraithKenny · wslyhbb · Xidorn Quan · Yui · Yunus Ertuğrul · Zebulan Stanphill · znuff · Česlav Przywara
By release day, 76 locales had translated 90-percent or more of WordPress 6.0 into their language. Community translators continue after a release ensuring more translations are on their way. Thank you to everyone who helps to make WordPress available in 205 languages.
Many thanks to all of the community volunteers who contribute to the support forums by answering questions from WordPress users around the world.
If contributing to WordPress appeals to you, it’s easy to learn more and get involved. Discover the different teams that come together to Make WordPress and explore the product roadmap on the core development blog.The WordPress Mission & You
WordPress is software designed for everyone, emphasizing accessibility, performance, security, and ease of use. The project believes great software should work with minimum setup, so you can focus on sharing your story, product, or services freely. The basic WordPress software is simple and predictable so you can easily get started. It also offers powerful features for growth and success.
WordPress believes in democratizing publishing and the freedoms that come with open source. Supporting this idea is a large community of people collaborating on and contributing to this project. The WordPress community is welcoming and inclusive. Our contributors’ passion drives the success of WordPress which, in turn, helps you reach your goals.
Learn more about WordPress and how you can join our community to help shape the future of the world’s most popular website platform.A Release Haiku
Six-point-oh is here
Time to download and upgrade
Let’s pause, celebrate
Tips from Daisy Olsen, Dave Lockie, Devin Walker, Greg Ziolkowski, Jonathan Wold, Milana Cap, Nev Harris, Paul Bearne, Ryan Welcher, Vassilena Valchanova and Vito Peleg