Yalla Download

Say hello to WordPress 6.2 “Dolphy,” named for the woodwind jazz wiz, the multi-instrumentalist—Eric Allan Dolphy Jr. Dolphy is acclaimed for having brought the bass clarinet to prominence in the jazz scene, creating a place for the flute and extending the lexicon of the alto saxophone. In a career that spanned continents, his artistry was at the forefront of pushing improvisational boundaries, ensemble work, and partnerships with well-respected artists like Charles Mingus and John Coltrane.

This latest version of WordPress reimagines your site editing experience, introduces more ways to style your site, and offers a new distraction-free way to write. Discover improvements that give you more control and freedom to express your creative vision. There’s something for everyone, whether you’re a content creator, developer, site builder, or designer. Let the music of Eric Dolphy delight you as you take in all that 6.2 has to offer.

WordPress 6.2 is the first major release of 2023, covering over 900 enhancements and fixes. It’s also a transition point in the WordPress project’s development roadmap, shifting focus from customization to early exploration of workflows and collaboration.

What’s inside

Meet the reimagined Site Editor

Ready for you to dive in and explore: 6.2 is your invitation to discover what the next generation of WordPress—and block themes—can do. 

Now out of beta, the Site Editor has an updated interface, giving you a new way to interact with your entire site. Explore full previews of your templates and template parts, then jump in and get to editing your site from wherever you choose.

Manage menus in more ways with the Navigation block

Add, remove, and reorder menu items faster—with a new sidebar experience that makes editing your site’s navigation easier.

Discover a smoother experience for the Block Inserter

A refreshed design gives you easier access to the content you need. Use the Media tab to quickly drag and drop content from your existing Media Library. Find patterns faster with a split view that lets you navigate categories and see previews all at once.

Find the controls you want when you need them

Your block settings sidebar is better organized with tabs for Settings and Styles. So the tools you need are easy to identify and access. 

Build faster with headers and footers for block themes

Discover a new collection of header and footer patterns. Use them with any block theme as a quick, high-quality starting point for your site’s templates.

Explore Openverse media right from the Editor

Openverse’s library catalogs over 700 million+ free, openly licensed stock images and audio—and now it’s directly integrated into the WordPress experience through the Inserter. 

Focus on writing with Distraction Free mode

For those times you want to be alone with your ideas. You can now hide all your panels and controls, leaving you free to bring your content to life.

Meet the new Style Book

Get a complete overview of how every block in your site’s library looks. All in one place, all at a glance, directly in the Site Editor.

Copy and paste styles

Perfect the design on one type of block, then copy and paste those styles to other blocks to get just the look you want.

Custom CSS

Power up your site any way you wish with design tools and custom CSS for another level of control over your site’s look and feel for maximum creativity and artistry in your designs.

Other highlights in 6.2

• Sticky positioning: Choose to keep top-level group blocks fixed to the top of a page as visitors scroll.
• Importing widgets: Options to import your favorite widgets from Classic themes to Block themes.
• Local fonts in themes: Default WordPress themes offer better privacy with Google Fonts now included.

Learn more about WordPress 6.2

Explore Learn WordPress for quick how-to videos, courses, and other resources for the latest features in WordPress. Or join a free live interactive online workshop.

Check out the WordPress 6.2 Field Guide for detailed developer notes to help you build with WordPress and get the most out of the latest release. Read the 6.2 release notes for additional technical details about this release, including installation information, updates, fixes, file changes, and more.

The 6.2 release squad

6.2 is made possible by the many folks who have enthusiastically helped keep the release on track and moving forward:

• Release Lead: Matt Mullenweg
• Release Coordinators: Francesca Marano, Héctor Prieto
• Core Tech Co-Leads: Tonya Mork, Jb Audras
• Editor Tech Co-Leads: George Mamadashvili, Nik Tsekouras
• Core Triage Co-Leads: Colin Stewart, Mukesh Panchal
• Editor Triage Co-Leads: Anne McCarthy, Nick Diego
• Design Lead: Rich Tabor
• Documentation Co-Leads: Birgit Pauli-Haack, Femy Praseet, Milana Cap, Abha Thakor
• Marketing & Communications Co-Leads: Jonathan Pantani, Lauren Stein, Mary Baum
• Test Co-Leads: Robin, Adel Tahri
• Performance Lead: Felix Arntz

Thank you, contributors

WordPress 6.2 couldn’t be here without the countless effort and passion of more than 600 contributors in at least 50 countries. A special thank you to the 178 new contributors who joined a release for the first time. Their collaboration helped deliver hundreds of enhancements and fixes, ensuring a stable release for all—a testament to the power and capability of the WordPress community.

