WordPress Planet

May 28, 2022

Gutenberg Times: Gutenberg Changelog #67 Gutenberg 13.2 and 13.3, WordPress 6.0 and more

Birgit Pauli-Haack and special guest, Grzegorz Ziolkowski talk about WordPress 6.0 release, Gutenberg 13.2 and 13.3 and interesting discussions happing on the Gutenberg Repo

Show Notes / Transcript

Show Notes

WordPress 6.0

Community Contributions

What’s Released

Gutenberg 13.2

Gutenberg 13.3

What’s being worked on or discussed

Stay in Touch

Transcript

The transcript for this episode is in the works….

by Gutenberg Changelog at May 28, 2022 08:45 PM under Gutenberg

BuddyPress: BP Rewrites 1.2.0 maintenance release

Immediately available is BP Rewrites 1.2.0. This maintenance release fixes two bugs. For details on the changes, please read the 1.2.0 release notes.

Update to BP Rewrites 1.2.0 today in your WordPress Dashboard, or by downloading from the WordPress.org plugin repository.

Many thanks to 1.2.0 contributors 

shawfactor & imath.

by Mathieu Viet at May 28, 2022 05:33 AM under rewrites

Post Status: What’s a WordPress “Developer?”

It’s a good time to celebrate growth, maturity — and longevity. This is our 500th issue. WordPress is 19! And the 6.0 release is just a few days old, with new and old hands contributing from all over the world. Many are "developers" of some kind. Those who are showing up every day to make the project work and to make a living in WordPress are the professionals. Here's to them!

by Dan Knauss at May 28, 2022 12:35 AM under The Post Status Team Blog

May 27, 2022

WPTavern: WordPress Turns 19

Today marks 19 years since 19-year old Matt Mullenweg partnered with Mike Little to release the first version of WordPress based on the b2/cafelog software. The blog where he shared his thoughts on life and tech was starting to get more traffic and he wanted to ensure its future after the b2/cafelog’s main developer disappeared.

Mullenweg had the vision for what WordPress should be, even before it had a name. It centered on extensibility, a hallmark feature that has made the platform as popular as it is today:

What should it do? Well, it would be nice to have the flexibility of MovableType, the parsing of TextPattern, the hackability of b2, and the ease of setup of Blogger.

Matt Mullenweg – The Blogging Software Dilemma, January 24, 2003

Although Textpattern, the interesting new publishing tool at the time, had everything Mullenweg might want in a blogging tool, he wasn’t sure about its licensing at the time. He decided to fork b2/cafelog, which lives on today in a different form as WordPress, thanks to its GPL licensing. Mike Little joined the effort and the rest is history.

The highlight of this year’s anniversary celebrations is the wp19.day website created by David Bisset and his daughter Olivia Bisset, who also managed the project. WordPress users and contributors from all over the world left their heartfelt greetings to celebrate the occasion. Reading through, it’s easy to get a sense of the tremendous good WordPress has done for the world, giving so many a voice, a livelihood, and a chance to live their dreams.

The wp19.day website also featured video submissions from WordPress enthusiasts. Although many first came for the software, the common thread among those who have stayed is the value of the community that has grown up around the project and the leadership it has cultivated. WordCamp and meetup organizer Joe Simpson said WordPress empowered him to take a leadership role in his local community.

“Our community here is nurturing – it’s a family,” Simpson said. “I’m excited to see where we go from here. Happy birthday, WordPress.”

Matt Mullenweg also joined in the fun of celebrating the milestone by contributing his own greeting to the wp19.day project. In his video submission, he said it’s very rare for a 19-year-old software project and its community to not just still be surviving but actually thriving and “doing better than ever.” He thanked contributors of all kinds who have helped people find their way with WordPress.

Matt Mullenweg on WordPress’ 19th Birthday – video source: wp19.day

“That is a testament to every single person who has ever told a friend about WordPress, participated on the forums, had a translation, contributed code,” Mullenweg said. “Anything that’s been part of the WordPress ecosystem is part of why WordPress is transforming the web and making it into a place that is more open, more inclusive, more democratic, and a place that we want our future generations to grow up in.”

by Sarah Gooding at May 27, 2022 10:12 PM under WordPress

Post Status: WooCommerce Function of the Week: add_fee

Before we dive in this week's function, please note that it's usually against any payment provider's Terms of Service (like PayPal's) to add fees to a transaction based on the customer's chosen payment gateway, so please make sure to use “cart fees” in a legal way. You got it — in this issue we'll study...

by Rodolfo Melogli at May 27, 2022 09:29 PM under WooCommerce

WPTavern: Gutenberg 13.3 Introduces Experimental Table of Contents Block

Gutenberg 13.3 was released this week with support for an experimental new Table of Contents block. It is perfect for longform content that is organized by multiple headings within the document. The block automatically detects Heading blocks within the content and will display them with anchor links that jump to each section.

Table of Contents block – video credit: Gutenberg 13.3 release post

Users may select the block without knowing how it works with headings. If the post or page doesn’t contain any headings, the block inserts a message prompting users to start adding Heading blocks in order to display a Table of Contents.

For sites that have registered custom taxonomies, Gutenberg’s Post Terms Block now automatically generates a block variation for each term. That means users can select a block to display all the terms associated with that custom taxonomy.

Other notable additions in 13.3 include the following:

  • Query block now supports a “parent” filter that will display content of children from the defined parent
  • Heading block now supports Font Family controls
  • Save Block List default view preference – allowes users to set a preference for having the Blost Lick view open or closed by default
  • New transforms between the Cover and Media & Text blocks

The latest release also brings dozens of enhancements and bug fixes to preferences, border controls, error messages, tooling, accessiblity, and performance. Check out the release post for the full list of changes.

by Sarah Gooding at May 27, 2022 06:21 PM under News

Matt: WordPress 19

Today is the 19th anniversary since WordPress’ first release, which is especially exciting for a number of reasons:

  1. The community put together an awesome site celebrating the occasion at wp19.day.
  2. We just had an awesome 6.0 “Arturo” release.
  3. Next week June 2-4 WordCamp Europe returns in-person in Porto, Portugal, and I’ll be there and so excited to connect with the community! Tickets are still available.
  4. Nineteen seems like an in-between number, but actually it’s very salient for me because now WordPress is the same age I was when the first release came out.
  5. Which means I’ve now been working on WordPress half my life!

Cheers and here’s to many more years together. 🥂

by Matt at May 27, 2022 06:14 PM under Asides

Post Status: Post Status Notes #500

By Dan Knauss and David Bisset 🗓 May 27, 2022

It's the 500th issue of Post Status Notes and the Post Status newsletter coinciding with WordPress's 6.0 release and its 19th anniversary! 🎂


WordPress 6.0 Released

WordPress 6.0 “Arturo” was released on schedule (May 24th) with many new features and enhancements related to full site editing.

  • Gutenberg 13.3 was released yesterday.
  • Check out Anne McCarthy‘s post on the latest core editor improvements to container blocks and block locking. Anne shows off some new features to explore with rows, stacks, and groups.
  • Anne also has a recap (video and written highlights) of yesterday's hallway hangout on Full Site Editing topics.

The Global Community of Contributors

Jean-Baptiste Audras offers some interesting stats for the 6.0 release as he's done with six previous releases — 5.35.45.55.65.7, not 5.8, and 5.9) so we can see compare them. Some highlights:

  • 519 people (~25% were first-time contributors) from at least 53 countries and 134 identified companies contributed.
  • The United States leads in contributions followed by Russia, thanks to Sergey, who had the highest number of individual contributions to 6.0. Then comes Jean-Baptiste himself in France and George Mamadashvili in Georgia.
  • Automattic (with its 70 contributors) had the most contributions, followed by Yoast, Whodunit (France), and GoDaddy.

It's interesting to see how national populations, the number of their contributors, and their total contributions are independent variables that can vary widely. Automattic‘s Jorge Filipe Costa from Portugal is in the top 20 by contributions, and Portugal ranks high despite having only three contributors in all.

Some standout individuals, like Sergey, George, Jean-Baptiste, and Jorge do an enormous amount for the project, and there are quite a few of them! It is ultimately a community effort.


WordPress's Last Year as a Teenager

Nyasha Green interviewed Olivia Bisset about her work on wp19.day. Olivia is also an intern here at Post Status. (An enthusiastic WordPresser, coder, WordCamp speaker and volunteer, Olivia is slightly younger than WordPress itself.)

Newly posted to WP19.day: brief video greetings from Matt Mullenweg, Lindsey and Cory Miller, Syed Balkhi, Vito Peleg, much of the team at Yoast, and many others.


WordCamp Updates

Hari Shanker R passed along the news that regional WordCamps will not need to go through a proposal process anymore — they can directly apply to organize a camp for their region using the WordCamp application form. From now on, “WordCamp Central will evaluate the health of local communities when assessing a regional WordCamp application.”


Bob Dunn has some nice, bite-sized tips on building WordPress sites from some of the speakers at the upcoming WordCamp Europe 2022.


Giving Back and Looking Forward

Thomas Fanchin at Weglot has a great post about his company enthusiastically embracing Five for the Future and becoming a WordPress Global Sponsor. He notes how much there is to look forward to in events, worldwide, in 2022.

Weglot has been sponsoring Juan Hernando, a WCEU organizer (among other things) and now Pedro Mendonça on the core Polyglot team.


What Contributions Count for Five for the Future?

Josepha Haden Chomphosy has taken a stab at defining activities that can be considered contributions to Five For the Future, and she is looking for feedback.

Josepha says valid 5ftF contributions should clearly benefit the WordPress project and not an individual person or company. Contributions related to creating or supporting (third-party) WordPress themes, plugins, or blocks “are critical to extending the reach and utility of the WordPress project,” but they are also in a “grey area.” Generally they shouldn't be associated with the Five For the Future mission or count toward corporate commitments to the program.

In the comments, Adam Warner asked if completely free code like Contact Form 7 might be worth counting, and Brian Gardner asked about contributions to the Pattern Directory with Courtney Robertson chiming in about CC0 images contributed to Openverse.


Managed WordPress(.com) Hosting Starter Plan

WordPress.com has launched a new plan called “WordPress Starter for $5/month. It seems to be a the “in-between” option some were looking for earlier when the “Pro” level was first announced. The “Starter” level includes custom domains, additional storage, simple payment processing, and Google Analytics to the free option.

Notably, WordPress.com is increasingly being marketed as a web host for “managed WordPress hosting,” and it can claim to be the fastest on the planet.


WordPress and Sustainability

Joost De Valk explains how optimizing search engine crawling can help save energy — and therefore the environment. Remember that search engines will crawl almost any URL they can find in your page source.

Tom Greenwood shares some tips on reducing waste in web design. Even if you just stop autoplaying videos, that's a start.

Over at the Matt Report, Hanna Smith asks, “Can WordPress save the planet?

It's good to see these economic and ecological concerns emerging more in the WordPress space. If you'd like to take a hard look at the situation, try starting with the Stockholm Resilience Centre‘s Planetary Boundaries Framework (CC BY 4.0).

One of Bill Gates‘ favorite authors, Vaclav Smil, is also worth a weekend deep dive. Smil is a Czech-Canadian scientist and policy analyst on the Faculty of Environment at the University of Manitoba. His new book, How The World Really Works, was summarized nicely in the latest issue of Sentiers by Patrick Tanguay.


Opportunities for Lean WordPress and WooCommerce Solutions?

Rob Howard asks what growth opportunities WooCommerce might see ahead as Shopify suffers a post-pandemic decline in its stock price and market share. Shopify will likely stabilize as pressure from Wix, Squarespace, and WooCommerce increases. Some would say — unfavorably — this is an “Apple-like” tactic. But Rob's right — there's an opportunity here for WordPress and Woo:

“Let Shopify, Squarespace and Wix duke it out for the low-end market, and do everything you can to help WooCommerce corner the market for higher-end, highly custom e-commerce solutions.”

There's also a good opportunity for a “build a store on a mobile device quickly” experience now.

Check out the new Fruits platform — it seems to do just that.

What if something similar existed based on a trimmed-down WordPress install? Want a full store with custom features? Click a button, and it becomes the full WordPress + Woo experience ready for customization.

Christina Warren and Dan Knauss have similar thoughts about a Substack or Ghost-like distribution of WordPress.


WordPress Job Titles and Skills – Where Do We Stand? (2015-22)

This recent Woo DevChat, with Zach Stepek, Till Krüss, and Carl Alexander is a deep, funny, and much more thoughtful (and generously, even inclusive) take on the age-old question “What is a WordPress Developer?”

