Posts in category: WordPress

WordPress belongs to all of us, but really we’re taking care of it for the next generation.”

Matt Mullenweg

A small audience of WordPress contributors, developers, and extenders gathered on December 15 for the annual State of the Word keynote from WordPress co-founder Matt Mullenweg. Those who could not join in person joined via livestream or one of 33 watch parties held across 11 countries, with more than 500 RSVPs.

Executive Director, Josepha Haden Chomphosy, introduced the event with a reminder of why so many of those gathered choose WordPress—the Four Freedoms of open source. As Haden Chomphosy noted, open source is an idea that can change our generation, and WordPress is one of the most consistent and impactful stewards of those freedoms.

As with past State of the Word events, Matt reflected on the year’s accomplishments, learnings, and aspirations as the project moves into 2023. From Gutenberg concluding its second phase of site editing in preparation for phase three—Collaborative Workflows, to the reactivation of meetups and global WordCamps, to the introduction of a new theme and plugin taxonomy, to musings on the potential of machine learning, WordPress enters its 20th year continuing to define bleeding edge technology in thanks to the ecosystem’s vibrant community. 

The one-hour multimedia presentation was followed by an interactive question and answer session where Matt fielded questions from the livestream and studio audience. All questions will be responded to in a follow-up post on Make.WordPress.org/project. 

Discover everything that was covered by watching the official event recording and join the ongoing #StateOfTheWord conversation on Tumblr, Instagram, Facebook, Linkedin, and Twitter. For another way to get involved, consider sharing your experience with WordPress in the 2022 WordPress Community Survey.

Referenced Resources 

Special thanks to @laurlittle and @eidolonnight for review and collaboration.

Each year, members of the WordPress community (users, site builders, extenders, and contributors) provide valuable feedback through an annual survey. Key takeaways and trends that emerge from this survey often find their way into the annual State of the Word address, are shared in the public project blogs, and can influence the direction and strategy for the WordPress project.

Simply put: this survey helps those who build WordPress understand more about how the software is used, and by whom. The survey also helps leaders in the WordPress open source project learn more about our contributors’ experiences.  

To ensure that your WordPress experience is represented in the 2022 survey results, take the 2022 annual survey now.

You may also take the survey in French, German, Italian, Japanese, Russian, or Spanish, thanks to the efforts of WordPress polyglot contributors. These are the most frequently installed languages based on the number of WordPress downloads. 

The survey will be open through the end of 2022, and then WordPress plans to publish the results sometime in 2023. This year, the survey questions have been refreshed for more effortless survey flow, completion, and analysis. Some questions have been removed, while a few new ones are now present, reflecting the present and future of WordPress. If you’re looking for the analysis of the 2021 survey results, those will also be shared in early 2023.

Spread the word

Help spread the word about the survey by sharing it with your network, through Slack, or within your social media accounts. The more people who complete the survey and share their experience with WordPress, the more the project as a whole will benefit in the future.

Security and privacy

Data security and privacy are paramount to the WordPress project and community. With this in mind, all data will be anonymized: no email addresses nor IP addresses will be associated with published results. To learn more about WordPress.org’s privacy practices, view the privacy policy.

Thank you

Thank you to the following WordPress contributors for assisting with the annual survey project, including question creation, strategy, survey build-out, and translation:

dansoschin, _dorsvenabili, angelasjin, arkangel, audrasjb, atachibana, bjmcsherry, chanthaboune, eidolonnight, fernandot, fierevere, fxbenard, jdy68, jpantani, laurlittle, nao, nielslange, peiraisotta, piermario, rmartinezduque, santanainniss.

This month we feature Huanyi (Eric) Chuang, a front end developer from Taiwan, who helps connect local groups to WordPress and the worldwide open source community. He is part of the team helping to make the first WordCamp Asia a success in 2023.

The People of WordPress series shares some of the inspiring stories of how people’s lives can change for the better through WordPress and its global network of contributors.

Discovering WordPress and the benefit of child themes

Huanyi’s first footsteps in WordPress began in 2017 when he worked for a firm that built blogs and developed ad content for clients.

After building a few sites using the platform, he discovered child themes and through them opened up a world of possibilities for his clients. To this day, he uses child themes to deliver truly custom designs and functionality for clients.

Later in his career, Huanyi moved into digital marketing, integrating sites with massive ad platforms like Google and Facebook. This led him to learn to work with tracking code and JavaScript. He also began his learning journey in HTML, CSS, and PHP, to be able to improve his development skills and customize child themes.

Meetups bring together software users to learn together

When Huanyi had a problem with a client’s site, he looked to WordPress meetups near where he lived in Taipei to help find the solutions.

“When I encountered an issue with the custom archive pages, a local meetup announcement showed up on my WordPress dashboard.”

Huanyi Chuang

At the meetup, he met more experienced WordPress users and developers there, who answered his questions and helped him learn.

“When I encountered an issue with the custom archive pages, a local meetup announcement showed up on my WordPress dashboard. That was my original connection with the local community,” Huanyi said.

The WordPress community gave Huanyi a chance to connect with people, feed his curiosity about the software, and join a circle of people he could share this interest.

At first, he thought meetups were an opportunity to source new clients, and he took his business cards to every event. However, he soon found that these events offered him the opportunity to make friends and share knowledge.

From then on, Huanyi started focusing more on what he could give to these events and networks, making new friends, and listening to people. This led him to share as a meetup speaker his own commercial website management experience.

The road to WordCamp

It was going to his first meetup and then getting involved with WordCamps that changed Huanyi’s whole relationship with WordPress.

In 2018, he took the step to help as an organizer, having joined the Taoyuan Meetup in Taiwan. He played several parts across the organizing team, and the welcoming feeling he got in every situation encouraged him to get more involved.

He recalls meeting new friends from different fields and other countries, which gave him a great sense of achievement and strengthened his passion for participating in the community.

When the team started this meetup, numbers were much lower than in the group in the city of Taipei, but they were not disheartened and gradually grew the local WordPress community.

They created a pattern of ‘multiple organizers,’ which spread the workload and grew friendships. 

“Being connected to and from meetups is the most valuable part of the community. Having these friends makes me gather more information. We share information and benefit from others’ information, and thus we gain more trust in each other. With such credibility, we share more deeply and build deeper relations.”

Huanyi Chuang

