WordPress Planet

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

September 24, 2024

WPTavern: Automattic Responds to WP Engine’s Cease and Desist with Legal Action

After the incidents at WordCamp US 2024, WP Engine sent a “cease and desist” letter to Automattic demanding that Automattic and its CEO, Matt Mullenweg, retract and stop making false, harmful, and disparaging statements about WP Engine.

Automattic Confirms Legal Action 

Matt Mullenweg has confirmed that they have officially initiated legal action against WP Engine for the “Unauthorized Use of WordPress Foundation and WooCommerce, Inc. Intellectual Property” and requested them to stop the unauthorized use of trademarks belonging to Automattic & Woo. 

The document reads, “Our Client owns all intellectual property rights globally in and to the world-famous WOOCOMMERCE and WOO trademarks; and the exclusive commercial rights from the WordPress Foundation to use, enforce, and sublicense the world-famous WORDPRESS trademark, among others, and all other associated intellectual property rights. We are writing about WP Engine’s web hosting and related services that improperly use our Client’s WORDPRESS and WOOCOMMERCE trademarks in their marketing.“

The letter further asserts: “We understand that our Client has contacted you about securing a proper license to use its trademarks, yet no such agreement has been reached. As such, your blatant and widespread unlicensed use of our Client’s trademarks has infringed our Client’s rights and confused consumers into believing, falsely, that WP Engine is authorized, endorsed, or sponsored by, or otherwise affiliated or associated with, our Client. WP Engine’s unauthorized use of our Client’s trademarks also dilutes their rights, tarnishes their reputation, and otherwise harms the goodwill they have established in their famous and well-known trademarks, and has enabled WP Engine to unfairly compete with our Client, leading to WP Engine’s unjust enrichment.

The legal team also accuses that, “WP Engine has developed a business generating annual revenues of over $400 million, which has been based entirely on extensive and unauthorized uses of our Client’s trademarks.”

Automattic’s lawyers warned, “Our Client is entitled to file civil litigation to obtain an injunction and an award of actual damages, a disgorgement of your profits, and our Client’s costs and fees. Our Client also is entitled to seek an award of attorney’s fees due to the bad faith and extraordinary nature of WP Engine’s knowing and willful infringements.” 

But Automattic is willing to amicably resolve this matter, including through a licensing relationship for use of its trademarks. WP Engine has time till October 03 to confirm its understanding of and compliance with Automattic’s requests including the below ones. 

The document also contains screenshots (shared below) from social media and WP Engine’s website, highlighting alleged misuse of trademarks and community confusion.

The legal battle between the two giants will have long-term effects on the community at large. Even more interesting is that Automattic had invested in WP Engine in 2011. 

More About Cease and Desist Letter From WP Engine 

WP Engine’s cease and desist letter stated that “WP Engine is fully prepared to take all necessary steps to protect its business, employees and customers, as well as the entire WordPress ecosystem, from the harm Automattic is attempting to inflict upon them.” 

The document stressed that “Automattic and its CEO Matthew Mullenweg must immediately cease and desist from disparaging WP Engine and/or its investor by making false factual statements.”

“Mr. Mullenweg’s statements also reflect a clear abuse of his conflicting roles as both (1) the Director of the non-profit WordPress Foundation, and (2) the CEO of at least two for-profit businesses that compete with WP Engine. From his sham assertion of trademark rights, to his market-wide disparagement, to disruption of known business relationships by either convincing or coercing WP Engine’s customers from doing any further business with it, these acts reflect just a few examples of Mr. Mullenweg’s unethical abuse of power. That Mr. Mullenweg quietly demanded tens of millions from WP Engine for his for-profit company while publicly claiming to be selflessly safeguarding the interests of the community is shameful.” WP Engine’s legal team stated. 

From WordPress #Announcements Slack channel

Matt also attended a Twitter Spaces discussion and Courtney Robertson has shared an AI-generated version of its transcript.

Other Developments

WP Engine’s News Feed Removed?

Matt tweeted about rumors that WP Engine removed the news feed from wp-admin dashboards. Some users confirmed that the whole WordPress News Metabox has been removed from the WP Engine dashboard but is still available in Local.

Users were divided on the widget’s importance, but several people expressed dissatisfaction with WP Engine’s move.

WP Tavern Articles Missing?

A Reddit post alleged that several WPTavern posts had disappeared after the WC US Q&A session. However, WPTavern founder Jeff Chandler debunked the claims, stating, “With some help, I conducted a thorough investigation and I can confidently say that not only were those posts not deleted, they never existed.” The Reddit post was later deleted.

(This concludes Part 2. Stay tuned for Part 3.)

by Jyolsna at September 24, 2024 11:58 PM under legal action

WPTavern: Highlights from Matt Mullenweg’s Spiciest Word Camp Presentation at WordCamp US 2024

The highly anticipated Q&A session with Matt Mullenweg at WordCamp US kicked off with him stating, “This might be one of my spiciest WordCamp presentations ever.” He opened the session by reading his recent article, WordCamp US & Ecosystem Thinking, set against the backdrop of jazz music. Matt then used the analogy of the “Tragedy of the Commons” to discuss the importance of Five for the Future. He also addressed his cryptic tweets and warned about the potential threat of private equity hollowing out and undermining open-source communities.

Key Points from the Q&A Session

This might be the last Word Camp you see WP engine have a booth at.

– Matt Mullenweg

Matt said that most of the information he’s about to share in the presentation has come from WP Engine employees who reached out to him. WPEngine is controlled by Silver Lake a Private Equity Firm that in Matt’s words “doesn’t give a dang about your open source ideals it just wants return on Capital.” 

He went on to discuss the fate of other companies Silver Lake has acquired. In 2010, they bought 25% of Talend and proceeded to monetize its open-source user base, eventually generating 20x returns over seven years. Silver Lake also bought 5% of Unity for $400 million and raised prices drastically, leading to multiple CEO changes and the rise of the open-source alternative, Godot Game Engine.

Silver Lake, valued at $102 billion, also owns WP Engine, but Mullenweg criticized the company for contributing little to the WordPress community’s “Five for the Future” initiative. He referred to Lee Wittlinger, the Managing Director of Silver Lake, as “a schoolyard bully” and announced that WP Engine would no longer be allowed at future WordCamps.  

Mullenweg offered to return the $75,000 WP Engine had paid to be a Super Admin Sponsor and also accused them of misusing the WordPress trademark. “WP Engine sounds like WordPress, and their colors are even similar to WP’s blue. There’s brand confusion.”

He also touched on broader issues, noting that WordPress growth had slowed in the last 18 months, partly due to changes in W3 Techs’ methodology and non-contributing companies outcompeting contributing ones. However, he pointed out that WordPress had recently regained momentum and “grown an entire Drupal of market share.”

What we create together is bigger than any one person.

– Matt Mullenweg

Matt admitted he didn’t want to make the presentation but felt compelled to speak out against bad actors. “The only way to fight a bully is to fight them back. If you just allow them to run rampant on the playground they’re just going to keep terrorizing everyone.”

Mullenweg explained that he had attempted to discuss increasing WP Engine’s contributions, but after receiving no positive response, he felt it necessary to call them out publicly. He encouraged users to consider switching to hosts that actively contribute to WordPress when their WP Engine contracts are up for renewal. He also emphasized that WP Engine employees are not at fault and that he supports those who speak out about their company’s lack of participation in the WordPress community.

Mullenweg also shared some exciting developments for WordPress, including upcoming Google Docs-like collaboration features. He stressed the importance of software licenses, likening them to the Constitution, as they guarantee freedom. Additionally, he expressed his pride in seeing WordPress adopted by the U.S. Army and the federal government.

A fan of AI, Mullenweg advised developers to explore AI-assisted tools like Cursor and also promised to honor Jessica Lyschik’s Speed Build Challenge.

The video of Matt Mullenweg’s Q&A session at WordCamp US is now available on YouTube.

Phase 2 – Matt’s Next Steps

Matt’s statements at the WordCamp session were just the beginning. He then followed up the attack on WP Engine by publishing WP Engine is not WordPress in WordPress.org. One of his major criticisms was that WP Engine is the only WordPress hosting provider that disables revisions by default. 

He didn’t mince words, stating, “What WP Engine gives you is not WordPress, it’s something that they’ve chopped up, hacked, butchered to look like WordPress, but actually they’re giving you a cheap knock-off and charging you more for it. This is one of the many reasons they are a cancer to WordPress, and it’s important to remember that unchecked, cancer will spread.” 

“WP Engine is setting a poor standard that others may look at and think is ok to replicate. We must set a higher standard to ensure WordPress is here for the next 100 years.”, he continued. 

He then launched a Twitter poll asking the community if WP Engine should be allowed to have a booth at the next WordCamp, and the majority voted in favor of WP Engine’s continued presence.

Response From WP Engine

In response, WP Engine published a blog post titled Highlighting Over a Decade of Innovation and Contribution to the WordPress Community. In it, they detailed their contributions to WordPress, including sponsoring WordCamps, organizing educational events like DE{CODE}, and empowering the WordPress community through content like the WordPress Roundup and Building WordPress series. They also highlighted their products like Faust.js, WPGraphQL, Headless WordPress platform,  Local,  Advanced Custom Fields (ACF), and Genesis Blocks. 

However, WP Engine did not address any of Mullenweg’s specific accusations. They concluded their post by reaffirming their dedication to WordPress, saying, “WP Engine’s commitment to WordPress and its passionate community is unwavering…WP Engine will remain at the forefront, finding new and exciting ways to drive the WordPress ecosystem’s success for years to come in partnership with this vibrant, innovative community.”

Community Reactions

Matt Mullenweg’s comments sparked intense debate within the WordPress community, leaving it shocked and divided. While some rallied behind Matt, even going so far as to cancel their WP Engine subscriptions, others were uncomfortable with his approach.

Rodolfo Melogli, founder of Business Bloomer tweeted, “I don’t think a CEO should attack people/corps based on personal opinions, no matter if right or wrong. Not good for the WordPress ecosystem tbh.”

Nate Finch, author at Level Up Tutorials suggested, “As far as I know, there is no requirement that any company that sponsors a WordCamp be involved with 5FTF, let only hit a certain threshold. If this is the case, and maybe it should be a requirement, it should be added to the sponsor agreement for WordCamps.”

“It’s not enough to provide services and products and marketing at WordCamps; if you’re making millions of dollars off WordPress I think we all can agree you really need to contribute some real hard value back into it.”, said Seth Rubenstein of Pew Research Center.

Hendrik Luehrsen, CEO of Luehrsen // Heinrich was worried, “With his recent remarks, @photomatt may have just killed the #FFTF program. It’s a tough sell to maintain public profiles on a platform that can be weaponized against someone – deserved or not.” However, Matt assured that his goal is to raise awareness of the 5FTF initiative.

“You can’t really promote the benefits of open source and then moan when companies build on that free platform and monetize it.” tweeted WPTuts. 

WPHercules published WordPress.com is not WordPress as a parody countering WP Engine is not WordPress. They point out that “plugin extensibility is sacred,” but WordPress.com restricts plugin installation in lower-priced plans. 

Andrew Palmer, in The Complex Dynamics of WordPress: A Passionate Critique, pointed out Matt’s difficulty letting go of certain issues, which at times contradicted his own WordPress philosophy. He recommended elevating other leaders within the WordPress community to help balance decision-making and ensure clearer guidance and recognition of contributions.

Kevin Geary’s WordPress’ Big “Tragedy of the Commons” Problem shares, “The problem is that Matt is putting a massively important project, and our future, in the hands of a historically failed model. Some of the smartest minds in economics have arrived at another obvious conclusion when tackling the Tragedy of the Commons problem: owned land is better cared for than public land because it benefits the private owner to protect and care for it.”

He suggests, “WordPress should be driven by a proper funding model, a proper visionary, a consistent core development team, and consistent marketing.”

James Giroux analyzed Matt’s actions as a Project Lead in WCUS: Freedom Isn’t Free. “Matt is the Project Lead, and he has a track record of calling things out in a direct, and sometimes uncomfortable way…I think it’s pretty hypocritical to say that Matt is mean or a bully while also saying things like “it’s because Matt wants Automattic to win” or “it’s because Matt doesn’t like competitors to Automattic”.

Another hot topic was the brand confusion Matt highlighted between WP Engine and WordPress. Robert DeVore pointed out that more people are confused by WordPress.org vs WordPress.com than by WordPress vs WP Engine. Daniel Schutzsmith also shared his experience with a client who faced the same confusion.

Discussions are taking place on Reddit too.

Pantheon & GoDaddy – Then & Now 

Matt’s criticism of companies is not new. One of the most memorable incidents took place the night before WordCamp US 2016 when Pantheon’s $100K sponsorship was abruptly revoked. Their promotional materials, including their booth, were stashed away in a storage room, and the sponsorship fee was later refunded in full.

Fast forward to this year’s WordCamp, and Pantheon returned as an Editor Sponsor alongside Automattic. Courtney Robertson of GoDaddy tweeted: “Wild how we are all talking about @wpengine and not the elevator doors from Pantheon sponsored. I would like to know more about standards changing.”

In 2022, Matt identified GoDaddy as a “Parasitic Company” and an “Existential Threat to WordPress’ Future”. And this year, the very same GoDaddy was a Super Admin sponsor. They sponsored Courtney Robertson for Contributor’s Day and allotted $2,000 for eight self-funded Table Lead contributors. Matt even mentioned their contributions in his Ecosystem Thinking article.

(This concludes Part 1. Stay tuned for Part 2.)

by Jyolsna at September 24, 2024 06:55 PM under wordcamp us

Do The Woo Community: The Ultimate Guide to WooCommerce Hosting: Performance, Support, and Growth with Marcel and Mike

Avalara: help developers make sure their Woo projects are tax compliance done right with Avalara’s API. Visit their extensive developer resources today.

WooCommerce: Join the official WooCommerce Marketplace and get your products in front of millions of engaged WooCommerce store owners.

Episode Transcript

Marcel:
Well, hello there. Welcome to the show. Hi, Mike, how are you?

