Introducing WordPress Starter: Make Your Mark

Posted by download | Posted in Software | Posted on 25-05-2022

Every site starts with an idea. WordPress Starter is a new, beautifully pared-back plan designed to put that idea center stage. For just $5/month.

Like the WordPress Pro plan (more on that below), WordPress Starter brings you the fastest WordPress managed hosting on the planet. Unlimited site traffic. And a revolutionary price.

Make Your Mark

From building your audience with a blog. To sharing your business, design, expertise, or experiences with the world. If you’re looking to make your work visible, and make it visual, the Starter plan has you covered.

Let’s take a look at the details.

Put Your Stamp on It – with a Custom Domain

WordPress Starter unlocks custom domains – the ability to make your site’s address on the web your own.

So instead of your web address looking like this:

My-site.wordpress.com

You can put your stamp on it, and make it look like this:

My-site.com

It’s the artist’s signature that separates a Picasso from a print. 

If you want to own a piece of the web, a custom domain makes a powerful statement. And your first year of domain registration is on us.

Make It Visual. Make It Visible.

Photos and images can really set your site apart. Making it visual goes a long way to making it visible.

Starter gives you a big boost in storage – a roomy 6GB for all your photos and images. So you’ll never need to think twice about adding visual flavor to every post. And every page.


From Visible to Profitable – with Simple Payments

As your site and audience grows, WordPress Starter has everything you need to start taking payments from your site visitors.

Simple payments – included with Starter – bring you three ways to do exactly that:


Track Your Success – with Google Analytics

Finally, Starter opens up an integration with Google Analytics. If you’re ready to dive a little deeper than the default WordPress.com stats, connecting your site to GA opens the door to a world of information. 

Who’s visiting your site, who’s coming back for more, and which content is really resonating with them is the tip of the iceberg.

WordPress Starter vs. WordPress Pro

So what’s the difference between WordPress Starter and the recently announced WordPress Pro plan?

WordPress Starter

WordPress Starter unlocks custom domains and the space to make your site beautifully visual and visible. It does that with a big boost in storage for your images – from 1GB on the free plan to 6GB on Starter. It also includes simple payments to get you started selling content, donations, and subscriptions. And with its Google Analytics integration, you’ll always be able to dig deep on what’s resonating with your audience, so you can double down on your success. 

And with Starter, you’ll never have to worry about site traffic. Because traffic is unlimited.

Starter is a solid place to land if you want a great looking, blazing fast blog or website with simple payments baked in, but don’t want or need to dig deeper into design customization, interactivity, or integrations.

Starter costs just $5/month. 

WordPress Pro

WordPress Pro unlocks access to over 50,000 plugins and themes – an infinite, open library of ways to customize the features, interactivity, integration and design of your home on the web. Whatever your ambitions.

Pair that with:

  • Everything included with Starter
  • 50GB of storage for images, audio, and videos
  • A full range of ecommerce and payment tools (with even lower processing fees of just 2.9% +30¢), including the full power of WooCommerce out of the box
  • Advanced SEO, design, and social media tools
  • Beautiful premium themes
  • Google Analytics integration
  • Automated one-click backups
  • SFTP and database access
  • A free custom domain for your first year
  • Unlimited user admins
  • The ability to earn ad revenue from your site
  • Premium expert support by email and live chat 
  • And a lot more than we could comfortably fit into this paragraph. 

Which gives you the raw power to build and grow any site, store, and audience you can think of. Whether you’re starting out, or you’re a seasoned WordPress publisher.

Pro is $15/month, billed annually.

Spoiler: There’s Another Reason We Called It Starter

We called the new plan WordPress Starter because it gives you an affordable way to get a beautiful site started and shipped. But that’s not the only reason.

Coming soon, we’ll be introducing a range of add-ons that pair with Starter to give you an extra boost. It’s an a la carte way to add just what you need to Starter. And nothing you don’t. 

Stay tuned for more updates on that. In the meantime, we’d love to hear what’s important to you in the comments.

Questions? We’ve Got Answers

WordPress 6.0 “Arturo”

Posted by download | Posted in Software | Posted on 24-05-2022

WordPress 6.0 Arturo

Welcome to “Arturo”

Say hello to “Arturo” and WordPress 6.0, inspired by Grammy-winning jazz musician, Arturo O’Farrill. Known for his influence on contemporary Latin jazz, Arturo has pressed more than 15 albums spanning a body of work across five decades. 

Take some time to explore WordPress 6.0, built to help you unlock your creative aspirations and make your site-building experience more intuitive. And check out some of Arturo’s inspirational sounds that span Afro Cuban jazz, contemporary Latin jazz, and so much more.

With nearly 1,000 enhancements and bug fixes, the second major release of 2022 is here. Download it now! As of today, WordPress powers more than 42% of websites worldwide.1

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

Expanding Gutenberg into a full site editing experience in WordPress means that all of the problems the community had to address were complex and far-reaching. WordPress 6.0 is an example of the community’s commitment to tackling these tough challenges together. With thoughtful updates to the writing experience, building better block functionality, and adding a new intuitive style switcher, I’m really proud of the work that’s been done in this release to make a great site editing experience.

Josepha Haden Chomphosy, Executive Director

What’s Inside

Selecting multiple lines of text from two blocks

Enhanced Writing Experience

Writing improvements abound, whether you’re writing a brand new post or adding elements to an existing page. Explore more ways to streamline your content creation process, including:

  • Select text across multiple blocks for easier copying and pasting.
  • Type two open brackets `[[` to quickly access a list of recent posts and pages.
  • Keep existing styles when you transform some blocks from one kind to another—from a Paragraph block to a Code block, for instance.
  • Create customized buttons and any new buttons you make will retain the style customizations automatically.
  • Make tag clouds and social icons even more appealing with updated settings and controls, and a new outline style for the tag cloud.
Style variations of Twenty Twenty Two theme

Style Switching 

Block themes now include the option to contain multiple style variations. This expands the new Style system even further and enables shortcuts to switch the look and feel of your site all within a single theme. In block themes that support this feature, you can change both the available settings, like the font-weight, and the style options, like the default color palette. Change the look and feel of your site with just a few clicks.

Popover listing available templates

More Template Choices

WordPress 6.0 includes five new template options for block themes: author, date, categories, tag, and taxonomy. These additional templates provide greater flexibility for content creators. Tailor each with the tools you already know or with the following new options in this release: 

  • Featured images can be used in the cover block.
  • New featured image sizing controls make it easier to get the results you want.
  • While editing a template, at the root, or between blocks, the quick inserter shows you patterns and template parts to help you work faster and discover new layout options.
  • The query block supports filtering on multiple authors, support for custom taxonomies, and support for customizing what is shown when there are no results.
Browsing footer patterns in the quick inserter

Integrated Patterns

Patterns will now appear when you need them in even more places, like in the quick inserter or when creating a new header or footer. If you’re a block theme author, you can even register patterns from the Pattern Directory using `theme.json`, enabling you to prioritize specific patterns that are most helpful to your theme’s users.

Additional Design Tools

Design tools grow more powerful and intuitive with each release. Some highlights for 6.0 include: 

  • A new color panel design saves space, but still shows your options at a glance. 
  • New border controls offer a simpler way to set your border exactly as you like it. 
  • Transparency levels for your colors allow for even more creative color options.
  • Control gaps, margins, typography, and more on a collection of blocks, all at once, in the Group block.
  • Switch between stack, row, and group variations to position groups of blocks with more layout flexibility.
  • Use the gap support functionality in the Gallery block to create different looks – from adding spacing between all images, to removing spacing altogether.