Ten years ago this topic was reliable clickbait for much wp-drama because it was often expressed as “who counts” or “who deserves to be called a Developer?” Will the real developers please stand up? Perspectives have changed and matured a lot.

Maybe today there is such a thing as a “No-Code Developer…”

Zach, Till, and Carl's conversation is reminiscent of this 2015 post by Mario Peshev and the comment discussion it provoked. It's worth a read still, and so are the comments.

Maybe that's where Bob locked onto Site/WordPress/Woo “Builder.” I knew “Integrator” and “Customizer” would never be widely used.

2015 is probably about when (if not exactly where) a lot of us locked onto the inclusive but specific term, “WordPress Professional” that Jenny Beaumont introduced in the discussion over Mario's post.

“WordPress Professional” slid into Post Status's self-understanding too and grew to become quite central to our idea of membership.


Do you enjoy our weekly notes?

Get them and more in Post Status' Week in Review. We gather WordPress and WooCommerce news along with significant writing, videos, and podcast episodes from the WordPress community and beyond. Don't miss the latest updates from the people making WordPress in our This Week at WordPress.org summaries. It's all in our newsletter! 💌

by David Bisset at May 27, 2022 04:30 PM under The Week in Review

Do The Woo Community: WooBits: Happy Birthday WordPress_Community

WordPress turns 19 today. And as I did my first draft of this podcast, I found myself redoing it. I have it all wrong.

>> The post WooBits: Happy Birthday WordPress_Community appeared first on Do the Woo - a WooCommerce Builder Community .

by BobWP at May 27, 2022 09:09 AM under WooBits

Post Status: WordPress Podcast and Video Picks for the Week of May 22

Catch up on the gold at Wordsesh! Mark Ashton on the success of UiPress. Hanna Smith on web sustainability. Michelle and Allie on sponsored events. Mark Root-Wiley on CSS Standards for WordPress. Takis and Taeke on organizing WCEU.

My Podcast Picks 🎙

My Video Picks 📺

  • WordSesh: Learn the path From Agency Owner to Plugin Shop from Lesley Sim, Aurooba Ahmed describes how to Hack the Block Editor for Faster Content Creation, Vikas Singhal has 5 Easy Ways to Fix your WordPress Workflow, and Leonardo Losoviz asks, Will WordPress be Better with the Block Protocol? Keynotes include Anil Gupta explaining How Big Enterprises Use WordPress for Publishing, the 10up team on Rebuilding WhiteHouse.gov in Six Weeks, and Susan Enners, Matthew Haines-Young, and Wisdom HamboluI on Building and Defending a Free Press. It's all there — and more!

Get our weekly WordPress community news digest — Post Status' Week in Review — also available in our newsletter. 💌

And don't miss the latest updates from the people making WordPress. We've got you covered with This Week at WordPress.org. ⚙

by David Bisset at May 27, 2022 07:38 AM under The Week in Review

May 26, 2022

WPTavern: Community Team Removes Red Tape From Regional WordCamp Applications

photo credit: World Maps

After a lengthy discussion, the Community Team has decided to make it easier for organizers to apply for regional in-person WordCamps. These are events that pull in a community from a geographical area larger than one city or metro area.

In past years, WordPress Community Support (WCS) saddled regional events with numerous additional requirements beyond regular WordCamps, such as preparing a proposal and a minimum of three cities in the region hosting local events, with at least one having hosted a WordCamp.

“The Community Team has decided to simplify the guidelines for regional in-person WordCamps,” Automattic-sponsored WordPress.org community manager Hari Shanker said.

“Moving forward, regional WordCamps will not need to go through additional steps (such as writing a proposal), and can directly apply to organize a camp for their region using the regular WordCamp application form.” 

Shanker asummarized community feedback that influenced the decision to ease up on the requirements and move towards using common sense as guide for hosting regional WordCamps:

  • Regional WordCamps could be beneficial in restarting events in a region in a post-pandemic situation. It would be a great way to revive the community.
  • WordCamps should be evaluated on a case-by-case basis, with conditions such as the region, geographic size, country, etc.
  • Successful Country-based WordCamps were held in the past, and the community team should not police event organizers based on the region. The event organizing process could be simplified.
  • City-based events could be difficult to organize because it’s difficult for a small group to organize a big event. It also causes repetition and a lack of repeat value for sponsors. Regional WordCamps might be a great way to solve this problem.

Shanker emphasized that while guidelines are being simplified, it’s imperative that local meetups are presesrved when regional WordCamps are organized.

“Local communities offer more accessible ways to connect over WordPress, and more supportive pathways to participation in larger, more complex events,” he said.

Organizers who are interested in starting up regional WordCamps are encouraged to continue developing local leadership and will be required to impose a strict, two-year term limit on lead organizers.

More simplified guidelines for these events is particularly beneficial in Europe where many smaller countries find that regional WordCamps have a strong unifying effect for their WordPress communities.

“There is a reason that a ‘small country’ like The Netherlands is now in the top of WordPress contributors and companies,” WordCamp organizer Dave Loodts commented on the previous discussion. “It all started in the lap of all the previous WordCamp The Netherlands. Never underestimate the power of these kinds of events.”

Shanker is requesting feedback on the proposal, particularly on what metrics should be in place to determine the health of regional communities. The proposed change has already started receciving positive feedback.

“Switzerland is like the Atlanta metropolitan area in term of population (8 millions vs 6 millions = ‘similar’) and about 10 meetup groups,”  Geneva meetup organizer and WordCamp Switzerland co-organizer Patricia BT commented.

“Since we had to rename Switzerland to city name after 2015, we knew it was unrealistic to have more than one per year in the country (like if you asked people of Atlanta to have one WordCamp per meetup group) so we moved it from city to city year after year, which was awesome to onboard new organisers, but still missing a ‘united’ event.

“It’s really cool that we can now go forward with WC Switzerland next year, as I feel we had lost a bit of the ‘Swiss community momentum.’ We will recreate that feeling again next year.”

by Sarah Gooding at May 26, 2022 06:55 PM under wordcamp

Post Status: Post Status Upgrade: Group Facilitation Skills

Learn new skills and build your knowledge to enhance your career in WordPress! Post Status Upgrade is an ongoing series of live workshops centered around a particular skill or learning activity.

Post Status' motto — Give, Grow, Together — is more than just a phrase we repeat a lot. We live our motto. This training will give you key insights into how to facilitate group conversations with an eye to giving and growing together.

This is a training workshop for anyone who wants to be a facilitator or a participant in the small groups that Post Status will be rolling out soon for its members.

Group Facilitation Skills with Corey Wilks.
Corey Wilks

Corey Wilks is a Licensed Clinical Psychologist and Executive Coach. His mission is to help founders, creators, and entrepreneurs build an Intentional Life using evidence-based psychology.

“How do I define an Intentional Life? Spending your most precious resource—time—doing meaningful, purpose-driven work that fulfills you. It’s about clarifying your Core Value, embracing your authenticity, and reaching your potential by building your life, and your business, around what resonates with you on a fundamental level.”

Dr. Corey Wilks
StellarWP

StellarWP is a collective of WordPress innovators empowering business owners and creators with plugins and tools to help them thrive. We build great plugins, but we don’t stop there; we continually challenge ourselves to keep innovating and improving. Our solutions include the most trusted names in WordPress, with more than 2.5 million installs. Since 2021, we’ve grown to encompass seven brands and dozens of plugins. StellarWP is part of the Liquid Web family of brands.

by David Bisset at May 26, 2022 06:38 PM under Post Status Upgrade

Do The Woo Community: Woo DevChat, What is a WordPress Developer with Zach, Till and Carl

Zach Stepek, Till Kruss and Carl Alexander have a conversation on how and if you can define a WordPress developer.

>> The post Woo DevChat, What is a WordPress Developer with Zach, Till and Carl appeared first on Do the Woo - a WooCommerce Builder Community .

by BobWP at May 26, 2022 09:33 AM under Woo DevChat

Post Status: This Week at WordPress.org (May 23, 2022)

Each week we are highlighting the news from WordPress.org that you don't want to miss. If you or your company create products or services that use WordPress, we've got the news you need to know. Be sure to share this resource with your product and project managers.

Are you interested in giving back and contributing your time and skills to WordPress.org? 🙏 Start Here ›

Get our weekly WordPress community news digest — Post Status' Week in Review — covering the WP/Woo news plus significant writing and podcasts. It's also available in our newsletter. 💌

News


Five for the Future

What's happening specific to Five for the Future? Provide your feedback on these posts:

Post Status

You — and your whole team can Join Post Status too!

Build your network. Learn with others. Find your next job — or your next hire. Read the Post Status newsletter. ✉ Listen to podcasts. 🎙 Follow @Post_Status. 🐦

by Courtney Robertson at May 26, 2022 01:00 AM under WordPress Core

May 25, 2022

WPTavern: WordPress.com Announces New Starter Plan For $5/Month

WordPress.com announced a new “Starter” plan today for customers that bridges the pricing gap between the free plan and its $15/month Pro plan. The Starter plan is $5/month and includes a custom domain name, along with 6GB storage, and the ability to use payment collection blocks (Donations Form, Premium Content, and Payment Button).

WordPress.com Pricing – 5/25/2022

When WordPress.com rolled out major, unannounced pricing changes on April 1, slashing free storage limits, users took to the forums to express their profound disappointment in the controversial update and the company’s lack of communication around it. After receving overwhelmingly negative feedback, WordPress.com increased traffic and storage limits on the free plan before officially announcing it.

Seven weeks after WordPress.com began testing the waters with pricing changes, the company has responded to feedback about the wide gap between the free and Pro plans. Many customers were diappointed to learn that they would have to pay $15/month to have access to custom domain names, even though they do not need the commercial themes and plugins included in the Pro plan. Some users expressed that they felt “trapped in the net” with the pricing updates and planned to shift their sites to new platforms.

The new Starter plan solves some of these customer issues but it is still partially subsidized by advertising. Customers on this plan and the free plan will have ads displayed on their sites. This is different than the legacy Personal plan, which was $4/month for no ads, a custom domain, and the ability to collect payments. The fact that the new Starter plan costs more but doesn’t remove ads is a point of contention customers mentioned in the comments on the announcement. It does, however, include Google Analytics integration, which was previously limited to customers on the legacy Premium plan and higher.

“The Starter plan is not meant to be a replacement for the old legacy Personal plan,” WordPress.com CEO Dave Martin told the Tavern. “Our goal with every additional pricing iteration that we launch will be to learn something new. The Pro plan and the Starter plan are two of many future iterations that we plan to experiment with.”

Martin also reiterated that customers on the legacy Free, Personal, Premium, Business, or eCommerce plans are able to continue on them.

“[If] you are happy with your current plan, we have no plans to force you to change,” Martin said. “You can stay on your current plan.

“Finding the right balance between the value that we deliver to our customers and the price that we charge in exchange for that value is something that generally has to be iterated towards. We plan to do just that.”

Moving forward, Martin said WordPress.com is aiming to do a better job at communicating important updates to customers.

“I made a mistake with how we communicated the pricing changes with WordPress Pro,” Martin said. “We listened to feedback from our customers, I took responsibility for it, and then we worked to correct that with this next phase of our pricing change. We’re constantly working to be better at communicating updates.”

It’s interesting to see how WordPress.com is evolving its pricing in response the market and WordPress’ changing capabilities. Whereas the legacy plans leaned heavily on selling access to commercial themes, full-site editing has changed the game, giving users more customization power than before.

The company is still planning to introduce a range of add-ons for the Starter plan to give customers more flexibility. It’s possible there will be add-ons for removing ads and adding more storage, but the company still hasn’t announced what they will offer.

by Sarah Gooding at May 25, 2022 09:54 PM under wordpress.com

WPTavern: #28 – Mark Root-Wiley on Creating Standards for CSS in WordPress

On the podcast today we have Mark Root-Wiley.

Mark builds WordPress websites for nonprofits in Seattle, Washington, USA with a focus on accessibility and usability. He’s a long-time WordPress community member in Seattle and has previously helped organise WordPress Seattle meetups and WordCamp Seattle speakers.

He maintains Nonprofit WP, a free guide for people building WordPress websites for their nonprofits, and has a few free plugins available on WordPress.org.

He’s on the podcast today to talk about why he thinks that it would be useful for WordPress to adopt some CSS standards.

Over the years, as WordPress has evolved, the way that you implemented CSS was very much left to the individual user, themer or developer. You could do what you like, and that worked very well, after all, we all have preferred ways of doing things.