Mike:
Hey, Marcel. I’m good. And yourself?

Marcel:
I am wonderful. It’s September, summertime is ending. Vacation was just a couple of weeks ago, so I guess I’m in the most perfect mode you can get in the year.

Mike:
Yeah, the gray weather has really shown us that summer might be over. I think we’ll get a second wave, right? Usually.

Marcel:
Yeah, it seems there’s going to be some cold weather coming. There’s something in Portugal that’s a special time of year in October, where there’s just this little extra sun coming in and warm weather that gives you a last goodbye kiss of the summer. And it seems like this year we’re going to have it a little bit earlier than October.

Well, today we’re going to go ahead and talk about WooCommerce and hosting—the critical aspects for anyone running an online store in WordPress. And unlike a regular WordPress site, WooCommerce introduces, I guess, unique challenges due to the dynamic nature of e-commerce. Things like product catalogs, customer data, and orders, all of which place more demands on your hosting environment. And the right hosting can mean the difference between a smooth shopping experience or a sluggish website.

I guess sales are directly affected by good hosting. So, I guess we could break down a little bit what our listeners need to know to ensure that WooCommerce sites perform at their best. And okay, let’s kick things off by discussing—we keep talking about performance here, Mike. I feel like this is the third or fourth episode where the word “performance” is going to come out multiple times per minute, or per episode. And I don’t want this to be maybe yet another episode about performance and how important this and this and this and that is. But having said that, the only—or not the only—but the main task of a good hosting service is effectively to provide performance to your website. So, performance is actually crucial for both the user experience, SEO, sales results, and all of that. If the store loads slowly, visitors will leave before making a purchase, search engines may rank you lower. So, it’s definitely a key factor in performance—the hosting, the server response time, and all of that. As a general rule, or if you had 30 seconds to give somebody good advice about hosting, what would you say?

Mike:
Pick something with enough resources, tools, and quality support to help you through any challenges that may arise as part of being an e-commerce store owner. And what you said is a very good list. I would add employee productivity. I have some clients who have 10 people in the backend processing orders all the time. That’s all un-cached, it requires a lot of resources and checking in the database for stuff. And then also business-to-business components—if your business needs to talk to another business, that’s fetching information, that’s going to require resources as well. I think, yeah, those three things I think are the most important. The support, quality tools, and resources. Without those, you’re going to be sacrificing some kind of quality overall, whether it’s for your users, your employees, or for your own, if you’re a stakeholder, profits and stuff like that.

Marcel:
Right, right. And when you say support tools, do you also mean the actual support service that a hosting company provides? Not only whatever you can get through a dashboard of some sort, but also talking to somebody—is that important to you?

Mike:
Yeah, definitely. I think talking to support staff, if you’ve worked with WooCommerce long enough, is generally one of those like, “Oh, how is this going to go?” moments. It could either go really well—you get someone who is enthusiastic and interested in troubleshooting together, finding solutions. And then you have other support staff who are like, “There’s nothing we can do,” or they try and point the finger somewhere else and are not trying to help you directly with the issue. And then as well as that too, it’s having the tools available to do troubleshooting, like having the command-line access with SSH, phpMyAdmin or similar tools to be able to investigate things in the database, New Relic or other things for gathering rich amounts of data. I know some service hosting companies have their own APM tool, and they have their own in-house scripts that they’ve built over time to help you scan logs and look for patterns and that kind of stuff. So I think both are really important.

Marcel:
Yeah, that’s why I asked you, because in our freelance work that we do, sometimes we need to do the job of a good host support agent and sort of translate—let the client know what the issue is or might be—and just do a little bit of the bridge that one has to do between support and our client. Because sometimes support will say, “Yeah, this is this plugin that is running slow, this is this other thing and you should contact your developer” and stuff like that. And sometimes they’re right, but sometimes it seems like they’re definitely lazy about investigating the issue. But I think there are a couple of, well, this is getting better from time to time. I guess competition is responsible for improving all these services, and there are some really good ones, like you said, that have their own tools, and they’re very quick and immediately identify what the issue is, or being proactive as well—maybe mentioning that your website is running slow, there’s a long-running task occupying a lot of CPU power, and they go ahead and inform the client about it. All of this, I think, is super important. Right?

Mike:
Yeah, you just reminded me, there are a few hosts that’ll send out emails if there’s been a 502 Bad Gateway or a 504 Timeout, or “Hey, we found malware,” or “You’re running this plugin version that has a known security vulnerability.” So, I think proactivity is one of the most attractive components of a hosting company, for sure.

Marcel:
So I guess if we would begin establishing a list of all the things that people should look out for in a hosting company—well, besides price and CPU power and memory and all of that, I guess one of the most important factors is really how support works and what support provides in terms of service when things go wrong, or when you need help and when you need advice. So yeah, before committing to any host service, just try to figure out a little bit more about how support provides, because I personally think it’s probably the most important thing you can get. I mean, if the memory is low, that support guy will tell you, “Raise the memory,” and it’ll work, right? Or if CPU is not enough, “Add more CPU power to your hosting,” or this or that. So, it’s always going to end up being that support provides the information you’re looking for when you have difficulties, and managing hosting and leveraging what is the best plan and what I need, etc., is a decision that you will make today. But probably in a month’s time, or in a year’s time when your store grows, you’re going to have to revisit all of those choices again, and you’re going to have to fine-tune the hosting service that you’ve just hired to be more efficient for your successful store that’s running. And so that’s not that much important at the beginning, I would say.

Mike:
Yeah, I agree. I think, like I said, if you have enough resources and things are performing well, things are smooth, then there’s not too much to worry about. But hopefully, as the store is growing and being successful, you then have to adapt over time, and it’s really useful to have support staff at the hosting company who can help you assess what your needs actually are resource-wise and be able to accommodate. Every store is different. I think we’ve both seen plenty of them. They’re never exactly the same. There are always a few differences.

Marcel:
And when you see those pricing tables, they usually talk about the bandwidth, the CPUs, and this and that. And some of them do mention a couple of support services or support nuances, but talking to someone before committing to hosting services is a good idea. Or maybe asking other people or the community or any social media for advice on that. But having said that, okay, so now let’s see. We’ve talked about the support. It’s important. The different places where the data centers are and the different areas of the world the hosting service covers is also important, especially for stores. If you want to have a very fast-running store and if you’re operating worldwide, it’s important for you to know where that hosting service has its data centers so that you can expand your assets or different resources to those data centers. But let’s dive into more specifically really what’s important about memory, disk speed, PHP workers, caching systems, database optimization, security, backups, and scalability at the end. So, let’s start with the memory. I will just introduce very quickly how important memory is. And Mike, maybe I’ll propose to you this format: I give you a statement about what memory is and how important it is for WooCommerce, and you either agree or disagree with me and add your points to it. Sounds good?

Mike:
Sounds good.

Marcel:
Alright. So, if we talk about memory, why is memory important? We know that WooCommerce requires more memory, more RAM than a typical WordPress

site because it’s all dynamic content. We have products, we have reviews, shopping carts, we have customer data. So, if you’re running a small store, maybe 1 or 2 gigabytes of RAM may be sufficient. But for larger stores and high-traffic websites, you would need 4, 8, 10, 12, 16, I don’t know, to run just to make sure everything runs smoothly. And without enough RAM, your server could become very overwhelmed. You could have slowing down pages and crashes, which is obviously the last thing that you want to have. What do you think about RAM? How important is RAM?

Mike:
Yeah, it’s really important for sure, especially for the database. If you don’t have enough RAM, the database queries will time out or get terminated. And that can cause all kinds of weird issues where things didn’t get synchronized or it didn’t add to a queue that needed to be processed later. And then you also have some plugins that use a lot of RAM, right? So one of the things we often have to adjust is the memory limit in PHP so that certain tasks can execute. So, it’s one of those things you can’t oversell. On hosting, if you start to allocate more RAM than what’s physically available, it won’t work. And if you try and use virtual memory—if you remember back in the day, we would have a RAM disk and stuff like that—RAM is always going to be faster than hard drives. Even if—I don’t think SSDs will ever get—eventually, maybe SSDs will just be RAM chips. That would be cool. But I have a feeling that’s quite expensive.

Marcel:
And RAM specifically has to have the ability to quickly read, write, read, write in a way and at a speed that SSDs are not designed to do. If we would have a world where SSDs and RAM would be the same chip, I guess the only company that could be able to do that would be Apple. But jokes aside, it’s sort of like every one of these two components has its own job to do in the environment. You talked about the database and RAM’s importance for the database, but there’s also the PHP side of it. So, when you’re working with RAM, RAM is basically shared between two main things: the database and the PHP. So, PHP, when it runs, it needs memory to do its calculations, and when it’s done, it just serves the results to the web server, which then displays it to the client. So, having PHP tasks that also take a lot of memory is also important in this case. But that is fairly easy to measure and to know. And if you have a PHP task that takes a lot of memory, then that’s usually a bad sign. So, increasing memory to cover up PHP memory leaks is not a good thing to do, but it’s also an important part of the process.

Mike:
I agree.

Marcel:
Then we have disk speed. The disk is another critical factor, particularly when you’re handling large amounts of data. And we know that with WooCommerce we can get that. But basically, for WooCommerce, I guess SSDs—the solid-state drives—are almost always a better choice than the traditional HDDs, and SSDs are mainly faster to read and write data, which is especially important for large WooCommerce stores with, I would say, thousands of products or images or orders or customers. So having SSDs can significantly improve site load times, which obviously are crucial for keeping customers engaged. We are old enough to have been around to witness the transition from HDDs to SSDs in the hosting world. Was that the same for you? Thank God we already have SSDs for hosting. And did that, in your experience, provide a huge performance impact?

Mike:
Yeah, I mean nowadays you wouldn’t ever choose a host that didn’t use solid-state drives. It’s directly related to performance and the database. You want the database stored on SSD, not a hard drive like the old school ones. I’m pretty sure there are instances where I’ve witnessed this happen, usually from very low-cost hosting on a machine that was older than it should have been for being allowed to be in the web hosting space. And then you move them somewhere that uses modern technology, and the client is like, “Whoa, my time to first byte used to be 15 seconds, and now it’s a second.” And they’re like, “I cannot believe that that makes that big of a difference.” So if you are lucky enough to find a client’s site that’s still using an old-school hard drive, and you move them to SSD, I’m sure you’ll see a significant boost.

Marcel:
I guess nowadays, HDDs in a hosting environment are used for more static data or for large data sets that you don’t provide specifically in a dynamic way to a web server. They would be more considered for saving data files that are just accessed sporadically. And so you do see some hosting companies offering this large amount of hosting space for this specific use, and they are usually using… there is still this discussion around which one of these two different types of drives lasts longer, because SSDs are more prone to fail, I guess, than HDDs. But then again, we have bad experiences with HDDs as well. If you mess with them too much or if… well, when they’re in the hosting environment, nobody will touch them, but they’re also very sensitive to movement and heat and other factors. I do remember the time when we had this transition from HDDs to SSDs on our personal computers, especially for the people who had Apple computers in early around 2012, 2011, 2012, when there was a transition between HDDs and SSDs. And people were buying these external SSDs and putting them into the USB connection and just booting off of external SSDs.

And some people also tweaked their computers and opened them up and installed the SSDs inside and replaced the HDD. And we got huge improvements in speed and suddenly the operating system was loading, we would say, it seemed like it was running off the memory only, there would be no hard drive. And I guess we can say the same for hosting. So files being read very quickly is a lot more efficient for hosting.

Mike:
Yeah, definitely. I do remember there’s one hosting company that they had… I brought a client that had so many images, it was like an Android news website, so they had so many images and they needed terabytes and terabytes. It was insane how much this was. And we ended up, because the SSDs were going to be so expensive, we ended up using hard drives in a RAID or something like that. And because it was just for the images—obviously you want to read the images as quickly as possible as well, similar to the database—but it was the only way that they could have sustainable long-term growth because of how much the image library grew every day. They needed something that made sense for the next 10 years at least. So yeah, I would just add to that. It’s an important little piece too. They still have their place, right? My Synology NAS, you have one as well, right? I chose Western Digital Red hard drives for the enterprise drives.

Marcel:
Exactly.

Mike:
They’re designed to run 24/7 and also last the longest. I think SSDs have a limited number of writes, right? Isn’t that…?

Marcel:
Yeah. There are some calculations around how many times they can read and write, which defines their lifetime cycle, yeah.

Mike:
Whereas hard drives are not unlimited, but it’s like, you have other problems at that point. You probably won’t be alive anymore.

Marcel:
Exactly. Alright, that’s the disk topic. Let’s talk on another topic, and let’s talk about PHP workers, which not every hosting company discloses how many PHP workers one can get when we do a hosting plan with them, but basically—and I think they’re often overlooked—but they are a very essential aspect of hosting for WooCommerce specifically. So for everyone listening who doesn’t know what PHP workers are, in simple terms, they handle the simultaneous processes that occur on your website. So let’s say, for example, multiple users adding products to their carts or checking out at the same time. If you don’t have enough PHP workers, your site will slow down during busy times because there aren’t enough resources to process all the requests, and people are going to wait for their requests to process. So from the time that you ask for a specific URL and by the time you get the result delivered, that’s the time that the hosting will spend doing some sort of work, calculating some result for you to show on the website.

And PHP workers are essentially the processes that take that request, process it, run the PHP script, and deliver the page that they’re requesting. So those 200 milliseconds, 400 milliseconds, they’re going to be busy doing something. So if you have 10 people coming in, there’s going to be eventually a queue, and people are going to be waiting for their turn to get the process running, to get the PHP worker running. So if you think of it like a restaurant, if there aren’t enough waiters, service gets slow. It’s kind of the same thing. PHP workers are expensive for hosting companies, and they’re also expensive for the resources that you have on your hosting side, but they’re an important part of it. What’s your take on PHP workers?

Mike:
Yeah, I wanted to add to the waiter example that service will slow down, but you also get people leaving,

which would be like a 502 Bad Gateway, where it’s like there’s not enough service, I’m leaving with a bad review.

Marcel:
Yeah, exactly.