Selecting multiple blocks in the list view

Better List View

New keyboard shortcuts enable you to select multiple blocks from the list view, modify them in bulk, and drag and drop them within the list. List View can be opened and closed easily; it comes collapsed by default and it automatically expands to the current selection whenever you select a block. 

Unlocking the block in the block toolbar

Block Locking Controls

Now you can lock your blocks. Choose to disable the option to move a block, remove a block, or both. This simplifies project handover, allowing your clients to unleash their creativity without worrying about accidentally breaking their site in the process.

Improved Performance in WordPress 6.0

This release includes several updates focused on improving the performance of WordPress. These enhancements cover a range of performance areas including improving the page and post-load speed, reducing the execution time of various query types, caching, navigation menus, and much more. The performance team working group is an important focus area of the core development team. For more information on this group’s work, please follow their work on Making WordPress with the #performance hashtag.

Enhancing WordPress 6.0 Accessibility

Accessibility is an integral part of the WordPress mission of fostering an inclusive community and supporting users of all types around the world. With this in mind, WordPress 6.0 includes more than 50 updates specifically focused on enhancing the accessibility of the platform. You can read about these updates and learn more about the accessibility initiatives that are ongoing.

Learn More About WordPress 6.0

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

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

Developers can explore the WordPress 6.0 Field Guide. It is overflowing with detailed developer notes to help you build with and extend WordPress.

Read the WordPress 6.0 Release Notes for more information on the included enhancements and issues fixed, installation information, developer notes and resources, release contributors, and the list of file changes in this release.

The WordPress 6.0 Release Squad

The group listed below tirelessly supported the release, from conception to ship date, and beyond:

Thank you to 500+ Contributors

WordPress 6.0 would not have been possible without the contributions of more than 500 people in at least 58 countries. Their asynchronous coordination to deliver hundreds of enhancements and fixes into a stable release is a testament to the power and capability of the WordPress community.

Aaron Jorbin · Aaron Robertshaw · Abdullah Ramzan · Abha Thakor · Adam Silverstein · Adam Zielinski · adi64bit · Adil Ali · agepcom · Ahmed Chaion · Aki Hamano · Akira Tachibana · Alain Schlesser · Alan Jacob Mathew · alansyue · Albert Juhé Lluveras · albertomake · Alefe Souza · Aleksandar Kostov · Alex Concha · Alex Lende · Alex Mills · Alex Stine · aliakseyenkaihar · Alkesh Miyani · Alok Shrestha · Amanda Giles · Andrea Fercia · Andrei Draganescu · Andrei Surdu · Andrew Dixon · Andrew Nacin · Andrew Ozz · Andrew Serong · Andrey "Rarst" Savchenko · André · Andy Fragen · Angelika Reisiger · Anh Tran · Ankit K Gupta · Anne McCarthy · Anoop Ranawat · Anthony Burchell · Anthony Ledesma · Anton Vlasenko · antonrinas · arcangelini · Ari Stathopoulos · Arne · Arpit G Shah · artdecotech · ArteMa · Arthur Chu · Asaquzzaman mishu · atomicjack · Aurélien Joahny · Aurooba Ahmed · Barry · Barry Ceelen · Bartosz Gadomski · Beda · Ben Dwyer · Benachi · Bernhard Reiter · BettyJJ · Bhrugesh Bavishi · binarymoon · Birgir Erlendsson (birgire) · Birgit Pauli-Haack · Blair Williams · BlogAid · Boone Gorges · Brandon DuRette · Brandon Kraft · Brian Alexander · bronsonquick · Brooke · Brooke. · Bruno Ribaric · caraya · Carlos Bravo · Carlos Garcia · Carolina Nymark · cbigler · Chad Chadbourne · Channing Ritter · charleyparkerdesign · charlyox · Chintan hingrajiya · Chloe Bringmann · Chouby · Chris Lubkert · Chris Van Patten · chriscct7 · clonemykey · Colin Stewart · conner_bw · Cory Hughart · Courtney Robertson · Crisoforo Gaspar · Dan Soschin · Daniel Bachhuber · Daniel Richards · danieldudzic · darerodz · Dat Hoang · Dave Smith · David Baumwald · David Biňovec · David Calhoun · David Gwyer · David Herrera · David Shanske · Deb Nath Utpol · Delowar Hossain · denishua · Dennis Claassen · Dennis Snell · Dhanendran · Dharmesh Patel · dhusakovic · Dilip Bheda · Dion Hulse · Dominik Schilling · donmhico · drago239 · Drew Jaynes · dromero20 · Eddy · ehtis · Eliezer Peña · Ella van Durpe · Emmanuel Hesry · Enrico Battocchi · eric3d · Erik Betshammar · espiat · Estela Rueda · etaproducto · EverPress · Fabian Kägy · Fabio Blanco · Faison · Felipe Elia · Felix Arntz · Femy Praseeth · Florian Brinkmann · Florian TIAR · FolioVision · Francesca Marano · Francisco Vera · frankei · furi3r · gadhiyaravi · Garrett Hyder · Garth Mortensen · Gary Jones · Gary Pendergast · genosseeinhorn · George Hotelling · George Mamadashvili · George Stephanis · geriux · Glen Davies · Grégory Viguier · Grant M. Kinney · Greg Ziółkowski · gregoiresailland · Guido Scialfa · gumacahin · gvgvgvijayan · Hareesh · Hasanuzzaman · Hasnain Ashfaq · Hauwa Abashiya · Haz · Helen Hou-Sandi · HelgaTheViking · Henry Wright · Hilay Trivedi · Hitendra Chopda · HristoK · Hugh Lashbrooke · Héctor Prieto · Ian Belanger · Ian Dunn · ianatkins · ianmjones · ImanGM · imokol · Isabel Brison · ishitaka · itsamoreh · Iulia Cazan · Ivan Lutrov · jadpm · Jake Spurlock · jakeparis · James Koster · Jamie · Jan Weiss · janh2 · Jarret · Jason Johnston · Jason LeMahieu (MadtownLems) · Javier Arce · Javier Prieto · Jay Trees · jazbek · Jean-Baptiste Audras · Jeff Bowen · Jeff Matson · Jeff Ong · Jeff Paul · Jenny Dupuy · Jenny Wong · Jeremy Felt · Jeremy Herve · Jeremy Yip · Jez Emery · jhned · jhnstn · jigar bhanushali · jiteshdhamaniya · Joe Dolson · Joe McGill · Joen Asmussen · Johannes Kinast · John Blackbourn · John James Jacoby · John Regan · John Watkins · Jon Brown · Jonathan Champ · Jonathan Desrosiers · Jonny Harris · Jono Alderson · Jorge · Jorge Costa · José Arcos · Josepha · Josepha Dambul · Joshua Fredrickson · Joy · jrivett · jsnajdr · juanlopez4691 · JuanMa Garrido · Juliette Reinders Folmer · Junaid Ahmed · Justin Ahinon · Justin Busa · Justin Tucker · KafleG · Kai Hao · Kajal Gohel · kapacity · Kapil Paul · Kaspars · kbatdorf · Kelly Choyce-Dwan · Kemory Grubb · Kerry Liu · Kev Provance · Kharis Sulistiyono · Kirtan Gajjar · Kjell Reigstad · KMix · Knut Sparhell · Konrad.K · Konstantin Obenland · kpegoraro · kubiq · Kukhyeon Heo · Lauren · Lena Morita · lenasterg · leskam · Lew Ayotte · linux4me2 · Lisa Schuyler · lkraav · Louis · Lovekesh Kumar · Lucas Karpiuk · Luis Felipe Zaguini · luisherranz · Luke Cavanagh · Lukman Nakib · M. van Dam · macbookandrew · Maciej · Maggie Cabrera · maguijo · Mahbub Hasan Imon · malthert · manfcarlo · Marcelo de Moraes Serpa · Marco Ciampini · Marcus Kazmierczak · Marin Atanasov · Marius L. J. · Mark Jaquith · Markus Kosmal · marv2 · Mary Baum · Mat Lipe · Mathieu · Matias Ventura · matiasbenedetto · Matt Chowning · Matt Martz · Matt Mullenweg · Matt Royal · Matt Stoney · Matt Wiebe · maur · Mauriac AZOUA · Max Kellermann · Mehedi Foysal · mgol · Michael Burridge · Michal Czaplinski · Miguel Fonseca · Mike Auteri · Mike Schroder · miken32 · Milan Dinić · Milana Cap · Minal Diwan · Mirco Babini · MMDeveloper · Mohadese Ghasemi · Mohammad Ahsan Habib · Mohammad Rockeybul Alam · MohammadJafar Khajeh · Morten Rand-Hendriksen · moushik · mqudsi · Muhammad Faizan Haidar · Mukesh Panchal · Mustaque Ahmed · Nabil · Nagesh Pai - a11n · Nalini Thakor · Nathan · Nayana Maradia · Nextend Support - Ramona · Nicholas Garofalo · Nick Ciske · Nick Diego · Nicolas Juen · nidhidhandhukiya · Nik Tsekouras · Nil · nmschaller · Noah Allen · oakesjosh · oguzkocer · Oliver Campion · Omar Alshaker · opr18 · Otshelnik-Fm · overclokk · ovidiul · Pablo Honey · Paolo L. Scala · Paragon Initiative Enterprises · Pascal Birchler · Paul Bearne · Paul Biron · Paul Ryan · Paul Von Schrottky · paulkevan · Pavan Patil · Pavlo · pbking · Pedro Mendonça · Petar Ratković · Peter Smits · Peter Westwood · Peter Wilson · petrosparaskevopoulos · Petter Walbø Johnsgård · pgpagely · Phil Johnston · Pieterjan Deneys · pikamander2 · Piotrek Boniu · Pooja Derashri · Pooja N Muchandikar · Pravin Parmar · Presskopp · presstoke · Priyank · pypwalters · r-a-y · Rachel Baker · Rafi Ahmed · Ramanan · Ramon Ahnert · Ramon James · Ravi Vaghela · ravipatel · Razvan Onofrei · Rehan Ali · Remy Perona · Riad Benguella · Rian Rietveld · Rich Tabor · Richard B. Kreckel · ricomoorman · Rob Scott · Robert Anderson · Rolf Allard van Hagen · Rolf Siebers · Rostislav Wolný · Rufus87 · Ryan Boren · Ryan Fredlund · Ryan McCue · Ryan Welcher · Sébastien SERRE · Sören Wrede · Sabbir Ahmed · Sabbir Hasan · Sami Falah · Sanjeev Aryal · santosguillamot · Sarah Norris · Sarah Snow · sarayourfriend · Sathiyamoorthy V · Sayedul Sayem · sbossarte · sclayf1 · Scott Buscemi · Scott Reilly · Scott Taylor · Segayuu · Sergey Biryukov · sheepysheep60 · Shital Marakana · Shreyas Ikhar · siddharth · Siddharth Thevaril · silb3r · Simon Blackbourn · Simon Prosser · simonhammes · Siobhan · Smit Rathod · snapfractalpop · socalchristina · Spencer Cameron-Morin · stacimc · stefanfisk · Stefano Lissa · Stefano Minoia · Stefanos Togoulidis · Stephen Bernhardt · Stephen Edgar · Stephen Harris · Steve Grunwell · Subrata Sarkar · Sumit Singh · Sumit Singh · Sumon Sarker · SunilPrajapati · sunyatasattva · Sven Wagener · Sybre Waaijer · Synchro · Takashi Kitajima · tharsheblows · Theo H · Thimal Wickremage · Thomas McMahon · Thomas Patrick Levy · Thomas Pike · Till Krüss · Tim Blankenship · Tim Nolte · Timothy Jacobs · tobifjellner (Tor-Bjorn Fjellner) · Tom · tomasztunik · Tomek · Tomoki Shimomura · Tony Tahmouch · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · Tracy · trex005 · tszming · tumas2 · twstokes · Tynan Beatty · tzipporahwitty · Uday Kokitkar · ugljanin · Ugyen Dorji · Ulrich · Utkarsh · valer1e · versusbassz · Vicente Canales · Vishal Kumar · vlad.olaru · Volodymyr Kolesnykov · vortfu · WebMan Design | Oliver Juhas · Wendy Chen · Wes Theron · Weston Ruter · whoisnegrello · wpcharged · wpmakenorg · wpsoul · WraithKenny · wslyhbb · Xidorn Quan · Yui · Yunus Ertuğrul · Zebulan Stanphill · znuff · Česlav Przywara