10upsimon · 254volkan · @mercime · Aaron D. Campbell · Aaron Graham · Aaron Jorbin · Aaron Robertshaw · Abha Thakor · Abid Hasan · abitofmind · ABTOP · ace100 · Adam Bosco · Adam Silverstein · Adam Wiltgen · Adel Tahri · Adhun Anand · adityaarora010196 · aduth · Afshana Diya · Ahmed Chaion · Ajay Maurya · ajayver · Akash Mia · Aki Hamano · Alain Schlesser · Alan Jacob Mathew · albarin · Alberuni Azad. · alecgeatches · Aleks Ganev · Alex Concha · Alex Lende · Alex Stine · alvastar · Alvi Tazwar · amin · amirrezatm · Amit Barai Alit · Amit Paul · Anantajit JG · Andrea Fercia · andreaboe · Andrei Draganescu · Andrew Matthews · Andrew Nacin · Andrew Ozz · Andrew Serong · Andrey "Rarst" Savchenko · André · Andy Fragen · Andy Peatling · Aniket Patel · Ankit K Gupta · Ankit Panchal · Anne McCarthy · Anthony Burchell · Anthony Hortin · Anton Vlasenko · Antony Agrios · Aparna Adhun · AR Rasel · Arafat Jamil · Aravind Ajith · Ari Stathopoulos · arnolp · Artemio Morales · Arthur Chu · ArtZ91 · Arun · Ashar Irfan · Ashraful Sarkar Naiem · Autumn · Ayesh Karunaratne · azurseisme · Barry Ceelen · Bart · Beatriz Fialho · Beda · Ben Dwyer · benish74 · Benjamin Grolleau · Benoit Chantre · Bernhard Kau · Bernie Reiter · Bethany Chobanian Lang · bgin · Bhavik Kalpesh · Birgir Erlendsson (birgire) · Birgit Pauli-Haack · bjorn2404 · BogdanUngureanu · bonjour52 · bookwyrm · Boone Gorges · Brad Jorsch · Brady Vercher · Brandon Kraft · Brennan Goewert · Brian Gardner · bronsonquick · Brooke Kaminski · Brooke. · buutqn · Cameron Jones · Carlos Bravo · Carlos Garcia Prim · Carolina Nymark · Chad Chadbourne · Channing Ritter · Chauncey McAskill · Chintan hingrajiya · Chirag Rathod · Chloe Bringmann · chocofc1 · Chouby · chrisbaltazar · Christoph Daum · Chrystl · ckanderson22 · Clayton Collie · cnspecialcolor · codesdnc · Coding Chicken · Colin Stewart · conner_bw · Copons · corentingautier · Corey Worrell · Cory Birdsong · Craig Francis · craiglpeters · Creative Andrew · Crisoforo Gaspar · Cupid Chakma · D.PERONNE · Daisy Olsen · dali-rajab · Damien Alleyne · Damon Cook · Daniel Bachhuber · Daniel Johnson · Daniel Richards · Daniele Scasciafratte · darerodz · datagutten · David Aguilera · David Baumwald · David Biňovec · David Calhoun · David Gwyer · David Herrera · David Marín Carreño · David Shanske · David Smith · David Vongries · Dean Sas · Dennis Claassen · Dennis Snell · derekblank · devanshijoshi · dhusakovic · Dilip Bheda · Dion Hulse · doctorlai · Dominik Schilling · Donncha · drzraf · DSIGNED · dustinrue · Edwin Cromley · Ella van Durpe · emanuelx · Emmanuel Hesry · Enej Bajgorić · Enrico Battocchi · Eric Andrew Lewis · Erick Danzer · Erik Betshammar · Esrat Sultana Popy · Eugene M · Evan Herman · Fabian Kägy · Faisal Ahmed · Faisal Alvi · fasuto · Felipe Elia · Felipe Lavín · Felix Arntz · Femy Praseeth · Florian TIAR · fpodhorsky · Francesca Marano · Francisco · Frank Bueltge · franzaurus · Fuad Ragib · Gal Baras · gamecreature · Garrett Hyder · Gary Pendergast · Gennady Kovshenin · George Hotelling · George Mamadashvili · Gerardo Pacheco · gisgeo · Glen Davies · Greg Ziółkowski · grl570810 · gvgvgvijayan · H-var · hakre · hanshenrik · Hareesh S · Harit Panchal · Hasan Misbah · Hasanuzzaman · Haz · Helen Hou-Sandi · HelgaTheViking · Helmut Wandl · Hendrik Luehrsen · Hilay Trivedi · hiren sanja · Hitesh Patel · hughie.molloy · hugodevos · hztyfoon · Héctor Prieto · Iain Poulson · Ian Belanger · Ian Dunn · Iazel · Ignat Georgiev · imanish003 · ingeniumed · Innovext · inwerpsel · iqbalrony · ironprogrammer · Isabel Brison · IT Path Solutions · ivanjeronimo · j.hoffmann · Jack Reichert · Jaed Mosharraf · Jakaria Istauk · James · James Koster · James Roberts · Jan Thiel · janusdev · Jarda Snajdr · Jarko Piironen · Javier Arce · Javier Carazo · Javier Casares · jchambo · Jean-Baptiste Audras · Jean-Philippe Green · jeawhanlee · Jeff Matson · Jeff Ong · Jeffrey Paul · Jennifer M. Dodd · Jeremy Felt · Jeremy Herve · Jeremy Lind · jeryj · Jessica Lyschik · jhned · jigar bhanushali · Jip Moors · Joe Dolson · Joe McGill · joelmadigan · Joen Asmussen · John Blackbourn · John James Jacoby · John Watkins · Jokerrs · Jon Brown · Jonathan Bossenger · Jonathan Desrosiers · Jonathan Pantani · Jong · Jonny Harris · Jorge Costa · jornp · Joseph G. · Josepha Haden · joshuatf · Joy · jsh4 · Juan Aldasoro · JuanMa Garrido · Juhi Saxena · Juliette Reinders Folmer · Julio Potier · Justin Ahinon · Justin Tadlock · Justin Welenofsky · justlevine · K. Adam White · kacper3355 · KafleG · Kai Hao · Kajal Gohel · kaneva · Kapil Paul · Kathryn P. · Keanan Koppenhaver · Kelly Choyce-Dwan · Kelly Hoffman · Kevin Batdorf · Kjell Reigstad · Konstantin Obenland · konyoldeath · Kowsar Hossain · Krunal Bhimajiyani · Krupal Panchal · Kunal Madhak · Lana Codes · larsmqller · laurelfulford · Lauren Stein · Lena Morita · Lena Stergatou · Leo Milo · lifeboat · Linkon Miyan · lkraav · Loïc Antignac · Lovekesh Kumar · Lox · lozula · lucius0101 · Lucy Tomas · Luigi · luisherranz · Lukman Nakib · Márcio Duarte · Madhu Dollu · Madhu Dollu · Maggie Cabrera · Mahbub Shovan · Mahek Kalola · manfcarlo · Manoj Patil · Marcelo de Moraes Serpa · Marco Ciampini · Marek Dědič · Marie Comet · Marin Atanasov · Mario Santos · Marissa Matthews · Marius L. J. · Mark Jaquith · Marko Ivanovic · marksabbath · Markus · Markus Kosmal · Martijn van der Klis · Mary Baum · matclayton · Mateus Machado Luna · Mathieu Paapst · Matias Ventura · matiasbenedetto · Matt Keys · Matt Mullenweg · Matthias Reinholz · Mauricio · Max · Max Lyuchin · Maxime J. · MD Jamil Uddin · Md Kawser Ahmed Khan Jami · Md Rakib Hossain · Md. Abir Hasan Dipu · Md. Reduan Masud · mdviralsampat · Mehul Kaklotar · mensmaximus · meyerdev.ch · mgol · Michael Burridge · Michael Kelly · Michal Czaplinski · Michel Many · Miguel Axcar · Miguel Fonseca · Miguel Torres · Mike Schroder · Mike Straw · Milan Dinić · Milana Cap · Minal Diwan · mitchellaustin · miya · Monzur Alam · mreishus · mrwweb · mtias · mujuonly · Mukesh Panchal · Mumtahina Faguni · Musarrat Anjum Chowdhury · Mustaque Ahmed · mw108 · Naeem Haque · Namith Jawahar · Nathan Johnson · Nazmul Hasan · nendeb · Neycho Kalaydzhiev · Nicholas Garofalo · nicholaswilson · Nick Diego · Nick the Geek · nidhidhandhukiya · Niels Lange · Nik Tsekouras · NikhilPatel · Niluthpal Purkayastha · Nitesh Das · Nithin John · Nithin SreeRaj · Nitin Rathod · nitman43 · Noah Allen · nuvoPoint · oakesjosh · Obayed Mamur · ockham · oguzkocer · oh_hello · Okamoto Hidetaka · Olga Gleckler · OllieJones · Omar Alshaker · Paal Joachim Romdahl · PabloHoney · Pascal Birchler · Paul Bearne · Paul Biron · Paul Kevan · Paul Schreiber · pavelevap · pbking · Pedro Mendonça · pepe · Petar Ratković · Peter Wilson · petitphp · Petter Walbø Johnsgård · Phil Webster · Phill · Pial · Pieterjan Deneys · Piotrek Boniu · PJ Brunet · pkolenbr · Pooja N Muchandikar · Pravin Parmar · Presskopp · Ptah Dunbar · pypwalters · raduiason · Rafael Agostini · Rafin · Rajan Panchal · Rajesh Raval · Ramon Ahnert · ramon fincken · Ramon James · Razthee Md. Yakini · Renato Augusto Gama dos Santos · Reza Khan · Riad Benguella · Riccardo Di Curti · Rich Tabor · Rinky Chowdhury · Ritesh Patel · rjasdfiii · Robert Anderson · Robin · Robin Labadie · rodage · rodricus · Rolf Allard van Hagen · Ross Gile · Roy Tanck · Ruchir Goswami · Rupok · Ryan · Ryan Kienstra · Ryan Welcher · Ryo · Sé Reed · Sérgio Gomes · Sören Wrede · Sahil B. · Sajib Talukder · Sakib Mohammed · Sam Fullalove · sam1el · samiamnot · Sampat Viral · samruddhikhandale · Samuel Wood (Otto) · sanjucta · Sanket Chodavadiya · Sanne van der Meulen · sapayth · Sarah Norris · Sarath AR · Saumil Nerpagar · Sazia Faizunnessa Ira · Scott Kingsley Clark · Scott Winterroth · Scout James · Sean Hayes · Sergey Biryukov · seriouslysenpai · Seth Miller · Shahidul Islam · Shamayel · Shamim Mia · Sharif Mohammad Eunus · Shraboni · shubham1gupta · Silicium · Simon Gomes · Simon Lieschke · Siobhan · snicco.io · sruthi90 · SteelWagstaff · Stefano Minoia · stentibbing · Stephen Bernhardt · Stephen Edgar · Stephy Miehle · stephymiehle · Steven Word · Subrata Sarkar · Sumit Singh · sun · sunyatasattva (a11n) · Suvro · syamraj24 · Sybre Waaijer · Syeda Sanjida Afrin · syhc · Synchro · syntaxart · szaqal21 · Tahmid ul Karim · tahminar27 · Takashi Kitajima · Tanaz Masaba · Tanbir Ahmod · Tanner Moushey · Tasnia Rahman Raima · teebee · tekapo · thedaysse · thejaydip · theode · Thomas Griffin · Thomas Patrick Levy · thomask · timbroddin · Timi Wahalahti · Timothée Brosille · Timothy Jacobs · TobiasBg · tobifjellner (Tor-Bjorn Fjellner) · Tom J Nowell · Tomasz Dziuda · Toni Viemerö · Tony G · Tonya Mork · Torsten Landsiedel · Toru Miki · Towhidul I Chowdhury · travisaxton · triumvirate · Tung Du · Umesh Gupta · upadalavipul · Vagelis · Vicente Canales · Viktor Szépe · Virginie Garnier · Vishal Kumar · Vlad T · vtad · vykesmac · WebMan Design | Oliver Juhas · Webrocker · websitegenii · Weston Ruter · whaze · winterpsv · wojsmol · Wojtek Naruniec · Wojtek Szkutnik · Yui · Yuliyan Slavchev · Zeba Afia Shama · Zenaul Islam · zevilz · zieladam · Česlav Przywara