Mike:
Which is what happens if a visitor comes to your site to try and buy something, and they just see an error message, right? 502 Bad Gateway. It’s like, oh, then they just leave. Some people will be patient and try to reload, but…

Marcel:
Right.

Mike:
Attention is harder and harder to maintain these days.

Marcel:
Yeah. Why do you think most hosting companies don’t disclose how many PHP workers they have?

Mike:
I think it’s a tricky thing to make equal because it’s very related to CPU and also the way that your site functions. So, I think it can be misleading to, for example, say you have 32 virtual CPUs and 500 PHP workers, though CPU cores and PHP workers, in my experience, are not created equally across hosting spaces. CPU is something that you can oversell and split. So, if I have 32 physical CPU cores, I can easily split that into 20 or 30 virtual machines that have four or eight CPUs, and it will just split and make them weaker between them. Whereas the kind of hosting I really like is when it’s a physical dedicated machine, and you’re not using virtual CPUs at all. And the PHP workers from that kind of machine tend to be way more powerful in executing scripts compared to ones on oversold VPS-style hosting.

Marcel:
And PHP workers, because they work simultaneously on a specific task, they are consuming CPU resources, and it’s sort of like, you would think, “Okay, I have four cores, so I can have at least four PHP workers, but I could also have eight PHP workers. We could split each core between two PHP workers.” But the more PHP workers you add, the slower they themselves will run because they’re concurrently running and doing their task. And so that will eventually also slow down, and you will serve more people at the same time, but everybody will get a slower response at the end of the day. So it’s not a linear thing. It doesn’t seem like the more PHP workers you have, the faster it will go. There are certain limits. So that’s why I think also hosting companies don’t disclose their PHP workers, because it’s a game of being the best performer but also not just wasting a lot of resources on PHP workers that aren’t clearly needed. And also there’s some sort of energy consumption concern behind this as well. You don’t just want to have a bunch of processes running all the time, so it’s kind of like a balancing game. But some hosting companies do provide those numbers, and they market offering according to PHP workers. And more isn’t always better.

Mike:
Yeah, very true. And it also depends a lot on the nature of the site and what it’s doing. I remember a client who did a lot of un-cached activity, so the idea was you would land on a website, and then they had a single sign-on system that you could connect your login to, and it would make an API request to a third party to authenticate, and then it would let you go shopping for some exclusive deals or whatever. We were doing load testing to get ready for the holiday season. It was for a very large company, and we found that they were running out of PHP worker threads. And even though we had a dedicated server with a huge amount of resources, and the CPU was basically flat, and the RAM wasn’t going that high, PHP workers were running out, and we were getting errors.

I had a long discussion with the hosting company to say, “Look, yes, we’re using that lane, right? Yeah, we’re sort of keeping a waiter at the table, but it’s because we’re waiting for information from—we’re taking an order from a friend who’s running late, and we’re just waiting for the feedback from them to give to the waiter.” So, it’s not like the waiter is stressed or carrying a lot of plates necessarily. Sometimes the PHP worker is not actively processing a lot of information; sometimes they’re idle and waiting for information to come back. And I think that’s an important part: if the PHP worker is not actively processing and you picture the waiter running around constantly, sometimes they’re not doing much. And it’s okay to allocate more PHP worker threads in situations like that, if you’re monitoring the system and you can see that it’s not stressed. If CPU and RAM are showing very low levels of usage, then you can ramp up the PHP workers.

But in the opposite way, if you have… I remember one of the first VPSs I ever provisioned and set up. It had one CPU core and 512 megabytes of RAM, and I was determined to run things on as few resources as possible and just rely on caching. It was a very cache-heavy website, it wasn’t a WooCommerce store, and I just kept increasing the PHP worker threads available, the MPM max children, and you can put it as high as you want. But then when I did load testing for un-cached responses, the server froze completely. And when I SSH’d in, the load number was like 200 and something, which it should be as close to 1 or 1 times the number of CPU cores that you have. You could just imagine these poor waiters, there was a lot of very, very tiny waiters carrying a lot of stuff, and none of them knew where they were going anymore. They were all confused, and the queue just got so backed up.

Marcel:
I would imagine if this podcast included video, we would put up a graphic of tiny waiters in multiple restaurants just running around and being unorganized, and it would be very interesting to visualize that. I completely forgot. So, we’ve been talking about the importance of RAM and disk space and PHP workers, but not naming numbers. So I will try to give people a little bit of some ideas of what the numbers are for each of these individual components. Let’s call them, and I’ll name some numbers, and you correct me if I’m good with my numbers or not. But this is basically the same thing with engines in a car. If you have BMW, for example, they’re famous for having these big engines, they have 3 liters, 4-liter engines, and you just throw a bunch of gasoline in it. The explosion is huge. They have thick engine walls that can handle all the explosion. Then you have superpower, you have a lot of power because you really just have thick walls and a lot of gasoline exploding inside those cylinders. So that’s one way to do it. Let’s call it the easy way. It’s not an easy way to have a very big controlled explosion inside a cylinder, but let’s call it easy. The more tricky way is to have a 1-liter engine or a 1.5-liter engine and have an explosion that has almost the same kind of force or power that has this bigger explosion, but because you’ve adapted the shape of the cylinder, but because you made a special mixture between air and combustion and all of that, because you took a little bit more time into figuring out how to almost get the same kind of force with a lot less energy.

I guess that’s a little bit the comparison that we’re making here. You can obviously have 16 GB of RAM and 16 CPUs and a lot of disk space and everything will run smoothly, yes. But is that efficient? Do you need all of that? Are you using your BMW to drive 5 kilometers to take your kid to school, or do you drive 300 kilometers every day and really need that strong engine to work in your favor? So, having that in mind, and taking into consideration that everything is running smoothly—you don’t have custom code that is just occupying a lot of resources—I would say less than 50 concurrent users, 2 gigabytes of RAM is enough. If you have 100 to 200 concurrent users, I think 4 gigabytes. And more than 200 concurrent users, it’d be 8+ to 16 gigabytes. I think these are good numbers. Would you agree with these numbers?

Mike:
I think those are probably safe starting points, assuming the database is not huge. That would be my one caveat. If you have a 20-gigabyte database, then you’re going to want to start with at least 32 GB of RAM, I’d say, or more. But yeah, and then load tests—now people are getting prepared for the holiday season, Black Friday is coming up, and I would load test the most resource-hungry scenarios you can think of in terms of the marketing stuff you’re doing, whether it’s newsletters or paid traffic on Meta or Google or whatever it is. And we’re doing something right now with a client, and once they get to 200 users, things are not going well. So, we’re identifying the bottlenecks with New Relic and coming up with strategies of how to mitigate them.

Marcel:
And the strategy is definitely not just, “Okay, let’s just double the RAM and everything will be good,” right? Because that’s also a cost that people have to take into consideration. You don’t have infinite money to pay for these resources and just be happy with it, right?

Mike:
Yeah, I think during the holiday season is when people tend to be more open to the idea of just throwing resources at the problem. It’s certainly the easiest solution. Even if it costs more, usually it’s going to be worth it. If your site is crashing, you’re not making as much money, for sure. But yeah

, in general, I don’t like the idea of, “Oh, just keep throwing resources at it until it works properly.” I think you and I would go and identify what is taking so long. Is the code optimized correctly? Is there a way to rewrite it so it’s more efficient in processing data and using less RAM and stuff like that?

Marcel:
And it’s a lot more intelligent and rewarding if you figure out what’s consuming that much resource, and then suddenly, with the same kind of resources, the website’s speed doubles. There’s something special about tuning that, right? Obviously, if you’re time-constrained, and the holiday season is coming, then okay, let’s add some more RAM for the next three months, and then we’ll figure it out later, fine. But the figuring out later part needs to happen sometime.

Mike:
Yeah, websites are just like a house or an F1 car. You can’t just keep adding stuff to it or turning something on and forgetting you left it on. If you have a basement and you turn the water on to do some sort of task, and then you got distracted and left it on, you’re adding more and more resources to accommodate a flood that you don’t need for any business purposes. I think that’s really important because a lot of the times when I do investigations, the thing that’s gobbling up CPU or RAM or disk space is a feature that they tested once upon a time and no longer use. The person at the company who suggested it is no longer with the company or whatever. So, I think this sort of website hygiene maintenance stuff is just so, so important. Also, hosting companies can help you with that, right? Good hosting companies will tell you if you’re about to run out of hosting, sorry, disk space, because without disk space, nothing will work. You won’t be able to do database operations, you won’t be able to log into your WordPress site.

Marcel:
You might not even be able to SSH into your hosting and do anything in there, yeah.

Mike:
Yeah, you can usually SSH in, but running commands will just give you weird output.

Marcel:
And the same thing with RAM, right? If you run out of RAM and you need just a little extra to run some command to just basically kill something or fix something, it’s the same thing.

Mike:
Yeah. You can SSH in, but running commands will just give you weird output. It’s a funny experience.

Marcel:
And as far as CPUs are concerned, for 50 concurrent users, I’d say 2 CPUs, for 100 to 200 concurrent users, 4 CPUs, and for more than 200 concurrent users, you’ll need 8 CPUs. I would say that’s a round number or more depending on the situation. Would you agree with those numbers as well?

Mike:
In general, I’d say they’re probably good starting points. It’s going to depend again on how many of those people are window shopping versus adding items to their cart. I think if you have caching set up properly and you don’t have a huge product catalog where every user is visiting different products, you can have tons—you could have hundreds or even thousands of window shoppers. But as soon as people start adding items to their cart, then the majority of caches are bypassed. Depending on how your site is tuned, we’ve seen this plenty of times where code is running unnecessarily for uncached visitors. WordPress runs a lot of functions, plugins execute a lot of code that doesn’t need to be, and that can slow things down.

Marcel:
And as far as PHP workers are concerned, I would say on the same scale—50 concurrent users, 2 PHP workers; 100 to 200 concurrent users, 4 PHP workers; and more than 200, 10 PHP workers.

Mike:
Yeah, you could start with those and see what happens.

Marcel:
Let’s talk about the big elephant in the room—caching systems. Caching is definitely one of the most effective ways to improve the performance of an eCommerce store. There are different types of caching. There’s page caching, which saves a static version of your website. But we all know that WooCommerce stores can only have so many static versions of pages. Not all pages can be static like on a regular site, and those will be delivered without making your server do all the work from scratch. Right? Then you have object caching, you have Redis cache, you have… those would help you with database queries. You have browser caching, so the client side can also do some caching to save the resources locally on the user’s devices. You have OPCache or code caching, and you have a bunch of different caching systems to reduce the load on the server.

I was thinking about asking you this question—how important is caching to you? But it seems like a silly question. I would rather ask you about the experience that you’ve been having with your most recent clients. Taking into consideration that hosting can provide some caching solutions, and based on the hosting services you’ve worked with, do you think there’s a hosting service that really nails the caching system for WooCommerce?

Mike:
I would say it’s really difficult to do it perfectly because all stores are different. So, the best you can really expect from a hosting company is that they provide the tools and configuration possibilities necessary to set up caching correctly for your site. Most hosts do a decent job of setting up things where the cart and checkout are excluded, and they make sure the right cookies are excluded, like the ones for items in the cart. Edge caching is becoming more popular now, thanks to Cloudflare Enterprise integration, which is becoming easier. You get to take advantage of that, which reduces time-to-first-byte across different locations.

So, no hosting company gets it perfectly right, but a lot of them offer a good starting point, a springboard, so you can configure caching yourself. I saw one hosting company recently that helped their client cache logged-in users for a Woo store, which I thought was really clever. Caching logged-in users sounds like dark magic, but their business model required users to register an account and log in to see the product catalog. Everything else was uncached, but once they logged in, they had a custom system where a cookie allowed for logged-in pages to be cached. It was really clever.

That’s a special use case, and I wouldn’t expect every hosting company to offer that, but it was a great example of a very customized solution that worked well. Usually, though, it’s a balance of having good tools and knowing how to use them.

Marcel:
The thing that’s special about WooCommerce is that some of the pages cannot be cached in the same way that other pages can. So, the least a hosting company needs to be aware of when offering WooCommerce-specialized hosting services is that there are certain pages within the WooCommerce store environment that need to be treated differently. You might also have custom pages where you want to insert exclusions for certain types of caching. Caching needs to be adapted to the nature of the store, not only for WooCommerce generally, but also for your own unique needs. I think that’s an important part of choosing a hosting provider. If you know they have the capability to adapt to your needs, that’s crucial.

And yeah, hosting services are getting better at accommodating those requests. If you have the knowledge, you can still go to AWS or Google Cloud and configure everything yourself, but most store owners don’t have the time or expertise for that. Thankfully, many of these caching techniques are now available through hosting companies, and they take care of a lot under the hood. So, it’s definitely something to look for when choosing a host.

Let’s talk very quickly about database optimization. This is one that site owners often overlook. Since WooCommerce stores store a lot of data, and we talked about this in our previous episode, everything from customer and order history… your database can get bloated, and that can slow things down. Regularly optimizing the database by removing transients or optimizing tables can make a big difference in performance. There are plugins that can help with that, and some hosting providers might also offer database optimization services. In 30 seconds, because I want to get to the end of the topics I have, Mike, how important is database optimization?

Mike:
I think it’s similar to disk space and other stuff. If you don’t have an optimized database, everything is slower. Especially with WooCommerce, where the post table holds so much data, things can get really bloated. If your database is cluttered with unnecessary data, queries take longer, and that can impact performance. So yeah, it’s critical. Optimizing the database is not an optional thing. It’s like a house—if things are disorganized, or if there are too many of the same item in one drawer, it’s hard to find what you need. The same applies to your database.

Marcel:
And also, I would say if people want to know more about database and performance optimization, they should check out our previous episode here on Do the Woo.

Now let’s talk security and backups. Security is vital, obviously, since you’re handling customer data and payments. So, there are a couple of measures that hosting providers take to provide more security. SSL is mandatory—there’s not even a need to discuss that. But backups are also very important, and backups can be tricky. If you have a store that’s running 24/7 and you have a lot of orders coming in, if something happens and you need to restore a database, you’re going to lose some data unless you have a smart backup system. Some automated backup systems are more clever than others, but that’s definitely something to keep in mind. Your hosting provider will help a lot if they take care of that. Would you agree, Mike?