By release day, 76 locales had translated 90-percent or more of WordPress 6.0 into their language. Community translators continue after a release ensuring more translations are on their way. Thank you to everyone who helps to make WordPress available in 205 languages.

Many thanks to all of the community volunteers who contribute to the support forums by answering questions from WordPress users around the world.

If contributing to WordPress appeals to you, it’s easy to learn more and get involved. Discover the different teams that come together to Make WordPress and explore the product roadmap on the core development blog.

The WordPress Mission & You

WordPress is software designed for everyone, emphasizing accessibility, performance, security, and ease of use. The project believes great software should work with minimum setup, so you can focus on sharing your story, product, or services freely. The basic WordPress software is simple and predictable so you can easily get started. It also offers powerful features for growth and success.

WordPress believes in democratizing publishing and the freedoms that come with open source. Supporting this idea is a large community of people collaborating on and contributing to this project. The WordPress community is welcoming and inclusive. Our contributors’ passion drives the success of WordPress which, in turn, helps you reach your goals.

Learn more about WordPress and how you can join our community to help shape the future of the world’s most popular website platform.


A Release Haiku

Six-point-oh is here
Time to download and upgrade
Let’s pause, celebrate


According to W3Techs as of May 5, 2022.

Your Website Looks Great. So Should Your Emails.

Posted by download | Posted in Software | Posted on 19-05-2022

A Fresh New Design For Subscriber Emails

We recently rolled out some fresh, flavorful updates to the design of the emails that go out to your subscribers when you publish new posts to your site. With this new design update we worked on modernizing the out-the-box email templates that come with your WordPress.com website.

Clean, Content-First Design

Let’s take a look at the new look and feel.

Design can have a huge impact on engagement. With the new update, your subscribers will get a fresh looking email when they subscribe, receive a welcome email, and whenever you publish new posts. The new designs put your content first, and look beautiful on any device.

1. Confirmation Email

When a site visitor subscribes to your updates, the first email they’ll get will ask them to confirm their subscription. This helps make sure that the person subscribing is the owner of the email address shared. Just in case.

To put your personal stamp on that email, you can edit the message that gets sent out. Just head to: Settings → Reading → Follower settings → “Blog follow email text”, and you’re all set.

2. Welcome Email

