WordPress Planet

October 05, 2024

WPTavern: New Social Web Foundation Launched with Automattic’s Support  

The Social Web Foundation was officially launched on September 24, 2024, with a mission to foster a “growing, healthy, financially viable, and multi-polar Fediverse.” This non-profit organization is spearheaded by Evan Prodromou (Research Director), Mallory Knodel (Executive Director), and Tom Coates (Product Director) and is dedicated to uniting social networks through the open standard protocol, ActivityPub.

The Fediverse is a collection of interconnected, decentralized social media platforms that communicate using open protocols, with ActivityPub—developed by the World Wide Web Consortium (W3C)—as the primary standard. “Until now, no major organization has taken on advocacy for ActivityPub as its central goal. Many people have ideas about what the Fediverse needs to be bigger, safer, and easier to use. But the solutions they propose fall between the cracks of anyone implementer or service. We want the SWF to be the entity that takes on those jobs.”, said Evan Prodromou, often referred to as “The Father of the Fediverse.”

Tom Coates emphasized the foundation’s straightforward goal: “Fundamentally, its goal is pretty simple – it’s there to help the Fediverse grow in a sustainable and healthy way that benefits everyone.”

The Social Web Foundation is our best chance to establish the conditions in which the new social media operates with zero harm.

– Mallory Knodel

The foundation aims to address challenges within the ActivityPub ecosystem and support its growth, especially in the commercial sector. Key areas of focus include:

  • People: Educating the public about the Fediverse and its benefits.
  • Policy: Clarifying policy frameworks for international and federated networks.
  • Protocol: Developing and maintaining open standards.
  • Plumbing: Building the necessary infrastructure

Thirteen prominent companies, including Automattic, Mastodon, Meta, Ghost, and Medium, are backing the foundation.

Automattic & Fediverse

Automattic’s involvement with the Social Web Foundation comes as no surprise, given its long-standing contributions to the Fediverse. Back in 2021, Automattic CEO Matt Mullenweg expressed interest in bringing ActivityPub support to Tumblr. In 2023, Automattic acquired the ActivityPub plugin for WordPress from German developer Matthias Pfefferle and made the ActivityPub feature available across all WordPress.com plans.

“Automattic is excited about the launch of the Social Web Foundation and its mission. We’re eager to collaborate with the Foundation to expand platform diversity and enhance the support for various content types—especially long-form content—within the Fediverse, fostering greater interoperability across the ecosystem.”, said Matthias Pfefferle, Open Web Lead at Automattic.

To know more about Automattic and Fediverse, check the YouTube series, The Fediverse Files

by Jyolsna at October 05, 2024 06:14 PM under Social Web Foundation

WPTavern: 159 Employees Leave Automattic After Accepting the Alignment Offer

While the controversy between Automattic and WP Engine was unfolding, social media discussions surged about whether Automattic employees not agreeing with Matt were offered an ultimatum to quit and exit with a generous payout. 

 In response, Matt Mullenweg addressed the situation in a blog post titled Automattic Alignment. He has clarified that: “It became clear a good chunk of my Automattic colleagues disagreed with me and our actions. So we decided to design the most generous buy-out package possible, we called it an Alignment Offer: if you resigned before 20:00 UTC on Thursday, October 3, 2024, you would receive $30,000 or six months of salary, whichever is higher. But you’d lose access to Automattic that evening, and you wouldn’t be eligible to boomerang (what we call re-hires). HR added some extra details to sweeten the deal; we wanted to make it as enticing as possible.”

Matt revealed that 159 employees, representing 8.4% of the workforce, accepted the offer. Of these, 79.2% were part of Automattic’s Ecosystem businesses, while 18.2% came from Cosmos, working on apps like Pocket Casts, Day One, Tumblr, and Cloudup.

“It was an emotional roller coaster of a week. The day you hire someone you aren’t expecting them to resign or be fired, you’re hoping for a long and mutually beneficial relationship. Every resignation stings a bit.”, Matt added. 

Automattic referred to this move as “a strategic realignment to better pursue our core values and operational goals.” 

We remain deeply grateful to all our employees, past and present. For those who have chosen new paths, we sincerely wish them the best, and thank them for helping make Automattic what it is today. We emerge from this chapter with a renewed vigor and clarity in our mission.

– Automattic 

159 People Accepted the Offer 

In a surprising turn, the names of people leaving Automattic include Josepha Haden Chompsky, the Executive Director of the WordPress project. “While my next steps aren’t yet clear, I hope to never be too far from this community that taught me so much.”, she said.

Other notable departures include Naoka Takano (Open Source Project Manager), Daniel Walmsley (AI Engineer and Architect), Jeffrey Pearce (Team Lead) and Reyes Martínez (Communications Wrangler & WordPress Media Corps lead). Daniel Bachhuber (head of WordPress.com) also left but posted this in LinkedIn: “I believe in Matt. Leaving Automattic for other reasons. It’s a bummer, and I will miss everyone there.”

91.6% of Automatticians are Staying

Meanwhile, 91.6% of Automattic employees chose to stay, with many expressing support for Matt’s decisions on X. 

Community Response

As usual, the community remains divided, with some praising the offer’s generosity while others are worried.

As mentioned above, 79.2% of the people who left Automattic were working on WordPress.org projects. The Marketing Team again got the short end of the stick with WordPress Media Corps’s future in doubt due to Reyes Martínez’s resignation. The coming days will provide more clarity on the effects this development has on WordPress.

by Jyolsna at October 05, 2024 05:45 PM under automattic

Matt: CNBC on WP Engine

Ari Levy at CNBC has a great article covering the battle between WordPress and Silver Lake / WP Engine: Why WordPress [co-]founder Matt Mullenweg has gone ‘nuclear’ against tech investing giant Silver Lake.

by Matt at October 05, 2024 01:03 PM under Asides

October 04, 2024

Matt: Automattic Alignment

Winston Churchill said, “Never let a good crisis go to waste.” Since I last blogged here, WP Engine filed a meritless lawsuit and Automattic responded, and there’s been a hurricane of public activity and press. Inside of Automattic, there’s been a parallel debate and process.

Silver Lake and WP Engine’s attacks on me and Automattic, while spurious, have been effective. It became clear a good chunk of my Automattic colleagues disagreed with me and our actions.

So we decided to design the most generous buy-out package possible, we called it an Alignment Offer: if you resigned before 20:00 UTC on Thursday, October 3, 2024, you would receive $30,000 or six months of salary, whichever is higher. But you’d lose access to Automattic that evening, and you wouldn’t be eligible to boomerang (what we call re-hires). HR added some extra details to sweeten the deal; we wanted to make it as enticing as possible.

I’ve been asking people to vote with their wallet a lot recently, and this is another example!

159 people took the offer, 8.4% of the company, the other 91.6% gave up $126M of potential severance to stay! 63.5% were male. 53% were in the US. By division it impacted our Ecosystem / WordPress areas the most: 79.2% of the people who took it were in our Ecosystem businesses, compared to 18.2% from Cosmos (our apps like Pocket Casts, Day One, Tumblr, Cloudup). 18 people made over 200k/yr! 1 person started two days before the deadline. 4 people took it then changed their minds.

It was an emotional roller coaster of a week. The day you hire someone you aren’t expecting them to resign or be fired, you’re hoping for a long and mutually beneficial relationship. Every resignation stings a bit.

However now, I feel much lighter. I’m grateful and thankful for all the people who took the offer, and even more excited to work with those who turned down $126M to stay. As the kids say, LFG!

by Matt at October 04, 2024 03:28 AM under Automattic

October 03, 2024

WPTavern: WordPress Enforces Plugin Check and 2FA for New Plugin Submissions

Security Review Lead Chris Christoff has announced two new changes for the WordPress Plugin Directory, effective from October 1, 2024. These changes aim to enhance plugin directory security and promote best practices among plugin developers.

Mandatory Two-Factor Authentication

As of October 1, 2024, all plugin owners and committers must enable Two-Factor Authentication (2FA) to submit new plugins to the WordPress Plugin Directory. This change was announced by Automattic-sponsored developer Dion Hulse last month.

Plugin owners are encouraged to enable 2FA, review committers’ access levels, and use additional security features like the SVN password option and Release Confirmation. Detailed guides on Configuring Two-Factor Authentication and Keeping Your Plugin Committer Accounts Secure are also available.

Plugin Check Tool

From now on, any new plugin submitted to the Plugin Directory will first go through a pre-submission check using the Plugin Check tool. If any errors are found, the submission will be blocked until they are fixed.

This new step aims to reduce the review queue by enabling plugin authors to catch common issues before submitting their plugins for manual review. Plugin Check helps by identifying frequent issues, such as mismatched versions between the plugin header and the readme.txt file, incorrect text domains, and erroneous “Tested To” values in the readme. Although Plugin Check adds a layer of automation, it will not replace the manual review of plugins.

David Perez from the Plugin Review Team recommended making Plugin Check a part of the development workflow as “In addition to things relevant for the review process, the tool flags violations or concerns around plugin development best practices, from basic requirements like correct usage of internationalization functions to accessibility, performance, and security best practices. It does so using both static checks using PHP_CodeSniffer and dynamic checks, where it actually activates your plugin to test it “live”.”

The Plugins Team is working to expand Plugin Check’s coverage to existing plugins. A roadmap detailing this broader application will be released in the coming months. Contributors can help improve the tool via its GitHub Repo.

The WordPress community has responded positively to these updates. Josepha Haden Chomphosy tweeted “This was years in the making and is a huge deal. Congratulations (and big thanks) to everyone who contributed!”

These two measures are expected to help the WordPress Plugin Team improve the security of the platform while reducing the backlog of plugins awaiting approval.

by Jyolsna at October 03, 2024 08:01 PM under plugin submissions

October 02, 2024

WPTavern: Automattic Publishes WP Engine Term Sheet Amidst Controversy

As the Automattic-WP Engine controversy continues, Automattic published the term sheet delivered to WP Engine on September 20, 2024. “In the interest of transparency, we’ve published the term sheet we offered to @LeeEWittlinger and @heatherjbrunner, it’s a simple one-pager.”, tweeted Matt Mullenweg.

The announcement post reveals that initial discussions between Automattic and WP Engine began in February 2023, led by Matt Mullenweg and continued by Toni Schneider during Mullenweg’s sabbatical.

The term sheet outlines five key points regarding a trademark license agreement. Under the terms, Automattic would grant WP Engine the rights to use WordPress and WooCommerce trademarks and branding, with WP Engine agreeing to follow all relevant guidelines. WP Engine was presented with three options for compensation:

  • Pay Automattic a royalty fee of 8% of its gross revenue on a monthly basis, along with a detailed report of its gross revenue, granting Automattic full audit rights.
  • Allocate 8% of its revenue to employee salaries for work on core WordPress features under the direction of WordPress.org, with both WordPress.org and Automattic retaining audit rights.
  • Combination of the above two options. 

The term sheet also prevents WP Engine from modifying or forking any software from Automattic, WooCommerce, or its affiliates. The agreement is for seven years with automatic one-year renewals.

However, the announcement post has a critical update: “Given WP Engine’s behavior, deception, and incompetence since September 20th these terms are no longer sufficient.

Matt also told The Repository, “That deal’s not on the table anymore. We’re seeking more, not 8%. I don’t want to speculate on what the deal might be… In July it was less than 8%, it was smaller. In September it was 8%. The deal they have to do next could be taking over the company, they have no leverage.” 

Public reactions to Mullenweg’s tweet sharing the term sheet have been mixed, with most replies critical of him, though some view the terms as reasonable.

The final results of a survey by Matt from The WP Minute:

During the ongoing discussions, co-founder & CEO of Cloudflare Matthew Prince offered to donate the capacity to power WordPress.org for the community. 

Meanwhile, the controversy seems to be spilling into Automattic, too. 

by Jyolsna at October 02, 2024 07:32 PM under wp engine

WPTavern: WP Engine Banned Again, Reports Deploying a Solution

After a brief reprieve, WP Engine has been banned again from WordPress.org and the company took to X to share: “Thousands of WordPress community members have once again been blocked from accessing WordPress.org. WP Engine has commenced deployment of its solution for accessing updates and installations for plugins and themes across our customers’ sites. We expect deployment of the solution to all customers to be completed within the hour.”

The next tweet read: “We are pleased to report that our solution has been fully deployed and regular workflow practices have been restored to our customers around the globe. We thank all our customers for their patience and support over the past week. Like so many of you, we love WordPress, and are committed to the stability and longevity of the community.”

WP Engine Website Updates

WP Engine has made several changes to its website, including reducing the use of the word “WordPress” and adding a new footer clarifying its trademark usage.

New Footer in WP Engine Website

The names of its pricing plans have been updated, omitting “WordPress” from the titles.

Current WP Engine Pricing Plans

Previous Pricing Plans of WP Engine

WP And Legal Stuff has covered more details on the website changes. 

WP Engine has not offered any explanation about the solution beyond what was shared on Twitter, though people have been asking for more details. 

WP Engine has been silent since the start of the incidents, while Matt has been going all-out speaking about the issues. Matt even issued an open invite to Lee Wittlinger, Managing Director of Silver Lake. “Lee, let’s debate this publicly. Propose a neutral venue and moderator,” he said in a post titled “Where is Lee Wittlinger?” “Why is WP Engine scared of talking to journalists live?”, he had asked earlier.

He also published his charitable contributions from 2011 to 2023, shared how WP Engine is violating WordPress’ trademarks, and gave interviews to Theo – t3․gg and WP Minute.

The community is deeply troubled by the proceedings but both sides do not show any signs of backing down.

by Jyolsna at October 02, 2024 06:23 PM under wp engine

WPTavern: #139 – Andy Fragen on Automatic Update Rollbacks in WordPress

Transcription