Mike:
Yes, absolutely. Backups are crucial. Hosting companies need to have quick, reliable backups, and the ability to restore them quickly. And backups should not take hours and hours to complete unless your database is absolutely massive. But without a proper backup and restore plan in place, you’re in trouble if something goes wrong. Hourly backups, for example, can be a lifesaver, especially for stores that have a lot of transactions.

Also, good hosting companies will take a snapshot before you restore a backup. In case you made a mistake or restored the wrong version, you can roll it back. It’s important to have that safety net.

Marcel:
Right. And snapshots are very useful. Having backups done quickly is important, but knowing how to restore them is just as important. You need to be able to get your site back up quickly if something goes wrong, and that’s where good hosting support comes in.

Mike:
I would also say verifying that your backups are actually valid and work should be part of every store’s maintenance. Test your backups periodically to make sure they restore properly. You don’t want to find out when something goes wrong that your backups were incomplete or corrupted.

Marcel:
Exactly. It’s like a fire drill. You need to run it once or twice a year to make sure everything works as expected.

Lastly, let’s talk about scalability. When your WooCommerce store grows, you’ll need to scale it. You might start with shared hosting, which we haven’t really mentioned in this episode, but as your traffic increases, you might need to upgrade to a VPS or even a dedicated server for larger businesses. Usually, companies use AWS or Google Cloud because they allow you to scale resources up and down easily. It’s important to choose a hosting provider that can grow with your store, so you’re not stuck with limits that could hurt your business.

How important do you think it is when people start out to choose a hosting company that can scale? Or do you think there are hosts that are

better suited for different stages of a business’s growth?

Mike:
That’s a good question. I think it’s always a good idea to bet on your own success. You should anticipate growth unless you’re sure that your business model is limited and won’t require much scaling. It’s important to choose a hosting company that can grow with you. I’m sure you’ve experienced this too—migrating a WooCommerce store from one hosting platform to another is a nerve-wracking experience for clients. Many people have had bad experiences with migrations, and it can be traumatic if something goes wrong. So, it’s better to start with a hosting company that offers both shared hosting and scalable options like VPS and dedicated servers. You want to be able to grow without needing to change hosts.

Marcel:
Exactly. And we fall back to what we talked about earlier—support is key. When you hit a threshold and need to upgrade, you want the hosting company to handle that transition smoothly. If you have a hosting provider that says, “Unfortunately, now you need to do this and that,” and they just put the whole thing back on the client, that’s not a good service. When scaling, the hosting company should be a partner in that process.

Ideally, they should say, “Hey, you’re growing. Shared hosting is not an option anymore. Don’t worry. Let’s schedule a migration during your least busy hours, and by tomorrow morning when you wake up, you’ll have a new hosting service that can accommodate your growth.” That’s the kind of hosting service you want, right?

Mike:
Yeah, definitely. When we’re offering advice to clients, we usually want them to be prepared for the next 10 to 20 years with whatever challenges or growth opportunities they may face. We have a handful of hosting providers we know can accommodate different types of stores and business models, so they will scale as needed.

It’s hard to find hosts that can do horizontal scaling—multiple servers. Usually, once you’ve added a domain name that maps to a specific server, you can’t add another. Vertical scaling is more common; they’re happy to let you resize your server and make it bigger. But some clients want parallel processing or geo-redundancy. I have one client that has servers in Chicago and New Jersey, with a primary and secondary database setup. If Chicago goes down, New Jersey takes over. Not every host supports that kind of infrastructure, though.

Marcel:
There are two other things I want to add before we wrap up: bandwidth and monitoring tools.

Bandwidth is something people need to keep an eye on, even though most hosting providers offer scalable or unlimited bandwidth. But you should calculate your bandwidth needs by taking the average page size and multiplying it by the number of visitors and pages viewed. For example, if your average page size is 2MB, and you get 5,000 visitors per month, each viewing five pages on average, you’re looking at 50GB of bandwidth a month.

I haven’t had a client run into bandwidth limits recently, but it’s still something to watch out for. Have you seen any issues with bandwidth?

Mike:
No, not in recent years. Most hosting providers have moved toward offering unlimited bandwidth, especially since many use Cloudflare to handle some of the load. I see more issues with outgoing emails being rate-limited, though. Some hosts will restrict the number of outgoing emails, especially if they think there’s suspicious activity, like a flood of order confirmation emails during a sale. It’s not great if you’re running a big sale and your emails are getting blocked, because customers start to wonder where their order confirmation is. That leads to support tickets and frustration.

Marcel:
Right, good point. And finally, monitoring. As a developer, I really appreciate hosting companies that provide good monitoring tools. I’m talking about dashboards where you can see CPU usage, memory usage, disk space, PHP workers, and even bandwidth. Some hosts offer integration with tools like New Relic, or they have their own monitoring tools. It’s important to be able to check on your website’s health regularly.

The first thing a developer or freelancer will ask a client is, “Do you have a staging website?” If your hosting provider allows you to spin up low-end environments like staging or performance environments, it’s incredibly helpful. You don’t need production-level power for staging, but you do need an environment to test things. And most hosting providers do offer them, but not all of them are free. So, having that capability without extra charges is key.

What do you think about that?

Mike:
I completely agree. As developers, we’re always asking for a staging environment. It’s the first thing we ask before making any significant changes. Having a staging site on the same host is crucial for testing updates, new features, or troubleshooting problems without affecting the live site. And yes, it shouldn’t be expensive.

Monitoring is also essential. The good hosting companies will provide a robust dashboard with real-time stats. And if you’re using New Relic or similar tools, you can get deep insights into performance, slow queries, and which plugins are hogging resources. That can save you a lot of headaches in the long run.

Marcel:
Exactly. And I would say the most successful clients I’ve worked with are the ones who focus less on dashboards and numbers and more on working with the right people. Having a good relationship with a hosting company that offers solid support is often more important than staring at charts all day. When something goes wrong, it’s the support that matters most.

Mike:
Yeah, and that’s something we’ve noticed too. If the client has a skilled development team, then having good monitoring tools is great, because they can dig into the details themselves. But if you’re a store owner who doesn’t have that technical expertise, then having access to a knowledgeable and responsive support team is far more valuable.

It’s like giving someone a spaceship—if they don’t know how to fly it, it’s useless. So having both—good tools and good support—covers all your bases. But if you had to choose between them, I’d recommend going with quality support.

Marcel:
Exactly. The store owners I’ve worked with who have been the most successful aren’t necessarily worried about the fancy dashboards—they care about the people they work with. And having a reliable hosting partner with good support is more important than anything.

Alright, everyone, that’s it for today. Thank you so much for listening and tuning in. This was, once again, Mike and I talking about WooCommerce and performance. We keep talking about performance—it’s important, I know! We’re probably getting a bit repetitive on that subject, but we have some future episodes ahead with different guests. We’re going to talk a lot more about development, too. So yeah, tune in for those.

Mike, I’ll talk to you in the next one!

Mike:
Sounds good, man. Thanks!

In this episode of Woo DevChat, Marcel and Mike dive deep into the critical aspects of hosting for WooCommerce stores.

They explore how hosting directly impacts your store’s performance, sales, and user experience, and discuss essential factors like RAM, CPU power, PHP workers, caching systems, and database optimization.

The conversation highlights the importance of choosing the right hosting provider that can scale with your store’s growth, while providing top-notch support. Whether you’re just starting out or building a high-traffic WooCommerce site, this episode will equip you with valuable insights to ensure your WooCommerce store runs smoothly and efficiently.

Takeaways

Hosting Directly Impacts Performance and Sales: A slow-loading WooCommerce store can lead to lost sales and lower search engine rankings. Choosing a hosting provider with sufficient resources, speed, and reliability is crucial for success.

The Importance of Support: Quality support is just as essential as having the right hosting resources. A knowledgeable support team that can proactively troubleshoot and resolve issues can be a game-changer, especially for non-technical store owners.

RAM, CPU, and PHP Workers: WooCommerce sites require more RAM and CPU power than regular WordPress sites due to the dynamic nature of e-commerce. PHP workers are crucial for processing simultaneous tasks, and understanding the right balance of resources can prevent slowdowns during peak times.

Caching Systems: Implementing effective caching strategies, such as page caching, object caching, and browser caching, is one of the most impactful ways to improve performance. However, WooCommerce stores require customized caching due to the dynamic content of e-commerce sites.

Database Optimization: Regularly optimizing your database by clearing transients and optimizing tables can significantly boost site performance, especially as your store grows and accumulates more data.

Scalability is Key: As your WooCommerce store grows, having a hosting provider that can easily scale from shared hosting to VPS or dedicated servers is important. Scaling smoothly without disruption requires the right provider and strong support.

Backups and Security: Frequent backups and a robust security setup are non-negotiable for WooCommerce stores. Automated, smart backup systems and proactive monitoring can save you from major losses in the event of a failure or security breach.

Monitoring and Staging Environments: Good hosting providers offer monitoring dashboards and the ability to create staging environments. These tools help developers test changes without affecting live sites and provide insights into performance, memory usage, and potential bottlenecks.

Links

by BobWP at September 24, 2024 08:55 AM under Performance optimization

September 22, 2024

Matt: On WP Engine

I wrote a bit more on Lee Wittlinger / Silver Lake and WP Engine over on WordPress.org: WP Engine is not WordPress.

by Matt at September 22, 2024 12:12 AM under Asides

September 21, 2024

WordPress.org blog: WP Engine is not WordPress

It has to be said and repeated: WP Engine is not WordPress. My own mother was confused and thought WP Engine was an official thing. Their branding, marketing, advertising, and entire promise to customers is that they’re giving you WordPress, but they’re not. And they’re profiting off of the confusion. WP Engine needs a trademark license to continue their business.

I spoke yesterday at WordCamp about how Lee Wittlinger at Silver Lake, a private equity firm with $102B assets under management, can hollow out an open source community. (To summarize, they do about half a billion in revenue on top of WordPress and contribute back 40 hours a week, Automattic is a similar size and contributes back 3,915 hours a week.) Today, I would like to offer a specific, technical example of how they break the trust and sanctity of our software’s promise to users to save themselves money so they can extract more profits from you.

WordPress is a content management system, and the content is sacred. Every change you make to every page, every post, is tracked in a revision system, just like the Wikipedia. This means if you make a mistake, you can always undo it. It also means if you’re trying to figure out why something is on a page, you can see precisely the history and edits that led to it. These revisions are stored in our database.

This is very important, it’s at the core of the user promise of protecting your data, and it’s why WordPress is architected and designed to never lose anything.

WP Engine turns this off. They disable revisions because it costs them more money to store the history of the changes in the database, and they don’t want to spend that to protect your content. It strikes to the very heart of what WordPress does, and they shatter it, the integrity of your content. If you make a mistake, you have no way to get your content back, breaking the core promise of what WordPress does, which is manage and protect your content.

Here is a screenshot of their support page saying they disable this across their 1.5 million WordPress installs.

They say it’s slowing down your site, but what they mean is they want to avoid paying to store that data. We tested revisions on all of the recommended hosts on WordPress.org, and none disabled revisions by default. Why is WP Engine the only one that does? They are strip-mining the WordPress ecosystem, giving our users a crappier experience so they can make more money.

What WP Engine gives you is not WordPress, it’s something that they’ve chopped up, hacked, butchered to look like WordPress, but actually they’re giving you a cheap knock-off and charging you more for it.

This is one of the many reasons they are a cancer to WordPress, and it’s important to remember that unchecked, cancer will spread. WP Engine is setting a poor standard that others may look at and think is ok to replicate. We must set a higher standard to ensure WordPress is here for the next 100 years.

If you are a customer of “WordPress Engine,” you should contact their support immediately to at least get the 3 revisions they allow turned on so you don’t accidentally lose something important. Ideally, they should go to unlimited. Remember that you, the customer, hold the power; they are nothing without the money you give them. And as you vote with your dollars, consider literally any other WordPress host as WP Engine is the only one we’ve found that completely disables revisions by default.

by Matt Mullenweg at September 21, 2024 11:57 PM under WordCamp

WordPress.org blog: PDX + WCUS 2024: A Recap

I love Oregon sculpture at The Oregon Convention Center in Portland, Oregon USA

WordCamp US (WCUS), North America’s largest WordPress event, hosted over 1,500 attendees from around the world at the Oregon Convention Center in Portland, from September 17 to 20.

Over four days, WordPress professionals and enthusiasts came together to explore the latest advancements and use cases, collaborate on open source projects, and strengthen community connections.

A dedicated team of more than 40 volunteers, led by Aaron D. Campbell, Julia Golomb, Katie Richards, and Sandy Edwards, made the event possible.

Building WordPress

Contributor Day brought together over 400 contributors across 25 teams to support the WordPress project. As with any Contributor Day, participants learned and collaborated while tackling key projects, including triaging issues, exploring performance improvements, advancing the Twenty Twenty-Five theme, and preparing for the upcoming WordPress 6.7 release.

Contributor Day 2024 at WordCamp USWordPress contributors discussing all things design at WCUS 2024’s Contributor Day.

Celebrating WordPress

At WCUS 2024, the inaugural Showcase Day highlighted how enterprises like Disney Experiences, The New York Post, CNN, Vox Media, and Amnesty International are leveraging WordPress across a variety of industries. With 19 sessions, attendees gained diverse insights into WordPress’s wide-ranging capabilities and features.

Disney at WCUS 2024Showcase day presentation by Alexandra Guffey and Katrina Yates of Disney on Gutenberg’s use in a complex ecosystem of sites.

Sustaining WordPress

Joseph Jacks at WCUS 2024Keynote presenter Joseph Jacks shares thoughts on the future of OSS.

Joseph “JJ” Jacks, founder of OSS Capital, kicked off the first day of programming with a keynote about how open source will dominate the next wave of software. In looking at emerging trends in tech, he expressed how closed core, or closed source, software is hitting a plateau. Commercial open source companies are able to disrupt and forge the path for a shift in the space. 