Once your subscriber has confirmed that they’re good to go ahead, they’ll receive a Welcome Email. This one’s really important.

It turns out that the average open rate of Welcome Emails is 82% (GetResponse, 2017). So, for every 100 emails you send out, 82 people will open them. Compare that with the average email open rate of just 21%, and it’s easy to see how making a good first impression really matters.

3. New Subscriber Email

We don’t leave you out, either. 

At the same time your new subscriber gets their Welcome Email, you’ll get a New Subscriber email. So you can celebrate.

4. New Post Updates

Now your subscriber’s all set, they’ll get a fresh new email every time you add a new post to your site. That’s one more reminder that you’re out there and publishing. And one more reason to keep coming back for more.

Getting Started

Email is one of the best ways to reach your site visitors, with 4.3 Billion users around the world forecast for this year alone (Statista, 2021). 

On WordPress.com, tapping into that huge audience is as simple as adding a block to your site. Check out our support guide for the subscribe block to walk you through how to get that up and running.

Adding the block makes it a couple-of-clicks simple for your site visitors to subscribe to your content. 

And once they’ve subscribed, they’ll receive all of your latest updates – with the new, fresh design – direct to their inbox.

WordPress 6.0 Release Candidate 3 (RC3) Now Available for Testing

Posted by download | Posted in Software | Posted on 17-05-2022

WordPress 6.0 is scheduled for release next week on May 24, 2022! This RC3 release is the final opportunity for you to test and help contribute to making the 6.0 release great.

You can view changes since the RC2 release via Gutenberg and Trac.

Installing RC3

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

You can test WordPress 6.0 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 release candidate (zip).

Option 3: When using WP-CLI to upgrade from Beta 1, 2, 3, 4, RC1, or RC2 on a case-insensitive filesystem, please use the following command:

wp core update --version=6.0-RC3

Plugin and Theme Developers

All plugin and theme developers are encouraged to complete testing of their respective extensions against WordPress 6.0 RC3 and update the “Tested up to” version in their readme file to 6.0 this week. If you find compatibility problems, please be sure to post detailed information to the support forums, so these items can be investigated further prior to the final release date of May 24.

Review the WordPress 6.0 Field Guide, for more details on this release.

Review additional information on the full 6.0 release cycle.

Check the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail upcoming changes.

Translate WordPress

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

How to Help Test WordPress

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to 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. This is also where you can find a list of known bugs.


RC3, An (Almost) Final Haiku

It’s near time for six
The reward is the journey
Just one week to go


Thank you to the following contributors for collaborating on this post: @dansoschin, @webcommsat

WP Briefing: Episode 31: Open Source & Accessibility– Celebrating Global Accessibility Awareness Day With Guest Joe Devon

Posted by download | Posted in Software | Posted on 16-05-2022

In the thirty-first episode of the WordPress Briefing, GAAD Co-Founder Joe Devon joins WordPress Executive Director Josepha Haden Chomphosy to discuss Global Accessibility Awareness Day and the role of open source in accessibility.

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

Credits

References

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] 

Y’all, we’ve got an absolutely jam-packed couple of weeks in WordPress. We’ve got events happening and releases shipping and contributor days being coordinated (I almost said contributor days being contributed). That’s also what they’re doing. I’ll share some of those highlights in today’s small list of big things, but I did want to specifically call out something that’s coming up this week on Thursday (May 19, 2022), and that something is Global Accessibility Awareness Day.

The team of contributors over on the Accessibility team has participated in the Global Accessibility Awareness Day in the past. So I thought it would be interesting to hear from one of the co-founders of this particular day of awareness.

[Josepha Haden Chomphosy 00:01:27] 

All right. And with that, Joe Devin, would you like to tell us a little bit more about yourself? 

[Joe Devon 00:01:34]

Sure. So I am the co-founder of Global Accessibility Awareness Day, which is a day that goes viral every year on the third Thursday of May. We typically have the Twitter reach on the GAAD hashtag on Twitter of 200 million users, which is, I think, pretty much their active user count. We stopped counting once we hit their daily active user count.

And then, I am Chair of the GAAD Foundation, which we launched last year. And then I have a day job too, where I’m CEO and co-founder of Diamond, which is an inclusive digital agency that builds software accessibly by default.

[Josepha Haden Chomphosy 00:02:15] 

Wonderful. Well, we are so excited to have you today. I said we like it’s me and the mouse in my pocket—we in the WordPress community that’s going to listen to this. Super excited to have you today. So you mentioned GAAD, Global Accessibility Awareness Day. Last year was your 10th anniversary, which is very exciting, but like with so many good things, I hear it all started with a blog post and a blog post on WordPress, no less.

So I’d love to hear about how GAAD evolved from that, with, as I understand it, your co-founder of Jennison (Asuncion). That must be where you met him, I assume.

[Joe Devon 00:02:51]

Yes. Yes. So what happened was I started a WordPress blog called My SQL Talk. So it’s a database blog, and I just thought it was a brilliant name. I mean, My SQL Talk, like that, should be super popular.

And it probably had maybe ten people who ever looked. Um, and then my dad was getting older, and my dad was a survivor of the concentration camps, and he was a genius. He spoke ten languages. It, he was one of those people. That, when he walked into a room, he just commanded respect. You knew that there was history. I don’t know how to explain it really, but it was special when my dad walked into the room. And considering all of this that he suffered in his life, watching him get older and struggle, particularly with his banking, was very painful to see. And the bank wasn’t accessible, so I wrote this blog post proposing that we create a Global Accessibility Awareness Day.

Sometimes I get these visions, and they never turn into anything. But while I think about it, I’m like, “all right, let’s write this blog post and this can definitely work. Right?” And then you finish the blog post to hit send, and you’re like, “this is not going to work.”

But I wasn’t even smart enough to do social media on it. But fortunately, WordPress had an auto-tweet feature, and it tweeted it out, and Jennison Asuncion, my co-founder, happened to be around and not out that Saturday night. And he read the blog post, and he said, “this is a great idea. Let’s make it happen.”

And we had two busy people, but we both had a community. He had the accessibility community, and I was building a tech scene in Los Angeles. And what I discovered is if you combine a great idea with the community, great things can happen.

[Josepha Haden Chomphosy 00:04:49]

Oh man, you’re speaking my language over here, helping people find their communities, knowing that community is the thing that is the lifeblood of society.

That sounded like a tautology. It is not a tautology. You can have a society with an attempt to not have any sort of community around it, but I bet it doesn’t work very well. Well, that’s, that’s very interesting. And so you all just kind of talked through what that would look like, I assume in confidence, or that would have to take place, right? Or was it on Twitter in those days? 

[Joe Devon 00:05:24]

Oh, you could still look in the comments and see the back and forth of Jennison and a bunch of other people that got pretty involved with GAAD that are some legendary folks in there. It’s kind of mind-blowing because I dunno how, how you feel, but for me, when I used to code, uh, three months later, I’d look back at old code and be like, “oh, I suck,” you know, or write an email even and you look back on it a day later and are like “what a stupid email, how stupid am I?” You know? But I look back on that one after ten years; I was scared to look at it because I’m like, it must’ve been really bad. But you know, it kind of held up, and exactly what I wrote in there happened – to my utter shock.

[Josepha Haden Chomphosy 00:06:06]

But also, it’s kinda nice, though, to look back and be like, “oh, I used to be much dumber.”

Cause then you’re like, look how far I’ve come. I’m no longer that dumb. I’m a different kind of dumb now; good for me. I always hope to be a different kind of dumb as I go forward.