Before the pandemic, the meetup met every month and grew to become the second largest meetup in Taiwan. Huanyi also contributed to the WordPress community as an organizer of WordCamp Taipei 2018 in the speaker team and lead organizer of WordCamp Taiwan 2021.

So why should you join the community?

According to Huanyi, you will always have something to take home with you. It might be new information or experiences. It might be plugins or theme ideas. But most of all, it is the chance to meet fascinating people and make new friends.

Huanyi’s message to other contributors:
“Keep participating, and you will find more you can achieve than you expect.”

He added that long-term participation will ‘let you feel the humanity behind the project’.

Localize: the road ahead for WordPress

Huanyi believes WordPress has the power to break down the barriers between designers, project managers, developers, marketers, writers, and publishers. In Taiwan, he said WordPress is ‘a common protocol’ that lets people from all of these disciplines work and communicate together more easily than they ever have before.

That is why he works on and encourages others to localize plugins today. He believes localization of the software is the foundation for the extension of the WordPress community as it enables people to ‘Flex their Freedom’ in a language they speak!

He has helped to organize online events around previous WordPress Translation Day events.

Huanyi said: “I think it’s important to localize WordPress because its very concept of ‘open source’ means that people can access it freely. In another way, free from the monopoly of knowledge and speech. To achieve it, it’s important that people can access it with their own language.

“Localization is the foundation of the extension of WordPress community because it helps people using different languages to access the project and lowers the hurdle to understand how things work.”

Share the stories

Help share these stories of open source contributors and continue to grow the community. Meet more WordPressers in the People of WordPress series.

Contributors

Thank you to @no249a002 for sharing his adventures in WordPress.

Thank you to Abha Thakor (@webcommsat), Mary Baum (@marybaum), Meher Bala (@meher), Chloe Bringmann (@cbringmann), Surendra Thakor (@sthakor), Adeeb Malik (@adeebmalik) for research, interviews, and contributing to this feature article.

The People of WordPress series thanks Josepha Haden (@chanthaboune) and Topher DeRosia (@topher1kenobe) for their support.

This People of WordPress feature is inspired by an essay originally published on HeroPress.com, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories might otherwise go unheard. #HeroPress

In the forty-fourth episode of the WordPress Briefing, our host Josepha Haden Chomphosy highlights the role of major and minor releases in the WordPress open source project.

Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.

Credits

Editor: Dustin Hartzler
Logo: Javier Arce
Production: Santana Inniss
Song: Fearless First by Kevin MacLeod

References

Twelfth Man
State of the Word

Transcript

[Josepha Haden Chomphosy 00:00:00] 

Hello everyone! And welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and 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:27] 

At the top of November, a new major release for WordPress shipped. That was WordPress 6.1. I know I talked about it basically nonstop. Then two weeks later, there was a new minor release for WordPress. It was WordPress 6.1.1, which I did not talk about at all. Way back in episode four of this podcast, I dug into the overall release cycle and what someone could expect from a high-level logistics aspect.

[Josepha Haden Chomphosy 00:01:05] 

And today we’re gonna take a quick look at minor releases in particular. Just as a general heads up, I always want to lean into sports metaphors when I’m talking about releases, and I think it’s because of the words major and minor. And so, I’ve done my level best to not include that in any of my explanations today.

But I do have one, I do have one that’s a sports thing. So just if you don’t like sports, know that it’s just one little bit and we’ll try to be carefully quick around it together. All right, so minor releases. You may have noticed that I don’t mention minor releases nearly as often as I mention major releases. And yet, most of the time, when we have a major release of WordPress, there’s a minor release that gets started almost immediately after.

So first major versus minor. Major releases in WordPress happen roughly three times a year, give or take a release. Inside a major release, you will find that we include features, so– brand new abilities, enhancements, which you can generally call improvements to existing abilities, and also any bug fix that we can find, big or small, we’ll take ’em all.

[Josepha Haden Chomphosy 00:02:16] 

So minor releases in WordPress happen about four or five times a year on average. Minor releases include patches for issues introduced in the major release and any bug fix that doesn’t add or change functionality. 

If you’re with me so far, you probably have noted that there’s basically always at least one minor release per major release. And you might have also noted that I said minors include patches for issues we introduced in a major.

Now, if I were hearing this with fresh ears, the first thing I would wonder is, okay, so if you start working on the minor right after you release the major to deal with issues you know you introduced in the major– why just not ship the major while there are bugs in it? Great question. I’m glad you asked. So there are a few things worth knowing here.

[Josepha Haden Chomphosy 00:03:09] 

Firstly, there is this concept of “ship and iterate,” which is present in both agile and open source. The idea is that we ship software as soon as we have confidence that what is in the release is non-breaking and represents our best guests at a better experience for our users.

Once that is out there, we use feedback on the initial release to quickly iterate and ship another release. That way, we don’t hold back any good features. And since we already planned the immediate minor, any major issues that show up can be fixed in as little as two weeks. Secondly, there is the concept that with many eyes, all bugs are shallow, which is primarily present in open source.

The idea here is that with enough people looking at a problem, that problem doesn’t stand a chance. So when a release is shipped in a workable state but with interactions that could use some refinement, the fastest way to find those refinements is to take it to the community of WordPress users and developers and invite them to co-create this CMS with us.

[Josepha Haden Chomphosy 00:04:10]

Which touches on my final thought. The concept of the user as co-creator.

If we think about the development and evolution of our software as a team effort, then we can think of the people who use our software as what’s called the “Twelfth Man” That’s in quotes, and I will, I’ll leave a link to that in the show notes as well. 

In sports, this refers to the fans. And if you’ve ever been to a live sporting event or played in any, you will know that the cheering and jeering from fans turns into this distinct motivating entity all its own. As a whole team or individual member, you know what you have to do. You know what you need to do in a game, but there’s something about that chaotic, loud roar of feedback that just brings life to what you’re doing, and that’s how I see our community of users.

[Josepha Haden Chomphosy 00:05:02]

So at the end of the day, the answer to the question of ‘why so many releases’ and the follow-up question of ‘why tolerate stable imperfection’ is largely the same. To get features into the hands of our users quickly so that we can always be breathing life into this CMS we care so much about.

I hope that answers your questions about our release cadence, and if you didn’t come into this podcast having any questions about release cadences at all, I hope this new information brings a little extra light to the complexity of working in open source. 