By release day, 70 locales had translated 90 percent or more of WordPress 6.2 in their language. Community translators are hard at work ensuring more translations are on their way. Thank you to everyone who helps to make WordPress 6.2 available in 200 languages.

A release haiku for 6.2 

Six point two, so new
Shiny and ready for you
Congrats on hard work!

* Portrait of Eric Allen Dolphy Jr. discovered via Openverse. Colorization by D. Pountain; Original by F. Wolff.
“eric dolphy” by dick_pountain is licensed under CC BY-NC-SA 2.0.

Are you taking your first steps in selling a product or service online and don’t know where to start? Be sure to register for our upcoming WooCommerce 101 webinar, where our expert Happiness Engineers will walk you through everything you need to know about setting up an online store with WooCommerce and WordPress.com managed hosting.

Webinar details

• Date: Tuesday, March 28, 2023 
• Time: 16:00 UTC  | 18:00 CEST | 12pm EDT | 9:00am PDT  
• Cost: Free
• Who’s invited: business owners, entrepreneurs, freelancers, service providers, store owners, and anyone else who wants to sell a product or service online.

What you’ll learn

Whether you’re an e-commerce veteran or this is your first business, join us for the inside scoop on launching a store that’s fully customizable, completely yours, and ready to grow from the start. In this live webinar, our Happiness Engineer will demonstrate how to:

• Instal Woo on your existing WordPress site
• Use the setup wizard to get up and running fast
• Set up simple products, basic shipping, and tax support
• Collect payments through WooCommerce Payments and other gateways

No previous e-commerce experience is necessary, but we recommend a basic familiarity with WordPress.com to ensure you can make the most from the webinar. A Q&A session will follow the walkthrough, so be sure to bring any questions you might have!
Seats are limited, so register now to reserve your spot. See you then!