So then, okay, so that was your ten-year anniversary last year. GAAD, in general, now has been going on for 11 years, and at the time of this recording, in a couple of weeks, but then probably a week when it finally publishes, you have your next, your next round of that going.

I think it seems safe to assume that awareness of the need for accessibility has increased during that time, but we all know that the work of accessibility is ongoing. And so, I’m just curious to hear from your perspective if the awareness of the need for accessibility has generally started to permeate developer communities.

And are you seeing more developer awareness around the need for accessibility in tech in general? 

[Joe Devon 00:07:12]

Yeah. You know, it’s not enough. It’s certainly improved a lot. I keynoted a conference probably four years after GAAD started, maybe five, and I kind of assumed nobody would have heard of accessibility, and I was taken aback when I asked who had heard of it, and a good chunk of the room had. So even then, there had been a difference, and I’d say now I see accessibility mentioned a lot more in conferences and stuff. But when it comes to actually building it, there’s a tremendous amount of ignorance. There, there still needs to be a lot more awareness.

And I think partially people are a little bit scared to dip their toe because they’re scared that they’re going to be told that “no, it’s not accessible,” or that they’re going to say the wrong word or offend somebody. So I’d say that there’s some degree of trepidation, but also developers, and it’s not just developers, designers, and product people. There’s so much to learn, and it’s like, “oh God, there’s another piece that I have to learn.”

And I’m so glad that you invited me on this podcast because it’s the developers that, you know, I am a developer, not anymore, I haven’t touched code in years, but that’s where I came from. Right? This is my peach, right? Particularly WordPress folks, because I had done a fair bit of WordPress before I moved on to some other things. And, I think we have to talk about usability and understand that accessibility is so much more than how we look at disability.

And if you don’t mind, I’m going to ask you a question. How do you think the typical WordPress developer or designer would define disability?

[Josepha Haden Chomphosy 00:09:05]

in the kinds of conversations that I’ve had over the years, it frequently has to do with visual things. Because it’s just screens all day, right? And that’s a primary area where our designers and developers really have made some effort.

But my personal favorite sort of, of example, for like, when you’re looking at how to make sure that your products are accessible is, what, if you have to use your website, or you have to build your website using only one arm. Because that gives you an opportunity to kind of look at disability from a permanent standpoint.

Like if you have lost permanent use of one arm, but also gives you an opportunity to look at the temporary options for that sort of lack of mobility. Like you’re a mother with an infant, and so you have to be able to, you know, get your stuff done with one arm. And so I know that we paid a bunch of attention to screen readers and what works in not way back in 2018 and 2019 did a lot of work with. Literally zero screen. And can you still do the thing that you need to do, which was incredibly difficult. And I was really excited to see what our developers came up with around that. But I think that that is quite a bit of that discussion as we’re going through it from the beginning to the end.

[Joe Devon 00:10:27]

Yeah. I mean, that’s a great answer, and you definitely understand some of the nuances way better than I think that the average creator, digital product creator, I’m including the, you know, the product people, the designers, and the developers. 

[Josepha Haden Chomphosy 00:10:42]

We’re very fortunate to have more than just developers in WordPress.

[Joe Devon 00:10:50]

The reason I bring this up is that the WHO (World Health Organization) had to; they’re the ones that did massive research across the globe. And they had to, they had to come up with a definition, and in their definition, they needed to draw a line. Typically, I don’t remember the exact thing cause it’s a 350-page report, and I kept looking for where they defined it again.

It was a little hard to find, but essentially it’s if there’s a major disability or a disability that impacts some significant portion of your day-to-day activities. And that’s really great when you’re trying to do a report on how many disabilities there are out there; what percentage of the population has a disability?

And their figures are something like 15% of the population has a disability, which is a huge number. But at the same time, they also mentioned that 2.2 billion people have a visual impairment. And we also know that over 33% of the population is over 50, and I’m included in that population. And I can say that when you’re over 50, you know, I’ve got clouds in my eyes.

I don’t know where they came from, but they definitely make it harder to see. When I’m in a restaurant, I can’t focus on the person across from me the same way. My hearing is not the same, and anybody over 50 is going to have certain impairments and won’t see as well; color contrast issues are a big deal.

Being able to raise the font is a big deal. And I think that accessibility is connected in most people’s minds with disability. And they’ll attach that to something like being blind or being deaf or hard of hearing or having a missing limb or having some other kind of disability.

And, as a result, they’re like, “well, I don’t even know any people in that category possibly,” and as a result, they’re like, “well, how important is this?” Yes. They might feel guilty. I should do the right thing. This is the right thing to do. But honestly, like how much money should I spend on it? How much, what percentage of my time should I spend on it?

And it’s because they don’t realize that everybody has different abilities. And so, I’m starting to go away from even talking about disabilities and asking people to remember that all of us perceive things differently.

Do you remember the gold dress where they were trying to say, what color is this dress? Is it gold and white or blue and black? And it is blue and black, but to me, all I see is gold and white. And then there was Laurel or Yanny. Do you remember that?. And some people heard it, and typically older people heard it as Laurel, and I’ve, and I do this in some of my presentations. I play that, that sound. And usually, it’s Laurel for me, but sometimes it’s Yanny. Even personally, it changes.

And so, we have a totally different perception. Now think about memory. There’s a different kind of blindness. If you try and remember, let’s say a relative or a friend that is no longer. How well do you see that picture?

Because for me, it is very, very vague, but for some people, they say, and I’ve been asking people, and I’d love your answer as well. How vivid is it? And some people say, I can read the, I can see the pattern on the shirt. It’s as vivid as if I see with opening my eyes, seeing, you know, the regular in front of me, and I can even read a name tag in the memory.

And I’m like, Woah, so maybe I’m blind in a way. Right? So how do you see it? How do you remember things? 

[Josepha Haden Chomphosy 00:14:42]

Oh, I’m a, I’m a real visual person and a tactile person. And so, like if I interacted with someone, I’m very likely to be able to picture, like, recreate that mental picture pretty well in my mind. I recently, very recently, met some of my first people in that executive leadership space who were like, yeah, I don’t, I don’t visualize things.

And I was like, what are you, how do you do this work? Because like, you have to be able to do that. And they were like, no, I don’t have mental pictures. 

[Joe Devon 00:15:13]

Some people don’t have an inner dialogue. 

[Josepha Haden Chomphosy 00:15:17]

I don’t understand that either, 

[Joe Devon 00:15:19]

Me either. So accessibility studies all of these differences with respect to how you’re presenting all of this information.

And if you don’t pay attention to accessibility, you’re really just missing out. And then there’s colorblindness. If you’re creating something like slack that has an online/offline indicator, and you only use red and green for people who are colorblind, they see gray and gray. And so what I’m trying to teach the community with digital product creators is that no, you cannot ignore it.

You can ignore accessibility, but then you’re not good at your job. I mean, I don’t mean to say it in an offensive way, but you’re not good at your job if you’re unaware. If you break a rule on purpose, great. But if you don’t know the rule, it’s just a lack of craft, and you absolutely should make it a priority.

And you’re not doing it as a charity. You’re doing it because you care about your users, and you care about your craft, and you want to build things well, and it’s a necessity. And I think that this is the kind of message that our community needs to hear. 

[Josepha Haden Chomphosy 00:16:31]

I want to touch on something that you sort of brought up a bit, um, at the start of the answer there.