[Josepha Haden Chomphosy 00:05:32] 

That brings us now to our small list of big things.

Big thing number one is that the State of the Word has been announced and is scheduled for December 15th. It’s a little earlier in the day than in past iterations, so I hope we get a new crew of listeners tuning in at the same time. I’ll leave a link to that in the show notes, or you can pop over to wordpress.org/news to see the announcement for yourself.

[Josepha Haden Chomphosy 00:06:00] 

Big thing number two is that team rep nominations are open on most teams right now. So if organization and people wrangling are high on your list of ways you can give back to WordPress, head on over to the team you contribute to and see how you raise your hand for that. 

Then big thing number three is that big-picture goals, hopes, and timelines are being gathered, and I will ship those shortly after the start of the new year.

It will give us all an idea of where we want to focus our attention to ensure that WordPress continues to grow toward the future. You can keep an eye out for that on make.wordpress.org/project. 

And that, my friends, is your small list of big things. Thanks 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.

With the end of the year fast approaching, the WordPress project has not slowed down. Read on to learn more about the latest major release, WordPress 6.1, and the State of the Word 2022 live event, among other exciting news. It’s time to catch up on all things WordPress!

Say hello to WordPress 6.1 “Misha”

The third and last major release of 2022, WordPress 6.1 “Misha,” shipped on November 1, 2022. Named after jazz pianist Mikhail “Misha” Alperin, this release comes packed with many improvements that refine the site-building experience introduced earlier this year in WordPress 5.9 and 6.0, as well as accessibility and performance upgrades.

WordPress 6.1 is also bundled with a new default block theme, Twenty Twenty-Three (TT3), that features 10 style variations designed by WordPress community members. These intentionally unique designs ensure that you can change the visual details of your site with ease—and within a single theme.

Learn more about what’s in 6.1:

Following WordPress 6.1 “Misha”, a 6.1.1 maintenance release landed on November 15, 2022. This minor release includes about 50 bug fixes.

State of the Word 2022 is coming on December 15

State of the Word 2022, the annual keynote address delivered by the WordPress project’s co-founder, Matt Mullenweg, will be held on December 15, 2022. The event will take place in person in New York City and live-streamed via various WordPress.org social media platforms.

You can also host or join a State of the Word watch party to enjoy the event with your WordPress friends.

What’s new in Gutenberg

Two new versions of Gutenberg have shipped in the last month:

• Gutenberg 14.4 was released on October 26, 2022, with support for a distraction-free mode that allows a more focused writing experience. Other notable highlights include a redesigned pattern inserter, content locking to the Navigation block, and improvements to fluid typography.
• Gutenberg 14.5 sets the groundwork for future releases with code quality improvements and bug fixes. This version introduces a new “Document Overview” panel for easier access to the list view and document information, expands margin and padding support, and improves spacing visualizers. It was released on November 9, 2022.

Team updates: Documentation Contributor Day, WordPress.org redesign updates, and more

Feedback & testing requests

Event updates & WordCamps

Have a story that we should include in the next issue of The Month in WordPress? Fill out this quick form to let us know.

The following folks contributed to this edition of The Month in WordPress: @rmartinezduque, @webcommsat, @santanainniss, @dansoschin, @eidolonnight.

Hello, WordPress! 

Mark your calendars; it’s almost time for State of the Word 2022!

State of the Word is the annual keynote address delivered by the WordPress project’s co-founder, Matt Mullenweg. Every year, the event shares reflections on the project’s progress and the future of open source. Expect this and more in this year’s edition.

This year’s event will take place in person in New York City and live-streamed via various WordPress.org social media platforms. 

Join Matt as he provides a retrospective of 2022, the latest WordPress releases, Site Editor advancements, and a return to in-person events around the globe, among other topics.

What: State of the Word 2022

When: December 15, 2022, 1–2:30 P.M. EST (18–19:30 UTC)

How: If you’re watching from the comfort of your home or local watch party, the live stream will be embedded in this post and available through the WordPress YouTube channel.

Would you like to join the in-person audience? Request a seat by completing this survey.

Have a question for Matt?

State of the Word will include a Q&A session. If you want to participate, you can either send your question ahead of time to ask-matt@wordcamp.org or ask during the event in the live stream chat on YouTube.

Given the volume of questions that are usually submitted, please note that it may not be possible to answer all of them in the live Q&A. A follow-up post will be published after the State of the Word to answer those not covered at the event.

First time attending State of the Word? Check out previous years’ recordings on WordPress.tv to get a sense of the event.

See you in person or online on December 15!

Join a State of the Word Watch Party near You

Can’t make it to New York? No problem, organize or join a watch party in your community in person or online. Like last year, the Community team has resources available to help! Check out this handbook page, which includes event templates, information on requesting a Zoom account, and how to get some swag.

Gather together to look back on how WordPress has grown in 2022 and what is ahead for 2023. Stay up-to-date as a group on the latest happenings in the WordPress world and collaborate together on any questions you might have for Matt!

We will be compiling a list of State of the Word watch parties in this post, which will be updated regularly as the event approaches. If you don’t see a watch party in your region listed here in the next few weeks, check this page on Meetup.com to see if your local WordPress group is organizing one.

If you are planning a watch party for State of the Word and have questions, please email support@wordcamp.org. A member of the WordPress community team will assist you in the best way possible.

WordPress 6.1.1 is now available

This minor release features 29 bug fixes in Core and 21 bug fixes for the block editor. WordPress 6.1.1 is a short-cycle maintenance release. You can review a summary of the key updates in this release by reading the RC1 announcement.

The next major release will be version 6.2 planned for 2023.

If you have sites that support automatic background updates, the update process will begin automatically.

You can download WordPress 6.1.1 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”.

For more information, check out the version 6.1.1 HelpHub documentation page.

Thank you to these WordPress contributors

The WordPress 6.1.1 release was led by @desrosj, @mamaduka, and @jeffpaul.

WordPress 6.1.1 would not have been possible without the contributions of more than 105 people. Their asynchronous coordination to deliver several enhancements and fixes into a stable release is a testament to the power and capability of the WordPress community.