Has your desktop been looking a bit drab lately? If so – or if you’d just like to show a little WordPress love – we’ve got just the remedy: 30 one-of-a-kind WordPress desktop wallpapers to breathe new life into your backgrounds.

The wallpapers

Download and install

To add a wallpaper to your desktop:

• Click on any image to open a fullscreen carousel
• Right-click the image if you’re using Windows or Linux, or command-click on a Mac
• Save the wallpaper to your favorite folder
• And set it as your desktop wallpaper (Windows / Ubuntu / MacOS)

About the wallpapers

The wallpapers are a homage to some of our favorite artists, with a nod to the freedom, innovation, and creativity of open-source software. 

We put these together with an entirely open-source AI tool called Stable Diffusion. Like WordPress, Stable Diffusion is all about helping more people to create, experiment, and share, while having the freedom to access and contribute to the code making it all happen.

Over to you

We’d love to hear what you think, and if you have any favorites. Of course, please feel free to remix, use these on your blog, or share your work in the comments!

On Episode fifty-two of the WordPress Briefing podcast, join WordPress Executive Director Josepha Haden Chomphosy and special guest Héctor Prieto as they discuss phase three and why it’s more than just collaborative editing!

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

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

Show Notes

• Write as Blocks in an Encrypted Collaborative Environment by Riad Benguella
• Riad Benguella’s collaborative editing GitHub repository
• Riad Benguella’s WordPress.org Profile
• Block Collab: New package, a framework for collaborative editing GitHub PR
• Phase 3: Collaboration
• Matías Ventura Quick Search GH Issue
• Matías Ventura WordPress.org Profile
• WordPress 6.2 Release Day Process
• Introducing the WordPress Developer Blog
• WordCamp Europe Contributor Day Registration
• WP20 Wapuu Coloring Giveaway

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:40]

I have with me today Hécto Prieto. You all may know him from the WordPress Slack. He recently was, I believe, a release coordinator, maybe for the last release. Was that for 6.1?

[Héctor Prieto 00:00:51]

Yes. It was for 6.1 and also 6.0, in fact.

[Josepha Haden Chomphosy 00:00:54]

All right. Well, welcome to the WordPress Briefing today. How are you doing?

[Héctor Prieto 00:00:59] 

Well, I’m excited to be here. I’m a longtime listener of the podcast since the first episode. So I’m super excited to be here with you today.

[Josepha Haden Chomphosy 00:01:06]

Yes. Longtime listener. First-time caller. All right, well, we’re gonna have a topic that just dumps you right in the soup, as they say in the United States. So we are actually here to talk about phase three of Gutenberg. It’s been a long time coming, and there are a lot of questions that folks have about what’s going into it and what’s not going into it.

And as someone who works really closely with our Gutenberg technical architect, Matías Ventura, I figured you would be exactly the right person to come and talk about your favorite things. From your perspective, what is going to be the biggest enhancement that we start to approach in phase three?

Like which thing, which API is gonna take the most work, do you think?

[Héctor Prieto 00:01:53]

Well, the most work, that’s a very hard question to answer because we are still we are going to start an exploration phase to determine how far we want to go with each of these APIs. So, in general, all these APIs and these products are standalone projects. And some of them are shorter, and some of them are longer.

I would say, in general, the real-time collaboration sounds the most technically challenging because of what it represents and all the changes needed to how we interact with WordPress from async to sync, basically. That would be the hardest part. I think there are also already a few prototypes working, but we need to see how that scales, for example.

[Josepha Haden Chomphosy 00:02:32]

Yeah. So speaking of a few prototypes, I know that there are two or three different prototypes specifically for collaborative editing, but do we have people or groups, working groups in the community that have built any other prototypes? Or is it just kind of first passes at collaborative editing that we’ve seen?

[Héctor Prieto 00:02:52]

Well, apart from Riad Benguella’s exploration, there’s a public repository with that exploration, there are a few plugins trying the same, trying real-time collaboration.

[Josepha Haden Chomphosy 00:03:03]

Yeah, I can think of co-blocks and as blocks, and then I feel like there was a third one.

[Héctor Prieto 00:03:09] 

Yeah.

[Josepha Haden Chomphosy 00:03:09]

We’ll find the links to all these

[Héctor Prieto 00:03:12]

Yeah. Let’s add them to the show notes.

[Josepha Haden Chomphosy 00:03:14]

Excellent. So that’s going to be the biggest one. Is there, of the list of APIs, and this is based on the post that Matías sent out last week. If you all haven’t seen that, we’ll put that in the show notes as well. But from the APIs that Matías sort of helped us to identify last week, is there any one that you are particularly excited about for fixing things in WordPress or just generally like an interesting topic of development for you?

[Héctor Prieto 00:03:42]

Well, I would say all of them and how they all play together. But, if I need to pick one of them…

[Josepha Haden Chomphosy 00:03:48]

Everything’s the best! 

[Héctor Prieto 00:03:50]

I’ll cheat anyway, and I will going to pick two out of them because they solve issues at different levels. I’m very excited about visual revisions. I think it helps a lot of users, and it affects even non-technical users.

So it’s one of the projects that lower how hard or complex WordPress can be to use sometimes. It’s going to be a huge improvement. It’s going to, I mean, bringing blocks to the revision system. I mean, it’s just a dream come true for me. I’m also going to highlight the search everywhere or quick search feature Matías already opened an issue in the GitHub repository right now. 

[Josepha Haden Chomphosy 00:04:28]

Mm-hmm.

[Héctor Prieto 00:04:28]

So the idea for this product is to have a power user shortcut that opens searching, an Alfred-like or Spotlight-like interface for those familiar with MacOS operating systems.

When you can type anything, any place you want to go, or you want to search for any specific text in a document. And it’s supposed to be your power user command tool. So that you can do most things there.

[Josepha Haden Chomphosy 00:04:53]

Oh, and I mean not only power user command tool, but also there are some applications there for folks who have mobility issues, people who are using primarily keyboard as opposed to keyboard and mouse, all that kind of stuff, right?

[Héctor Prieto 00:05:07]