So you brought up the concept of usability. And in the last time that I did a podcast about accessibility, I defined accessibility as a subset of usability. Do you think that if we were to consistently draw that line for people so that it’s not just like accessibility is this thing that you should do outside of usability?

If we were to more consistently draw that line, do you think that that would help people to see and understand better that its shades of existence, usability, and accessibility?  

[Joe Devon 00:17:10]

Oh, 100%, a hundred percent. And in my company, we kind of realized that that’s exactly what we have to do. We have to see this as usability.

And I don’t, we talk about accessibility a lot, but I don’t want to. It’s part of the plumbing for us. We’ve made it part of the plumbing, and I can tell you it’s a struggle to take accessibility and make it part of an organization, even when you’re bringing it top-down, believe it or not. For our teams, particularly the designers, they are blown away by what they’re learning because they’re improving their craft.

And design is typically where there’s a struggle to get accessibility accepted because there seems to be a very strong idea of what a design should look like. And I think it’s really about the approach because UX and design it’s all about empathy for people. And when you approach it, not as, even though empathy should mean that, that, you know, do the right thing at the same time, it’s more about empathy for your user, and your user includes so much more than just people with disabilities that you haven’t run into somebody that has that disability and therefore you build it better, and it’s, it’s completely blown their mind. They love it. They love doing it. And I’m not hiring people with accessibility coming in. We’re training them to work accessibly.

[Josepha Haden Chomphosy 00:18:34]

So I think it’s interesting that you talk about empathy as part of being able to make sure that you’re creating something that’s accessible because I actually feel like empathy is. Like it’s being considered this gold standard for many, many things right now. And I think it actually is more harmful in the long run than instead making altruistic choices.

And so, I have a blog post that I will link in our show notes that will kind of help everybody see more fully my concept there. But when you rely on empathy, you do kind of have to rely on one, being able to run into all of the issues you were mentioning. You have to know people who have problems in order to know that the problems exist.

And then you also kind of have to assume that once you have willingly put yourself into the discomfort of that kind of disability, whatever, wherever it exists on that spectrum, your experience of that discomfort is the same as someone who lives with it. And I just don’t think that we can necessarily do that.

I always think that trying to do the altruistic thing, like doing your research and figuring out what it is and trying to make decisions on behalf of other people as best you can, which is a terrible thing. Still, like decisions that take into account the experiences that people are sharing with you and then going to them and saying, “does this make that experience better or worse?” is the more sustainable option from my perspective, this is specifically leadership. Still, I think it’s true for accessibility as well, and probably product design as a whole, but it’s very difficult. Like people really feel like they understand the concept of empathy right now. And I do think that sometimes that leads us down the wrong path for things.

What’s your thought on that? I think you kind of agree based on what your answer was 

[Joe Devon 00:20:33]

Oh, no, absolutely. And you know, we, you, can’t never about us without us, as the common saying, and we’ve gathered a group of a hundred people with a wide variety of disabilities for research. Whenever we do any UX and research, and sometimes we’re asked to just do research projects, we go out and ask the users.

We had some really interesting companies approach us to do innovation and accessibility, and they had strong assumptions. We looked at the assumptions and agreed with it, but we’re like, all right, they were smart. They said, “vet this with users for us, please,” because they didn’t want to gather their own group.

We vetted with users, and we’re blown away, always blown away because there are so many things you just don’t know unless you’ve lived with a particular disability. You can’t guess, and you’ve got to speak to your users and a wide variety of them.  

[Josepha Haden Chomphosy 00:21:30]

Yes, absolutely. Absolutely. What role does open source play in expanding accessibility, either in specifically the digital space or just accessibility in general?

[Joe Devon 00:21:42]

I guess if the question is, what role does it play? I would say the role it plays is it is, unfortunately, it makes accessibility worse because, for the most part open source is not very accessible. And it’s a personal passion of mine, so I’m really glad that you brought that up.

You know, it is so bizarre. You write a blog post and then it goes viral, and it goes viral every year to a degree that you can’t even believe it, that all these companies that you know are running events. Privately, publicly talking about it. And then you get all these people thanking you for what you’ve done year after year.

And then one year, you read on Twitter, The Blind Onion; I’m sure you’re familiar with The Onion, the satirical clip, there’s the Blind Onion. And they tweet out, “Now that Global Accessibility Awareness Day is over, we look forward to 364 days of global accessibility oblivion.” And that really hurt at the time, but at the same time, and I was told to ignore it, don’t worry about it, but I’m like, no, this is coming from a place of pain.

And the point of GAAD was to make a difference. It wasn’t too to just give everybody an opportunity to say, “Hey, look at what we’re doing,” and then not make a difference. So, as a result of that, I started to think about, well, where are we with this? And, and so I’ve created a state of accessibility report that through my company, we’re able to run for a few years, and it’s not, you know, the state is not great.

And I’m like, well, what can we do to change things? So, as a result of all of this, I really wanted to figure out, well, what can we do to make sure that GAAD does make a difference? And so, I came up with the idea of the GAAD pledge, which is specifically meant for open source frameworks.

And the idea of the GAAD pledge is that an open source framework, when they are ready, takes the pledge to make accessibility a core value of the framework. Now, terms of what that actually entails are different for every single project because every project is unique. We did create a bit of a framework, which had the idea of saying, okay, you’re going to, first of all, create an accessibility statement that says that this framework is going to conform to whatever, WCAG, which is Web Content Accessibility Guidelines, to whatever WCAG level is decided and is appropriate for the framework. That there’s going to be documentation for anybody that is downloading this piece of open source project and trying to implement it, that there should be guidelines for them, that all of the examples should be accessible.

It’s really important because even the frameworks that try to pay attention to accessibility. You’ll often see that people from the community will provide examples, and they’re inaccessible. And it’s really sad when you see that because so many people are just copy-pasting. That’s typically how it works, and they’re going to copy-paste something bad. So putting a statement around it, I think, would be really great.

And what we’re hoping to see is that lots and lots of big open source communities decide to take the pledge. And then it’ll sort of be table stakes that any new open source projects as well look, all of these frameworks that made it, they took the pledge and therefore we should take the pledge as well.

And so the very first year, we had React Native take the pledge, and they put a lot of effort into their accessibility. The second group to take it was Ember.js, and they always put a lot of effort into their accessibility, and they continued that effort. We’re about to announce the next one, but we’re still two weeks away.

So I can’t say anything yet, but yeah, we’re, uh, we’re hoping for a lot more uptake on, on the gap pledge because it, it affects so many people downstream. WordPress’s what percent of the web right now? 43%? So there you go. That’s so many people. 

[Josepha Haden Chomphosy 00:25:57]

So many people. Yeah, fun fact Gutenberg, our current rewriting of the editing experience in WordPress, primarily uses React. And so, I’m glad to hear that they have taken that pledge as well.

As with any good cooking, it starts with good ingredients.

[Joe Devon 00:26:12]

You said it. That was great. I wish I was a cook, though.

[Josepha Haden Chomphosy 00:26:23]

I love it. All right. Let’s what keeps you up at night when it comes to the state of accessibility? 

[Joe Devon 00:26:29]

What keeps me up at night is how to move the needle. It is such a big thing to change. And there are so many angles that you can approach this with, but at the end of the day, it’s, it’s a monster.

It’s a monster. There are so many legacy sites out there. If you look at WebAIM, they do a yearly report on the state of accessibility as well. They call it the WebAIM Million, and they’re typically seeing 97% inaccessible, 98%. It goes up and down a little bit every year. And that’s, that’s just a huge boat to move.