10upsimon, Aaron Jorbin, Aaron Robertshaw, Adam Silverstein, Aki Hamano, alexstine, Andrei Draganescu, Andrew Ozz, Andrew Serong, Andre, Andy Fragen, Ari Stathopoulos, azurseisme, Ben Dwyer, Bernie Reiter, Bethany Chobanian Lang, Birgit Pauli-Haack, bjorn2404, Carlos Bravo, Carolina Nymark, Clayton Collie, codesdnc, Colin Stewart, Daniel Richards, David Baumwald, David Smith, David Vongries, Dilip Bheda, Dion Hulse, Dominik Schilling, Ella, Eugene M, Felix Arntz, fpodhorsky, franzaurus, gamecreature, Gary Pendergast, George Mamadashvili, gisgeo, glendaviesnz, Innovext, ironprogrammer, Isabel Brison, James, Jan Thiel, Javier Carazo, Jb Audras, jchambo, jeffpaul, joelmadigan, Joen A., John Blackbourn, John Watkins, Jonathan Desrosiers, Jonny Harris, jsh4, Juliette Reinders Folmer, K. Adam White, kacper3355, Kai Hao, Konstantin Obenland, konyoldeath, larsmqller, Lena Morita, Leo Milo, lozula, Marco Ciampini, Marin Atanasov, Marius L. J., Matt Keys, Michal Czaplinski, Miguel Axcar, Miguel Fonseca, Mukesh Panchal, mw108, Namith Jawahar, Nick Diego, Nik Tsekouras, Nithin SreeRaj, nuvoPoint, oakesjosh, ockham, Oliver Juhas, Pascal Birchler, Paul Biron, Peter Wilson, petitphp, pkolenbr, pypwalters, ramonopoly, Riad Benguella, rjasdfiii, Robert Anderson, rodricus, Ryan Kienstra, Sarah Norris, Sergey Biryukov, stentibbing, Stephen Bernhardt, Subrata Sarkar, Sybre Waaijer, Timi Wahalahti, Timothy Jacobs, Tonya Mork, Torsten Landsiedel, and vtad.

How to contribute

To get involved in WordPress core development, head over to Trac, pick a ticket, and join the conversation in the #core and #6-1-release-leads channels. Need help? Check out the Core Contributor Handbook.

In the forty-third episode of the WordPress Briefing, Josepha Haden Chomphosy explores two resources for openly licensed media in the WordPress project– Openverse and Photo Directory– and how they differ from one another!

Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.

Credits

Editor: Dustin Hartzler
Logo: Javier Arce
Production: Santana Inniss
Song: Fearless First by Kevin MacLeod

References

Photo Directory Make Page
Submit a Photo to the Photo Directory
Openverse Make Page
Openverse Call for Contributions: Block Editor Integration
Download WordPress 6.1
Docs Team Contributor Day Recap Post
Hallway Hangout Block Themes (Video)

Transcript

[Josepha Haden Chomphosy 00:00:00] 

Hello everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and 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:00] 

About 18 months ago, the Openverse project became part of the WordPress open source project, and at roughly the same time, we also welcomed the Photo Directory.

Since that time, we’ve seen growth in teams supporting both of these initiatives. But if you’re not involved in the day-to-day, it can be hard to know how those two things fit together or if they fit together at all.

[Josepha Haden Chomphosy 00:01:00] 

Today, let’s take a brief tour of those two projects and why they came to be. 

In my timeline, work on the Photo Directory started before the work on Openverse, so that’s where we’ll start.

For as long as I can remember, the WordPress community has raised the need for WordPress-first ways to have and host GPL-compatible photos for use in themes, site builds, and marketing efforts as a whole. As recently as 2016, that was still coming up as a question at various flagship events and among the career photographers that contribute their time to WordPress.

So in 2017 and 2018, as attention started to turn toward rebuilding the CMS using blocks, it dropped down the list of priority items. But it never really went away as a thing that people were hoping we could do for the project as a whole. So in 2019, it was becoming clear that having open source-first tools of all varieties for people whose businesses were built on our software would help broaden the availability of the open source freedoms we believe in.

[Josepha Haden Chomphosy 00:02:00] 

This began the work on the Photo Directory with the intention of providing a GPL-friendly, community-driven repository of images. It has since launched, and we have photos in it now. We have a whole team around it. It’s wonderful. But that is how that all kind of came to be. 

Openverse, on the other hand, was launched as CC Search in 2019 with the laudable mandate to increase the discoverability and accessibility of open access media.

Late in 2020, while work on the Photo Directory was underway, Matt shared with me that the team was looking for a new project home. When I first met with them, they shared an overview of the product, which they shorthanded as an open source search engine that searches openly licensed images. We were working on a repo of openly licensed images, so clearly, this was all written in the stars. And so you might be asking yourself at this point, great, how does it work together?

I think for most of us, the timeline there kind of covers the question of what is the difference between these two things. 

[Josepha Haden Chomphosy 00:03:00] 

But because I never know which of you will want to strike up a conversation about open source on an elevator, I’ve also got the elevator pitch version. 

Openverse is an open source search engine that searches, indexes, and aggregates copy left media from across the web using sources such as WordPress’s Photo Directory, Flickr’s CC Tagged Media, and Wikimedia, to name just a few. 

Another key difference between the Photo Directory and Openverse is that in order to contribute to the Photo Directory, now that it’s all built, that’s mostly done by submitting photos or reviewing photos. So you don’t really need to be a developer to join in. 

Openverse is not only a developer-centric contribution opportunity, but it also uses a different tech stack than WordPress as a whole. So it’s a good place for folks to go if they’re looking to broaden their horizons.

So that’s your elevator pitch of what Openverse is and how it uses the Photo Directory. 

[Josepha Haden Chomphosy 00:04:00] 

You have a couple of ways that you can get involved with these two projects. For the Photo Directory, as I mentioned at the start, you can always contribute photos, and they could always use more photo contributions.

I’ll include a link to the submission guidelines in the show notes below, and as I mentioned, it is a no-code way to give back to the WordPress project. So no code, development environments, and testing skills are required. The Photo Directory team also could always use more contributors to help with the moderating of photo submissions.

And so I’ll link to their making WordPress page in the show notes as well so that you can get started there. 

And as I mentioned before, Openverse is an aggregator, so it doesn’t host any media itself, but it is always accepting suggestions for new GPL-compatible media providers. I’ll link the area where you can leave suggestions in the show notes as well.