Exactly. And just thinking long term with the rise of AI, it could be possible even to add some natural language processing to this interface so that users could just write in, in plain text, in natural language, what they want to do, and WordPress would provide the action for them.

[Josepha Haden Chomphosy 00:05:23]

Very nice. My two favorites, since you gave two favorites and I can’t just give one at that point, my two favorite projects, which are also probably really, really hard projects, are those explorations around fixing notifications. That is a really big project. And one that I think that, in general, the WordPress project is going to be really excited to have some input on. 

And so that’s one that I really will have an eye on. And the other one that I’m going to definitely have my eye on is the media gallery redesign. I realize that this shows, between you and I, that shows our two specific focuses. Because, of course, you work directly with guiding all of our developers. And I am very much like our user advocate. And WordPress “everyman.”

I don’t know if that’s a term that makes sense outside the US. But I do a lot of advocacy for folks who are using WordPress from the user side as opposed to from the developer side because, of course, we have a lot of excellent developers. So y’all don’t need my help with your advocacy.

But yeah, that really shows that you and I have different focuses, which I think is good too.

[Héctor Prieto 00:06:32]

Yes. Also, it’s worth noting that at the end of the day, any improvement we make for developers is so that developers can build better things for users. So, at the end of the day, everything is in the best interest of the users.

[Josepha Haden Chomphosy 00:06:45] 

That’s right. That’s definitely a good point. Yeah. So, a final question about this particular thing because we’re trying to keep it a little brief and also because we’ll have a few other podcasts that are specifically about phase three as our explorations get going. Final question here: If you felt like there was one API or one project in particular that could benefit from a lot of community involvement which would you guess that was?

[Héctor Prieto 00:07:20]

I don’t think I can single out any of them. I think getting user feedback is going to be a vital part of this phase, as always. So I would encourage our listeners to just participate in discussions and provide feedback as we start releasing the first prototypes in the Gutenberg plugin. I don’t think I can pick one of them for you, completely honest.

[Josepha Haden Chomphosy 00:07:43] 

Yeah. My guess for that is going to be the rework of the dashboard, the admin, WP admin. I think that a lot of people are gonna have a lot to say about what they use it for, what they would like to be able to use it for, how to make it look more modern, how to make it feel more modern. I think that that probably is going to benefit from a lot of early testing and possibly some specific user testing around the concepts of design in there.

And so that’s one that that I think probably is going to take a lot of feedback from the community. And community, in this case, I think, is not only our developers and designers and copy folks who are working to build the CMS, but probably also all of our folks who are extending WordPress, everybody who is working in agencies, things like that.

[Héctor Prieto 00:08:35]

Hmm, well, if I need to pick one, I would say the publishing flows could use also lots of feedback and testing because we are going to implement editorial requirements and customized user flows. And, of course, there are many, many different workflows out there that we might not be able to think of ourselves.

So just imagine the sheer amount of different use cases. There’s going to be, or there currently is with customizations of third-party plugins. So, yeah. I would like to listen to how people would like the publishing flows to be. What are the specific use cases? 

[Josepha Haden Chomphosy 00:09:09]

So really, just everything, we need a lot of user feedback on everything.

[Héctor Prieto 00:09:13]

Yes. That’s the summary.

[Josepha Haden Chomphosy 00:09:15]

I don’t think that’s a bad summary. I know that we talk a bit about how WordPress is made better by the activity of our co-creators, the people who are using the software and testing the software, and telling us how it could be better. Those are the groups of people that make sure that we are the best version or headed in the best direction on any of our things with the software.

And so I guess it’s probably not super unusual for everyone to hear like we need your feedback on everything because that’s probably what we do half the time.

[Héctor Prieto 00:09:44]

Yeah, absolutely.

[Josepha Haden Chomphosy 00:09:47]

So the publishing workflows, that reminds me that there has been a little bit of a conversation lately around the naming of this phase, basically.

And I know that the phases don’t necessarily need names. Like that’s why they’re numbered, and that’s a great idea. Like numbers are wonderful ways to reference things, but it also is just easier to reference it in kind of general conversation.

So the first phase was easier editing, and it really focused on the editing experience itself. The second one was customization, and now the third phase has been called collaboration for quite a bit of time.

But as we got closer and closer to this phase and we had more and more conversations that were coming out of phases one and two, it became really clear that really what we’re looking at here is more around workflows. And I love that that is an option for how to refer to this. Probably that’s how I will refer to it for most of the time that I talk about it as we are looking at phase three.

Because I remember that when we were first building the prototypes of Gutenberg, one of the big flags that I had was that breaking changes are not just about what we can see or any sort of visual regressions or what causes the white screen of death. Also, some of the things that are breaking changes should be considered in those workflows when we change where things are or how you accomplish a task.

And our users weren’t ready for it. That is something that is breaking for them, right?

[Héctor Prieto 00:11:25] 

Yes. As you mentioned, this phase was referenced as collaboration, real-time collaboration, for a long time, but if we think of how this collaboration looks, it’s much more than just editing at the same time. A very big part of collaboration is also asynchronous collaboration by adding in-line comments and improving these notifications when you have a comment in your draft. I think the power of this phase is how everything comes together. These individual pieces come together.

[Josepha Haden Chomphosy 0:11:51]

Yes, and I don’t know where that first flag that sparked the discussion around, like, okay, but collaborative editing is not quite big enough and also means a bunch of different things for a bunch of different people. It depends on the size of your organization or the type of content you’re writing.

Like, I don’t know where that conversation started. My guess is, you know, some WordCamp somewhere, and an attendee was like, did you, did anybody ever think about these problems? And then they kind of worked their way around the Make Core site or otherwise made their way around to Matias’s ears.

But yeah, I think that was a really smart choice. And you’re exactly right, collaborative editing; that can refer to the synchronous kind or the asynchronous kind, and both of those types of collaboration are equally valuable and probably equally used.

[Héctor Prieto 00:12:40]

Yes. And one important point to note here is that this editorial flows, and this collaboration is crucial to implement multilingualism going into phase four. We need to think that as soon as we have posts and pages in different languages, there are going to be requirements in terms of how to translate these pieces of content.

So this will need collaboration, all forms of collaboration.

[Josepha Haden Chomphosy 00:13:02]