Sharing his optimism for the future, JJ highlighted emerging projects OSS Capital is excited about and emphasized that the most successful open source companies thrive by generating more value than they capture.

Learn WordPress

The second half of the conference featured more than 20 sessions and workshops across three tracks. Topics ranged from leveraging AI in WordPress to getting the most out of wp-admin.

Thursday’s dedicated networking session brought attendees to the sponsor hall to explore and connect with the vast ecosystem of hosts, plugins, agencies, and service providers. The WordCamp US Lounge, located within the exhibit hall, held focused discussions on hosting, neurodiversity, inclusivity, and content marketing.

Friday began with a fireside chat between TIME’s CTO Burhan Hamid and WordPress VIP’s CMO Tim Hossain. The duo discussed how TIME’s implementation of reusable components allowed them to scale and support major traffic-generating topics such as Taylor Swift’s Person of the Year, House of the Dragon, and political events.

Troubador Typewriter at the Code is Poetry Lounge, WCUS 2024WordCamp attendees stopped by the Code is Poetry lounge to try their hands at the vintage Smith Corona and have a poem written by the Typewriter Troubadour.
Campfire Lounge at WCUS 2024Attendees take a break in the center of the exhibit hall at the “campfire” where various discussions were held throughout the event.

Q&A with Cofounder Mullenweg

In a dynamic keynote, WordPress Cofounder Matt Mullenweg delivered one of his “spiciest” WordCamp presentations, combining insights on WordPress’s open source future with a creative twist. He opened by reading his recent post that explores open source philosophy, touching on themes of freedom, collaboration, and the ongoing influence of open source projects like WordPress. Mullenweg also critiqued companies for misleadingly labeling proprietary models as open source, stressing the importance of true open source licenses for the future of software freedom.

Matt further emphasized WordPress’s ecosystem-driven development and highlighted the Five for the Future initiative, an effort to avoid the tragedy of the commons and ensure that WordPress thrives for everyone. His speech addressed community concerns about companies profiting off WordPress without giving back and urged attendees to support companies that contribute to the platform’s growth.

Before diving into the Q&A segment of the presentation, Matt expressed the importance of recognizing:

“What we create together is bigger than any one person.”

Matt Mullenweg speaking at WCUS 2024 in Portland, Oregon USAWordPress Cofounder Matt Mullenweg on the main stage at WCUS 2024.
Matt Mullengweg and Brian Richards taking the stage at WCUS 2024.Matt Mullenweg and Brian Richards on stage at WCUS 2024.

Save the Dates

In his closing remarks, emcee Brian Richards expressed gratitude for the fantastic work the event organizers and volunteers contributed to produce WCUS 2024.

Brian reminded attendees to save the date for WordCamp US 2025, which will once again take place in Portland, Oregon, from August 26 to 29, 2025. 

WCUS 2024 Attendees gather for a group photo.Attendees gather at WCUS in Portland, Oregon.

No WordCamp is complete without an after-party, with this year’s taking place at the Oregon Museum of Science and Industry (OMSI). Attendees concluded a week of WordPress with refreshments while visiting the exhibits—including a submarine and planetarium—and posing in the photo booth.

Stay connected

WordPress events enable technologists, open source enthusiasts, and community members around the globe to meet, share ideas, and collaborate to drive WordPress and the open web forward.

Mark your calendars for State of the Word (Tokyo) on December 16, 2024, 2025’s WordCamp Asia in Manila, WordCamp Europe in Basel, Switzerland, and WordCamp US in Portland, Oregon!


This post is a collaboration between the contributors who produce content for wordpress.org/news and the WordCamp US Communications Team.

Props to the following contributors for the work reviewing/contributing to this post: @rmartinezduque, @juliarosia, @brettface, @eidolonnight, and @cbringmann. Thank you to the Photos Team for supplying images for this post and the official WordPress social media accounts throughout the event: @gwallace87, @m_butcher, @correliebre, and @zstepek.

by Dan Soschin at September 21, 2024 07:10 AM under WordCamp

Gutenberg Times: Four #WCUS Talks, Multi-block plugin, Tabor’s new theme, and more — Weekend Edition #305

Hi there,

This turned out to be a slow news week in WordPress, apart from four days of WordCamp US. You can read the recap here.

I miss my US WordPress friends, I haven’t seen since 2022. To give you a head start on watching the fantastic programming, I added four video links in this edition. I held back the newsletter for the fourth video: Matt Mullenweg’s In-Person Q & A, which was uploaded in the wee hours of this Saturday.

WCUS 2025 will take place in Portland again, August 26 – 29, 2025, and I added it in my calendar to take the long journey to the West coast in Summer once more. Will I see you there?

Have a splendid weekend ahead!

Yours, 💕
Birgit

Join JuanMa Garrido, André Maniero, and Nick Diego on September 24th, 2023 at 15:00 UTC for the Developer Hours: An Introduction to Data Views. Data Views offer a flexible way to display data as tables, grids, or lists, with options for filtering, sorting, and more. Even though it’s still being improved, you can already use the DataViews component in your projects and plugins. In this Developer Hours session, you will explore:

  • How to display a custom dataset using Data Views
  • The fundamentals of the DataViews component
  • How to add a React app to a custom WordPress admin page

Q&A will follow the presentation. As a reminder, JuanMa Garrido recently published Using Data Views to display and interact with data in plugins on the WordPress Developer Blog.

Developing Gutenberg and WordPress

Riad Benguella‘s post on the WordPress Core blog shares critical insights into Gutenberg development practices and pitfalls like inefficient code patterns and the importance of adhering to coding standards. Emphasis is placed on thorough testing and clear documentation to ensure smoother development and collaboration. The post is a handy guide for current and aspiring Gutenberg developers, helping them to avoid mistakes and streamline their workflow for better results. Worth a read if you’re diving into Gutenberg or looking to polish your skills!


The second update on DataViews made it on the Make Design Blog. Here are the highlights:

A view of advanced filtering screen showing how you can combine different filters.

Matt Walker, designer at Automattic, shared his thoughts on Design Systems: Storybook Improvements. First, he references other design systems based on the Storybook. Then he reviewed the current space and suggests a broader architecture review. Walker is at the start of the exploration and request feedback along the way to find out if he is on the right track with his ideas. At the end of the post, you can also locate previous discussions regarding a future design system on color scales, corner radius, elevation, and typography.

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

In case you are keen to learn how the Speed building battle with Jamie Marsland went at WordCamp US, here is the direct link to the recording from the Live stream.: Brian Coords and Amber Hinds rebuilt the home page of a site from the WordPress Showcase: Bi-Rite Market in San Francisco. Tracy Levesque commented on X: “This is one of the best things I’ve ever seen at a WordCamp. It was as riveting as watching a sporting event. Good job, everyone!!”


Rich Tabor, product manager at Automattic, wants you to Meet Kanso, my best blogging theme yet. He wrote: “In Japanese, ‘kanso’ means simplicity or plainness, embodying a minimalist aesthetic that emphasizes clarity and the elimination of the unnecessary. I wanted to create a WordPress theme that reflects this philosophy in the design, writing, publishing, and reading.” The theme comes with 16 color palettes, and offers various patterns to lay out your post list. The source code is available on GitHub and the theme is also available in the WordPress repository.


Big Bite shared a case study about their work with The Times & Sunday Times. “When it comes to breaking news, every second counts. Discover how we transformed digital publishing for one of the UK’s largest publishers, resulting in record-time content creation.” You’ll find a video and impressive numbers. To read the full story, you need to give an email address, though.


Automattic’s special projects team published a list of their open-source tools and plugins. You’ll find five plugins and two blocks, the Accordion and the Stretchy Type Blocks. The plugins are

Theme development for full site editing and blocks

Anne Katzeff continues on her quest to create her first block theme. She shares in her 4th post of a series: Building My First WordPress Block Theme – part 4: Child Themes, how she saves changes to a child theme and syncs it to a GitHub repo for version control.


In his video, Fränk Klein answered Theme.json V3: Common questions, among them: “What did version 3 change? and How to migrate from v2 to v3?”


 “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

Mike Davey, Senior editor at Delicious Brain, highlighted a few Golden Guides and Hidden Gems From the WordPress Developer Blog. “The WordPress Developer Blog is a treasure trove of valuable resources that can help you stay ahead of the curve” he wrote. And he wrote about the What’s new for developers roundup posts: “If you can only manage one post a month, make sure it’s this one. We have to warn you, though: there’s a very good chance it’ll lead you down at least one rabbit hole, and you’ll end up spending more time (and learning much more) than you intended.”

📣 Never miss a Developer Blog post again: Subscribe!

Speaking of which, if you haven’t read the What’s new for developers? (September 2024) edition, it was my turn to put it all together.


Troy Chaplin, long-time WordPress developer and designer from Ottawa, Canada, published his first article on the WordPress Developer Blog. In his tutorial How to build a multi-block plugin, you’ll learn how to build a multi-block plugin by registering several static and dynamic blocks all in one plugin while optimizing its structure along the way.


In his talk at WCUS, Damon Cook unleashed the power of the Interactivity API. He explored with the audience what this API is all about, why it matters, and how to get started with it. By the end, you’ll have a solid understanding of the Interactivity API and be ready to implement it in your projects. You’ll see some great examples, too.


During his WCUS talk, The Power of Extending the WordPress Editor: A Block Visibility Showcase on Showcase day, Nick Diego gave people a peek behind the curtains of his Block Visibility plugin and showed how to make the most out of WordPress Core components. He shared some really useful tips and tricks that help you level up your own projects by extending the WordPress Editor and boosting block functionality. You can follow along his slidedeck here.


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: Photo by Ravi Palwe on Unsplash


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 21, 2024 02:32 AM under Weekend Edition

September 20, 2024

Matt: Are Investors Bad?

Some people have been interpreting my comments around private equity and investors as saying they’re all bad and you should never accept investment or trust a company that does… I don’t agree with that at all. Investors are amazing, they’re the fuel of entrepreneurship and capitalism and responsible for most of what we enjoy today. I can look in the eye of another founder and wholeheartedly recommend Automattic’s investors—True Ventures, Addition, Tiger Global, Salesforce, GIC, ICONIQ, LVMH/Aglaé, Akkadian, Wellington, Sweetwater, BlackRock, Alta Park, Schonfield, Chris Sacca…—and say they’ve upheld open source values and allowed us to nourish the open source ecosystem and flourish as a business. (They’re not an investor, but there are new folks like OSS Capital which are totally open source aligned.)

So investors, even “private equity” ones can be okay, but just like with anything, there are good ones and bad ones, so it is worthwhile to look into their track record. After an investor joins a company, what happens next? Do they change away from an Open Source license? Does the community flourish or wither on the vine as a result of their actions? It can be complex because you can have, as we do in WordPress, some companies contributing and some companies just taking. Some investors, like ours, are minority investors, which means they don’t control the company. Some buy a majority share in companies and control them, and that’s where who ultimately owns things matters the most.

Can they change? Of course. Every saint has a past and every sinner has a future. I think everyone should be afforded that grace. But it can’t just be in words, it has to be in action.

I may make my keynote tomorrow a deep dive presentation into some specific examples of this going poorly, because I think it’s highly relevant to WordPress’ survival. Tune in! There will be a livestream here.

by Matt at September 20, 2024 07:00 AM under WordPress

WPTavern: Patchstack Secures $5M in Series A Funding

Patchstack, a leading WordPress security company, recently raised $5 million in its Series A funding round. The funding round was led by Karma Ventures, G+D Ventures, and Emilia Capital, an investment firm backed by Yoast founders Marieke van de Rakt and Joost de Valk.

“With the Series A, we plan to accelerate Patchstack product development and build a top-level sales and marketing team,” said Patchstack’s co-founder and CEO, Oliver Sild. He believes Patchstack could “potentially hyper-automate the entire open-source software security process.”

In 2022, the company received a €2.7M R&D grant from the European Innovation Council. Earlier this year, Patchstack was also selected by Google for its AI for Cybersecurity accelerator program, leveraging its vast dataset—the largest in the world of open-source security vulnerabilities.

The company’s managed VDP platform, developed in collaboration with the European Union, is free for all plugin and theme developers and helps projects comply with the upcoming European Cyber Resilience Act. 

Last year they published 76% of all known WordPress-related security vulnerabilities and became the largest CVE (Common Vulnerabilities and Exposures) Naming Authority by volume in 2023. Their Zero-Day Bug Bounty Program awarded the highest bounty in WordPress history – $14,400- to John Blackbourn, who exposed a critical vulnerability in the LiteSpeed Cache plugin last month.

“I have been following Patchstack’s progress for some time, have had many great discussions with Oliver, and think that the team is on a noble and exciting mission to protect users of open-source technologies from cyber threats,” said Kristjan Laanemaa from Karma Ventures.

by Jyolsna at September 20, 2024 04:33 AM under Patchstack

September 19, 2024

WPTavern: Matt Mullenweg’s Ecosystem Thinking for Open Source Success 

WordCamp US 2024 is in full swing, and Matt Mullenweg, co-founder of WordPress, shared his thoughts on a powerful philosophy driving Open Source. 

Ecosystem Thinking

Mullenweg introduced the concept of “Ecosystem Thinking,”  a philosophy that drives successful collaborative projects. 

Actual Open Source licenses are the law that guarantees freedom, the bulwark against authoritarianism. But what makes Open Source work isn’t the law, it’s the ethos. It’s the social mores. It’s what I’m now calling Ecosystem Thinking: the mindset that separates any old software with an open source license from the software that’s alive, that’s humming with activity and contributions from a thousand places.” he noted.

This philosophy comprises four essential elements:

  1. Learn: Embrace the beginner’s mindset and constantly engage with new ideas.
  2. Evolve: Apply what you learn to the next iteration, allowing real-world feedback to guide you.
  3. Teach: Teaching others reinforces your own understanding, spreading knowledge throughout the ecosystem.
  4. Nourish: Share the fruits of your success with the broader community to help everyone thrive.

