This Week in WordPress #371 - CourtneyR.dev's 2nd Brain

This Week in WordPress #371 ![rw-book-cover](https://img.youtube.com/vi/afc5kunvNT4/maxresdefault.jpg) 🔗 **Source:** [This Week in WordPress #371](https://www.youtube.com/watch?v=afc5kunvNT4) > [!note]+ Document Notes > tags: #wordpress #collaborative-editing #performance #hosting #core-development #wordpress-events #agencies > author: Nathan Wrigley > source: WP Builds > reference: https://www.youtube.com/watch?v=afc5kunvNT4 > date created: 2024-12-19 14:30 > > # 🏷️ Title: This Week in WordPress #371 - WordPress 7.0 Delayed, Collaborative Editing Performance Issues >  ## 🧰 Action Inbox - [H1] Test collaborative editing performance impact on shared hosting — before WordPress 7.0 release #performance #hosting - [H2] Evaluate core development environment tools for contributor accessibility — WP-ENV vs new solutions #core-development - [H3] Review agency pricing strategies based on State of WordPress Agency Report — combat market pressures #agencies ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [WordPress 7.0 Release Information](https://wordpress.org) - [State of WordPress Agency Report](https://adminbar.com/2024-survey) ## 📝 Summary - WordPress 7.0 release delayed from April 9th to May 20th due to collaborative editing performance issues - Collaborative editing feature generates up to 4,000 SQL queries in 2-minute window, causing hosting concerns - Hosting companies, especially shared hosting providers, face potential performance impacts - WordPress events like PressConf and Checkout Summit gaining momentum as alternatives to WordCamps - Agency survey reveals increasing challenges in WordPress business sustainability ## 📖 Main Content WordPress 7.0 was originally scheduled for release during WordCamp Asia on April 9th but was postponed after Matt Mullenweg called for a return to beta phase. The primary concern involves collaborative editing functionality that creates significant performance overhead. The feature tracks user presence, cursor position, and selection data through constant polling cycles, dramatically increasing server requests compared to traditional single-user editing. Technical analysis shows the pre-release implementation generated close to 4,000 SQL queries in a two-minute collaborative window. This represents a fundamental shift from WordPress's traditional request pattern where users work independently and send data only when saving. The new collaborative approach requires continuous data exchange between server and clients. Hosting industry impact appears severe, particularly for budget shared hosting providers operating on tight resource margins. The feature's performance requirements may force hosts to disable functionality or upgrade infrastructure, potentially increasing costs for end users. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/afc5kunvNT4?t=0) — [H1] Show introduction and panel setup - Key idea: Episode 371 with regular WordPress discussion panel - Evidence: "We're here to drone on about WordPress with the four of us" #### ⏱️ [05:30](https://youtu.be/afc5kunvNT4?t=330) — [H2] WordPress 7.0 release delay announcement - Key idea: Release postponed from April 9th to May 20th due to performance issues - Evidence: "The release was originally scheduled for April the 9th during contributor day at Word Camp Asia, but was paused in late March" #### ⏱️ [08:45](https://youtu.be/afc5kunvNT4?t=525) — [H1] Collaborative editing performance concerns - Key idea: Feature creates massive server load through constant polling - Evidence: "Pre-release implementation generated close to 4,000 SQL queries in a two-minute collaborative window" #### ⏱️ [12:20](https://youtu.be/afc5kunvNT4?t=740) — [H2] Impact on hosting providers - Key idea: Shared hosting will struggle with increased resource demands - Evidence: "Every time you move the mouse, it's sending data back to the server" #### ⏱️ [18:30](https://youtu.be/afc5kunvNT4?t=1110) — [H3] Canonical plugins concept abandoned - Key idea: WordPress moved away from lean core with canonical plugins - Evidence: "12 months ago were all talking about canonical plugins and how canonical plugins were the future" #### ⏱️ [25:15](https://youtu.be/afc5kunvNT4?t=1515) — [H2] Panel consensus on collaborative editing usage - Key idea: None of panel members plan to use collaborative editing - Evidence: "Straw pole. The four of us who will use collaborative editing the minute it becomes part of core. Hands up. No hands." #### ⏱️ [30:45](https://youtu.be/afc5kunvNT4?t=1845) — [H3] Core development environment toolkit discussion - Key idea: New tool attempts to simplify WordPress core contribution setup - Evidence: "OneMar is saying a lot of people get lost at WordPress contributor day" #### ⏱️ [38:20](https://youtu.be/afc5kunvNT4?t=2300) — [H2] WordPress events diversity with PressConf and Checkout Summit - Key idea: Alternative events providing different conversation types than WordCamps - Evidence: "Both are not work camps but WordPress centric events" #### ⏱️ [45:10](https://youtu.be/afc5kunvNT4?t=2710) — [H2] State of WordPress Agency Report findings - Key idea: Making living with WordPress becoming more challenging - Evidence: "Getting harder to make a living using WordPress. Not impossible. Certainly not impossible. But harder" #### ⏱️ [48:30](https://youtu.be/afc5kunvNT4?t=2910) — [H3] Agency market squeeze analysis - Key idea: Mid-size agencies facing pressure from both larger and smaller competitors - Evidence: "The middle has been gutted. So, if you were a midsize agency, you're finding that the larger agencies are now coming down at one level" ## 📚 References - [WordPress Make Blog](https://make.wordpress.org) - [WP-ENV Core Development Environment](https://developer.wordpress.org/block-editor/reference-guides/packages/packages-env/) - [AdminBar State of WordPress Agency Report](https://adminbar.com/2024-survey) ## 🗣️ Paraphrase - WordPress 7.0's collaborative editing feature creates too many database queries for most hosting environments to handle efficiently - Alternative WordPress events like PressConf and Checkout Summit offer more focused conversations than traditional WordCamps - WordPress agencies face increasing competition and pricing pressure from both larger and smaller competitors ## 📰 Newsletter WordPress 7.0 faces a significant delay as collaborative editing reveals performance challenges that could impact hosting providers across the ecosystem. The feature's database-intensive approach requires careful optimization before release. Meanwhile, the WordPress events landscape continues evolving with specialized conferences like PressConf and Checkout Summit offering alternatives to traditional WordCamps. These focused gatherings enable deeper technical and business conversations. For WordPress agencies, market conditions remain challenging with increased competition squeezing mid-market providers from both directions. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### WordPress - Core Performance: Profile collaborative editing queries, optimize database interactions, establish performance budgets - Core: Evaluate canonical plugin approach for collaborative editing, consider phased rollout strategy - Community: Improve contributor day onboarding, create simplified development environment setup - Hosting: Engage shared hosting providers in collaborative editing testing, establish performance guidelines #### OSPO - Performance Management: Establish metrics for acceptable resource usage in core features - Community Engagement: Facilitate hosting provider feedback channels for core development decisions #### Community - Maintainers: Support alternative event formats like PressConf model for specialized conversations - Contributors: Develop better onboarding pathways for new contributors at events ## 🧪 Hypotheses - Collaborative editing performance issues will force WordPress to adopt canonical plugin architecture - Shared hosting providers will disable collaborative editing by default upon WordPress 7.0 release - Alternative WordPress events will gain popularity over traditional WordCamps for business-focused discussions - Mid-market WordPress agencies will consolidate or pivot to specialized services to survive market pressure ### 📊 Methodology - Performance testing collaborative editing across different hosting environments and server configurations - Survey hosting providers on resource allocation policies and collaborative editing impact - Track attendance and feedback metrics for alternative WordPress events versus WordCamps ### ❓ Questions - How can WordPress balance innovation with hosting provider constraints? - What governance model should guide core feature decisions that impact infrastructure requirements? - How might collaborative editing usage patterns differ between traditional publishing and AI-assisted workflows? ### 🔮 Future Research - Long-term performance optimization strategies for real-time WordPress features - Economic impact analysis of core feature decisions on hosting ecosystem - Alternative event format effectiveness for WordPress community development ### 💡 Implications - Practice: Hosting providers need performance testing protocols for WordPress core updates - Policy: WordPress needs formal hosting provider consultation process for resource-intensive features - Security: Increased server requests create expanded attack surface requiring monitoring - Education: Contributor onboarding requires simplified technical setup processes - Funding: Performance optimization may require dedicated development resources ### 🧠 Learning Styles Assessment Reading level estimate: 12th Grade #### 👀 Visual learners - Present: Performance charts, hosting impact diagrams - Improve: Database query visualizations, server load comparisons #### 🔊 Aural learners - Present: Podcast format with expert panel discussion - Improve: Technical deep-dive audio segments #### 🗣️ Verbal learners - Present: Clear technical explanations, hosting analogies - Improve: Performance terminology glossary #### 🧩 Kinesthetic learners - Present: Setup process walkthroughs, contributor day guidance - Improve: Hands-on performance testing labs #### 🧠 Logical learners - Present: Query count data, performance metrics timelines - Improve: Decision tree for hosting resource planning #### 🧑‍🤝‍🧑 Social learners - Present: Panel discussion format, community event coverage - Improve: Collaborative problem-solving sessions #### 🧘‍♀️ Solitary learners - Present: Individual performance analysis, self-directed research - Improve: Personal hosting environment assessment tools #### 🌿 Naturalistic learners - Present: Ecosystem thinking about WordPress community - Improve: Environmental impact of increased server resources ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure in show notes - Improve: Alt text for performance charts and diagrams #### Keyboard navigation - Present: Video player keyboard controls available - Improve: Timestamped navigation shortcuts #### Contrast and readability - Present: High contrast video player interface - Improve: Transcript formatting with better visual hierarchy #### Text resizing and reflow - Present: Responsive show notes layout - Improve: Scalable performance data presentations #### Media and captions - Present: Full transcript provided - Improve: Speaker identification and technical term highlighting #### Forms and interactions - Present: Simple comment submission process - Improve: Accessible error handling for live chat ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global WordPress community perspective with Asia WordCamp coverage - Improve: More diverse hosting provider examples beyond Western markets #### Inclusive language - Present: Technical terms explained clearly - Improve: Avoid insider jargon without definition #### Neurodiversity support - Present: Timestamped sections for easy navigation - Improve: Content warnings for technical complexity levels #### Representation - Present: Diverse panel backgrounds and expertise - Improve: Include hosting provider perspectives from different regions #### Psychological safety - Present: Respectful technical disagreement modeling - Improve: Clear escalation paths for community feedback ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Performance data clearly supports hosting concern conclusions - Inductive strength: Agency survey trends indicate broader market patterns - Causal reasoning: Direct connection between feature complexity and server load - Analogical strength: Google Docs comparison illustrates collaborative editing challenges #### Fallacies - Appeal to authority: Matt Mullenweg's decision cited without questioning rationale - False dichotomy: Presenting canonical plugins vs core features as only options #### Tone of voice - Overall tone: Informal but knowledgeable, balancing technical detail with accessibility ### 🛡️ DARVO Analysis - Deny: No denial patterns observed - Attack: No attacks on accusers present - Reverse victim/offender: No victim/offender reversals noted - Emotional cues and rhetoric: Technical frustration expressed appropriately without personal attacks ## 🎯 Conclusion WordPress 7.0's collaborative editing delay highlights the complex balance between innovation and infrastructure reality. The performance issues demonstrate the need for better hosting provider consultation in core development. Meanwhile, the broader WordPress ecosystem shows signs of evolution with alternative events and increasing business challenges for agencies. The community must address both technical performance constraints and sustainable business models to maintain healthy ecosystem growth. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] Collaborative editing creates performance bottlenecks requiring infrastructure consideration > [!quote] This Week in WordPress #371 by Nathan Wrigley via WP Builds. Published 2024-04-24. Accessed 2024-12-19. > "Pre-release implementation generated close to 4,000 SQL queries in a two-minute collaborative window." Technical features requiring constant server communication fundamentally change hosting resource requirements and must be evaluated against existing infrastructure constraints. [view highlight](https://youtu.be/afc5kunvNT4?t=525#H1) #xref #articleseed ID:rw_wp7_collab_perf ### [H2] WordPress events ecosystem diversifying beyond traditional WordCamps > [!quote] This Week in WordPress #371 > "Both are not work camps but WordPress centric events." Alternative conference formats enable different conversation types and may better serve specific community segments than traditional WordCamp structure. [view highlight](https://youtu.be/afc5kunvNT4?t=2300#H2) #xref ID:rw_wp_events_alt --- ### 🔖 Atomic Split Pad (Zettel Candidates) Purpose: Promote reusable claims into Atomic notes. Split level: H4 #### [Z1] Real-time collaboration requires continuous server communication - Scope: Web applications with live collaborative features - Pointer: 12:20 timestamp discussion of mouse movement tracking - Links: [[Performance-Optimization]] [[Server-Architecture]] #### [Z2] Hosting providers operate on thin resource margins - Scope: Shared hosting business model constraints - Pointer: Tim Nash analysis of hosting economics - Links: [[Hosting-Economics]] [[WordPress-Performance]] --- ### ✏️ Fleeting Queue Purpose: Capture quick actions for Fleeting notes. - [F1] Interview Juan Mar about core development environment toolkit — understand tool positioning vs existing solutions #fleeting #inbox - [F2] Research PressConf and Checkout Summit attendance/feedback metrics — compare to WordCamp effectiveness #fleeting #inbox - [F3] Follow up on canonical plugins concept abandonment — investigate decision timeline and rationale #fleeting #inbox --- ## Full Transcript [00:29] Hey. Hey. Hey. [02:00] Hello, good morning, good afternoon, [02:03] good evening, wherever you are in the [02:05] world. It is number 371. That's what it [02:08] says, so I'll believe it. Of this week [02:10] in WordPress, um, we're here to drone on [02:13] about WordPress with the four of us, I [02:15] think, are quite good at droning on [02:17] about WordPress. Apologies, panel. That [02:20] wasn't supposed to be insulting, but it [02:21] came kind of came across like that, [02:23] didn't it? I'm very sorry. Uh, it was [02:25] supposed to be self-deprecating. That's [02:28] that's it. I'm out of here. Out of here. [02:30] Barely begun. Yeah, it's totting. Um, so [02:33] yeah, that's the plan. We talk about [02:35] WordPress rather a lot. I don't think [02:36] we're going to stray too much into other [02:38] subjects, but we've got the usual [02:40] smogers board of plugins and themes and [02:42] all of that kind of thing. Um, if you [02:44] would like to uh join us in this, feel [02:47] free to do that. Um, after the fact, you [02:49] you obviously can't comment live, but [02:51] you can comment on the blog post on [02:53] wpbuilds.com. But if you happen to get a [02:56] notification through your email and you [02:57] are watching this live, the best place [02:59] to go is is this one URL and it's [03:02] wpbuilds.comlive [03:05] like that. wpbuilds.comlive. [03:08] If you go there, then you got two [03:10] options. If you're logged into a Google [03:12] account, you can use the comment box uh [03:14] on the right uh on desktop or underneath [03:17] on mobile. But if you don't want to be [03:19] logged into a Google account, there's a [03:20] little black box on the player itself. [03:23] something like live chat is what it [03:24] says. Click on that and that's uh that's [03:27] the chat that comes through the [03:28] platform. So, you know, feel free to [03:29] click that. Um that would be great. So, [03:32] who have we got today? Well, you can see [03:35] let's go around the houses. Let's go [03:36] this way. Um it's Mark Benz again first. [03:39] How you doing, Mark? [03:41] >> I'm doing fantastic. [03:44] >> Amazing. [03:46] >> Yeah. [03:47] >> So good. So, two in the morning or [03:50] something where Mark lives. So, he's [03:52] pushing through. Uh, what time is it? [03:55] >> It is it's it's uh 6:04 a.m. [03:59] >> Yeah. [04:00] >> Yeah. [04:01] >> Yeah. Thank you. I have no words. Uh, [04:04] I'm very appreciative. Let's go with [04:06] that. So, I'll read the bio uh so that [04:08] we and you can have a small break. Have [04:10] a coffee. Mark Benzerane is the [04:12] partnerships and community lead at [04:13] MainWP where he spends his time working [04:15] with plug-in developers, agencies, and [04:16] service providers across the WordPress [04:18] ecosystem. He's been involved with [04:20] WordPress for many years and is [04:21] particularly interested in helping site [04:23] owners keep control of their own [04:24] infrastructure while still benefiting [04:26] from the broader plug-in and hosting [04:28] landscape. At MainWP, he focuses on [04:30] partnerships, community management, and [04:32] using those partnerships to help unlock [04:33] and extend what's possible with the open [04:36] source ecosystem. Outside of work, Mark [04:38] keeps busy by drinking coffee, creating [04:41] hands-on projects. He's usually [04:42] tinkering with a new idea, building [04:44] something in the workshop, experimenting [04:46] with design and graphics, or finding [04:48] excuses to get outside on his bike now [04:50] that the weather Yes, now that the [04:52] weather supports those excuses. He also [04:55] spends lots of time writing and [04:56] generally [04:58] exploring whatever interesting project [05:00] happens to grab his attention this week. [05:01] I have rediscovered my bike as well this [05:03] week, which has been quite nice over the [05:05] last couple of days. [05:08] So, thank you for joining us, Mark. [05:09] Really? Thank you for Thank you for [05:11] having me. [05:12] >> You're very welcome. [05:13] >> Always appreciate it. [05:14] >> Yeah. Well, likewise. Really appreciate [05:17] it. Thank you. And let's go clockwise, I [05:19] guess. Is that uh and we'll get to [05:21] Remus. Hello, Remus. [05:23] >> Hello, Nathan. Mark, [05:24] >> it's been a while. [05:25] >> It has. [05:26] >> How you doing? [05:27] >> Well, it you know, there's a reason for [05:28] why it's been a while because, you know, [05:30] I was I was being uh picked on in the [05:33] one four or five years ago. So, I was [05:35] like, "Yeah, we're not doing that." But [05:38] I I can only apologize if it was me. [05:40] What did I do? [05:42] But uh No, it it really I it has been a [05:45] while. I think probably several months [05:46] since you've been on and [05:47] >> Yeah. Yeah. Yeah. I I've been busy. I've [05:49] been I've been very very busy. Not Not [05:51] that I'm not busy right now, but [05:53] >> yeah, just lots of lots of moving parts, [05:56] lots of stuff going on. [05:57] >> Okay. Well, I think we're going to find [05:59] out more about that next week. I uh I [06:01] failed to spot something that Remus was [06:02] doing. [06:03] >> No, no, no, no, no. Uh anyway, here we [06:06] go. Here's the Remus bio. Remus Dere is [06:08] a WordPress performance specialist. He [06:10] co-founded Scanfully, a site health and [06:13] performance monitoring tool and runs [06:15] within WordPress, home to the guild [06:18] alongside courses, a newsletter, and a [06:20] podcast for those serious about building [06:22] better WordPress sites. He also runs [06:24] truer than North, which is a strategic [06:27] guidance service for companies in the [06:28] WordPress world for making the right [06:30] technical and ecosystem decision. So [06:33] that's Remus and on the screen if you [06:35] can see it you can see the URL for the [06:36] scanfully products scanfully.com. [06:40] Thank you for joining us. Appreciate [06:42] that. And lastly, [06:44] >> Tim Nash who always leaves his bio to [06:46] the last minute so I don't have a chance [06:48] to practice it. And uh here it goes. How [06:52] you doing first Tim? You all right? [06:53] >> I'm fine. I today was unusual. I don't [06:56] normally leave it to the last last [06:58] second. So that's true. Apologies for [07:00] the mid mediocre bio. And I I think [07:04] Remicus may have been referring to our [07:06] attempt to get him to do a rap battle [07:08] with somebody else who rather forgotten. [07:11] >> Oh yeah, that had totally gone [07:17] that via Twitter. [07:19] Wasn't it Cromwell? Wasn't it Cromwell? [07:21] We wanted you to get it. Yeah. [07:22] >> Yeah. Yeah. Yeah. Yeah. [07:24] >> And I say if you hadn't weren't watching [07:26] the episode, that could have looked much [07:29] worse than if you'd actually watched it. [07:31] >> One of one of the nice things about my [07:33] brain, and it is a nice thing, but it's [07:35] also a terrible thing, is my capacity to [07:38] forget things is truly profound. And I'd [07:42] completely forgotten about that. I [07:43] really now it all comes flooding back. [07:48] That was so much fun. I'm so sorry. [07:51] Yeah, you you were threateningly, you [07:54] know, trying to gain violence and [07:55] there's me going, "No, I meant singing. [07:57] I want them to sing." [07:59] >> I was I was trying to get Remus to beat [08:02] up Matt Croble, wasn't I? In memory. [08:04] >> Yeah, that was that was the goal was I [08:06] think it was a a two men enter, one man [08:09] leaves kind of thing. [08:10] >> I think I think truly I think we know [08:12] the outcome of that battle, but let's [08:14] not re let's not revive that whole [08:17] thing. I'm only going to make it worse. [08:20] Uh, so, [08:22] oh, this isn't going to go well, is it? [08:24] Uh, here we go. Tim Nash's biography. [08:26] Cap Oh, I see. Star Trek, right? Here we [08:29] go. Captain's log, star date 47291.6 [08:34] discovered life form. Tim Nash, a [08:36] security consultant specializing in [08:38] WordPress. He seems to be some sort of [08:40] educator. While observing him, he seems [08:42] to help developers, site owners, and [08:44] businesses navigate the hostile sectors [08:46] of the website of website security, [08:48] practical risk, and modern web [08:50] infrastructure. First contact protocols [08:52] engaged. Visit his site at tim [08:55] dash.co.uk. [08:57] That's not bad for just throwing it [08:59] together at the last minute. I quite [09:00] like that. Star Trek fans will get it [09:02] anyway. [09:05] >> Where did you Where did you come up with [09:06] the star date? Uh when I said to uh my [09:11] my favorite local AI, "Hey, uh come up [09:15] with a Star Trek themed based on a star [09:17] on a captain's log entry for me." Uh it [09:21] came up with the star date. [09:22] >> There you go. It came up with the star [09:24] date. Okay, lovely. So, there's our [09:26] panel. Um we'll be chatting about [09:28] WordPressy bits and pieces. Like I said, [09:29] if you want to join us, feel free to do [09:31] that. Drop a comment in. Oh, there's a [09:33] few people that have put a comment in. [09:34] So, here we go. One's from Tim Nash, so [09:36] I'll ignore that one. One's from Remus [09:38] Dice. So, uh, is that rude? Is it rude [09:40] to ignore your comments because you're [09:42] on the show? No, it is, isn't it? Hi [09:44] folks. Hope you're having a good week, [09:45] says Tim Nash. And Remus says, "This [09:48] week is awesome so far, but probably [09:50] have better gauge of things after this [09:52] podcast." Yeah, could easily I think we [09:54] know already how it's going to go. [09:57] Elliot Sersby just down the road from [09:59] me. Hello. Hope all is well. Reese W, [10:02] afternoon folks, and welcome back. And [10:05] Elliot Richmond, good day. WP builds and [10:07] panel. Seems we have a panel of [10:09] cyclists. Oh, nice. That's good to know. [10:12] I should explain why we've been away [10:15] from the interwebs. Firstly, I went into [10:17] hospital and had some eye things done. [10:19] So, that knocked me out for a few weeks. [10:21] And then I went to um I went to World [10:24] Camp Asia in India. And listeners to the [10:27] podcast from many years back will know [10:28] that when I started the podcast, I did [10:30] every episode with a chap called David [10:32] Warmsley. really lovely guy but I don't [10:35] know two years ago or something he moved [10:36] on from WordPress so we stopped doing [10:38] the podcast together but we very much [10:40] kept in touch and started another [10:41] podcast called the no script show um and [10:44] he lives in India and so after word camp [10:47] Asia I spent a couple of weeks um [10:49] basically abusing his hospitality [10:52] um and as him and his wife took me [10:54] around India and I've had a absolutely [10:57] fabulous time so you know no regrets [10:59] there and then I landed with a bump on [11:02] Saturday and this show kind of has [11:04] brought me back to reality. So, okay, [11:06] there we go. That's why the show hasn't [11:08] been going on, but that's why we are [11:10] back, right? Let's share the screen and [11:12] get stuck into it. Here we go. Oh, let's [11:14] forget the promotional stuff. Put your [11:16] name, put your email in that thing. [11:17] Press go. You know, we'll send you [11:19] email. Yeah. How's that? And then I did [11:21] an episode with [11:22] >> How many emails will you send, Nathan? [11:24] >> Uh, I'll send two a week. Two a week. [11:26] There's a strict no spam guarantee apart [11:28] from the spammy ones. They'll be full of [11:30] spam. Uh, but the non-spammy ones don't [11:33] have any spamming at all. Um, but yeah, [11:36] two emails a week, something like that. [11:37] And there's our archive. They're the [11:39] episodes that we've done recently. A few [11:40] of these went out whilst I was in Asia. [11:42] I scheduled them all. So, I did one with [11:43] Jamie Marsen where I debated him about [11:46] the usefulness of AI. And frankly, it [11:49] wasn't worth it. He's not a He's not a a [11:51] rival. I absolutely wiped the floor with [11:53] him. He's going to hate me for saying [11:55] that. He's going to absolutely hate me [11:58] for saying that. Um, we spent a lot of [12:00] time in Asia and carried on the debate [12:02] endlessly and both of us claimed [12:04] victory, but I'm certain that I was the [12:07] winner. I also did an episode with [12:08] Jonathan Jernigan, with Brian Gardner, [12:11] and then recently um with this chap here [12:13] who's got this plug-in called Tilbuchi. [12:16] So, go and check those episodes out. And [12:18] that's it really. Let's get stuck into [12:20] the content itself. I was very excited [12:23] heading to Word Camp Asia because [12:24] Jonathan D. Rosia uh and I did an [12:27] episode where we talked about um the [12:29] fact that WordPress 7 was going to be [12:30] released with all this fanfare at [12:33] contributor daycam Asia like this big [12:36] red button kind of event you know where [12:38] all the people gather around a big [12:39] button is here and WordPress gets [12:41] released it's a gimmick but it I think [12:43] it's quite a good gimmick quite like the [12:45] idea of mixing live events with releases [12:48] and things like that however it got [12:50] pulled uh at the last minute because of [12:53] um well we'll get into Why? In a moment, [12:55] but we have a new release date. [12:57] Hopefully, this one will be stopped to. [12:59] It's about I don't know 3 weeks from [13:01] now, something like that. May the 20th [13:03] is the uh is the upcoming release date. [13:05] Uh there isn't really much to say about [13:07] that, just that that is the date, the [13:09] new date. But um I don't know if any of [13:11] you have got more wisdom than I have [13:13] about why it was pulled. I just know it [13:16] had something to do with collaborative [13:17] editing and the fact that the um I I [13:20] guess the way that it was being handled [13:22] wasn't performant. I think it was all [13:24] handled as metadata, whereas now I think [13:26] the move is to push it into a a [13:28] specialized table for this collaborating [13:30] collaborative editing experience. So I'm [13:32] going to hand it over if any of you can [13:34] explain what the heck that was, I would [13:36] be most grateful. So over to you if you [13:38] feel you can do that. [13:42] And there's total silence. Nobody knows. [13:44] Okay, fine. Um in which case I'll just [13:47] read it from the screen. I'll read the [13:48] bits that I've highlighted. D. [13:52] Apparently, it was, let's have a look [13:55] here. D. [13:57] Here we go. The release was originally [13:59] scheduled for April the 9th during [14:00] contributor day at Word Camp Asia, but [14:02] was paused in late March after WordPress [14:04] co-founder Matt Wallenweg called for a [14:06] return to the beta phase uh to allow [14:09] more time to address, and I guess this [14:11] is the thing, a cache invalidation issue [14:14] found in real time collaboration. [14:17] um blah blah blah blah blah and there's [14:20] some more bits and pieces here but it [14:21] basically seems that there was a bit of [14:23] a snafu and if we had have gone into [14:25] live production it wouldn't have been [14:27] all that performant and anyway now the [14:30] idea really is that um there's been a [14:33] call for some of the big hosts to get [14:35] involved in testing this because unlike [14:37] other releases where it's just a release [14:40] of WordPress you know things have [14:41] changed this one really could impact you [14:43] I suppose if you're a smaller host on [14:45] budget hosting if you're a smaller host [14:47] if If you're any if you're a bigger [14:48] host, it's going to have a fundamental [14:50] screw effect on you. If you're running [14:53] shared hosting and you're to running on [14:55] a 5 10% CPU margin, you and or and [14:59] you're already running with a over [15:01] stuffing your memory supply, which is [15:03] like every host outside of a few of the [15:07] very expensive ones. Uh that you're all [15:10] going to suddenly discover that every [15:11] single WordPress website's going to have [15:13] a sudden massive impact performance if [15:15] it's on by default. which [15:18] is something that has been told [15:22] repeatedly all the way through that one [15:24] thing you can't do is have a performance [15:25] impact on this. This and you you know [15:28] you can't you don't you don't want to [15:30] centralize things into a central server [15:32] that's owned by one company and you [15:35] don't want to have performance impact at [15:37] the host level because they won't be [15:38] able to do their margins and everybody's [15:40] hosting is going to go up for a feature [15:42] that's going to be used by literally no [15:45] one. And it does feel very much like we [15:49] haven't done any testing ac across the [15:51] board. And when they started to do the [15:52] testing, it all went horribly wrong. [15:54] Right. Rant over. [15:57] >> Is it is it purely of the nature of So [15:59] in in a previous iteration of WordPress, [16:01] you know, 6.9 and before, when you start [16:05] to edit a post or a page, you you load [16:07] up the experience of the editor, [16:09] whichever editor you're using. Then you [16:10] do your stuff, not much is happening. [16:13] click save or publish or what have you [16:15] or update and then information flies [16:17] back between the host and you and that's [16:19] the moment where things start to you [16:21] know use workers and what have you. [16:23] Whereas in this collaborative editing [16:25] experience is it just more or less a [16:27] constant stream a trickle of things [16:29] backwards and forwards because on the [16:31] screen here it says awareness is the [16:33] data that tracks who else is currently [16:35] edit editing the post. So awareness is [16:37] the name that is being given to this [16:39] sort of feature. I guess uh it's [16:41] tracking their presence, cursor position [16:43] and selection and it's re and it's read [16:46] and written on every poll cycle. Now I [16:48] don't know what that poll cycle means [16:49] which is why it's becomes central as a [16:52] performance question for the next [16:54] release candidate. Um [16:55] >> so if you imagine you were you sitting [16:58] by yourself you you would write your [17:01] document and you would hit save. [17:02] >> Yeah, [17:03] >> that would send a single HTTP request. [17:06] Now, secretly actually behind the [17:08] scenes, the editor was sending other [17:10] HTTP requests, especially with Gutenberg [17:12] with the blocks. Every time you dropped [17:14] a block on it was making a HTTP request, [17:16] but generally the the big component was [17:19] hit the save button, HTTP request over, [17:22] heartbeat was going in the background [17:24] that was making some requests back. But [17:26] you could be doing most of this in [17:28] isolation and you'd be having very [17:30] little impact. Right [17:31] >> now, every time you move the mouse, [17:35] it's sending data back to the server. So [17:38] the server has and then but and if [17:40] there's two of you on the post, it's now [17:42] repeating that information back out. So [17:44] it's got to relay it to however many [17:46] people are looking. So let's get into a [17:49] wonderful world where we are [17:50] collaborating. Let's say all four of us [17:52] are collaborating and each one of us is [17:55] moving our mouse, our mice. Mes [18:01] are mice around the screen and editing [18:03] things. Now think about that how just [18:06] how many requests are suddenly hitting [18:07] this server. [18:09] >> That's absolutely fine on your VPS [18:12] running on a managed host. I I I don't [18:14] imagine your DP engines kinsters of this [18:18] world are going to have any problems for [18:20] most people. Now imagine your uh 199 a [18:25] year host. [18:28] >> Yeah. [18:28] >> Which is not atypical of what the vast [18:31] majority of people run on. Um if you [18:34] think about those shared host boxes, [18:38] they are going to have so many problems, [18:40] right? not even if they um do get brown [18:44] over the CPU and RAM constraints, they [18:46] might even hit the sheer just the sheer [18:48] number of connections that are [18:49] connecting up depending on what's [18:51] happening at any given point. And the [18:53] you know you're going to if you end up [18:55] in a scenario where you are maxing out [18:57] the transit to the server there nothing [18:59] you can do about that of if you you [19:02] either have to split the split out of [19:05] the boxes which is going to cost you [19:06] more money or say no we have to turn [19:09] that feature off. Um, and I I I'm [19:12] imagining a lot of hosts are going to [19:13] just disable this until because not [19:16] because it's wrong or not and not even [19:18] and this is no reflection on whether [19:21] it's even the right tool or the right [19:23] thing or if it should exist in the first [19:25] place. It is simply a case of a [19:27] reactionary knee-jerk reaction will be [19:29] to turn it off and investigate later. [19:32] >> Right. Right. because that's how hosts [19:35] work and that's how they have to work [19:37] because they work at scales that are [19:40] scary. Um, so yeah, this I really I was [19:45] so surprised when this turned up in [19:46] seven [19:48] gone from [19:50] >> a a a yeah, we would like to do this. [19:53] Yeah, we're going to experiment on this [19:54] to it's in seven now [19:56] >> and there just seems to have been very [19:59] little hang on can we do real world [20:01] test? You know, if you take something [20:02] like Gutenberg that took several years [20:05] of re real world tests before it even [20:07] got in to the five editor and this feels [20:10] like it accelerated at such a rate and [20:14] it the result was it gets pulled which [20:18] is [20:18] >> and I suppose the curious yeah the [20:20] curious thing here as well is that it's [20:22] not users that needed to do the tech [20:26] well they did but you know it's more the [20:28] hosting companies right because they're [20:29] the points of failure [20:31] And from this article, not I don't know [20:33] that I've highlighted these bits, but [20:34] this this is also a clarion call for [20:37] hosting companies to get involved as [20:38] well. And I know they've had feedback [20:40] from some of the usual suspects. Um, [20:43] >> it's unfortunately not going to be the [20:44] usual suspects. The usual suspects are [20:47] going to be yo going, "Yeah, we can deal [20:48] with that cuz we're the good guys in [20:51] this scenario." It's the generic [20:53] unwashed hosts, the smaller hosts who [20:56] are going to also be utterly unprepared [20:59] >> because no one's telling them this. [21:01] There's not a big campaign to let hosts [21:04] know. a call by a by Matt in one corner [21:08] of the internet hiding in a in a make [21:10] post somewhere is not and a message in [21:14] the uh hosts and on make slack in the [21:17] host section does not constitute a [21:20] campaign to to tell hosts that oh by the [21:23] way we might be turning on a feature [21:24] that might impact you. [21:26] >> Uh it's just will impact. [21:29] >> Yeah, that's a better way. Yeah. Well, I [21:32] guess the ar could argue might in that [21:34] the vast majority of sites still only [21:36] have a single user. So, while they will [21:39] be exponentially increasing the amount [21:40] of calls that one user makes, [21:42] >> but that that is I mean um [21:44] >> still going to scale mass horribly. [21:46] Yeah, I think the the [21:49] if you look at the feature itself um and [21:52] you know I I've had hundreds maybe up in [21:56] the thousands of clients and build sites [21:58] for I have maybe a handful for whom this [22:01] would be fully practical. Um that said [22:06] um uh Matt Mullen highlighted a case I [22:10] think it was on X somewhere at some [22:12] point where he essentially said this is [22:15] a feature that is particularly uh well [22:18] suited for AI to be the collaborative uh [22:22] second I remember that yeah [22:24] >> and I hadn't considered that position so [22:27] if we take that in and the rise of AI as [22:30] we see it uh it it will be used more [22:32] than the 3 4% uh that it's currently [22:35] claimed. But um [22:39] your recap and as to the the whole [22:41] impact, Tim, that is very spot on. It's [22:43] just we're going to hear the most amount [22:46] of [ __ ] from the most amount of shitty [22:49] hosting companies when this is going to [22:51] be pushed as is. [22:52] >> I mean, on on the plus side, where it [22:54] was before, I think that last paragraph [22:57] that you is that's not highlighted, but [22:58] it's on the screen. Uh, the pre-release [23:01] implementation generated close to 4,000 [23:03] SQL queries in a twominute collaborative [23:05] window. [23:06] >> Yeah. [23:08] >> Yeah. No, no. Databases don't like that. [23:12] >> No. [23:13] >> Okay. [23:14] >> I would go as far as saying they hate [23:16] it. [23:16] >> Yeah. [23:17] >> Okay. Okay. So, this then this then [23:20] raises a question of and to to Tim's [23:22] point earlier, I obviously I do this [23:25] show weekly. This has been coming and [23:27] coming and coming, but for the longest [23:29] period of time, everybody was talking [23:31] about it as a nice to have kind of, oh, [23:33] it's off in the distance somewhere. And [23:35] then I think you're right, Tim, it [23:37] suddenly was going to be in core like [23:40] two months ago or something like that. [23:42] It suddenly got parcled up as a yeah, [23:44] yeah, we're going to we're going to run [23:45] this as part of core. And it is kind of [23:48] surprising in a way, isn't it? That it [23:50] never that this particular aspect of it, [23:53] you know, that the burden on the server, [23:55] which I think everybody that that [23:57] probably has dealt with this probably [23:58] knew in the background that somehow it [24:00] didn't it didn't get surfaced and [24:02] punting. [24:03] >> I think every single naysayer of this [24:06] would was would pointing it out. [24:09] >> Yeah. [24:10] We're talking like years ago when this [24:12] was first mentioned. It was like no [24:14] because the only way you can do this is [24:15] centralizing it or burning or burn a [24:18] server running it. [24:19] >> Yeah. [24:19] >> And it seems like they've fixed a lot of [24:22] it to get it somewhere performant, but [24:24] that's still not the same as performant. [24:27] >> But uh what's really I this this will be [24:30] a rantiness is 12 months ago were all [24:32] talking about canonical plugins and how [24:34] canonical plugins were the future and we [24:36] should definitely talk about canonical [24:37] plugins and canonical plug [24:39] Where'd that go? [24:41] >> You are you meaning this feature as a [24:43] canonical plug-in? [24:44] >> Well, the idea was that if we were going [24:46] to have that we were going to have [24:47] WordPress core was going to be really [24:49] lean and light and you know there were [24:51] certain features that we might need that [24:53] we should that but they should be uh [24:57] given as a canonical plugin. So they're [24:58] still owned by WordPress. They're still [25:01] maintained to the same high standards, [25:02] the same release cadence, but wouldn't [25:05] wouldn't take up space in the very lean [25:08] and light WordPress of the future. And [25:11] uh roll on nine months and we've got an [25:14] what an MCP servery thing coming in. Uh [25:17] an agent uh a whole new AI agent set [25:21] thing that's in there with meaning for [25:23] the first time ever, we're going to have [25:24] credentials now in databases and this [25:27] all in one place. It feels like who [25:30] where at some point that that idea of [25:32] canonical plugins just got thrown out [25:34] the window. [25:36] >> Again, that's not even a criticism of [25:38] whether it's good or bad. It's just like [25:41] >> we didn't even last 9 months. [25:44] >> Yeah. [25:44] >> That that because that announce I think [25:46] that announcement might have been in [25:47] Asia when they were talking about [25:49] canonical plugins last year, [25:51] >> but it it really was. So, it might be 12 [25:54] months. It might not be nine months [25:56] since they were talking about the future [25:57] is all canonical. Well, that's right. [25:59] And this now that you've mentioned it, [26:01] it's dredged up my memory, which is [26:04] exactly that that this would be the [26:05] canonical plugins would be like this [26:07] repository of things which could have [26:10] been in core would get the same [26:12] treatment as if it were core in terms of [26:14] security updates and things like that, [26:16] but it was more a toggable set of things [26:18] if you like. You know, I don't need [26:20] collaborative editing, so we'll switch [26:21] that off or at least never install it. [26:24] You know, that's Yeah, that's [26:26] interesting. And I don't know if it was [26:27] you, Tim, or Remus in in their little [26:31] bit said that nobody will ever use it. I [26:34] I only really interact with WordPress [26:36] websites which I run nowadays. So I [26:38] obviously that tells you everything. I [26:40] will never use collaborative editing in [26:42] WordPress in the with how I've got it [26:45] set up at the moment. But I'm imagining [26:47] that some of the bigger players out [26:49] there, you know, the tech crunches and [26:50] the, you know, the some of the big [26:52] publishing houses that are using it, [26:54] maybe that would be a nice feature for [26:56] them to have because, you know, their [26:57] editorial team is messily trying to [26:59] figure things out on Google Docs and [27:00] then copy and paste whatever that [27:02] workflow looks like. Um, but yeah, it [27:06] kind of everybody else gets to be the [27:08] collateral damage because those small [27:10] amount of websites use it. Um, yeah. [27:14] Okay. Straw pole. [27:16] The four of us who will use [27:18] collaborative editing the minute it [27:20] becomes part of core. Hands up. No [27:24] hands. Interesting. Okay. And the idea [27:28] of it maybe being used for with an AI [27:30] attached to it is interesting, but you [27:33] if you're use your AI is having to use [27:36] the good the direct post editor [27:38] interface to drive everything, then this [27:42] that's probably not the right approach. [27:44] So really what you're saying is that the [27:46] collaborative AI the collaborative [27:48] component would be to render what the AI [27:51] is managing to get in from an external [27:53] endpoint coming in. [27:56] Uh [27:56] >> I think that was tied up with notes, [27:58] wasn't it? This the sort of sidebar of [28:01] uh like we have in Google Docs with [28:02] comments. I think they're called notes [28:04] in the new the latest iterations of [28:06] WordPress. And you would interact in [28:08] that sidebar on the right if you like. [28:10] And then the output would then get put [28:11] into the the block editor which then [28:14] obviously in real time you could adapt [28:16] and amend as it was typing it out. So [28:18] gosh. Okay. Anyway, the story there was [28:21] that WordPress 7 got punted. Um and [28:24] obviously that is a fairly big uh punt. [28:27] Matt Mulleng made the decision to punt [28:29] it and it sounds Tim from everything [28:31] that you've said as if that was the [28:32] right decision because there could have [28:33] been some sort of systemic collapse on [28:36] >> I wouldn't I wouldn't I'm not going to [28:38] say that I would um put money on it but [28:40] I wouldn't be shocked if on the the come [28:44] the next release it actually does get [28:46] that this gets ejected out and that they [28:48] go actually we've talked to people [28:51] we're going to save face we're going to [28:53] throw this as a a collab we're going to [28:54] put this in a plug-in territory for a [28:56] little it, get more feedback, get it [28:58] running probably and that's absolutely [29:01] fine thing to do and I think I would be [29:05] >> uh much more uh on board with it coming [29:08] into core once it's been through that [29:10] sort of release phase [29:12] >> and also I think I'd have a lot more [29:15] respect for people who people who are [29:17] brave enough to say actually yeah we [29:19] need to punt this and we we we we we [29:21] can't we shouldn't be slowing things [29:22] down we need to punt this and get this [29:24] we can come back to [29:26] load of respect for people doing that [29:28] because it's not easy to do especially [29:29] when your boss has made it the most [29:31] important thing ever for him. [29:36] >> The um the other thing I suppose is the [29:38] canvas that you're working on like [29:39] Google Docs it's it's a plain white [29:42] sheet isn't it? You know you've got [29:43] various functions and you know you can [29:46] bold things and italicize things and [29:48] what have you but it's really [29:49] constrained and if you open up one of [29:50] their spreadsheets again it's fairly [29:52] constrained in what you can do. [29:54] WordPress has this aspiration. Well, [29:56] there's just like a trillion different [29:58] things that you can do with WordPress. [29:59] Like, does does the does this [30:01] collaborative layer start to be involved [30:03] in theming? You know, can you can you [30:06] collaborate on the the theming side of [30:09] WordPress and things like that? [30:11] >> I don't know. Um, [30:13] >> anyway, there you go. [30:14] >> Yeah. But that then of course makes it [30:16] all the more complicated. Whereas the [30:18] Google I mean, God knows how much money [30:21] Google spend on their servers each year. [30:23] Can you imagine getting two people and [30:25] they collaboratively can edit the pallet [30:28] section? [30:29] >> I want it pink. I want it green. I want [30:30] it pink. I want a green. Yeah. Not this [30:33] font. No, we're not having that font. [30:35] Yeah. Okay. Uh right. Okay. Okay. So, [30:37] there we go. There's some um there's [30:39] some thoughts on that. We've had a few [30:40] comments come in. Glad to have you back, [30:42] says uh Kev Clark. Hello, Kev. Nice to [30:44] have you with us. [30:46] >> Um Remas made a comment. Oh, we were [30:48] talking about uh bikes. There you go. [30:50] Yeah, I was talking about a push bike, [30:52] which I presumed is what they were [30:54] talking about. Patricia says, "Hello." [30:56] Um, I'm guessing this is Matt. Matt [30:57] Maderos. Oh, you got a nice new icon, [30:59] Matt. Uh, how many speed limits did Rem [31:01] Remus break to get back to do this [31:03] podcast? I don't know. Where was he? If [31:05] you Oh, in uh in Cloud Press. Is that [31:09] what [31:09] >> on Saturday morning? I was at Checkout [31:12] Summit in Palmo, Sicily, Italy. [31:15] >> Okay. Driving. [31:17] >> Driving. [31:18] >> When was that? You were in Palmo [31:21] >> Saturday morning. [31:22] >> And how many miles is that that you had [31:23] to achieve to get back to the [31:24] Netherlands? [31:25] >> I don't know about freedom units, but [31:26] it's 2600 kilometers. [31:28] >> Okay. Yeah, that [31:31] Yeah. Was there any speeding? I know [31:34] you're there's quite a lot in Germany. I [31:36] guess you can [31:37] >> Let's just say I really behaved in [31:38] Switzerland, which is what [31:41] >> which which is what one guy [31:42] >> This is why he's on the podcast today. [31:45] >> Yeah. Um, and Elliot's rebotted with at [31:48] least Italy has a majority of straight [31:50] roads. [31:51] >> It was it Italy was uh very smooth, I [31:53] would I'll have to say. Um, [31:55] >> oh, I love driving around in Italy, [31:58] especially coastal roads. There's so [32:00] much fun. Oh, boy. [32:01] >> I didn't do much of that, but I I did [32:03] still have fun. So, yeah. [32:04] >> Can you just tell us, Remas, I know that [32:06] this isn't in the the show notes or [32:08] anything like that, but you've been to [32:10] two events recently, haven't you? We [32:11] went to Prescom in [32:13] >> I want to say Phoenix, but it's not [32:15] Phoenix, is it? It's [32:16] >> Tempe in the greater Phoenix area. Yes. [32:19] >> Yeah. And also um the one that you just [32:21] mentioned, Checkout Summit. Do you feel [32:23] willing to just give us a quick [32:25] appraisal of what the heck that was and [32:27] what they were like and what you enjoyed [32:28] and whatnot. [32:30] >> So both are not work camps but WordPress [32:33] centric events. Um, Presconf is a [32:37] gathering of people [32:40] uh more on the executive slash uh makers [32:45] and movers type uh uh corner of of [32:49] WordPress people I would say. Um [32:52] >> very different types of conversations [32:54] and and presentations. Um but incredibly [32:58] valuable for for anyone really vested [33:02] and interested in the WordPress and the [33:04] state of it and the future of it to be [33:06] uh to be at that event. Uh press conf I [33:10] I highly recommend anyone who's serious [33:12] about WordPress to at least visit once. [33:15] It'll make you want to visit a second [33:16] time because [33:17] >> nice [33:18] >> not not just the presentations but or [33:20] the vibe of the event itself but just [33:21] the conversations and who who are there. [33:24] Uh it's it's um it's it's it's a good [33:27] place to have those types of [33:29] conversations which you may occasionally [33:32] have at a work camp but uh it's quite [33:34] different if the whole event is around [33:36] those types of conversations which I [33:37] mean [33:38] >> you know um you know how it is there [33:41] there's an environment that uh there are [33:44] particular environments that open up [33:45] different types of conversations that [33:46] are to have so that's press conf okay [33:49] >> um checkout summed is uh WooCommerce [33:53] related ated WooCommercecentric and it's [33:55] it's roughly the same type of crowd but [33:58] then Woo Commerce. Uh it's also [34:00] different conversations. It's also [34:03] incredibly good to have woo people in [34:06] the room. Um [34:08] most notably uh James Kemp and Brian [34:10] Cords. [34:11] >> Okay. [34:12] >> Um [34:14] uh three things I think have been [34:16] mentioned are we should really fix this [34:18] and on the go James is processing them. [34:21] So, we were jokingly saying there's [34:23] going to be three uh um hot fixes being [34:27] released uh on Woo, but the whole point [34:30] is uh it's good to understand there's [34:33] many players um very active in the [34:37] WooCommerce ecosphere that are not doing [34:40] more than talking via text essentially, [34:42] right? So when you meet in person, you [34:45] have longer and better and deeper [34:47] conversations. And it's the type of [34:48] conversations we need to have if we're [34:51] >> if we're to move this community to the [34:53] next level. Uh whether that's WordPress [34:55] or WooCommerce, both both apply. Um [34:58] Checkout Summit was I mean it's it's in [35:01] Italy. Uh it's in Sicily specific, [35:04] right? [35:04] >> Yeah. Palmo, [35:05] >> right on the beach, more or less. [35:07] >> No, no, literally on the beach. [35:08] >> Yeah. Yeah. It's a stones throw away. [35:11] We're looking out at over the the sea as [35:14] we're having um breakfast and dinner. Um [35:19] Rodulfo did a wonderful job as a single [35:22] organizer organizing that event and um [35:27] he just brought the right type of crowd [35:30] in one room. U [35:31] >> and again it's Italy. I I I I I this is [35:35] not an exaggeration. We had a um [35:41] just just essentially dinner at a [35:43] pizzeria nearby. Like literally nearby [35:46] between us and the beach. So super [35:48] close. Uh and I I have had the best [35:51] pizza in my life. [35:52] >> Yes. [35:53] >> Randomly. [35:54] >> Yeah. [35:55] >> And I wasn't the only [35:56] >> Italians don't do bad food. That's not [35:58] an option, is it? They just do not allow [36:00] it. and the the the the vibe of the [36:03] event matched that uh feeling of the [36:06] best pizza. Like there's a lot of lot of [36:09] lots of things came together. Uh [36:11] conversations were good spin-offs for [36:14] sorry presentations were good spin-offs [36:16] for conversations. Uh all that sort of [36:18] stuff. So yeah, um if you haven't been [36:21] you you should feel FOMO. [36:23] They they were both were really good [36:25] events and we should have many more of [36:28] these nonwork camp types of events. [36:30] >> Do you know if Rulo is planning on doing [36:33] Check Out Summit again? [36:34] >> He will. In fact, uh the first version [36:36] of what he's done just now is uh [36:39] checkoutsummit reloaded which is an [36:41] offline version of this. So check out [36:44] checkoutsummit.com and there's more [36:46] information on that. Um, but yes, uh, [36:49] all all signs are pointing into the [36:50] direction that this will be a repeat. [36:52] >> Yeah, I had quite a few conversations [36:54] with him in the run-up to it. And the [36:56] the bit that I took away from it was how [36:57] incredibly seriously he was taking it [36:59] all. I don't mean that in a negative. I [37:00] just meant that he was he appeared to be [37:02] sweating every detail. Um, and being [37:05] concerned in the nuts and the bolts of [37:07] it all as opposed to being sort of hands [37:10] off and paying for people to organize [37:11] everything. It felt like he was the [37:13] decision maker here, there, and [37:14] everywhere, which [37:15] >> Yep. Yeah. Uh, which could be a [37:16] heartache, but he seemed to be embracing [37:18] it. [37:19] >> Um, [37:19] >> can I comment on Elliot's uh comment? [37:22] >> Yeah. Yeah. Okay. Best Oh, sorry. Sorry, [37:24] Elliot. There's It's best pizza in [37:29] >> uh Elliot, you're going to have to [37:31] believe me as as a connoisseur of pizzas [37:33] and Italians literally saying the same [37:36] thing that this was absolutely the best [37:38] pizza I've ever had and they have ever [37:40] had. [37:41] >> Do you know about Elliot's side gig? [37:43] >> Yeah. Yeah. Yeah. Yeah. [37:44] We talked about it. [37:46] >> Uh Elliot, I feel like a trip to um to [37:49] check out Summit next year is going to [37:50] be on. You can have some sort of pizza [37:52] bake off. [37:53] >> So now I was going to say now we need [37:55] two ovens. [37:56] >> Yeah, [37:58] >> we could do some sort of collaborative [38:01] >> rap battles with this. We're on to pizza [38:04] wars with Elliot. This is [38:06] >> so for the record, I'm not about wars [38:09] and fighting, Tim. [38:10] >> I'm a lover, not a fighter. No, no, no. [38:12] I'm justine. [38:13] >> I I think Food Wars is about the point [38:15] where I'm quite I'm quite keen to get [38:17] >> it. [38:19] That's until someone mentions pineapple [38:21] and then that's a whole [38:23] >> You had to ruin things, Mark. [38:26] >> Um, okay. So, he now wants to know what [38:28] the restaurant's called. [38:29] >> Uh, I can find it somewhere. [38:31] >> Okay. He's going to Google it for you [38:32] and have a little look, Elliot. That's [38:34] that's great. Uh, so there we go. We [38:36] have a battle set up 12 months from now [38:38] in Palmo. Elliot's going to rock up with [38:40] all of his gear. we can see who does in [38:42] fact do uh the best bits. That's [38:46] brilliant. That's so much less [38:47] aggressive than the uh the previous [38:49] thing between Matt and Remus. Okay. All [38:51] right. Thank you for that. There are two [38:53] two sort of events that we haven't [38:54] really mentioned much on this show. Um [38:58] yeah, there you go. I see a pizza speed [39:00] builder coming along. Pizza press. [39:05] Okay, so the comments are just going to [39:06] be about pizzas from now on. I can tell. [39:09] Right, let's put this screen back up and [39:10] see where we got to next. Um, okay. This [39:12] is a sort of word camp sort of thing. It [39:15] may have may not be of interest to you, [39:17] but I don't know if you I I can't say [39:18] that I've experienced this because I'm [39:20] not a developer, but if you have shown [39:22] up to a WordPress event uh in the past [39:25] and let's say this was your first time [39:27] and you don't have your machine set up, [39:28] perhaps you had this idea that you turn [39:30] up to contrib [39:33] and 10 minutes from sitting down you'd [39:34] be fruitfully engaged in um part of the [39:37] WordPress project. Well, not apparently. [39:40] That's not how it works because um [39:42] allegedly uh OneMar is saying a lot of [39:45] people get lost at WordPress uh [39:48] contributor day. So much so that people [39:50] actually just sort of leave halfway [39:52] through the setup of their machines um [39:55] because they're just I guess just a bit [39:56] weary of it. They figure out that [39:58] they're not going to achieve anything [39:59] just because the whole process of [40:01] getting your Mac or Windows machine or [40:03] whatever it is setups a bit of a bit of [40:05] an ache. And uh so Wanmar has decided to [40:09] take this on and he has built the core [40:11] dev environment toolkit which is let's [40:14] just call it a one-click install of [40:16] everything that you need in order to be [40:18] up and running. I'm not sure uh how [40:22] effective it is. One m maybe I'll grab [40:24] him on a podcast or something like that. [40:26] But I just thought this was quite an [40:27] interesting little project. There's some [40:29] uh you know there's some videos about [40:30] how it all works and Matt jumped into [40:32] the comments and said awesome. He'd like [40:34] to see if he can get it sort of [40:36] torrented around the room so that if one [40:38] person's got it correctly set up, [40:40] everybody in the room can just sort of [40:42] leech off their correct setup and get [40:44] going. Um, not really a story there, but [40:47] I'll drop that one in if anybody wants [40:49] to comment. Now is the moment, but if [40:51] not, [40:51] >> it's weird. We already have [40:55] WordPress core environment dev set up. [40:58] >> Okay, I didn't know that. Uh so you've [41:00] got things like JP hyphen EMV which is [41:03] the worst name possible for a local [41:05] development environment agency but it's [41:08] basically a oneclick you get going and [41:11] you can have either it you can you can [41:14] go you can drop it into any if you into [41:16] a folder that has a plugin or a theme [41:18] and you can just literally type- enm [41:21] start I think it's start and it will [41:24] load up a web load up that plugin for [41:26] you set up but if you just want to do [41:28] something C with core you just literally [41:30] I think it's WPMV core and off it goes [41:33] and it gets you all the latest core [41:35] setups. It was built originally for [41:37] working with the uh Gutenberg stuff. So [41:41] it's it was managed I think initially by [41:43] the theme team. So this feels like we're [41:46] >> just doing something again. This just is [41:49] looks more like it's just a wrapper for [41:51] Playground, which is a terrible place to [41:53] be doing core tickets, I would have [41:56] thought, because [41:56] >> Tell me why. [41:57] >> Playground's awesome. Playground's [41:59] amazing. Playground is not a P proper [42:01] PHP install of your WordPress site. [42:03] >> Playground has interesting bugs, [42:06] >> right? [42:06] >> Because it doesn't behave quite the [42:08] same. It behaves mostly the same. Um, [42:11] >> I wonder why I wonder why Juan Mars done [42:13] it. That's so that's definitely [42:14] >> I guess because one of the key things he [42:16] has on there is it doesn't have git, it [42:18] doesn't have mpm and it doesn't have [42:20] docker. And uh the problem with this is [42:24] that to do serious core development [42:26] sadly [42:27] >> you need to have some sort of git svn [42:29] access you unfortunately need to have [42:33] npm because we've we've become a [42:36] javascript first CMS for a humongous [42:39] part of it. Uh so you need all the [42:42] things he doesn't want you to have but [42:45] they are all utter barriers. [42:47] >> So interestingly in the post he does [42:49] reference core committers doesn't he? So [42:52] he says here before writing a single [42:53] line of code a first-time WordPress core [42:55] contributor typically and then on and [42:57] on. [42:58] >> Uh so would there be any utility in this [43:01] for somebody that was I don't know just [43:03] sort of dabbling around and wanted to [43:04] see what a contributor day felt like? [43:07] Probably not. Right. Okay. [43:09] Now, [43:10] >> yeah, I mean, it's it's it's basically [43:11] he's wrapped playground, which is great [43:13] if you want to have a a a a not quite [43:18] like for like, but close to like setup. [43:21] >> But then that's exactly what you could [43:24] do. If you're going to do that, you [43:26] could argue, well, shouldn't you use is [43:27] it Studio by WordPress.com that uses [43:30] Playground? [43:31] >> Yeah, Studio [43:32] >> or or Playground. Uh yeah, these are all [43:35] available to you. So it feels like we've [43:38] built yet another tool, [43:39] >> but no, I feel like I'm I'm being really [43:42] mean on people. I don't mean it. I I [43:45] people are doing things like this. [43:46] >> No, no. At the same time, feels left, [43:49] right hand, left and right hand. What [43:50] would be awesome is that we saw [43:53] development along the lines of DPMV with [43:56] a pretty interface on it. Okay. [43:58] >> For people who might be scared of using [44:00] the terminal, that would be awesome. [44:02] That doesn't seem to be what this is. I [44:04] will get in touch with Wanmar um and see [44:08] um if he's willing to come on a podcast [44:10] and explain what the uh what the the [44:12] core focus of that was because that's [44:14] does seem curious, doesn't it? Um if [44:16] you're lurking anywhere one, let us [44:18] know. Uh one click, are you sure? No. Uh [44:21] I'm not sure. Um Mark, sorry Mark. Uh is [44:26] that Mark Wilkinson? I think it is. Uh [44:29] D. Also, just as an aside, uh it even [44:32] though it says it doesn't use npm, it [44:33] literally says as a second thing on its [44:36] figures, what does it do? It clones a [44:39] clones, so presumably it's using git and [44:41] then runs npm install. So, at the [44:43] minimum, it seems to be installing [44:46] >> both git and npm onto your server, which [44:49] means it's putting node on to your your [44:51] computer. [44:53] >> At this point, if you've got a previous [44:54] copy of node, you're probably having [44:56] conflicts. It's probably all going to [44:58] break. And now you've got a bunch of [45:00] people getting angry at poor one for for [45:03] breaking their computers set up. [45:05] >> So Mark, I I was just taking that from [45:08] this line here where it says you install [45:09] it, choose a directory for WordPress [45:11] hyphen develop, click a button, and you [45:14] have. So that was why I went for that [45:15] one. [45:16] >> I I reckon local setup [45:18] >> Yeah. [45:18] >> tools is one of the hardest things to [45:21] get right. [45:22] >> Yeah. Yeah. Yeah. Yeah, [45:25] basically when we when we had Zam WAMP [45:27] and ZAMP and all XAMP and all of those, [45:30] >> they might have been the pinnacle of [45:32] usability sheerely because they did they [45:35] isolated enough of it away but just sort [45:37] of seemed to work. [45:39] >> Yeah. [45:39] >> And yeah, getting local dev tools to to [45:42] consistently work and not be a tech [45:44] support nightmare. I have so much [45:46] respect for people who try to do this. [45:49] Uh so I have respect for the project. [45:52] just think it would be great if we could [45:54] if it was a bit more coordinated. [45:56] >> Right. And also not an overlapping. [45:57] Yeah. Yeah. Yeah. That's [45:58] >> we can overlap. It just needs to overlap [46:00] in a way that is complimentary. [46:02] >> Right. Right. Right. Okay. Well, like I [46:04] said, I'll get in touch with one and [46:05] we'll see if we can get him on the show. [46:07] Uh Cameron Cameron Jones, he's in the [46:09] UK. Good afternoon from a surprisingly [46:11] sunny Brighton. It is always sunny in [46:13] Brighton. Cameron, I lived there for [46:15] many years and it never stopped. It was [46:17] relentless. and uh WWP is [46:21] I'll just move on. Uh it wasn't that [46:25] funny, but thank you Mark Westgard. I [46:27] guess that was you. [46:29] Appreciate it. Okay, we've done two of [46:31] the myriad articles. So, we need to burn [46:34] through the next one. I'm going to miss [46:35] that one out because we just don't have [46:36] time for [46:38] maybe I won't. Just very quickly, this [46:40] this appeared on Word uh the [46:42] makewordpress.org. It's kind of related [46:43] to what was talking about. Contributing [46:46] is hard, especially if you're new. And [46:48] so, there's a piece written by Velder, [46:51] uh, which was came out a couple of days [46:53] ago, 23rd of April. It's called Help [46:55] Others Contribute to WordPress. And it's [46:57] it's not the technical side of getting [47:00] set up. It's more the sort of, you know, [47:01] how do we make it accessible to other [47:03] people? Um, in terms of walking things [47:05] through and giving people issues that [47:08] they can immediately grab hold of like a [47:11] menu, if you like, of here's a bunch of [47:12] stuff which can be achieved in a day. [47:15] here's what you need to do, here's how [47:16] to do it, blah blah blah, that kind of [47:18] thing. So, go and have a quick look at [47:20] that one as well. And there's this idea [47:21] of pathways as well, which is kind of [47:24] scaffolding your contribution during [47:26] those days. It feels like um those [47:29] contributor days are I don't know [47:32] they're getting thin on the ground in [47:33] places like Word Camp US and Word Camp [47:36] uh EU, Word Camp Europe, but man, there [47:40] were so many people at the contributor [47:42] day at Word Camp Asia. Like I'm going to [47:45] say plural thousands. I don't know if it [47:48] was that many, but that [47:49] >> there were 2,200 in total at the [47:51] >> in the in the contrib. [47:53] >> No, at the event in total. [47:55] >> Okay. And I reckon most of them were at [47:57] the contra. It certainly felt that way. [47:59] The biggest room I've ever been in in my [48:02] life. I mean, it was truly enormous that [48:05] room. It was like honestly the size of a [48:08] football pitch. Um, and it was basically [48:11] full of people contributing. So, that [48:14] excitement is definitely still uh in [48:17] that part of the world, which was kind [48:18] of interesting. So, I don't know, maybe [48:20] these things are not so much of an issue [48:22] over there, but there's a piece that you [48:24] can read. Um, just a bit of a hat tip [48:26] really to uh an McCarthy. She wrote this [48:29] piece. It really it's just spelling [48:31] who's going to be on the 2027 theme [48:34] team. So, that's all there is there [48:37] really, but I just thought I'd mention [48:38] it. Um, and then where did we go to [48:40] next? Uh Kyle Kyle from the admin bar [48:45] every year does this state of the [48:47] WordPress agency report or at least he's [48:50] been doing it I don't know three four [48:52] years something like that. Um where he [48:54] goes into what what it's like basically [48:56] to be somebody that's employed building [48:59] websites. So you know plug-in developer [49:02] agency owner I think more agency owner [49:04] freelancer kind of thing. Um, in a [49:07] normal world, we probably would have [49:08] spent quite a while going through all of [49:10] this, but really, I think what I'm just [49:12] going to say is go and check it out. Uh, [49:15] it's the adminbar.com2026- [49:20] survey. Um, and what the takeaway is [49:24] really, I suppose if you were to distill [49:26] it into one line, it's getting harder to [49:29] make a living using WordPress. Not [49:32] impossible. Certainly not impossible. [49:35] um but harder and it seems like people [49:38] that have been doing it for a while seem [49:41] to do better than people that are coming [49:42] into it for the first time which you [49:44] know uh did anybody have a comment on [49:47] that? Did anybody read a bit which I [49:48] thought was worth drilling down into. [49:51] >> I read I read through it and I found it [49:53] actually a pretty fascinating article. [49:56] Um and it's it's interesting I it's [50:00] interesting that um personal burnout [50:03] ended up as high as it did. I didn't [50:05] expect it quite up as high as it is, but [50:07] it's number three on the reasons that uh [50:10] that the agencies are being held back. [50:14] And then the the uh client management [50:16] and scope is at the very bottom, which [50:18] also surprised me. Uh but of course, I [50:21] don't do a ton of agency work, so what [50:23] do I know? But um it it is different [50:26] than I would have expected it to be. Um [50:29] I and and of course he attributes the [50:32] burnout to basically underpricing [50:36] uh your product, which makes perfect [50:38] sense. If you're not making if you're [50:40] working extra hard and you're making [50:42] less money, you know, then then [50:45] obviously you're going to get burned [50:46] out. If you're working 24 hours a day [50:48] and making two bucks a week, um you're [50:50] going to get burned out. [50:52] >> I know that you collaborate with a lot [50:54] of people over at MainWP. Do you [50:55] collaborate quite a bit with the admin [50:57] bar? because it feels like the stuff [50:58] that they're doing over there or at [51:00] least particularly this like really fits [51:03] well with what you do as a business. You [51:05] know, the data that they're drawing out [51:07] here would be really interesting to your [51:09] your audience, I'm guessing. Mark, [51:11] >> I I definitely [51:14] uh read pretty much everything that they [51:17] put out at the admin bar. Um and I think [51:21] uh Kyle has some uh really good [51:24] insights. we have interacted but we [51:27] haven't really done a lot of [51:28] collaboration now. Uh I I I wouldn't say [51:31] that but uh okay [51:33] >> but I I really did appreciate this [51:35] article though. [51:37] >> Um it's basically you know it's like [51:40] lots of chart if you can't if you're not [51:41] watching this and you're listening to [51:43] it. It's um it's you kind of got to read [51:45] it. There's lots of different charts [51:46] drilling down into different bits of [51:48] business like burnout, like how much do [51:50] people make, how big are teams, um what [51:53] kind of things do they sell, how much do [51:54] they charge for things and all of that. [51:56] And you know, there's a I don't know 30 [51:59] something data points here. [52:01] >> So, um you can go and draw your own [52:02] conclusions. Well, and of course some of [52:04] some of the things you have to take with [52:06] a grain of salt is like how much money [52:07] they're making because different parts [52:09] of the world obviously you know a dollar [52:13] or whatever is going to go a lot further [52:15] than others. So um certain things you [52:17] can only take into consideration so much [52:20] but um but it is really fascinating data [52:25] >> and beautifully presented like [52:26] everything [52:27] >> and very beautifully very beautifully [52:28] presented. [52:29] >> Yeah. [52:31] say purely anecdotally from my own [52:34] because most a lot of my clients are [52:35] agencies. So I I get to sort of chat [52:39] through them and the shift over the last [52:42] couple of years has very much been the [52:44] middle has been gutted. So, if you were [52:46] a midsize agency, [52:49] uh you're finding that the larger [52:51] agencies or the more which would have [52:53] traditionally been the more expensive [52:54] agencies are now coming down at one [52:57] level to come and try and poach your top [52:59] end of your client base. [53:01] >> Oh, [53:01] >> meanwhile, the lower level, the agencies [53:04] that are tending to be much cheaper are [53:07] coming up and taking your lower level, [53:10] leaving you with very few pickings left. [53:13] And so you end up in a scenario where [53:14] you feel like you have to compete with [53:16] one or the other which then shifts you [53:18] one way or the other and too many people [53:22] seem to not recognize their own value [53:24] and therefore seem to be shifting [53:27] downwards instead of upwards that chain. [53:29] So they'll reduce their prices or [53:31] they'll try and compete with those lower [53:33] value propositions which I don't know I [53:37] feel like I I vaguely remember a [53:40] business course where they told me not [53:41] to do that. [53:44] I'd like to add something to that [53:46] because I I think in in in for the most [53:48] part you're spot on Tim. Um but what I [53:52] also see as a as a mix into that is [53:57] >> we've had a very very long period where [54:01] any type of relatively serious agency [54:04] could get work. There was plenty of work [54:06] to go around. [54:08] uh we have entered a phase where what [54:11] you're saying is happening [54:14] as well as [54:16] specific agencies that specialize in uh [54:20] let's call it two or three things are [54:23] doing much better than those who have [54:24] never uh absolutely went in and said [54:29] look we uh we're not just treating this [54:32] as work but we're treating this as a [54:35] um an opportunity to shine in certain [54:38] areas of the development thing. So [54:40] whether that is Woo Commerce and LMS's [54:43] and I don't know something else or whe [54:46] whether that's a particular market [54:47] they're focusing on. [54:50] you've entered the phase where this is [54:52] absolutely a necessity because there's [54:54] plenty of agencies that I talk to on on [54:56] very different levels uh quite similar [54:59] uh to yours Tim where uh most of the [55:02] connections that I have are with [55:04] agencies they're finding it very [55:06] difficult to [55:08] understand where the thing went wrong [55:11] but the thing went wrong 3 four years [55:13] ago when you weren't specializing and [55:15] telling people you were specializing I [55:18] see I've seen so many agency sites over [55:20] the over the I don't know past 6 months. [55:23] Uh just people reaching out to me asking [55:26] questions and asking for help or a small [55:30] analysis or whatever. Uh and I look at [55:33] their website and it's like I'm I'm [55:35] aware of what you do cuz I've seen some [55:37] of your work but I don't see it on your [55:39] site. There's no specification of a [55:42] niche or a particular skill that sets [55:45] you apart from anybody else. So if a [55:48] client is looking, they're going to see [55:50] the same thing. They're going to go, I [55:52] recognize that this particular agency is [55:55] very specialized in XYZ. I need Y and Z. [55:58] So that's that's good enough. That's [55:59] what I'll go for. Um that whole and and [56:04] I I kind of hinted at that at my latest [56:06] one of my latest blogs. I think um we as [56:10] a community and and players in that [56:12] community uh we need to level up in our [56:15] entire thinking in our entire skill set [56:17] in our our entire integrations of all [56:20] the tools that we use. We need to [56:22] understand what's out there what's in [56:25] there in order to become the best type [56:27] of uh development party as well as [56:31] understand that we need to brand [56:32] ourselves. We need to be out there. It's [56:34] a different world. We can't go on how [56:37] you know we can't go on how we've been [56:39] doing for I don't know [56:43] for uh I saw something like the median [56:46] age of uh of that survey 11 age 11 years [56:49] or so [56:50] >> but in those 11 years eight of them have [56:52] been relatively easy. So if you don't [56:55] recognize that, if you don't if you're [56:56] not aware that this is a this is in part [56:59] also a very large thing about branding, [57:03] a large thing about visibility, a large [57:06] thing about [57:08] uh understanding what your skill sets [57:10] are and and not afraid to use them as a [57:12] as a thing that sets you apart. It's [57:14] very difficult to find continuous growth [57:17] in a period where the level of of skills [57:22] needed to get the base um projects done [57:26] is going down that is AI. And on the [57:29] complex end of things, yeah, if an [57:32] agency has a really good profile on on [57:34] large complex projects, then it's very [57:37] logical they're going to get those [57:38] projects. If a if a if a small in [57:41] between agency [57:43] is never, you know, every now and then [57:45] touches the larger project but hasn't [57:47] turned that into a skill that is [57:49] sellable and presentable and all that [57:51] sort of stuff. How how is the market [57:53] going to react? It's going to react uh [57:56] pleasantly to those who have put in the [57:58] work of marketing, of presenting, of [58:02] case studies, all that sort of stuff. [58:04] It's inevitable. Every single industry [58:07] outside of our industry goes through [58:09] these levels of, [58:11] you know, there's growth and then then [58:12] then you hit a plateau. Something needs [58:16] to change when you hit that plateau. And [58:18] the thing that needs to change [58:20] >> is very much something that you need to [58:23] see coming instead of all right now I [58:26] have to do something. You're already two [58:27] years too late. If now now is the time [58:30] that you think I I need to change [58:32] something, it's too late. So the only [58:34] thing you can do is radically improve [58:36] all every single thing that you do. That [58:38] is sales, that is marketing, that is [58:40] development, that is understanding all [58:42] the things that set you apart from a [58:43] technical skill. It's everything. [58:46] >> It is so hard to niche down in a [58:49] drought. When you when when the pipeline [58:52] is feeling good, that that that feeling [58:55] of like, oh, I can we can afford to [58:57] niche down now. We can become that [58:59] specialist. whether that's a niched [59:00] subject or a niche tool set. But when [59:03] there's a drought, [59:05] as someone who's been there, been in [59:07] that in that place, [59:09] the panic mode that comes on to every [59:11] business owner is because they got to [59:13] sit there and ultimately business owners [59:15] are there going, I have to make payroll [59:16] this month. So, I'm willing to take [59:18] things to make payroll to even if it [59:20] makes my life hund times worse down the [59:23] line, [59:24] >> they there comes a point where you sort [59:26] of have to do that just to scrap through [59:27] and survive. But I agree. I think if you [59:30] don't if you weren't in a niche, if [59:33] you're not in a niche now, you probably [59:35] need to be in a niche really quickly. I [59:39] think the only bit where I'm like is I'm [59:41] not necessarily sure the niche has to be [59:43] tools. I don't think you need to be a [59:46] niche Woo Commerce developer or even a I [59:50] think you can niche out in a different [59:51] way. You can maybe [59:53] >> there's various ways audience there [59:55] there's various ways of doing it. It can [59:56] be topical. It can be it can be skill [59:58] set. It can be it can be many things. [60:00] But you need to specialize in a way that [60:02] is presentable, marketable, all those [60:05] things because h how is your next client [60:08] going to know? How are they going to [60:10] know? They're going to look at a generic [60:12] site where you present your skills as we [60:13] build themes, we build plugins, we're [60:16] good at it. Yay. Like well I mean that's [60:18] that's the thing is when you're in a [60:20] when you're in a boomer bust sort of um [60:23] industry which is what we are either you [60:26] can do no wrong right which is when [60:29] you're in the boom you can do no wrong [60:30] you're growing and and everything and [60:33] then it becomes I think it feels risky [60:37] when you're in that boom to say what do [60:40] I specifically want to pick here when I [60:44] can do no wrong. [60:46] >> Yeah. and and and that's where the [60:48] people succeed when there's the bust and [60:52] are the people who look down the road [60:54] and they can see it coming and they can [60:56] choose wisely or they just plain get [60:59] lucky. Um, you know, there's there's [61:01] sometimes just plain dumb luck. You look [61:04] at the oil booms and all that stuff, [61:06] it's just sometimes it's just people [61:08] pick the land that happen to have the [61:09] oil, you know. So, [61:12] >> it's the same type of thing. Wait, you [61:14] mean my two sticks are not going to get [61:16] me oil consing along for my [ __ ] Maybe [61:20] sticks won't work. [61:21] >> I've done 20 years of the two sticks [61:23] thing and I've never [61:25] >> No, just grass. [61:27] >> Why doesn't that Why doesn't that [61:28] surprise me? [61:29] >> Every evening I'm out with the dowsing [61:31] rods. Um, so it's a fairly um, so the [61:36] report that we had on the screen from [61:37] Kyle, it doesn't paint this sort of [61:39] picture of um, there's no sense of sort [61:42] of doom there or anything like that, but [61:44] but this is uh, this is the tenor of [61:47] what is coming out of WordPress [61:49] publishing houses at the moment, like [61:51] podcasts and blogs and what have you. [61:53] There's this sort of how the heck do we [61:55] navigate this thing? And so, [61:57] >> well, it starts with any problem. You [61:59] are you recognize that it's a problem. [62:01] So if you haven't identified it as a [62:02] problem just yet, now is the time to [62:05] level up and pick a direction. And it [62:07] can be multiple directions. Like it's [62:08] not a it's not a binary thing. [62:10] >> But I I'll give you I'll give you one [62:13] good example. We all know AI has taken [62:15] over some version of search. How much? [62:19] We don't know. But it's certainly [62:22] quantifiable. Now, if you have an agency [62:26] and you haven't [62:28] uh optimized your site in terms of this [62:31] is what I do and and all the things I [62:33] just said, I'm not going to repeat all [62:34] that, but you haven't made that [62:36] available for the AI to do in the most [62:39] uh [62:41] smoothest way. [62:42] >> Yeah, [62:43] >> that's an indication of you're running [62:44] behind. There's there's a Cloudflare uh [62:48] released a website last week I think or [62:51] the week before. Is my [62:55] is my site agentic? What is it? [62:57] >> Yeah. Is Okay. [62:58] >> Is it agentready.com? [63:01] >> Okay. [63:02] >> So, for starters, add your site in there [63:05] just to have you be aware of what uh [63:09] what your site needs to qualify for [63:11] nowadays just to be visible on the AI [63:13] side of things. like all of these things [63:15] matter now. [63:16] >> Go. [63:17] >> And and that's just one piece of the [63:18] jigsaw puzzle. So AI feels like a giant [63:21] piece of that jigsaw puzzle, but it's [63:22] also possible shrinking market share. [63:25] >> It can be all of the things, but you [63:27] need to you need to get off your ass and [63:28] and and be proactive. You there's no [63:30] time for reactiveness now. [63:32] >> Okay, that's it. We're going to wrap [63:33] this show up and I'm going to go and uh [63:35] yeah, I'm I'm out of here. I'm going to [63:37] do all the things that need doing. Um [63:39] there's a few comments around this. This [63:41] seems to be the piece today that's got [63:42] the uh got the comments. Um firstly, um [63:46] Mark in the UK, Mark Wilkinson said, [63:50] "Getting harder." I would agree with [63:51] that for sure. Seems to be no doubt [63:53] about that. And then Mark made a few uh [63:56] complimentary comments about what Tim [63:57] was saying. I can't remember the context [63:59] because it's several minutes ago now. Um [64:01] also, uh James Laauo said he totally [64:04] forgot about this show. Well, I don't [64:06] know what to make of that, James. That [64:08] betrayal. Uh no. I'm joking. Uh I [64:12] >> It's a good demonstration of promotion [64:14] and branding being important and your [64:17] brand clearly failed because it didn't [64:19] last even three weeks. [64:21] >> Okay. Damn it. Okay. My brand as if I as [64:25] if I have a brand. Uh but appreciate [64:28] that, Tim. That's very kind of you. Uh [64:30] and then getting back to the real stuff, [64:32] he says, um I will be asking the state [64:34] of the WordPress. Uh, sorry. I'll be [64:36] asking about the state of WordPress from [64:38] Mary Hubard during tonight's Boston [64:40] WordPress meetup. Okay, that's [64:41] interesting. Thank you. Uh, James, uh, [64:43] Tim has a great point. A small, as a [64:46] small new agency owner, I am seeing this [64:48] change. My niche, this is James [64:51] commenting again. My niche has been uh, [64:53] eaten up by Squarespace, Web Flow, etc. [64:56] WP is still top, but people are asking [64:59] for other options. It's truncated, so [65:01] I'll read it. These platforms offer [65:03] other integrated options, but I have to [65:06] relearn my brain. And then an agreement. [65:08] >> That last sentence is spot on. [65:10] >> Yeah. [65:11] >> You have to relearn your brain. [65:13] >> Relearn your brain. [65:14] >> Absolutely. [65:15] >> And then he's agreeing with you. Um, [65:17] Remus need you need to see what's [65:19] coming. It depends on the niche or the [65:21] client. [65:21] >> And for the record, I don't mean like [65:23] you need to have the the the the glass [65:25] ball, right? Nobody has that. That [65:27] that's not what I'm saying. What I'm [65:28] saying is there's there's there's [65:30] changes in our industry and you need to [65:32] embrace them instead of I'll look at it [65:35] when I'm forced to or when the project [65:37] asks for it that that you don't have [65:39] that luxury anymore. [65:41] >> And then this sort of speaks into that a [65:43] little bit. Um again, James, uh I've [65:45] accepted work from my niche that isn't [65:46] only WordPress work. It's just the point [65:48] we're at right now. Okay. So the niche [65:50] is the thing, not WordPress being the [65:53] thing. But that's fine because again if [65:55] you one of the things that we've got [65:57] coming is that and this has always been [66:00] the case but nobody's believed that [66:03] clients don't actually care. They don't [66:05] care for example they don't really truly [66:09] care if you built their word their site [66:10] on WordPress as long as it meets the [66:12] feature set that they wanted at the [66:14] time. This can lead them down into [66:16] terrible paths when this is how, you [66:18] know, dev shops that build custom CMSs [66:20] still exist and shouldn't, but they [66:22] still exist. But that's because clients [66:24] don't actually care about that. Well, [66:26] they care about the functionality. And [66:27] if you give them what they wanted in [66:29] terms of functionality, they don't care [66:30] about what it was behind the scenes. In [66:33] the same way that clients don't care if [66:36] you manually update a site every day and [66:39] keep it, they they care about will you [66:41] keep it up to date and will you keep it [66:42] secure. how you do that irrelevant to [66:45] them. As long as you're doing it, [66:47] >> they couldn't give a flying monkey. [66:50] >> They couldn't give a flying monkey. [66:53] >> If your if your niche doesn't if it mean [66:56] your niche no longer has WordPress as a [66:59] feature in part of its part of thing it [67:02] cares about, then you don't need to use [67:05] I know that's apocalypical on a [67:07] WordPress podcast, but you don't need to [67:10] use WordPress in that scenario. [67:12] >> I'm going to mute him. so badly. [67:13] >> I know you're going to if you are [67:16] someone who is now sitting and you write [67:18] all your blog posts or rather Claude [67:20] writes all your blog posts, you might [67:22] and you're never going to review them. [67:24] You're never going to do any formatting [67:25] on it. You're never going to log in. You [67:28] probably don't want WordPress anymore. [67:30] And that's [67:31] >> the thing we have to accept is that is [67:34] okay. That's always been okay because [67:37] I'm having heart [67:40] should have had to force them to do [67:41] this. Nath Nathan's like, "What is my [67:43] podcast going to be about next week?" [67:44] >> This week in this week in talking, [67:49] >> he's he's gonna change the name from WP [67:51] Builds to, you know, [67:53] >> build. [67:55] Yeah. Yeah. Yeah. But I agree, Tim. That [67:59] makes perfect sense. And I'm sure that [68:01] on many levels, many of us have got it. [68:02] You have also spawned this week's titles [68:05] episode without a doubt. Uh Tim Nash [68:07] says, "Clients don't actually care." [68:09] That's gonna I might miss the Tim Nash [68:11] bit out at the beginning, but that I [68:13] think will be the episode. So, some more [68:14] comments about that. Uh just to keep [68:16] this going for a little while. Uh [68:19] where were we? Nomad skateboarding. [68:21] Hello. Um some also choose to run their [68:24] own waist so they can't be left behind [68:25] in the popular one. Oh, interesting. [68:27] Okay. Yeah. So, forge your own path. [68:29] Make make your own way and be the [68:31] trailblazer and everybody follows you. [68:33] Um, [68:35] so this is definitely Steve Burge's [68:38] picture, but I don't recognize the [68:39] handle there. So, normally it says [68:41] something different. Um, but there we [68:43] go. Ali, so Steve Burge, the flat cap [68:46] and headphones are a brand I'd recognize [68:48] Nathan silhouette anywhere. That's very [68:51] kind. I appreciate that. Um, oh, I'll [68:54] just put the same comment up twice. What [68:56] scares me now, says James, is when a [68:58] client comes to you with a solution [69:00] based on what AI told them. Oh, [69:02] >> so I [69:04] >> can can I say it shouldn't scare you, [69:07] >> right? [69:07] >> You should have an ready type of [69:10] approach answer, [69:11] >> right? [69:11] >> In in how you deal with this because [69:13] this is the new reality. I have clients [69:15] as well who are paying me handsomely [69:17] every month for XYZ. There's a you know [69:20] a variety of things that I do. Every now [69:22] and then someone now says, "Hey, I've [69:25] seen this and they said I can do this. [69:29] Why don't you uh integrate this for me?" [69:30] And then I explain them why this is or [69:33] isn't a good idea in detail. You have [69:36] you need to have these answers ready [69:37] now, [69:38] >> right? [69:39] >> That's a great start should be your [69:41] should be be your hand for any for any [69:44] statement when it [69:47] >> sentence. [69:48] That's a great that means you've had a [69:50] conversation where you hashed out what [69:52] you want and you we have a direction. [69:54] >> It's no different than than back in the [69:56] days. I remember doctors hated when [69:58] you'd go to WebMD and bring in a [70:00] diagnosis. Yeah. [70:02] >> And and those doctors have kind of [70:04] fallen by the wayside. Now when you go [70:06] to the doctor, you go in and you say and [70:08] you've googled it, they're like, "Oh, we [70:10] really appreciate the fact that you've [70:12] gone and done all the work because we [70:14] only have 15 minutes to talk to you [70:15] anyway, and it's best, you know, and and [70:18] and I will tell you why this is wrong, [70:21] but I will also tell you why this is [70:23] right." And if you're going to an [70:25] expert, that's what an expert does. An [70:27] expert says, "Hey, thanks for doing the [70:29] research before you came here." It means [70:31] you're serious about your project. And [70:34] here is, like you said, this is a great [70:37] start and this is how we can expound [70:40] upon it and this is how we can build on [70:41] it. And if we the reality is there going [70:44] to be people who embrace AI and there [70:46] are people who don't. And the get off my [70:48] lawn people, I'm sorry. They're going to [70:51] have to find another industry because AI [70:53] is here. You're gonna have to deal with [70:55] it and you're gonna have to deal with [70:56] everything that that entails. [70:58] >> Correct. [70:59] >> Okay. So, all of that was spawned by the [71:02] We sort of went off in myriad directions [71:04] there, but that was really nice. Um, [71:06] they're the best bits at this point. Do [71:07] you mind if I add one last bit about the [71:10] article or not? Which is um and I think [71:12] it was you who said it, but I think [71:15] they've had far less [71:17] >> responses this year. [71:21] >> The survey, let's just put it back on [71:23] the screen. So, the survey had 622. [71:26] I can't for certain say that that's [71:27] down, but I for some reason I think it [71:30] was [71:32] >> you put the word five there. [71:33] >> Let's try 25. Yeah, let's try that. Good [71:36] point. I don't know if it'll surface it [71:37] in the same way. [71:40] >> Literally half. Yeah. [71:41] >> Okay. 2024. [71:43] >> Okay. Let's see what we get with that [71:49] >> similar 1,200ish. But I feel like that [71:52] in itself is indicative of something. [71:54] Whether that is um whether that is [71:57] business owners who are going actually [71:59] I'm in a really negative place and [72:01] especially if they I I suspect that when [72:03] it got to the financials in the [72:04] questionnaire that that's where a lot of [72:06] the cut off came where people sort of [72:08] went [72:11] >> yeah I've had a bad year [72:14] and and that and that that just was [72:16] where they turned off and stopped [72:17] putting in or whether it is an [72:19] indication that we really have just lost [72:22] half an industry which which I don't [72:24] believe is the case, but I I found that [72:26] to be possibly the biggest statistic of [72:29] all because I don't think the admin bar [72:32] has lost half its readership. I don't [72:36] think it's lost its uh impact to reach [72:39] its audience by half in a year, which [72:42] means there must be another reason that [72:44] it [72:45] >> Well, I I think there might also be [72:47] survey fatigue just people are tired of [72:49] filling out surveys. [72:50] >> That could be it. [72:51] >> Yeah. Okay. So, it's spawned a lot. Um, [72:54] there's so much data in that. Um, and it [72:57] is literally just presented as data with [72:59] KL dropping in some thoughts about, you [73:01] know, what that data might mean. Um, but [73:03] no sort of overall uh conclusions, but [73:06] we definitely toss that around a little [73:07] bit. That was fascinating. I So, we've [73:10] got very little time left, so we'll just [73:12] whip through a few of these. So, this is [73:13] an interesting one. It's by Matias [73:15] Reinholds. [73:17] And, um, I don't know if this kind of [73:19] speaks to what we've just been talking [73:21] about. you know, this fear out there of [73:23] our industry sort of shrinking or what [73:25] have you. But there seems to be a lot of [73:27] trying out new things, let's put it that [73:29] way, out there in the wild and, you [73:31] know, so lots of things about setting up [73:34] dev environments for contributors at [73:36] word camps, lots of um educational [73:38] initiatives in the WordPress space that [73:39] didn't exist before. And now we have [73:42] this which I think is so interesting. So [73:44] Matias is obviously an automatician [73:46] because this post is kickstarting a [73:48] radical month at automatic. Now, Remus, [73:50] I think knows more about this in terms [73:52] of who's in and who's out, but um this [73:55] person along with a companion inside of [73:58] WordPress um has been authorized for one [74:01] month and I'll just read it. Today is [74:03] the first day of radical speed month at [74:06] Automatic. For one month, I get to get [74:08] to pair up with a colleague and build [74:10] something real. No design reviews, no [74:12] product signups, no marketing sign off. [74:15] I'm curious to see what a pair can ship [74:17] in a month without the usual approval [74:19] chain in place. And um so they have [74:23] decided to do a particular thing you can [74:26] find out more on the website. But I I I [74:28] don't first of all I don't know like I [74:32] don't know if everybody gets to do this [74:33] if you're a developer automatic in other [74:35] words has automatic more or less shut [74:37] down for a month or is it just like a [74:38] cherrypicked you know five or six seven [74:40] or eight people which one remicked and [74:43] it's notic there's there's quite a [74:46] number um our friend Jamie Marsland is [74:49] one of them [74:50] >> okay [74:51] >> um it's best I have gathered that it [74:55] this is a this is an a mechanism to [74:58] spark creativity and productivity and [75:02] just [75:03] >> blue sky thinking unconstrained. [75:06] >> It's a hackathon type approach, right? [75:08] >> But it's a month of a hackathon. I mean, [75:10] you know, it it reminds me of those days [75:12] when Google gave all of their dev [75:14] employee, in fact, I think everybody, [75:16] I'm not sure, uh like a Friday off every [75:19] >> every week, right? It was 20% time and [75:21] you could do whatever you liked and [75:23] loads of [75:24] >> stuff came out of Google because of that [75:27] 20% time. I'm sure there was a hell of a [75:29] lot of waste. [75:30] >> That's how I see this, [75:31] >> right? So, it's like the 20% time, but a [75:34] month I mean gosh, I am imagining these [75:37] people bright individuals. They've got [75:39] loads of history doing things. I'm very [75:42] curious to see what the heck comes out [75:44] of a month of [75:45] >> So, a month is essentially saying don't [75:47] don't think too small. [75:49] >> Yeah. Right. Right. Exactly that. Yeah. [75:51] >> Which is which is what we're inclined to [75:53] do anyway because you know APR what is [75:56] that? You you you you you research a [75:58] particular bug or a small feature this [76:00] and that and here's here's my PR and and [76:02] voila. But if you have a month you get [76:05] to think about it. You get to [76:06] experiment. You get to play. You get you [76:08] have your buddy that you're back and [76:10] forthing with with um I like this. I [76:13] like this a lot actually. It's a very [76:16] confident step financially as well. You [76:19] know, that's not a cheap gesture. [76:21] >> No, [76:22] >> it's going to cost millions of dollars [76:24] presumably, [76:25] >> but it might reward them with millions [76:27] as well. [76:27] >> Yeah. [76:28] >> Imagine if one one of the ideas turns [76:30] into, I don't know, the next SAS app. [76:32] Obviously, automatic, we we align it [76:35] very much with WordPress, don't we? But [76:36] they also have irons in many fires. [76:38] They've got podcasting things, you know, [76:41] there's all sorts of they've got like [76:42] Day One, haven't they? like a journaling [76:44] app and things like that. So perhaps it [76:46] the gamut is not going to be limited [76:48] around WordPress. But I just thought [76:50] that was really curious. So um let's see [76:52] what these folk do. Sorry Tim, I think [76:55] you might have been trying to say [76:56] something. [76:56] >> No, no, I'm just though I have I was [76:58] sitting here going what if I could just [77:01] have a month? I could do so much cool [77:03] stuff. I didn't have to do anything else [77:05] for that month. Yeah, [77:06] >> right now I think anybody who's got that [77:10] time, this is the this is the possibly [77:13] the fastest point for to be able to go [77:16] from idea to implementation [77:19] >> ever that we've ever had. [77:21] >> It's wild. [77:22] >> Yeah. [77:24] >> Sorry, it's not James. Sorry. Nomad [77:26] skateboarding. Um I presume, let's just [77:29] assume that this is research and it's [77:30] true. 400 plus teams doing that. So, by [77:34] that, do you mean 800 individuals or [77:36] there's 400 different, you know, paired [77:40] people? Either way, that's not nothing. [77:43] Wow. Gosh, that's going to be so [77:45] interesting. Let watch this space. Let's [77:48] see what comes back in a month's time. [77:49] It wouldn't be surprising if there was [77:51] one. [77:52] >> That's 30 days of shower thoughts, which [77:54] is when all the good ideas happen. So, [77:56] >> yeah. Yeah. Yeah. I wonder what these [77:59] individuals will do with themselves. I [78:01] wonder what their day will look like. [78:02] you know, whether they'll just, I don't [78:04] know, go and sit on the beach and enjoy [78:05] themselves whilst doing it as opposed to [78:07] stuck in Slack meetings at home and [78:09] things like that. Anyway, fascinating [78:12] and an automatic which is definitely [78:16] trying out some new things. So, let's [78:18] see where that goes. Anybody else on [78:21] that? Oh, it came from an automatic post [78:24] on the Facebook page that gives you an [78:26] insight into the whole program. So, it [78:28] is 800 people. Man alive. That is not a [78:32] cheap thing to have offered for free. [78:34] Wow. Okay. [78:36] >> Okay. There we go. That's that one. Uh [78:38] let me just get that comment off the [78:40] screen. We really are running out of [78:41] time. Where did we get to? No, there's [78:44] no time for that. There probably isn't [78:46] time for that. No, let's just go [78:49] straight to this one. [78:51] >> Um I kind of like the uh agent one. [78:54] >> Okay. Do you want to go for this one? [78:56] >> I I think this is an interesting uh [78:58] take. um that sort of has been forming [79:02] as we were seeing 7.0 O come to be [79:07] um [79:09] coinciding with quite a few things [79:11] happening on um the AI side of things [79:17] I think I mean first of all this is this [79:20] is published on automatic.com so it is [79:22] in some way promotional it is in some [79:24] way positioning sure [79:27] but WordPress does have the opportunity [79:30] with the market share that we have and [79:33] with 7.0 O being first step into [79:36] integrating AI on a few different [79:39] levels, it does have to the absolute [79:42] perfect position to turn into the [79:44] operating system of the agentic web. [79:47] There is it's more than just branding [79:50] the thing. I think this is actually [79:51] something that's starting to happen. uh [79:54] it is an entirely new argument as to why [79:58] you should want to use WordPress because [80:00] yes why open source is the choice and [80:02] the MCP is the thing and you know but [80:06] there's already a lot of stuff going on [80:09] inside and uh outside of WordPress but [80:13] connecting to WordPress that really [80:16] makes WordPress a fine candidate for [80:18] this u [80:21] um this concept the operating system of [80:23] the agentic web. [80:25] >> It is so interesting this debate. So [80:27] I'll just read into the record the name [80:29] of this piece. So it is on automatic.com [80:31] and the piece is called WordPress colon [80:34] uh the operating system of the agentic [80:36] web and it's James Greersonen I think [80:38] you would pronounce his name as and he's [80:40] he's running through the you've probably [80:43] thought of most of these thoughts if [80:44] you're into WordPress I would have [80:46] thought um how how WordPress could [80:49] easily serve as the foundational layer [80:51] of future initiatives on the web like [80:53] like it says the operating system of the [80:55] web and as you would imagine the things [80:58] that are brought to bear in this [80:59] argument are things like the scale of [81:01] WordPress. So 43% and all of the [81:04] community that that brings. um the [81:06] 61,000 plus plus pro you know uh paid [81:10] for plugins which probably take it well [81:13] over a h 100,000 I would have thought [81:14] maybe more like 200,000 don't know and [81:17] um and the fact that opensource the [81:20] nature of WordPress being open source I [81:22] is that the the AIS know exactly what to [81:25] do um with WordPress because [81:28] everything's freely available so if you [81:30] want to do a thing the AI knows already [81:33] how to do that thing because all of the [81:35] document and what have you has been out [81:36] there for many many years. And that's [81:39] kind of the context of his argument. He [81:41] goes into the pros and the cons. I um [81:45] there's a there's a little bit of me [81:47] when I hear this argument um where I [81:50] think I wonder in 10 years time what [81:52] we'll think about arguments like this, [81:54] whether it will have been a case of [81:56] okay, that was very optimistic. We were [81:58] desperately clinging for WordPress to be [82:01] the thing. And the reason I say all of [82:02] that is because I don't even know what's [82:04] going to happen in two weeks time in AI. [82:07] It just seems to be happening at such a [82:09] breathtaking pace. I [82:10] >> it is but if if the foundation of that [82:13] is WordPress and WordPress makes all all [82:15] the new things uh that are are there to [82:19] to settle down as as permanent things. [82:22] >> Uh it facilitates that, it operates with [82:24] that, it integrates with that, it talks [82:26] with it in a loweffort manner which is [82:28] what 7.0 will be the first step towards [82:31] >> um I I I I don't see any other solution [82:34] than uh sorry um uh outcome than yes to [82:38] some degree it will I mean the same [82:39] >> it's a strong argument isn't it I agree [82:41] >> the same can be said when when custom [82:43] post types and tonomies were introduced [82:46] like people said oh now you can build [82:48] everything with WordPress and it'll be [82:50] the future and some people were like nah [82:52] I mean come on it's a blog we're not [82:54] we're not going to we're not going to [82:56] use a blog and to get out of here and [82:59] yet those who were building understood [83:02] what that unlocked. Um [83:06] I I kind of see this the same way if I'm [83:08] being really honest. [83:09] >> There is also the advantage that uh [83:12] people know WordPress. If you uh were to [83:15] ask an AI right now to spin you up a [83:18] website, it would go and get you tell it [83:21] would tell start telling you to write [83:22] some content into markdown files and [83:24] then it would load up a Nex.js JS app [83:26] which it would then spin up a bunch of [83:28] crap into. Uh it would then do a bunch [83:30] of stuff and then it would tell you I [83:32] have a website and that's great until [83:36] you need to fix something and then you [83:37] need to the AI. [83:38] >> That's it is like you have locked [83:41] yourself back in [83:42] >> to those commercial developers we were [83:45] dumping on ages ago who were building [83:47] their own CMSs. [83:49] >> It locks itself down in that way. [83:51] WordPress is something that is known by [83:54] everybody that you can that is universal [83:57] in that it can be deployed onto pretty [83:58] much any hosting company you ever can [84:01] think of. You can have it working very [84:04] quickly, very easily. You can pay [84:06] someone to maintain it. You can and [84:08] alongside this, if we make it easier and [84:11] easier for AI to operate and use it and [84:14] successfully, [84:15] we have the best of both. [84:17] >> Yeah. We can we maintain ownership, [84:21] which is something that at the moment [84:23] people who are just flinging sites up [84:25] with AI have actually losing and they [84:27] don't even realize they're losing that [84:29] really vital part, which is true [84:31] ownership, which is portability because [84:34] they are stuck in a scenario where [84:35] they're going to have to have somebody [84:37] or something debug every time. Now, I'm [84:40] not saying that every person who has a [84:42] WordPress site should should be doing [84:45] development on a WordPress site, but [84:47] they have that option and they have the [84:49] ability to go to a gamut of people from [84:53] really cheap companies to ginormous big [84:56] VIP agencies to help them alongside AI, [85:00] which is a really powerful tool in its [85:03] own right. Yeah, it feels to me as if [85:05] the direction of travel is a little bit [85:07] more like the the editing of already [85:12] kind of AI generated stuff is a big win [85:15] for WordPress. So, in other words, you [85:17] know, you've told you've told some um AI [85:20] to build you a web page. Now, what like [85:23] how do you go and amend it? How do you [85:26] like do you have to have a conversation? [85:27] No, not that bit. The the other cat, you [85:30] know, that kind of thing. And so having [85:32] it dumped into an an interface that [85:35] you're familiar with, it'll be really [85:37] interesting to see in the future how [85:39] much creation is done by the AI and then [85:41] the human in the loop bit is the okay [85:44] now we need to amend it because it's [85:45] Christmas and we want it to look [85:47] Christmy and yada yada that that'll be I [85:51] think that [85:52] >> and you know with real time [85:53] collaboration when you amend it it will [85:55] go no I didn't tell you to do that. [85:59] Oh, wheels within wheels. Um, go and [86:03] check out the piece though. It's on [86:04] automatic blog. Uh, it's by James [86:06] Greerson. It's called WordPress [86:08] operating system for the agentic web. I [86:10] I I got to say I I'm kind of convinced [86:13] that I think it's that's the um that is [86:15] the that is how it'll turn out. Um, [86:20] right. How are we doing for time? Not a [86:22] lot of time. And have we got any new [86:25] comments coming? Yes, a couple. So, uh, [86:29] James again, James is being a truly [86:31] amazing commenter. Thank you. Um, off [86:34] topic, he watched Dre from the Drupal [86:36] project at Drupalcon in 2026, the [86:39] keynote, and they Oh, yeah. I remember [86:41] this. Yeah, I remember seeing this, too. [86:43] They've got uh AI built directly into [86:46] their dashboard. It's called Drupal [86:47] Canvas. And you you just basically start [86:50] out a Drupal site now, don't you? Or at [86:51] least you can. Um, and it's all baked in [86:54] right at the very beginning. Um and he [86:56] makes the point that Dre made a good [86:59] point that even with all these agent [87:01] platforms um a scaffold uh to the front [87:04] end of the site is nice. You still need [87:06] governance humans in the loop really to [87:09] uh to help operate the nuances of the [87:11] nuances of the back end. So there we go. [87:14] Okay. Anything on that? I think we need [87:16] to rush. We will rush. Here we go. Um a [87:20] little while ago a plugin came out as a [87:21] suite of blocks which I thought was [87:23] quite nice. It enabled you to do a [87:25] little bit more with core blocks. It [87:27] extended the features. It was called [87:29] Twentig. If anybody played with it, it [87:32] was pretty lightweight in that it didn't [87:33] try to launch new blocks. It just added [87:36] menus to existing blocks. They've [87:38] decided to jump in the um the theming [87:40] space as well. So, I just thought I'd [87:41] mention that it's called Twig One. [87:44] Haven't tried it. I've no idea what it's [87:46] like. As far as I can tell, it's free um [87:49] just like their blocks were. But uh [87:51] anyway, there's that and [87:55] uh yeah, we'll just raise that on the [87:56] screen very quickly and several of the [87:58] panel can uh grimace. And [88:02] did they grimace sufficiently is all [88:06] moving on. Uh okay. Um [88:11] this was supposed to be the thing that [88:13] we talked about most this week and yet [88:15] we got totally derailed by the admin [88:17] bars article. So, [88:18] >> you know, if you want to do that, you [88:19] need to a tell the palist that this is [88:21] the figure you want to focus on and b [88:22] put it at the beginning. [88:24] >> Yeah. Well, that was [88:25] >> he did he did he did hint at it [88:27] actually. [88:29] >> But hint hinting is not being very clear [88:31] in your communication. Just play [88:35] never been good at this thing doing a [88:37] live show. It's uh but anyway, this is a [88:40] bit of a big deal and if you guys have [88:42] got a couple of minutes, let's just [88:43] explore it a little bit. Um this news [88:46] dropped. This is the repositories [88:48] version of it. But essentially, if you [88:50] had Woo Commerce subscriptions, [88:52] there is a chance, and you have to have [88:55] the docs incorrectly lined up in a row [88:58] for this to matter to you. But there is [89:00] a chance that you will have had [89:04] subscriptions which your customers had [89:07] set to autorenew. [89:09] Woo Commerce subscriptions might have [89:11] switched them off without alerting you [89:15] or alerting your customers. And so [89:17] basically they just went into this [89:18] completely silent fail state. Now, I [89:22] don't have any of this, so it's just a [89:24] news story to me, and it's, you know, [89:26] it's kind of, wow, that's a shame. But [89:28] it would appear that out there in the [89:30] wild, there are people that are claiming [89:31] that this is really cost them quite a [89:34] lot of money. And um and now we're in [89:37] that phase where uh the patches are [89:39] trying to be put together. My [89:41] understanding is much of it has already [89:42] been patched. Um, but it's quite a big [89:45] story that if you've got it set up and [89:48] the intention was to set it up so that [89:50] you know things would tick over next [89:52] year the subscription would happen [89:53] again. If it utterly silently failed, [89:56] that's really really bad from a business [89:59] point of view and it doesn't help Woo [90:01] Commerce uh out there in the public [90:04] sphere. I wouldn't have thought. [90:05] Anything to add to that? [90:08] >> A good example of where monitoring comes [90:11] into its own. [90:12] >> Yes. Yes, but who does I mean obviously [90:14] the the sites that say that this hadn't [90:17] happened uh sorry that this has happened [90:19] to them presumably they weren't doing [90:21] that. Yeah, fair enough. Um [90:23] >> I mean I don't not not to you know that [90:26] terms of like I don't care about the [90:28] people who it has happened to but uh if [90:31] you're running a subscription whether [90:32] it's a membership site or you're running [90:34] a subscriptions of any sort and this [90:37] surely affected a churn I mean maybe [90:40] maybe they're making enough that it [90:41] doesn't affect the churn rate and the [90:42] the percentages were small enough but [90:44] even just your churn rate would have a [90:47] noticeable change. What does it look [90:49] like though if you're a WooCommerce [90:51] store owner that from what from [90:52] everything I've read it looked to them [90:56] as if their customers had switched it [90:58] off because I I don't know what the logs [91:01] look like and you know what it actually [91:02] looks like in the database and yada yada [91:04] yada but my assumption I suppose as a [91:07] store owner would be okay I can see that [91:09] that is now not set to autorenew I would [91:12] just be thinking there's a dissatisfied [91:14] customer okay we lost them let's [91:16] concentrate on next year getting a load [91:17] of few people through the door. Do you [91:19] know what I mean? I can see how this [91:20] would slip through the cracks. [91:21] >> But presumably what is that whole one [91:24] one is unfortunate, two is a [91:27] coincidence, three is starting to be [91:29] >> I again it does depend on scale because [91:31] if this is only affecting four out of a [91:33] thousand customers a month, [91:35] >> you're not likely no amount of [91:37] monitoring is likely to pick that up. [91:38] But if it was, [91:40] >> you know, if all of your subscriptions [91:41] are suddenly having this problem, then [91:43] that's going to be you're going to [91:45] notice hopefully and people seemingly [91:47] did. [91:48] >> Yeah. So, the the person who figured [91:51] this all out, I'm not even going to try [91:52] and pronounce their name correctly. [91:54] >> Ver, [91:55] >> there you go. It sound as if it might be [91:57] Dutch. uh what Remus just said, they um [92:01] they um got into all of this, found a [92:04] bug, and then penetrated deeper over the [92:05] course of the next few days and found [92:07] four, three more, total of four, and [92:09] discovered that 121 subscriptions in [92:13] their setup had been affected and they [92:15] lost 40 Oh, I mean, it's not nothing, is [92:18] it? $43,000 [92:21] in potential revenue. Now, you can't be [92:23] certain that they were going to renew [92:24] anyway, but nevertheless, [92:25] >> well, yeah, [92:26] >> wouldn't the subscriber also notice that [92:30] their subscription is not active or [92:33] >> Well, that's the only way that this [92:35] would be alerted is that the subscriber [92:37] noticed and got back to the website and [92:39] says something's gone wrong. We wanted [92:41] access to whatever it is, in this case, [92:43] presumably a plugin. I guess the we're [92:45] sorry to see you go email that you just [92:48] that you absolutely hate when people [92:50] when you're canceling subscriptions and [92:52] your inbox fills in with the we're sorry [92:54] to see you go here have 10% off if you [92:56] click this button that you know 90% of [92:59] us will probably immediately been might [93:02] have in this one case this case possibly [93:04] have saved no I'd have just binned it [93:07] I'd have been it [93:08] >> also wasn't it a a total silent fail did [93:13] it it didn't trigger any emails or [93:14] anything like that. I think as well [93:16] that's my understanding is it just [93:17] failed utterly silently. So none of the [93:20] usual cavalcade of emails that might [93:22] >> Yeah, that's how I took it. That's how I [93:24] took it to mean that it was completely [93:26] just under the radar. Maybe this is an [93:30] example of where using your having your [93:32] email marketing and email transactional [93:35] system tied tightly into your [93:37] WooCommerce. [93:37] >> Right. Right. Right. Okay. So you could [93:39] have mitigated this on your own. Yeah, [93:41] that's possibly. I mean the thing is you [93:43] can't you ultimately you can't mitigate [93:45] for a bunch of series of c of cascading [93:47] failures. You can mitigate against lots [93:50] of things and we can be sitting here [93:52] afterwards going well if you've done [93:53] this and you put it like this and you [93:54] could have done this wrong and perfectly [93:57] fine but the reality is stuff like this [93:59] happens [94:00] >> and it's part of the cost of anything. [94:04] This is the equivalent of somebody in [94:06] the shop going and you know closing the [94:09] front door and locking it by accident [94:11] for 20 minutes at the start of the day. [94:13] >> Yes. Yeah, that's right. Go and sack the [94:16] employee. Uh anyway, WooCommerce are on [94:19] it, my understanding is. And they're [94:20] also trying to figure out if there's a [94:22] way of um an automated tool for one of a [94:26] better word. Mark's just turned into [94:28] like he's gone to Hades. um if there's a [94:32] way of figuring out who these affected [94:35] people are and then going back to them [94:36] cap in hand kind of basically saying [94:38] look we messed up the system messed up [94:40] what have you. So anyway that was fairly [94:42] big story. What else have we got? [94:44] Nothing. Oh couple of events I'll just [94:46] mention these quickly before we end. Uh [94:48] web agency summit is around the corner [94:50] 27th of April i.e. today it started. Um [94:53] if you go to atrim.iossummit io/summit [94:57] you can get involved in that and because [94:59] time is short uh there this will be the [95:02] last one uh if you are thinking about [95:04] going to word camp EU which is happening [95:06] in June then the schedule has been [95:10] announced in a lovely table with a [95:12] lovely feature you can actually [95:14] highlight with this little star the bits [95:15] that you like and send yourself an email [95:18] because uh you know we're all lazy and [95:20] that's helpful. That's it. That's all we [95:22] got time for. [95:25] Take a breath, Mr. Wriggley. [95:29] It's a lot It's a lot cooler here than [95:30] it is in India. That's I'm gonna I'll [95:33] definitely say that. I've got the even [95:35] though I've got the window open, at [95:37] least I'm not pouring [95:39] uh with sweat. Right, there we go. We [95:41] will be back hopefully uh this time next [95:44] week. All that it remains for me to do [95:45] is say thank you to our three panelists. [95:48] Mark, Benzerane, thank you Mark. Uh, [95:52] Remus somewhere there. Remus Travis, [95:55] thank you. He says he's got some news [95:57] next week. I don't know what that I want [95:59] him to tell me now. [96:01] He's not going to. Look, he's got that [96:03] face of I'm not saying [96:04] >> you could do do some investigating and [96:06] it's not [96:08] >> I'll do some investigating when we [96:09] finish this show. You can tell me then. [96:12] Uh, and Tim Tim Nash down there as well. [96:15] Uh, thank you very much. We will push [96:17] this out as a podcast audio episode, [96:19] which is how most people consume it. [96:20] That'll happen tomorrow at 7:30 or 7 in [96:23] the morning. And we'll be back, like I [96:25] said, next week for some more this week [96:27] in WordPress. Take it easy. Thank you [96:29] for Oh. Oh. Oh, got to do the handy [96:31] thing. Quick, the hand wavy thing, if [96:33] you don't mind. Only only one hand from [96:36] Tim. The one handed. There we go. [96:39] That'll do. That's great. See you all [96:41] next week. Take it easy. Bye. Ciao for [96:43] now. [96:44] >> Ciao for now indeed.  📄 **Full text:** ![[Full Document Contents/Articles/This Week in WordPress #371.md|This Week in WordPress #371 by YouTube]] ## Highlights - >> Yeah. >> Yeah. Thank you. I have no words. Uh, I'm very appreciative. Let's go with that. So, I'll read the bio uh so that we and you can have a small break. Have a coffee. Mark Benzerane is the partnerships and community lead at MainWP where he spends his time working with plug-in developers, agencies, and service providers across the WordPress ecosystem. He's been involved with WordPress for many years and is particularly interested in helping site owners keep control of their own infrastructure while still benefiting from the broader plug-in and hosting landscape. At MainWP, he focuses on ([View Highlight](https://read.readwise.io/read/01krgph6k26hmhpgz8h9d9ng8g)) - Tags: 👻 ai highlighted - maintained to the same high standards, the same release cadence, but wouldn't wouldn't take up space in the very lean and light WordPress of the future. And uh roll on nine months and we've got an what an MCP servery thing coming in. Uh an agent uh a whole new AI agent set thing that's in there with meaning for the first time ever, we're going to have credentials now in databases and this all in one place. It feels like who ([View Highlight](https://read.readwise.io/read/01krgph6k6qntd25q9bke3nw3d)) - Tags: 👻 ai highlighted - up to contrib and 10 minutes from sitting down you'd be fruitfully engaged in um part of the WordPress project. Well, not apparently. That's not how it works because um allegedly uh OneMar is saying a lot of people get lost at WordPress uh contributor day. So much so that people actually just sort of leave halfway through the setup of their machines um because they're just I guess just a bit weary of it. They figure out that they're not going to achieve anything just because the whole process of ([View Highlight](https://read.readwise.io/read/01krgph6k9k13t07whm3rxe06k)) - Tags: 👻 ai highlighted - the myriad articles. So, we need to burn through the next one. I'm going to miss that one out because we just don't have time for maybe I won't. Just very quickly, this this appeared on Word uh the makewordpress.org. It's kind of related to what was talking about. Contributing is hard, especially if you're new. And so, there's a piece written by Velder, uh, which was came out a couple of days ago, 23rd of April. It's called Help Others Contribute to WordPress. And it's it's not the technical side of getting ([View Highlight](https://read.readwise.io/read/01krgph6kdtdm6f2znjtjwh7je)) - Tags: 👻 ai highlighted - and then getting back to the real stuff, he says, um I will be asking the state of the WordPress. Uh, sorry. I'll be asking about the state of WordPress from Mary Hubard during tonight's Boston WordPress meetup. Okay, that's interesting. Thank you. Uh, James, uh, Tim has a great point. A small, as a small new agency owner, I am seeing this change. My niche, this is James commenting again. My niche has been uh, eaten up by Squarespace, Web Flow, etc. WP is still top, but people are asking for other options. It's truncated, so ([View Highlight](https://read.readwise.io/read/01krgph6kg0h8ydjchwfn29atq)) - Tags: 👻 ai highlighted - wonder what their day will look like. you know, whether they'll just, I don't know, go and sit on the beach and enjoy themselves whilst doing it as opposed to stuck in Slack meetings at home and things like that. Anyway, fascinating and an automatic which is definitely trying out some new things. So, let's see where that goes. Anybody else on that? Oh, it came from an automatic post on the Facebook page that gives you an insight into the whole program. So, it is 800 people. Man alive. That is not a ([View Highlight](https://read.readwise.io/read/01krgph6km8cjgxy365dbkkppg)) - Tags: 👻 ai highlighted - the thing. And the reason I say all of that is because I don't even know what's going to happen in two weeks time in AI. It just seems to be happening at such a breathtaking pace. I >> it is but if if the foundation of that is WordPress and WordPress makes all all the new things uh that are are there to to settle down as as permanent things. >> Uh it facilitates that, it operates with that, it integrates with that, it talks with it in a loweffort manner which is what 7.0 will be the first step towards ([View Highlight](https://read.readwise.io/read/01krgph6krbayxavs1xs6vp1xn)) - Tags: 👻 ai highlighted - of stuff and then it would tell you I have a website and that's great until you need to fix something and then you need to the AI. >> That's it is like you have locked yourself back in >> to those commercial developers we were dumping on ages ago who were building their own CMSs. >> It locks itself down in that way. WordPress is something that is known by everybody that you can that is universal in that it can be deployed onto pretty much any hosting company you ever can ([View Highlight](https://read.readwise.io/read/01krgph6kvaespkjbc7j3xk1z8)) - Tags: 👻 ai highlighted - check out the piece though. It's on automatic blog. Uh, it's by James Greerson. It's called WordPress operating system for the agentic web. I I I got to say I I'm kind of convinced that I think it's that's the um that is the that is how it'll turn out. Um, right. How are we doing for time? Not a lot of time. And have we got any new comments coming? Yes, a couple. So, uh, James again, James is being a truly ([View Highlight](https://read.readwise.io/read/01krgph6m0gqv09d8phkf7b4vc)) - Tags: 👻 ai highlighted - amazing commenter. Thank you. Um, off topic, he watched Dre from the Drupal project at Drupalcon in 2026, the keynote, and they Oh, yeah. I remember this. Yeah, I remember seeing this, too. They've got uh AI built directly into their dashboard. It's called Drupal Canvas. And you you just basically start out a Drupal site now, don't you? Or at least you can. Um, and it's all baked in right at the very beginning. Um and he makes the point that Dre made a good point that even with all these agent ([View Highlight](https://read.readwise.io/read/01krgph6m35t1kh2n5gws4bm4b)) - Tags: 👻 ai highlighted