And if you are more code inclined, there’s an open issue for adding Openverse browsing to the block editor right now.  

[Josepha Haden Chomphosy 00:05:00] 

So I’ll link that issue in the show notes in case you thought to yourself, gosh, that sounds like my most favorite thing to do. That is where you can go. 

[Josepha Haden Chomphosy 00:05:12]

This leads us now to our small list of big things.

In case you missed it, WordPress 6.1 is now available. It launched on November 1st. Late, late, late in the day, and so it was easy to miss if you’re used to seeing it at a particular time. We were about six hours later than usual. But if you go to wordpress.org/download, you can get your own copy there.

The second thing on our small list of big things is that the Docs team had a contributor day. It was excellent. There’s a recap post up. I will include that in the show notes. 

And then the final thing is that there was a recent hallway hangout that talked about the site editor and block themes.

The video for that is also published. I will also share that in our show notes.

And that, my friends, is your small list 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.

This post was written in collaboration with Lauren Stein (@laurlittle) and Anne McCarthy @annezazu).

Twenty Twenty-Three is here, alongside WordPress 6.1! The new default theme offers a clean, blank canvas bundled with a collection of style variations.

Style variations are predefined design options that give you the opportunity to alter the appearance of your site without having to change your theme. This means that you can keep your template structure but change the visual details of your site with ease.

For a truly diverse collection, Twenty Twenty-Three’s featured style variations were submitted by members of the WordPress community, resulting in 38 submissions from 19 people in 8 different countries. From those submissions, a curated collection of ten was chosen and bundled with the new theme.

This approach to style variations ushers in the next generation of block themes, able to harness the potential of the platform’s latest design capabilities and tools directly in the Site Editor. Since style variations don’t require any code experience, you’re encouraged to tweak and/or create your own.

Thank you to everyone who contributed. 🎉

Useful links:
Download Twenty Twenty-Three
Twenty Twenty-Three Documentation
Twenty Twenty-Three Project Kick Off
Twenty Twenty-Three Selected Style Variations

Say hello to WordPress 6.1, “Misha,” inspired by the life and work of Soviet-Norwegian jazz pianist Mikhail “Misha” Alperin. Misha introduced the work of jazz ensembles in the USSR and globally. He is also celebrated as a founding member of the Moscow Art Trio.

“Misha” further refines the site-building experience. Inside WordPress 6.1 you’ll interact with enhancements that continue to make site creation more intuitive while pushing your creative boundaries further than ever. Don’t forget to enjoy some of Misha’s jazz piano as you take in all WordPress 6.1 has to offer.

The third major release of 2022 is here. Download it now! As of the time of this release, WordPress powers 43% of websites worldwide.

Site owners and administrators should upgrade today to take full advantage of the many stability, performance, and usability enhancements. Furthermore, WordPress content creators will enjoy a suite of new features geared toward improving the writing and designing experiences.

This release includes features that many in the WordPress Community have been most excited about since the start of this project. Additional enhancements and improvements to the editor give site owners more control and easier customization while offering a more cohesive experience to users. A lot of writing-focused improvements are included in the release, because if you’re giving voices to the voiceless you’ve got to focus on folks writing the copy.

Some of my favorite enhancements are the refined ability to select partial paragraphs in a block; settings to keep list view open by default; and the keyboard shortcut to add internal links expanded to all blocks.

Josepha Haden Chomphosy, Executive Director

What’s Inside

Twenty Twenty-Three:
A fresh default theme with 10 distinct style variations

After introducing foundational elements for block themes and style variations in releases 5.9 and 6.0, WordPress site builders welcome a new default theme, Twenty Twenty-Three, that is powered by 10 different styles and tagged as  “Accessibility Ready.” These intentionally unique styles ensure users can apply a different look and feel to their site with a single click—all within a single theme.

New templates for an improved creator experience

New and more refined templates now give site builders more control over the creation of their sites. In this suite of new templates, find a custom template for posts & pages in the Site Editor. Create and edit template parts like headers and footers more quickly with a new search-and-replace tool and easily view your new site.

Design tools for more consistency and control

Thoughtful upgrades to the controls for design elements and blocks make laying out and building your new site a more consistent, complete, and intuitive experience.

Manage menus with ease

New fallback options in the navigation block mean you can edit the menu that’s open; no searching needed. Plus, the controls for choosing and working on menus have their own place in the block settings. The mobile menu system also gets an upgrade with new features, including different icon options, to make the menu yours.

Cleaner layouts and document settings visualization

View and manage post and page settings with a better-organized display improving the use of features like template picker and scheduler.

One-click lock setting for all inner blocks

When locking blocks, a new toggle lets you apply your lock settings to all the blocks in a containing block like the group, cover, and column blocks.

Improved block placeholders

Various blocks have improved placeholders that reflect customization options to help you design your site and its content. For example, the Image block placeholder displays custom borders and duotone filters even before selecting an image.

Compose richer lists and quotes with inner blocks

The List and Quote blocks now support inner blocks, allowing for more flexible and rich compositions like adding headings inside your Quote blocks.

More responsive text with fluid typography

Fluid typography lets you define font sizes that adapt for easy reading in any screen size.

Add starter patterns to any post type

In WordPress 6.0, when you created a new page, you would see suggested patterns so you did not have to start with a blank page. In 6.1, you will also see the starter patterns modal when you create a new instance of any post type.

Find block themes faster

The Themes Directory has a filter for block themes, and a pattern preview gives a better sense of what the theme might look like while exploring different themes and patterns.

Keep your Site Editor settings for later

Site Editor settings are now persistent for each user. This means your settings will now be consistent across browsers and devices.

A streamlined style system

The CSS rules for margin, padding, typography, colors, and borders within the styles engine are now all in one place, reducing time spent on layout-specific tasks and helps to generate semantic class names.

Updated interface options and features

Updates include styling elements like buttons, citations, and links globally; controlling hover, active, and focus states for links using theme.json (not available to control in the interface yet); and customizing outline support for blocks and elements, among other features.

Continued evolution of layout options

The default content dimensions provided by themes can now be overridden in the Styles Sidebar, giving site builders better control over full-width content. Developers have fine-grained control over these controls.

Block Template parts in classic themes

Block template parts can now be defined in classic themes by adding the appropriate HTML files `parts` directory at the root of the theme.