‘Nourish’ is the philosophy behind WordPress’s Five For the Future initiative, where companies and individuals commit a portion of their resources to supporting the WordPress project and ecosystem. This ethos is what keeps Open Source alive and vibrant.

Mislabeling Open Source

He also shared the challenges Open source is facing. Even though Open Source has taken over as an “intellectual and moral movement,… false prophets like Meta are trying to co-opt it.” He referenced Meta’s “open-source” AI model, Llama, as a prime example of this trend.

While LLaMA is free, its license restricts use for companies with over 700 million active users. Mullenweg argued that although Meta has the right to impose such terms, labeling it as “Open Source” misleads the public.

Vote with your Wallet

Mullenweg encouraged the community to “vote with your wallet” by supporting companies that actively contribute to the Open Source ecosystem. He praised organizations like Newfold, Awesome Motive, 10up, Godaddy, Hostinger, and Google but warned of “parasitic entities that just want to feed off the host without giving anything back.”

To make his point, Mullenweg compared the Five For the Future contributions from Automattic and WP Engine, a competitor of similar size. Automattic contributes 3,786 hours per week, while WP Engine contributes just 47.

“Those of us who are makers, who create the source, need to be wary of those who would take our creations and squeeze out the juice. They’re grifters who will hop onto the next fad, but we’re trying to build something big here, something long term—something that lasts for generations,” he said.

Mullenweg urged the community to be mindful of their choices: “Think about that next time it comes up to renew your hosting or domain, weigh your dollars towards companies that give back more, because you’ll get back more, too. Freedom isn’t free.”

This is not the first time Mullenweg has discussed this point. “Those who care about the future of WordPress should spend their dollars with less parasitic companies,” he said in 2022.

by Jyolsna at September 19, 2024 06:46 PM under open source

Do The Woo Community: A Blog for the Community, by the Community

Episode Transcript

BobWP:

Well, hello, BobWP here. I am sitting in my motel room recording this while at WordCamp US. So much stuff going on, this being the Thursday the 19th, have already done 2 days of the hectic schedule and now into the official two days of the camp

There’s a lot I could share with you so far, but that is not why I am here. And I mean by talking to you and not where I am physically.

On September the 2nd I pushed out a post on Do the Woo called The Soft Relaunch of the Do the Woo Blog, It was short, and hinted a bit of what we have in store. Then while I’m here at WordCamp, I realized that in that post I said I would be telling you more about the blog. Which was not optimal nor did I plan that as it should have been.

So I felt obligated to do this episode while knowing I still have a few things left to do.

But let me share where we are at.

As I mentioned in that post, Ronald Gijsel and myself did a podcast while we brainstormed the ideas around what the Do the Wo blog would look like. Why was there no blog. At some point last year I decided to move posts off of the site and focus on the audio we were putting out. Several reasons for that but in hindsight it was probably a mistake or at least something I should have just let ride.

Then I realized, maybe I woke up, that the site had a big missing part to it. And also, I was missing blogging here at Do the Woo. For someone who has blogged since 2018, well, a void in my life. Of course, as Ronald and myself talked about the blog, it was obvious that we have the perfect site for a blog

Yes, a blog by the community and for the community. Want a rundown on my plans

I will blog of course. But hosts, guests and friends of do the woo will also guest post.

We are not going down the tutorial path, doing reviews, building a news blog or pitching products.

What we want is conversations continuing based on podcast episodes. For example, a guest wants to dive into a topic that they only were able to mention on the episode. Or perhaps they have additional thoughts that didn’t get covered. And yes, at anytime a past guest can come in and update us on something that was mentioned in their show. In other words, a lot of flexibility.

But what about your the listener? Maybe leaving a comment isn’t enough for you. You may have thoughts on an episode and would like to write a guest post to share them with our audience. These could be as short as a paragraph or two, or if you have a lot to say, as long as you need to make it.

Of course, guest posts will be scrutinized to make sure they cover what we are looking for.

We have a three things that will make your content that you post here so valuable. One we will be sharing soon, and the other two likely will be worked on for the next several month.

And, we will soon have things in place if you want to do a guest post, or maybe even become a regular. Things like guidelines, forms to submit your interest to us, etc, etc. In fact I will write a blog post something after I return home here from WordCamp US when all of these things are in place.

So that’s it. If you did carve out sometime to actually listen to this and you are still at WordCampUS, please let’s connect and at least say hi if we haven’t already. And to everyone out there, we are excited to share and amplify even more voice from this community.

Until the next time.

In this episode, BobWP records from his hotel room at WordCampUS, sharing exciting updates about the soft relaunch of the Do the Woo blog.

Bob reflects on past decisions, including the removal of blog posts from the site, and how he now realizes the blog’s absence created a void in the community.

He outlines plans for the blog’s future, including contributions from hosts, guests, and even listeners, creating an open space for continued conversations around podcast episodes.

Keep your eyes and ears open to hear more about how Do the Woo is amplifying voices and building stronger community connections.

Links

by BobWP at September 19, 2024 05:29 PM under Blogging

September 18, 2024

WPTavern: WordPress.com Offers 1,000 Free Premium Websites to University Students

WordPress.com announced that it is giving away 1,000 free premium websites exclusively to university students. This offer is a fantastic opportunity for students to build their online presence.

The first thousand students who sign up will receive a premium WordPress.com website for one year, complete with a free custom domain name, SSL certificate, 13 GB of storage, access to premium themes, and an ad-free experience. With these features, students can create professional websites to showcase their portfolios, projects, or blogs. 

“This offer is perfect for students looking to stand out in their personal and professional journeys, ” WordPress.com said in the official announcement.

Interested students can fill out a simple form with their educational details and email address. After submitting, they will receive an email asking them to verify their student status. Once verified, a unique code will be provided within 24-48 hours to unlock their free premium website. 

Recently, the WordPress community has been trying to find ways to attract new users in the backdrop of discussions about the WordPress market stagnating. Executive Director of the WordPress Project, Josepha Haden Chomphosy, has also recently spoken about how WordPress equips students with essential skills for thriving in their future careers.

by Jyolsna at September 18, 2024 07:19 PM under wordpress.com

WPTavern: #137 – Jamie Marsland on Heading the WordPress YouTube Channel

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, how YouTube can promote the WordPress project.

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 Jamie Marsland, and it says third appearance on the podcast, which is a first.

Jamie has recently embarked on an exciting new journey as the head of the WordPress YouTube channel at Automattic. This role is set to amplify the WordPress story through engaging and informative video content, capitalizing on YouTube’s reach to over 2.7 billion monthly users.

As you’ll hear, Jamie only started his role a few days prior to recording, but he’s already full of plan lists to transform the WordPress YouTube presence. Automattic created this role to ensure a more focused effort on growing the channel, which currently has around 36,000 subscribers, significantly lower than some of the other WordPress YouTube channels.

Jamie envisions targeting distinct groups. Beginners, DIYers, developers and designers, agencies and freelancers, product suppliers, and the community. Each piece of content will aim to add value whilst trying to maintain some fun.

Throughout our conversation, Jamie shares his insights into why this role is necessary, especially in light of commercial rivals like Wix and Squarespace, who possess enormous marketing budgets. He discusses the importance of bringing new users into the WordPress ecosystem, whether they’re complete beginners or migrating from other platforms.

We also explore Jamie’s broader vision for the channel, including making high quality content that genuinely adds value to the viewer, regardless of its production quality. He stresses that every video needs to answer the question of what value it brings to the audience. Fun and engagement are key themes, but quality content is paramount.

We also touch on his plans to bring in other voices, aiming to build a diverse team that reflects WordPress’ global reach.

Jamie also talks about the balance between engaging the YouTube algorithm and producing valuable content. He shares his experiences and strategies for creating content that draws listeners in, emphasizing the importance of creativity in ensuring all target groups find something of interest.

Jamie assures us that his new role won’t mean an end to his own popular YouTube channel, which has been advocating for WordPress for many years. He plans to continue creating content on this channel, whilst focusing on growing the official WordPress channel.

Towards the end, Jamie hints at the changes that might start materializing by October, post WordCamp US. He’s eager to hear from the community, so if you have innovative, fun or valuable content ideas, Jamie wants to know.

If you’re interested in the evolving landscape of WordPress on YouTube, Jamie strategic approach, or how you might contribute to this exciting venture, this episode is for you.

If you want 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 Jamie Marsland.

I am joined on the podcast, again by Jamie Marsland. How you doing, Jamie?

[00:04:35] Jamie Marsland: I am really sorry about all these appearances. I’m great, thank you, Nathan.

[00:04:38] Nathan Wrigley: Honestly, the reason that you’re appearing many times is because you have many things to say. But I believe you’re the first person to appear for a third time. And it wasn’t all that long ago that we were talking about your speed builds happening at WordCamp Europe. Well, maybe that is going to come up today. Let’s find out.

[00:04:53] Jamie Marsland: Well, it’s coming to WordCamp US in a few weeks time, so there you go, there’s a plug for that.

[00:04:57] Nathan Wrigley: Well, it’s exciting. Well, maybe we can get into that specifically a little bit later, but that’s not the main reason. The main reason is because you’ve taken on a brand new role. And rather than me butcher what that role is and what you’re doing, you just want to give us your brief potted bio?

[00:05:11] Jamie Marsland: I’m now working for Automattic as head of the wordpress.org YouTube channel, which is an incredibly exciting role to fulfill. So I started literally two days ago, and I’m now in day three, it’s Wednesday, isn’t it? Day three of my onboarding, of which I’m going to go onto the wordpress.org forums this afternoon as part of, when you join Automattic you do a support rotation, so I’ve got two weeks support rotation, and then I start in earnest on the YouTube channel.

[00:05:36] Nathan Wrigley: Is this a brand new role? My intuition says, I think it is because I’ve not heard of it before.

[00:05:41] Jamie Marsland: It is a brand new role. There is a team working diligently on the YouTube channel doing cool stuff, and they’ve grown it actually really well, but there’s no one sort of leading on the channel. Everyone in that team is doing lots of other cool stuff as well. So this is having somebody completely focused 100% on growing the channel.

[00:05:57] Nathan Wrigley: Okay, so I’m imagining that more or less everybody knows what YouTube is, and probably has gone down that alley of stepping into YouTube, and then several hours later figuring out that they’ve lost their entire day on YouTube. Why do we need this role then? So you mentioned that there’s a team. Is it just that it was felt that that effort wasn’t sort of guided correctly, that there needs to be more content? Why the role?

[00:06:19] Jamie Marsland: Can I give you some stats on YouTube, because this blows my mind? So as of 2024, YouTube has more than 2.7 billion users every month. That’s 51% of all people who use the internet. One third of everyone in the world uses YouTube monthly, a third of everyone in the world uses YouTube monthly. And over half the people who use the internet on their phones visit YouTube each month.

So YouTube is, I mean it’s just absolutely massive, and WordPress, the official channel, has as we speak, about 36,000 subscribers. And if you compare it to its, let’s say competitors, it’s lower than it needs to be. So that’s why there’s now a unrelenting focus from me on helping WordPress through that channel.

[00:07:02] Nathan Wrigley: So is there a particular kind gap that you are trying to fill here? Because obviously, you know, YouTube is just full up of content for literally everything. Is it going to be directed mainly at a particular type of YouTube content? Do you have any sort of intuitions as how that’s going to go? You know, is it going to be related to Gutenberg, or Core? Well, I’ll leave it open to you.

[00:07:22] Jamie Marsland: At the moment, and I’m obviously on day three, this is kind of how I view the world in terms of the content groups we’re going to aim content at. What I’m also asking everyone is to let me know what you think, so I’d be interested to know what you think about this, Nathan.

So these are the kind of groups we’re going to target content at. So I’ve got beginners, group one. DIYers, developers. We’ve got designers, agencies and freelancers, product suppliers. So that’s plugins, and themes, and service providers, and then we’ve got the community. So broadly, six groups of target viewers that, at the moment, that’s what I’m thinking the type of content we’re going to produce content for.

But at the top of that, we have the kind of overlying everything is, you know, every piece of content that we want to produce on that channel needs to kind of tell the WordPress story, or help tell the WordPress story, what the story is. That’s all the things that make me love WordPress. So it’s empowering, it’s free, it’s open, it’s radical, it’s fun, it’s being used by loads and loads of people. So everything needs to kind of fit under that story.

And then we’ve got those groups of people that we want to target content at. And then within that we’re going to have a number of different formats. And then flowing from those formats will be the actual content itself. That’s the way I’m viewing the world at the moment. Early days, I’m asking people to give me their feedback.

[00:08:34] Nathan Wrigley: I’m going to give you a little bit of feedback on that. So you had six categories there, and they all speak to people already using WordPress. I wonder if part of the role, given all of the talk that we’ve had recently about, you know, commercial rivals in the website building space having giant marketing budgets, is that piece of advertising to the, as yet undecided, website builder. Drawing in people who are just curious about starting a career in web development, or want their own website? And obviously WordPress has that sort of free and open credentialing to it. Trying to draw them in as well and just say, okay, here’s WordPress, you’ve never used it, this is what it could do for you.

[00:09:12] Jamie Marsland: Yeah, and that’s a massive part of my thinking. I would probably group that group of people into beginners or pre beginners. Yeah, that was one of the biggest pieces of feedback. I put out this tweet, and put a post on Facebook and LinkedIn, and got tons of feedback and fantastic ideas from people of the type of content.

That was one of the strong themes coming through is, how do we bring people on board to WordPress from either, they’re looking for the first time, or they’re using something like Wix and they don’t realise where the roadblocks they’re going to hit at some point in the future? So, one hundred percent.

[00:09:40] Nathan Wrigley: Just a little bit of personal story then. How did this role come your way then? So just curious as to, two sides to that really. How did the negotiations happen and, you know, how did you get into this role existing in the first place, and why the role now? I guess I’m alluding to the whole Wix thing that I mentioned a moment ago. Is it that the time is right to concern ourselves with the commercial rivals out there and the march that they’ve got into the marketplace?