Yeah, absolutely. This maybe was before your time with the project, but I was team multilingual-first for a long time. Or at least thinking that we could do the multilingual part of this work alongside the collaborative editing part of the work. I’ve spent a lot of time trying to understand what we think is going in phase three versus what probably we need to be able to do as far as having native multilingual support in the project.

And I have softened my very hard position on that. You know, we’re big fans of strong positions loosely held, strong opinions loosely held. And this was one of those moments where I had that really strong opinion that we could just do them concurrently. We can do them at the same time.

And I think it was a conversation that you and I were having when you were pointing out the complexities of translating WordPress at all, let alone being able to translate all your content as well. And it makes a lot of sense, and you’re right. I think that there are a lot of interactions, a lot of workflows that we’re gonna have to kind of refresh or redesign or rebuild before it really makes sense for us to help make that a nice streamlined option for multilingual offerings.

[Héctor Prieto 00:14:17]

Yes, absolutely. As a Spanish-speaking person, I’m super excited about having multilingual in Core, but I also understand that we need some tooling ready before implementing multilingual in Core. 

[Josepha Haden Chomphosy 00:14:29] 

There are no, there really are no easy problems left in WordPress, right? Like, we all agree on this now?

[Héctor Prieto 00:14:36]

That’s correct. And we’re creating something incrementally. If we look at the phases, they are ordered sequentially. But that doesn’t mean that when we start phase three, we are, finishing phase two completely in the same way. We have not finished phase one.

That will be like saying, when is WordPress finished, when is the development finished? So it’s an incremental project, and it’s always going to be to need refining. So it’s of course, multilingual needs to come after collaboration because we need those tools.

But that doesn’t mean we need to finish the collaboration phase or have it very advanced phase three before we can start phase four. That will be determined in the next month as we start explorations.

[Josepha Haden Chomphosy 00:15:17] 

So if you all, which I know you are, are interested in better workflows, more streamlined ways of working inside WordPress, and or interested in how we are gonna get multilingual settled in the future, this is a great time to get involved in this project and in the community. Like I said, we’ve got that post up that Matías shipped last week, which, again, if you have not read it, go read it because it’s got excellent, excellent information in there for you. 

Héctor, before we head out, is there anything that you wanna make sure that you let the listeners know, either about phase three or just about WordPress in general?

[Héctor Prieto 00:15:57]

Well, tomorrow is WordPress 6.2 release day. So happy 6.2, everybody!

[Josepha Haden Chomphosy 00:16:04]

Happy 6.2. Oh, yeah. Yeah. Which means today is the dry run; probably in three hours, we’re doing the dry run.

[Héctor Prieto 00:16:14]

Depends on when we’re listening to this, but yes.

[Josepha Haden Chomphosy 00:16:18] 

Oh, that’s a good point. Right? Not everybody listens to this the second it becomes available. Time zones. That’s right. Oh, man. Look at us being a global project and just pretending like everybody listens to this particular thing the moment that it’s available.

I apologize to everybody who’s listening to it after the release or in the middle of the release party or whatever you’re doing. Regardless, tomorrow, if you’re listening to it today, is the WordPress 6.2 release, and it’s gonna be great.

Well, Héctor, thank you so much for joining me today. I really enjoyed having you on, and thanks for letting me interview you.

[Héctor Prieto 00:16:59]

Thank you for having me. It was my pleasure to be here.

[Josepha Haden Chomphosy 00:17:10]

So that brings us now to our small list of big things, and as is frequently the case, it’s actually kind of a big list of big things. So we’re gonna hop right in here. As Héctor and I mentioned in the episode, the release WordPress 6.2 is coming out tomorrow, depending on when you’re listening to this. If you listen to it on the 27th, it comes out on the 28th of March. 

If you have a chance to drop by the release party. I would encourage you to; they’re pretty interesting just to get an idea of everything that it takes to build WordPress. It is, of course, the last few hours before a release, and so you don’t get a full scope.

But it’s always nice to see the way that everybody in the community works together, especially there in that last moment when we’re trying to package something and test it in a bunch of environments all across the world. 

[Josepha Haden Chomphosy 00:18:00] 

I love attending those. And so I encourage it. The next episode of the WordPress Briefing is going to have the release rundown.

I’ll go through the key features and highlights that finally made it into 6.2. The reason we don’t do those beforehand is just in case we have to remove anything at the last minute from a release. It doesn’t happen too often, but it does happen sometimes. And so, next episode of WP Briefing, that’s what we’ll be talking about.

The next thing on my list is a new developer blog. So there is a brand new developer blog. It was launched last Wednesday. It’s a great resource for WordPress developers to stay up to date and hear the latest in the WordPress development world. And also, we had been hearing some feedback from our developers in recent years that if you are like exploring how to extend WordPress, if you’re in that group of extenders, people who are building themes or building plugins, you’ve kind of feel like you’ve lost a place where you can have those exploratory conversations. 

[Josepha Haden Chomphosy 00:19:00] 

This is gonna be one of those places. We’ll put a link in the show notes. So far, the content that’s planned, I think, is really interesting.

Next thing on our small list, big list, of big things is WordCamp Europe’s Contributor Day.

So registration for Contributor Day is now open, and it does require a separate registration than regular attendance at WordCamp Europe. So if you are registered for WordCamp Europe, you already have your ticket for that, but you are not registered for Contributor Day, click the link in the show notes and come on down to spend a little time giving back to the WordPress Project.

And the last thing on our list today is that we have a WP20 Wapuu coloring giveaway. So put on your little party hats, and grab your crayons. The 20th anniversary Wapuu coloring giveaway is here. There is an opportunity to color in your own community-driven Wapuu and tweet it to us using #WapuuWP20 for your chance to win a sweet haul of WP20 swag items.

[Josepha Haden Chomphosy 00:20:00]

You can check out the full rules at the link in our show notes.

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 much activity happening in the WordPress development space every day, keeping up-to-date with the latest updates can be challenging. The new WordPress Developer Blog is a developer-focused resource to help you stay on top of the latest software features, tutorials, and learning materials relevant to the open source project.

This blog is the culmination of a community effort that began last year. Formed by experienced WordPress community members and developers, the editorial group has since worked on a wide range of content already available—from theme and block development tutorials to tips and tricks for leveraging WordPress in the site editing era.

A new home for developers