Expanded support for Query Loop blocks

New filters let Query Block variations support custom queries for more powerful variations and advanced hierarchical post types filtering options.

Filters for all your styles

Leverage filters in the Styles sidebar to control settings at all four levels of your site—core, theme, user, or block, from less to more specific.

Spacing presets for faster, consistent design

Save time and avoid hard-coding values into a theme with preset margin and padding values for multiple blocks.

Content-only editing support for container blocks

Thanks to content-only editing settings, layouts can be locked within container blocks. In a content-only block, its children are invisible to the List View and entirely uneditable. So you control the layout while your writers can focus on the content. Combine it with block-locking options for even more advanced control over your blocks.

Other notes of interest

• 6.1 includes a new time-to-read feature showing content authors the approximate time-to-read values for pages, posts, and custom post types.
• The site tagline is empty by default in new sites but can be modified in General Settings.
• A new modal design offers a background blur effect, making it easier to focus on the task at hand.

Enhancing WordPress 6.1 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.1 includes nearly 60 updates specifically focused on enhancing the accessibility of the platform. Read these updates to learn more about the continual initiatives aimed at improving accessibility.

Improved Performance in WordPress 6.1

WordPress 6.1 resolves more than 25 tickets dedicated to enhancing performance with improvements for every type of site. A full breakdown can be found in the Performance Field Guide.

Learn More About WordPress 6.1

See WordPress 6.1 in action! Watch a brief overview video highlighting some of the major features debuting in WordPress 6.1.

Explore learn.wordpress.org for brief how-to videos and lots more on new features in WordPress. Or join a live interactive online workshop on a specific WordPress topic.

Developers can explore the WordPress 6.1 Field Guide, complete with detailed developer notes to help you build with and extend WordPress. Read the WordPress 6.1 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.1 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 Jonathan Desrosiers 
Core Tech Co-Leads: Mike Schroder, David Baumwald, and Jeff Paul
Editor Tech Co-Leads: Michal Czaplinski, Bernie Reiter, and Carlos Bravo
Core Triage Co-Leads: JB Audras and Ahmed Chaion
Editor Triage Co-Leads: Nick Diego and Anne McCarthy
Documentation Co-Leads: Birgit Pauli-Haack, Milana Cap, and Femy Praseeth
Marketing & Communications Co-Leads: Jonathan Pantani and Dan Soschin
Test Lead: Brian Alexander
Design Lead: Rich Tabor
Default Theme Co-Leads: Beatriz Fialho & Sarah Norris

Thank you to all the contributors who dedicated time and energy to bring the best WordPress experience to everyone.

Josepha Haden Chomphosy