I think we need to at least get the newer, uh, newer websites and mobile apps to move. And what we’ve seen in our state of accessibility report is that only the very top companies seem to put in the effort to make their products accessible. There is a big push with the enterprise companies to do it.

The CEOs are starting to talk about it, but what we need is the entire culture of software development to change. Or I should even say digital product development change and to move that boat is massive. And that’s I put it in my tagline in my email like that’s my mission in life, and I hope to achieve it before I die.

So that keeps me up at night.

[Josepha Haden Chomphosy 00:27:52]

I think that would keep me up at night as well. I mean, it seems like you are really just personally mission-driven and impact-driven. Do you feel like, in the event that the work that you’ve accomplished so far is what you accomplish, you feel still like you’ve had an impact?

I feel like you have had an impact.

[Joe Devon 00:28:13]

I’m not one of those people that tries to have a legacy or like tries to focus on what my impact is and all of that. I just try and do good work. And hopefully, it just shows at the end of the day. I’m just trying to have the impact without the accolades.

[Josepha Haden Chomphosy 00:28:34]

I get it. Well, Joe, thank you so much for joining us here on this episode of WP Briefing. You have been a delight to chat with.

[Joe Devon 00:28:42]

Likewise, it’s really been a pleasure to meet you, and uh, and I appreciate the opportunity.

[Josepha Haden Chomphosy 00:28:54]

And now it’s time for our smallest of big things. As I mentioned at the start, it is packed. Number one tomorrow, May 17th, RC3. So one of the final RCs that we’re going to have for the WordPress 6.0 release, unless something goes horribly, horribly wrong, which I don’t think it will.

And then, two days after that, Global Accessibility Awareness Day, as I mentioned, will be on May 19th. So, this coming Thursday.

And then next week, we have the 6.0 release. We have the WordPress 6.0 release on May 24th.

Three days after that, WordPress turns 19 on May 27th, starting its final teenage year before we turn twenty in 2023. So that was the rapid-fire dance card for the next two weeks.

The stuff that is happening with and around WordPress for everyone to know. As a heads up, also, many people are headed to WordCamp Europe in Porto(, Portugal). The first week of June, I am going to do a live from WordCamp Europe episode. It will not be live. I’ll just record it live. And so. You know you’ll get to hear me with my hoarsest voice and maybe singing to my computer. Cause that almost always happens at these things.

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.

WordPress 6.0 Release Candidate 2 (RC2) Now Available for Testing

Posted by download | Posted in Software | Posted on 10-05-2022

The next release candidate for WordPress 6.0 is now available! 

WordPress 6.0 is scheduled for release on May 24th, 2022 – just two weeks from today.

“Release Candidate” means that this version of WordPress is ready for release! Since the WordPress ecosystem includes thousands of plugins and themes, it is important that everyone within the WordPress community check to see if anything was missed along the way. That means the project would love your help.

Thank you to everyone who has contributed towards testing and logging issues to help make WordPress 6.0 stable (and awesome). WordPress still needs your help testing, especially theme and plugin developers.

Since the RC1 release on May 3rd, 2022, there have been approximately 40 issues resolved in Gutenberg and Trac.

Installing RC2

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

You can test WordPress 6.0 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 3: When using WP-CLI to upgrade from Beta 1, 2, 3, 4, or RC1 on a case-insensitive filesystem, please use the following command:
    wp core update --version=6.0-RC2

Additional information on the full 6.0 release cycle is available here.

Check the Make WordPress Core blog for 6.0-related developer notes in the coming weeks, which will detail all upcoming changes.

Plugin and Theme Developers

All plugin and theme developers should test their respective extensions against WordPress 6.0 RC2 and update the “Tested up to” version in their readme file to 6.0. If you find compatibility problems, please be sure to post detailed information to the support forums so that these items can be investigated further prior to the final release date of May 24th.

Review the WordPress 6.0 Field Guide for more details on this release.

Translate WordPress

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

How to Help Test WordPress

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to 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. This is also where you can find a list of known bugs.


An RC2 Haiku for You

Anticipation
Sprinting toward G/A now
Please — test, translate — thanks!


Thank you to the following contributors for collaborating on this post: @dansoschin, @priethor.  

The Month in WordPress – April 2022

Posted by download | Posted in Software | Posted on 05-05-2022

This past month saw a lot of preparation work for WordPress 6.0, due to release on 24 May 2022. This major release brings exciting improvements – read on to find out more about the latest happenings in the WordPress project.


WordPress 6.0 Release Candidate 1

The first release candidate (RC1) for WordPress 6.0 is now available for download. Help improve the project by testing and translating this version to non-English languages. Check out the RC1 release post to learn what’s new and how to contribute. For a more in-depth look at the upcoming changes, you can refer to the WordPress 6.0 Field Guide.

WordPress 6.0 is packed with all kinds of improvements for everyone. It brings new blocks, accessibility enhancements, refined design tools, the ability to switch theme styles easily, multi-block partial text selection, and a new block locking interface, to name a few of its highlights.

Gutenberg releases: Versions 13.0 and 13.1 are here

  • Gutenberg 13.0 shipped on April 14, 2022, and introduced the final updates that will be part of WordPress 6.0. These include an improved editor experience (with the ability to select text across blocks), better responsive blocks, and prominently exposed block patterns.
  • Gutenberg 13.1 landed on April 27, 2022. This version adds border support to the Columns block and accessibility and Comment block improvements.

Team updates: Updated guidelines for in-person events, redesign of the Gutenberg page, and more

  • The Community team announced updated Covid-19 guidelines for official WordPress events.
  • The redesign of the Gutenberg landing page on WordPress.org is nearing completion.
  • #WPDiversity announced new meeting times for Asia-Pacific (APAC) areas. You can express your interest in this post.
  • The Training team plans to migrate the Contributor Training materials to Learn WordPress. This move will help consolidate all the community-based training content in one place.
  • All learners on Learn WordPress can now enjoy using a live WordPress demo site as they go through courses on the site.
  • Read the latest edition of the Meetup Organizer Newsletter.
  • Everyone is welcome and encouraged to join the new Photo Directory team meetings. They are held on the first Friday of every month at 14:00 UTC in the #photos channel of the Make WordPress Slack.
  • The Performance team published a follow-up post with the next steps on the WebP proposal.
  • Check out the projects the Design team contributed to over the past couple of weeks.
  • Official Featured and Beta plugins now limit ownership and committer changes.
  • The April 2022 edition of the Polyglots Monthly Newsletter was published.
  • The latest edition of People of WordPress features Meher Bala, a frontend web developer and community builder from India.
  • The #props channel of the Make WordPress Slack is now connected to the WordPress.org profile activity! This way when you give props, it will be included on your WordPress.org profile and the profile of those you mention. This change is part of a larger project that will help credit more non-code contributions.

Open feedback/testing calls

  • Following this proposal for a WordPress Project Contributor Handbook, Executive Director Josepha Haden opened a round of discussions to share feedback on the various handbook sections.
  • Version 19.8 of WordPress for Android and iOS is available for testing.
  • Join the 14th testing call of the Full Site Editing (FSE) Outreach program – “Rallying Recipe Reviewers.” This call focuses on testing blocks that help recipe authors make their recipe blogs more interactive. Leave your feedback by May 18, 2022.

Get ready for WordCamp Europe in Porto

  • We are four weeks away from WordCamp Europe. After being postponed twice due to the pandemic, the WordPress event is taking place in Porto, Portugal, on 2-4 June 2022. Check out the schedule and get your tickets if you haven’t yet!
  • WordCamp US announced a new program to support underrepresented speakers.
  • WordCamp Irun (Spain) is happening this month on May 21 and 22, 2022.