[00:10:05] Jamie Marsland: So I’m going to skip some steps here, just to give you a broad brush stroke. So I did some research about, I guess it was a year and a half ago was it, maybe two years ago, looking at the YouTube channels of wordpress.com, wordpress.org, and also the competitors, so Wix, Squarespace, Shopify, and a few others. Did a blog post, and then I sent the blog post around to some people within Automattic that I’d sort of been chatting to, and saying, I can help with some of this stuff.

Now, I’m skipping a lot of steps here, Nathan. And following from that, I had lots of discussions. And then I did a series of videos with wordpress.com and the team at wordpress.com, and started chatting to some people within Automattic. So I did 24 videos for them. Obviously more conversations around the video strategy for .com and .org. And, again, I’m skipping lots of steps.

Then I met up with Matt Mullenweg in Turin for an hour, and had a fantastic chat around video, and content, and competitors, and then more conversations. And then it kind of crystallised while I was on a mountain, climbing up a mountain, when I say climbing a mountain, I was walking along a mountain in France. You know, started to formulate what the role could be, what the need was, you know, my desire to do it, which was massive. So for me it’s like the perfect, because I’ve been kind of doing this stuff on my own channel for three years. So this was like the perfect opportunity to kind of work on a bigger stage really.

[00:11:22] Nathan Wrigley: Yeah, that’s great. I’m curious as to the nature of the conversation that you had with Matt. Obviously, Matt, the co-founder of WordPress, largely guides the project, if you like. We have a lot of intuitions that come from Matt, which then turn into the reality of the project. Whilst I don’t want you to reveal anything of a confidential nature, I am curious as to hear what thoughts came up in that meeting as to the importance of this job, you know, the kinds of things that he would like to have seen you doing.

[00:11:47] Jamie Marsland: I mean the first thing to say, it was a great conversation because I’d never met Matt before. So, we struck it off really well, which was fantastic, and massively intellectually curious, that was a very interesting conversation. But it was kind of centered around content, and the importance of video content, and what WordPress is doing in terms of video content at the moment, and just the massive opportunity there is for video content in the WordPress, official WordPress space.

Obviously, there’s some amazing content being produced by other creators, but on the official channel, as I say, we’ve got 36,000 subscribers. So there’s a massive opportunity to get more engagement, and sort of spread the WordPress word.

[00:12:22] Nathan Wrigley: The fact that you are doing content on YouTube, does it allow you this role to also do video content elsewhere? So one of the things that comes into mind is the Learn project, so learn.wordpress.org is making lots of educational content, much of it in the form of videos. I wondered if there was any overlap with those teams, or any opportunity to overlap. Because it sounds like a lot of the pieces that you’re going to be making are educational in nature.

[00:12:48] Jamie Marsland: Obviously it’s very early days, and they’ve got a team producing lots of Learn content, which is currently going on the YouTube channel, which is great. There’s an interesting space which says, what is the connection? Because some of the content they’re doing is very, very good if you are going step by step through videos. But I think there’s an interesting discussion that says, how can we start to tailor some of that content? So it’s kind of more suited to specific YouTube audiences.

Because when you go onto YouTube, you’re kind of in a different frame of mind than if you are going onto a learning management system. And I think they’re two quite separate pieces of content, like some of the content I produce on my channel is more edutainment than just educating people around it. It’s got to kind of grab them quite quickly, and you’ll get more engagement and more learning. So there’s some interesting, definitely some interesting overlaps there. Early thinking on that though.

[00:13:34] Nathan Wrigley: One of the things that Matt said during his address in WordCamp Europe, where obviously you had your meeting with him, one of the things that I took away from that was that he wants WordPress to feel a bit more fun. I don’t really have my finger on the pulse of what entirely he made of that, but it did strike me that your speed builds was a really, you know, it was a really credible way of doing that. It’s entertainment with learning bolted in, which is really nice. You get the fun of doing it at the same time, and if you’re paying attention, you will actually learn things, which is kind of like the perfect goal.

I did wonder that was how you were hoping to drive it, if it was supposed to be fun. If you’d got any guidelines about that, if you’ve got any thoughts on that. Because I always enjoy watching fun content more than sort of the dry stuff. But nevertheless, sometimes the dry stuff is what you need to do, so whether it’s a bit of everything, or direction is fun, over to you.

[00:14:26] Jamie Marsland: We’ll bring the fun. There will be more fun, but it’s not all going to be fun. But it all needs to be great. I think the key thing is it’s going to have massive value. If it’s going on the channel, it needs to have massive value to whoever’s watching it, and that’s probably somebody within those six groups. So there will definitely be some, I’ve got some ideas, there’ll definitely be some fun stuff, and definitely more live stuff.

We want to try and have a connection with the end users that are using WordPress. So definitely more fun. But there’s some really cool stuff going on on the wordpress.org channel, which, with a little bit of love and attention, we can elevate to the next level quite easily. Like there’s some amazing developer stuff going on with Justin Tadlock and his team, and Nick Diego, and Ryan Welcher. Just gold dust in there.

And there’s some really simple things we can do really quickly to get them more views. So there’s some easy low hanging fruit. So some of that developer stuff is absolutely fantastic, but there is a lot of stuff on there that’s, at the moment there’s this automatic feed, so there’s a lot of stuff that just, it’s like a bucket, just gets dumped on there.

So there’s a conversation to be had around how we tailor that stuff. Do we keep that process going where it’s just automated? So we have lots and lots of videos on there, which don’t necessarily all reflect what we’re trying to reflect in terms of the WordPress story. I’m not sure that’s answered your question, but there’s going to be more fun.

[00:15:36] Nathan Wrigley: Running through that, the message that you gave me at the beginning of that little section was that you want it to be of high quality. The importance is on the high quality. So if it’s fun and high quality, that’s great, if it’s serious and high quality, it’s great. But if it’s fun and low quality, no.

[00:15:50] Jamie Marsland: And I think, when I say high quality, I’m not talking about production value, I’m talking about value to the person watching it. If it’s filmed on a phone in a field and it’s absolute gold dust, then that’s okay. But it has to be, every bit of content has to ask itself the question, what value am I giving to the person watching this? Why are they going to watch this piece of content? And if we can’t answer that, then it shouldn’t be on the channel anyway.

[00:16:08] Nathan Wrigley: Yeah, it’s interesting, sort of editorial guidelines, you know, if the BBC, for example, the British Broadcasting Corporation, I imagine they have a quality guideline about how it looks and feels, not just about the quality of the content. But that’s an interesting position that you take there. If the content is good but the production quality is not that great, that gets a pass.

[00:16:26] Jamie Marsland: I think there’s probably a couple of phases of this. The first phase is, it’s got to be all about the content. And then the second phase, then we look at the production. And you can do these together, but the most important thing is the content has got to have, it’s got to have value.

One of the best lessons I ever learned in running a YouTube channel is that there’s only three reasons why somebody will ever click on a YouTube thumbnail, because you are competing against lots of other people on YouTube. And those are curiosity, number one, hope, number two, or fear. Those are the three psychological triggers that make anyone click onto a YouTube video. There’s some broad guidelines we can start to introduce.

[00:17:00] Nathan Wrigley: I think also it’s important for the creator of the video to have a white border around them, and to be pointing at something with their mouth open.

[00:17:08] Jamie Marsland: Actually, no, that’s not true anymore. There’s been some stats that show that mouth open isn’t working anymore.

[00:17:12] Nathan Wrigley: Okay. Oh gosh.

[00:17:13] Jamie Marsland: I’m serious about that.

[00:17:14] Nathan Wrigley: People go into it at that level. So the content that you’ve created on your own YouTube channel has been you creating content, and you’ve obviously been very successful at that, and I imagine that that is the primary reason that you’ve got into this discussion, got this job. So bravo for that firstly.

But secondly, does this new job point to an era in which you, the head of YouTube, are making all of the content, or are you hoping to bring other voices in? And into that question I’m going to throw the sort of international thing as well, you know, different languages, different parts of the world, different perspectives.

[00:17:47] Jamie Marsland: So, no, definitely won’t just be me producing videos. I mean, my plan is to make myself redundant over the next three or four years, and build a team of younger, diverse people that reflect where WordPress is heading. So that’s part of my plan. And then part of my plan is, and I’ve been reaching out to other content creators in the WordPress space, is to help them to amplify themselves, and get them on the channel as well. Because there’s some people doing some amazing stuff. And also people in the community.

Plus we’ve already got some existing amazing content that’s going on through people like Justin and his team, and the Learn team. So absolutely not, it won’t just be me. I will definitely be on the channel, but hopefully I’ll be a fraction of the overall content going forward. There was another part of your question, which I didn’t answer.

[00:18:25] Nathan Wrigley: Well, there was the international part, so the different languages all around the world. So it’s not just in English basically.

[00:18:30] Jamie Marsland: Yeah, that’s a really interesting one. So one of the challenges you face when you run a YouTube channel is that, if you produce a piece of content that doesn’t get many views, it’s a bit of a channel killer. So what will happen is their algorithm will say, they’ve just produced, you might have one piece of content that gets like 10,000 views, if you produce a piece of content that only gets like 12 views, that will affect the overall channel views.

You need to be aware of that when you’re running and trying to grow YouTube channel. I’m going to go onto the international bit. So that’s one of the things we need to confront pretty quickly. We need to make sure that the content we’re producing is always creating a high number of views, otherwise it affects the overall health of the channel.

So one of the decisions on the international stuff is, does that fit into that? How does that fit into that? Does that affect the channel because our audience is expecting one thing and they get another thing, and it might get lower views? Or do we say, we create multiple channels for multiple languages, or do we create multiple channels for multiple, like there’s thousands of word, well, not thousands, but there’s lots and lots of WordCamps that happen around the world which are currently being presented on the YouTube channel, which might not get massive amount of views, but are very important content. So the question is, do we have a separate channel for those, so it doesn’t affect the main channel in terms of the algorithm and kind of story we’re trying to tell on those? So those are some of the kind of quite difficult decisions we need to make fairly early on.

[00:19:43] Nathan Wrigley: That’s curious because you are having to worry about the algorithm of YouTube, not just the quality of the content, but whether the content is going to receive the click. So some part of your brain has to be engaged with how viral, for want of a better word, maybe that’s not quite right word. But, you know, something like, how viral will this piece of content be?

And I guess that raises concerns about, if we’re always chasing the algorithm, do we then drop the stuff which may not get the clicks or the views, but could be really important? So for example, the last piece you mentioned, I think it was number six, community, that may not get quite the number of views as, oh I don’t know, the latest, greatest new feature that’s come out in WordPress, or your speed builds, or whatever that may be. But it’s still equally important, and that’s going to be a difficult tightrope to tread, isn’t it? It’s sprinkling that stuff in that you have an intuition won’t be quite so popular, but is probably needed.

[00:20:31] Jamie Marsland: But I think there’s creative ways of making that stuff interesting to people that it will get clicks. That’s the challenge of the channel, right? So all those six groups, I’m confident we could create content that is really interesting, that would get a large amount of clicks. But it needs to speak, it needs to focus on the value it’s bringing to the people that are watching it. That’s got to be the a hundred percent focus.

I spend a huge amount of time on my thumbnails and title, and I want to instill that in the content that’s going on the channel. I do that because, and this isn’t just me making this stuff up, this is coming from like, the best YouTubers all do this as well. And if you do that, then it focuses your video on the value you are creating. You are trying to create to the person watching it. And if you can’t get a YouTube thumbnail and title sorted out, it means you haven’t got your story straight in your head, and you’re not sure on the value of this piece of content is going to bring to the people watching it. If you can’t do that, then you shouldn’t make the video. It’s a really useful discipline to go through, and it’s one I want to instill on any piece of content going forward, because it focuses the whole point of the video.

[00:21:28] Nathan Wrigley: But the bottom line is you are open to other voices, it’s not just going to be Jamie making video content. And a question which is related to that, but not entirely the same, the content that I’ve seen of you so far has been heavily related to a core version of WordPress. You know, you download WordPress from .org and you run with that. You’re not chucking a load of other things in, third party plugins, and themes, and what have you.

And I do wonder if that has a place in this new future. Whether or not third party plugins, themes, blocks, whatever it may be, whether there’s going to be scope for those. Maybe there’ll be an embargo on, well, it has to be in the repository. I don’t know. Again, just over to you, what are your thoughts?

[00:22:04] Jamie Marsland: Yeah, my view is a hundred percent, I want those in there. Because it’s one of the best things about WordPress, that we have 60,000 plugins and thousands of amazing themes. The challenge is how you do that without annoying the heck out of everybody that isn’t featured on that week. I want to find formats that we can showcase stuff without annoying people that aren’t on there.

But if you think about it, wordpress.org is already advertising all those 60,000 plugins, so we absolutely should be. And there’s some amazing stuff happening, some amazing innovation happening, so we definitely want to showcase that stuff on the official channel, is my view at the moment.

[00:22:34] Nathan Wrigley: I’m just curious about the cadence at which you are hoping to do this. Because at the moment, Jamie’s YouTube channel, I presume that there is importance in you getting content out on a regular basis to satisfy the algorithm. But it’s up you how often you want to do that. You know, you can take a week off here, a week off there, and go out for a walk or whatever, whenever you feel. And I’m just wondering how this is going to play. Do you have intuitions there? You know, it’s got to be several things a week, several things a day. It’s a big community after all, we could probably create that content. But, any thoughts?

[00:23:03] Jamie Marsland: Well, yeah, if you look, at the moment there’s tons of content going on it, but I think there’s too much content. I think the cadence will be, the first step is to get a content plan, which I’m going to share I think at this point, get a content plan together drawing on all those things that I’ve talked you through already.

And then I think the cadence drops out from that. Once you’ve got the content structure in terms of those groups, and then you’ve got the formats flowing from those. So like we’ve already got developer hours who have a certain cadence. And then you’ve got the content plan from that, the cadence will be dropping out from that. But my view is at least two a week.

But probably, as we start to power the engine many more. And, you know, the other thing that we want to do far more of is repurposing this content for like social media, because at the moment that’s not really happening. Once we get the source content the way we want it, that’ll be much, much easier. Because that’s been a lot of the growth of my channel, is resharing relentlessly on Twitter, and Facebook, and LinkedIn. LinkedIn especially at moment, actually.