Now however, the reach of WordPress has outgrown those early roots and some 40+ percent of websites are using it. Projects that were built by one agency are often taken over by another. Users are often swapping themes to reflect their brand. Extra work is created for those inheriting sites as they try to unpick the way that the CSS is built and implemented.

Mark thinks that it’s time for WordPress to lay out some simple standards which are easy to understand, and if they became universal, would save us a lot of time and head scratching.

He’s not proposing anything radical, just some basic advice for the most commonly used CSS, and it’s quite a compelling idea which would need a lot of community buy-in, and possibly some top-down approval if it were to move forwards.

It’s very much the kernel of an idea at present, but thought provoking nonetheless.

Useful links.

Standardized Design Tokens and CSS for a consistent, customizable, and interoperable WordPress future

Standardized block markup, theme.json design tokens, and CSS classes to improve interoperability

Variable Design Token Scales with Static CSS Classes (Proof of Concept)

Core Styles and Theme Customization: the next steps

Explore options to add back semantic classnames to block wrappers

Add a Style Engine to manage rendering block styles

Transcript

[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox has a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, creating standards for WordPress’s CSS.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to WPTavern.com forward slash feed forward slash podcast. And you can copy and paste that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast well, I’m very keen to hear from you, and hopefully get you all your idea featured on the show. Head over to WPTavern.com forward slash contact forward slash jukebox, and use the contact form there.

Before we start, I thought that I’d let you know that there won’t be an episode of the podcast next week. This is because I’m hoping to be going to WordCamp Europe. I’ll be there with my microphone, recording episodes for the coming weeks. If you’re going to be there too, it would be lovely to meet up.

So on the podcast today we have Mark Root-Wiley. Mark builds WordPress websites for nonprofits in Seattle, Washington with a focus on accessibility and usability. He’s a long time WordPress community member in Seattle and has previously helped organize WordPress Seattle meetups and WordCamp Seattle speakers.

He maintains NonprofitWP. A free guide for people building WordPress websites for their nonprofits. And has a few free plugins available on wordpress.org.

He’s on the podcast today to talk about why he thinks that it would be useful for WordPress to adopt some CSS standards. Over the years as WordPress’s evolved, the way that you implemented CSS was very much left to the individual user, themer or developer. You can do what you like, and that worked very well. After all, we all have preferred ways of doing things.

Now, however, the reach of WordPress has outgrown those early roots and some 40 plus percent of websites are using it. Projects that were built by one agency are often taken over by another. Users are often swapping themes to reflect their brand. Extra work is created for those inheriting sites. As they try to unpick the way that the CSS is built and implemented.

Mark thinks that it’s time for WordPress to lay out some simple standards, which are easy to understand, and if they became universal would save us a lot of time and head scratching.

He’s not proposing anything radical. Just some basic advice for the most commonly used CSS. And it’s quite a compelling idea, which would need a lot of community buy-in, and possibly some top-down approval if it were to move forwards. It’s very much the kernel of an idea at present, but thought provoking, nonetheless.

If you’re interested in finding out more, you can find all the links in the show notes by heading over to WPTavern.com forward slash podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Mark Root-Wiley.

I am joined on the podcast today by Mark Root-Wiley. Hello Mark.

[00:04:02] Mark Root-Wiley: Hello. Thanks for having me.

[00:04:04] Nathan Wrigley: You are really, really welcome. I always like to begin the podcast with a bit of orientation. I think it’s very important that the audience gets to know a little bit about our guests. Who they are, what their journey with WordPress is and so on.

So although the question is a little bit generic, I’m going to ask it anyway. Please, just give us a little bit of a history about yourself specifically in relation to your WordPress journey.

[00:04:28] Mark Root-Wiley: Awesome. Yes, let’s see. It’s been a pretty long one at this point. I am a child of the web almost. So, even back in the middle grades, I was learning to make websites. And so, it’s always been my hobby and my passion. And so when I, when I went off to college and got a degree in sociology, of course, that was much less employable than web work.

So, I looked around at all the systems and I had some jobs and internships where I was working with Joomla and Drupal. And so of course I ended up landing on WordPress. So since 2010, I’ve been here in Seattle, Washington where I build WordPress websites specifically for nonprofits most of the time, and so, my journey has really been that about serving clients, building custom themes doing some custom plugin work, but really like, deep in the world of WordPress for well over a decade now. And, I got to say, I love it and I’m not considering going anywhere anytime soon.

[00:05:19] Nathan Wrigley: Oh, that’s excellent news. Now the topic under discussion today is going to be CSS and in particular, we’re going to reference right at the beginning, an article, which was published by Justin Tadlock on February 22nd on the WP Tavern website. And it was called the case for a shared CSS toolkit in WordPress.

And we’re going to get into the nuts and the bolts of that in a moment because Mark, I think it’s fair to say, would like to see some kind of overhaul in the way that WordPress handles CSS. And as I say, we’ll get into what that means in a moment. But Mark, I know that you may not be able to lay out the history of CSS in WordPress perfectly for us, but clearly you believe there’s a problem.

I’m just wondering if you could give us any insight that you’ve got into the way that the legacy of CSS in WordPress has meant that we’ve got a problem where we are right now. What has been going on and where are we at now?

[00:06:15] Mark Root-Wiley: It’s such an interesting question, and I think if I had to boil it down to just one sentence answer, you know, it’d probably be there used to not be very much CSS in WordPress and now there’s a whole lot more. To really expand upon that, I think what has happened is, you know, it used to be that WordPress really only had a little bit of front-end markup that it would put out. There were things, HTML for menus, HTML for the search form, HTML for widgets and themers just sort of applied their own CSS to that.

Maybe in some limited cases, WordPress had a little bit of CSS that they were adding to the front, but really very little. And with the block editor, we saw the project looking to really empower users to be able to control much more design of the sites they build, through the WordPress editor interface.

And if you want to give people more control over the design, you’re going to be, at the end of the day, you have to do that with CSS. CSS is the language we use to make design on the web. And so it has just become much, much more complicated. And I think all software, you know, to some extent, right, it’s always evolving, but I think in our world of open source, that development process can be much messier and much more organic. And I think that that can be a benefit sometimes. But I think that maybe this is one of those instances where, right now there’s a lot of different ways for accomplishing, you know, similar types of CSS on the front end. Certain blocks handle their CSS in different ways.

And I think we’re just seeing that, you know, it’s been what, three or four years now of the block editor and there still isn’t really a strong opinion of sort of, this is the way that the block editor handles CSS and that has made it really hard for, people in my chair. I’m trying to make themes that are going to work every time I hit the update button on WordPress.

There’s just more complex CSS. There’s more of it. It’s done in varied ways. With more code comes more complexity and, it’s time to try to bring some order to that complexity.

[00:08:20] Nathan Wrigley: So it’s a case of the project being older than it was 15 years ago. There’s more that’s been added on top. It’s like a layer cake. We’ve had update after update, after update and things have been added in and fiddled with. We’ve had complete turnarounds in the way the interface has been put together and so on Gutenberg and all of those kinds of things.

And, essentially we’ve now got something which you, I think it’s fair to say, you would like to have a bit of a reset. You’d like us to rethink the way that the CSS is handled. And you’ve got some ideas around that.

Could you give me, before we get into the weeds of it, could you give me examples of pain points that you believe need solving? And you can be as specific as you like, you could describe a particular website that you built and a particular moment where you realized, ah, there’s things that I wish were different. So pain points that illustrate well what the problem is.

[00:09:12] Mark Root-Wiley: Yeah, that is such a, such a good question. I think that in some ways, the WordPress 5.9 release gave us a brief set of examples that I think made things hard for a lot of us themers. What probably looked like fairly small changes to for instance, the HTML and CSS of the cover block.

There was I think one class that was removed from buttons that told you about the orientation of the buttons, how they were vertically aligned. But when that was removed, suddenly all these themes that had written CSS styles where they needed to know the alignment of buttons on their site, they just stopped working because that class had been removed.

So rather than even really an overhaul, I think it’s a lot more about refining the practices and making a public commitment to, in the future, we are going to include classes in all of these circumstances, so that you can rely on them.

We are going to output all of our CSS rules with a certain specificity. It’s time for the CSS to sort of be better, organized, more consistent, and just communicated better. Which is not really an issue of code, it’s more matter of having standards for the project. If anything that’s really what I am hoping to see.

[00:10:24] Nathan Wrigley: You’re not the first person to suggest that this would be a good idea. It feels in the article, at least anyway, you, you make the point that you are standing on the shoulders of giants, really. And do you just want to give a shout out to some of the people who in the past have elucidated what it is that you’re trying to do? There’s several of them, but I think it might be nice to give them some credit along the way.

[00:10:46] Mark Root-Wiley: Absolutely. Yes. I completely agree. I hoped that when I wrote my big blog post, this proposal that I know we’re going to talk about. What I see as one of the strengths is that there’s very little original thought in it. It’s really trying to bring together all these other great ideas from other people.

I think it goes back to, and I think you can still find it, the theme user experience standards, or TUX that came from Automattic’s theme team. And I think they have an example we should talk about in a little while. So, I owe a lot to them. Rich Tabor, I think about two years ago had some really awesome posts about what it would mean if we could standardize how we named font sizes, how we named colors and how we handle spacing and WordPress.

I think that’s a critical thing that we really do want to make happen. That’s something that I would love to see. And then, I think if you’re just tooling around on GitHub and following, you know, people who are filing issues and the Gutenberg repository, or writing about it. I certainly think Matias, one of the lead developers of the Gutenberg project has written really, really smart stuff about CSS.

And there were also I think, a couple of like small folks I want to give shout outs to. Louis herons on Github, talked about having a theme block contract. Things that themers can count on for blocks, making that contract. I love that phrase. I think that is super important. And I think also, uh, Andrew on ocean has written about needing different layers of CSS. And I really liked that idea too.

[00:12:11] Nathan Wrigley: Well, thank you. Hopefully, they’ll be listening in and they’ll acknowledge your acknowledgement, which is nice. So the idea really is you want there to be some sort of overarching structure. You want there to be some sort of consistency in the way that things are handled, and that WordPress Core would make moves towards that.

Now this is probably something that you’re going to have an opinion on, but there are out there already, all sorts of different ways of handling CSS. Frameworks, and what have you, you know. Just off the top of my head written a couple of down here, you know, you’ve got CSS Grid and Bootstrap and so on, but I’m pretty sure that that’s possibly not the approach you want us to go down. You don’t want to bolt those into WordPress Core?

[00:12:52] Mark Root-Wiley: Definitely not. Yeah. I think that WordPress has never taken a really strong position on like, this is how your theme code has to be written, and if you’re going to pull in an entire CSS framework like Bootstrap or Tailwind, that’s way more opinionated. That would be very limiting to anyone who didn’t want to do things that way.

So, I think, when I sat down and really thought about like, what is it that I as a themer want. What it was is really baseline standardization more about just making sure that all block HTML and block CSS are done in a similar way. So that they’re, they’re sharing styles, they’re sharing CSS classes.

I think that there is also a ton of power if we can just standardize key styles that every site is going to need. So colors and font sizes. The amount of space between elements, things like that. But certainly not going as far as something like Bootstrap where there’s, gosh, sliders and drop down menus and modal dialogues and all those things.

It’s not at all about that. It’s really, I think the word I really settled on is it’s, it’s a toolkit. It’s providing more tools that all theme developers, all plug in developers, we can all use and share, but we still get to choose how we use them and how much we use them. So that, if we want to play nicely together, you know, those tools are available, but we can still choose to do things in our own way where it makes sense.

[00:14:18] Nathan Wrigley: We mentioned at the start that there was a WP Tavern article, which in turn was written because of something that you wrote and I’m going to include everything that we talk about today as far as possible in the show notes. But if you wish to pause this podcast and go and read Mark’s piece, it’s called standardized design tokens and CSS for a consistent, customizable and interoperable WordPress future.

You’re going to find that over at There’s no, no hyphens or anything like that. It’s just M R W web.com. That outlines everything that Mark is talking about. And so that really frames the conversation that we’re going to have from this moment on.

Now you mentioned that you wanted some sort of standardization. Presumably if that’s the case, you believe that the standardization at the moment is lacking. It’s messed up. It’s a muddle for people to create things. Everybody’s using their own different ways of doing things. Just kind of outline the specific problems about fragmentation versus standardization. What is it that you’re trying to overcome? What are the problems in Core that we’ve got at the moment? Things that need amending. Things that possibly need creating or uncreating?

[00:15:35] Mark Root-Wiley: Yeah. I’m going to answer your question and I think I want to like start us maybe five years in the future and then walk backwards to get there. in five years, I think we’re going to see a lot of sites that were built with the early years of the block editor.

Like now suddenly they’re needing to move to new themes. And so what does that look like? And, right now what we have are a lot of what I think of as kind of in the moment decisions that have been made. Both by the themer and the editor. Let’s take the theme or example first.

So, the block editor from day one has always allowed themers to define named font sizes, right? So, they can call them whatever they want. A lot of themers have something like small, medium, large, extra large, I know. Justin Tadlock on the Tavern posted his extensively researched list of font size names that he likes. Definitely worth a read for anyone who hasn’t seen that.

But I think the critical thing is that you can call them whatever you want. You can call them broccoli, apple, bicycle. You can call them seven forty, two ninety six, even if that has nothing to do with their sizes. And so what this means is that if we’re going to switch to a new theme in the future, if we switched to a theme that uses different names, all those font size settings that were set on the last version of the site are just gone. There is no bridge.

And so if we could agree to some like naming schemes, whether it is small through large, or even just 0 1, 2, 3, 4, 5, 6, 7. Now, when you move from one theme to another, you’re going to inherit, the choices that were made by the editors of the site, and be able to keep content as intact as possible. And right now I think the systems that the block editor is giving us are not really encouraging that consistency.

And it hasn’t really bitten us yet. The problems I think are coming. And so when I talk about portability of content. That’s what I’m talking about is how, what happens when we move from one theme to another. And I think that when you make that process smoother, it’s because you have good standards and that’s going to benefit everybody, working all the time.

[00:17:41] Nathan Wrigley: So the idea then is that things would become more standard and hopefully the community as a whole would adopt some standards.

Now, although we haven’t discussed this in our conversation prior to clicking record, I’m curious about your thoughts about this. Do you have any expectation that this would be something that would be, if you like, top down, in other words, would this be something which you would like to just be reflected in documentation?

And it’s a thing that you could use, or are you looking for a framework for CSS where really there are standards, which must be adhered to. In other words, you don’t really get to choose. If you want to be a WordPress theme in the repository, then you must do it in such and such a way. And over time, you mentioned five years in the future, we slowly encourage people to become the writers of CSS in that way.

[00:18:38] Mark Root-Wiley: That is such a tough question. I think that I guess I’ll say a few different things. I mean, I think that whenever possible, it’s better to use carrots than sticks. And I think that, right now in fact, I think the theme dot json standard is a great one where, if you’re building, what we’re now starting to think of is like classic themes.

Like you can use the theme dot json it’s on, it’s up to you and you also get like a ton of benefits by doing it. So I think that if we had standards like this, there would just be tremendous benefits to anyone who uses them, because themes would sort of work more similarly and even, there would be ways where plugins could suddenly sort of start referencing theme styles.

I would like to think that maybe this could bubble up, and be, you know, a community standard that people want to buy in, but aren’t forced to buy into. At the same time, I don’t know what it’s going to take to get this moving. Standardizing semantic names is something, we could talk about it forever.

And so I know that I personally, like I put out, in my blog post, a bunch of suggestions for the names. I thought really long and hard about them. I have my reasons. And honestly, like if someone said, nope, we’re going to use this really weird naming scheme that I don’t really care for anyway, I would use it in a heartbeat. I think having standards is more important than the specific names of them are. And so I do think that, there could be some room for some top-down decision-making here. As long as it’s a fairly simple thing, and we’re not going to punish people for not using it.

In WordPress land, you know, maybe that means we’re going to maybe throw some errors on occasion if you’re not using, some warnings, excuse me, not errors warnings. But no errors, nothing’s going to actually quit working.

[00:20:21] Nathan Wrigley: You mentioned in the piece that there are some recent issues They were obviously some kind of catalysts for you, where you thought, okay, these kinds of things are happening and it makes it pretty obvious that we need to rethink this. I’m just going to read them out, and maybe this will give some context to somebody listening to this.

You say to quote, recent issues make the need for a consistent, transparent approach, clear. Classes that were previously present and used by theme authors have been removed in favor of inline styles. Okay, we’ll get onto why that’s bad. Inline styles are redundant, hard to override and remove valuable selectors for theme authors. New instances of important, let’s just say that, CSS rules catch theme authors by surprise. Markup changes to Core blocks were only announced after the fact.

Now, I don’t know if you want to take all four of those or just riff on generally why you think these are the core things which need to be addressed, but yeah, there’s obviously something in there that sparked your interest and made you want to create this framework, if you like. Let’s just talk about that for a minute. Have you got something to say around that? What is it that you’ve found problematic?

[00:21:27] Mark Root-Wiley: I certainly have things to say. I suspect that honestly, maybe it was just random, how many, how many issues in 5.9 there were that sort of just got my goat as it were. I think that this is maybe one of the areas where there has already been a little bit of movement actually, which is wonderful. So yesterday, was this day when sort of all the dev notes for WordPress 6.0 showed up on the make.wordpress.org/core blog, and it included a lot of announcements about some changes to things, that are coming in WordPress 6.0. And I think that that advanced notice, already feels like, maybe some of what I’ve been saying has been heard and, and that, that is really great to see.

So, you know, there’s going to be some changes to like how images get aligned, the quote blocks CSS, some changes around the group block in the block editor. And, I’m really happy to see that communication. So I do think that some of these smaller things were addressed, but I also think that the fact that some classes disappeared and some markup changed and nobody knew about it, and like important CSS got added. If you ever want to like really get a bunch of people worked up about CSS, just start talking about important.

I think the fact that those all happened at once, I think more than any one specific issue, it just felt like, okay, there’s a lot of people changing a lot of things all at the same time and there’s no cohesive vision for we’re trying to take CSS in WordPress.

[00:22:47] Nathan Wrigley: Yeah. So essentially you want there to be far less surprises in the way that things are released and also to have some cohesive framework that everybody can dip into and everybody understands because it’s been well-documented and everybody can buy into it. As you said, carrot, not stick, because it just makes sense.

The article on the WP Tavern website had a very large amount of commentary on it. More so than anything I’ve seen in quite a while, to be honest, a lot of praise for the idea of what you’re doing. A lot of people saying, yes, we need this, we need this right now. And to develop it a little bit further, you are, you’re keen to get involved in a semantic approach.

Now that might not be obvious to everybody. So what does that mean? What is it you hope would come out of this? We may have a different vocabulary, in use in the end, but the idea is that we’re going to be substituting words or not as the case may be. So talk to us a little bit about that.

[00:23:43] Mark Root-Wiley: Yeah. I when I’m talking about semantics here, it’s really about can we establish shared meanings for some naming conventions within our CSS? So, back to the font size example earlier, if we can all agree that every time we name our font sizes, we’re going to call them small, medium, and large.

And every time we create our color palettes, we’re going to start with a primary color and a secondary color and maybe an accent color. Having that shared meaning, that’s what semantics are, is going to just provide so many benefits, and it’s also going to speed things up.

There’s going to be less mental overhead, fewer decisions that themers have to make. There’s just tons of value there. Thinking back I had mentioned that the theme user experience standards were maybe the best spiritual forbearer to this kind of point of the proposal. One of the things they recommended is when you’re naming your menu positions to call them menu one, menu two, menu three, menu four. Maybe that’s not what I would have chosen, but I started doing it and I’ve done it ever since.

And what it means is that any time I switched one of my themes to another themes that uses that same menu naming convention, like, the same main menu just popped up in the header, right where I would want it to be without me having to update any settings at all, just because, our themes knew how to talk to each other.

So it’s really about, can we make our themes and plugins talk to each other better and, ironically or, or appropriately, I think that just means we all need to do a bit more communication together in the project.

[00:25:10] Nathan Wrigley: Let’s get into weeds of the areas you think ought to be covered off, with some kind of framework. I keep using the word framework. I hope that’s okay. So for example, you mentioned fonts and you mentioned that the fonts might have things like small, medium, large, and that could probably extend up and down.

But also there’s obviously other things in CSS that we would like to cover. So before we get into nomenclature of what those things might be, let’s just talk about the things that you want to cover aside from fonts. What other things do you think are so essential that we need to have a standard that everybody just understands?

[00:25:47] Mark Root-Wiley: Great question. So in terms of those kinds of like standard things that we should name, I think beyond font sizes, including font weights, because if you’ve ever used a font, you know, that some have nine or now in infinite number of weights. So we need a way to sort of have a standardized font scale. Colors and gradients I had mentioned.

And again, that’s something where WordPress already lets us name our colors and gradients. So let’s just agree to always call them the same things. I think font families. So what are you using for your copy versus what you’re using for your heading? And then I would love to also see maybe some border widths, and probably the biggest one that I am most excited about is let’s agree on one or a few named scales for spacing.

So the space between blocks in a post, also the space between columns. The space between a gallery. If we can all agree on those names, then we can have a gallery with small space, a gallery with large space. And that’s just always going to look good from theme to theme, even though those values are going to be different and up to the themer.

[00:26:53] Nathan Wrigley: So aside from the fact that you would like to take into account things like font sizes and weights, colors, gradients, font, families, borders, spacing gaps, and so on columns and what have you. There would obviously need to be things that are associated with those, and you, you mentioned font sizes, small, medium, and large. Do you have some sort of insight into how far each of these go? Let’s for example take font sizes or weights? Well, let’s go for font sizes just for illustrative purposes.

How far would you like to take that, and do you have a system for making it so that it can be extendable indefinitely? So an example might be, one dash large or something like that, or XL large or something like that. Just give us a flavor of how far that scale would go down as well as up.

[00:27:39] Mark Root-Wiley: Yeah, that’s a good question. So I think, if it were up to me, if I were making a top-down decision, I think I would just pick a scale of numbers. Either, you know, starting at zero or going up, or maybe even centered around zero with positive and negative numbers. I like the fact that you don’t need to know English to use a scale like that, and it is infinitely scalable.

I think the other scaling systems that a lot of people really like is what’s often called a t-shirt sizing. So instead of small, medium and large, we would just have S M and L. And the nice thing about that one is you can infinitely go in either direction.

So XL, XXL, XXXL. It gets a little silly after a while, but you can do it. Some people like to say like three XL instead of XXXL. And you can do the same with XS, extra small. I will say that I think that when it comes to what WordPress should be standardizing, I don’t think it makes sense for us to say that every theme needs to have a 15 point scale for font sizes.

Some themes are gonna want three or five and that will be fine. I like to think of, of the 80 20 rule. 80% of needs out in the world can be satisfied by only 20% of the possible names in this case, that we could come up with.

So I think that for something like font sizes, a seven point scale, maybe would probably meet everybody’s needs in terms of switching from site to site, and keeping things looking pretty good. Again, to go back to sort of like why I like to think of this as a tool kit. I wouldn’t want to ever say that themes can only have seven font sizes. Right. It would just be that if they want more than that, they’re on their own to go figure that out.

I will say that I did, I did a lot of thinking about this even after my blog post. And there’s, there’s a demo I put together that was showing how maybe we could even have a way of having really big scales that could kind of shift down to only a three point scale, or maybe you want to have a five point scale, but it skipped 0.4. I think there’s some clever things you can do with CSS custom properties that could allow that to happen. So you can find that demo in the blog blog post.

[00:29:38] Nathan Wrigley: Yeah. I ran that demo. That was really useful to look at that. But let’s move on to colors and much, much more constrained there. You just want a handful really unlike font sizes, which there’s definitely more scope with colors. You just want a few basic standards that will satisfy most websites I guess?

[00:29:56] Mark Root-Wiley: I think that’s right. And I think that the more colors that we defined, probably the more disagreement there would be. What purpose does the fifth most important color in your palette have versus what purpose does the primary or secondary colors have in your palette?

And so I think that, especially for colors, I think it’s the best example where if you had a bunch of standards, they probably wouldn’t actually be that useful. So let’s just, let’s keep it simple, right? Let’s not, over-complicate this. Let’s make as few things we all need to agree on as possible. So hopefully we can actually agree on them and move forward.

[00:30:28] Nathan Wrigley: The font weights and the font size is obviously really dramatically changed the way a website looks. And if you switch from theme to theme and those get messed up, it really can look remarkably different. And you mentioned spacing, so gaps and columns and padding and margin and all that.

Again, it can really catastrophic effect things. What was a very small space can become a gigantic gulf, given a change in theme and so on, and so I was just wondered let’s ask the basic question again. What kind of constraints are you placing on that? How many different things do you think you need regarding spacing and gaps and all of that? Are we looking at dozens of different options or just three or four?

[00:31:06] Mark Root-Wiley: My first thought was, we probably only need maybe five, and I think that that probably would be about enough. If someone wants to do a few more than that, that would be fine. I think that spacing is maybe a really good example of the other key reason why I would love to see themes like shifting to these scales, because right now, for the most part, when an editor wants to change the spacing, of something in their posts, they can, you know, set a specific margin value or a specific padding value.

They can say, I want the top margin of this image to be 24 pixels. And they’re making that decision based on how their content looks in that moment, on their screen with that specific theme. Let’s say design trends again in five years are like really into white space. Maybe that 24 pixels is going to look super tiny all of a sudden. So if we can allow editors instead of having to pick a number and on the next page, they forget that they entered 24. And so they entered 20. And like now there’s just chaotic numbers all over the place. If we just say like, well, at the top of this image, I want to have a large margin.

Now, when they move to their next theme, it’s going to be not 24 pixels, it’s going to be whatever that is in the next theme. It’s always going to look cohesive. And so I think it’s really important to point out that it’s not just about standardizing the scales for theme developers, but I think if we provide these scales as options for customizing post content, we’re going to see editors just having to like not think so specifically, and that’s actually going to enable them to be more consistent, both in the moment and in the future, when they need to sort of switch their design.

[00:32:43] Nathan Wrigley: In a sense, you’ve read my mind because my next question was really about that because obviously your doing this for a living, you can probably come up with some naming system, some framework that works for you, and just keep executing that over and over again. But, that’s not the world. We live in the world where you’ll probably take over a website in a few years’ time that somebody else built, and it will be littered with CSS classes and CSS styling, specific to that exact one little thing on that one page and how on earth did that happen?

But it did. And so you need to go back and unpick all of the problems. So there’s that. The developers amongst us have probably figured out a system for themselves over the years, and they’ve got something which works. But when you swap a website, when you go and take on somebody else’s work, the fact that there’s consistency and stability in the naming of things would really help.

But then you mentioned the bit, which I thought was really interesting, about the non-technical users and having things in easy to understand, non-technical language that somebody can just get a hold on and okay. All right. It would appear that that thing, okay, might not be the most obvious name in the world, but right, it does that. And it seems to do that consistently over the site. That just makes sense for end users.

You described them as editors, but it could be anybody touching the website who has the capability to edit things. They, they really don’t want to get involved with CSS. In fact, that’s probably their worst nightmare that they need to think about CSS. They just want a handful of things, easy to understand. A minimal array of choices. The styling decisions were made months ago, and I’m just happy to stick with them.

[00:34:17] Mark Root-Wiley: You probably described that bit better I ever could. And, I think it really gets to this, there are lots of strong feelings about, is WordPress maybe becoming more like a site builder? Is it forgetting about being a content management system?

I truly believe that I think it can be both. And I also think that a lot of the work, especially around full site editing right now, like it has that more site builder mindset. And so I do think it’s important to remember that not every person with a WordPress site wants that super, super, super fine-grained control.

You’re right. I work with folks that just, they are busy professionals in nonprofits in particular. A lot of the organizations I have, you know, whoever is updating the website that is a teeny tiny part of their job. It’s probably not even in their job description at all sometimes.

They don’t want to be thinking about pixels or ems or if they don’t even know what MSR right. Can’t I just have some large space. That’s all I want, right. And so I think that not only are there these like huge technical advantages behind the scenes, but I really do want to just call out that I think this could actually like, just bring some simplicity to the editor and like help people make good decisions without constraining them.

[00:35:25] Nathan Wrigley: It also provides some kind of muscle memory options as well, in that if you have been working with a WordPress website, let’s say you’re working for company A over here, and you’ve been working with a WordPress website, and you go to interview for another job and they say, have you any experience with WordPress website?

Yeah, that’s fine. I can do that. Then you don’t need to relearn it over on this site though. That thing does. Okay, that wasn’t quite expecting that. That’s a lot bigger than I thought. It makes the whole process of editors moving from one website to another easier as well. So it just seems like a bit of a win-win.

Now having said all of that, we’re 15 years plus into the project. Everybody in the comments on the Tavern article seemed to think this was a cracking idea. You seem to think it’s a cracking idea, the likes of Rich Tabor, they think it’s a cracking idea. And yet here we are talking about it as an idea.

What’s holding us back? What is stopping this gaining momentum if it’s such a sensible idea? Are we, is the project too limited in time? Are we concentrating on other things? You may not have the answers, but you may have some intuitions.

[00:36:33] Mark Root-Wiley: I guess I would start with, this is, you know, a little off the cuff, just a theory, but I do think that the block editor is written in JavaScript. And so the amount of JavaScript in the WordPress project in the last few years has just exploded.

To be really clear, that’s fine. You couldn’t build the block editor without that level of JavaScript. But I do think it means that a ton of the development is done. When people are thinking in terms of JavaScript, and I will say that, one thing that I’ve looked for and I don’t really feel like I’ve seen a lot of, is people sort of starting with, like, what do we want the output to look like? What is the ideal HTML and CSS to allow a user to select the margins of their images, you know, how do we want to handle that? And then build the interface that’s going to enable that.

It feels like it’s sort of working the opposite way. If we’re worried about what is the settings interface going to look like? And then like, we’ll figure out what the code, to make it actually work on the front end is going to be last. I do think that maybe working backwards a little bit more frequent. What CSS do we want, and now how are we going to make sure that it can be created in a sensible way? I wonder if that would help, because at least to me looking, somewhat from the outside, it doesn’t seem like folks are working that way.

And now having said all of that, I think it’s mostly a people and a communication problem. And I think that’s just harder than tech problems, right? Give someone an infinite amount of time and by themselves they could build the block editor on their own, but they certainly could not organize an entire community to agree on what to call font sizes.

That just requires folks coming together. And honestly like making compromises and, and trying to think about what’s best for the community and not just best for themselves. I think that’s really hard. I think we can do it. I think things like that have happened in the past. I do think that’s the fundamental issue and so I don’t, I don’t know exactly what’s needed though.

Again, that’s why I do wonder, could someone maybe make a, a bit of an executive decision on this one and, and just try to say this is happening and we’re going to be taking comments for this long, and then we’re going to make a decision and roll with it because we think the advantages to having a system are bigger than the disadvantages to any sort of, in the weeds decision that might make it through.

[00:38:47] Nathan Wrigley: I wonder if it’s because CSS, of all of the different parts of WordPress. The HTML and the CSS bits, they’re the easy building blocks, aren’t they? They’re the bits that a lot of people can get hold of really quickly. And with a quick flick through some kind of 1 0 1 tutorial, you can get yourself up and running with the basics of font sizing and padding and margins and, and quickly gain an understanding of it.

And so everybody’s been left to their own devices on that. The theme may very well take care of all of that, of all of that for you. And you may need to adjust absolutely nothing. You’re entirely happy with the theme and you don’t dabble. But if on that one particular occasion, you just wished to change that one particular thing you want the, I, don’t know, the, the heading to be slightly bigger, you just fiddle about and locate the CSS for that and modify it, add something to a style sheet, so on. And it’s fairly straightforward and it can be done by more or less anybody on their own, but it doesn’t require any consistency. Naming what you like so long as it works.

But your approach is, is slightly different. And yeah, it feels as if maybe it’s not got the momentum at the moment, but it feels like, you know, maybe with things like this happening, your initiative happening, people talking about it more, maybe somebody could take this on. And as you say, maybe at some point it does need somebody on high to make a decision executively and say, okay, we’re going to concentrate on this and it’s going to become important. But I don’t know that any of that is in the roadmap right now. So you may need to keep banging the gong for a little bit longer I think.

[00:40:23] Mark Root-Wiley: I actually, you know, I, I played a lot of percussion growing up, so I love banging a good gong. One thing I noticed is, you mentioned the number of comments on the Tavern post, I certainly got a few comments on my blog post and I published a, sort of a Github issue that the sister of the blog post and it got a lot of comments and, and I do think people are listening.

I’m not sure what’s required to sort of get some action steps. But, I will say that, what really made me think that, yes, I, I do think people are listening at this moment is there was a blog post, at this point, I think about a month ago, on the make wordpress.org/core blog called core styles and theme customization, the next steps.

The gist of that post is basically like here’s a bunch of links to get hub issues, please go read them and leave your feedback. The speed of change in an open source project is never going to be what we want it to be. And I really do try to always remember that when I’m feeling impatient, which is certainly why I wrote this whole thing.

But I do think that, it is important for folks to always be paying attention, always be sharing their mind, because I do think, at some point, especially if a lot of us keep talking about this, like some decisions will get made. And so, you know, make sure if you’re interested in this, make sure to go leave some comments on, on these issues and keep bumping them up so people can see that they are high priority for a lot of us in the community. I know it’s not just me.

[00:41:42] Nathan Wrigley: Yeah, it was quite interesting. The article that you mentioned, the core styles and theme customization, the next steps I was highlighting the bits that were basic replications of everything that you were saying. And quite a lot of the article got highlighted. Let’s put it that way. So it would seem that, on some level, there is movement here and people are definitely in agreement with you.

Do you have any insight into how this might get revved up and get more interest attached to it? In other words, are you willing to put your best foot forward and become somebody in the vanguard? Like I said, banging the gong. Or do you find that there’s probably a better way of, have you got any insights into where people could go if they agree with you and want to get involved to make this happen?

[00:42:25] Mark Root-Wiley: Gosh, it takes everyone in the community weighing in, I think that. One thing I’ll say is that, you know, I tried to get a lot of people to review my blog post and, even gives me advice on like, how should I publish it and who should I let know about this?

Cause I think that if it’s just me it’s ineffective. It does need to be a community. And so, you know, I would say I would love to see other people sharing their own proposals even. I don’t know. I don’t even know if you want to include this part, I don’t think it can just be me.

I it’s pretty silly actually. I published this blog post and then 24 hours later, we had a new baby. I definitely had to fall off the face of the earth and disappear for a while, but I was so thrilled to see other people, saying like, yeah, this is awesome. And here’s the couple of things I have to add.

[00:43:08] Nathan Wrigley: There’s a whole lot towards the end of the article where you outline the different problems that your solution may solve. I won’t list them all now, but all of it kind of makes common sense to me. One can only hope that the ideas that you’ve suggested go forwards and that people, as a community, can coalesce and come up with an idea.

And as you said, you’re not bound to any one particular way of doing it. It’s just the mere idea of standardizing things, whether it be named this or that is not important, it would just be nice to have some standard documented that everybody can adhere to and therefore make it a lot easier for all of us to make websites, whether we’re building them for clients or we’re just editing and tweaking them ourselves.

One of the concerns that we may have is the stability of WordPress CSS in the future. And I know that you have possible concerns that in the future, for example, Gutenberg blocks, there’s no requirement for the CSS, the classes, and so on to be the same today as it will be tomorrow or indeed yesterday.

So in other words, is that a problem, do you think? Is there any problem of consistency where let’s say that you build something and you ship It, and it goes out to your client. It’s using blocks, but suddenly unbeknownst to you, the blocks CSS classes all get modified, perhaps ever so slightly, but enough to break things. Is that a concern that you have?

[00:44:36] Mark Root-Wiley: It really is. And I think that this is one of the biggest things I sort of learned from this intense period of engagement I’ve been having with the project is that, in discussing this with other people and really closely going through, uh, lots and lots of issues and the Gutenberg Github repository. I found some core development team members really saying that they viewed the HTML markup and the classes and how the CSS has written as essentially like non-public, which is to say you can’t count on this stuff not changing in the future.

That was really shocking to me. And I think for a couple of reasons, I mean, th the first is that, you know, that’s never how it’s been in WordPress in the past. The HTML for the comment forum, the HTML for the search forum, like those weren’t always seen as, you can count on this, there are ways to change it if you need to, but if we’re going to change this stuff, it’s going to be a huge deal and you’ll hear about it in advance, and we’re really gonna try to avoid that.

And so it felt like, uh, that was a departure from how things had previously been. And also as I’m someone who I think follows the project, like more closely than average, even though I, you know, I’m certainly not like a day-to-day contributor, or anything, but this was huge news to me as someone who’s been working with the block editor for years now.

At least to me, I don’t even really know that it’s reasonable to just say that like, well, here’s a bunch of HTML and CSS. Themers I know you have like your job to do and you need to make changes to this, but like, you can’t count on it. That doesn’t really seem fair.

And I certainly don’t think people are really aware of that. They’re not going to go in and one day, you know, completely change the image block or the block quote block drastically. I don’t really think they mean we’re going to just completely change everything. But I do think it just highlights the need again, to really spend some time focusing on what is the HTML that can serve as best going forward. So we don’t need to change it.

What are the CSS classes and the ways of handling CSS styles that we want to commit to now so that we can all just know what’s coming in the future. And so that when there are changes made, they are a big deal, and people are given lots of advance warning and they can, they can react.

And so I think I’m seeing more advanced warning in WordPress 6.0, which is awesome. It’s time to have that conversation about how can we just reduce the number of times we need to make big changes like that. Cause people are going to style HTML, no matter what.

[00:46:58] Nathan Wrigley: Yeah. I wonder if it’s a product of the fact that the block editor is now basically a conduit to put in lots and lots of little components. So you might have a paragraph block and you might have a, an image block or a cover block or whatever it might be. You’ve got all of these different blocks and the functionality of that is not yet a hundred percent certain. In other words, aspects of it could change. And so I wonder if them communicating CSS will change is a product of that. They’re just not sure exactly what those blocks will look like in a few years time. And if they become radically different, maybe the functionality changes. Let’s hope it doesn’t. I’m sure it won’t, but if it did, some of the CSS may need to change. I don’t know.

[00:47:42] Mark Root-Wiley: I think you’re right on the money there. I mean, the block editor is so much more powerful and I want to be really clear that like, that’s awesome. Like the folks I work with generally, like love that they can do more complex things like columns, or like finally putting text on top of an image for the cover block.

Those are good things. And we had to have a more complex system to make that possible. So I’m not against the complexity, but I just think it’s really important that the folks who are building the product, don’t forget about those of us in the real world who, you know, have to make things work every day. And we have, we have new sites we’re constantly working on, the impact of even what can seem like a really tiny change can be really big.

To bring it all back around, I really do think that if we can have just a few more standards and right, if we can have that kind of contract between themes and blocks, I think we can reduce the amount of times that those kinds of changes happen.

I totally acknowledge that they’re going to have to happen every once in a while. If we want to have this like big, nice thing, we’re going to have to put up with probably more changes. Cause there’s more things that can change, but, let’s really, let’s take a minute and figure out how we can make that as infrequent unpainful as possible.

[00:48:51] Nathan Wrigley: Yeah. It’s interesting your language there. You described it as a big, nice thing. And in a sense it’s a big, nice thing made up of lots of smaller little nice things. Each of those little nice things is completely independent. And you may not use those on your website, but you may.

And if there’s modifications made to the CSS classes and what have you, the downstream effect could be pretty catastrophic. You know, if you’ve just built 50 websites and they’re all using the exact same block and some tiny little change affects you 50 times, that’s suddenly created a lot of work for you that potentially was not even thought about elsewhere.

[00:49:27] Mark Root-Wiley: It has. In some extreme cases, this is maybe the reason why some people are often building custom blocks that really they could just be using the core block, but I’ve, I’ve at least anecdotally heard that folks do that sometimes because they know that their block isn’t going to change, even if they don’t want to have to take the time to build it.

[00:49:44] Nathan Wrigley: If people Mark wants to find you. They want to actually reach out to you. You may wish to share a Twitter handle or a website or an email address. Totally up to you. Yeah, any place that you could be found if people are inspired to join you?

[00:49:58] Mark Root-Wiley: Yes. I am M R W web pretty much everywhere. So that’s, uh, MRW web with two W’s, uh, I’m MRW web.com. I’m M R W web on GitHub and Twitter and in the WordPress Slack and Post Status Slack. All these other places. I have a highly Googleable namee. If you want to come find me, I would love to hear from you I’m. I am not that hard to find.

[00:50:23] Nathan Wrigley: Well, Mark, thank you very much for being on the podcast today. I really appreciate.

[00:50:28] Mark Root-Wiley: Thanks so much for having me. This was a blast Nathan. Great, great questions. I got to say.

by Nathan Wrigley at May 25, 2022 02:15 PM under podcast

Do The Woo Community: dev_life snippet: Timing the Perfect Follow-up Customer Email

Although as a WooCommerce builder, you likely don’t sell fish, but here is a story to get you thinking creatively about follow-up emails.

>> The post dev_life snippet: Timing the Perfect Follow-up Customer Email appeared first on Do the Woo - a WooCommerce Builder Community .

by BobWP at May 25, 2022 02:00 AM under Upsells and Cross-Sells

May 24, 2022

WPTavern: WordPress 6.0 “Arturo” Adds More Templates and Patterns, Style Switching, and Block Locking UI

WordPress 6.0 “Arturo” was released today, named for Latin jazz musician and director Arturo O’Farrill, who has 15 albums to his credit.

Check out the official release video for a quick overview of some of the most important changes.

This release introduces sweeping improvements to the block editor and its utilities and design tools. Most notably, users can now select text across multiple blocks, manipulating the highlighted portion as a group while keeping the rest of the content blocks in tact.

image credit: Gutenberg 13.0 Release Post

The List View has been updated to offer a more intuitive display that helps with navigating blocks on a page. Select multiple blocks using keyboard shortcuts, make changes, and drag-and-drop inside the list. List View is closed by default but will expand to the current selection when a block is selected.

image credit: wordPress 6.0 About Page

WordPress 6.0 also introduces a new interface for locking blocks, which allows useres to prevent blocks from being moved or removed. It is useful for preventing accidental edits but also for theme developers who want to prevent users from removing blocks inside templates, preserving more complex layouts.

image credit: WordPress 6.0 About Page

Other block editor improvements include the following:

  • New Blocks: Avatar, Post Author Biography, Read More, Comments Query Loop, and Stack block
  • Type two open brackets [[ to quickly access the link menu
  • Improved support for preserving unrecognized content in the editor
  • Preserve existing styles transforming blocks from one kind to another—from a Paragraph block to a Code block, for instance
  • New block style transformation options: Tag Cloud > Categories, Calendar > Archives, Paragraph > Code, and Group > Row
  • Create customized buttons and any new buttons will retain the style customizations automatically
  • New drop-down based color picker UI
  • Make tag clouds and social icons more appealing with updated settings and controls, and a new outline style for the tag cloud
  • Instant block style previews
  • Featured images now available in Cover block
  • New border controls for more precise control when setting borders
  • Transparency levels for colors offers more creative control

WordPress 6.0 also introduces a gaggle of new layout controls for page building. Users can now control gaps, margins, typography, and more on multiple blocks inside a Group block. Creating layouts is easier with the ability to position groups of blocks by quickly switching between stack, row, and group variations. The Gallery block is now more flexible with gap support for custom spacing.

Full-Site Editing Updates: More Templates, More Patterns, and Style Switching

Patterns are now available in more places and better integrated with the Site Editor. Gutenberg 12.7 brought major improvements to the patterns experience by making them easier to discover. The block inserter has been updated to display patterns, as opposed to blocks, when users are editing a template in the post or site editor. It also favors showing patterns when the inserter is at the root level or the content being inserted is between other blocks. WordPress will now show existing template parts, as well as block patterns in the template creation process.

image credit: WordPress 6.0 About Page

Theme authors can now register patterns from the official Pattern Directory using theme.json, so that users have quick access to patterns the author has highlighted.

WordPress 6.0 introduces five new template options for full-site editing: author, date, categories, tag, and taxonomy. 

One of the most anticipated features of this release is the Style Switcher. It allows userse to apply quick style changes within the same theme, and includes the ability to further edit the font weight, style options, and color palette.

Theme authors can create multiple different theme.json style variations and place them into their themes’ /styles folder. Users will then see the styles under the Styles menu in the top toolbar of the site editor.

WordPress 6.0 is the product of collaboration from more than 500 contributors in 58+ countries. It introduces more than 1,000 updates and bug fixes, including many that make the platform more performant and accessible.

Check out the 6.0 Field Guide and the release notes for a more detailed look at all the changes in the latest release.

by Sarah Gooding at May 24, 2022 08:29 PM under WordPress

WordPress.org blog: WordPress 6.0 “Arturo”

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 VanRaalte · Jan Weiss · janh2 · Jarret · Jason Johnston · Jason LeMahieu (MadtownLems) · Javier Arce · Javier Prieto · Jay Trees · jazbek · Jean-Baptiste Audras · Jeff Bowen · Jeff Matson · Jeff Ong · Jeff Paul · Jenny Dupuy · Jenny Wong · Jeremy Felt · Jeremy Herve · Jeremy Yip · Jez Emery · jhned · jhnstn · jigar bhanushali · jiteshdhamaniya · Joe Dolson · Joe McGill · Joen Asmussen · Johannes Kinast · John Blackbourn · John James Jacoby · John Regan · John Watkins · Jon Brown · Jonathan Champ · Jonathan Desrosiers · Jonny Harris · Jono Alderson · Jorge · Jorge Costa · José Arcos · Josepha · Josepha Dambul · Joshua Fredrickson · Joy · jrivett · jsnajdr · juanlopez4691 · JuanMa Garrido · Juliette Reinders Folmer · Junaid Ahmed · Justin Ahinon · Justin Busa · Justin Tucker · KafleG · Kai Hao · Kajal Gohel · kapacity · Kapil Paul · 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.

by Matt Mullenweg at May 24, 2022 08:01 PM under releases

Do The Woo Community: Builder Tips from WordCamp Europe 2022 Speakers

Tips from Daisy Olsen, Dave Lockie, Devin Walker, Greg Ziolkowski, Jonathan Wold, Milana Cap, Nev Harris, Paul Bearne, Ryan Welcher, Vassilena Valchanova and Vito Peleg

>> The post Builder Tips from WordCamp Europe 2022 Speakers appeared first on Do the Woo - a WooCommerce Builder Community .

by BobWP at May 24, 2022 09:01 AM under Woo Community

May 23, 2022

WPTavern: Open Source Initiative Launches News Blog on WordPress

The Open Source Initiative (OSI), a public benefit corporation and steward of the Open Source Definition, has launched a news blog on WordPress. In 2021, OSI’s board appointed Stefano Maffulli as its first Executive Director, and he is leading the organization in overhauling its web presence.

“One of the main objectives for OSI in 2022 is to reinforce our communication channels,” Maffulli said. “We’re improving the perception of OSI as a reliable, trustworthy organization. The OSI didn’t have a regular publishing schedule before, nor a content plan. Now we have established a regular cadence, publishing at least once a week (often more), commenting on recent news like a winning against a patent troll or court decisions about open source licenses, featuring our sponsors, and offering opinions on topics of interest for the wider community. It’s a starting point to affirm OSI as a convener of conversations among various souls of the open source communities.”

The blog was launched on a subdomain of the opensource.org website, which uses Drupal 7, self-hosted on a droplet from Digital Ocean. It’s also tightly integrated with CiviCRM to manage members’ subscriptions, donations from individuals, tracking sponsorships, and sending the newsletter.

As Drupal 7 is approaching EOL in November 2022, the team is planning to move everything to WordPress. They explored managed hosting with Drupal but found it was more expensive and also required them to migrate to a more recent version of Drupal. Themes and plugins made for D7 are not compatible with D9+, so they didn’t see an advantage in terms of time or simplicity.

“Unfortunately we don’t have staff to manage a self-hosted Drupal installation and nobody on staff really knows how to use it,” Maffulli said. “Tasks like creating landing pages proved to be quite time consuming for us.

“With money, knowledge and time constraints and an urgent need to increase our publishing rate, ramping up the organization’s visibility online we decided to migrate the website in two phases: First, we migrate the blog so we have a fresh look together with the improved publishing schedule. This phase is complete – the blog is on a managed hosting offered by DreamHost. The second phase is the migration of the rest of the site: this is ongoing with the help of Automattic and will take a few months to complete.”

Although Maffulli wanted to avoid creating a blog under a subdomain, and preferred using the old URL (opensource.org/blog...), mixing Drupal self-hosted with a managed WordPress site was not a common use case with straightforward solutions. If the new blog design looks familiar, that’s because it was inspired by WP Tavern’s new design.

Open Source Initiative’s new WordPress-powered blog

“Once we decided to go with a subdomain, the new site took really only a few days to launch: I knew I wanted to have a simple site, minimal amount of plugins, no page builders and a very clean design based on WP Tavern, of which I’m a fan,” he said.

Since the Tavern’s theme wasn’t yet on GitHub, Maffulli contracted a developer who used WordPress’ new full-site editing features to create a simple child theme based on the Twenty Twenty-Two default theme. He said he is glad overseeing the project gave him a chance to learn the basics of FSE.

Some members of the OSI staff were already familiar with WordPress, which contributed to the decision to use the software. The wide range of functionality and third-party integrations were also a factor.

“We rely a lot on content calendar solutions that allow to manage schedule posts and social media promotions from one tool,” Maffulli said.

“We’re addicted to CoSchedule. That tool is far from perfect, primarily because it’s not Open Source. But it’s so incredibly powerful and convenient for a small team like us. We track our publishing calendar and tasks with CoSchedule, making it so easy not to miss a beat: every blog post has it’s social media attachment, same with the newsletter, that becomes a blog post for archive. Soon, we’ll add podcasts.”

Maffulli said he wishes the WordPress media library offered a more standardized way of storing and tracking copyright information, like the author, source, and license.

“I think this unnecessarily exposes WP users to copyright infringement claims where trolls could threaten successfully people who may have not kept their records clean,” he said. “It’s something to think about for future releases of Instant Images and similar plugins.”

The OSI team has opted to keep comments closed on posts at this time, since they do not have the capicity to properly moderate comments.

“I have a lot of experience managing online communities and I know it can become very time consuming,” Maffulli said. “We just don’t have staff but we’re raising funds to solve that.”

OSI is also looking into creating a way to give its members the privilege of commenting. This would require a way to integrate authentication with CiviCRM to access members’ records.

“While we build staff and upgrade opensource.org, I hope to setup services from the IndieWeb community into Voices of Open Source,” Maffulli said. “This will allow for comments made on various social networks to be aggregated back into blog.opensource.org.”

The new Voices of Open Source blog has started by featuring the network of OSI affiliates, which boasts 80 organizations, including Mozilla, Wikimedia, Linux Foundation, OpenUK, and more.

“We’d like to share OSI’s unique position to highlight open source stories, challenges, and successes of companies and people around the world,” Maffulli said. OSI is in communication with its affiliates to make them aware of this opportunity and is aiming to open guest posting on the blog to indvidual members in the wider community sometime in the future.

by Sarah Gooding at May 23, 2022 09:31 PM under open source

May 22, 2022

Post Status: WooCommerce Function of the Week: wc_get_product_category_list

Here's yet another time-saving WooCommerce function. No need to reinvent the wheel — with a single line of code and no custom queries, you can get all the categories a product belongs to.

This week's function is wc_get_product_category_list, and there's no need to explain what it does as its name is self-explanatory.

As usual, we'll study the WooCommerce core function code, see where and why it's used, and finally we'll cover a quick case study. Enjoy!

Function code

The function wc_get_product_category_list can be found under \woocommerce\includes\wc-product-functions.php:

/**
 * Returns the product categories in a list.
 *
 * @param int    $product_id Product ID.
 * @param string $sep (default: ', ').
 * @param string $before (default: '').
 * @param string $after (default: '').
 * @return string
 */
function wc_get_product_category_list( $product_id, $sep = ', ', $before = '', $after = '' ) {
	return get_the_term_list( $product_id, 'product_cat', $before, $sep, $after );
}

First of all, let's look at the function parameters:

  • $product_id, which is of course the product we want to get the categories for.
  • $sep, by default a comma, which defines the list separator.
  • $before and $after, by default empty strings, which define what shows before and after the list of categories. (prefix / suffix)

Now to the function statements — actually, statement, as there is only one:

return get_the_term_list( $product_id, 'product_cat', $before, $sep, $after );

That really sounds like a WordPress function as there is no mention of “woo,” “wc,” or any other WooCommerce prefixes. Let's look it up in the WordPress developer code reference documentation. (https://developer.wordpress.org/reference/functions/get_the_term_list/)

Here we go:

function get_the_term_list( $post_id, $taxonomy, $before = '', $sep = '', $after = '' ) {
    $terms = get_the_terms( $post_id, $taxonomy );
 
    if ( is_wp_error( $terms ) ) {
        return $terms;
    }
 
    if ( empty( $terms ) ) {
        return false;
    }
 
    $links = array();
 
    foreach ( $terms as $term ) {
        $link = get_term_link( $term, $taxonomy );
        if ( is_wp_error( $link ) ) {
            return $link;
        }
        $links[] = '<a href="' . esc_url( $link ) . '" rel="tag">' . $term->name . '</a>';
    }
 
    /**
     * Filters the term links for a given taxonomy.
     *
     * The dynamic portion of the hook name, `$taxonomy`, refers
     * to the taxonomy slug.
     *
     * Possible hook names include:
     *
     *  - `term_links-category`
     *  - `term_links-post_tag`
     *  - `term_links-post_format`
     *
     * @since 2.5.0
     *
     * @param string[] $links An array of term links.
     */
    $term_links = apply_filters( "term_links-{$taxonomy}", $links );  // phpcs:ignore WordPress.NamingConventions.ValidHookName.UseUnderscores
 
    return $before . implode( $sep, $term_links ) . $after;
}

Simple enough — get_the_term_list accepts basically the same parameters we covered above, plus the $taxonomy parameter, which in our case is passed as product_cat to tell WordPress we're retrieving WooCommerce product categories.

Here's how it works:

  • get_the_terms( $post_id, $taxonomy ) gets the product ID category objects.
  • $links array gets filled with the list of categories, each with its own link.
  • return $before . implode( $sep, $term_links ) . $after gives us the content we need: “prefix + $links separated with $sep + suffix”

Function usage

Define a product ID (e.g., 57) — and that's all you need to do!

Call the function:

echo wc_get_product_category_list( 57 );

And see the magic happen:

cat1 link, cat2 link, cat3 link, ...

Of course, if you have access to the $product global, you can call the function dynamically. For example, if you want to call the function on every single product pages, you could do this:

echo wc_get_product_category_list( $product->get_id() );

Now I want to see where and when the function is called, so we give it a bit of context. With a quick search through the WooCommerce plugin, I find a single result in \woocommerce\templates\single-product\meta.php, line 34:

<?php echo wc_get_product_category_list( $product->get_id(), ', ', '<span class="posted_in">' . _n( 'Category:', 'Categories:', count( $product->get_category_ids() ), 'woocommerce' ) . ' ', '</span>' ); ?>

Which generates this output on my single product page:

Now we know wc_get_product_category_list is responsible for showing the list of categories in the single product page where it comes with a prefix (‘Category:' or ‘Categories:' based on category count) plus the default comma separator and no suffix.

Let's use wc_get_product_category_list for our custom development example now and consider a quick case study.

Case study

Where could wc_get_product_category_list come in handy? Surely, in the shop page.

By default, WooCommerce shows the list of products with image, title, price and button. There is no mention of product categories there, so let's add them ourselves.

Before:

The custom snippet:

/**
 * @snippet       Show Categories | WooCommerce Shop
 * @how-to        Get CustomizeWoo.com FREE
 * @author        Rodolfo Melogli
 * @testedwith    WooCommerce 6
 * @donate $9     https://businessbloomer.com/bloomer-armada/
 */

add_action( 'woocommerce_after_shop_loop_item', 'bbloomer_show_product_categories', 9 );

function bbloomer_show_product_categories() {
	global $product;	
	echo wc_get_product_category_list( $product->get_id(), ' - ', '<p>In: ', ' ' . _n( 'category', 'categories', count( $product->get_category_ids() ), 'woocommerce' ) . '</p>' );
}

After:

A few notes:

  • I used the woocommerce_after_shop_loop_item hook with priority 9, which is just before priority 10 (the add-to-cart button). TLDR: I'm outputting the category list above the add to cart button.
  • I declare the global $product so that I can access the product ID.
  • I then call the wc_get_product_category_list function, with the following parameters:
    • $product->get_id() -> the product ID
    • ' - ' -> the separator
    • '<p>In: ' -> the prefix
    • ' ' . _n( 'category', 'categories', count( $product->get_category_ids() ), 'woocommerce' ) . '</p> ' -> the suffix

It's interesting how I reused this line from the single product page, as I mentioned above:

_n( 'category', 'categories', count( $product->get_category_ids() ), 'woocommerce' )

Basically, if count = 1 the first string is returned (singular “category”), while if count > 1 you get the plural “categories.” You can see the difference in the last screenshot above.

Any other use cases you have in mind? Let me know in the comments!

by Rodolfo Melogli at May 22, 2022 09:00 PM under WooCommerce

May 21, 2022

Gutenberg Times: WordCamp Europe, 75 Themes, Thunks and Filters – Weekend Edition 216

Howdy,

Greetings from Porto, Portugal. It’s a wonderful city. You cn walk and walk and walk, up the hill, down the hill, with ever changing view. The ratio of restaurants and bar per block is on average three. In certain areas, every single doorwar offers you a different place to eat or drink.

Last week, WordCamp Europe organizers announced that there will be a livestream of the sessions’ in track one and two. That’s good news, as there are amazing talks and speakers on the schedule. If you want to casually run into me, I will be at the Community Booth Friday and Saturday around 10 am 🙂

Before people from the WordPress Community descend to Porto, core contributors will release WordPress 6.0 on May 24, 2022. The signs seem in their favor, and RC candidate four is now available. Hector Prieto, release co-coordinator, outline the WordPress 6.0 Release Day Process, just in case you are interested in how the sausage is made, so to speak.

Stay well, and safe!

Yours, 💕
Birgit

Theme Building and Full-Site Editing

Nick Diego, developer advocate at WPEngine, has been teaching the Working with Template in Full Site Editing series on the Meetup Social Learning space. Part 1 and Part 2 are now available on WordPress.tv


If you want to know how far the Gutenberg project and the block editor in WordPress has come, watch this video by Anne McCarthy: Building a site with WordPress 5.0 vs WordPress 6.0


The Pattern Creator is a online tool which allows you to create block patterns for inclusion into the WordPress Patterns Directory, a place where you can access freely available patterns for your websites. On this podcast episode of the WPTavern’s Jukebox, Ana Segota and Kelly Choyce-Dwan on How To Use the New Pattern Creator, Nathan Wrigley talked to Ana Segota and Kelly Choyce-Dwan, who share two different perspectives. Segota is a themer and Choyce-Dwan is on the team, that built the Pattern Creator.


Now that the Style Switcher is coming to WordPress 6.0, it might be time to learn how to create Style variations for your theme. A style variations is a user-selectable skin of the same theme. Everything stays that same except the color palette or the available fonts. Caroline Nymark published a lesson for you on her site.

Justin Tadlock also wrote about Global Style Variations, “Skins” for Themes, Have Landed in Gutenberg earlier this year.


Carolina Nymark aslo pursued the question: Can a full site editing theme be accessibility-ready? and shares her throughts and knowledge

Update for site owners and site builders.

75 Block Themes in the WordPress Theme Directory, Catch FSE is one of them. Justin Tadlock took it for a spin and published his review. Catch FSE Is a Bold, Business-Friendly WordPress Block Theme.

Take a look at the others: WordPress Theme Directory, Full-Site Editing


Kevin Batdorf, developer at Extendify, published a plugin called Image Filters that adds 22 more filters to your choices, even better than Instagram and you can do it all on your website!

Read more about it on the WPTavern: The Image Filters Plugin Adds Over 20 Filters, Including Vintage, Pastel Pink, and More

Now available on WordPress TV

Using the Navigation Block with Wes Theron, a 45 minute walk through the ins and outs of the new Navigation block.

And when you are done with that, or if you already know it you might want to Take Advantage of Query Loops also with Wed

Block Buidling and Tools for Developers

In his live stream, reviewing the changes to the @wordpress/scripts package and trying out Thunks for the first time, Ryan Welcher looked at the new changes to the @wordpress/scripts package that make using it much easier for developers. He then get into using Thunks in the datastore created for the pre-publish checklist.

What are Thunks you might ask? Here is a post by Adam Zielinsky: Thunks in Gutenberg

Upcoming WordPress Events

Social Learning Events

May 23, 2022 1pm EDT / 17:00 UTC
Hello Blocks! Coding a custom block w/ Ryan Welcher

May 25, 2022 – 7pm EDT / 23:00 UTC
Design With Me: Create a Simple Website for your Small Business w/ Sarah Snow

May 26, 2022 – 5 pm EDT / 19:00 UTC
I want a Website, not a Blog! w/ Destiny Kano

June 16, 2022 – 5pm EDT / 19:00 UTC
Let’s build a homepage together w/ Wes Theron.

WordCamp and other Events

June 2 – 4th, 2022
WordCamp Europe

June 11 + 12, 2022
WordCamp Warsaw

June 20 – 24, 2022
Page Builder Summit

June 25, 2022
WordCamp Montclair, NJ

September 9 – 11, 2022
WordCamp US, San Diego, California

September 15 + 16, 2022
WordCamp Netherlands

February 17-19 2023 (tent)
WordCamp Asia, Bangkok, Thailand


Don’t want to miss the next Weekend Edition?

We hate spam, too and won’t give your email address to anyone except Mailchimp to send out our Weekend Edition

Thanks for subscribing.

by Birgit Pauli-Haack at May 21, 2022 05:43 AM under Weekend Edition

WPTavern: New Video Explores Site Building Progress From WordPress 5.0 to 6.0

Do you remember what it was like to use WordPress 5.0? Three years and ten major releases have radically changed the site building experience, but it’s not always easy to see recognize when focused on some of the smaller, iterative changes that slowly add up. Anne McCarthy, WordPress product liaison at Automattic and co-release coordinator for 6.0, has created a short 13-minute video that shows the immense amount of progress contributors have made on site building features.

McCarthy takes viewers back in time to WordPress 5.0, released in December 2018, which introduced the block editor and the Twenty Nineteen default theme through the work of 400+ contributors. She demonstrates using the Customizer with the default theme. These were simpler days and it’s clear now how limited the Customizer was for implementing the most basic changes.

The video contrasts that experience with the upcoming 6.0 release, which features the work of 500+ contributors on features that didn’t exist three years ago.

McCarthy quickly demonstrates the 6.0 site editing experience, swapping out template parts, and showcasing the breadth of the customization available for images, colors, typography, controlling the posts that are displayed, style variations, and the impressive array of design tools available.

Ten major versions later, nearly every aspect of a WordPress site is customizable through the site editor. For those who have not yet made the leap into full-site editing – it’s essentially like the old Customizer but with super powers, better instant previews, and the interface is a panel on the right. At this point, I don’t think the usability is at a level where someone can just get in there and immediately know what they are doing. It takes a little bit of exploring, but it’s moving in the right direction.

Videos like this one show what is possible and just how far WordPress has come since it first introduced the block editor. It also indirectly answers Joost de Valk’s recent claims that the full-site editing project not being done yet is partially to blame for WordPress’ recent decline in market share.

While WordPress remains the uncontested market leader among CMS’s, some say this small percentage of a decline is inconsequential. Matt Mullenweg has stated in previous interviews that he views market share stats as a “trailing indicator” in the quest to create the best possible experience for users and developers. A growing market share, in that sense, is a signal of user satisfaction.

WordPress jumped into the block paradigm at the right time, just as many other apps began adopting the concept of composable blocks for creating content and designs. Full-site editing is the extension of that vision but it takes time to make it something polished and delightful to use. McCarthy’s video is a good reminder of the limitations that users previously labored under while trying to edit their sites, and the “why” behind all the effort going into FSE.

“As someone who’s currently on the WordPress 6.0 Release Team, I can attest that the project needs more contributors,” WordPress contributor Nick Diego said in response to the recent market share discussion. “The fact that FSE has taken so long is not a lack of effort. There are many contributors pouring their hearts and souls into the project. We just need more help.”

by Sarah Gooding at May 21, 2022 01:14 AM under full-site editing

May 20, 2022

Post Status: Post Status Upgrade — Zen and the Art of Lockpicking

Learn new skills and build your knowledge to enhance your career in WordPress! Post Status Upgrade is an ongoing series of live workshops centered around a particular skill or learning activity.

Watch Robert Rowley explain the basics of lock picking in this live, hands-on workshop for Post Status members that took place on May 5th, 2022. Watch as Robert teaches participants how to open locks, as well as their minds. He shares stories about emotional intelligence and the life cycle of skill practice from the beginner's mind to the expert's. You'll laugh at some entertaining mishaps Robert has had with lock picks!

Robert RowleyRobert Rowley

Robert Rowley is Patchstack‘s Security Advocate and has been picking locks since 2004. Between 2016 and 2019 Robert ran a retreat for his information security friends and colleagues called Disconnect Camp. This is where he first combined skills like lock picking with reflection on mental health, wellness, skill development and more.

StellarWP

StellarWP is a collective of WordPress innovators empowering business owners and creators with plugins and tools to help them thrive. We build great plugins, but we don’t stop there; we continually challenge ourselves to keep innovating and improving. Our solutions include the most trusted names in WordPress, with more than 2.5 million installs. Since 2021, we’ve grown to encompass seven brands and dozens of plugins. StellarWP is part of the Liquid Web family of brands.

by David Bisset at May 20, 2022 09:15 PM under Post Status Upgrade

Post Status: Post Status Notes #499

Kim Parsell Memorial Scholarship returns to WCUS › Think like a platform again! › Leo Gopal on support for mental health in the community › WP Accessibility Day › Performance Lab 1.1.0 › The WordPress Way › Dropping jQuery for speed › More to WP than Headless and FSE for devs › and more…


With WordCamp US being held in-person (September 9-11), that also means the WordPress Foundation’s Kim Parsell Memorial Scholarship has returned! This scholarship provides financial assistance — including travel costs — so the recipient can attend the conference. It's good to see three scholarships will be awarded this time, thanks to COVID-19 taking out in-person events for us in 2020 and 2021.


Brian Coords says WordPress “needs to start thinking like a platform again.” While I don't agree that Full Site Editing feels like or is the next “Google Plus or Apple’s Ping,” I do believe it could distract from user experience elsewhere and other things that need attention. (My take: Google abandoned Plus without putting much effort into it, and Apple is just bad at social full stop.) [DB]

I talked about what WordPress needs in a recent Post Status Comments episode on the prospects of declining market share with Joost de Valk, Alex Denning, and Jessica Frick. [DB]


Leo Gopal from Cape Town, South Africa writes about depression and mental illness, and how the WordPress community has rallied around him.


Here's a new plugin from Xaver Birsak that hosts the Google Fonts you use on your own server.


If you're a Gravity Forms user and have ever needed charts and graphs, then GravityView‘s new plugin might be of interest.


The WP Accessibility Day website is live! The date for this event is November 2-3, 2022.


Carolina Nymark took to Twitter for an insightful investigation and survey about the Full Site Editing themes already in the .org theme directory. She shares stats like the number of core blocks styled in theme.json and common color slugs.


Here's a good two part series (part one and part two) from Hidde de Vries on common accessibility issues that you can address and fix on your site today.


Ross Wintle has combined a searchable command palette with “fancy browser APIs” to enable voice-controlled WordPress. Fun experiment!


If you are new to WooCommerce and looking into performance enhancements, this post from Ibad Rehman might be a good place to start.


Bernhard Kau has released a WordPress plugin for MailChimp users. “If you are using MailChimp and want to show a nice archive on your page, you can now add it with a block.”


The WordPress Performance Team has published the 1.1.0 release of the Performance Lab plugin. It includes an enhancement that “replaces the featured image with a WebP version when available.”


A nice take here from Ollie Williams on color fonts. Modern web typography, fonts, and CSS have come very far in a relatively short period of time.


While Jason Coleman‘s “The WordPress Way” post is a few weeks old, if you haven't read it, you should. Jason explains the core values of his team at Paid Memberships Pro, which includes the idea that the GPL license will result in “the best code.”

Jason explains what this means in specific terms in a time of debate and discussion about what should happen to WordPress software when a paid support license expires. For Jason, the WordPress way “means our code will continue to work as expected if your paid license expires.”

While I think there are slightly different takes on what is best for customers and that experiments in the WordPress ecosystem should be encouraged, I also would like to see more people follow in Jason's footsteps and publish their core values.


WooCommerce has opened up a call for testing regarding the move to custom tables. It's the first milestone for a large effort but the goal of the call “is to test the migration process across various hosts and server combinations.”


Courtney Robertson shows you how to lock blocks in WordPress, a new feature coming in 6.0. Good for when a client takes over writing and revising content and hits a button accidentally.


Here's a free and open source tool that converts tweets into static HTML — perfect for testimonials.


GOV.UK dropped their jQuery dependency from their front end, with some impressive numbers in the performance results. Great takeaway: “Don't shortchange your users if the web platform can easily do the job a framework can.”


Héctor Prieto shares the WordPress 6.0 release process (starting next week), including the timeline and how you can help.


Tom McFarlin thinks there is more to WordPress than FSE and Headless. He feels “we’re spending a lot of time talking about the same things in WordPress as of late.”

I can understand where Tom is coming from — there are lots of technologies beyond React we can use. Getting off the beaten path is a good way for developers to get new ideas, have fun, and prevent nimble competitors from dominating certain niches.


Jonathan Bossenger explains why it's important to think about indexes for custom database tables — and when not to use them. He shows how you can diagnose and add indexes, offering valuable tips. One example: “When you are filtering or joining data based on specific fields, adding indexes to those fields is a crucial step in ensuring your queries are optimized.”


Sari Azout says it’s no longer enough to organize the world’s information — it's more important to organize the world’s trustworthy information with “boutique search engines that index, curate, and organize things in new ways.” This article rings true to me, as I find some Google searches less effective than they have been in the past.


Do you enjoy our weekly notes?

Get them and more in Post Status' Week in Review. We gather WordPress and WooCommerce news along with significant writing, videos, and podcast episodes from the WordPress community and beyond. Don't miss the latest updates from the people making WordPress in our This Week at WordPress.org summaries. It's all in our newsletter! 💌

by David Bisset at May 20, 2022 09:04 PM under The Week in Review

Post Status: Getting Uncomfortable

Growth is uncomfortable; you have to embrace the discomfort if you want to expand.

Jonathan Majors

Have you ever had to work outside of your comfort zone? It’s something I’m trying to get used to. But it sure isn’t easy.

This week and next I’m working from my dad’s home office in Tennessee while we prepare to sell his house.

This place is beautiful, and the view from the office is breathtaking. It’s easy to see why my dad loved it here.

But beautiful things can still be uncomfortable.

Traveling to WCEU has many people anxious about traveling after so long, and attending a WordCamp after a number of years.

But discomfort can help us grow, connect, and be more than we were before.

Whatever you’re doing, I hope you’ve built in a little discomfort to help you evaluate where you are, plan a course for the future, and thrive wherever you end up.

If you're going to WCEU, here are some tips on getting the most out of it!

Have a great weekend,

— Michelle

by Michelle Frechette at May 20, 2022 07:22 PM under The Post Status Team Blog

Post Status: WordPress Podcast and Video Picks for the Week of May 15

Good viewing and listening for you this weekend! Krogsgard on memberships and churn. Web 2.0 tech leaders reflect. Mike McAlister on the journey from Atomic Blocks and Array Themes to the Liftoff Creator Course. Paid services at Underrepresented in Tech. The Pattern Creator and Directory. WCEU. Inclusive Open Source Processes and Governance.

My Podcast Picks 🎙

My Video Pick 📺

  • Inclusive Open Source Processes and Governance is a great presentation by Silona Bonewald via Open Source 101 in early April 2022.

Get our weekly WordPress community news digest — Post Status' Week in Review — also available in our newsletter. 💌

And don't miss the latest updates from the people making WordPress. We've got you covered with This Week at WordPress.org. ⚙

by David Bisset at May 20, 2022 01:41 PM under The Week in Review

Akismet: Version 4.2.4 of the Akismet WordPress Plugin is Now Available

Version 4.2.4 of the Akismet plugin for WordPress is now available. This update contains the following improvements:

  • Improved translator instructions for comment history.
  • Bumped the “Tested up to” tag to WP 6.0.

To upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in the WordPress plugins directory.

by Stephane Daury at May 20, 2022 10:01 AM under Releases

Do The Woo Community: Do the Woo is Heading to WordCamp Europe 2022 as a Media Partner

WCEU is happening in Porto, Portugal. Find Do the Woo there and join us in a podcast or let's just have a conversation.

>> The post Do the Woo is Heading to WordCamp Europe 2022 as a Media Partner appeared first on Do the Woo - a WooCommerce Builder Community .

by BobWP at May 20, 2022 09:00 AM under WooBits

Follow our RSS feed: 

WordPress Planet

This is an aggregation of blogs talking about WordPress from around the world. If you think your blog should be part of this site, send an email to Matt.

Official Blog

For official WordPress development news, check out the WordPress Core Blog.

Subscriptions

Last updated:

May 28, 2022 11:30 PM
All times are UTC.