As a complementary resource to the WordPress documentation, the Developer Blog aims to provide a shared space to stay informed of development-related updates, keep up with ongoing discussions and ideas, and explore cutting-edge use cases.

In other words, consider it as a central hub for developers and extenders of different backgrounds and skill levels to learn with quality content from reliable sources, share knowledge, and drive WordPress development forward.

True to the open source way, the blog will likely evolve. As its editors and readers learn and create more content, it will adapt in response to the needs of community members like you.

Everyone is welcome to chime in on-topic discussions, share ideas or contribute. Learn more about how to get involved.

What about the content?

Content on the WordPress Developer Blog covers many topics, including tutorials on theme development, plugins, and block development. You can also expect posts on WordPress APIs, best practices for working with WordPress, updates on upcoming releases, and learning resources for beginners and seasoned developers.

These articles offer a good hint at what’s already in store for you:

• Demystifying home and posts templates in WordPress theme development
• Creating themes from a pattern-first mindset
• Static vs. dynamic blocks: What’s the difference?
• Creating custom block styles in WordPress themes
• What’s new for developers? (March 2023)

Sounds interesting?

Subscribe to the Developer Blog to keep up with the latest content in the WordPress development space.

Props for content and peer review @chanthaboune @rmartinezduque @mburridge @marybaum @bph @greenshady @webcommsat.

It’s the final countdown: the third (and last) scheduled release candidate (RC3) for WordPress 6.2 is ready!

The WordPress 6.2 release is scheduled for March 28, 2023—just one week away! Now is your last opportunity to test it before the general release. 

Just tuning in now? Catch up on the featured highlights, and dig into more 6.2 details in the WordPress 6.2 RC1 release announcement.

Thanks to all the Beta and RC testers who have assisted in this release. Since RC2 was released on March 14, there have been about 21 issues resolved in Trac and GitHub.

Your feedback and help in filing bug reports keep the WordPress experience stable, smooth, and delightful. It’s critical work and a great way to contribute to the project. 

How to install RC3 for testing

This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it is recommended that you test RC3 on a test server and site. 

You can test WordPress 6.2 RC3 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the RC3 version (zip).

Option 3: Use the following WP-CLI command:

wp core update --version=6.2-RC3

A shout out to plugin and theme developers

Your products are the reason WordPress does so many things for more people across the world. As you test your latest versions against RC3, make sure you update the “Tested up to” version in your plugin’s readme file to 6.2. If you find compatibility problems, please post detailed information to the support forums.

Check out the WordPress 6.2 Field Guide for more details about the major changes in this release.

Help translate WordPress

Do you speak a language other than English? Help translate WordPress into more than 100 languages. 

Keep WordPress bug-free—help with testing

Without your testing support, hitting important product milestones would be a much bigger challenge. It’s also a meaningful way to contribute to the project. If you’re new to testing, or it’s been a while, this detailed guide can help you get started. 

If you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. You can also check your issue against a list of known bugs.

Release the haiku

Wow, we’re oh so close
Test, test. Get it out the door.
Please no RC 4.

Thank you to the following contributors for collaborating on this post: @laurlittle @marybaum @audrasjb @cbringmann @webcommsat

One of the biggest benefits of our Business and Commerce plans is that you can add additional WordPress plugins to enhance the functionality of your website.

Below, we’re highlighting two of the newest additions to our plugin marketplace, now available at a hefty exclusive discount for WordPress.com users.

Create courses with Sensei Pro

Automattic, the same company behind WordPress.com, creates Sensei LMS. We’ve collaborated to bring our Learning Management System and course creation tools to WordPress.com sites in one seamless experience.

With Sensei Pro, you can create online courses with quizzes, certificates, cohorts, and detailed student reports. Lessons are edited just like WordPress posts or pages, so you will already know how it works.

You can enable the distraction-free Learning Mode to provide students with an optimized mobile-friendly learning environment that keeps your course content front and center.

Learn more about Sensei Pro.

Sell courses with WooCommerce integration

Selling courses can be a lucrative way to generate revenue for your blog or business. Sensei LMS integrates deeply with our WooCommerce suite of tools to make selling access to a course a breeze. 

You can also take advantage of WooCommerce extensions to handle coupons, memberships, subscriptions, and more. 

Learn more about WooCommerce and Sensei integration.

Publish interactive and private videos

Videos are often a big part of online courses. WordPress.com sites also come with our VideoPress service, which lets you upload videos directly to your site without dealing with a third-party tool or embed codes. Especially important for video courses, you can mark a video as “private” to ensure it won’t be downloaded or linked to, and will only be available to course students.

Even better, with Sensei’s Interactive Videos block, you can create pause points with additional content to any video. For example: 

• Add a quiz question in the middle of a course video. 
• Add a contact form to the end of a sales video.
• Show links to additional resources to a blog post video.

Add Interactive Videos to any WordPress page or post. They are not limited to courses or lessons.

Learn more about Interactive Videos.

Engage with interactive blocks

In addition to the Interactive Videos, Sensei also comes with interactive and educational content blocks, including:

• Quiz questions
• Accordions
• Image hotspots
• Flashcards
• Task lists

Using these blocks, you can craft compelling content that captivates and keeps your readers engaged. Whether writing an educational blog post or creating a sales landing page, you can add these blocks to any WordPress page or post. 

Learn more about Interactive Blocks.

Getting Sensei Pro and Sensei Blocks

For existing sites on WordPress.com, you’ll find Sensei’s plugins in the plugin marketplace. WordPress.com users receive a 30% discount on Sensei Pro automatically.

• Sensei Pro — all course creation tools and interactive blocks included. Get Sensei Pro here.
• Sensei Interactive Blocks — interactive videos, accordions, image hotspots, flashcards, and task lists. Creating courses is not needed to be able to use these blocks. Get Sensei Interactive Blocks here.

Or, create a brand new site with Sensei Pro bundled here.

We’re excited to announce that Automattic, the parent company of WordPress.com, has acquired the popular WordPress plugin ActivityPub. 

This innovative plugin brings a whole new level of social networking to your website by integrating it with the wider federated social web. When installed, the plugin allows you to easily share your content and interact with users on Mastodon and other platforms that also support the ActivityPub protocol. 

Just as Automattic aims to do with all of our products, this plugin helps to decentralize the web, break down silos, and foster a more connected online ecosystem. 

Why you should use the ActivityPub plugin