[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, automatic update rollbacks in WordPress, what they are, and why this was a difficult feature to build.

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/feed/podcast. And you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.

So on the podcast today, we have Andy Fragen.

Andy is a dedicated member of the WordPress community, as well as a trauma surgeon. Somehow he manages to balance the demands of his profession with his passion for the community. And, as you will hear, to important work inside of WordPress Core. Even while in the operating room waiting for patients to be prepped, Andy has been known to find moments to answer forum questions and provide support to others. It’s truly remarkable.

Andy talks about the important topic of automatic rollbacks in WordPress, a feature aimed at reverting to a previous version if an automatic plugin or theme update fails, ensuring the website remains functional for users. I’ve managed to encapsulate the idea into the previous sentence, but as you will hear, the execution of that idea was anything other than straightforward.

Andy discusses the origins of the rollback feature. The team working on this problem identified complexities and potential fatal errors during plugin updates, and came up with a simple, yet effective solution, which worked. But as with so much in code, some edge cases meant that the road to a fully workable solution for all WordPress users was not quite in sight. Many times the drawing board had to be dusted off, and the problem looked at once again.

While developing this feature, numerous challenges were encountered. From finding consistent test conditions to managing technical limitations. Andy shares insights into the critical role of testing and collaboration with hosting companies, meticulous attention to detail and problem solving skills, developed to combat issues like file write delays, and loop back test redirects.

Andy explains how the team managed to avoid fatal errors in active plugins with extensive testing and incremental improvements. They introduce functionalities like WP error checks, simulation features for testing error handling, and a new move directory function to enhance reliability.

Andy also discusses the broader impact of their rollback efforts. Many users might not notice this new feature, but in a sense that’s how it should be. The more unnoticeable to end-users update failures are, the better. It means that sites that would previously have been broken and are now working, and that’s a win for everyone.

If you’re interested in the behind the scenes development of a WordPress feature, that quietly keeps your website running smoothly, and in hearing how a dedicated contributor balances his passion for WordPress with a demanding medical career, this episode is for you.

If you’d like to find out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Andy Fragen.

I am joined on the podcast by Andy Fragen. Hello, Andy.

[00:04:21] Andy Fragen: Hello Nathan. How are you?

[00:04:22] Nathan Wrigley: Yeah, good. Nice to speak to you. We are in WordCamp US, we’re in Oregon. We’re in the convention center. I’ve actually no conception of what the convention center’s called.

[00:04:30] Andy Fragen: I think that’s it. I think it’s called the Oregon Convention Center.

[00:04:32] Nathan Wrigley: Normally when I come to these events, I’m talking to people who are doing a presentation of some kind, but we had a conversation, introduced, I think, via Courtney Robertson. She suggested that I might like to talk to you about this particular subject, and I bit her hand off frankly, because this is really interesting.

We’re going to talk about automatic rollbacks in WordPress Core. And if that doesn’t mean anything to you, that’s fine, Andy will introduce the subject a bit later. First of all though, Andy, it’s a bit of a boring, dull question, but can you give us your little bio, and then I think, unusually, I’m going to dwell on your bio for quite a long time, if that’s all right? Tell us what you do in all of your life.

[00:05:08] Andy Fragen: I am a full-time trauma acute care surgeon, and I work in Southern California. And I dabble in WordPress as a hobby.

[00:05:18] Nathan Wrigley: You are also a Core committer.

[00:05:19] Andy Fragen: Yes, sir. I got my first props for a Core commit about nine years ago.

[00:05:23] Nathan Wrigley: Okay. So, to me, Core commit, if you have privileges to commit to Core.

[00:05:29] Andy Fragen: Well, I’m not a committer, I’m a Core contributor.

[00:05:31] Nathan Wrigley: A core contributor.

[00:05:33] Andy Fragen: If they ever offered me commit access, I would decline.

[00:05:36] Nathan Wrigley: Yes, okay. Nevertheless, you are working at a very high level within WordPress, and this is the kind of thing that I think, this is what people do as a career. You know, they become incredibly skilled at coding, and in this case with WordPress, and this is the level maybe that they reach.

But let’s just rewind a little bit, because at the beginning of your bio you said you are also a trauma surgeon, which to me seems much more than a regular job. It seems like that would be an incredibly difficult thing to achieve in life, but also a thing which would consume many, many hours. And so I’m kind of wondering, how do you keep up in life with being a Core contributor as well as a trauma surgeon?

[00:06:13] Andy Fragen: As I said previously, time is the only fungible commodity we have. You spend it how you want to spend it. Obviously, depending on how you work and what the structure is, you have certain time availability, and then certain time not availability.

Some of what I have as a trauma surgeon is downtime. There are certain parts of my day that are busier than others, and there are certain parts of my day that aren’t as busy. I have been known to answer forum questions, and do support while in the operating room, waiting for a patient to be prepped.

[00:06:46] Nathan Wrigley: So, let me just parse that a little bit. Whilst in the hospital, when there are not urgent things to be done, you are whipping out the laptop and contributing to WordPress.

[00:06:56] Andy Fragen: No, I usually do that on the phone, believe it or not.

[00:06:58] Nathan Wrigley: I think that’s remarkable. Honestly, I am really, really amazed that you can manage that. I think you must have an incredible grasp of your own time management.

[00:07:07] Andy Fragen: Honestly, a lot of the support stuff is just having been in my own plugins that I’ve written for a long time. I have a better understanding of what the issue is almost without even getting too much you know, stack traces and things like that. Not that I don’t need them sometimes, but if you’ve ever done support and gotten issues from people, sometimes it takes a while to tease out the actual information you need to give a response.

[00:07:31] Nathan Wrigley: Do you regard WordPress as a hobby then, or is it more like a second career almost?

[00:07:36] Andy Fragen: Career would imply that you earn something from it. And, yes, I do sell a plugin, and part of the reason my wife allowed me to fly up to Portland for a WordCamp is I could say that the plugin sales paid for an airline ticket and a hotel. The usual deal I had with my wife living in Southern California was I could go to any WordCamp I could drive to. Since Covid they’ve really just stopped. Everybody’s sort of burned out, and that’s a whole other issue unfortunately.

[00:08:01] Nathan Wrigley: Yeah. How much time do you think, let’s say a month, would you be putting into WordPress?

[00:08:08] Andy Fragen: Some of that depends on where you consider your time. If I’m kind of paying attention to the Core dev Slack when they’re doing meetings, do you count that towards time? I mean, some people do, some people don’t. So I have said that I have usually put anywhere between 10 to 15 hours a week into it, depending on where it was. I mean, for a while I was running the Core upgrade install meeting. Sometimes we get, there’s not much for us to talk about, we’ve foregone the meeting at times.

Yes, somehow I’ve found myself as a component maintainer for the upgrade install component, along with several other people.

Over the years I’ve done, or found my way into, I should say, several different things. And one of the things I did when we met Courtney last WordCamp US in San Diego, she was having trouble getting set up in a dev environment on her computer. And I’d already sort of figured it out, and sat down and helped her with it and, yes, by the end of the time period, we had Courtney up and running in the docker dev environment for WordPress Core.

[00:09:08] Nathan Wrigley: So 10 to 15 hours a week, 40 to 60 hours a month, that’s a lot.

[00:09:14] Andy Fragen: Yes, and you have no idea what my normal schedule is like. Even if I didn’t do that, as a trauma acute care surgeon, we work shift work, and our shifts are 12 hours long. And an FTE, full-time equivalent, for being considered full-time is 16 shifts a month. Whether that’s two shifts in a row in 24 hours, or not, or individually, it just depends. I would’ve considered at some point in time, in the last several years, only doing 16 shifts quite nice. I’ve done as many as 30 in a month, and probably in the last several years, averaged somewhere around 20, give or take.

[00:09:54] Nathan Wrigley: I think what I’m taking from this, Andy, is that you work quite hard in all things that you do.

[00:09:59] Andy Fragen: I have two adult children, 29 and 23, and I did not encourage them in the least to go into medicine. I think they saw how hard I worked, or how much I worked, and I’m very pleased to say that neither one of them went into healthcare. I think it’s just a changing field.

[00:10:16] Nathan Wrigley: Yeah. Where did your interest in WordPress, or coding come from? Is this something that you’ve had as a child, or did you pick this up later in life?

[00:10:23] Andy Fragen: I took a coding class in college, not my major. But I graduated from college in 1985 as a senior, the first time they had an intro to microcomputers, and there was this new computer out called a Macintosh. And it looked fascinating. And the class had a lab, you could either choose to be in the Macintosh lab or the PC lab. And honestly it was a freshman level class, I took the class just so I could do the lab and learned how to use the computer. And on graduation I bought one, and I’ve been using Macintosh computers since 1985.

[00:10:57] Nathan Wrigley: So it is not really from childhood this, I guess maybe, I don’t know exactly how old you are, but certainly at my age, computers were a brand new thing. You couldn’t really do a great deal with computers back in the day. But I picked up the interest when I was probably a similar age to you, and it just kind of blossomed in me, and I just got really into it. And although it’s become what I do for a living, I can well imagine that if I hadn’t have done it for a living, it would’ve been a big part of my life anyway, a little bit like you by the sounds of it.

[00:11:23] Andy Fragen: I look at it as an interesting hobby. It’s a lot about problem solving, and it’s a lot about making a repetitive process simple, defined and consistent.

[00:11:34] Nathan Wrigley: Yeah. We’re going to talk now about something which is new in WordPress, and it’s automatic rollbacks. I don’t know if there’s a more grandiose title than that.

[00:11:44] Andy Fragen: We call it, I mean, internally we call it rollback auto updates, that’s just part of it though. Initially we just called it rollback.

It’s taken several years, and many cycles to kind of get into Core. And part of the issue was, when we first had it, a lot of Core committers don’t want to touch something, or don’t want to commit something that touches such a large piece of WordPress, such as plugin updates, or theme updates. And as you can imagine, everybody had a lot of trepidation. And it was a big enough project that somebody who wasn’t directly involved in it, if they left and weren’t paying attention for several months, they’d come back and whole things were new again.

[00:12:24] Nathan Wrigley: Right. Let’s describe what it is. So this is my understanding of it. A couple of years ago it feels like now, we got this option in the plugin screen to automatically update plugins. And it may be that almost everything in your WP admin, plugin wise, you can automatically update. So you don’t check a box, but in effect you check a box.

And from that moment on, that plugin, or all the plugins, if you decide to go that route, will automatically update in the background, so you don’t have to think. I guess it’s a part of a broader initiative to make WordPress as automatic as possible, so that you don’t have to log in if you’re an inexperienced user, or you’re just not really bothered about WordPress, you just want a website. And it’ll just all tick over in the background and keep itself updated.

Now that’s great, except when there’s a problem with the plugin update, and the updating automatically breaks something. You know, you come back and either you’ve got an email to say that things have gone wrong, or you just go to your website and discover, why does my website now not function anymore?

The initiative here was to make it so that some automatic detection mechanism would update the plugin, throw an error, say, there’s a problem, wait, roll it back, so go back to the previous safe version, and go from there. And so everything in theory should be good. Now that all sounds so straightforward to say, but just before we hit record, you indicated to me, and let’s get into this really granularly, you indicate to me that it was anything other than straightforward. Now, why was that?

[00:13:54] Andy Fragen: So Core has had the ability for a failed update to revert, try again, I’m not quite sure of the process, since about 3.5 or 3.7. And the ability to roll back a failed update for a plugin, or a theme really just wasn’t around. Colin Stewart and I, and Paul Baron had kind of gotten together on trac tickets about rolling back, and I think it was Paul’s initial trac ticket about it and, no, I don’t remember the number offhand, that really got us started. And it was intriguing to all of us on how to do it, and where to go.

And so we get together in private DMs, and discuss it, and kind of try and figure it out. We would overcome problems and basically create the solution, and I’d put it in a plugin so that we could test. And what we found was, well, once we got to parts where we had the whole solution, and we had a whole solution for quite a while, including the auto updates before we even had any of it committed.

But again, as I say, it was so complex and, you know, when you have millions of sites, and 45% of the web, and all of them are doing updates to plugins and themes at any given time, it’s like touching the third rail. I mean, sometimes you can kind of get away with it, but more often than not, you could potentially kill yourself.

So we never had a Core committer deeply involved in it. We had some that came and would give us advice on how to do things, or not do things, and we would seek to solve those issues and those problems. But without having someone with commit access, it made it very difficult to actually get things in. Colin now has commit access, and he got it just before the rollback was complete. But again, he’s like, I don’t feel comfortable, as my very first commit, committing this big part of Core.

After we’d had it done for a while, there was a discussion on the trac ticket about what it would take to test it. And one of the Core committers suggested that we test it on thousands of sites, of various different server setups, to ensure that it didn’t cause issues or problems.

Now, conceptually I do understand that, because WordPress can run on a vast variety of installations, and hardware, and virtual environments, and all sorts of things. You don’t want to screw it up. You don’t want to brick somebody’s site consistently.

The problem is, I don’t think anybody’s ever been asked to do something so extensive before. And so we basically found that it was almost impossible. I was at the first WordCamp in San Diego, the first one after Covid, and I literally went around to all the hosts and said, I need you to test this, I need you to test this, I need you to test this. And everyone was very agreeable, but they would test it on their environment, right? Make sure that it worked in their system, but probably only on one site that was a test site, and not in production on anywhere else. And I’m not quite sure that that’s what they were looking for.

We only kind of overcame that process when we broke it down in smaller pieces. So rollback started out with getting, let me go back. Currently, the way Core works, Core updates work, and the way plugin and theme updates work is, Core would download the package, the update, it would store it on your system locally. It would run some checks, it would re-expand the zip into the upgrade folder, and then it would do a recursive file copy into the location of the plugin directory, or the theme directory. Although it would also delete the file first, before it that recursive copy.

Consequently, if something failed, your plugin was gone. You had to go find it again and reinstall it, if somewhere along that process failed. The first thing we did is try and, well, one of the first things I did was made it a zip file. So I back up the plugin or theme is a zip file, store that, do the update. If it failed, I’d reinstall the zip file. But we heard from several hosting companies, that may be taxing on resources creating, and zipping, and unzipping files at that scale.

And so I’m like, okay, let’s come up with something else. And what we ended up with is changing that recursive file copy to use PHPs rename function, with the recursive file copy as a backup, as a fallback for it. Now, you would think that, since this runs on PHP, and everybody has PHP installed, that it would work out just fine, except VirtualBox and VVV. And so these are custom local dev environments.

We did put out a call to the hosting companies, does anyone offer a virtualised solution using VVV or VirtualBox? And the answer was, no. We kept getting failures using the PHP rename and VirtualBox. Partial file transfers, partial rights, and it took a lot of investigation to figure it out. Peter Wilson, one of the Core committers from Australia, uses VVV as his dev environment. And when you get a Core committer, and some basic part of this isn’t working, it’s not going in.

So we got the fallback. We did a lot of research, and it appears, from some Composer bug reports, that VirtualBox has sort of a delayed file right. Go figure. And they found that by adding a 200 millisecond delay to things, it solved the problem. We added a 200 millisecond delay to things, it sort of solved the problem. We later had some help from, I want to say it was Andrew Ozz, who’s clearly been around WordPress for a long time. And he suggested we try flushing the memory for, after we did the rights and stuff.

And we eventually got it so that it did work by doing that. We had a PR for essentially a new function, for a move directory, move dir, underscore dir, that replaced, copied, the recursive file copy, copy dir, in the update process. Copy dir’s still there as a fallback, but we now had the PHPs rename function working in every environment that we had, and consistently, even with VirtualBox and its limitations, or its peculiarities.

And that was the first big step we had towards getting committed. And I want to say that was committed in 6.2. So if you think back, all the stuff we had, aside from that little piece with the VirtualBox, was all done before 6.2. And the final piece just got committed in 6.6. So when I say this was years in the making, it really was years in the making.

The second part we did was just on manual updates. So we had, when you click a manual update, several things can happen during the course of the update process. Somewhere along the way the file copy, or the download can fail, the file copy can fail, certain pieces can be missing. So we created enough checks during that process and returned errors, such that, if any of those pieces failed, how we started with is storing the file to be updated in a temporary update folder.

And so if any of those processes failed, we would go and restore that folder using our moving function. The process was actually very quick in testing, on the order of, you know, less than a second because PHP rename just sticks the whole chunk and moves it. So you have to remember the first part of the process on the update is, you delete the plugin in the folder that it’s in, and so as you’re downloading and installing the other one, you’ve got nothing left.

The normal update process, you’ve deactivated the plugin, you reinstall it, and then it reactivates. That’s in a manual process. Remember when we get to the automatic updates how that’s different, and where it can be problematic. So we had restore functions, we had our delete functions, because after we had a couple of cron tasks that we created to clean up after ourselves on a weekly basis, so that those copies wouldn’t be around anymore. Even on a shutdown function, we would delete the folders, and then on a weekly basis we’d make sure they were all gone.

So once we got that working and committed, we had basically a safe method for manual updates. So if someone would go to the dashboard, they’d click update, if somewhere along the way their connection lagged, or their connection to wordpress.org was delayed, and things took too long, and the server timed out, it would reinstall the previous version. And you would still show that the plugin or theme required an update, because you’ve now reinstalled the previous version that was installed.

We didn’t have to go out to .org and re-download anything. Part of that is really what limited the resources that we were acquiring for servers. Because all we were requiring them to do was copy a directory back and forth to different locations.

[00:22:59] Nathan Wrigley: What’s the flag for success or failure in this case? What’s the thing which determines that the update hasn’t succeeded?

[00:23:06] Andy Fragen: It depends on different parts of the process. So if there’s a failure in the download package, and the downloading the package, there are several parts that we’re already checking, where it would succeed or fail. We either created new WP errors for those, and returned those values, and so when we looked for those returns, if they happened, we would send it to the functions we wrote to restore from the backup or not.

So we’d start the process by creating the backup. And then if the process continued on without error, the backup just got deleted at the end. If there was an error in the process, the backup was restored. You’d basically be right back to the place you started from, requiring an update to either the plugin or a theme.

[00:23:44] Nathan Wrigley: Yeah. Does the user in this scenario of the website, do they get some sort of notification that, actually, this didn’t work out? We’ve rolled back, your site is now working, but the thing that you intended to do didn’t happen. And if they do, does it list out what the problem was? Like it was, I don’t know, a download failure, or the plugin seems to be malfunctioning.

[00:24:03] Andy Fragen: You would see an error message, either in, if you were using the shiny updates on the plugins page, or the themes page, you’d receive the error message, and kind of a brief description of where the error was. Either the directory wasn’t writeable, or there was a download problem, or whatever the error happened to be. And then you’d be back at the place, if you refreshed your screen, it would show that you still needed the update.

If you did the update from the Core update page, you know how the update shows, here’s the zip I’m downloading, it’s doing this, you would see an update error there. And part of what we put in the test plugin, or the feature plugin, was a way to simulate an error. And so we simulated a download error. And so you’d see that, and it would say it’s simulated error.

[00:24:47] Nathan Wrigley: If I was to receive this error, let’s say that I’d put a plugin onto automatic updates, and I had received a failure, does your setup then say, okay, permanently stop automatically updating this, or is it more a process of wait for a day, or is there a setting that I can engage to say, try again arbitrarily later, just keep trying the update, or is it a case of, okay, we’ve identified there’s a problem here, now it’s up to you to go and check and fix?

[00:25:15] Andy Fragen: Well, at this point it’s just a manual update, right? So if the manual update fails, you refresh the page, it’ll say, update now again. And you just try again. Our assumption at that point is, if you continue to get an error because your upgrade path isn’t writeable, well, it’ll tell you that, and you probably have to check your permissions on the folder, and make sure that they are writeable. If there’s some other issue involved in downloading the file, the usual assumption is that will go away. And so you try updating again, and maybe the next time you update it works. You’re done.

[00:25:47] Nathan Wrigley: I guess one of the goals of automatically updating plugins was that you could have a site that you essentially could have an autopilot. And it could be, let’s say a brochure site, where the intention really is just to have a site and never look at the backend ever again.

[00:26:01] Andy Fragen: We haven’t gotten to that part. That was part one and two. The third part was the auto updates. Now, this does not apply to themes, and I say that doesn’t apply to themes because themes are kind of a different beast. And I guess we probably could figure that out, and maybe that’s the next, on the part four, which we haven’t really defined yet. But there’s certainly a lot more plugin updates than theme updates.

The difference between an auto update and a manual update is the auto update runs in a cron task. The auto update does not deactivate the plugin, update the plugin, and then reactivate the plugin. The plugin is active the entire time, which means if the plugin has an error in it, and the update completes successfully, you’ll have a white screen. And this has happened.

What we needed to do was figure out how to catch the error, essentially. And I want to say, the first iteration, there are basically three types of error handlers in PHP. I was checking every single one of them to make sure that we would catch the error. Now the problem with doing that is the shutdown error handler catches everything. So sometimes you catch the error twice, and that’s okay, but it was trying to figure out how to make sense out of some of those errors that was difficult.

And so we had a list of certain types of errors sometimes, and we would cause a rollback if we spotted any of those things. And it worked. For all the errors that we figured out, it worked. That’s not what we went with though, because what they don’t tell you is, when you write these things and you have feature plugins, is that, the way they integrate into Core, when you’re trying to commit them, may be totally different. So integrating it into Core is like, okay, now I need to update this file in Core, and that file in Core. Some of those things we could not duplicate in a plugin.

One of the things that we ended up with was a change to the load PHP file. There’s no way to mock it, there wasn’t. I couldn’t duplicate it, it loads too early, I couldn’t replace it. So we were just, okay, this could be the problem. So we tried to work around it a little bit, which is fine too. Colin did a little bit more digging and found out that, if you edit a plugin in the plugin editor on screen, it does a loop back check as it saves, to determine whether or not there’s a fatal in that plugin, and it won’t save it for you. And so we reutilise that loop back, as a test for whether the reactivation, or the installation of the plugin causes an issue or not.

We found it worked well. It greatly simplified what we were doing. I don’t even want to get into the fact that I was using reflection, and reflected objects, and reflected methods, and all sorts of things to fix it in the plugin in the first place. It worked and, yes, there are places in Core that uses the reflection classes, and reflection objects, and things like that, but not many. At least we knew we weren’t breaking new ground with that. But in adding that to Core, it made it a lot easier to do the loop back request.

Part of the issue in testing was we didn’t really have a file that would accurately fail every single time it was updated. I make an updater, it was easy to create a file that would fail on an update. So that’s all we had for a moment, until Aaron Jorbin piped up in one of the Slack meetings and said, here’s a plugin that’s been in the repo for a while, the title is, DO NOT USE THIS PLUGIN! And it is exactly for that. It’s set to fail on an update, it’s set to fatal on an update. And so now we had a plugin that other people could use more successfully, they didn’t have to go and install my updater or to find it.

Having both of them installed though did help things out because there’s all the scenarios you have to test for. What happens when you have a plugin that runs, and then a fatal, and then another plugin update that needs to happen, and maybe another fatal after that, or maybe two fatals in a row? All these things you don’t really think about, but you should test for, or you have to test for.

And it’s all manual testing. I had no idea how we could ever write, and then testing for it otherwise, without just doing it manually. I want to say, the first time we tested it for the update rollback, we picked 13 of the largest plugins. And when I say largest, some of the more complex plugins, as far as folders, and files, and size to run, and to see whether we get timeouts, whether they would complete successfully, and things like that.

We found what worked well, and that’s one of the places we found that VirtualBox error, because it would just time out. It wouldn’t complete it. We were making it fall back to the file copy originally, and nobody is going to have this list of files to recursively update at any one time, except us and testing, but it just wouldn’t work consistently. And so that was before we got the move directory function in and working for it, and then it worked.

[00:30:59] Nathan Wrigley: What I’m getting from this is you must have incredible patience. Years and years and years of trying different things, problems emerging that you couldn’t foresee, solutions that you tried to implement, and then discover, okay, that didn’t work, let’s try something new. I don’t know how good you are at not throwing things at the wall, but it feels like there was an opportunity here to throw things at the wall.

[00:31:19] Andy Fragen: You’re making an assumption Nathan, who says I don’t throw things at the wall.

[00:31:23] Nathan Wrigley: Was it a fairly, how to describe this? Did it surface things about the open source project, in terms of the way it’s done, that you wish were different?

[00:31:33] Andy Fragen: Certainly. You know, one of the things that certainly helped move us along was having a lead developer, in this case Andrew Ozz, take an interest, and help answer questions and move along the way. He helped us tremendously with the plugin dependencies feature as well.

Since none of us were committers, and it’s a big feature, it would be nice if the leadership assigned experienced Core committers to feature projects, assuming that most of the people involved in the development of those projects aren’t Core committers. Another reason I should never have commit privileges.

[00:32:11] Nathan Wrigley: Yeah, it sounds like from everything that you’ve said, that the process could have been expedited in a variety of different ways.

[00:32:17] Andy Fragen: It certainly could have. And some of that made for a lot of frustration because we would have experienced Core committers who would look at the project every couple of months maybe. It was a huge undertaking in total. And it was really only by splitting up into smaller pieces that we were able to accomplish it at all.

[00:32:36] Nathan Wrigley: Yeah, and also the dramatically impactful nature of what you were doing. And I’m sure the irony’s not lost on anybody, that you could have achieved fatal errors in the attempt to remove fatal errors. Just the idea that such an important thing, from your perspective, maybe didn’t get the, how to describe it, didn’t get the.

[00:32:55] Andy Fragen: Attention.

[00:32:55] Nathan Wrigley: Yeah, the attention, the sort of level of importance that it might have done given the impactful nature of it.

That now is in the past though, this is now a feature of WordPress. How much of a hand on heart moment, and I don’t know if that’s the right phrase, how difficult was it for you on the day that the version of WordPress that the shipped with came out? Were you fairly confident at that point that all the things were going to be fine?

[00:33:18] Andy Fragen: I’ve been running the plugin, which has had a version of the rollback code in it on sites for years, with plugins that would fatal on update. Now, the auto update will only check for the fatal update if the plugin is active, right? Because if it’s not active and it updates, all you’ll happen is, is when you go to activate it, it won’t let you activate it because it’ll say it fataled. And so you’ll have to go and reinstall another version or something, but it won’t take your site down. We specifically don’t test for plugins that aren’t active. Honestly, we’ve been running the code for so long on our own stuff, I wasn’t worried. I mean, have you heard of anyone having a problem?

[00:33:57] Nathan Wrigley: No, and that’s pretty remarkable. Have you?

[00:34:01] Andy Fragen: No. Well, yes, yesterday.

[00:34:04] Nathan Wrigley: Deliberately?

[00:34:04] Andy Fragen: Well, it was something we found that we hadn’t honestly considered.

[00:34:08] Nathan Wrigley: But just one individual, so far, that you know of.

[00:34:10] Andy Fragen: So far. And I think I actually no way to mitigate it. Apparently, if you have a redirect to your homepage, the loopback doesn’t work. So what happens is you don’t see a failure, even if there is a failure. And so because you don’t see the failure, because you’re now no longer looking at your actual homepage, you’re looking at a redirect, it might work just fine. And so you don’t revert, and your site might, you know, when you go somewhere else in the site, it might fatal then.

[00:34:40] Nathan Wrigley: Given that WordPress occupies 43% of the web, and that this endeavor of yours, and colleagues working on it, is probably now inside of millions of websites, the fact that you’ve found one character who has been able to show that it didn’t work in a, it sounds like you can mitigate more or less immediately. That’s pretty remarkable. And you’ve just, over the last 40 minutes or so, you’ve done this, it sounds like a detective story almost. Here’s a problem, we tried to fix it, this went wrong, we tried to fix that, this went wrong, we didn’t have the boots on the ground or whatever. You’ve managed to achieve it. And it also feels as if this is the kind of feature update that nobody will ever thank you for, because it’s in the background, if you know what I mean?

[00:35:24] Andy Fragen: Oh, no.

[00:35:25] Nathan Wrigley: Oh, good.

[00:35:25] Andy Fragen: The people that are going to thank us for this are all hosting companies that aren’t going to see these issues anymore.

[00:35:30] Nathan Wrigley: That’s what I meant. It’s more of an invisible.

[00:35:33] Andy Fragen: It is exactly invisible. The user has nothing to do. All they have to do is have auto updates enabled, and their plugins will auto update. If there’s a problem or an issue, it’ll revert back, and all it’ll do is show another update again, in 12 hours it’ll try again.

[00:35:50] Nathan Wrigley: As we said at the top of this interview, it sounds so simple, just roll back when there’s a problem, but now we know.

[00:35:56] Andy Fragen: It’s not that the problem isn’t simple to define, it’s finding all the little pieces in creating the solution that isn’t always simple.

[00:36:04] Nathan Wrigley: Yeah, I remember Kennedy saying, we choose to go to the moon.

[00:36:07] Andy Fragen: Not because we have to, because we want to, or something like that.

[00:36:09] Nathan Wrigley: Yeah, and the problem was hard, but they got over it. And we have echoes of that here. All I can say is thank you so much for making this an important thing. And hopefully, for me at least, and probably everybody else, the more invisible it is in the future of WordPress, in a sense, the better that is.

The less time that I have to worry about plugins updating, the more time that I can concentrate on building the website, and not thinking about those things. And for the millions, millions of people who have no interest in WordPress, but just want a website, this stuff will be remarkable, but probably they’ll never know, which is nice.

[00:36:48] Andy Fragen: You know, honestly our goal is if nobody ever knows about it, perfect. That means it works. No one sees a problem. It hopefully pushes people into clicking that little button link that says, enable auto updates, so that they keep their sites up to date. Because one of the biggest security issues in WordPress is out of date websites, or websites with out of date plugins.

[00:37:14] Nathan Wrigley: Well, dear listener, if you are listening to this podcast, I think there’s a high chance that you obsess about WordPress. So hopefully what Andy has told us today gives you some understanding of the complexities of what’s been going on in the background, but also will make you aware that it happened. If you haven’t been reading the change log, and you’ve just updated to the latest version of WordPress, this fairly consequential, but fairly hidden feature is now available to you free of charge, on the back of Andy’s, and many other people’s labor. So just very quick thank you from me. Thank you for taking the time to do that, and thank you for chatting to me today.

[00:37:46] Andy Fragen: It is certainly not me alone. Colin Stewart has been invaluable, and is a brilliant developer.

[00:37:52] Nathan Wrigley: Well, a profound change to WordPress. Yeah, thank you so much for chatting with me today, I really appreciate it.

[00:37:58] Andy Fragen: You’re very welcome, sir.

On the podcast today we have Andy Fragen.

Andy is a dedicated member of the WordPress community as well as a trauma surgeon. Somehow he manages to balance the demands of his profession with his passion for the community and, as you will hear, to important work inside of WordPress Core. Even while in the operating room, waiting for patients to be prepped, Andy has been known to find moments to answer forum questions and provide support to others. It’s truly remarkable.

Andy talks about the important topic of automatic rollbacks in WordPress, a feature aimed at reverting to a previous version if an automatic plugin or theme update fails, ensuring the website remains functional for users. I’ve managed to encapsulate the idea into the previous sentence, but as you will hear, the execution of that idea was anything other than straightforward.

Andy discusses the origins of the rollback feature. The team working on this problem identified complexities and potential fatal errors during plugin updates and came up with a simple yet effective solution which worked, but as with so much in code, some edge cases meant that the road to a fully workable solution for all WordPress users was not quite in sight. Many times the drawing board had to be dusted off and the problem looked at once again.

While developing this feature, numerous challenges were encountered, from finding consistent test conditions to managing technical limitations. Andy shares insights into the critical role of testing and collaboration with hosting companies, meticulous attention to detail, and problem-solving skills developed to combat issues like file write delays and loopback test redirects.

Andy explains how the team managed to avoid fatal errors in active plugins with extensive testing and incremental improvements. They introduced functionalities like WP error checks, simulation features for testing error handling, and a new move directory function to enhance reliability.

Andy also discusses the broader impact of their rollback efforts. Many users might not notice this new feature, but in a sense that’s how it should be. The more unnoticeable to end-users update failures are, the better. It means that sites that would previously have been broken, are now working, and that’s a win for everyone.

If you’re interested in the behind-the-scenes development of a WordPress feature that quietly keeps your website running smoothly, and in hearing how a dedicated contributor balances his passion for WordPress with a demanding medical career, this episode is for you.

Useful links

Andy’s WordPress.org profile

core-rollback on GitHub

by Nathan Wrigley at October 02, 2024 02:03 PM under podcast

Do The Woo Community: WordPress Accessibility Day with Michelle Frechette, Sarah Kornblum & Ryan Bracey

Episode Transcript

Michelle:
Well, I’m excited because I host a bunch of podcasts. This is my first time guest hosting on the Do the Woo Podcast. So we’re here today at WordPress Event Talk because the three of us are going to be working on a very important event coming up. So who is us? I’m Michelle Frechette. I am the Director of Community Engagement at StellarWP. I’m also the Executive Director at Post Status, but all of that takes a backseat today to the fact that I am one of the organizers for an incredible upcoming 24-hour event on accessibility called WordPress Accessibility Day, coming up on October 9th and 10th. So who is the rest of us? I’m going to ask you to introduce yourselves, tell us a little bit about yourselves, and then we’re going to talk, the three of us, about why WordPress Accessibility Day is so important. Over to you, Sarah. Sarah, tell us a little bit about yourself.

Sarah:
Hi, I am Sarah. I have my own web design company, Two Dogs and a Laptop. Before coming into the WordPress space and the website world, I was a middle school special education math teacher. Accessibility has a very important place in my heart because, given the right tools, anybody can do anything they want to do. So that’s why I am here today.

Michelle:
I love it. I do have one question though. Does that mean you could never get another dog?

Sarah:
Right now, I actually have two fosters.

Michelle:
So it’s temporarily four dogs and a laptop?

Sarah:
Yes, right now it’s four dogs and a laptop. The numbers change every once in a while.

Michelle:
As long as the URL stays the same, it’s all good.

Sarah:
That’s right. The name doesn’t change, but sometimes the number fluctuates a little bit.

Michelle:
Exactly. And joining us today, we also have Ryan Bracy. Ryan, tell us about yourself.

Ryan:
Yeah, my name is Ryan Bracey. I’m the Director of Web Development and User Experience at an agency called Second Melody based in New Jersey. I am also an organizing member of WordPress Accessibility Day, which, as Michelle said, kind of takes front row today.

Michelle:
I’m excited. This is my first time organizing this event. Ryan, this is your second year, is that correct?

Ryan:
Yeah, I was a volunteer three years ago and an organizer the past two.

Michelle:
Oh, so it’s more than, yeah. And Sarah?

Sarah:
This is my first time. I’m new to this space as well.

Michelle:
So, how have you found our organization? It seems like we had our first meeting at the beginning of the year, thinking we had so much time, but now it’s coming up very quickly.

Sarah:
It goes really fast.

Ryan:
It really does.

Sarah:
When we’re talking in January or February, it seems like the event is so far away, and now we’re here, and it’s crunch time. It’s coming up real quick.

Michelle:
It sure is. Comments, Ryan?

Ryan:
No, the same. Yeah, I remember a bunch of our updates being like, “I’m just in a holding pattern right now,” and then all of a sudden, it was every day something new happening. But we’re coming up to it now.

Michelle:
And now we need flight control because so much is happening all at once.

Sarah:
Yes, exactly.

Michelle:
So what are your roles within the organizing team? Sarah, what are you doing?

Sarah:
I am helping June with social media, so I’ve been doing a lot of the social media posting. She does most of it. I’m just here for moral support and backup. But it’s a lot. I don’t know how any one person does it on their own, which is why there’s a team of us, right? Because it’s not possible to do all of this. It’s become such a big day that you need as much help as you can get.

Michelle:
Absolutely. It would be like seven full-time jobs if anybody tried to do it alone. It’s unlikely that one person could handle it all. If anybody could, it’d probably be Amber or Joe, but we’ll talk about them in a little while. Ryan, what’s your role on the team?

Ryan:
I think Amber and Joe did it by themselves for a while, too.

Sarah:
Probably.

Ryan:
I am the team lead for the speakers’ team. My role this year has been receiving speaker applications, reviewing them with my team, making selections, coordinating with speakers, getting them the information they need, adding them to our Slack workspace, and preparing them for the event. We’re also holding practice sessions as we lead up to the day. So, pretty much everything with the speakers is coming through me.

Michelle:
Yeah, 24 hours of programming is all but on your shoulders. I know you have a team, and we all work together.

Ryan:
Yeah, and day of, I’ll just be coordinating with speakers, of course. But yes, it’s not just me, there’s a whole team.

Michelle:
Absolutely. You asked what I do. I am the team lead for marketing. I’ve been doing things like asking people like Bob to let us have an episode of his podcast to talk about the event. We’ve also had great team members on other podcasts and webinars for different companies to spread the word as much as possible. Which brings me to my next question: Why is web accessibility so important? Why should people attend a 24-hour event like this? We don’t expect anyone to listen to all 24 hours live, but why is it important for people to learn more about web accessibility, especially if they don’t have any disabilities themselves? Ryan, what are your thoughts?

Ryan:
A lot of thoughts, but I’ll try to keep it short. So, I’ve been involved in this space for a few years now, probably since 2016 or 2017, when I started to become aware of accessibility. At first, you think it’s just about catering to people with disabilities. But as you dive in, you realize that making a website more accessible improves the experience for everyone. Better contrast, more functional UI components, structured headings—all of these make the site easier to use for everyone, not just those with disabilities. By focusing on accessibility, you put out a much better product, which benefits everyone. At the end of the day, you’re creating something that anyone in the world can use, which is how it should be. There’s a Tim Berners-Lee quote where he says the internet is for everybody, and accessibility is a way to achieve that.

Michelle:
Oh, I like that. Sarah, when we talk about accessibility, I know you and I echo everything Ryan just said. I don’t know if you have anything to add, but we often hear that accessibility compromises design and aesthetics. What are your thoughts about that?

Sarah:
I don’t think accessibility compromises design and aesthetics. If your design can’t be viewed by most people, what’s the point of the design? If you feel it’s a compromise, then the design wasn’t good to begin with. Accessibility means everyone can use it, no matter their background or what’s going on in their lives. Going back to my teaching background, when I made adjustments to help certain students, all the students benefited. It made the material accessible for everyone, not just those who needed extra help. The same applies to websites—accessibility helps everyone, and it’s often overlooked if you don’t personally need it. Accessibility Day starts the conversations that need to be had.

Michelle:
That reminds me of something people often talk about when they say accessibility helps everyone. When curb cuts started to be required for wheelchair users, of which I am one, it also made life easier for people pushing strollers, using pushcarts, or walking with a cane or walker. Curb cuts benefit so many people, not just those in wheelchairs. Isn’t that also true of accessibility features on the web?

Ryan:
Definitely.

Sarah:
So true. And those little plates with bumps on them at curb cuts—those are meant for people with vision impairments, but they help everyone. If you’re texting while walking and you hit those bumps, you’re reminded that a street crossing is coming up. They benefit everyone, not just those with vision impairments.

Michelle:
Absolutely. Ryan, you had something to add?

Ryan:
I love bringing in real-world examples like that. It makes the case for accessibility so much clearer. The web is just an extension of that.

Michelle:
I like to compare it to my experience as a wheelchair user. I walk around my house, but as soon as I go beyond 20 or 30 feet, I need accessibility features. If I approach a building with no curb cut and no automatic door opener, I can’t access it. The same happens on the web—if the tabbing doesn’t work, or the screen reader isn’t accurate, I can’t access your website, just like I can’t access stairs in the physical world.

Ryan:
Yeah, that’s great.

Sarah:
Exactly. And there are so many people who need the help, so you’re losing those potential customers if your website isn’t accessible. If somebody can’t access it, they’re leaving. Just like you wouldn’t try to break down a door to get into a building—you’d just go somewhere else.

Michelle:
We often think of people with disabilities as being born with them or having experienced some tragic accident, like becoming blind or using a wheelchair. But the truth is, most of us—or I’ll say many of us—will end up with some kind of disability as we age. For instance, a large portion of the population will need glasses as they get older. And I think my generation, and younger ones, will experience this even more rapidly because of our constant screen use. This is anecdotal, but from my own experience, I now wear not only glasses for the computer but also bifocals. That didn’t happen because I was born with vision issues—it’s from years of screen use and aging. So, web accessibility benefits all of us as we grow older and need things like larger fonts and better contrast.

Ryan:
That’s a great point. Microsoft has an Inclusivity Handbook, which is excellently written, and they break down user impairments into categories: visual impairment, hearing impairment, motor impairment, cognitive impairment. But then they also talk about the temporality of those impairments, meaning that you can have a permanent disability, a temporary disability, or even a situational one. For instance, if someone breaks an arm, that’s a temporary disability. Or if you’re a new parent, breastfeeding a child, you temporarily can’t use both hands, so you have a motor disability. Situational impairments might be something like being on a noisy train and not being able to hear your phone, so captions become really important. Accessibility helps everyone, even in temporary or situational contexts.

Sarah:
I love how you mentioned situational and temporary disabilities, because those are so often overlooked. When people think about disabilities, they tend to only consider permanent disabilities, but there are so many times when a temporary or situational disability affects someone’s ability to use a website, and accessibility helps in those moments, too. For example, if you’re on the subway, you can’t listen to something at full volume, so you need captions. Accessibility just makes life easier for everyone.

Michelle:
Exactly. And every time you consider these things, you increase the number of users your website reaches by making it accessible.

Michelle:
I live in a condo built in 1988, and every door handle is just a knob. I walk with a cane, so if I have something in one hand and my cane in the other, I have to put something down to turn the doorknob. I just ordered brand-new handles with levers so that I can hit them with my elbow and open the door without putting anything down. It’s a simple fix, but it makes a big difference. It’s the same with web accessibility—it’s often about small changes that make things much more accessible.

Sarah:
You just have to be careful not to make the doors too accessible for your cats! They might learn how to open them, and then you’ve got a whole new problem.

Michelle:
Right, especially when you have guests in the restroom—awkward! But yes, you’re always being observed if you live with pets.

Ryan:
I love the door example. Those are called Norman doors—doors that are confusing to use. It’s a user experience concept introduced by Don Norman in the ’90s. His example was how you don’t know whether to push or pull a door when you walk up to it. Your example ties into that—it’s about making doors, or anything, easier to use.

Sarah:
Exactly.

Ryan:
Something as simple as a door.

Sarah:
And even with keyless entry cars now, I never take my car key out anymore. It used to be a hassle to find it in my bag or pocket, but now I just walk up to the car, and it opens. Accessibility can be like that—it makes things easier for everyone.

Michelle:
I need one of those cars! My next car will definitely have more features.

Michelle:
But bringing it back to WordPress Accessibility Day—Ryan, you’re the speaker wrangler, the lead speaker organizer, as we might say in WordCamp talk. What are some of the things we can look forward to that day?

Ryan:
Oh boy, this is a hard question for me because I love all my speakers equally! But yes, I’ll start with the keynote. Our keynote speaker this year is Lainey Feingold, a disability rights lawyer. She’s going to talk to us about the legal landscape surrounding web accessibility, which is really in flux right now, especially with new European laws coming out. Lainey has been involved in accessibility since the early ’90s. One of her major accomplishments is the braille on ATM machines—that was because of her advocacy. So she’ll be kicking off the entire event. It’s definitely a session to attend if you can.

We also have a wide range of topics that cover everything from beginner to expert levels. Whether you’re a content creator, designer, developer, product manager, or team manager, there’s something for you. The full schedule is up now, and you can also register on the website.

Michelle:
I love that. Sarah, what are some of the topics you’re excited about?

Sarah:
Oh, there are so many that I want to stay up for all 24 hours just to catch them all. It feels like if I’m not there live, I’m missing out. But honestly, there’s so much I want to see!

Michelle:
Same here. As a non-developer, I’m not as interested in those more technical talks, but I’m excited for developers to hear them. I’m a content marketer, so I’m most excited about the sessions on content and design, but I plan to catch as many as possible.

Ryan:
I know, it’s hard to pick favorites. But if you can’t attend live, don’t worry—all the sessions will be available on YouTube afterward, and we’re striving to have them translated into as many languages as possible. So if anyone listening speaks another language and would like to volunteer to help with translations, that would be a great way to contribute!

Michelle:
And during the live sessions, we’ll have human live captioning, so the transcripts will be accurate. We’ll also have live ASL interpretation on screen during the event. While we recognize that there are different sign languages around the world, for this event we’ll be using American Sign Language (ASL). I’ve also been busy recording all the intros for the sessions that will be on YouTube afterward, so you’ll hear my voice introducing speakers and thanking our sponsors.

Sarah:
Wow, that’s a lot of work!

Michelle:
Yes, the dulcet tones of Michelle Frechette! (laughs) But seriously, it’s been a lot of fun. And speaking of which, Sarah, tell people how they can register and what they can expect.

Sarah:
It’s a completely free event! You just need to register ahead of time. The registration link is 2024.wpaccessibility.day/register/. It’s a big register button, so you can’t miss it.

Michelle:
And Bob assures us that all the links will be in the show notes for this episode, so you can find them there as well. Sarah’s wearing our official T-shirt for this year that says “Focus: It’s a Feature, Not a Bug,” which is a fun inside joke for developers.

Ryan:
Yes, it comes from people reporting the focus outline (the box around links when tabbing) as a bug, when in fact it’s a feature for accessibility.

Sarah:
Exactly! Focus outlines aren’t a design flaw—they enhance the design by making it easier for people to navigate the site.

Ryan:
I still get that comment on almost every website.

Michelle:
And if you want a shirt like Sarah’s, you can get one when you register with a donation of $50 or more. All the funds go toward running the event—paying speakers, interpreters, and captioners, and covering the costs of the website and other resources.

Ryan:
Yes, and no one on the organizing team pockets any of the money. We do this because we love the community and accessibility, and we want to help others.

Sarah:
If this event had a paid staff, it would cost money to attend, but we’re all volunteers.

Michelle:
Exactly. Any donations go toward making the event possible. And because we operate under the umbrella of a nonprofit, donations are tax-deductible. It all goes back into the event to keep it going year after year.

Michelle:
October 9th and 10th is coming up fast! Ryan, what time does the event start?

Ryan:
It starts at 14:45 UTC, which is 10:45 AM Eastern time.

Michelle:
And are all of our speakers from North America?

Ryan:
No, we have speakers from 12 different countries this year, which is three more than last year. We’ve made a strong effort to branch out, and we have speakers from Europe, Africa, Asia-Pacific, Australia, Canada, South America—we’re very international this year.

Michelle:
That’s awesome! I think around 25% of our speakers also identify as disabled, which I think is really cool.

Ryan:
Yes, I have all the stats. We have 37% of our speakers identifying as male, 57% as female, 7% as non-binary, and 3% as trans. Additionally, 17% of our speakers are non-white, and 23% identify as living with a disability.

Michelle:
And all of that information was volunteered by the speakers themselves.

Sarah:
What other stats do you have for us?

Ryan:
Four of our speakers are first-time speakers, which is very exciting!

Michelle:
That’s amazing!

Sarah:
We’ll definitely need to show up and give them extra support.

Ryan:
Exactly.

Sarah:
And we can ask questions, right? This is a live event.

Ryan:
Yes, all the sessions are live, and there will be time for Q&A at the end of each talk. We’re asking our speakers to limit their talks to 30 to 45 minutes so there’s about 10 minutes for questions. There will also be breaks between sessions.

Michelle:
I’m going to try to stay up for all 24 hours, but we’ll see how that goes!

Sarah:
All-nighters aren’t kind to us anymore!

Michelle:
Exactly. Any final thoughts, Ryan?

Ryan:
We’re just really excited for this year and hoping for a huge turnout. There’s no limit on registration, so if you’re interested, definitely sign up! Whether you’re new to accessibility or an expert, there’s something for everyone. You can also volunteer or donate to support the event.

Sarah:
I’m super excited for this event! It’s my first time attending live, and I can’t wait to experience it.

Michelle:
It’s going to be great! Thanks to both of you for joining me today, and thanks to Bob Dunn for letting us take over this podcast spot to talk about WordPress Accessibility Day. We’ll see everyone on October 9th!

Ryan:
Yeah!

Sarah:
Yay!

In this episode of Do the Woo, Michelle Frechette, guest hosting for the first time, joins fellow WordPress Accessibility Day organizers, Sarah Kornblum and Ryan Bracey, to discuss the upcoming 24-hour event on October 9th and 10th, 2024. Together, they chat about the importance of web accessibility, the challenges of organizing a global event, and the various ways accessibility improves the user experience for everyone.

Whether you’re a developer, designer, or content creator, this episode highlights why WordPress Accessibility Day is an essential resource for anyone in the WordPress community.

Takeaways

Web Accessibility Benefits Everyone: The hosts emphasize that web accessibility is not just about helping people with permanent disabilities but improves the experience for all users. Features like better contrast, structured navigation, and user-friendly designs make websites easier to use for everyone, including those with temporary or situational impairments.

Small Changes Can Make a Big Difference: Simple adjustments, both in physical spaces and on the web, like curb cuts or focus outlines, improve access for a wider audience. Accessibility features benefit all users, not just those with specific disabilities.

WordPress Accessibility Day is Global: The event has speakers from 12 different countries, showcasing diverse perspectives on accessibility from around the world. This international focus enhances the inclusivity of the event and the information shared.

It’s a Free Event with a Wide Range of Topics: WordPress Accessibility Day covers accessibility for all levels—from beginners to experts. There are sessions tailored for content creators, designers, developers, and team leaders, making it a valuable resource for anyone in the WordPress community.

Inclusivity Goes Beyond Design: Beyond aesthetics, accessibility is about creating websites and digital experiences that everyone can navigate and use. Good design doesn’t compromise accessibility—it enhances it.

Live and Accessible: All sessions at WPAccessibility Day will feature live human captioning, live ASL interpretation, and will be made available on YouTube afterward with translations in multiple languages, ensuring the event is accessible to as many people as possible.

Opportunities to Get Involved: Listeners can volunteer, help with translations, or donate to support the event. This community-driven approach helps make the event free and accessible to all while ensuring that speakers, interpreters, and captioners are compensated for their work.

Links to WordPress Accessibility Day

Connect

by BobWP at October 02, 2024 09:18 AM under Accessibility

October 01, 2024

Do The Woo Community: Tips for the Anonymous Product Developers About Page

This is a pet peeve of mine. Being a visible player in the WooCommerce (and WordPress) space, I am inundated with requests to look at stuff, connect, offer advice, all of which I’m cool with. I also keep my eye on what’s happening out there. Often this all happens on social media. But regardless of the quality of the product, there is one thing that bugs me.

Who are you?

This has happened a lot of times to me. And it happened again, so it’s fresh in my mind. a month or so ago. I was on X, saw a Woo plugin that I have never heard of and I clicked through to the site. Typically, I do two things. I glance at what the extension does, then I find out who created it. I look for the about page.

But as so often happens, there is nothing about the person, team or business behind it. Now I understand that a lot of developers are introverts. And sometimes writing about themselves can be challenging, but yet…

Absolutely nothing.

Where is the online authenticity?

Guess what people? I am not going to use— or buy— your product out of the blue, even if I really need it. Unless you tell me who the heck you are.

In that last example, I did a bit more investigation and in a roundabout way figured out it was the person who had originally tweeted it. But he didn’t make it easy.

And it didn’t change my mind about using it. Sorry.

And not too long ago I saw a different tweet. There was no link for a handle to the plugin’s Twitter page. Lo and behold, in the description, I found who created it. Following through to the site I was kept in the dark there with little information.

I cannot say if other people are like me or not. But I can only wonder if there is some specific reason you don’t want to let me know you are behind this plugin? Do you really think I will snag it up without any proof of credibility? And I’m not talking an about page that says something like:

We are a dedicated team of WooCommerce developers who really understand your needs and wanted to give you a solution that would make your life easier.

And that is it. Well, blah, blah, blah.

About pages are important. Otherwise, in the whole scheme of things, you are just another speck of dust in the cosmic universe. So, please tell me, who are you . It will certainly help you and just may put a few more bucks in your pocket and build that needed trust.

by BobWP at October 01, 2024 07:50 AM

WordPress.org blog: WordPress 6.7 Beta 1

WordPress 6.7 Beta 1 is ready for download and testing!

This beta version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, set up a test environment or a local site to explore the new features.

How to Test WordPress 6.7 Beta 1

You can test Beta 1 in any of the following ways: 

WordPress Beta Tester Plugin Install and activate the WordPress Beta Tester plugin on a WordPress install. Select the “Bleeding edge” channel and “Beta/RC Only” stream.
Direct DownloadDownload the Beta 1 version (zip) and install it on a WordPress website.
Command Line (WP-CLI) Use this WP-CLI command: wp core update --version=6.7-beta1
WordPress PlaygroundUse a 6.7 Beta 1 WordPress Playground instance to test the software directly in your browser. No setup required–-just click and go!

The scheduled final release date for WordPress 6.7 is November 12, 2024. Your help testing Beta and RC versions over the next six weeks is vital to ensuring the final release is everything it should be: stable, powerful, and intuitive.

How important is your testing?

Testing for issues is a critical part of developing any software, and it’s a meaningful way for anyone to contribute—whether or not you have experience.

If you encounter an issue, please share it in the Alpha/Beta area of the support forums. If you are comfortable submitting a reproducible bug report, you can do so via WordPress Trac. You can also check your issue against a list of known bugs.

Curious about testing releases in general and how to get started? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

WordPress 6.7 will include many new features that were previously only available in the Gutenberg plugin. Learn more about Gutenberg updates since WordPress 6.7 in the What’s New in Gutenberg posts for versions 18.5, 18.6, 18.7, 18.8, 18.9, 19.0, 19.1, 19.2, and 19.3.

What’s New in WordPress 6.7 Beta 1

WordPress 6.7 Beta 1 contains over 500 enhancements and over 500 bug fixes for the editor, including more than 200 tickets for WordPress 6.7 Core. Here’s a glimpse of what’s coming:

Meet the Twenty Twenty-Five theme

Launching with WordPress 6.7, the new default theme, Twenty Twenty-Five, embodies ultimate flexibility and adaptability, showcasing how WordPress empowers you to tell your story with a rich selection of patterns and styles. Inspired by glimpses of natural beauty and ancestry heritage, it evokes ideas of impermanence, the passage of time, and continuous evolution–mirroring life’s journey. Experience effortless site creation with Twenty Twenty-Five and follow its progress or report issues on this GitHub repo.

Zoom Out to Compose with Patterns

The Zoom Out view simplifies your editing experience by allowing you to create and edit at the pattern level rather than focusing on individual blocks. Easily toggle this view from the toolbar to streamline your site-building process, making it faster and more intuitive to design pages using patterns.

Media improvements 

Now supporting HEIC image uploads–automatically converted to JPEG for maximum compatibility–you can add high-quality images without worrying about browser support. Plus, enjoy auto-sizing for lazy-loaded images and expanded background image options at both individual and global levels, giving you greater control over your site’s visuals and performance. 

Expanding Block Supports

Several blocks now come with expanded support options, enabling even more design possibilities. Notably, the long-requested shadow support for Group blocks has been added, a big win for designers and theme developers!

Preview Options API 

The latest WordPress release enhances the Preview Options in the block editor, empowering developers to customize content previews. A new API allows plugins and themes to add custom items to the preview dropdown menu, enabling users to see content in different formats or environments. This flexibility enriches the editing experience while maintaining the existing familiar Preview dropdown structure.

Refined Data Views

The Data Views introduced in 6.5 continue to be improved. This release is focused on refining the experience with a few new features aimed at making these views more flexible for customization and more functional to use. 

Manage Block Bindings Directly

Updates to this API in 6.7 polish and open most of the underlying APIs, improving the overall user experience, and add a user interface (UI) that allows you to connect attributes with custom fields to their binding sources. This new UI makes it possible to create bindings directly in a block instead of needing to use the Code Editor. By default admin and editor users can create and modify bindings, but this can be overridden with `block_editor_settings_all or map_meta_cap` filters.

Simplified and Smarter Query Loop Block

The Query Loop block is improved, as it now automatically inherits the query from the template by default, eliminating the need for manual configuration. This means your posts display immediately in both the editor and on the front end, streamlining the process so users can focus on content without extra configuration needed.

Edit and Control Font Size Presets

An enhanced Styles interface allows for greater flexibility when creating, editing, removing, and applying font size presets. You can now easily modify the presets provided by a theme or create your own custom options. A key feature is the ability to toggle fluid typography, which enables responsive font scaling with additional options for finer control over responsiveness.

View Meta Boxes in the iframed Post Editor

A new split view option has been introduced that allows you to access both the editor canvas and metaboxes while editing. This change will provide a consistent WYSIWYG experience between the editor and front end views.

Template Registration API

With this release, developers can now more easily register custom block templates without complex filters. Streamline your development process and create custom templates with ease. 

The features included in this first beta may change before the final release of WordPress 6.7, based on what testers like you find.

Get an overview of the 6.7 release cycle and check the Make WordPress Core blog for 6.7-related posts in the next few weeks for further details.

Vulnerability bounty doubles during Beta & Release Candidate

The WordPress community sponsors a monetary reward for reporting new, unreleased security vulnerabilities. This reward doubles during the period between Beta 1 on October 1, 2024 and the final Release Candidate (RC) scheduled for November 5, 2024. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.

Just for you: a Beta 1 haiku

Lines of code arise, 
Testing shapes the future path,  
WordPress grows once more.

Props to @annezazu, @cbringmann, @colorful-tones, @courane01, @desrosj, @marybaum, and @priethor or reviewing and collaborating on this post!

by David Baumwald at October 01, 2024 04:41 AM under releases

September 30, 2024

WPTavern: InstaWP Announces the World’s First WordPress Online Hackathon ‘AnyoneCanWP’

InstaWP, known for its innovative one-click WordPress sandbox launcher, has launched AnyoneCanWP, the world’s first online hackathon dedicated to WordPress development. Registrations are open now, and participants can submit their projects until October 26.

The hackathon will officially begin on October 11, 2024, with a keynote address by Joost de Valk, founder of Yoast SEO and a pivotal figure in the WordPress ecosystem. This sets the stage for an engaging competition where developers and designers can showcase their skills.

Important Dates

  • Hackathon Start Date: October 11, 2024
  • Submission Deadline: October 26, 2024
  • Public Voting Period: October 18 – October 28, 2024
  • Final Presentations and Judging: November 10, 2024

To participate, individuals must first register with an email address to receive official details and an invitation. Participants can create their projects using InstaWP’s 1-click sandbox launcher. Projects must be completed within a 15-day timeframe using only free plugins and themes.

During the public voting phase, which runs from October 18 to October 28, participants can promote their projects and engage with the community to gather votes.

The hackathon jury includes WordPress celebrities, including Miriam Schwab (Head of WordPress Relations at Elementor and co-founder of Strattic), Jamie Marsland (Head of WordPress YouTube), Davinder Singh Kainth (curator of the WP Weekly newsletter), and Anne-Mieke Bovelett (Accessibility advocate and multilingual WordPress expert).

The winner will take home $3,000, with second and third places receiving $1,000 and $500, respectively. All top ten participants will also get InstaWP credits and additional partner credits to elevate their WordPress projects and services. Plus, the top winners will receive a complimentary one-year premium account with InstaWP, unlocking a suite of advanced features and tools.

The event is sponsored by Automattic, who also provided seed funding to InstaWP in 2022. For more information and to register for the hackathon, interested participants can visit the official website.

by Jyolsna at September 30, 2024 06:34 PM under hackathon

Do The Woo Community: The Do the Woo Lunch

For the first time, we had a invite-only lunch during the recent WordCampUS 2024. We invited our sponsors, hosts and some DTW friends. Having it during the day, and on Showcase Day, gave more opportunity to for people to fit it into their schedule. But of course, some were not able to make it as there is so much going on with meetings and other get together. But we are so happy that we were able to do it.

What was absolutely amazing is that our sponsor Avalara stepped up to sponsor the lunch. Oliver St. George who lives in Seattle is very familiar with Portland as he has lived there as well. So he was able to find us a room at the Spirit of 77, across from the convention center.

Avalara is an exclusive sponsor of our Scaling Enterprise: WordPress & OSS and a shared sponsor of Woo DevChat.

So a huge thank you to Avalara!

And check out some photos from the lunch. (We will be adding more soon)

And if you would like to see more photos from BobWP from WordCampUS 2024, check the gallery out here.

by BobWP at September 30, 2024 09:12 AM

Gutenberg Times: Gutenberg Changelog #108 – Gutenberg 19.3, WordPress 6.7 – Block Themes for Agencies, WordCamp Asia

In this episode, Birgit Pauli-Haack and JC Palmes, engineering manager at WebDev Studios, discuss Gutenberg 19.3, WordPress 6.7 – Block Themes for Agencies, and WordCamp Asia.

Add a summary/excerpt here

Show Notes / Transcript

Show Notes

JC Palmes

Announcements

What’s released:

Stay in Touch

Transcript

Birgit Pauli-Haack: Hello, and welcome to our 108 episode of the Gutenberg Changelog podcast. In today’s episode, we will talk about Gutenberg’s 19.3, WordPress 6.7 briefly, block themes for agencies in WordCamp Asia. I’m your host, Birgit Pauli-Haack curator at the Gutenberg Times, and a full-time core contributor for the WordPress Open Source project sponsored by Automattic. For the first time on the show, I have a great pleasure to introduce to you, dear listeners, JC Palmes. She’s one of the local leads of the WordCamp Asia 2025, and in her day job, JC works as the engineering manager at WebDev Studios. Welcome to the show, JC. How are you today? How’s the weather in the Philippines?

JC Palmes: Hi, Birgit. Thank you so much for having me. It’s a real pleasure to join you on the show. The Philippines is still very warm today. Well, warmer than usual. We are supposed to have a typhoon coming up.

Birgit Pauli-Haack: Oh, no. Oh, no. So the Philippines is in the tropics, right? So it’s similar to Bangkok from the weather in Florida.

JC Palmes: More or less. Yeah.

Birgit Pauli-Haack: Yeah. All right. So the Philippines, I don’t know a lot about the Philippines that will change when I come over for WordCamp Asia, but the Philippines comprises of about 7,000 islands. So where do you live?

JC Palmes: Yeah. It’s 7,641 islands to be exact. It changes on a decade to decade basis, I guess. But yeah, I am in the Panay Island in the city of Iloilo and it’s a small island, but it’s a vibrant hub for tech and innovation. Yeah. It’s not as traffic heavy as Manila, which you will experience next year. You’ll love the people here if we come to visit.

Birgit Pauli-Haack: Oh, I’m sure about it. Yeah. But when you say you’re active in the community, so you organized WordPress meetups in Iloilo, and you also organized or started the WordCamp Iloilo. When did this all happen?

JC Palmes: We organized WordPress Iloilo Meetup Group around August 2016, 2017.

Birgit Pauli-Haack: You almost at eight years.

JC Palmes: Yeah.

Birgit Pauli-Haack: Over eight years.

JC Palmes: Started our first WordCamp in 2018.

Birgit Pauli-Haack: Oh, wow. Yeah. And then you had one 2019, right?

JC Palmes: Yeah. We did.

Birgit Pauli-Haack: Yeah. Did you also organize one after the pandemic?

JC Palmes: Yes, we did. We organized… Well, we had one last 2023 and opted not to do 2024 because WordCamp Asia is going to be in the Philippines and most of my local organizers here are also organizers in WordCamp Asia and volunteers as well. So it’s a lot to ask them to pay local WordCamp as well as the flagship one.

Birgit Pauli-Haack: Yeah. No, I wouldn’t have thought that there would be a local one when there is a regional one, because that takes a lot of out of you as an organizer or especially a lead organizer, but also if you just going to have a team organizing role, it’s a lot of work and you don’t want to lose focus on that. Yeah. I totally get it. Yeah. So yeah, we had the last month we got together because I connected with you about two things, right? There was one was the webinar for WebDev Studios on the lunch-and-learn.

And then we also discussed, I read the article by Lisa Sabin-Wilson on the website, WebDev Studio that you started to have working with Block Themes. And then when I read through the article, I found that you had created a starter theme that your agency is going to use for projects. So today I want to talk to you a little bit about it because we get a lot of questions about how agencies work with Block Themes and all that. So I just wanted to, being with the source as the engineering manager, I think you had a major role in putting that together.

JC Palmes: Yeah. WDSBT was, well, it’s kind of a brainchild between Lisa, me, and Mitch, our director of engineering, and it’s a starter theme. We stands for, of course, WebDev Studios Block Theme. And the goal really was to create a flexible block-based foundation that fully embraces modern WordPress capabilities while also allowing for highly customizable websites. When we initially started this, we started with Brian Gardner’s Powder theme for inspiration. But because I spearheaded the project, and really when I started this, I was learning about Block Themes, and as I go along, I found that instead of changing, adding into the Powder theme, we needed to make it entirely our own ’cause we have a design system and we need to make sure that the theme that we are going to create aligns with that design system. So the original setup with the Powder theme didn’t really align with the vision, so it was mostly overhauled by me. So…

Birgit Pauli-Haack: Tell me a little bit about the design system, because a lot of people think about design system that is not in WordPress, but maybe in Figma or in some other design tool. How are you working with that? Is that something that you now built into the Block Theme or is it separate?

JC Palmes: It’s built into the Block Theme. So what we did was take that design system, so the design system was created with blocks in mind. We have sort of redesigned the core blocks in a way that it would be easier for us to create the components that we mostly use in our projects and would be easily extendable based on, of course, on a project-to-project basis because every project is different, but all of the elements in a component are going to be the same. And the core blocks as is with our design is pretty solid, but we needed more. Well, clients needed more, and that is what our design system allows us to do. And by integrating that with the theme, it just makes our work with whatever design our senior UX designer, Jennifer Cooley creates and just makes things easier and faster.

Birgit Pauli-Haack: Mm-hmm. Excellent. Excellent. So when you put this together, how long did it take you to from learning about Block Themes in zero learning to, “Okay. We have a solid foundation for our projects.”

JC Palmes: It took me probably around two, three months. It would probably take a lot, well, it would probably be faster if I already knew the structure. And I’m saying that because I’m dyslexic, so I work with patterns and learning new things kind of takes me out of my comfort zone. But because of how Block Themes in general are structured, it’s structured enough for me to pick up the patterns right away. And it took two, three months before we are actively using it on projects. So we’ve used it on three successful projects so far, launched projects.

Birgit Pauli-Haack: So what did you find coming from the classic theme in the agency? So what you found easy to do with or easier maybe in switching to Block Themes and what did you think was very hard?

JC Palmes: So what was relatively easy is the process of working with native WordPress blocks. That’s the mouthful. Again, my brain works with patterns, right? I’m not sure if it’s going to be the same for other engineers, but that was what’s easy for me. And because of that, it kind of provided us with a solid foundation and really allowed for quick implementation of reusable design elements, which is integrated in our design system. And what was hard, of course, was transitioning from our wd_s PHP-based framework to a block-based approach. Although before it was transitioned into Block Themes already. It was a hybrid theme, but we were mostly using it for PHP based framework still, but transitioning meant rethinking of the entire development process, and that takes a while for it to click, and we are getting there. Again, as I mentioned, we’ve successfully launched three projects. One of those is a really big site and well, the last project that we launched is the first TrueBP Build where we did not really use any shortcuts, I guess.

Birgit Pauli-Haack: Good. Good. Good.

JC Palmes: And it’s also probably one of the most successful launches that we’ve had with regards to performance and page speed and all those fun stuff. It’s a site with 18,000 plus users and it got 100 performance scores on page speed and 93 on mobile, 100 on desktop, 93 on mobile, and 93 on mobile was big.

Birgit Pauli-Haack: Yeah.

JC Palmes: Yeah.

Birgit Pauli-Haack: That’s awesome. Congratulations. Yeah.

JC Palmes: Thank you.

Birgit Pauli-Haack: So you have a team of developers that also had a different level of familiarity with Block Themes and blocks. How did the transition work for them? What were the blocks mostly?

JC Palmes: Yeah. So the team that I worked with at WebDevs teachers for this particular project are, well, all of the engineers that I have on WebDevs teachers are amazing developers. The theme that created this site already established in Block Themes, although didn’t have the actual experience of building one for clients. They built one personally as I did, and I worked with them closely to make sure that we learned together.

Birgit Pauli-Haack: Excellent.

JC Palmes: That’s best, right?

Birgit Pauli-Haack: Mm-hmm. Yeah.

JC Palmes: And there were a lot of gutters we had to pull in Ryan and Nick. 

Birgit Pauli-Haack: You mean Ryan Welcher and Nick Diego?

JC Palmes: Ryan Welcher. Yeah. Ryan Welcher helped us a lot and figuring things out, especially with Block Bindings, that unblocked a lot of stuff for us.

Birgit Pauli-Haack: Yeah. Block Bindings, so it’s amazing, especially because it works so much with the meta fields and you can have your own data sources. Yeah. So what I often heard from agencies is that they don’t use core blocks, but that seems to be different in yours, in your case, that you mostly base it all on native core blocks and only have variations and primary block styles that you extend them to or with. So I think that’s a great way to leverage all the work that the developers do in core to bring those forward and you can build your sites on it. 

The last question I have on that, and then I think we can move on unless you want to say something more, is so with the Block Themes, there is also your clients are now able to create their own templates or modify the templates. Is that all open to them or what’s the training about? What’s the implementation at the clients? What’s the process there to give them that freedom?

JC Palmes: It’s open to them, but we did add in some guard rails, particularly with what we’ve set in theme Jason, but then again, it’s WordPress, it’s open for clients this time around. We did not sort of think deeply, I guess? That’s the only word they can really think of right now. Features are with a website that is designed for clients, you’ll have to be very careful with telling them what to do, how to use this block, how to figure things out.

And with Block Themes, because they’re able to just create an entire template at an entirely new header and all those stuff, we made sure that we have all of the documentation ready for them. Documentation that is part of WordPress, we just give them the link to that because you don’t have to change it out. It’s all there for them to read. We fully document any custom block that we create. And also all of the custom blocks that we do are also just core blocks. We opted to always do core blocks first if it’s doable, and just go the other route if not. But so far we were able to do everything just using core blocks.

Birgit Pauli-Haack: Core blocks. Yeah. Wonderful. Excellent.

JC Palmes: And clients showing them how to use the website and with Block Themes, we thought was going to be hard. It wasn’t it. They were very happy with just having that freedom and being that it’s intuitive enough for them to just go in and add in their content. It’s just amazing to see.

Birgit Pauli-Haack: Yeah. So when you have one of these large projects, how many block patterns do you… What’s the good number that you use there? Is it 25 or is it 50 or is it… Yeah. I heard other people have 58 patterns in there, or 58 new blocks.

JC Palmes: Oh wow. That’s a lot.

Birgit Pauli-Haack: Yeah.

JC Palmes: Because we are leveraging core blocks, we are actively using them for everything. We have variations. So BT, WSBT, we can add in variations with just a couple lines of code and eight variations that variations and block variations. You don’t really need to create that many patterns or blocks because then they’ll be able to just use it. But of course, if there’s a sub layout, we create a pattern for that, a template pattern so that they can just add that in a page and then just change things around. I’m not exactly sure how many patterns we did for this site. I know that it’s not 50 plus, it’s less than that.

Birgit Pauli-Haack: Okay. All right. Okay. So if listeners are interested in learning from you, and I know developers like to look at code and theme developers even more, especially your theme JSON and how you set up all the assets. And so your theme is available on GitHub, that’s public record, right?

JC Palmes: Yes.

Birgit Pauli-Haack: It’s in a public record.

JC Palmes: It is public now. It was silently public for the past few months, and then we opened it up publicly release this post when we set out version 1.0, and it’s that to go up to 1.5 by this week with some modifications with the versioning cache buster, and then fix this particularly to the mobile menu because that needs a lot of love.

Birgit Pauli-Haack: It does. Yes. Yes. Absolutely. Yeah. Especially when you have things that are you want on a desktop, but you don’t want them on the mobile and you want to kind of stack things differently in a different order. It’s really hard to implement that. Yeah. Totally get it.

JC Palmes: Yeah.

Birgit Pauli-Haack: Yeah. So I will show in the show notes if that’s okay with you, the GitHub repo for the WDS-BT theme. Well, maybe you could come up with a cuter name.

JC Palmes: We just really call it BT.

Birgit Pauli-Haack: Yeah, of course. Block Themes, I get it. Yeah. And it’s the acronym from your company, WebDev Studio.

JC Palmes: Yeah.

Birgit Pauli-Haack: Totally get it. I will share that. And I also will share, again, the link to the article that Lisa Wilson put together in the show notes so you can kind of look through it to your listeners. But I find it very interesting to talk to you about that. So thank you for sharing all your insights on that.

JC Palmes: Thank you.

Announcements

Birgit Pauli-Haack: So dear listeners, we have a few announcements for you, and it’s mostly about what’s published. So there’s a data views update number two, has been published on the design make blog with new updates on cam-sounds like what are new features on the data views. There’s some great work being done there. You can catch up with that. So it was the primary filter visibility has been changed. Then you can reorder table columns and view options. So you can hide columns, a feature that was available in the WP admin, but not always all columns and not always all columns are in there, so you can get them in and out.

And then also have a featured image and the title field in the display for pages. And then you can pin columns and rows. And the advanced filtering is really great. You can have and and/or filtering categories in tag or is any out of particular list of tags. So when you’re looking at the 2,000 or 20,000 blog posts, you can narrow down the filtering quite a bit in the admin section there. So check it out, I share it in the show notes. Then there’s two more posts on the developer blog. So if you went to block development more on the beginner side, there’s an article on how to build a multi block plugin.

So with the create-block scaffolding tool, we had a similar article about two months ago, but this is a little bit of a different approach. So you get more variations on how you can approach that, and it’s really great because it gets you step by step through that tutorial. Troy Chaplin is a new writer on the developer blog, and he is from Ottawa, Canada and is writing on the second blog now… blog post. And the second blog post was actually the second part of a series on data views on how you as a plugin developer can use it for your plugin in the admin section. So the first part came out a month ago, like using data views to display and interact with data in plugins. And then the second one is called actions from data views. So how to add the image that you bring in from the data into a media library.

So it’s kind of an app pretty much that you can build there. It’s a React app and you get through in the tutorial from beginning to end. So it’s a really interesting series of blog posts. And with that, there was a data views developer hours where both JuanMa Garrido wrote the two articles that I just mentioned. But then there was also Nick Diego was in the developer hours, and Andre Manero who’s one of the developers who put this all together. And the recording I will also share in the show notes. And the last announcement… it’s not the last announcement, the second last announcement is you take it’s about WordCamp Asia.

WordCamp Asia

JC Palmes: Oh, yeah, right. Okay. WordCamp Asia. So the next batch of tickets for WordCamp Asia 2025 will be released on October 3 at 12:00 PM Philippine time. I’m not sure what that is in UTC. I’m really bad with time zones.

Birgit Pauli-Haack: Oh, it’s kind of earlier in the day. It’s in the morning. Yeah. So October 3rd in the morning is the ticket release. Yes. Yeah. Awesome.

JC Palmes: With those who don’t know WordCamp Asia 2025 will be held at the PICC in Manila Philippines from February 20 to 2022… No, 20 to 22, 2025. So yeah, be sure to mark your calendars and secure your tickets as soon as they’re available. Maybe we can talk, if you see me just say hi.

Birgit Pauli-Haack: Yeah. And I just saw on Twitter a series from Sushi about the photos of the walkthrough of the organizing team in Manila. So it was, if you follow him on Twitter, I can share some links that as well in the show notes. So you can see how grand this convention center is where the conference will be held. So I’m really looking forward to that.

JC Palmes: Yeah. They’re doing that today. I did fly out because, well, I need to fly again in the next couple of weeks. But then again, also I do have one more thing with WordCamp Asia 2025, you’re also still looking for sponsors.

Birgit Pauli-Haack: Okay.

JC Palmes: Yeah. So if you or your company are interested in supporting the event, feel free to reach out. I’d love to discuss how you can get involved.

Birgit Pauli-Haack: Yeah. And I’ll link the call for sponsors page in the show notes so you can check it out what the options are for different levels and all that and what’s all included into the sponsor packages. I think that helps. No, that was really good. Thank you. Well, that’s a few months to go. So some people are really late in their decisions and it’s the next year, so their budget is not out yet. So I can understand that some people are a little bit hesitant to get this going. So the speaker is also, you got a lot of submissions I heard for speakers.

JC Palmes: A lot.

Birgit Pauli-Haack: Yeah. Was it more than last year?

JC Palmes: I haven’t checked yet. So I’m mentoring sponsors, operations and the technology team. Global leads are sponsoring other teams. And then one of the local leads as well, Andrew is he is mentoring venue, which takes a lot.

Birgit Pauli-Haack: Oh, yeah.

JC Palmes: So we all have our hands full. We are getting there. We have an amazing set of organizers as usual, and I can’t wait to see them.

Birgit Pauli-Haack: Yeah. I’m so grateful that everybody puts things together. And the two WordCamps Asia that I… ’23 and ’24 were just amazing. And I had a great time and it was great to talk to everybody there. And they were also open. And yeah, I’ve made a lot of new friends, so happy to also hopefully get there again next year.

JC Palmes: You should. It’s in my country.

Birgit Pauli-Haack: Yeah. And if I come, I’ll spend a few days. So my approach is always I come in early, maybe a week or four days early, get over the jet lag, get the lay of the land. So I don’t know. So when I want to meet people. I know where the restaurants are, I know where the venue is, but I also get to do some sightseeing in a place where I haven’t been. So if it’s the first time… Yeah. I’m really looking forward to exploring Manila the few days that I have beforehand. I haven’t booked the flight yet. I need to wait for the okay. Of course, I don’t see why not. We’ll see how that goes.

JC Palmes: That would be nice. Amazing. I mean, Manila is an amazing city to explore.

Birgit Pauli-Haack: I’m looking forward to that. 

What’s Released – WordPress 6.7 Beta 1 – Create Block Theme

So next week, WordPress 6.7 Beta 1 is going to come out in October. On Thursday, October 1st, no Tuesday, sorry, on Tuesday, October 1st. And if you want to refresh what’s on the docket, I’ll share the link to the roadmap from 6.7 that Anne McCarthy put out. But I’m also hoping that by then after that, she also publishes a little bit more updated, because I know there is some change in the Zoom out feature, which I really love and I know the best part that I love will get in.

What was a little bit harder was to figure out how the editing works when you edit what you zoom out on your site for design. And if you want to contribute and have some time and want to learn at the same time, keep an eye out for that. The Make test team is about to publish with the beta, the help to test WordPress 6.7 post. It’s going to be a long one, but you can pick the features that you want to learn about or you want to test about, and the more you test, the better the version becomes. So that’s a big appeal to help us testing the beta versions.

JC Palmes: Yeah. For sure. I do want to touch on ’cause you’ve already mentioned some of the big updates, right? I think it’s also worth mentioning some of the smaller fixes that don’t always get a lot of attention, but really make a big difference in day-to-day use. There are a few things that I really love personally and versus there’s the great Block theme plugin that now allows you to, no, they rename on assets when saving or exporting, and it’s a small but neat update, but that makes asset management easier for developers working with custom fonts. And we work with custom fonts a lot.

Birgit Pauli-Haack: Mm-hmm. Yeah. Yeah. Yeah.

JC Palmes: So fonts are now copied directly to the local theme folder, which is such a time saver when dealing with multiple customizations. One other update that I think is worth mentioning is removal of the categories hidden tag.

Birgit Pauli-Haack: I haven’t mentioned anything about the… So when we are talking about now about the create Block Theme plugin new version that was released a week ago, and are you using in your Block Theme building process, the grade Block Theme plugin? How do you use that?

JC Palmes: We are. So it’s integrated in WDEVS BT, we are able to create… Well, this scaffold new blocks using a template that we have set in BT and leveraging the create-block script. So we have that added in our package JSON, and when our developers create a new block, we just run the script and it will scaffold all the files they need as part of the theme and they can just start creating a new block right away. It works right away, right away, right away. Yeah. It works. Once you run the script, it takes the template that we’ve set and then scaffold is a block and you have a very simple block showing up right away.

Birgit Pauli-Haack: Oh, okay. So that’s the create-block script. And that’s where probably Ryan came in because he’s a specialist in the…

JC Palmes: Yeah. That one.

Birgit Pauli-Haack: Yeah. Yeah. Yeah.

JC Palmes: And also we are… So this is an internal thing that we do with the create blocks plugin where we use it for a versioning thing or when we are doing patterns, changing patterns, and editing patterns and grading patterns. And it’s still a work in progress of course, but we are actively using that plugin and also the script and amazing plugins.

Birgit Pauli-Haack: Yeah. So the create block theme, you create the patterns in the editor and then you…

JC Palmes: Yes.

Birgit Pauli-Haack: Yeah. Okay. So you export them through the create block theme plugin methods into the…

JC Palmes: Yes, part of. So the create-block theme plugin right now does not really take patterns, but we somehow are finding a way to override that.

Birgit Pauli-Haack: Mm-hmm. Okay. All right. Yeah. The newest version of the create block theme plugin had a few things, and you mentioned one that was the rename of the font assets, when the theme is saved when exported, there’s also an attempt to try to add the synced patterns to the theme on save. 

JC Palmes: That one I have not tested yet.

Birgit Pauli-Haack: Yeah. It hasn’t been out long enough probably.

JC Palmes: Oh, okay. Yeah.

Birgit Pauli-Haack: It just came out last week. Yeah. So that is definitely something to test for theme developers and that were really waiting for that to happen. And then the remove categories hidden, you wanted to mention that?

JC Palmes: Yeah. So removing categories hidden from the default pattern header, and it’s a very subtle fix, right? But it just cleans up the UI, making it easier to manage and organize patterns, especially when you have more than 50 plus patterns.

Birgit Pauli-Haack: Yeah.

JC Palmes: So if you want to keep things tidy, you have to organize.

Birgit Pauli-Haack: Yeah. Yeah. And then another new feature is that it wraps the main tag around the Query Loop instead of the post content. It’s necessary because, so the skip to content kind of goes to the Query Loop instead of the full page kind of thing. So that has solved quite a few accessibility items there. And then the last one I wanted to mention is, oh yeah, that the fonts are copied and you mentioned it as well in the local theme folder. When you use a different font for a style variation, it automatically is downloaded there and added to the theme as its folder. Yeah. Cool.

JC Palmes: Yeah. I actually have two more.

Birgit Pauli-Haack: Go ahead.

JC Palmes: Yeah. So you’ve mentioned the main tag that’s also one of the things, and I think that just makes it, that’s an accessibility thing that we really need to improve on and that will help ensure better semantic HTML and accessibility. And also there’s some behind the scenes cleanups that I really like and it’s removing unused styles and unused style rules in data views, and it just makes for a leaner code base and better performance.

Birgit Pauli-Haack: Excellent.

JC Palmes: Also, the swapping of the pre-published check buttons was another nice tweak because I’m visual when I’m coding, so if something changes, I notice right away because dyslexic. I work in patterns. So if one thing changes and I think that is a really good change, I check it out and see how and why that is like one of the… it’s one of my top, it just makes it leaner and easier for me to work.

Birgit Pauli-Haack: I’m glad. Yeah. No. I find it very helpful to have this plugin and in combination with the site editor and then you make some changes there and it gets better and better even goes a little bit further than core, especially with the sync patterns for themes. I think that’s a little bit of a step forward that is outside of core because core is not yet ready for that and to get it into hands of theme developers to test it out and see how does it work and how good does it fit in into the development process. Yeah. So that’s our create Block Theme plugin update, and now we come from the big one, that’s the Gutenberg 19.3 plugin release. 

Gutenberg 19.3

The release had about 165 PRs following 52 contributors, including 7 first-time contributors. Kai Hao was the release lead and he published a release post that I certainly will share with you in the show notes.

Enhancements                                                       

So there are a few enhancements that we’re going to talk about. There are also new API or one new API. I’m sorry that my voice is a little horsey. I come from a week of nasty cold and I’m glad that we can connect today. Yeah. So I’m happy that you also can take over some of the things JC with me. Okay. 

So the first enhancement is actually not an enhancement. It’s kind of an update on the minimum PHP requirement for the create block script, which is 7.2. You cannot be on an older PHP version anymore. And using that script to create blocks, sometimes they need to point out that thing. So in the restore, there’s a restore, the move to trash button disappeared in the document settings and people were looking for it. They found them in the three.menu, but they needed it more prominent. So it’s coming back.

JC Palmes: Yes.

Birgit Pauli-Haack: Yeah.

JC Palmes: Thank you.

Birgit Pauli-Haack: So the inspector controls, so when the developer talks about inspector controls, they talk about the sidebar on the block editor and now they changed that when for custom blocks, they didn’t always have the block name in there to highlight that out. So that has changed. It was actually a bug I would think, because you want the name of the custom block name also in the inspector control. So that has been rectified and for patterns you can now change. It’s not for the patterns, it’s for when you go to add a page, your editor always comes out with a set of patterns that are available and you don’t want them. Now there is a user preference that you can switch on or toggle on and off in your preference sidebar or tool. So the modal, you can disable that modal and not have the selection in front of you. It took a while, but there was definitely something they listen to users to have that. Same with a move to trash button. The developers always, not always, but often listen to users when there is a strong emotion coming there away.

JC Palmes: Yeah. That’s amazing. I have strong emotions with that trash button as well. Having that not there is just, it’s making things off for me.

Birgit Pauli-Haack: Yeah. It’s kind of disconcerting. I want to have just trash it. Where is it? Yeah. 

Components

So in the components, it’s not a public component yet, but the developers are working on a tabs block component or a tabs component, and that is actually used throughout the editor, but it’s not available yet for blocks. It’s not public yet, but you can definitely look at the PR and see how it works so you can prepare yourself and they just improve the animation and the related utilities to make it to prepare for coming out of experimentation.

JC Palmes: Tabs block would be amazing. We’ve had to grade our own custom tabs block just because it’s not available and having that as one of the core blocks would be really awesome.

Birgit Pauli-Haack: Mm-hmm. Yeah. Same with the accordion block, I think there’s someone working on that as well. I saw some prototypes how that works. But yeah, it’s not going to come. I don’t think it’s going to come for 6.7 because they’re still in experimentation and we have what? Four days to go. Three days to go for beta, so I don’t think it’s coming.

JC Palmes: Yeah. Just three days.

Block Library

Birgit Pauli-Haack: Yeah. So what else? The block library had some changes, especially here now for the image block. I think there was…

JC Palmes: Oh, yeah. That one. Sorry. Yeah, with dropping multiple… not just multiple images, right? So you are now able to drop any kind of media and it’ll automatically translate to whatever that is. If it’s a video, it’ll be an actual video and images. It’s a time saver.

Birgit Pauli-Haack: Mm-hmm. Yeah. It automatically… So if it’s all images automatically creates a gallery block.

JC Palmes: Gallery. Yeah.

Birgit Pauli-Haack: Yeah. I tested it quite a bit and you need to be a little bit… When you drag and drop, you need to be quite precise with your mouse.

JC Palmes: With that. Yeah.

Birgit Pauli-Haack: Yeah. To get it next to the image that’s already there to create a gallery out of two images, but it’s just a little practice that you need. And then it’s really saving so much time to upload and download and gallery block and oh, I changed my mind. I don’t want one image, I want two images. So now I need to remove the image and put a gallery block in and yeah.

JC Palmes: Yeah. It’s just a time saver really.

Birgit Pauli-Haack: Absolutely. Especially when you’re someone who changed their mind often.

JC Palmes: Yeah.

Birgit Pauli-Haack: And what’s also there now is for the gallery list block to have now added a drop-down for the taxonomies so you can really select all the categories that you want to have in there. And then there were quite a few enhancements that are coming under the umbrella of a zoom out feature. 

Zoom Out

So the zoom out mode is officially out of experiment and it’s now available to all users. And this mode allows you to zoom out, to edit, or create at the pattern level over granular block editing. So you’ll see it when you want to add a pattern to a site, an existing site kind of zooms out so you see more of your page and then you get the insert outside of that, so where you can insert it without getting into other container blocks kind of thing. Yeah. So it’s actually really neat to see how a pattern would change the content of your page in relation to the other patterns or other page content that’s there. So it’s a really interesting way of helping you with the design of things. Have you experienced that on the Gutenberg plugin level yet? 

JC Palmes: Works not so much yet. Yeah. But that is one of the things that I want to play with this week. I just didn’t have the time to do that last week, but with all of this new things, so I just want to play around with it.

Birgit Pauli-Haack: Well, when you say play, it’s testing, right?

JC Palmes: It’s testing.

Birgit Pauli-Haack: It’s testing.

JC Palmes: Well, in my brain it’s still playing love to code. Yeah.

Birgit Pauli-Haack: Yeah. Mine too. Yeah. It’s kind of, “Oh, I’m going to play around with that.” But it’s more like, “Yeah. We need to test it.”

JC Palmes: Testing, creating, and all that fun stuff.

Birgit Pauli-Haack: Thinking about use cases, thinking about how to break it because that’s-

JC Palmes: Exactly.

Birgit Pauli-Haack: … yeah. And last month ago, or maybe three weeks ago, I got a kudos from a co-worker who said, “Well, you always find creative ways to break things.” It was my superpower, you know?

JC Palmes: Super power.

Birgit Pauli-Haack: Yeah., the zoom out toggle that is in the header section of the editor, there is a zoom out toggle. So you can say, okay, give me 50% of the view or give me the 100% that’s next to the preview tab. It might not stay there, but if you just want to kind of test it a bit and you don’t know, and I don’t always know when I would trigger that there’s an automation when all of a sudden it zooms out. But if you want to be in control of it, there’s a little toggle switch in the editor header and then you drag and drop your patterns into the zoom out mode. And then you also see of course everything in the list view and have the top level section in the zoom out mode and the list view is open. You only see the top sections of your site.

Block Editor                                                       

It’s really interesting. So the block editor got a few things. So this release also had a few other drag and drops, not only the image or the pattern, but you also can drag and drop a mix of audio and image blocks into the canvas and it will automatically create those individual blocks. That’s what you mentioned earlier as well.

JC Palmes: Yeah.

Birgit Pauli-Haack: Yeah. And then there is the link editing. That’s a small fix, but it’s something that was really missing was to create a link for the phone number. So if there’s a phone number or a recognizable phone number in your content, it will automatically create the link for it. So when you watch it on or look at it in mobile, you get the button-

JC Palmes: You’ll be able to click on it. Yeah.

Birgit Pauli-Haack: … call button. Yeah.

JC Palmes: Yes. ‘Cause adding that is going to be really awesome. It’s missing, and we’ve been adding that for some clients who needed that. So having that automatically added is just a nice small thing to have.

Post Editor

Birgit Pauli-Haack: Yeah. Absolutely. So there is a new preference modal in the new media section.

JC Palmes: That I didn’t know about.

Birgit Pauli-Haack: Yeah. I didn’t know about it either. Yeah. So this preference for the media section is to switch on client-side media processing. So it doesn’t all have to go to server sooner or later it will go to the server, but you can do it actually in the browser window. And then you have a lot more options open for dealing with media. And it’s the first part of the client-side media processing by Pascal Birchler. He had a featured plugin where he tested all that out and now this one comes into core. That’s really great. I’m really happy about that. So it’s definitely for mobile, also interesting for mobile users because they can’t wait till everything is done on the server because if you have a slow connection, you want it still to be processed without having to wait for all the back and forth there. So that’s really cool.

JC Palmes: I just let this pre-upload compression and having that as a toggle. And then, yeah, the approval step is sometimes when media is optimized, it just does not always look the way that we want it to look. So having that approval step is nice to have.

Birgit Pauli-Haack: So in the page editor, you can now double-click on the template part. So when you edit a page and you click into the template parts, it’s going to sometimes tell you this is a template part, you can’t edit that or go to the edit template part kind of screen. And now with double-click, you can switch over to template part editing. So it’s much faster now to, and if you know what you’re doing, it’s definitely helpful to have that there. I was always trying to do that with a double-click. I don’t know why, but it was kind of really-

JC Palmes: Oh, same. I do that too. I like this.

Birgit Pauli-Haack: So when you publish a post in the pre-publish section there, there is a warning in a notification that you might have pictures and other from a third place so that the images are not on your site and they’re linking out to either Google or some other place. And the feature offers you to upload all the images to your own media library so you can really have your… You’re not surprised when all of a sudden images go away from the third party.

JC Palmes: That is a very helpful fix. We’ve had issues with that where with patterns, when you copy a pattern, it will try to, it’ll look for images in your local, right? And you don’t always know that it’s referencing your local, because when you look at the site and it’s uploaded on an environment, you see that images are there and it’s only because it’s referencing local images and you are viewing the site in your computer. So you see that, but other people would not know. So having that would be a lifesaver.

Birgit Pauli-Haack: And it was in the section there, but very rarely did it pop up but now… and it was only working for gallery blocks and image blocks. But if you had an image from a third party in a media text block or in a cover block, it wouldn’t come over. It wouldn’t recognize it in that, and now it does. So it’s kind of expanding that feature to other block types. And I experienced that when I was working. I’m working on a tutorial on how to use Playground for a theme demo site so you don’t have to spin up your own site and you can get everybody their own link to Playground.

And I was trying to figure out how is the content or what do I have to do with the content? And I used a theme that had some patterns with the local assets, with the theme local assets, and I needed to get those into the media library. So when I import it to Playground, it knows, okay, I have those images because it wouldn’t go back to the theme assets for that. So it was really interesting to figure that out, and this was really helpful to at least get the marker, but it didn’t do it for the cover and the media text blocks. So seeing that here in the new release is really interesting.

JC Palmes: Yeah. It’s going to be very helpful that that is missing for those blocks. And we’ve been using those blocks quite extensively.

Birgit Pauli-Haack: They’re wonderful blocks to use. Yeah. They make a really great design all the time. So the next thing is also about the pre-publish screen, but it kind of switch the cancel the publish button so that the publish button is always under the mouse. So when you hit the publish first and then the next one, it had the cancel button there. So people sometimes cancel their publishing, although they wanted to publish, so now you can just keep your mouse there and have the second publish there as well. That’s a very good and nice quality of life kind of feature, but obviously somebody needed to think of it to do that. Yeah.

JC Palmes: That’s one of the things that I mentioned earlier and one of my favorite bits, so just swapping that is just, it just reduces unnecessary cursor movement and improves the user experience.

Block Bindings

Birgit Pauli-Haack: Oh, yeah. So totally. Then is the block bindings, your new favorite feature has an update. So what the feature does not do yet is give you an interface to actually create the post meta data or metafields, but now it uses the label that you put in your registration for the block bindings and not the variable name, which is definitely an improvement for that, especially for users who are not developers who always kind of little put back when they’re not reading normal words, but words with underscores in it and all that.

JC Palmes: I just love block bindings and I’ll always be on the lookout for whatever is new that’s going to come into it. We’ve been using that and learning more about how it works and just again, playing around with it and trying to make it do things that it’s not doing yet with core.

Birgit Pauli-Haack: Which part? What are those?

JC Palmes: Well, we’ve kind of packed it around to be able to.

Birgit Pauli-Haack: I love that when you say, “Oh, we hacked around it.”

JC Palmes: Just allowing to show meta that it’s not supposed to… Well, it’s not that it’s not supposed to show it’s always there, right? It’s just not ready yet. But it’s a play around between checking on the database and then checking things on. It’s a lot of experimentation in order to get what it natively does not do what we needed it to do for the project that we were working on before.

Birgit Pauli-Haack: So you were ahead of your time with your needs.

JC Palmes: Well, we had to, right? The client work that would really… We can’t really wait for when a feature that we need is going to come out and WordPress the way it is. And with all the things ready for us to just change, I guess. No, not change, build on.

Birgit Pauli-Haack: Yeah. I heard from a few extenders that’s plugin developers, theme developers, agency developers that they feel, oh, it’s time that more blocks are actually… Because you can only do block bindings for four blocks. One is the paragraph block, the image block, the button block, and the headings block, but all the other blocks, you cannot do a list block with things here and all that. So yeah, it definitely is time to expand the range of blocks that can hold bindings to metadata, definitely. And I know that the team knows that they’re definitely working on it. I’m scrolling through things.

Experiments                                                       

Yeah. There is one, speaking of block bindings under the experiments is now bringing the UI to the site editor to edit the values for the metadata or the block bindings. So you can do that in your… and they built the rest API endpoints for that so they can go back to the server and come back and have it all saved. So that’s a really good… It’s an experiment. You have to enable it through the experiments page. But yeah, test it out. Developers would love your feedback on it.

JC Palmes: Oh yeah, we’ve kind of done the same thing, but it’s not visible to users. It’s more in the code where we are able to change things around. But then again, it’s having that as a visual changeable thing. It’s just going to be a time saver.

Birgit Pauli-Haack: Absolutely. Absolutely.

Documentation

What I also want to point out, for those who are keen on learning more about the data views, the documentation has been updated, and especially the storybook has now better styles for the combined fields stories and also allows more layout for the combined fields storybook. So definitely an enhancement for those who want to look up the documentation for the data of use. And the stories for that storybook is kind of a component, is a documentation style to have each single component outside of the context of the block editor to what are the properties and how does it behave when you change settings just alone for that component.

And it’s a really great way to learn about all the WordPress components and not a whole lot of people know about it. But that will change because the design system that the design team is working on will be also based probably on storybook because for the admin, if you ever want the data views to be part of the WordPress WPAdmin, there is a whole lot of work to be done to cement the design system about every single screen and all that. So they’re working on that for the color scheme and the typography and all that to make it more seamless. And I think somebody did a test or an audit on all the color strings that are in the WP-Admin sections. And I think she found 68 different colors. So it’s all kind of different gray tones. It’s different. Yeah, blue tones, different dark blue tones. And I was really amazing. And they definitely is not increasing the standardization when you have so many colors and a thing too about the design system-

JC Palmes: So it could be a nice thing to have that revamped on and just be able to make it more visible to everyone ’cause it’s a very helpful way to when you’re creating components and creating blocks.

Code Quality

Birgit Pauli-Haack: So the next two items I think are more for the developers because they are code quality related. The editor uses hooks instead of higher order components in the block manager. So that’s interesting for contributors. And then the data view fields store is, and the actions are moving from the editor package into the fields package. So if you have already done some exploration on the data views and data view fields, you need to make a note of that, that the package has changed a bit. I think the Gutenberg developers are very good and do the warnings in the console. So you probably see that when you use them. All right. So that’s the Gutenberg Changelog for Gutenberg plugin 19.3 and my voice is a bit fading, so I’m really happy that you walked this through with me. JC, it was wonderful to have you. We are coming to the end of the site, so if people want to get in touch with you, what is a good place for them to reach you? WP Slack or is it more on the social webs? 

JC Palmes: I’m always in Slack and I’m always on Facebook and Instagram as well.

Birgit Pauli-Haack: Okay. Yeah. So I will share the links in the show notes as well too. So you can get in touch with JC Palmes if you have questions about WordCamp Asia or the Block Theme that they’re working on. It was wonderful that you have been on the show. Thank you so much. And as always, dear listeners, the show notes will be published on gutenbergtimes.com/podcast. This is episode 108, and if you have questions and suggestions or news you want us to include, send them to changelog@gutenbergtimes.com. That’s changelog@utenbergtimes.com. All right. Well, thank you everybody and thank you, JC.

JC Palmes: Thanks so much for having me, Birgit. It’s been a great conversation and I really enjoyed diving into all these updates with you. This is also my first podcast, by the way.

Birgit Pauli-Haack: Oh, right. Oh, we got you.

JC Palmes: Yeah, amazing. I love it.

Birgit Pauli-Haack: Yeah. So until the next time then if I may, I will ask you to come to the show again, maybe after WordCamp Asia and we talk about our adventure in Manila, how about that?

JC Palmes: I love that.

Birgit Pauli-Haack: All right. Well, thank you so much. And do you have a wonderful weekend or rest of the evening for you and see you all and hear you all, dear listeners, in two weeks. Thanks again. Bye-bye.

by Birgit Pauli-Haack at September 30, 2024 09:07 AM under Gutenberg

September 29, 2024

Matt: On with Theo / T3.gg

On Thursday, a prominent developer, YouTuber, Twitch streamer, and journalist posted a video titled This might be the end of WordPress. It was very harsh. In that video you’ll hear him say about me, “he’s a chronic hater” (7:55), “seems like he’s been a pretty petty bastard for a long time now” (10:22), “I hate this shit, I hate when people are assholes and they get away with it because I’m doing it for the greater good, the fake nice guy shit. I’ll take an asshole over a fake nice guy any day, people whose whole aesthetic is being nice, I hated it.” (11:25), “Honestly I’d rather the license just be explicit about it than this weird reality of ‘If you get popular enough you can still use it but the guy who made WordPress is going to be an asshole to you.’ That seems much worse than most open source models.” (14:39)… it goes on.

Ouch!

However, one of my colleagues Batuhan is a follower of Theo’s and suggested I engage with him. It turns out we were both in San Francisco, and he was game for a livestreamed, no-conditions interview at his studio. I believe discussion is the best way to resolve conflict, that’s why my door is open to Lee Wittlinger, Heather Brunner, Brian Gardner, or any WP Engine or Silver Lake representative who wants to talk to resolve things.

Saturday afternoon I went to Theo’s studio, we had a vigorous two hour debate and discussion with some real-time chat polling that also changed my mind on a few things, and his, too. I left feeling like I had a new friend. ️And met some awesome cats. Check out the video.

by Matt at September 29, 2024 08:35 PM under WordPress

Do The Woo Community: We Are Looking for Guest Posts from our Listeners

Episode Transcript

BobWP:
Hey everyone, BobWP here on Community. Well, this episode is more or less about the return of our blog here at Do The Woo, but it really is about community. Now, before I even get into that, a little news about this show, BobWP on Community. I know everyone loves conversation, and often when I go solo on this show, it just really doesn’t fit like our other shows do, which are centered around conversation. So, very soon, I’ll be announcing a new member of our hosting team and co-host of this show. It will be BobWP and whoever I choose on Community. We will have conversations between ourselves and an occasional guest.

What I really want to share with you is that we have everything in place to accept guest posts on our new blog. As with our podcast, the blog is by the community, for the community. During WordCamp US, I recorded more details on that. I talked about some of the past decisions regarding whether to have a blog or not. I also outlined the blog’s future, including contributions from hosts, guests, and even listeners. It was pretty brief, but I talked about moving forward with this new blog.

Now, as I said, we are ready for you, the listener. We have an invitation for you. Our guest posts are unique in that we’re looking for you to add to the conversation. For example, do you have a story that relates to an episode you’ve listened to? Do you want to expand your thoughts and insights on a particular episode through a short post or maybe a longer post instead of a comment? Or were you a guest, and would you like to update something from your episode or maybe even elaborate on something you mentioned?

So, as a listener, if you have an idea for a post, you can go to dothewoo.io/guest-posts, or you can reach out in another way, and I’ll send you the link. The link will also be in the show notes. But I’m pretty excited about this blog because it’s a little different in that we want to tie all the posts into episodes from our podcasts. So, if you’re interested, reach out to us. I’m looking forward to you being a bigger part of the Do The Woo community.

Here’s a suggested intro for your show notes:


In this episode of BobWP on Community, Bob shares news about the return of the Do The Woo blog and how it will further engage the WooCommerce community.

He chats about the future of the blog, opportunities for listeners to contribute guest posts, and the plans to bring on a new co-host for this show.

Whether you’re a longtime listener, guest, or simply a member of the community, Bob invites you to join in and become an even bigger part of the conversation.

More on the blog

by BobWP at September 29, 2024 03:30 PM under Podcast

September 28, 2024

Matt: Where is Lee Wittlinger?

Lee controls the board of WP Engine. The board is why WP Engine hasn’t done a trademark deal for their use of the WordPress and WooCommerce trademarks.

You hide behind lawyers and corporate PR when you’re wrong, not when you’re right.

I’m replying on Twitter, I’m commenting on Reddit and Hacker News, I’m dropping into livestreams with ThePrimeagen and WPMinute. I’m talking to journalists whenever they reach out, and I’m happy to go on any large credible podcast or show to discuss these issues.

Lee could do the same. Why isn’t he?

Lee is a managing director of a $102B private equity firm, he is probably richer than me. (Though I doubt he gives back as much.)

“Because their lawyers are telling him not to.” Why do you think their lawyers are telling them not to?

Open invite: Lee, let’s debate this publicly. Propose a neutral venue and moderator.

by Matt at September 28, 2024 08:12 PM under Asides

Matt: Multidots Support

Anil Gupta has made an amazing commitment to the WordPress ecosystem. I applaud the way he runs his business.

by Matt at September 28, 2024 05:50 AM under Asides

WPTavern: Matt Mullenweg Announces Temporary Lifting of WP Engine Ban

Matt Mullenweg has announced that the restrictions on WP Engine will be temporarily lifted until October 1, 00:00 UTC, allowing them to access WordPress servers. WP Engine was banned on September 25 from utilizing any WordPress.org resources following legal actions related to trademark disputes, which left WP Engine customers unable to access the Plugin/Theme directory or update their websites

The temporary reprieve gives WP Engine time to “spin up their mirrors of all WordPress.org’s resources that they were using for free while not paying and making legal threats against us.”, according to the official statement.

The announcement post blamed WP Engine for the situation: “WP Engine was well aware that we could remove access when they chose to ignore our efforts to resolve our differences and enter into a commercial licensing agreement. Heather BrunnerLee Wittlinger, and their Board chose to take this risk. WPE was also aware that they were placing this risk directly on WPE customers. You could assume that WPE has a workaround ready, or they were simply reckless in supporting their customers. Silver Lake and WP Engine put their customers at risk, not me.”

Matt tweeted, “We’ve removed all network blocks so anything they’ve having trouble with is a result of their own work.” In another tweet, he clarified, “Silver Lake is the only entity we have beef with.” During the WP Minute live stream, Matt reiterated that the WP Engine situation was uniquely bad and that he doesn’t foresee this happening again with any other hosting provider.

On the same livestream, Matt was asked by Brian Coords about allowing WP Engine users more time to transition to new hosts. Matt acknowledged the suggestion, admitting it was a valid point.

WP Engine tweeted: “We’re pleased to see access restored to the repository of WordPress plugins for our customers who operate their sites with us at WP Engine.”

The community remains divided—some support the decision, while others are less impressed.

While the reprieve is a temporary solution, it remains to be seen how the situation will unfold in the long run.

by Jyolsna at September 28, 2024 04:37 AM under wp engine

Gutenberg Times: Gutenberg 19.3, Simplified Query Loop and blocks in theme.json — Weekend Edition #306

Hi there,

This was anything but a slow WordPress news week, though, however none of it related to the software and the block editor. There are a few WordPress news places where you get updates and opinions. Official WordPress news is one, Michelle Frechette over at Post Status has a great summary with links: Give Back … Deeply, Matt Medeiros and the WP Minute team share what they know, and Anil Gupta, Multidots is taking a stand for the WordPress Ecosystem: why we must all give back 

Next week, WordPress 6.7 Beta 1 is on the schedule for October 1, 2024. To refresh what is on the docket for this next version you can consult Roadmap to 6.7. If you want to contribute and learn at the same time, keep an eye out for the “Help to test WordPress 6.7” post from the Make Test team as well.

I’ve been battling a nasty cold all week, and it seems I just need to let it run its course. I apologize in advance if my thoughts aren’t entirely coherent. To minimize any potential embarrassment, I’m keeping this weekend’s edition brief.

I will be taking a social media break for a few days, too, it’s good for my mental health people tell me.

Yours, 💕
Birgit

Developing Gutenberg and WordPress

Release lead, Kai Hao, shared in his post What’s new in Gutenberg 19.3? (25 September) the highlights from the new version:

Zoom Out view Gutenberg 19.3

Joen Asmussen published his 64th Design Share and shows off the work of the WordPress Design team of the last two weeks:

  • Global styles iA
  • WP Briefing Landing Page
  • Adding “Drag” to Image Placeholder Text
  • WP.org: Moving “Log in” to the secondary navigation
  • Figma Organization for the new design system
  • Secondary button appearance concept
  • Unify DropZones
  • Updated shadows / elevation in WP Components
  • Updating ToggleGroupControl
  • Storybook Improvements
An early in-the-clouds exploration of how the global styles iAAn early in-the-clouds exploration of how the global styles iA

Plugins, Themes, and Tools for #nocode site builders and owners

Anne McCarthy continued in their Core Improvements series about the Simplified Query Loop block with smarter defaults & intuitive settings. The enhancements streamline how you create dynamic post lists, making it more user-friendly and customizable. McCarthy explains how stronger defaults help with the first time usage, a toggle switch lets you change from default query to using a custom query, and the block’s filtering options include post formats now.

Theme Development for Full Site Editing and Blocks

Fabian Kägy, director of editorial engineering at 10Up, documentation release lead for WordPress 6.7 was a guest on the ShopTalk Show 634th podcast episode, with hosts Chris Coyier and Dave Ruppert. “Fabian Kägy helps us understand the modern WordPress development process, Gutenberg vs Block editor vs full site editing, building with blocks or pages, what’s coming in the Twenty Twenty-Five Theme, and whether the theme authoring process has been made too difficult in 2024?” they wrote in the description.

634: Fabian Kägy on WordPress, Blocks, and Enterprise Dev on ShopTalk Show.

In the article, What WordPress developers need to know about the blocks property in theme.json, Jeremy Holcombe breaks down the “blocks” property in the theme.json file for WordPress. This lets developers set up block settings globally. It makes customizing Gutenberg blocks a breeze by centralizing design options like colors and typography. Plus, it keeps everything consistent and boosts site performance by cutting down on custom CSS. Holcombe also includes easy-to-follow implementation tips, practical examples, and code snippets to help theme developers get the most out of this feature. It really streamlines the development process and amps up overall site optimization.

 “Keeping up with Gutenberg – Index 2024” 
A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test, and Meta team from Jan. 2024 on. Updated by yours truly. The previous years are also available: 2020 | 2021 | 2022 | 2023

Building Blocks and Tools for the Block editor.

JuanMa Garrido published Actions from Data Views: Adding images to the Media Library. It’s a continuation of the tutorial, he published earlier this month: Using Data Views to display and interact with data in plugins in which he walked you through on how to create a plugin that displays a React app in the WordPress admin to list a dataset of pictures using Data Views. In this second part, you learn how to provide users with tools to directly add any listed images to the Media Library.


In this week’s Live Developer Hours, JuanMa Garrido, André Maneiro and Nick Diego gave An Introduction to Data Views and answered a ton of questions. They covered, the fundamentals of the DataViews component, how to add a React app to a custom WordPress admin page and how to display a custom dataset using Data Views.


Need a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.

Now also available via WordPress Playground. There is no need for a test site locally or on a server. Have you been using it? Email me with your experience

GitHub all releases

Questions? Suggestions? Ideas?
Don’t hesitate to send them via email or
send me a message on WordPress Slack or Twitter @bph.


For questions to be answered on the Gutenberg Changelog,
send them to changelog@gutenbergtimes.com


Featured Image: “Mitchell Library, Sydney (#24)” by Christopher Chan is licensed under CC BY-NC-ND 2.0


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 September 28, 2024 03:09 AM under Weekend Edition

September 27, 2024

WordPress.org blog: WP Engine Reprieve

I’ve heard from WP Engine customers that they are frustrated that WP Engine hasn’t been able to make updates, plugin directory, theme directory, and Openverse work on their sites. It saddens me that they’ve been negatively impacted by Silver Lake‘s commercial decisions.

On WP Engine’s homepage, they promise “Unmatched performance, automated updates, and bulletproof security ensure your sites thrive.”

WP Engine was well aware that we could remove access when they chose to ignore our efforts to resolve our differences and enter into a commercial licensing agreement. Heather Brunner, Lee Wittlinger, and their Board chose to take this risk. WPE was also aware that they were placing this risk directly on WPE customers. You could assume that WPE has a workaround ready, or they were simply reckless in supporting their customers. Silver Lake and WP Engine put their customers at risk, not me.

We have lifted the blocks of their servers from accessing ours, until October 1, UTC 00:00. Hopefully this helps them spin up their mirrors of all of WordPress.org’s resources that they were using for free while not paying, and making legal threats against us.

by Matt Mullenweg at September 27, 2024 09:03 PM under Updates

Do The Woo Community: Our Weekly Recap is Coming Back to the Blog

Over the years, we have done a weekly recap on Friday’s. It evolved over time and I always strategize exactly what we will be dropping in here.

It’s not going to be the latest news, products, etc. in the space, as there are more than enough sites doing that.

Instead, this will serve as a good weekly collection of:

  • Posts and episodes here on Do the Woo
  • Content from our hosts, partners and sponsors.

Plus, if any listener comments on a specific episode or post, we will also be including a snippet from their comment in the recap. 🙂

Just a solid list of content that you may have missed. That’s it.

by BobWP at September 27, 2024 09:58 AM

Matt: On ThePrimeagen

I dropped on the livestream for ThePrimeagen earlier today after a colleague pinged me that he was talking about the Silver Lake / WP Engine situation.

Afterward, I also privately shared with him the cell phone for Heather Brunner, the WP Engine CEO, so she can hop on or debate these points. As far as I’ve heard she hasn’t responded. Why is WP Engine scared of talking to journalists live?

by Matt at September 27, 2024 06:31 AM under press

September 26, 2024

WordCamp Central: Quarterly WordPress Event Sponsorship Report, 2016-2024 Q3

Below is the total amount of sponsor invoices generated to date for WordCamp and WordPress events, including the Community Summit fund and the Global Sponsorship fee.

Global Sponsorship

$1,500,000 or above

  • Automattic
  • Bluehost

$1,000,000 or above

  • Bubblestorm Management
  • GoDaddy

$200,000 or above

  • DreamHost
  • BoldGrid
  • Liquid Web
  • Weglot

$100,000 or above

  • OnTheGoSystems
  • GreenGeeks
  • Awesome Motive

$50,000 or above

  • HubSpot
  • Pantheon
  • InMotion Hosting
  • Nexcess
  • SiteGround
  • SiteLock

$10,000 or above

  • Parallels International
  • Yoast
  • WiredTree

Per Event Sponsorship

$2,000,000 or above

Automattic

$500,000 or above

WP Engine

$100,000 or above

  • Pantheon
  • SiteGround
  • Google
  • GoDaddy
  • SiteLock
  • Elementor
  • Hostinger
  • Wordfence
  • Cloudways
  • A2 Hosting
  • Yoast
  • Flywheel
  • Plesk
  • Gravity Forms
  • DreamHost
  • WPMU DEV
  • Nexcess

$50,000 or above

  • GreenGeeks
  • WordPress VIP
  • InMotion Hosting
  • dotblog
  • Media Temple
  • Pressable
  • Weglot
  • BoldGrid
  • Liquid Web
  • StellarWP
  • WEDOS
  • BigCommerce
  • PayPal
  • Omnisend
  • DigitalCube
  • Kinsta

$25,000 or above

  • NitroPack
  • Qualpay
  • Avalara
  • Setka
  • Rocket.net
  • Hover
  • Sucuri
  • Patchstack
  • FastSpring
  • KnownHost
  • Jilt
  • Themeum
  • GiveWP
  • WebPros
  • PeachPay
  • WP Buffs
  • WP Rocket
  • YITH
  • Litespeed

$10,000 or above

  • Amazon Lightsail
  • ilkli
  • Pagely
  • 10up
  • VendorFuel
  • Verisign
  • HubSpot
  • RunCloud
  • GoWP
  • Square
  • Oliver POS
  • WPDeveloper
  • LearnDash
  • InstaWP
  • Stackabl
  • BuddyBoss
  • Beaver Builder
  • ServerPress
  • doMEn Ltd
  • WS Form
  • rtCamp
  • Crocoblock
  • FIU College of Business
  • Deer Designer
  • AddThis
  • Blockonomics
  • WP Beginner
  • Monarx
  • CookiePro
  • miniorange
  • Airwallex
  • AdRoll
  • Prime Strategy
  • CloudAccess.net
  • UpdraftPlus
  • Rochen
  • TextExpander
  • Titan
  • GoGoCreate
  • TraitWare
  • Tutor LMS
  • Cloudinary
  • EasyWP

by Isotta Peira at September 26, 2024 12:56 PM under Sponsors

Matt: WPE & Trademarks

I’ve been writing and talking about WP Engine a lot in the last week, but I want to be crystal clear about the core issue at play.

In short, WP Engine is violating WordPress’ trademarks. Moreover, they have been doing so for years. We at Automattic have been attempting to make a licensing deal with them for a very long time, and all they have done is string us along. Finally, I drew a line in the sand, which they have now leapt over.

We offered WP Engine the option of how to pay their fair share: either pay a direct licensing fee, or make in-kind contributions to the open source project. This isn’t a money grab: it’s an expectation that any business making hundreds of millions of dollars off of an open source project ought to give back, and if they don’t, then they can’t use its trademarks. WP Engine has refused to do either, and has instead taken to casting aspersions on my attempt to make a fair deal with them.

WordPress is licensed under the GPL; respect for copyright and IP like trademarks is core to the GPL and our conception of what open source means. If WP Engine wants to find another open source project with a more permissive license and no trademarks, they are free to do so; if they want to benefit from the WordPress community, then they need to respect WordPress trademark and IP.

Further reading:

by Matt at September 26, 2024 08:25 AM under WordPress

WPTavern: WP Engine Banned from Using WordPress.org Resources

The dispute between Automattic and WP Engine has intensified. Both companies have issued Cease and Desist orders to each other, leading WP Engine to remove the news feed from the WordPress admin dashboard. In response, WordPress.org has now banned WP Engine from utilizing any of its resources.

The WordPress.org statement read: “Pending their legal claims and litigation against WordPress.org, WP Engine no longer has free access to WordPress.org’s resources. WP Engine wants to control your WordPress experience, they need to run their own user login system, update servers, plugin directory, theme directory, pattern directory, block directory, translations, photo directory, job board, meetups, conferences, bug tracker, forums, Slack, Ping-o-matic, and showcase. Their servers can no longer access our servers for free.”

The statement continued: “The reason WordPress sites don’t get hacked as much anymore is we work with hosts to block vulnerabilities at the network layer, WP Engine will need to replicate that security research on their own. Why should WordPress.org provide these services to WP Engine for free, given their attacks on us?”

The announcement also reiterated what was shared in the WP Engine is not WordPress article. “WP Engine is free to offer their hacked up, bastardized simulacra of WordPress’s GPL code to their customers, and they can experience WordPress as WP Engine envisions it, with them getting all of the profits and providing all of the services.”

For those wondering about Flywheel, Matt has clarified that Flywheel also would be affected as WP Engine had acquired Flywheel in 2019.

The new status page on WP Engine explains: “There is currently no impact on the performance, reliability or security of your site nor does it impact your ability to make updates to your code or content. We know how important this is for you and we are actively developing a remediation for this issue.”

Meanwhile, Automattic-owned Pressable has a new page.  The WordPress community is not happy with these events. Several people have come forward to offer help to those caught in the crossfire.

by Jyolsna at September 26, 2024 06:55 AM under wp engine

September 25, 2024

WordPress.org blog: WP Engine is banned from WordPress.org

Any WP Engine customers having trouble with their sites should contact WP Engine support and ask them to fix it.

WP Engine needs a trademark license, they don’t have one. I won’t bore you with the story of how WP Engine broke thousands of customer sites yesterday in their haphazard attempt to block our attempts to inform the wider WordPress community regarding their disabling and locking down a WordPress core feature in order to extract profit.

What I will tell you is that, pending their legal claims and litigation against WordPress.org, WP Engine no longer has free access to WordPress.org’s resources.

WP Engine wants to control your WordPress experience, they need to run their own user login system, update servers, plugin directory, theme directory, pattern directory, block directory, translations, photo directory, job board, meetups, conferences, bug tracker, forums, Slack, Ping-o-matic, and showcase. Their servers can no longer access our servers for free.

The reason WordPress sites don’t get hacked as much anymore is we work with hosts to block vulnerabilities at the network layer, WP Engine will need to replicate that security research on their own.

Why should WordPress.org provide these services to WP Engine for free, given their attacks on us?

WP Engine is free to offer their hacked up, bastardized simulacra of WordPress’s GPL code to their customers, and they can experience WordPress as WP Engine envisions it, with them getting all of the profits and providing all of the services.

If you want to experience WordPress, use any other host in the world besides WP Engine. WP Engine is not WordPress.

by Matt Mullenweg at September 25, 2024 10:50 PM under Updates

Matt: Charitable Contributions

I knew going to war with Silver Lake, a $102B private equity firm, they would pull out every dirty trick to try to smear my name, do oppo research, imply I’m a mafia boss trying to extort them, etc.

I have kept my personal philanthropy private until now. I would like to offer up one piece of evidence for the public to consider, which is the IRS accounting of my 501c3 charitable donations.

This is something I’ve tried to keep quiet, because true philanthropy isn’t about recognition. As you can see, my personal liquidity goes up and down but I give back as much as I can when I can.

  • 2011: $295,044.60
  • 2012: $401,121.00
  • 2013: $2,088,890.88
  • 2014: $98,648.00
  • 2015: $101,947.00
  • 2016: $42,300.00
  • 2017: $51,562.50
  • 2018: $606,957.68
  • 2019: $620,802.65
  • 2020: $607,452.48
  • 2021: $2,151,602.26
  • 2022: $2,780,054.20
  • 2023: $2,276,425.06

If Lee Wittlinger, who controls Silver Lake’s investments in the WordPress ecosystem, or Heather Brunner, the CEO of WP Engine, would like to publish their charitable contributions over the past 12 years, they are welcome to do so.

by Matt at September 25, 2024 08:06 PM under Personal

WPTavern: Ajmer in India to Host its First WordPress Event ‘WP Campus Connect’

Ajmer, a city in the Indian state of Rajasthan, is all set to organize its first-ever WordPress event – WP Campus Connect. This month-long initiative in October aims to empower students across multiple campuses by introducing them to the powerful tools and opportunities that WordPress offers.

Organizers have partnered with four different colleges to host a series of interactive workshops over four weekends – October 5-26, 2024. Each workshop will take place on a different college campus, providing students with the chance to learn in a hands-on environment.

Participants can expect comprehensive training sessions led by experienced professionals from the WordPress community. In addition to technical skills, the workshops will also cover various career paths within the WordPress ecosystem. 

Pooja Derashri, event organizer and co-founder of WPVibes, said: “By introducing students to WordPress, we’re providing them with more than just technical knowledge; we’re giving them access to a world of career possibilities. This initiative will help students not only build valuable skills but also connect with professionals and peers who can guide them in their career journey.”

The Ajmer WordPress Meetup group has been active since 2017, and the organizers had planned to engage with students even before the pandemic caused the group to go quiet. They later shifted their approach, opting to conduct workshops at colleges rather than gathering students in one location.

With an anticipated turnout of 350 to 400 students, WP Campus Connect promises to be a vibrant hub for learning and collaboration. The event is designed not only to educate but also to inspire students to consider future careers in web development, digital marketing, and more.

The organizers have ambitious plans to expand the program in the future. They aim to bring in global speakers to offer valuable industry insights and establish a mentorship program that connects students with experienced WordPress professionals. They also plan to host hackathons and competitions focused on WordPress while collaborating with industry partners to create internship and job opportunities for students.

Recently, much emphasis has been placed on attracting new users, especially students, to WordPress. Josepha Haden Chomphosy, Executive Director of the WordPress project, discussed this month the importance of WordPress and how it equips students with essential skills for thriving in their future careers. WordPress.com is also giving away 1,000 free premium websites exclusively to university students.

by Jyolsna at September 25, 2024 05:04 PM under WP Campus Connect

WPTavern: #138 – Isla Waite, Bet Hannon and Ryan Bracey on What to Expect From WP Accessibility Day 2024

Transcription

[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress, the people, the events, the plugins, the blocks, the themes, and in this case, what to expect from WP Accessibility Day 2024.

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/feed/podcast. And you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.

So on the podcast today, we have Isla Waite, Bet Hannon and Ryan Bracey.

Isla Waite, originally from the UK has lived in Sacramento, California for 17 years. With a background in graphic design and over a decade in website project management, she recently started her own accessible web design business. Three years ago, Isla joined the WordPress accessibility meetup led by Amber Hinds, which also led to her involvement with the WordPress Accessibility Day. She is now a team lead, managing the tech and vendor teams to promote web accessibility.

Bet Hannon has worked with businesses and nonprofits for over 16 years, helping them build WordPress websites, integrate other communication channels, and learn how to use digital marketing tools more effectively. She is the founder and CEO of AccessiCart, a services agency that focuses on accessibility and e-commerce, along with other high user interaction websites. Bet lives in Bend, Oregon and is a co-organizer of the WordPress meetup there.

Ryan Bracey is the director of web development and user experience at Second Melody, a mid-sized branding agency located in New Jersey, which builds custom WordPress websites for clients of all sizes and industries. In this role, Ryan has taken a holistic approach to accessibility within the agency by promoting collaboration between clients and departments alike, to ensure all phases of a project are completed with intention.

During the podcast, we discussed the significance of WordPress Accessibility Day, which is a 24 hour virtual conference running on the ninth to the 10th of October, 2024.

It’s free to attend, and we’ll offer a wealth of resources around the topic of WordPress accessibility. The event will include live captions, ASL interpreters, and professionally created event transcriptions.

It’s being driven by a team of passionate volunteers, and is geared towards making the digital space accessible for all.

We’ll cover the logistical details, including how to register, and the optional donations and sponsorships that can enrich your participation. Our guests share their personal motivations and experiences that fuel their dedication to the accessibility cause.

We also get into the global reach of the event with translation efforts and volunteer opportunities that make WordPress accessibility day 2024 for a truly inclusive initiative.

Isla, Bet and Ryan talk about the challenges and triumphs of advancing web accessibility. The importance of both conformance and compliance, and practical steps you can learn about during the event to make your website more accessible.

Whether you’re a developer, a designer or a content creator, this episode is packed with insights and inspiration to help you contribute to a more accessible web using WordPress.

If you’re interested in making the web a more accessible and inclusive place, this episode is for you.

If you’d like to find out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Isla Waite, Bet Hannon and Ryan Bracey.

I am joined on the podcast by Isla Waite, Bet Hannon and Ryan Bracey. Welcome to you all.

[00:04:51] Bet Hannon: Great to be here.

[00:04:52] Ryan Bracey: Thank you, yeah.

[00:04:52] Nathan Wrigley: Very, very nice to have you. I can’t actually remember if we’ve had three guests on the podcast before.

A quick hat tip before we begin to Michelle Frechette, who has been instrumental in lining up this podcast episode and wrangling today’s three guests.

In no particular order, I’m just going to go in the list that I’ve got them written down on my screen. Would you mind just doing a very quick one minute introduction, quick bio about who you are? Something relevant to what we’re going to be talking about today, which is the WordPress Accessibility Day 2024. So let’s start with Isla. Could we just have your little bio please?

[00:05:24] Isla Waite: Okay, my name is Isla Waite, I hail from the UK, but I live in Sacramento, California for the last 17 years. I have been in website project management for, gosh, more than a decade. Graphic design was my original life, and before that I was in Britain doing things.

I recently started my own business in accessible websites. I stumbled upon WordPress Accessibility Meetup, run by Amber Hinds, about three years ago. And through that discovered WordPress Accessibility Day and said, yes, I’ll get involved in that. And now I am one of the team leads, I’m the tech and vendors team lead.

[00:05:58] Nathan Wrigley: Very, very nice. Thank you so much for that. Okay, next one on the list is Bet. Bet, would you do the same? Just introduce yourself.

[00:06:05] Bet Hannon: Absolutely. So I’m Bet Hannon, I’m the CEO of AccessiCart. We are an accessibility services agency that focuses on e-commerce and other high user interaction sites. And this is my third go around with WordPress Accessibility Day. I serve on the board of directors, I’m the treasurer, and I am the team lead for finance and sponsors. So I primarily do money things for WordPress Accessibility Day.

[00:06:32] Nathan Wrigley: Okay, thank you so much. And finally, last but by no means least, Ryan.

[00:06:36] Ryan Bracey: Thanks. So yeah, Ryan Bracey, I’m the director of Web Development at Second Melody. We’re a branding studio located here in New Jersey, where I’m also located. Yeah, much like Isla, I stumbled across Accessibility Day through Amber Hind’s Accessibility Meetup. Joined as a volunteer three years ago, been an organiser for the past two years, and this year I am helping out as the team lead for speakers. So, dealing with everything related to talking to speakers, reviewing speakers, making the schedule, with the help from a lot of other people.

[00:07:06] Nathan Wrigley: Thank you very much. I obsess about WordPress, and so it’s not news to me that the WordPress Accessibility Day is a thing, but it occurs to me that maybe a bunch of people listening to this podcast will not have heard of this event before. So, whoever wants to take the question, could you just briefly outline what it is, what the intent is, and maybe, given that it’s coming up very soon, let’s get the date and the URL out there as well, so that people can pause this podcast, go and have a look, and then come back and press play again. So whoever wants to take that, just give us the lowdown, the introduction to when it is, and what it’s all about.

[00:07:39] Ryan Bracey: Yeah. So WordPress Accessibility Day will be held this year, October 9th through 10th. We are a 24 hour conference, that’s why it spans the 9th through the 10th. So there are 24 hour long sessions. You can tune in starting on the 9th, watch all the way throughout the day, the night, into the next day. We are an international conference, a hundred percent virtual, so this is why we’re able to do a 24 hour day.

So no matter where you are in the world, you can find a session that you’re interested in, that works for your schedule, participate how you want to participate. And our main focus here is just WordPress accessibility. So looking at educating and informing people on accessibility within the space, how they can help out, how they can get involved, and hopefully educating some people on things they didn’t know.

[00:08:27] Nathan Wrigley: Nice. Thank you so much. I don’t know about the schedule too much. We can come to that in a moment. I don’t really want to particularly cherry pick out individual speakers, although you may wish to later.

But given the fact that it’s running around the clock, so this 24 hour cycle, has that given you an opportunity to highlight different parts of the world, and raise the profile of different communities?

So, you know, we’ve got three flagship events which span the globe, Asia, Europe, and America. But, you know, there’s communities in Australia, the Philippines, Taiwan, South America, all of these things. Has that been an endeavor? Is that part of the whole 24 hour nature, to raise the profile of different community members throughout the world?

[00:09:04] Isla Waite: Absolutely, yeah. This year in particular, we have grown our marketing department of this nonprofit Accessibility Day, and thank you to Michelle. We are sending out social media, and blogs, and podcasts in all different areas of the world. She’s connected with all kinds of people to make sure stuff is pushed out at appropriate times for different time zones.

We’ve had good responses to those things. So we now have team members coming in from different regions in Australia and Hungary. Speakers from all different places, all around the world. I think this year, as it should be, is better than the last, and next year will be better than this year, and that will keep happening.

[00:09:42] Nathan Wrigley: Bet I think it was, that mentioned that she was a director. And when I hear that word, it immediately summons up some sort of structure in the background, you know, a hierarchy of people and what have you.

A lot of the events that I’ve seen online, I get the impression that it’s a bunch of friends that get together sometimes, and organise an event around a particular theme. But given that there’s directors and things like that, I’m presuming that there’s more going on in the background, a little bit more of a professional nature to it. Perhaps like a, well, we call it in the UK a charity, I think it’s called a nonprofit in North America. But is there some sort of structure in the background like that?

[00:10:16] Bet Hannon: Yes. Intentionally done in 2021, as we were going into 2022, was really thinking about, and one of the things that we, as a community, felt was really important was making sure that our speakers were compensated. All over the world, often people with disabilities are not compensated, and we expect them to do the educational work, but we expect that we want our speakers to be compensated.

So there’s a small stipend that they get, and that was not allowed by the WordPress Foundation. So we explored other options, and we incorporated ourselves as a 501 C3. So we are a nonprofit organisation within the United States. And we exist under the fiscal umbrella, or the kind of oversight, fiscal oversight, of a larger nonprofit called Knowbility, that does a lot of work around education and accessibility awareness.

That gives us the, we have the nonprofit piece, and so we just have three board members, so it’s not huge. And then we have the organising team for the event that has grown quite dramatically. You know, Isla talked about things kind of improving year to year, but this is by far the most organisers and volunteers that we’ve had, in terms of getting things put forward.

And we’ve been able to do some amazing new things. You know, Isla mentioned the marketing efforts that have really stepped up this year. But we’ve also had some folks step forward, not so much related to the day of the event, but to start doing some translation so that we’re able to, you know, all the talks happen in English, but we are wanting to be sure that we’re finding some ways to translate those into Spanish, and French, and other languages that folks are interested in having them appear in, so we can spread the word.

[00:11:56] Isla Waite: Shout out to Joni for all the work she’s done for that.

[00:11:59] Bet Hannon: New translation lead, so that’s been amazing.

[00:12:01] Nathan Wrigley: So a lot of the events that are online in the WordPress space, a lot of them are free to attend, certainly. Some of them are, you know, there’s a gatekeeping aspect to it, it might be financial, it might be the surrender of an email address or something like that. Is there any barrier to participating in this event during the day, or can literally anybody rock up and consume the content that you are creating?

[00:12:23] Isla Waite: I was just commenting that, wouldn’t that be terrible if we put a barrier in the way of people accessing WordPress Accessibility Day?

[00:12:30] Bet Hannon: We’ve worked really hard to make sure that there are no financial barriers for attending this. And so you can come to WordPress Accessibility Day. The only thing you need to do is surrender your email because you need an account to log into the Zoom, to attend the events. You can opt in or out of our mailing list though. So it’s free to attend.

We offer you the option to give a $10 donation. If you want an event t-shirt, you can make a $50 donation. If you want to micro sponsor your company for $150, you can do that. But we have some amazing sponsors that have come in to help us put on the event.

It’s more than just needing a streaming service to be able to do the event, because we’re offering live captions, because we’re talking about technical matters, sometimes that’s an issue, right? We have to have folks that are really skilled at doing those sorts of live captions. We’re offering live ASL interpreters during the event. And then, really quickly after the event, within the next few weeks, there’ll be professional transcriptions done.

As you probably know, when you are doing a transcription of an audio, not a lot of them that are technical get everything right, the AI versions of those. And so having folks that are skilled to do that is a piece of that.

So those things together, having the streaming service, and all those other things to get it all out, our amazing sponsors are helping us to do that in a way that makes it free for people to attend.

[00:13:52] Nathan Wrigley: So if I was to show up and I surrender my email address, it’s going to be taking place through Zoom, and you’ve given some nice options there for some things that you can do to help the cause, if you’d like to buy a T-shirt or what have you.

But if I turn up and I wish to read the captions, I think you mentioned there that you’re going to be having live captions. That implies, although I could be wrong, that you’ve got a human, a person actually transcribing them in real time.

And I think you’re right, the option to do that with technology falls over so quickly with technical terms. And no doubt, a WordPress event, there’s going to be hundreds of words bandied around, which wouldn’t be accurately transcribed, so that’s really nice. So you’ll be able to read those, and I’m guessing that that will be in English.

[00:14:33] Bet Hannon: Yes. Initially, all the presentations and all the captions will be in English.

[00:14:36] Nathan Wrigley: And is that the case for all of the presentations as well? I was to, yeah. So everything throughout the 24 hours is in the English language, and the captions will be in the English language as well, okay.

[00:14:46] Bet Hannon: Right. And our hope is that, you know, our volunteer translators are going to be getting to work fairly quickly, and starting to put those out as they can, right? Again, the translation pieces are all done by volunteers.

[00:14:58] Nathan Wrigley: Oh, okay. So, as soon as the session has ended, you’ve got, in your team of volunteers, there’s a bunch of people who are going to be transcribing those into, well, I’ll just name some languages and you can tell me, things like Spanish, and Italian, and what have you, and Japanese and things like that.

[00:15:11] Bet Hannon: The big focus is Spanish, and then after that French, just in terms of the number of places that those languages are spoken. But we do have volunteers that pop up, for example, you know, there’s some languages in the different regions of India that people have an interest in making sure that the talks are available to their communities, and so folks can step up. And so if you have folks that, you know, I was in an interview earlier today, and someone expressed an interest in translating for Arabic because they want their community to be able to access this information. So if you have a community that you want to volunteer to help translate for, reach out.

[00:15:46] Nathan Wrigley: Bet, where would we reach out to?

[00:15:48] Bet Hannon: So the wpaccessibility.day is the website, and we’ll get you the link for that. And then there’s a volunteer section, and people can volunteer.

[00:15:56] Isla Waite: I think it very much depends on where we can get volunteers from. We have ideal languages that we know are very popular in our part of the world, but we want as many languages as possible. So there’s really no restriction on who might volunteer and from where. And if you can speak another language, then we want you.

[00:16:13] Nathan Wrigley: I’m just going to ask a question one at a time. And, again, we’ll just go in the order of the people that we did before, so I’ll start with Isla. It’s a personal question so you can answer this in any way that you like.

Why have you gone in the direction of accessibility? Given all the interesting things that you can do online, why has accessibility become such a crucial part of your life, such that you are being involved, and giving up probably quite a lot of your time to organise an event like this? So it’ll be the same question, but we’ll begin with Isla.

[00:16:38] Isla Waite: For me, I don’t think it’s any one thing. I think a number of things sort collided at the same time for me in my professional career and private life. Like I said, I’ve been a project manager for more than a decade, with a background in graphic design. Before that I was in the military.

I am a very mission-focused person, and I was finding after a decade that, as much as I love my clients, I have some wonderful clients, I felt like, I need something to dig my heels into, and my fingers, and my brain, that has a bigger impact. And I think a lot of people find that at some point in their career. I just needed to see that I was somehow making a difference. Just little me, you know, little part of it, little butterfly wing situation.

So that was part of it. And then, like I said, I stumbled across the Accessibility Day, Accessibility meetup. I was just intrigued. At that point I was really just learning what accessibility was. I stumbled upon the quote by Tim Berners-Lee, you know, the internet, access for everyone regardless of disability, which is now in my signature block.

And then my father was diagnosed with Alzheimer’s, which is one of those hidden diseases for a long time. But early on, I watched him struggle on the internet. So he’s, at the time, in his sixties. I was watching over his shoulder, just sort of trying to do something really simple. I was like, huh, this could happen to anybody, it’s not just Alzheimer’s. I’m very interested in the cognitive side of things, as much as the seen disabilities.

Anyway, that all sort of happened at the same time, and I decided, this is a path for me I think. And then just recently, I got involved with IAAP, the International Association of Accessible Professionals, and I just passed my CPAC. So yeah, for me it’s about getting on a path for the rest of my working life, and maybe beyond, where I feel like I’m doing something that my heart is driving.

[00:18:18] Nathan Wrigley: What a lovely answer. That’s great, thank you. Same question to Bet.

[00:18:23] Bet Hannon: Yeah, so I had been around flagship WordCamps and hearing about accessibility a little bit. But in 2016 we had a, one of our clients mentioned they needed help making their site accessible. And so that was when we really, about eight years ago, we really dug into learning about accessibility.

And when our team did that, we realised all of us on the team had people that we knew that were impacted. And we saw the difference it makes in people’s lives, to be able to be independent, and have sense of human dignity in being able to do stuff on the web.

And so much so that we shifted the focus of the agency. So it is what we do, but it’s, my take on it is, I hope we work ourselves out of work. I mean, if we could get to the point where nobody needs help learning how to do accessibility, because it’s just something we all do and know how to do. And so that’s a piece of what drives me to work.

With Accessibility Day, is really just sort of extending that education and finding ways to help people learn and grow, and know how to do accessibility better. Because I think when we know better, we can do better. But to think about building in empathy for different ways of accessing the web. It’s just a huge part of what I want to be about, so this organisation gives me a chance to do that.

[00:19:40] Nathan Wrigley: Yeah, another great answer. No pressure at all, Ryan.

[00:19:43] Ryan Bracey: I know, I can’t believe I have to follow those two.

[00:19:46] Nathan Wrigley: Two really powerful messages, so over to you.

[00:19:49] Ryan Bracey: Similar to Bet’s timeline, right around 2016 for me. I’ve been a developer for, gosh, probably over a decade as well. But around that time period, 2016, we had a lot of clients coming to us mentioning accessibility. And up to that point in my career, it hadn’t really been something I knew much about, or given a lot of focus to.

Started really focusing on it because it was a client ask, obviously something I needed to do for work. And as I went down that path of researching, what is this? What do I need to do to be compliant? I stumbled across Amber Hind’s accessibility meetups, started attending those, found this really warm and welcoming community.

And just the whole push behind it, or the movement behind it even of, when you do this work it’s, I mean, yes, at the end of the day, we’re just creating websites, but it’s something so small that, why should we ever create a website that not everyone on earth can access? Meaning, yes, it doesn’t seem like a huge impact overall, in the big scheme of the world, but everyone has the right to be able to do anything anyone else can do. So why not just something as simple as browse the web.

And then as you really dive more into it, you realise a lot of the things you do to help cater to the accessibility crowd, you’re also catering to everybody in the world. So when you make something easy for one person, you make it a lot easier for everybody. So there’s added benefit across the board. It makes your work a lot better, it makes your work more accessible, everyone can participate.

I was also lucky around that time to find WordPress Accessibility Day. So I volunteered as a moderator, I believe I was three years ago. At the same time in my professional life, at my company, we went through massive growth. We had some restructuring, I was promoted to director of the website department. So as part of that role, I was tasked with also becoming more active in the community. So already had spoken at Amber’s Meetup, I was already a little bit of a part of Accessibility Day, so I took a larger role as an organiser. Lucky enough to work at a company that gives me the ability to do those things, and encourages me to do those things.

I think to echo what both Isla and Bet have said, it just really kind of gives meaning to your day, to know that what you’re doing is making someone’s life a little bit easier.

[00:22:08] Nathan Wrigley: That was also a fabulous answer. I think, in the last sentence, you encapsulated it in the one word, meaning. I think maybe that sort of sums it up. It gives some significance to work, which could otherwise be fairly technical and a bit dry. You know, if you’re just building websites all day, every day, I think it would be easy to, I don’t know, maybe you are fascinated by that for its own sake, but it would be easy to lose sight of that.

And everything that you’ve, the three of you have just mentioned, points to a kind of more moral dimension to the work of building a website. I get this intuition, having spoken to many people in the community that you are in, that it seems to be replete with genuinely nice people, which is just lovely. I mean, the WordPress community itself is fairly nice, but then there’s a subset of that community, the WordPress community, the accessibility in WordPress community, which seems to have its own high level of loveliness, for want of a better word.

[00:23:07] Bet Hannon: Well, Ryan kind of touched on that, you know, like finding this warm community. And I think that’s, you know, a lot of us work from home, and serving on this planning, organising team, for me, and I think for others too, is a way that we really connect every week. You know, we’re meeting most of the year, every two weeks. We’re now in the kind of pitched lead up to the event, so we’re meeting every week, and we get a chance to know one another. A lot of us have never met face to face yet, but we’re just a part of each other’s lives in a way that is genuinely warm and supporting, and that’s awesome too.

[00:23:38] Nathan Wrigley: Yeah, that’s really nice. If somebody was to be listening to this and decides, you know what, I’m going to show up for the Accessibility Day 2024. Are there parts of the event which enable socialising, for want of a better word, or is it all about the presentations, or do you have, I don’t know, breakout rooms, or some way in which people can facilitate what you’ve just mentioned? You know, this kinda moral aspect, this nice camaraderie that you’ve all got.

[00:24:02] Bet Hannon: If you only log into the Zoom, then you’re just consuming the presentations. But there is a Slack channel that you can get access to, and there will be a lot of chatting going on there. And that’s where you’ll get notified if you win any of the sponsors prizes, and the drawings and those kinds of things. So the Slack channel is the place where you could start to make some connections.

[00:24:24] Nathan Wrigley: So there are opportunities for that. So, dear listener, if you are going to attend then, you never know, you might come out of it with a bunch of new friends as well, which is really nice.

I’m just looking at the website itself, you have the most fabulous URL, by the way. It’s wpaccessibility.day. I mean, it couldn’t be better, that’s just great. Well done for bagging that one. That website itself, I’m presuming had to go onto the microscope quite a lot. Given the nature of the event, it would be somewhat remiss if the website had glaring accessibility errors in it.

I don’t know if any of you three have been involved directly with the website, but I’d be interested in hearing some of the challenges. I think we all know that the idea of a hundred percent accessibility is something a bit off there into the distance, and it may never be achievable in anybody’s timeframe. But, what are some of the things that you’ve really gone out of your way to make as accessible as possible over there?

[00:25:14] Bet Hannon: I want to like give a shout out to Ryan because he designed that website for us.

[00:25:19] Ryan Bracey: Thank you Bet.

[00:25:20] Bet Hannon: It’s awesome. Do you want to talk a little bit about that, Ryan?

[00:25:23] Ryan Bracey: Yeah, absolutely. So as I mentioned, I do work for a branding agency, and as part of my involvement last year with Accessibility Day, we donated our agency resources to the group. There was interest to go through a rebrand, get a new logo, get a new entire branding.

So my wonderful branding designers that I work with, and I’ll give him a shout out, Jay Zawislak, he is our creative director, took this on. He designed the logo, chose the color palette, chose the fonts. And when he went through that exercise, he worked pretty closely with myself, just because I’m a little more versed in accessibility.

But we were really looking at, from step one of coming up with the brand, are these fonts accessible? And accessibility, as you mentioned, there is no a hundred percent, it is a spectrum. What works for one person might not work for another person, and vice versa. But you can look at small things like, if I do a lowercase l, a capital i, the number one, are those glyphs all different? Is the spacing between letters enough that it’s easy to read? Are the characters distinct enough that they’re easy to read?

So even looking at fonts in that way, when we were picking colors, we were comparing all the colors against each other to make sure contrast worked. So wherever text is laid over a color, those have been checked.

We also then took an opportunity to kind of showcase what can be done in an accessible website design. So when I designed it, I worked closely with our other board member, Joe Dolson, who actually started Accessibility Day, and now leads our website team as well, developed the website. And we decided to try to showcase things that can be done to make a site beautiful and accessible, because there is a little bit of a misconception within the design community that accessible design means ugly design, which is not true.

So we even, you’ll notice at the top of the site if you are on it, there is a toggle to go into kind of a dark mode. We really wanted to showcase that this can be done in an accessible way. It honors users’ browser preferences. If you prefer dark, it’s in dark by default. If you prefer light, it’s in light by default. We made sure when you switch it over everything is accessible in that mode as well. So that was done very intentionally too, because dark mode was kind of a big trend last year. So when we did the site, we wanted to show that can be done accessibly as well.

We used a lot of pastel colors. Again, those are often seen as inaccessible. So showing that actually you can have a very colorful site, you can have a soft colorful site in a very accessible way. So a lot of thought went into it. And it was, like I said, kind of used as a showcase piece to say, actually, you can be accessible and beautiful at the same time. You just have to put a little bit more thought into it, but you can have a good product at the end of the day.

[00:28:08] Nathan Wrigley: It’s really nice. I should say, I probably misspoke a little bit, given when this podcast is going to air, the URL that maybe would be more relevant is 2024. So the URL is the numerals 2024.wpaccessibility.day. That will actually get you to the current version of the site. It looks broadly similar, doesn’t it? You know, the design aesthetics, and what have you. But it’s absolutely marvelous. And so thank you for all of the hard work you’ve put in there.

Just out of interest, Ryan, because you’ve been in the weeds with that, how much extra work, if you like, and I know this is a sort slightly contentious question, but if you had built this website, I don’t know, with some kind of page builder technology built inside a WordPress, and you’d had no thought to accessibility at all, against the version that we’re looking at now, how much more time do you actually have to spend on it? Was it a significant overhead, or is it just now muscle memory for you that you can just do it all at the same speed as you would with any website?

[00:29:05] Ryan Bracey: I find there’s actually not a lot of extra work that goes into making something accessible, like I kind of alluded to, it’s just having that thought in your head beforehand. So to kind of draw a design analogy, if you know you’re working with a brand that has a red and black color palette, you know you have to design in red and black. It’s no harder, or easier, or more work, or less work than designing a blue and green website, it’s just a different approach. You have to think about it a little differently.

So accessibility works in the same way, you just go into it knowing, I have to make sure that my fonts are big enough, I have to make sure I’m not pairing fonts, colors, and background colors that no one can see. I have to make sure, if I’m introducing functionality, I’m introducing something that’s well known, it’s being introduced in the right way, I am doing it in a way that’s easy for everyone to use.

[00:29:57] Bet Hannon: It’s really just kind of an additional, thinking about user experience.

[00:30:01] Ryan Bracey: Right. I was going to say, at the risk of sounding controversial, it kind of just is, if you’re good at user experience, you’re good at accessibility.

[00:30:09] Isla Waite: And it gives you boundaries. I know so that many designers flail without some kind of boundaries. And yes, the brand gives you some boundaries but, you know, I was talking to another designer recently, and it’s designed with purpose. That’s how I look at accessibility. Yes, you have a brand, but now you’re designing with a purpose. And going after it like that, everyone just totally is on the same page immediately. As long as the team has an accessible culture, it’s not any different to designing the old way.

[00:30:35] Ryan Bracey: Yeah, it’s essentially just laying out a larger set of design requirements at the beginning of a project.

[00:30:40] Nathan Wrigley: We’re at an interesting time with accessibility because I feel, I’ve said this a few times on this podcast, that if we rewound the clock a decade, then accessibility wasn’t really, it didn’t really have a spotlight on it particularly. But now it really does, almost that it’s the thing of our time. You know, in the year 2024, it really does feel like one of the most talked about subjects.

I think there’s a couple of reasons for that, and the one is the moral dimension that you mentioned, all three of you alluded to that. And actually it felt like that was the dimension for the three of you, you know, the moral aspect to it. And probably behind that a little bit, the community that is behind that moral dimension.

But increasingly, I think there’s going to be a legal dimension as well, where the carrot, if you like, the moral thing, you know, dangle the carrot and hopefully people will come along. That will work for some people, you three being prime examples. But the stick, the legal aspect I think is coming fairly soon. I know that in the European Union, we’re going to have legislation coming around next year, which will make this all the more important.

So attending events like this feels like, really, if you’re not skilled on this, this is the perfect moment to get involved, because at some point somebody might be knocking on the door with some paperwork that you don’t necessarily want to read. That’s not a particularly great reason to do it, but it is a fairly compelling reason. And I don’t know if anybody’s got anything to say about that, about the legal aspect, and the ambulance chasing lawyers and all of that coming up.

[00:32:10] Bet Hannon: The reality is, for a lot of medium and small businesses, they tend to put off a lot of compliance things until they have to. That’s just sort of the way that they are, because of the revenue is just not there to do it often, so that happens. But people do come on board, and try to work at what they are required to do.

And you’re right, we already have that in the US with the serial plaintiff lawsuits. We’re gearing up for the enforcement of the European Accessibility Act. But even in the UK and other places, there are other laws already there that are starting to be more enforced.

And so, yeah, legal compliance is a thing. That is the main topic of our keynote speaker at the event this year in fact. Lainey Feingold is a US attorney who has been instrumental in accessibility law throughout the United States. She got involved with some of the early lawsuits around bank customers who were suing their banks over non-accessible ATMs, primarily blind consumers suing them. And out of that developed a kind of, structured negotiation, bringing together the people who build the ATMs, and the people who are blind who need to use them, and the users.

And so it kind of builds on that user experience that we were talking about before, bringing folks together rather than being antagonistic. I mean, I think people do want to do the right thing. So I don’t know how much of those stories she’ll tell us in her keynote, but she was very, you know, if you’re in the US and you have an ATM with braille on it, Laney was a part of that. She’s going to be talking about the legal landscape for the WordPress community, and I’m really excited about that.

[00:33:52] Nathan Wrigley: Yeah, that’s a nice segue Bet actually because, again, the URL 2024.wpaccessibility.day, and then if you add forward slash schedule, to the end of that, you’re going to be able to see what’s going on. And as you said, right at the top of the list is Lainey’s keynote address.

But then underneath that we have all of the different bits and pieces that are rolling out over the following 24 hours, and they’re all clearly labeled, the times that you can see them live, and what have you.

I’m going to put you all on the spot and ask for you to pick one, or maybe two, that you are particularly excited about. Now, caveat emptor, I am not suggesting, even for a moment, that if you pick two, that means the others are in any way, shape, or form, less worthwhile, let’s put it that way. We understand how this works. We can’t mention all of them because we just don’t have the time. But if you find that to be a fair thing to do, I’ll start with, well, let’s go with Isla. Couple that you are particularly excited about, or one, whichever you like.

[00:34:48] Isla Waite: Well, I’m going from my brain, and I’ve only really studied the schedule twice. Once when I was, this is how the process goes, I was eliminating all indication of who these speeches, presentations come from, so that the speaker’s team could go through that, and it was anonymised so there’s no favoritism or anything, so yeah, that’s how it’s done.

So that was my first exposure to, all of the applications of the speakers, which were somewhere in the region of 80 to 100. So the team did an amazing job of getting through all of that, and coming up with the 24, 25 presentations.

I’ve since looked at it once because we’ve been pretty busy. So from the top of my head, I know there is one that focuses on a culture among developers, and that stuff is obviously very, very interesting to me because I work, I guide the team or whoever’s involved in a particular project.

And that involves people who work predominantly with me, and people who work with the organization that we’re helping. It becomes a very molded team of people who need to understand how this all works, and how you’re going to keep doing it going forward.

So I’m always interested on other people’s approaches to that. And I believe that speakers from Hungary, so I’m super excited to hear about that perspective from another country.

[00:35:57] Nathan Wrigley: There’s one right in front of me at the moment which is entitled, Creating a Developer Culture of Accessibility and it’s Jessie Frio, Mark Steadman. So maybe that was the one that you were thinking of. So there we go, we’ve managed to find that one. That’s great. Okay, let’s go to Bet. Same question.

[00:36:12] Bet Hannon: I am, not so much the presentations, I am super excited about hearing Lainey’s keynote. I do a lot of work with folks that are trying to wrestle through all those legal compliance things, and that’s just the nature of what I end up doing with a lot of folks. So I just eat that stuff up, and I really eager to hear from her, she’s a great presenter too.

[00:36:31] Nathan Wrigley: Perfect. So we’ve had a culture one, we’ve had a compliance one. So, yeah, over to you, Ryan, for the last one or two.

[00:36:37] Ryan Bracey: Oh wow. As the speaker lead organiser, I feel like I love all my children. We do have some really interesting topics this year, maybe I’ll answer it that way.

To go off Lainey’s keynote, we do have a few other talks that kind of focus around the legal landscape this year. This was a big push for us to get speakers in that area because it is becoming more prevalent.

We also have some interesting talks that focus around accessibility from a designer aspect, which I think is an oft overlooked topic. I think a lot of times it just falls to the developer, when it’s really something that starts in the beginning.

We do have some interesting culture ones, that talk about how to structure accessibility within your company.

But there is one talk I am actually pretty excited about. It is called, How to Remediate Accessibility Issues in WordPress by Cam Coulter. And I think that one’s going to be very interesting to our audience because he’s talking specifically about how to address issues that pop up in WordPress, which, as WordPress developers, we know is not often a fully hardcoded, self-built system. You’re working with a lot of page builders, plugins, third party developers, software systems. So he’s talking about how to identify those things, and make changes when maybe you don’t have access to that source code.

[00:37:53] Nathan Wrigley: Oh, well, thank you. That was nice, all three of you giving us a very different answer.

If you go to that page though, although it might sound on the face of it that accessibility is a niche, it turns out that niche is really broad. I’ll just go through a few, I’m just looking at the page now. So the one that you just mentioned, Ryan, How to Remediate Accessibility Issues in WordPress.

Then there’s one about agile accessibility, Building Inclusivity into the Product Roadmap. Practical Accessibility Tips for Content Creators. Accessibility Challenges with Single Page Applications. Why can’t I use my brand color there, and if not there, then where? That’s an interesting one. Is your page builder, accessible? Captchas and other gotchas. CSS tiny tips. Insights from a community driven survey. Developing accessible Gutenberg blocks. That one would capture I think.

I’m about halfway down the page and I’ll stop there. But you’ve immediately got the idea that this not one thing, there really is a whole broad church of things to be consuming and getting involved in.

So I know it’s not the three of you entirely, but I think this event is going to be absolutely fabulous. So just quickly, one more time, 2024.wpaccessibility.day. Just before we knock it on the head, as we say in the UK, just before we finish, is there anything that you want to just mention as a way of rounding it off? Something that I failed to ask, something that you think was important say. Let’s go round the houses. Let’s start with Isla.

[00:39:19] Isla Waite: Yeah, I want to tack on a little bit to Bet’s comments about the legal stuff. It’s been a big thing in California recently, and I’m definitely not going to go into the details of that. But, you know, eventually California will sort itself out and there’ll be some kind of law that makes sense.

But something that came up in the draft of that bill was compliance, and somewhere else, I believe the word conformance was used. I’ve studied those words a lot having just done my CPAC. Compliance being a legal thing, conformance being in the spirit of. And with all this talk of laws, and people definitely being worried and, scared and, you know, Bet’s clients and mine as well, oh my gosh, how do I get compliant?

Yes, that is super important and, yes, it’s probably going to be the law. But for everyone else who’s just trying to get on board and figure this out, start with conformance. Start with doing something in the spirit of accessibility. All you have to do is squint at your colors and figure out, can I see them if my eyesight’s not very good? There’s so many places you can start to conform, and work in the spirit of accessibility. And I hope lots of those people come to WordPress Accessibility Day 2024.

[00:40:25] Nathan Wrigley: Nice. Thank you for that final comment, that’s lovely. And, Bet, anything you wanted to add?

[00:40:30] Bet Hannon: Yeah, I think a lot of times, we’ve kind of alluded to it a couple different times, some of the stuff Ryan talked about. A lot times people think accessibility is something very complex, that only specialists can do. And I try to help people understand, you know, start where you’re at, and if you can put alt text on images, and make sure your heading structures are right, and make sure your link texts are there, and work on your color contrast. That’s a lot of accessibility issues, and they don’t necessarily require very much technical knowledge at all, right? Content creators do a lot of that work. And so get started and start learning, but also, the more you educate yourself, the more you can stop creating inaccessible content.

[00:41:11] Nathan Wrigley: Nice. And it feels like this event is perfectly poised for that. Whether you are really deeply into this journey, there’s content here you. But you are the 101 stage, and you just want some tips right at the outset, there’s things here well. Okay, thank you. And, Ryan, rounding us off.

[00:41:25] Ryan Bracey: Yeah. And I just wanted to say, and Nathan, you alluded to this but, as you read our schedule, we do have a little bit for everybody, and we took a really concerted effort to make sure that this wasn’t a fully technical conference. If you’re not a developer, there are going to be talks for you here. If you’ve worked in accessibility for years, there will be talks for you here. If you’ve just heard about accessibility today on this podcast, there are talks for you there.

So as we’ve mentioned, it is free to attend. So if you go to our website, you can register right now. It’s October 9th, block off your calendar. Each session only lasts for 45 minutes. One happens every hour, so you can kind of watch them at your leisure throughout the day. And like I said, we have something for everybody. So no matter what position or role you work in, no matter where you are in your accessibility day journey, you can probably find a talk that is relevant to what you are looking to get out of it.

[00:42:15] Nathan Wrigley: Thank you so much. And playing it forwards a little bit, I would also draw attention to the menu on the URL, which we’ve been mentioning, 2024.wpaccessibility.day. Couple of things, there’s a volunteer menu item, maybe go and check that out if you’re interested in supporting the event going forwards. And also a donate menu item as well if you want to support the endeavors in that way.

That has been a really interesting podcast. If you are new at accessibility, this event is for you. If you’re experienced, this event is for you. And if you would like to possibly make some new friends in a different community, this event is also for you. So it’s got a bit of everything for everybody.

Thank you so much for chatting to me about it today. Thank you, Isla, thank you Bet, and thank you, Ryan. I really appreciate it.

[00:43:03] Bet Hannon: Thanks for having us.

[00:43:04] Ryan Bracey: Yeah, thank you.

On the podcast today we have Isla Waite, Bet Hannon and Ryan Bracey.

Isla Waite, originally from the UK, has lived in Sacramento, California for 17 years. With a background in graphic design and over a decade in website project management, she recently started her own accessible web design business. Three years ago, Isla joined the WordPress Accessibility Meetup, led by Amber Hinds, which has led to her involvement with the WordPress Accessibility Day. She is now a team lead, managing the tech and vendors teams to promote web accessibility.

Bet Hannon has worked with businesses and nonprofits for over 16 years, helping them build WordPress websites, integrate other communication channels, and learn how to use digital marketing tools more effectively. She is the founder & CEO of AccessiCart, a services agency that focuses on accessibility and eCommerce, along with other high user interaction websites. Bet lives in Bend, Oregon, and is a co-organizer of the WordPress Meetup there.

Ryan Bracey is the Director of Web Development & User Experience at Second Melody. A mid sized branding agency located in NJ, which builds custom WordPress websites for clients of all sizes and industries. In this role Ryan has taken a holistic approach to accessibility within the agency by promoting collaboration between clients and departments alike, to ensure all phases of a project are completed with intention.

During the podcast we discuss the significance of WordPress Accessibility Day, which is a 24-hour virtual conference running on 9th to the 10th October, 2024. It’s free to attend and will offer a wealth of resources around the topic of WordPress accessibility. The event will include live captions, ASL interpreters, and professionally created event transcriptions. It’s being driven by a team of passionate volunteers and is geared towards making the digital space accessible for all.

We cover the logistical details, including how to register and the optional donations and sponsorships that can enrich your participation. Our guests share their personal motivations and experiences that fuel their dedication to the accessibility cause. We also get into the global reach of the event, with translation efforts and volunteer opportunities that make WordPress Accessibility Day 2024 a truly inclusive initiative.

Isla, Bet, and Ryan talk about the challenges and triumphs of advancing web accessibility, the importance of both conformance and compliance, and practical steps you can learn about during the event to make your website more accessible. Whether you’re a developer, a designer, or a content creator, this episode is packed with insights and inspiration to help you contribute to a more accessible web using WordPress.

If you’re interested in making the web a more accessible and inclusive place, this episode is for you.

Useful links

WP Accessibility 2024 website

WordPress Accessibility Meetup

AccessiCart website

Second Melody website

Knowbility website

International Association of Accessible Professionals website

by Nathan Wrigley at September 25, 2024 02:00 PM under podcast

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:

October 06, 2024 01:30 AM
All times are UTC.