Have a story that we could include in the next issue of The Month in WordPress? Let us know by filling out this form.

The following folks contributed to this Month in WordPress: @rmartinezduque, @cbringmann, @dansoschin.

New: Free SEO Course

Posted by download | Posted in Software | Posted on 04-05-2022

A successful website is a labor of love. I know, first-hand, how much work goes into getting a site launched. But the effort can’t stop there, because for most people, the whole point of publishing a website is to get people to see it. 

If your goal is like mine and you want to see a gradual increase in your site’s visitor traffic, a solid marketing strategy is needed. And no strategy would be complete without good SEO practices. SEO stands for search engine optimization, and as technology is always changing, optimizing your site for search engines, like Google, is a continual undertaking.

This is why we launched our FREE course, Intro to Search Engine Optimization (SEO).

The field of search engine optimization is complex and the sheer volume of information can be daunting and overwhelming for even the most fluent internet surfers. SEO has come a long way since Google first launched in 1996 and many practices that were considered strategic back then are now viewed as black hat tactics, which can penalize your site. 

Luckily, we’ve launched our latest course to provide a straightforward and easy-to-follow introduction to the world of SEO, which will give you a solid foundation of what you can do to ensure people have the best chance to find your content when they search online. 

In this course you will:

  • learn what SEO is and why it’s important
  • understand how to find and apply keywords
  • equip yourself to create stand-out content that gets results

By registering, you’ll get access to our course platform, where you can work through each lesson at your own pace and take your time to really put that knowledge into practice with your existing and future content.

WordPress 6.0 Release Candidate 1

Posted by download | Posted in Software | Posted on 03-05-2022

The first release candidate (RC1) for WordPress 6.0 is now available!

This is an important milestone on the 6.0 release cycle journey. “Release Candidate” means that this version of WordPress is ready for release! Before the official release date, time is set aside for the community to perform final reviews and help test. Since the WordPress ecosystem includes thousands of plugins and themes, it is important that everyone within the WordPress community check to see if anything was missed along the way. That means the project would love your help.

WordPress 6.0 is planned for official release on May 24th, 2022, three weeks from today. 

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

You can test WordPress 6.0 RC1 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 release candidate version here (zip).

Option 3: When using WP-CLI to upgrade from Beta 1, 2, 3, or 4, on a case-insensitive filesystem, please use the following command sequence:

Command One:
wp core update --version=6.0-RC1

Command Two:
wp core update --version=6.0-RC1 --force

Additional information on the full 6.0 release cycle is available here.

Check the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail all upcoming changes.

What’s in WordPress 6.0 RC1?

Since Beta 4, various items have been addressed, including (but not limited to): 

  • Backport updates of Comment blocks tests (#55643)
  • Backport a bugfix of Comment Template block pagination (#55658)
  • Editor: Backport bug fixes for WordPress 6.0 from Gutenberg (#55567)

WordPress 6.0 is the second major release for 2022, following 5.9 which became generally available in January. This release includes nearly 1,000 fixes and enhancements spanning most areas of the WordPress platform. Some key highlights within the content creation and site-building feature sets include:

  • Style Switching: switch up the look and feel of your site, all in one block theme. No need to change themes!
  • More template options: use blocks to edit five more templates (author, date, categories, tag, and taxonomy).
  • Multi-select: Easily select text across multiple blocks. Edit to your liking.
  • Retain Styles: Keep your custom styles in place, whether transforming between blocks or creating new buttons. 
  • More patterns in more places: the Quick Inserter surfaces patterns that might work well for the condition you’re in, baking in relevant patterns for template parts and pages you’re working on. 
  • List View improvements: New keyboard shortcuts (shift + click) let you select multiple blocks to modify in bulk (reposition, delete, etc.), see your content at a glance with a collapsed by default view, and more.
  • Refined design tools: Explore a new color panel, transparency options, more group block variations to create new layout options (Stack, Row), the ability to set your featured image in a Cover block, control the exact size of your featured image, gap support for the Gallery block, and more.
  • New blocks: Various Post Comments, Read More, No Results in Query Loop, Post Author Biography, Avatar blocks. 
  • Block Locking: Choose to disable the option to remove a block, move it, or both, right in the editor. 
  • Export block themes: Explore the improved block theme export tool, as WordPress heads closer to codeless visual block theme building.

Plugin and Theme Developers

All plugin and theme developers should test their respective extensions against WordPress 6.0 RC1 and update the “Tested up to” version in their readme file to 6.0. If you find compatibility problems, please be sure to post detailed information to the support forums, so these items can be investigated further prior to the final release date of May 24th.

Review the WordPress 6.0 Field Guide, for more details on what’s contained in this release.

Translate WordPress

Do you speak a language other than English? Help translate WordPress into more than 100 languages. This release also marks the hard string freeze point of the 6.0 release cycle.

How to Help Test WordPress

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to 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. This is also where you can find a list of known bugs.


Haiku Fun for RC 1

Release candidate 
Our journey nearly done
Get ready, WordPress


Thank you to the following contributors for collaborating on this post: @dansoschin, @webcommsat, and @annezazu.

WordPress 6.0 Beta 4

Posted by download | Posted in Software | Posted on 02-05-2022

WordPress 6.0 Beta 4 is now available for testing!

Beta 4 was not part of the originally published development cycle. It is aimed at providing an opportunity for testing some specific issues that were resolved since Beta 3. WordPress will continue with the regularly scheduled release milestones on May 3rd, 2022, with the RC1 release.

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

You can test WordPress 6.0 Beta 4 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 beta version here (zip).

Option 3: Use WP-CLI to test: wp core update –version=6.0-beta4.
Do not use this option if your filesystem is case-insensitive.

The current target for the final 6.0 release is May 24, 2022, which is in less than a month! 

Additional information on the full 6.0 release cycle is available.

Check the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail all upcoming changes.

Explore What’s in Beta 4

Since Beta 4, various items have been addressed, including (but not limited to): 

  • Update post content placeholder (#40177)
  • Comments block: Fix glitches found while backporting (#40628)
  • Show add pattern label when patterns are being prioritised (#40598)
  • Fix regression with featured images in latest posts (#40662)
  • Navigation Link: Avoid unnecessary re-renders (#40696)
  • Navigation: Improve selector performance (#40700)
  • Comments Title: Count toggle working in ‘Singular’ editing mode (#40728)
  • [Writing Flow]: Try to fix multi-selection with shift+click (#40687)
  • Fix alignment issue with comment author name (#40610)
  • Comment Content: Show moderation message (#40612)
  • Display paragraph breaks in comment contents block (#40667)
  • Fix style comment awaiting moderation indentation (#40681)
  • Fix: Page patterns don’t show when only one pattern is available (#40707)
  • Update the placeholder for post excerpt (#40178)
  • REST API: Fix regression in the Pattern Directory endpoint. (#55617)
  • REST API: Fix the scheme for the Block Directory search endpoint. (#53621)
  • Show comments previews in the Comment Query Loop. (#55634)
  • Avoid DB error in comment meta queries. (#55218)

How to Help

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to 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. This is also where you can find a list of known bugs.


Another Haiku, Just for You

Beta four, surprise!
Iterating all day long
Time to share and test


Thank you to the following contributors for collaborating on this post:
@dansoschin, @annezazu, and @costdev