If you’re a blogger or content creator who wants to reach a wider audience, the ActivityPub plugin is perfect for you. Just as Jetpack Social — another one of our great plugins! — automatically shares content to large social networks like Twitter, Facebook, and LinkedIn, ActivityPub automatically allows anyone on a federated network to follow your blog’s posts, which will show up in their Home feed. The federated networks include:

• Mastodon
• Pleroma
• Friendica
• HubZilla
• Pixelfed
• SocialHome
• Misskey

Responses on those platforms show up in your WordPress post’s comments, allowing you to interact directly with readers across the fediverse, streamlining engagement and creating a more cohesive online presence. 

Moreover, in using ActivityPub for WordPress, you’re supporting the open source movement, promoting transparency and collaboration, and empowering users to take control of their online experience and contribute to a more diverse and inclusive internet landscape.

How to install ActivityPub for WordPress

Installing the ActivityPub plugin is a breeze, even if you’ve never added a plugin before. 

1. From your dashboard’s left-side menu, navigate to the plugin marketplace and search “ActivityPub” (all one word). Alternatively, you can click here and go directly to the plugin page. 

2. Click “Install and activate.” 

3. Once activated, you can click “Manage plugin,” which allows you to choose the type of content that will show up in fediverse feeds — if you’re not quite ready for that, you can always access it later under “Settings” → “ActivityPub.” 

At Automattic, our philosophy has always been to democratize publishing and make the web a better place. In our acquisition of ActivityPub for WordPress, we’re doing that for the social web.  

WordPress.com is an organization — like others within Automattic — that is heavily invested in Open Source and the democratization of the web. We genuinely believe that everyone should have control over their presence, their data, and even their social experiences. That’s why we’re really excited about some of the work Bluesky is doing.

What is Bluesky?

We’re building a new foundation for social networking which gives creators independence from platforms, developers the freedom to build, and users a choice in their experience.

blueskyweb.xyz

Think about all of the different pieces tied to any one of your social accounts:

• Your username – how people identify you in that platform
• Your connections/network
• The content you’ve created
• The media you’ve uploaded
• The conversations you’ve had with others
• Your connections to influencers, brands, and businesses
• Purchases within a specific platform

Now, imagine being able to bring all of that with you when you get frustrated with changes on one social network and rediscover the magic of one you had *almost* forgotten about.

This is exactly what Bluesky is trying to accomplish with its AT Protocol, and we can’t way to see how it evolves.

That’s so cool! Why is that cool?

So glad you asked!

We’re all probably familiar with the “blue checkmark of officialness” used across may social platforms. It’s essentially a way for users to identify the real accounts for famous and notable people/brands/things.

Bluesky lets you claim a domain that you own as your username/handle, and they automatically verify it by checking your domain for a simple text record. That may sound complicated, but it’s actually quite simple — especially on WordPress.com.

Think of it like any kind of certificate you might get, which often requires a signature from you as well as from some sort of official before it’s considered a verified document. It’s just like that, except that instead of collecting dust, this unlocks a digital superpower: a consistent way for anyone to find the real you (potentially) anywhere on the web.

How do I add a text record to my domain?

I’ll cover some simple steps for those of you who manage your domains here on WordPress.com. If you have domains registered elsewhere on the web you will have to check that registrar’s documentation. If you’d rather just manage it here, you can check out the steps to transfer it over.

Note: You will need an invitation to join to the private beta of Bluesky before you can set up an account and use this feature.

6 easy steps

Step 1: Navigate to the site that your domain is associated with on WordPress.com — if you only have one site you can simply go to WordPress.com.

Step 2: Use the left hand menu to navigate to Upgrades/Domains.

Step 3: Identify the domain you want to use and click on the vertical elipses on the right. Click “view settings.”

Step 4: Click on the arrow to the right of “DNS Records” to expand the information. Click on “Manage.”

Step 5: Click the “+ Add Record” button at the top of the screen.

Step 6: Change the record type from “A” to “TXT.”

Step 7: Add the Bluesky information to your record.

• Add _atproto in the “domain name (optional)” field.
• Add the Bluesky “Value” in the “Text” field.

Step 8: Click the “Add DNS record” button.

I’m always pleasantly surprised by how fast our DNS is. In this case, I was able to verify the record in the Bluesky app less than 30 seconds after I saved it on WordPress.com. Here’s what the app looks like while you’re setting up, after it’s verified, and after you officially update your handle.

If you made it this far, you’re at least a little bit interested. Let us know what piqued your interest in the comments!

Here it is: the second release candidate (RC2) for WordPress 6.2 is ready! 

WordPress 6.2 is scheduled for release on March 28, 2023—which is only two weeks away. Now is your perfect opportunity if you haven’t tried it out yet. Your feedback and help filing bug reports are what keep the WordPress experience stable, smooth, and delightful. It’s important work and a great way to contribute to the project. 

Thanks to everyone who tested the Beta and RC releases so far. Since RC1 was released on March 9, there have been about 36 issues resolved in Trac and GitHub. 

Catch up on the featured highlights, and dig into more 6.2 details, in the WordPress 6.2 RC1 release announcement.

How to install RC2 for testing

This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it is recommended that you test RC2 on a test server and site. 

You can test WordPress 6.2 RC2 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the RC2 version (zip).

Option 3: Use the following WP-CLI command:

wp core update --version=6.2-RC2

A shoutout to plugin and theme developers

Your products are the reason WordPress does so many more things for more people across the world. As you test your latest versions against RC2, make sure you update the “Tested up to” version in your plugin’s readme file to 6.2. If you find compatibility problems, please post detailed information to the support forums.

Check out the WordPress 6.2 Field Guide for more details about the major changes in this release.

Help translate WordPress

Do you speak a language other than English? Help translate WordPress into more than 100 languages. 

Join the bug hunt—test, test, test

Without your testing support, hitting important product milestones would be a much bigger challenge. It’s also a meaningful way to contribute to the project. If you’re new to testing, or it’s been a while, this detailed guide can help you get started. 

If you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. You can also check your issue against a list of known bugs.

Release the haiku

Listen, we are close
One step to final RC
Breathe, and keep going

Thank you to the following contributors for collaborating on this post: @laurlittle @marybaum @audrasjb @cbringmann

Haiku by @sereedmedia