1naveengiri · Aaron D. Campbell · Aaron Jorbin · Aaron Robertshaw · Abha Thakor · Abu Hurayra · Adam Bosco · Adam Pickering · Adam Silverstein · Adam Wiltgen · Adam Zielinski · Addie · Adil Öztaşer · aduth · Aezaz Shekh · afrid1719 · Ahmed Chaion · Ahmed Saeed · Akash Mia · Aki Hamano · Akram Ul Haq · Akshit Sethi · Alain Schlesser · alamgircsebd · AlanP57 · alansyue · albatross10 · Albert Juhé Lluveras · Alberuni Azad. · Alejandro J. Sanchez P. · Aleksej · Alex Concha · Alex Lende · Alex Mills · Alexis Coulombe · alexstine · allancole · allisonplus · Alvaro Gómez · amirkamizi · Amjad Ali · Anantajit JG · Anariel Design · Andrea Fercia · Andreas · Andrei Draganescu · Andrei Surdu · Andrew Nacin · Andrew Ozz · Andrew Serong · Andrew Wilder · AndrewNZ · Andrey "Rarst" Savchenko · Andrija Naglic · André · Andy Fragen · Andy Keith · Aniket Patel · anitanenova · Ankit K Gupta · Anna Bansaghi · Anne McCarthy · Ante Laca · Anthony Burchell · Anton Vlasenko · apedog · apokalyptik · AR Rasel · arcangelini · archon810 · Ari Stathopoulos · Ariel Chinn · Arjun Singh · Arnab Mondal · Arslan Kalwar · Artur Grabowski · Arunas Liuiza · Aspexi · Aurooba Ahmed · Austin Matzko · Ayesh Karunaratne · BaneD · barneydavey · Bartosz Bobnis · Beatriz Fialho · Ben Dwyer · Ben Greeley · Benachi · Benjamin Grolleau · Benoit Chantre · Bernhard Reiter · Bernie Reiter · Bhrugesh Bavishi · Bing · Birgir Erlendsson (birgire) · Birgit Pauli-Haack · Blockify · Bob · bobbingwide · bonger · Boone Gorges · Brad Jorsch · Brandon Kraft · Brian Alexander · Brian Gardner · Bruno Cantuaria · Bruno Ribaric · burgiuk · Burhan Nasir · bwbama · cadlec · cagsmith · Carlos Bravo · Carlos Garcia Prim · Carolina Nymark · cavalierlife · cdbessig · Chad Chadbourne · Chandra M · Channing Ritter · Chetan Prajapati · Chintan hingrajiya · Chloe Bringmann · Chouby · Chris Budd · Chris Hardie · Chris Zarate · chriscct7 · chrisguitarguy · Christian-W. Budde · Christina Voudouris · Christoph Daum · Christopher Finke · Chuck Reynolds · chynnabenton · ckanderson22 · CodePoet · codewhy · Colin Stewart · Collie-IT, Anne K. Frey · colonelphantom · Cory Birdsong · Courtney Robertson · craigfrancis · crazycoders · Crisoforo Gaspar · Cupid Chakma · Curdin Krummenacher · cyrillbolliger · Daijiro Miyazawa · dainemawer · Daisy Olsen · Dale du Preez · Damon Cook · damonganto · Dan Farrow · Dan Soschin · Daniel Bachhuber · Daniel Iser · Daniel Richards · Daniel Schutzsmith · Daniele Scasciafratte · darerodz · Daria · Darin Kotter · Darko G. · darkskipper · Darren Coutts · Dat Hoang · datainterlock · Dave Hilditch · dave1010 · David Anderson · David Baumwald · David Biňovec · David C · David Calhoun · David E. Smith · David Goring · David Gwyer · David Herrera · David Rozando · David Smith · daxelrod · daymobrew · Deepak Vijayan · Denis de Bernardy · Denis Žoljom · denishua · Dennis Claassen · Dennis Snell · derekblank · Derrick Hammer · Dharmesh Patel · dhl · Diane Co · Dilip Bheda · dingdang · Dion Hulse · Dipak Parmar · divyeshgodhani · Dominik Schilling · donmhico · Doug Wollison · Dougal Campbell · Drew Jaynes · Drivingralle · drzraf · dsas · Dwain Maralack · Dzikri Aziz · Dōvy Paukstys · eclev91 · Edwin Cromley · eedee · Ehtisham S. · Eliezer Peña · Ella van Durpe · Emily Clarke · Emmanuel Hesry · Enrico Battocchi · Erick Hitter · Erik · Erik Betshammar · estelaris · eugene.manuilov · Eugene.Manuilov · Evan Herman · Evan Mattson · Evan Mullins · Fabian Kägy · Faisal Alvi · Faison · Felipe Elia · Felix Arntz · Fellyph Cintra · Femy Praseeth · Florian Brinkmann · Francisco · Fuad Ragib · furi3r · gabri3lmarques · Gabriel de Tassigny · Gabriel Rose · Garrett Hyder · Garth Mortensen · Gary Jones · Gary Pendergast · garymatthews919 · George Hotelling · George Mamadashvili · George Stephanis · Gerardo Pacheco · gigitux · giox069 · giuseppemazzapica · Glen Davies · goldenapples · Grégory Viguier · graham73may · Grant M. Kinney · Greg Ziółkowski · greg24 · gRegor Morrill · gunterer · Gustavo Bordoni · h2ham (Hiromu Hasegawa) · hakanca · hakre · Hans-Christiaan Braun · Hardik Thakkar · Harit Panchal · harshvaishnav · Hasanuzzaman · Hauwa Abashiya · Helen Hou-Sandi · Henrique Iamarino · Henry Wright · here · Herre Groen · Hilay Trivedi · hiren sanja · hiyascout · Howdy_McGee · hugodevos · huubl · hztyfoon · Héctor Prieto · Ian Belanger · Ian Dunn · iansvo · iCaspar · Ignacio Cruz Moreno · Igor · igrigorik · ilovecats7 · ilunabar · imadarshakshat · ipajen · Ipstenu (Mika Epstein) · irecinius · Isabel Brison · Iulia Cazan · ivanjeronimo · iviweb · J.D. Grimes · Jacob Schweitzer · Jakaria Istauk · James Kemp · James Koster · jamieburchell · Jan Thiel · Jarret · Jason Johnston · Jasper Kinoti · Javier Arce · Javier Casares · Jay Trees · Jean-Baptiste Audras · jeawhanlee · Jeff Ong · Jeff Paul · Jeff Uberstine · Jeremy Felt · Jeremy Herve · JeroenReumkens · Jessica Lyschik · jhart35 · jhnstn · jigar bhanushali · jnz31 · Joe Dolson · Joe Hoyle · Joe McGill · joelhardi · Joen Asmussen · John Blackbourn · John James Jacoby · John Regan · johnmark8080 · Jon Brown · Jon Surrell · Jonathan Bossenger · Jonathan Desrosiers · Jonathan Pantani · jonmackintosh · Jonny Harris · jonny-s · Jono Alderson · Joost de Valk · Jorge Costa · Jos Velasco · Joseph Grainger · Josepha Dambul · Josepha Haden · Josh Habdas · Joshua Abenazer · Joy · jrbeilke · jsnajdr · Juhi Saxena · Julie Moynat · Juliette Reinders Folmer · Julio Potier · just0nequestion · Justin Ahinon · Justin Sainton · Justin Tadlock · Justin Welenofsky · jyolsna · K. Adam White · KafleG · Kai Hao · Kajal Gohel · Kalpesh Akabari · Kapil Paul · Kari Anderson · karlgroves · Karlijn Bok · Kaspars · Kathryn Presner · kbrownkd · Keanan Koppenhaver · Kelly Choyce-Dwan · Kelly Hoffman · Kevin Behrens · Kevin Hagerty · Khoi Pro · Khokan Sardar · killua99 · Kishan Jasani · kitchin · Kjell Reigstad · kkmuffme · klewis · Knut Sparhell · Koen Van den Wijngaert · Konrad.K · Konstantin Kovshenin · Kris Kelvin · KrishaWeb · Krupal Panchal · Kunal Madhak · Kurt Payne · kwillmorth · Kyle B. Johnson · Kyle Nel · laurelfulford · Lauren Stein · laurent22777 · lazam786 · Lee Willis · leemon · Lena Morita · leogermani · Linkon Miyan · Linnea Huxford · lonnylot · Lovekesh Kumar · Lovro Hrust · Lucas Bustamante · lucilastancato · luigipulcini · Luis Felipe Zaguini · luisherranz · Luiz Araújo · Lukas Niebler · Luke Cavanagh · M S Newaz · Maarten · Maciej · maciejmackowiak · Madhu Dollu · Madhu Dollu · Maggie Cabrera · magicoders · Mahrokh · maksimkuzmin · malthert · manfcarlo · Manish Songirkar · Manzoor Wani · Manzur Ahammed · Marc · Marcelo de Moraes Serpa · Marco Ciampini · Marcus Kazmierczak · Marek Dědič · Marianna · Marie Comet · Marin Atanasov · Marius L. J. · Mark Biek · Mark Howells-Mead · Mark Jaquith · Mark Parnell · Marko Heijnen · Markus · Markus Kosmal · Martijn van der Klis · Martin Stehle · martin.krcho · Mary Baum · Mashu · masteradhoc · Matías Emanuel Surdi · Matias Ventura · matiasbenedetto · Matt Chowning · Matt Mullenweg · Matt Wondra · Matthew Boynes · Matthew Eppelsheimer · Matthias Pabst · Matthias Reinholz · mattyrob · Mauriac AZOUA · Maxime J. · Maxime Meganck · Mayank Majeji · maythamalsudany · Mayuge · mcliwanow · Md Rakib Hossain · Md. Russel Hussain · mdrago · Mehedi Foysal · Meher Bala · Mehul Kaklotar · Mel Choyce-Dwan · meloniq · Merkys Maliukevičius · meysam norouzi · Micha Krapp · Michael Bourne · Michael Burridge · Michal Czaplinski · Miguel Fonseca · Mihai Dumitrascu · Mike Crantea · Mike Glendinning · Mike Hansen · Mike Jolley (a11n) · Mike Schroder · mikemanzo · Milana Cap · Milind More · mimi · Minal Diwan · miya · Mladen · Mohammad Jangda · MohammadJafar Khajeh · Mohit Dadhich · Monique Dubbelman · moto hachi · mreishus · mrobit · msolution · mtias · Muhammad Arslan · Mukesh Panchal · Muntasir Mahmud · Mustaque Ahmed · mvraghavan · mweichert · n8finch · Nahid Hasan · Nalini Thakor · Namith Jawahar · Naresh Bheda · Nate Allen · Nathan · Nathan Johnson · navigatrum · neffff · nendeb · Neycho Kalaydzhiev · Nicholas Garofalo · Nick Diego · Nick Halsey · Nico · nidhidhandhukiya · Nik Tsekouras · nikkigagency · Niloy · Ninos · Nithin John · Nithin SreeRaj · nlpro · Noah Allen · noplanman · nouarah · NumidWasNotAvailable · Nuno Morgadinho · Nurul Umbhiya · nvartolomei · Obayed Mamur · obliviousharmony · oguzkocer · Olga Gleckler · Oliver Stapelfeldt · OllieJones · oneearth27 · Onni Hakala · opr18 · ovidiul · p_enrique · Paal Joachim Romdahl · Pablo Postigo · PabloHoney · palmiak · Paolo L. Scala · Paragon Initiative Enterprises · Parham Ghaffarian · Pascal Birchler · Patrick Groot · Paul Bearne · Paul Biron · Paul Kevan · Paul Ryan · Paulo Cruz · Paulo Trentin · Pavan Patil · pavelschoffer · pbking · Pedro Mendonça · Peter Westwood · Peter Wilson · petitphp · Petter Walbø Johnsgård · Phil Johnston · Phill · Pierre Sylvestre · Pieterjan Deneys · Piotrek Boniu · Pippin Williamson · Pooja Derashri · Pooja N Muchandikar · Praful Patel · Pratiksha · presscustomizr · Presskopp · presstoke · Priyo Mukul · prokium · Q · Rachel Baker · Rachel Peter · raduiason · Rafi Ahmed · Rahi Prajapati · Rajan Panchal · Rajesh Raval · ralucastn · Ramanan · Ramon Ahnert · Ramon Corrales · ramon fincken · Ramon James · randhirexpresstech · Ravikumar Patel · rcanepa · rebasaurus · Rehan Ali · Remy Perona · Renatho (a11n) · renegeuze · Reuhno · rflw · Riad Benguella · Rich Tabor · Rinat · Rinky Chowdhury · Rishi Shah · rkaiser0324 · Robert Anderson · Robert Chapin · robertght · Robin · robmiller · rodrigosevero · Rolf Allard van Hagen · Rolf Siebers · rollybueno · Romain Herault · romulodl · ross_ritchey · Roy · Russell Aaron · Ryan Boren · Ryan McCue · Ryan Murphy · Ryan Welcher · Sébastien SERRE · Sérgio Gomes · Sören Wrede · Sabbir Ahmed · Sajjad Hossain Sagor · Sakri Koskimies · Sami Keijonen · Sampat Viral · Samuel Wood (Otto) · Sandip Mondal - a11n · Sandra Sanz · santosguillamot · Sarah Norris · sarahricker · Sathiyamoorthy V · Saumya Majumder · Saurabh Sharma · Scott Fennell · Scott Kingsley Clark · Scott Lesovic · Scott Taylor · scribu · Sean Fisher · Sebastian Pisula · seieric · Sergey Biryukov · Sergio Scabuzzo · seriouslysenpai · Seth Alling · shangidah afroz · Shannon Little · Sharjeel Khan · shetheliving · Shoaib Ali · Shraboni · Shreyas Ikhar · shuvo586 · siddharth ravikumar · Siddharth Thevaril · Siobhan · sirzooro · Slava Abakumov · Slobodan Manic · Smit Rathod · sobatkras · Stanislav Khromov · SteelWagstaff · Stefano · Stefano Minoia · Stefanos Togoulidis · Stephen Bernhardt · Stephen Edgar · Stephen Page · Sterling Hamilton · Steven Lin · steveo2000 · studiolxv · Sumit Bagthariya · Sumit Singh · Sumit Singh (WP Lovers) · Sumon Sarker · SunilPrajapati · sunyatasattva · Sybre Waaijer · Synchro · system909 · Tahmid ul Karim · Takashi Kitajima · Tammie Lister · Tanbir Ahmod · Tanvirul Haque · Taras Dashkevych · targz · Taylor Lovett · tazotodua · tbember · Teddy Patriarca · Tellyworth · Terence Eden · tharsheblows · thejaydip · Thierry Muller · Thijs · Thomas Griffin · Thorsten Schraut · threadi · Tiffany Bridge · Till Krüss · Timothy Jacobs · Titus Moore · TobiasBg · tobifjellner (Tor-Bjorn Fjellner) · Tom de Visser · Tom J Nowell · Tom Janssen · Tom Rhodes · Tomasz Tunik · tomepajk · Tomoki Shimomura · Toni Viemerö · tony.localword · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · transl8or · Travis Smith · Tremi Dkhar · TrevorPolischuk · Trinadin · Tung Du · turtlepod · Ugyen Dorji · Ulrich · Umesh Gupta · upadalavipul · utsavmadaan823 · Vagelis · varma · vasartam · vdankbaar · Velochicdunord · Vicente Canales · vikasprogrammer · Virginie Garnier · Vishal Kakadiya · vortfu · webbeetle · Weston Ruter · whaze · Whissi · William Earnhardt · williampatton · withinboredom · woji29911 · Yahil Madakiya · Yan Knudtskov · Yann · Yoav Farhi · Yohann Billard · Yui · yuu · zaerl · Zebulan Stanphill · Zenaul Islam · ziposc · Česlav Przywara · 沈唁

WordPress 6.1 would not have been possible without the contributions of more than 800 people in over 60 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.

Haiku Fun for 6.1

Another release,
Mark it down as completed.
Breathe, relax, and cheers!