[00:23:55] Nathan Wrigley: You’ve obviously been making content recently, and I presume you’re doing that because you enjoy it. Is there any part of you which is a little bit nervous about the fact that you are going to have this more managerial role and, you know, taking care of other people’s content, and less time in the video editor, making the content, thinking about the topics, and creating the titles and the thumbnails and all that? They’ll presumably be handled by you, but also by other people. Is there a bit of you, which is, I don’t know, a little bit sad at waving goodbye to your own endeavors?

[00:24:20] Jamie Marsland: I’m not waving goodbye to them. So my own channel is going to carry on. And actually this will probably give me, well, it will give me more freedom to be a bit more, I’m going to be quite experimental, but probably more experimental on my own channel. So that’s definitely going to continue. I’ve paused sponsorships at the moment on that channel, just to avoid some conflicts of interest.

But I have to say, I did have pre-match nerves about two weeks ago when I first got the job. Because normally I wake up and I’ve got like a hundred ideas banging around my head for videos, and for about a week I literally had nothing going on in there. It was like a vacuum of ideas, which was a bit worrying. Thankfully they’re back.

So yeah, I’m so excited about being able to run a channel, and there’s all these amazing people that I can now, that I’m already chatting to about the stuff they’re already doing and how we can take it to the next level. So the community aspects are like incredibly exciting.

[00:25:05] Nathan Wrigley: So just to be clear, there’s no embargo on Jamie ceasing doing what Jamie’s doing already. You’ve got free reign to keep making your own content. You know, you’re a good custodian of that. You don’t create incendiary content and drop a bomb walk away, or at least that’s not what I’ve seen anyway.

[00:25:20] Jamie Marsland: I’ve been advocating for this, for WordPress, for three years on my own channel. So it’d be a bit weird if I stopped. I’ve got over 100,000 subscribers on that channel now, so it’d be a bit weird if I didn’t keep producing video content that kind of advertise WordPress on that channel because it’s got a big audience. The same with my Twitter and LinkedIn. I’ll use all those channels to help the wordpress.org channel as well.

[00:25:41] Nathan Wrigley: Do you know if that puts you in a unique position at Automattic? Because I don’t know, I genuinely don’t know the answer to this, but I have some thoughts that when people join Automattic, there may be contractual things that they can and cannot do. And obviously in this case, you know, that probably doesn’t matter quite so much because it’s not like you’re doing two jobs. Your YouTube channel is presumably going to be in your evenings and weekends. It returns to being more of a hobby. There’s just a thought around that, whether people have, you know, mentioned that to you.

[00:26:06] Jamie Marsland: They have mentioned that to me. And it is a unique position, I’m not sure there’s any perfect scenario for it because if I hadn’t grown the channel, then I probably wouldn’t be good for the YouTube job, because I’ve got experience of running a YouTube channel. So it would be quite hard to run this. And then people would say, well, why are you running the YouTube channel if you’ve never run a YouTube channel before? That’s kind of a difficult one.

And also it is unique because, if you think about it, Automatticians obviously tweet and make videos on their own channels, you wouldn’t expect them not to do that because they’re tweeting. To answer you, it is a unique thing. I’m not sure there’s any easy answer to it, apart from I’m hopefully helping WordPress in everything I’m doing. That’s been the sole point of my own channels, is to advocate strongly for WordPress over the last three years. So I’ve kind of been doing this job for free until recently, when I started taking sponsorships for a while. It feels like a continuation that, but just on the official channel actually.

[00:27:00] Nathan Wrigley: When do you anticipate we’re going to see the beginnings of your endeavors here? So we’re recording this very early in September, 2024. You’re obviously doing the support role at Automattic, answering support tickets, just like every other Automattician did. And once that fortnight, two weeks is expired, presumably you’ll have your head turned onto this role. How long do you think we need to wait before we start seeing the ball rolling?

[00:27:23] Jamie Marsland: I’ve got two weeks rotation, and then we’ve got WordCamp US, which is very exciting. Come and check out the speed build on the 19th with Brian Coords and Amber Hinds, which is going to be an exciting one. I think we’re in the main room as well, so that could be huge if we are, that could be a big one.

So I suspect we’ll start seeing some changes around October. It’s important to do some groundwork first before just breaking everything. Although we could just break everything, and see how it goes. See how many people I can annoy within a shortest space of time. But I’m very impatient to get on and start improving things. But also incredibly excited because there’s so much cool stuff happening.

So if anyone’s got, you know, I’ve been asking people, if you’ve got anything exciting going on that you want to share with the world around WordPress, whether it’s innovative, fun, crazy, enterprise, beginner. I really want to hear your stories, so just send them to me.

[00:28:09] Nathan Wrigley: When you say send them to you, what’s the best way to do that?

[00:28:12] Jamie Marsland: Good question. So I’ve got an Automattic email, now this is very strange. Still don’t know what it is, I think it’s jamie.marsland@automattic.com, or just tweet me on Twitter at pootlepress. But yeah, just get in touch. Send me your ideas, I want as many ideas as possible.

[00:28:26] Nathan Wrigley: And if you’re listening to this in the year 2025, I presume you’re going to be heading to youtube.com/wordpress.

[00:28:32] Jamie Marsland: Yes, exactly. Yeah.

[00:28:35] Nathan Wrigley: I’m not entirely sure whether that’s the right URL, but I’ll make sure to find out, and link it into the show notes. So hopefully this episode will reach the airwaves prior to WordCamp US. And you are doing a speed build, and as you said, it’s Brian Coords. If you’re not familiar with Brian, I think it’s fair to classify him as developer. And you’ve also got Amber Hinds, and I think it’s fair to classify Amber as accessibility advocate.

I thought that was a really curious combination. And I wondered if that was very intentional in terms of two different outputs. If you’re following Brian, I’m presuming we’re going to see a focused on the front end, focused on the design, making it look accurate to whatever it is that you serve up. Whereas I was curious, you know, are we going to see Amber focusing on just getting the menu exactly right? Which may take the full half an hour with all the aria labels and things. Are you hoping for that?

[00:29:22] Jamie Marsland: I am hoping for that. I think it could be really interesting. But in the heat of panic, who knows what might happen. I think Brian’s been practicing as well. He’s done a live practice on YouTube, which I think shocked Amber a little bit. But yeah, I think it’ll be a really interesting combination to see the two different approaches. And I still haven’t chosen the website, so if anyone’s got any ideas for that.

[00:29:41] Nathan Wrigley: It’s Ling’s Cars, let’s be honest. It’s not going to be Ling’s Cars. Okay, well, that genuinely is everything that I’ve got to ask you today. So, Jamie Marsland, all the best. First of all, massive congratulations. Your endeavors have not gone unrecognised by just about everybody in the community. The quality of what you’ve been doing has been second to none, and utterly deserved position. And I hope it proves to be everything that you wish it to be. Well done.

[00:30:03] Jamie Marsland: Thank you so much, Nathan. Good to talk.

On the podcast today we have Jamie Marsland, and it’s his third appearance on the podcast, which is a first.

Jamie has recently embarked on an exciting new journey as the Head of the WordPress YouTube channel at Automattic. This role is set to amplify the WordPress story through engaging and informative video content, capitalising on YouTube’s reach to over 2.7 billion monthly users.

As you’ll hear, Jamie only started his role a few days prior to recording, but he’s already full of plans to transform the WordPress YouTube presence. Automattic created this role to ensure a more focused effort on growing the channel, which currently has around 36,000 subscribers, significantly lower than some of the other WordPress YouTube channels.

Jamie envisions targeting distinct groups: beginners, DIYers, developers and designers, agencies and freelancers, product suppliers, and the community. Each piece of content will aim to add value, whilst trying to maintain some fun.

Throughout our conversation, Jamie shares his insights into why this role is necessary, especially in light of commercial rivals like Wix and Squarespace, who possess enormous marketing budgets. He discusses the importance of bringing new users into the WordPress ecosystem, whether they’re complete beginners or migrating from other platforms.

We also explore Jamie’s broader vision for the channel, including making high-quality content that genuinely adds value to the viewer, regardless of its production quality. He stresses that every video needs to answer the question of what value it brings to the audience. Fun and engagement are key themes, but quality content is paramount.

We also touch on his plans to bring in other voices, aiming to build a diverse team that reflects WordPress’ global reach.

Jamie also talks about the balance between engaging the YouTube algorithm and producing valuable content. He shares his experiences and strategies for creating content that draw viewers in, emphasising the importance of creativity in ensuring all target groups find something of interest.

Jamie assures us that his new role won’t mean an end to his own popular YouTube channel, which has been advocating for WordPress for many years. He plans to continue creating content on this channel, whilst focusing on growing the official WordPress channel.

Towards the end, Jamie hints at the changes that might start materialising by October, post WordCamp US. He’s eager to hear from the community, so if you have innovative, fun, or valuable content ideas, Jamie wants to know.

If you’re interested in the evolving landscape of WordPress on YouTube, Jamie’s strategic approach, or how you might contribute to this exciting venture, this episode is for you.

Useful links

Jamie’s Speed Build session at WordCamp US 2024

WordPress YouTube channel

Learn WordPress

Developer Blog

Jamie on X

by Nathan Wrigley at September 18, 2024 02:00 PM under youtube

Matt: WordCamp US & Ecosystem Thinking

(This post should be read while listening to Wish by Joshua Redman. The writing is synchronized to the music reading speed.)

Contributor day just wrapped up for Portland for WordCamp US. If you ever have a chance to visit a WordCamp, I recommend it. It’s an amazing group of people brought together by this crazy idea that by working together regardless of our differences or where we came from or what school we went to we can be united by a simple yet groundbreaking idea: that software can give you more Freedom. Freedom to hack, freedom to charge, freedom to break it, freedom to do things I disagree with, freedom to experiment, freedom to be yourself, freedom expressed across the entire range of the human condition.

Open Source, once ridiculed and attacked by the professional classes, has taken over as an intellectual and moral movement. Its followers are legion within every major tech company. Yet, even now, false prophets like Meta are trying to co-opt it. Llama, its “open source” AI model, is free to use—at least until “monthly active users of the products or services made available by or for Licensee, or Licensee’s affiliates, is greater than 700 million monthly active users in the preceding calendar month.” Seriously.

Excuse me? Is that registered users? Visitors to WordPress-powered sites? (Which number in the billions.) That’s like if the US Government said you had freedom of speech until you made over 50 grand in the preceding calendar year, at which point your First Amendment rights were revoked. No! That’s not Open Source. That’s not freedom.

I believe Meta should have the right to set their terms—they’re smart business, and an amazing deal for users of Llama—but don’t pretend Llama is Open Source when it doesn’t actually increase humanity’s freedom. It’s a proprietary license, issued at Meta’s discretion and whim. If you use it, you’re effectively a vassal state of Meta.

When corporations disingenuously claim to be “open source” for marketing purposes, it’s a clear sign that Open Source is winning.

Actual Open Source licenses are the law that guarantees freedom, the bulwark against authoritarianism. But what makes Open Source work isn’t the law, it’s the ethos. It’s the social mores. It’s what I’m now calling Ecosystem Thinking: the mindset that separates any old software with an open source license from the software that’s alive, that’s humming with activity and contributions from a thousand places. 

Ecosystem Thinking has four parts:

  1. Learn
  2. Evolve
  3. Teach
  4. Nourish

Learn is about keeping ourselves in a beginner’s mind, the curiosity to always engage with new ideas and approaches.

Evolve is where we apply those learnings to our next iteration, our next version. We see how things work in the real world: it’s the natural selection of actual usage.

Teach is actually where we learn even more, because you don’t really know something until you teach it. We open source our knowledge by sharing what we’ve learned, so others can follow on the same path.

Nourish is the trickiest, and most important part: it’s where we water the garden. If you’ve done the previous three steps, you’ve been very successful; now your responsibility is to spread the fruits of your labors around the ecosystem so that everyone can succeed together. This is the philosophy behind Five For the Future, which you’re going to see us emphasize a lot more now.

That’s the ecosystem. But if it’s the yin, what’s the yang? This openness and generosity will attract parasitic entities that just want to feed off the host without giving anything back. There are companies that participate in the Learn/Evolve/Teach/Nourish loop like a FernGully rainforest, and there are those who treat Open Source simply as a resource to extract from its natural surroundings, like oil from the ground.

Compare the Five For the Future pages from Automattic and WP Engine, two companies that are roughly the same size with revenue in the ballpark of half a billion. These pledges are just a proxy and aren’t perfectly accurate, but as I write this, Automattic has 3,786 hours per week (not even counting me!), and WP Engine has 47 hours. WP Engine has good people, some of whom are listed on that page, but the company is controlled by Silver Lake, a private equity firm with $102 billion in assets under management. Silver Lake doesn’t give a dang about your Open Source ideals. It just wants a return on capital.

So it’s at this point that I ask everyone in the WordPress community to vote with your wallet. Who are you giving your money to? Someone who’s going to nourish the ecosystem, or someone who’s going to frack every bit of value out of it until it withers? Newfold, especially since its acquisition of Yoast and Yith, gives back. (I’ve asked them to consolidate their Five for the Future pages to better represent the breadth of their contributions.) So does Awesome Motive, 10up, Godaddy, Hostinger, even Google. Think about that next time it comes up to renew your hosting or domain, weigh your dollars towards companies that give back more, because you’ll get back more, too. Freedom isn’t free.

Those of us who are makers, who create the source, need to be wary of those who would take our creations and squeeze out the juice. They’re grifters who will hop onto the next fad, but we’re trying to build something big here, something long term—something that lasts for generations.

I may screw up along the way, or my health may falter, but these principles and beliefs will stand strong, because they represent the core tenet of our community: the idea that what we create together is bigger than any one person.

(Hat tip to Automattician Jordan Hillier for the great ecosystem image.)

by Matt at September 18, 2024 03:49 AM under WordPress

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:

September 30, 2024 02:30 AM
All times are UTC.