'Aye eye' - This Week in WordPress #361 ๐Ÿ”— **Source:** ['Aye eye' - This Week in WordPress #361](https://www.youtube.com/watch?v=wxOewLY-6X8) > [!note]+ Document Notes > tags: [wordpress, podcast, ai, accessibility] > author: Nathan Wrigley > source: WP Builds > reference: https://www.youtube.com/watch?v=wxOewLY-6X8 > date created: 2024-01-15 14:30 > > # ๐Ÿท๏ธ Title: 'Aye eye' - This Week in WordPress #361 > <!-- deep-read:sections start --> ## ๐Ÿงฐ Action Inbox - [H1] Review accessibility audit methodology โ€” prioritize user impact over developer convenience #accessibility - [H2] Implement collaborative editing testing โ€” try Gutenberg plugin real-time editing feature #wordpress - [H3] Explore partnership opportunities โ€” consider strategic alliances for plugin/business growth #business ## ๐Ÿงญ Table of Contents - [๐Ÿ“ Summary](#-summary) - [๐Ÿ“– Main Content](#-main-content) - [๐Ÿ—’๏ธ Notes](#๏ธ-notes) - [๐Ÿ“š References](#-references) - [๐Ÿ—ฃ๏ธ Paraphrase](#๏ธ-paraphrase) - [๐Ÿ“ฐ Newsletter](#-newsletter) - [โœ… Action Items](#-action-items) - [๐Ÿงช Hypotheses](#-hypotheses) - [๐Ÿ“Š Methodology](#-methodology) - [โ“ Questions](#-questions) - [๐Ÿ”ฎ Future Research](#-future-research) - [๐Ÿ’ก Implications](#-implications) - [๐Ÿง  Learning Styles Assessment](#-learning-styles-assessment) - [๐Ÿ“Š Accessibility Assessment](#-accessibility-assessment) - [๐ŸŒ DEIB Assessment](#-deib-assessment) - [โœ… Logical Validity](#-logical-validity) - [๐Ÿ›ก๏ธ DARVO Analysis](#-darvo-analysis) - [๐ŸŽฏ Conclusion](#-conclusion) ### ๐Ÿ”— References - [SEMrush Accessibility SEO Study](https://www.semrush.com/blog/accessibility-seo-performance/) - [Katie Keith Plugin Sales Analysis](https://barn2.com/blog/plugin-sales-down-2025/) - [Joe Dolson Accessibility Severity Guide](https://joedolson.com/2025/01/judging-severity-and-accessibility-issues/) ## ๐Ÿ“ Summary - WordPress podcast covering accessibility, AI impact, and business trends - Key focus on accessibility improvements driving SEO performance and business value - Discussion of declining plugin sales but opportunities through partnerships - Collaborative editing features becoming production-ready in WordPress - Balanced perspective on AI challenges and WordPress future opportunities ## ๐Ÿ“– Main Content This WordPress podcast episode covers multiple key areas affecting the WordPress ecosystem in 2026. The panel discusses breakthrough research showing direct correlation between accessibility compliance and improved SEO performance, including 27% more keyword rankings and significant authority score boosts. They examine declining plugin sales across the industry with strategic responses including irreplaceable product development and strategic partnerships. The conversation addresses AI concerns with a bullish outlook on WordPress future, citing market dominance, economic ecosystem strength, technical flexibility, and continued developer opportunities. Additionally, they highlight WordPress collaborative editing reaching production-ready status through the Gutenberg plugin. ## ๐Ÿ—’๏ธ Notes #### โฑ๏ธ [00:00](https://youtu.be/wxOewLY-6X8?t=0) โ€” [H1] Show Introduction and Panel Setup - Key idea: WordPress podcast episode 361 with accessibility focus - Evidence: "Nathan Wrigley joined by Michelle Fchett, Mark Benzakane, and An Mika Blett" #### โฑ๏ธ [06:45](https://youtu.be/wxOewLY-6X8?t=405) โ€” [H2] Accessibility SEO Performance Study - Key idea: Research proves accessibility compliance directly improves search rankings - Evidence: "27% more keywords ranked with accessibility improvements" #### โฑ๏ธ [12:30](https://youtu.be/wxOewLY-6X8?t=750) โ€” [H1] Judging Accessibility Issue Severity - Key idea: Prioritize accessibility fixes by user impact, not developer convenience - Evidence: "Tackle critical content first, then frequency of occurrence, then ease of fix" #### โฑ๏ธ [18:15](https://youtu.be/wxOewLY-6X8?t=1095) โ€” [H2] Plugin Sales Decline Analysis - Key idea: Industry-wide plugin sales down 17.8% in 2025, new customers affected most - Evidence: "Katie Keith's data shows renewals stayed solid but new customers dropped" #### โฑ๏ธ [25:40](https://youtu.be/wxOewLY-6X8?t=1540) โ€” [H1] Irreplaceable Plugin Strategy - Key idea: Plugins with unique value propositions maintained or grew sales - Evidence: "The plugins that continue to have solid sales were the ones people consider irreplaceable" #### โฑ๏ธ [32:10](https://youtu.be/wxOewLY-6X8?t=1930) โ€” [H2] Partnership Success in Plugin Business - Key idea: Strategic partnerships showed strongest correlation with sales growth - Evidence: "Real success seems to have come out with partnering with people" #### โฑ๏ธ [38:50](https://youtu.be/wxOewLY-6X8?t=2330) โ€” [H1] WordPress Collaborative Editing Ready - Key idea: Google Docs-style editing now works smoothly in WordPress - Evidence: "Steve Burge: For the first time, it works great right out of the box" #### โฑ๏ธ [42:20](https://youtu.be/wxOewLY-6X8?t=2540) โ€” [H2] Big Bite Agency Joins WP Engine - Key idea: 15-year enterprise agency transitions from client services to product development - Evidence: "Gradually shift from client services to product development for larger scale solutions" #### โฑ๏ธ [46:35](https://youtu.be/wxOewLY-6X8?t=2795) โ€” [H1] Bullish WordPress 2026 Outlook - Key idea: Four strong reasons for WordPress optimism despite AI concerns - Evidence: "Market dominance, economic ecosystem, technical flexibility, developer opportunities" #### โฑ๏ธ [52:15](https://youtu.be/wxOewLY-6X8?t=3135) โ€” [H2] AI Assistant vs Replacement Perspective - Key idea: AI works best as creative assistant for unexpected solutions - Evidence: "Corey Mass uses AI for unexpected things like Brian Eno's oblique strategies" #### โฑ๏ธ [58:40](https://youtu.be/wxOewLY-6X8?t=3520) โ€” [H1] Plugin Team AI Overwhelm - Key idea: WordPress plugin review team struggling with AI-generated submissions - Evidence: "Plugin team member: tired of reading AI generated email responses" ## ๐Ÿ“š References - [SEMrush Accessibility SEO Study](https://www.semrush.com/blog/accessibility-seo-performance/) - [Joe Dolson Accessibility Severity](https://joedolson.com/2025/01/judging-severity-and-accessibility-issues/) - [Katie Keith Plugin Sales Analysis](https://barn2.com/blog/plugin-sales-down-2025/) - [Open Channels FM Grade Interview](https://openchannels.fm/) - [Big Bite WP Engine Announcement](https://bigbite.net/) ## ๐Ÿ—ฃ๏ธ Paraphrase - Accessibility compliance directly correlates with better SEO performance, with studies showing 27% more keyword rankings and improved authority scores - Plugin sales declined industry-wide in 2025, but strategic partnerships and irreplaceable product positioning showed strongest resilience - WordPress collaborative editing has reached production-ready status through the Gutenberg plugin, enabling Google Docs-style real-time collaboration ## ๐Ÿ“ฐ Newsletter **WordPress Weekly: Accessibility Drives SEO Success, Plugin Market Shifts** Hey WordPress community! ๐Ÿ‘‹ Big news this week: breakthrough research proves what accessibility advocates have long claimed - building accessible sites directly improves your search rankings. The SEMrush study of 10,000 websites shows accessible sites get 27% more keyword visibility. This isn't just good ethics, it's smart business. **What This Means for You:** - Prioritize accessibility fixes by user impact, not developer convenience - Focus on critical content access first, then frequently occurring issues - Consider accessibility as website hygiene, not compliance checkbox **Plugin Business Reality Check:** Sales are down 17.8% industry-wide, but don't panic! Successful strategies include building "irreplaceable" products and forming strategic partnerships. Katie Keith's transparent analysis shows partnerships had the strongest correlation with growth. **Exciting Development:** WordPress collaborative editing is production-ready! Try the Gutenberg plugin's real-time editing feature for Google Docs-style collaboration. **Resources:** - [Learn WordPress Accessibility](https://learn.wordpress.org/tutorial/introduction-to-web-accessibility/) - [Gutenberg Plugin](https://wordpress.org/plugins/gutenberg/) - [WP-CLI](https://wp-cli.org/) for accessibility testing automation Stay accessible, stay growing! ๐Ÿš€ ## โœ… Action Items #### WordPress - Core: Integrate collaborative editing feedback, improve accessibility defaults - Accessibility: Promote business case data, create severity assessment tools - Plugins: Address AI submission volume, maintain human review quality - Documentation: Create partnership guide templates, accessibility audit checklists - Community: Share positive AI integration examples, counter doom narratives #### OSPO - Developer Support: Accessibility training integration, AI tool evaluation - Community Engagement: Partner with accessibility organizations - Strategic Alignment: Track accessibility compliance KPIs #### Community - Maintainers: Implement accessibility-first development practices - Contributors: Focus on user impact prioritization in issue triage - Sponsors: Support accessibility tooling development ## ๐Ÿงช Hypotheses - Accessibility improvements create compound SEO benefits beyond initial rankings - Strategic partnerships provide more sustainable growth than organic search optimization - AI tools work better as creative assistants than task replacements - WordPress collaborative editing will accelerate enterprise adoption ### ๐Ÿ“Š Methodology - Analyze SEMrush accessibility correlation data across different website types - Survey plugin developers on partnership strategies and outcomes - Test collaborative editing features in real agency workflows ### โ“ Questions - How can WordPress core better integrate accessibility by default? - What partnership models work best for different plugin niches? - How will collaborative editing change WordPress agency workflows? ### ๐Ÿ”ฎ Future Research - Long-term accessibility SEO impact tracking - AI integration patterns in successful WordPress businesses - Enterprise collaborative editing adoption metrics ### ๐Ÿ’ก Implications - Practice: Accessibility becomes primary SEO strategy, partnerships essential for plugin success - Policy: WordPress accessibility standards need business case emphasis - Security: AI-generated submissions require enhanced review processes - Education: Accessibility training must include business value proposition - Funding: Accessibility tooling deserves increased investment priority ### ๐Ÿง  Learning Styles Assessment Reading level estimate: Grade 10 #### ๐Ÿ‘€ Visual learners - Present: SEO correlation charts, plugin sales graphs, accessibility audit screenshots - Improve: Collaborative editing workflow diagrams, partnership structure visuals #### ๐Ÿ”Š Aural learners - Present: Full podcast audio with panel discussion - Improve: Accessibility screen reader demonstrations, AI tool comparisons #### ๐Ÿ—ฃ๏ธ Verbal learners - Present: Clear terminology definitions, business case analogies - Improve: Step-by-step accessibility audit narratives #### ๐Ÿงฉ Kinesthetic learners - Present: Plugin testing recommendations, collaborative editing trials - Improve: Hands-on accessibility audit checklists, partnership worksheets #### ๐Ÿง  Logical learners - Present: SEO correlation data, plugin sales analysis timelines - Improve: Decision trees for accessibility prioritization, ROI calculations #### ๐Ÿง‘โ€๐Ÿคโ€๐Ÿง‘ Social learners - Present: Panel discussion format, community feedback integration - Improve: Accessibility user testing guides, partnership networking frameworks #### ๐Ÿง˜โ€โ™€๏ธ Solitary learners - Present: Individual research links, self-assessment opportunities - Improve: Personal accessibility audit worksheets, reflection prompts #### ๐ŸŒฟ Naturalistic learners - Present: Organic growth vs artificial patterns discussion - Improve: Ecosystem thinking about WordPress sustainability ### ๐Ÿ“Š Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure, podcast transcript available - Improve: Time-stamped navigation, detailed alt text for charts #### Keyboard navigation - Present: Standard YouTube player controls - Improve: Custom skip-to-topic functionality #### Contrast and readability - Present: Standard podcast player interface - Improve: High contrast mode for show notes #### Media and captions - Present: Full transcript provided, audio available - Improve: Synchronized captions, downloadable transcripts ### ๐ŸŒ DEIB Assessment #### Cultural breadth - Present: International panel perspectives, global WordPress focus - Improve: More diverse geographic examples, multilingual resources #### Inclusive language - Present: Clear technical explanations, defined jargon - Improve: Plain language summaries, avoid cultural idioms #### Neurodiversity support - Present: Structured format, clear timestamps - Improve: Summary bullets, consistent navigation #### Representation - Present: Diverse panel backgrounds, varied expertise areas - Improve: More underrepresented voice inclusion ### โœ… Logical Validity #### Strong reasoning - Deductive strength: SEMrush data analysis provides solid statistical foundation - Inductive strength: Plugin sales trends generalized from specific case studies - Causal reasoning: Accessibility-SEO correlation well-established - Analogical strength: AI assistant comparison to Brian Eno cards effective #### Fallacies - Survivorship bias: Focus on successful partnerships may miss failed attempts - Hasty generalization: Plugin sales trends from limited sample size #### Tone of voice - Overall tone: Informative and optimistic, balancing concerns with opportunities ### ๐Ÿ›ก๏ธ DARVO Analysis - Deny: No concerning denial patterns identified - Attack: No attacks on accusers present - Reverse victim/offender: No victim/offender reversals noted - Emotional cues and rhetoric: Professional, supportive discussion tone throughout ## ๐ŸŽฏ Conclusion This WordPress podcast episode provides valuable insights into the intersection of accessibility, business strategy, and technology evolution. The key takeaway is that accessibility improvements drive measurable SEO benefits while strategic partnerships offer the strongest path to business growth in challenging market conditions. WordPress remains well-positioned for future success through technical flexibility and strong ecosystem foundations, with collaborative editing representing significant progress toward enterprise capabilities. ## ๐Ÿงฑ Refactor Appendix ### ๐Ÿ“š Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] Accessibility compliance correlates with SEO performance > [!quote] ['Aye eye' - This Week in WordPress #361](https://www.youtube.com/watch?v=wxOewLY-6X8) by [[Nathan Wrigley]] via [[WP Builds]]. Published 2026-01-12. Accessed 2024-01-15. > "27% more keywords ranked with accessibility improvements" SEMrush study of 10,000 websites proves business case for accessibility investment. [view highlight](https://www.youtube.com/watch?v=wxOewLY-6X8#H1) #accessibility #seo #articleseed ID:rw_001 ### [H2] Strategic partnerships drive plugin business success > [!quote] ['Aye eye' - This Week in WordPress #361](https://www.youtube.com/watch?v=wxOewLY-6X8) > "Real success seems to have come out with partnering with people" Katie Keith's analysis shows partnerships as strongest growth correlation during industry decline. [view highlight](https://www.youtube.com/watch?v=wxOewLY-6X8#H2) #business #partnerships ID:rw_002 --- ### ๐Ÿ”– Atomic Split Pad (Zettel Candidates) Purpose: Promote reusable claims into Atomic notes. Split level: H4 #### [Z1] Accessibility fixes should prioritize user impact over developer convenience - Applies to all web development accessibility audits - Referenced at timestamp 12:30 and Joe Dolson methodology - Links: [[Accessibility-Strategy]] [[User-Centered-Design]] #### [Z2] AI works better as creative assistant than task replacement - Relevant for all AI integration strategies - Demonstrated through Corey Mass Brian Eno card example at 52:15 - Links: [[AI-Strategy]] [[Creative-Process]] --- ### โœ๏ธ Fleeting Queue Purpose: Capture quick actions for Fleeting notes. - [F1] Test collaborative editing in Gutenberg plugin โ€” wpbuilds.com/live #fleeting #wordpress - [F2] Review accessibility audit methodology with Joe Dolson approach โ€” business impact focus #fleeting #accessibility - [F3] Research partnership opportunities for plugin/service businesses --- ## Full Transcript [00:04] It's time for this week in WordPress<br>[00:06] episode number 361 entitled A I. It was<br>[00:12] recorded on Monday the 12th of Jan 2026.<br>[00:16] My name is Nathan Wrigley and today I'm<br>[00:18] joined by co-host Michelle Fchett but<br>[00:20] also by Mark Benzakane and by an Mika<br>[00:23] Blett. It's a WordPress podcast so we<br>[00:25] spend quite a lot of time talking about<br>[00:27] WordPress. We kick things off though<br>[00:29] with a conversation about well lots and<br>[00:32] lots of articles related to<br>[00:34] accessibility. An's expertise is in that<br>[00:37] area and so we bring quite a few bits<br>[00:38] and pieces to bear in the accessibility<br>[00:40] space. I also mentioned a show that I<br>[00:42] did recently with Joe Doulson and<br>[00:45] promoted that a little bit as well. And<br>[00:46] then we get onto WordPressy stuff,<br>[00:48] collaborative editing, the fact that Big<br>[00:50] Bite has joined WP Engine. We also talk<br>[00:54] about why in the era of AI it is still<br>[00:57] possible to be bullish about the<br>[00:59] opportunities for WordPresses. There's a<br>[01:01] few articles floating around about that.<br>[01:03] And then the plug-in team seems to be<br>[01:05] delued by AI plug-in submissions which<br>[01:08] is good but also has its drawbacks<br>[01:11] because of the toll on the humans trying<br>[01:12] to keep all of that thing going. Then<br>[01:14] there's a whole new section all about<br>[01:16] the different things that are coming in<br>[01:18] the WordPress space. So there's a few<br>[01:19] new projects. There's something called<br>[01:21] Phantom WP, WP Falcon, and Dave Gray has<br>[01:25] got a new product as well. There's loads<br>[01:27] more. We talk about WordPress events<br>[01:29] that are coming up in the next few weeks<br>[01:30] as well, and it's all coming up next on<br>[01:33] this week in WordPress.<br>[01:36] This episode of the WP Builds podcast is<br>[01:39] brought to you by GoDaddy Pro, the home<br>[01:42] of manage WordPress hosting that<br>[01:43] includes free domain, SSL, and 24/7<br>[01:47] support. Bundle that with the hub by<br>[01:50] GoDaddy Pro to unlock more free benefits<br>[01:53] to manage multiple sites in one place.<br>[01:56] Invoice clients and get 30% off new<br>[01:59] purchases. Find out more at<br>[02:01] go.me/wpuilds.<br>[02:06] Hello. Good morning, good afternoon,<br>[02:08] good evening. What was going on there,<br>[02:10] Mark? You were uh you were up something.<br>[02:13] Uh good morning, good evening, good<br>[02:14] afternoon, wherever you are in the world<br>[02:16] watching this. That's very very nice to<br>[02:18] have you with us. Um, as I always say,<br>[02:21] this work this whole show works really<br>[02:22] well when people drop comments in and<br>[02:25] um, and Taco's already put one in. Thank<br>[02:27] you, Taco. He's singing the theme tune<br>[02:29] and I have no words, Taco. That theme<br>[02:31] tune is the worst tune imaginable and I<br>[02:34] just can't be bothered to change it. So,<br>[02:36] anyway, there you are. He says, "Hi<br>[02:39] y'all from a virtually snowless vegan<br>[02:43] again after a week of beautiful white<br>[02:45] chaos." Yeah, our snow's all gone sadly<br>[02:47] now. It rained and um yeah, bit sad. It<br>[02:50] is a bit sad.<br>[02:52] >> Um but yeah, so we are going to I'm just<br>[02:54] going to go through the sort of like the<br>[02:55] housekeeping bits and then I'll<br>[02:56] introduce our fabulous panel. So the<br>[02:59] first thing to say is that if you are<br>[03:01] watching this live and you would like I<br>[03:03] don't know like your friends to join in<br>[03:04] uh pause the video or just you know open<br>[03:06] up a new tab whatever it may be and the<br>[03:09] best place to send them is right there<br>[03:12] being supported by an um go to<br>[03:14] wpbuilds.comlive<br>[03:18] once more wpbuilds.comlive<br>[03:21] if you go there on a desktop you'll have<br>[03:23] the Google like YouTube comments on the<br>[03:25] right um and if you're on a mobile it'll<br>[03:27] fall underneath the video. However, if<br>[03:29] you don't have a Google account or you<br>[03:31] don't like using a Google account, click<br>[03:32] on the video itself. Top right is a<br>[03:35] little black button which says live<br>[03:36] chat, you can click that and you don't<br>[03:38] need to be logged into anything at all.<br>[03:40] So, yeah, wpbuilds.com<br>[03:44] forwardlive.<br>[03:46] So, so, so let's uh let's go around the<br>[03:49] houses and say hi to our panelists. I'll<br>[03:51] start off with our co-host, our frequent<br>[03:54] co-host. I can't do it. I I can't manage<br>[03:56] it. There is Michelle. Hello, Michelle.<br>[03:59] >> Hello. Hello.<br>[04:00] >> Michelle is um Michelle's got a little<br>[04:02] bit of a poorly voice at the moment, so<br>[04:04] she's going to sound a little bit<br>[04:05] different, but I hope that you're uh<br>[04:07] you're able to contribute. If you need<br>[04:08] to if you need to take five and go and<br>[04:10] get some Alka-Seltzer or whatever it is<br>[04:13] >> uh that you take, feel free. You've<br>[04:15] shortened your bio, I think, have you?<br>[04:17] Or did I shorten it? I can't remember.<br>[04:18] Anyway,<br>[04:19] >> I think I shortened it a bit. Yeah.<br>[04:20] >> Yeah. Thank you. Michelle Fchette is the<br>[04:22] executive director of Post Status. And<br>[04:24] in addition to the work over there,<br>[04:26] Michelle is the podcast barista at WP<br>[04:28] Coffee Talk, co-founder of<br>[04:29] Underrepresented in Tech, creator of WP<br>[04:31] Speakers and WP Career Pages. She also<br>[04:35] co-founded sponsor EWP Speed Network<br>[04:37] Online. She writes books. She's an<br>[04:40] author, influencer, and frequent<br>[04:42] organizer and speaker at WordPress and<br>[04:43] tech events. Living outside of<br>[04:45] Rochester, New York, she is an avid<br>[04:48] nature photographer. And you can learn<br>[04:50] more about Michelle at meetmleonline.<br>[04:55] >> I I should add speaker of the year for<br>[04:58] women tech global.<br>[04:59] >> Oh. Yeah, that's that's pretty cool. I<br>[05:03] um I How long when did you get that? Was<br>[05:05] that towards the end of last year, I<br>[05:06] think, wasn't it?<br>[05:07] >> It was. I also received influential<br>[05:09] women uh of 2025 award as well. So, I'm<br>[05:13] looking at my new plaques.<br>[05:14] >> Oh, nice. Nice. You don't have them in<br>[05:15] the background. You're just keeping them<br>[05:17] in front of you, are you?<br>[05:18] >> Yeah. I mean, yeah, they're all in front<br>[05:20] of me.<br>[05:20] >> They're there.<br>[05:21] >> That was that was the space. It inspires<br>[05:23] me to continue to do better.<br>[05:24] >> Yeah. Nice. Well, congratulations for<br>[05:26] all that. And um let's hope that your<br>[05:28] voice holds out for the rest of the<br>[05:30] episode. Okay.<br>[05:31] >> So much better than it was. Yeah.<br>[05:32] >> Well, that's good. I'm pleased to hear<br>[05:33] that. Yeah, that's good. Over there is<br>[05:36] Mark. Mark Ben. How you doing, Mark?<br>[05:38] >> I'm doing fantastic.<br>[05:41] >> Mark always comes on at like 3 in the<br>[05:43] morning or something. I have no idea.<br>[05:45] >> It's a ridic It's a ridiculous time.<br>[05:47] It's I don't even I have no words. I<br>[05:50] like But you're an early bird, right?<br>[05:52] >> You just enjoy getting up.<br>[05:53] >> The older the older I get, the less of<br>[05:55] an early bird I'm becoming.<br>[05:59] >> That feeling.<br>[06:00] >> I'm not going to lie. I I I used to be<br>[06:03] an early bird, but yeah.<br>[06:05] >> I became an early bird about 18 months<br>[06:07] ago. I was predictably not that early. I<br>[06:10] could work late into the evening. And<br>[06:11] then about 18 months or so ago, I just<br>[06:13] my body just said, "No, that's it.<br>[06:15] you're gonna flip to the other side of<br>[06:16] the day and now I'm up at five mostly<br>[06:19] every morning.<br>[06:19] >> Yeah, I think that I think the exact<br>[06:21] opposite happened with me. I've always<br>[06:23] been an early bird. And then about a<br>[06:25] year ago, probably six months ago, it's<br>[06:27] been like,<br>[06:28] >> okay,<br>[06:28] >> I I can't wake up at 4 in the morning<br>[06:30] like I used to.<br>[06:31] >> Okay. I think the trick is just stay in<br>[06:33] bed all day and work on the laptop.<br>[06:35] That's the uh that's the way.<br>[06:36] >> I I like where your head's at. I really<br>[06:41] >> That's pretty.<br>[06:44] Well, there there's Mark. Mark Ben Kane<br>[06:46] joining us once more from the other side<br>[06:47] of the pond right on the west coast of<br>[06:49] the US. And last, but by no means n<br>[06:52] least is an MALT. How you doing, An?<br>[06:55] >> I'm doing good. Thank you. I'm glad the<br>[06:57] slippery slope outside is rained off now<br>[07:00] and y<br>[07:01] >> I can finally go for a walk again.<br>[07:03] >> You are just like us. Yeah, I I actually<br>[07:06] fell the other day. I I got that was<br>[07:08] carrying a car battery<br>[07:10] >> and I as I fell my legs went out from<br>[07:12] under me and I threw it up and I watched<br>[07:15] it in the air and I was thinking where<br>[07:17] this lands is really going to change my<br>[07:19] life potentially. Luckily it landed on<br>[07:21] my chest<br>[07:23] but I was thinking if that is anyway uh<br>[07:26] so slippery slopes and all that.<br>[07:28] >> So no broken nose on today's show.<br>[07:30] >> No broken tray. I was carrying on a<br>[07:32] tray. The whole thing went up. The tray<br>[07:34] landed on me. Then the battery landed on<br>[07:35] the tray. smashed the trait to bits and<br>[07:38] then luckily I'm here to tell the t. It<br>[07:40] was a good story.<br>[07:41] >> Okay.<br>[07:41] >> Yeah. Yeah. It was I was totally just a<br>[07:43] bit winded, but it was one of those<br>[07:44] moments where you know like like when<br>[07:45] you step out into the road and the car<br>[07:47] honks and you think that could have gone<br>[07:49] a different way, couldn't it? My life<br>[07:51] could have been very different. So<br>[07:52] anyway, there we go. Um<br>[07:54] >> so an joining, have you been on this<br>[07:57] particular show before? I know that<br>[07:59] you've been on the podcast with me<br>[08:00] before.<br>[08:00] >> I don't think so.<br>[08:02] >> I don't think so. First time actually.<br>[08:04] So, I sent her I sent her the link.<br>[08:07] >> You are very good. You are a very good<br>[08:09] person. Um, let's hope that this is the<br>[08:11] first time of many. Um, we're going to<br>[08:14] lean into a subject today quite a bit<br>[08:16] actually that Anne's really into. And<br>[08:17] I'll start the bio and you'll get an<br>[08:19] impression of that. So, an is an<br>[08:21] accessibility strategist who knows that<br>[08:23] while empathy matters, nothing motivates<br>[08:25] a business owner like realizing they're<br>[08:28] quietly losing serious revenue and backs<br>[08:31] by real world data and proven research.<br>[08:33] She mentors software companies,<br>[08:34] agencies, and e-commerce teams to build<br>[08:37] for everyone. She is a loud advocate for<br>[08:40] the WordPress block editor because it<br>[08:42] actually works if you take the time to<br>[08:43] learn it properly. Whether she's on<br>[08:45] stage or mentoring a development team,<br>[08:47] her focus is the same. Turning technical<br>[08:50] requirements into measurable business<br>[08:51] growth because accessibility is simply<br>[08:54] smart business. So there you go. Thank<br>[08:57] you. Thank you. Thank you.<br>[08:59] >> So there's our panel today. Um, the way<br>[09:01] that this show works is we love it if<br>[09:04] you sort of put in comments. You know,<br>[09:05] not all of them will I manage to get<br>[09:07] onto the screen because I'm trying to<br>[09:09] juggle a few things, but I'll try to<br>[09:10] keep up with what you write and if I do<br>[09:12] and something is relevant to what we're<br>[09:13] talking about, I'll pop it on the<br>[09:14] screen. So, I would encourage you to<br>[09:16] write as many comments as you possibly<br>[09:18] can. Uh, so let's have a look. Here, a<br>[09:20] coma for you. Did you fix the settings<br>[09:21] on your DSLR, Nathan? I have no idea.<br>[09:24] So, last week the the camera just kept<br>[09:26] switching off. Uh, all I have to do is<br>[09:28] lean over and press a button like that.<br>[09:30] But if it switch if it goes black,<br>[09:33] >> that's what's going on. So, apologies,<br>[09:35] panel, if that happens, we just have to<br>[09:37] cope.<br>[09:38] >> Um, what does this one say? He's back.<br>[09:40] It's um, does the power grid even work<br>[09:43] at 5:00 a.m.? Yes, just<br>[09:46] >> uh, the kettle certainly does.<br>[09:49] It's the only way to get going.<br>[09:51] Patricia's here. Hello, Patricia. She<br>[09:53] says, Patricia.<br>[09:56] >> Oh, no. again. Oh, no. Again.<br>[09:59] >> Wait, no, he's got his name right in it.<br>[10:01] Look, it says Gerard.<br>[10:02] >> Oh. Oh, great. Okay, great. That's Thank<br>[10:04] you, Gerard.<br>[10:07] >> I have no words. Uh, it's Gener.<br>[10:12] He says, "Hi, here. I have I know you<br>[10:14] I've got a total mental block with your<br>[10:16] name, Gerard. I have no idea why, but<br>[10:18] I'm extremely pleased that you<br>[10:19] >> You need You need to learn to say that<br>[10:21] in Dutch, though.<br>[10:23] >> Go on.<br>[10:26] That that was a word which I don't think<br>[10:28] I'll ever get. Say it again.<br>[10:33] >> Yeah. Well, there is a child in the way<br>[10:35] we speak Dutch in the south of the<br>[10:37] country below river. It's nest hard on<br>[10:39] your throat. You can say<br>[10:42] >> okay. Because we don't have that sort of<br>[10:44] whatever that sound was at the beginning<br>[10:46] where<br>[10:47] >> that's only when you have a cold.<br>[10:49] >> Oh. Oh,<br>[10:51] >> that is definitely not an American<br>[10:53] English sound that we make in all.<br>[10:55] >> That's right. We don't have that sound.<br>[10:57] Uh, and then James Laauo is joining us<br>[10:58] and saying, "Good morning. Thank you<br>[11:00] very much." Um, Taco, very kindly. Glad<br>[11:02] you're okay, but a bit sad that you're<br>[11:04] not sharing video footage of your<br>[11:05] battery adventure.<br>[11:06] >> Yeah. Did you get that on Ring? Ah, no<br>[11:08] Ring camera. No Ring camera footage or<br>[11:10] anything of that. No. And Elliot, last<br>[11:13] comment for now. Elliot's joining us.<br>[11:15] He's just down the road from me. Hello,<br>[11:16] Elliot. Nice to have you. So, like I<br>[11:18] said, please drop your comments in as we<br>[11:20] get going. We're WordPressy, so the idea<br>[11:23] is to do as much possible about<br>[11:24] WordPress, but we we go off pieced a<br>[11:26] little bit as well. So, here we go.<br>[11:28] We're going to go off piece a bit now.<br>[11:30] Bit of self-promotional stuff. We<br>[11:32] produce two episodes a week basically on<br>[11:34] this podcast. If you want to be kept<br>[11:35] updated via email, just put your email<br>[11:38] address into there or go to your podcast<br>[11:40] player of choice, search for WP Builds,<br>[11:42] and click follow or whatever it might<br>[11:44] be. That's probably the best way to do<br>[11:46] that. The latest episode of the podcast<br>[11:48] was with I I called him Sir Dave Foy<br>[11:52] because I hold him in such high regard.<br>[11:54] Uh Dave Foy has he's done like loads of<br>[11:57] courses about Elementor and bricks and<br>[11:58] things like that. He's releasing a lot<br>[12:00] of new materials, but he's got this<br>[12:01] whole different way of doing it now.<br>[12:03] He's going to be doing live cohort<br>[12:05] learning. So he's instead of doing this<br>[12:06] like Leviathan course, um he's going to<br>[12:09] be doing it per week and then getting<br>[12:11] taking feedback from his from his<br>[12:13] customers each week and then doing the<br>[12:15] next week on a rolling schedule so he<br>[12:17] keeps up to date with them. Anyway,<br>[12:18] that's what that podcast episode there<br>[12:20] is all about is him trying to figure<br>[12:23] that out and um anyway there there is<br>[12:26] the episode that was number 4 I think<br>[12:29] 51. So we're fast approaching. By the<br>[12:32] end of this year, I'll be on 500 of that<br>[12:34] uh particular podcast. Speaking of<br>[12:36] which, I'm going to blow my own trumpet<br>[12:39] again. Um, this week I'm releasing the<br>[12:42] 200th episode of the WP Talon podcast.<br>[12:46] >> I know it's got two zeros. I feel like I<br>[12:48] should have a cake or something. But<br>[12:51] >> I feel like we should have sound effects<br>[12:52] where like all of a sudden like insert a<br>[12:54] pause here.<br>[12:55] >> That's right. No, I'm not doing<br>[12:56] anything. I'm just releasing it as<br>[12:58] exactly the same as all the others. I<br>[13:00] don't even mention it. I recorded my<br>[13:02] intro earlier today and then I got to<br>[13:04] the end of it and thought I didn't<br>[13:05] mention that it was the second 100 one,<br>[13:07] but anyway, whatever. Um, so anyway,<br>[13:10] there we go. That's the WP Builds<br>[13:11] promotional stuff, right? Each week the<br>[13:15] guests get to drop in a few links if<br>[13:17] they so choose and uh they get featured<br>[13:19] toward the beginning of the show. That<br>[13:20] was Michelle's idea. Thank you for that.<br>[13:22] And um today uh An Mika has dropped in<br>[13:25] this one. It's called well it's from the<br>[13:27] SEM Rush or SEMrush website. is called<br>[13:29] why accessibility matters more than ever<br>[13:32] for SEO purposes. I had a read through<br>[13:34] but I I wondered if um an if you wanted<br>[13:36] to take the helm on this and tell us why<br>[13:38] you included it.<br>[13:39] >> Yeah, the reason why I included it is<br>[13:41] because for years um especially for<br>[13:45] those who started with accessibility<br>[13:47] even earlier than I did, our biggest<br>[13:50] frustration has always been, "Yeah, but<br>[13:53] where are the numbers? Give us the<br>[13:56] numbers. Give us the data." And I'm<br>[13:58] like, "Yeah, sure. Throw your common<br>[14:00] sense out of the window and just wait<br>[14:02] for people to send you the data." Right?<br>[14:05] So, um, and then I was, um, always<br>[14:09] talking about and many of my colleagues<br>[14:11] as well about SEO is incredibly,<br>[14:14] uh, highly connected to accessibility.<br>[14:18] And, um, something people tend to forget<br>[14:20] is that the main customer for Google is<br>[14:23] not the advertisers, it's the users.<br>[14:27] Right. So they will prioritize that and<br>[14:31] so they did this research with real<br>[14:34] numbers. If you go to this article, it<br>[14:36] will be in the show notes I think.<br>[14:38] >> Yeah, it will.<br>[14:38] >> Um you can also link to the full<br>[14:40] research page u where they have<br>[14:42] everything and it just shows that<br>[14:46] traffic increases when your compliance<br>[14:49] increases. And I I'm really actually bit<br>[14:52] sad that they use the word compliance,<br>[14:54] you know, because I'm really like go<br>[14:57] away with your compliance. It should be<br>[14:59] part of your website or app hygiene.<br>[15:03] It's website hygiene. And the thing is,<br>[15:07] if you look at it being compliant,<br>[15:10] you'll never win because if your<br>[15:12] competitor is looking to be more<br>[15:15] accessible than you are, they are miles<br>[15:17] ahead of you. And then this research<br>[15:20] showed that 27% of more keywords ranked<br>[15:24] with accessibility improvements. And<br>[15:26] this is also important. This is why I<br>[15:28] love this article because it is about<br>[15:30] progress over perfection. People are<br>[15:33] like, "Oh, how am I going to start?" And<br>[15:35] then they don't start. They get totally<br>[15:36] get paralyzed with where to start. And<br>[15:38] if they would just start with getting<br>[15:40] heading order, okay, and getting color<br>[15:43] contrast done better and all of that.<br>[15:46] Well, you know, I'm gonna how do you say<br>[15:48] that? I'm going to segue too much. So,<br>[15:50] forget about Yes, that is the one.<br>[15:53] >> And then one of the most important<br>[15:55] things here when it when you look at SEO<br>[15:58] is the incredible boost in authority<br>[16:02] score for compliant sites.<br>[16:06] It's just it's just crazy.<br>[16:08] I'll read from the the top of the<br>[16:10] article actually because it kind of<br>[16:11] gives it so you know they tried to<br>[16:13] establish the credentials of the people<br>[16:14] doing it which are pretty formidable<br>[16:16] actually. So collaboration with<br>[16:18] accessibility checker.org built<br>[16:21] rush uh 10 and this is analysis of<br>[16:23] 10,000 websites and they were trying to<br>[16:25] figure out and like you said they use<br>[16:27] the word compliance where their<br>[16:28] accessibility compliance impacts online<br>[16:31] discoverability. In other words, if you<br>[16:33] you put the effort in on the<br>[16:34] accessibility side do you get more<br>[16:36] visitors? That's kind of the bottom<br>[16:37] line. And the study revealed that the<br>[16:39] major I'm just reading this by the way,<br>[16:41] you know, off the site. The study<br>[16:42] revealed that the majority of websites<br>[16:44] still fail to meet accessibility<br>[16:46] standards. Yet across the fuller sample,<br>[16:49] higher accessibility scores correlated<br>[16:51] with stronger search outcomes, including<br>[16:55] increases in organic traffic, broader<br>[16:58] keyword visibility, and stronger<br>[17:00] authority scores. Now, I'm no SEO<br>[17:03] expert. That is all a bit of a mystery<br>[17:05] to me. But I I'm I'm not entirely<br>[17:09] surprised that this is true, that this<br>[17:11] has been written down, but I am I am<br>[17:12] glad that somebody wrote it down in<br>[17:14] black and white so that you can kind of<br>[17:15] point to this forever more and say,<br>[17:17] "Okay, you now have yet another reason<br>[17:20] >> exactly to do this work." And and I'm<br>[17:22] I'm going to take this one a notch<br>[17:24] further<br>[17:25] >> um because I'm sure that soon the next<br>[17:28] articles will come out because LLMs<br>[17:32] >> y<br>[17:33] >> are not Google and they look at your<br>[17:35] website differently and I like once a<br>[17:38] week I'm doing this deep search. It's<br>[17:41] becoming a bit of a costly hobby these<br>[17:43] days. Like are there new new uh studies<br>[17:47] out there why accessibility also<br>[17:50] influences how an LLM picks up on you?<br>[17:53] Because if you think structured data is<br>[17:56] everything, well, bye-bye.<br>[18:00] >> Um, okay. So, the the the the URL for<br>[18:03] this will be in the show notes. So if<br>[18:05] you do subscribe like I said earlier or<br>[18:06] what have you or you visit the website<br>[18:08] tomorrow episode whatever this is um<br>[18:11] then go and check it out you it'll be<br>[18:13] under the community section by<br>[18:15] accessibility matters more than ever for<br>[18:17] SEO performance will be the link that<br>[18:19] you're looking for. Uh Michelle um or<br>[18:22] Mark anything to add to that or shall we<br>[18:24] move on?<br>[18:26] >> Um<br>[18:26] >> I I don't think I could improve upon<br>[18:28] what Anamica says.<br>[18:29] >> Yeah. Yeah. And and I know we're going<br>[18:33] to be talking more about accessibility.<br>[18:34] >> We are there's a few more accessibility<br>[18:36] pieces. And it was pure coincidence that<br>[18:38] and and was on today. But uh yeah,<br>[18:40] there's more data at the bottom which I<br>[18:42] didn't highlight, but you can see that<br>[18:43] there's a whole lot more if you're<br>[18:44] looking at the video for this. You can<br>[18:45] see there's all sorts of other stuff. Um<br>[18:48] you can explore the the survey properly,<br>[18:50] but this is just a heads up that that<br>[18:51] exists. So thank you for bringing that<br>[18:53] to our attention. That's a good one. Um<br>[18:56] so this next one also in the realm of<br>[18:58] accessibility. This is um uh on the<br>[19:01] accessible web design um is what it's<br>[19:04] called, but it's Joe Doulson.com. Joe<br>[19:06] Doulson is a a friend of the podcast. In<br>[19:08] fact, I'll just get this one out the way<br>[19:10] quickly whilst we're here. It's sort of<br>[19:12] another self-promotional bit, I'm<br>[19:13] afraid, but it sort of matches very care<br>[19:16] very closely. I did an episode of um<br>[19:19] with Joe Doulson with our accessibility<br>[19:20] show. We're on number nine now. and he<br>[19:23] picked out this um this website which<br>[19:25] had been sort of like pushed in socials<br>[19:27] by automatic and various other um<br>[19:31] various other things and uh Joe was just<br>[19:34] sort of saying okay it this this was<br>[19:35] supposed to be and I use air quotes it<br>[19:38] was an example of the best in WordPress<br>[19:40] and Joe was just sort of picking it<br>[19:42] apart from an accessibility point of<br>[19:44] view and whilst he liked the website he<br>[19:46] said you know there was definitely a lot<br>[19:47] of work to be done so if you enjoy that<br>[19:49] kind of content uh and you enjoy looking<br>[19:51] an expert figure out where accessibility<br>[19:53] problems are and what to do about them.<br>[19:56] Go and have a look at that. It's about<br>[19:57] 40 minutes long. Right.<br>[19:58] >> I just I just realized I should have<br>[20:01] given you another link as well.<br>[20:03] >> Ah, another time. That's a there's a<br>[20:05] good reason to drag you back onto the<br>[20:07] show on another page.<br>[20:09] >> So, the reason I've put this one in uh<br>[20:12] on Joe's website, it's called judging<br>[20:14] severity and accessibility issues. is<br>[20:16] because<br>[20:18] this is so obvious but actually I never<br>[20:21] thought about it this way which is<br>[20:23] ridiculous. Joe makes the point that<br>[20:25] when you're so let's say you've<br>[20:26] inherited a website or something like<br>[20:28] that and you're trying to make a<br>[20:29] judgment about what do we tackle first<br>[20:33] his point is well duh tackle the stuff<br>[20:36] which gives the biggest impact to the<br>[20:38] end user to the people using the<br>[20:41] website. Don't go for the stuff which is<br>[20:43] necessarily easiest for you to fix,<br>[20:46] which you know, I guess if you're a<br>[20:48] developer, that kind of makes common<br>[20:49] sense. You can go to your boss and say,<br>[20:50] "Look, here's all the things I ticked<br>[20:52] off." But his point is, and there's<br>[20:54] three points, um, look at the content.<br>[20:57] If there's critical content that the<br>[20:59] users need to be able to see or gain<br>[21:02] access to, do that first. Uh, yeah,<br>[21:06] okay, that makes complete sense. Then<br>[21:08] his second metric is how frequently does<br>[21:12] this thing occur. In other words, I<br>[21:13] don't know if there's a if there's a<br>[21:15] very important button to download the<br>[21:17] PDF or whatever it may be and that's on<br>[21:19] every page but the button is not<br>[21:21] accessible, we'll do that because that's<br>[21:23] a frequently occurring thing on the<br>[21:25] website. And then um his last one is um<br>[21:29] it's just a challenge really about how<br>[21:31] easy it is to overcome. So that's the<br>[21:33] one that I imagine most developers<br>[21:34] tackle first. You know, how easy is it<br>[21:36] for me to fix? I'll do that first<br>[21:38] because that's a nice easy one. Uh his<br>[21:40] is yeah it how easy is it for the user<br>[21:43] to get around and make a sort of<br>[21:44] priority list of those kind of things.<br>[21:46] >> So anyway, great wisdom from Joe and<br>[21:50] kind of nice to be confronted by<br>[21:51] something that<br>[21:53] >> is now really obvious to me but until I<br>[21:56] read it uh wasn't all that obvious. So<br>[21:59] again Mark and Michelle if anybody's got<br>[22:01] anything they want to contribute please<br>[22:03] feel free.<br>[22:05] Um, I I I just might share an experience<br>[22:08] I had with Joe once. He sat down with me<br>[22:10] on a definitely this was I I have to say<br>[22:14] this was not MainWP. This was a<br>[22:16] different product that I sat down with<br>[22:18] him on. This was like five or six years<br>[22:20] ago anyway. and uh he went through uh<br>[22:25] what I was showing him and and oh my<br>[22:29] goodness, I had five pages of notes by<br>[22:31] the time I was done sitting and it was<br>[22:34] awesome of him to take the time<br>[22:36] >> to just do that with me. Um I am not an<br>[22:40] accessibility expert uh like other<br>[22:43] people on this show are, but I've<br>[22:45] learned so much over the last few years<br>[22:47] and Joe's been a big part of that. So,<br>[22:49] just kind of wanted to shout out to Joe<br>[22:50] that you know.<br>[22:52] >> Yeah. There's something I'd like to know<br>[22:54] from you about that though, Mark. How<br>[22:56] Okay. Do you remember how you felt<br>[22:59] that first in these first moments when<br>[23:01] you got this list? What what happened<br>[23:04] >> in your um<br>[23:09] in my head? I I will say that I was not<br>[23:12] shocked.<br>[23:13] Um it was a little bit uh embarrassing<br>[23:18] I'd say. But the worst experience I had<br>[23:21] actually was about 10 years ago when I<br>[23:23] was uh sitting down with someone. We<br>[23:25] actually had a word camp that I had<br>[23:27] organized and this this woman, she was<br>[23:30] blind. She was one of the presenters.<br>[23:32] She was blind and she sat down with our<br>[23:35] software to show me the struggles she<br>[23:37] had to go with. And that was my first<br>[23:39] exposure to like the true<br>[23:42] uh not just hurdles that we needed to to<br>[23:47] overcome, but the things that I had<br>[23:48] never thought of because I'm not blind<br>[23:50] and I I was not putting myself in their<br>[23:53] shoes and and uh so that kind of opened<br>[23:56] the door for me to become a little bit<br>[23:57] more empathetic uh towards it. When Joe<br>[24:00] sat down with me, I already knew that he<br>[24:02] was going to tear it apart because I<br>[24:04] already I've known Joe for a long time<br>[24:06] and and and<br>[24:08] have a ton of respect for him. So, uh it<br>[24:11] was uh one of those I shook my head a<br>[24:15] little bit, but none of it was I I<br>[24:17] wasn't surprised. I I don't know how to<br>[24:19] I'm trying to think on my head. I may be<br>[24:21] embarrassed a little probably. I'm<br>[24:23] always I'm always asking because some<br>[24:25] people are like it's like someone stole<br>[24:29] the air from their lungs, you know, or<br>[24:31] they they're like or I'm never going to<br>[24:33] fix that.<br>[24:34] >> Yeah, that was the experience I had that<br>[24:36] first time when when the this this woman<br>[24:39] was not just visually impaired, she was<br>[24:42] completely blind and<br>[24:44] >> Yeah.<br>[24:45] >> and um an amazing person and she was so<br>[24:49] patient with me. I I mean if I were her,<br>[24:52] I would have like smacked me upside the<br>[24:54] head five different ladies, but she was<br>[24:57] so patient and so kind and so<br>[24:59] understanding and and my whole thought<br>[25:03] the whole time is like we are not<br>[25:04] servicing these people the way that we<br>[25:06] should be.<br>[25:07] >> Well, one of the things that that should<br>[25:10] also be part of your hygiene,<br>[25:14] you know, when you are building a<br>[25:16] product is the actual user testing.<br>[25:20] Every time I see that this process has<br>[25:23] been skipped and and just disregarded,<br>[25:28] you know, in the end it's going to cost<br>[25:30] you so much. And I'm not talking only<br>[25:33] about people who have um who are who are<br>[25:38] blind or visually impaired. A group that<br>[25:42] everybody seems to forget is the one<br>[25:44] that I am uh part of is people with<br>[25:48] cognitive issues like ADHD,<br>[25:52] >> autism. I have a combination of that.<br>[25:55] >> Sometimes I land on websites and I'm<br>[25:58] just like,<br>[26:00] >> yeah,<br>[26:02] >> as a fellow ADHDer, I I totally relate<br>[26:06] to that. And um I going further I<br>[26:09] everyone here I think knows who Jen<br>[26:11] Harris is.<br>[26:12] >> Yeah.<br>[26:12] >> And I did I did an interview with her a<br>[26:15] few months ago for MainWP which is up on<br>[26:18] YouTube. My little bit of self-promotion<br>[26:19] there.<br>[26:20] >> I'm going to go and watch that.<br>[26:21] >> And she opened my eyes, pardon the pun,<br>[26:25] in so many ways because what she what<br>[26:28] she did so well at explaining and I<br>[26:30] could I you need to watch it because I<br>[26:32] can't explain it the way she did. Um<br>[26:35] what she did very well was explain how<br>[26:38] accessibility<br>[26:40] isn't just for people with um<br>[26:43] disabilities or anything. It actually<br>[26:45] affects everybody. An example she gave<br>[26:47] is like what if you're on a train and<br>[26:49] you're and and it's you know vibrating<br>[26:51] and you're trying to read something and<br>[26:53] and things like that. And so and and and<br>[26:56] what it helped helped me to understand<br>[26:58] is that we are losing a lot of business<br>[27:01] as developers and and uh product uh<br>[27:06] producers just because we're not taking<br>[27:09] into consideration that that everybody<br>[27:12] needs accessibility whether they realize<br>[27:14] it or not. and she was she was very good<br>[27:17] at like explaining that to like a third<br>[27:21] grader who didn't really grasp you know<br>[27:24] any of these things until it was brought<br>[27:25] to my attention. So um<br>[27:27] >> yeah it was it was really really<br>[27:30] >> you know there there are a lot of<br>[27:31] politically very incorrect uh examples<br>[27:34] that I always use when I do live talks<br>[27:37] on stage where I'm not getting filmed.<br>[27:41] Well, I'll I'll I'll give you uh two of<br>[27:45] the um not so uh politically incorrect<br>[27:49] ones. Um one of them is a massive<br>[27:52] hangover.<br>[27:54] >> Oh,<br>[27:55] >> going online shopping with a massive<br>[27:57] hangover because you forgot to go to the<br>[27:59] supermarket.<br>[28:01] >> And another one that people always<br>[28:04] forget is hay fever.<br>[28:08] >> Okay. Suddenly your eyes Yeah. Yeah. you<br>[28:10] you get fuzzy, you get dizzy, you you<br>[28:13] have trouble seeing and your patience is<br>[28:16] a lot less than um<br>[28:20] than normally people get<br>[28:22] >> and I actually know about I think it's<br>[28:24] Japanese island. I still have some draft<br>[28:27] article about that lying around where<br>[28:29] due to some genetic issue. Um the<br>[28:34] largest portion of the um population<br>[28:37] there has a fever.<br>[28:40] >> Yeah.<br>[28:41] >> Entire island.<br>[28:42] >> Okay. A whole island full of<br>[28:44] >> aver specific island. I don't know which<br>[28:46] one it was. I will publish that article<br>[28:49] at some point. I just have to hit<br>[28:50] publish.<br>[28:51] >> Yeah. That's kind of curious.<br>[28:52] >> I want to sell tissues on that island.<br>[28:54] >> That's a great<br>[28:56] Great business to be in. Yeah. Yeah. Um,<br>[28:59] so, so Joe's piece here, judging<br>[29:01] severity and accessibility issues. It's<br>[29:03] really short. It'll take you five<br>[29:04] minutes to read, but it's a really, it<br>[29:06] kind of, it was such an obvious thing,<br>[29:09] but such an a thing that I hadn't really<br>[29:11] thought about. The long and the short of<br>[29:12] it is basically tackle the things which<br>[29:14] help the most people first. Don't do it<br>[29:16] from your point of view first. The thing<br>[29:18] I would add about accessibility also is<br>[29:20] that it is much easier to build an<br>[29:23] accessible site than to retrofit an<br>[29:25] accessible site.<br>[29:26] >> So don't build a site thinking I'll add<br>[29:28] that later<br>[29:30] >> because you won't like yourself later.<br>[29:32] You'll you'll be like yesterday Michelle<br>[29:34] was horrible because today Michelle has<br>[29:36] to retrofit something. So build build<br>[29:39] accessibly. Obviously we inherit sites<br>[29:42] that we have to do that. There's always<br>[29:43] going to be that. But don't plan<br>[29:45] accessibility as the second set of<br>[29:48] things you're going to do where step two<br>[29:50] build with accessibility in mind.<br>[29:52] >> Nice. So that is our second piece in<br>[29:55] terms of accessibility. And I think<br>[29:57] there is another one coming in a little<br>[29:59] while. So we'll come to that in a<br>[30:01] moment. There's a uh a tool a WordPress<br>[30:03] plug-in which we'll mention as well. But<br>[30:05] for now we're going to segue to this<br>[30:07] piece which came directly from Mark.<br>[30:10] Mark I don't know if because you dropped<br>[30:11] it in. Do you want to take the the helm<br>[30:13] on this one?<br>[30:14] >> Well, this was a this was an article uh<br>[30:16] actually Dennis shared it with us over<br>[30:18] the weekend uh that Katie Keith wrote<br>[30:21] and uh it it's Katie being Katie, which<br>[30:26] is you know what I like about Katie in<br>[30:29] general is that she is very data driven.<br>[30:32] So yeah,<br>[30:33] >> she she will start out with a you know a<br>[30:36] kind of a she'll posit something and<br>[30:38] then she'll get the data to back it up<br>[30:40] or or to to get details. And um the the<br>[30:46] uh<br>[30:49] she starts out with at barn 2, our new<br>[30:50] plug-in sales were down 17.8% in 2025.<br>[30:54] And the general idea is that plug-in<br>[30:56] sales are down uh were down in 2025.<br>[31:01] Uh and um so then she followed up with a<br>[31:05] survey to say to to kind of find out how<br>[31:08] that broke down um and how the plug-in<br>[31:13] role relates to sales performance<br>[31:16] covers kind of like the new versus uh<br>[31:18] versus uh returning customers or<br>[31:21] renewals. And it seemed like renewals<br>[31:23] stayed pretty solid, but the the new<br>[31:25] customers uh are are the area that kind<br>[31:29] of dropped. And I find that um not<br>[31:33] surprising. It kind of goes to this<br>[31:35] whole idea that fewer and fewer new<br>[31:37] people are coming into WordPress and and<br>[31:39] it might feed into that.<br>[31:41] >> Uh but I also feel like uh you know the<br>[31:45] niches have more people in the in the<br>[31:46] playing field as well. So it's probably<br>[31:49] distributed a little bit more. uh among<br>[31:52] that. Um so this goes into the thing<br>[31:55] that I found really interesting which<br>[31:58] was uh about replaceability and what she<br>[32:02] found is that the plugins that<br>[32:07] cons continue to to have solid sales<br>[32:10] were the ones that people might consider<br>[32:12] to be irreplaceable.<br>[32:14] >> Yeah. Um,<br>[32:15] >> and and of course that, you know,<br>[32:18] everybody wants their plugin to be<br>[32:19] irreplaceable and there's different<br>[32:21] things that can go into what what makes<br>[32:24] it irreplaceable. Um, I think I have a<br>[32:29] whole bunch of thoughts on that in I'm<br>[32:30] still thinking about this this question.<br>[32:33] Uh, as a marketer, you think about that<br>[32:35] constantly. Um, what can we do to make<br>[32:38] our plug-in more irreplaceable? I think<br>[32:40] to start with, you make a plugin that<br>[32:42] just works. And I'm not talking about a<br>[32:44] plugin that works. I'm talking about one<br>[32:45] that just works, right? So you click a<br>[32:47] button and click a button and it just<br>[32:49] works.<br>[32:50] >> And I think that's where you start. Um,<br>[32:53] and then there's different ways that you<br>[32:54] can make it irreplaceable. If you run a<br>[32:56] SAS model, it's it's a little bit easier<br>[32:58] maybe to make it irreplaceable because<br>[33:00] you're kind of controlling the data and<br>[33:02] the and the platform and and all of<br>[33:04] that. Um, but it also I I also feel like<br>[33:09] the more uh robust a plugin is um the<br>[33:13] more irreplaceable it can become because<br>[33:16] of the fact that it might<br>[33:18] uh take a little bit more effort to<br>[33:20] switch from one to another. So that kind<br>[33:23] of can make it irreplaceable as well.<br>[33:26] >> So there's a whole bunch that goes into<br>[33:27] it. It's a really interesting article. I<br>[33:29] I won't you know I I I won't go into all<br>[33:34] the details and like I said my brain is<br>[33:35] still kind of processing this. Um<br>[33:38] >> well what what I found kind of<br>[33:39] interesting was you know firstly Katie<br>[33:42] is probably the most um how to describe<br>[33:45] it. Honest. Let's go with that. Um she's<br>[33:48] very honest to the point where even in<br>[33:51] failure she'll tell everybody about the<br>[33:53] things that that have failed for her.<br>[33:55] Whereas I think I think that's that's<br>[33:56] not typical<br>[33:58] >> um in almost every part of life. You<br>[34:00] know, when you ask people how they're<br>[34:01] doing and what have you, you know,<br>[34:02] they'll sort of gloss over that. Katie,<br>[34:05] not in a not in a kind of like, oh, poor<br>[34:07] me kind of way, but in a oh, this<br>[34:08] happened to our business, right? This<br>[34:11] curious, wow, how did that happen? So,<br>[34:13] she comes from the point of view that<br>[34:14] their sales were down. And of course, I<br>[34:17] don't think firstly that most companies<br>[34:18] would admit that. You would never hear<br>[34:20] that. But this article is a completely<br>[34:22] voluntary offering of that. She's<br>[34:24] telling us, she doesn't have to tell us,<br>[34:26] but she tells us. And then what kicks in<br>[34:29] for Katie isn't the normal cycle of the<br>[34:31] skies falling in. It's okay, what the<br>[34:32] heck can we do about that?<br>[34:34] >> What what what are the reasons that this<br>[34:36] might be? And so she went out onto<br>[34:38] Twitter, did a poll, found that this<br>[34:41] broadly speaking was the case across the<br>[34:44] board. You know, we're not in that sort<br>[34:45] of barnstorming area that we might have<br>[34:47] been five years ago. And and then drew<br>[34:50] some inferences from from some of the<br>[34:51] questions that she asked. And this whole<br>[34:53] thing about um irreplaceability<br>[34:57] seemed to be a central pillar of her<br>[34:58] argument. You know, if you've got a<br>[35:00] plug-in which literally can't be swapped<br>[35:02] out for somebody else's, then you're on<br>[35:05] to solid ground. That that seems to be<br>[35:07] something which either flatlined or or<br>[35:09] improved sales. You know, the numbers<br>[35:11] went up. Um uh so that whole replace<br>[35:15] thing was important. And then the other<br>[35:17] thing which I thought was important<br>[35:19] which came out was this the third<br>[35:20] question was um companies that partnered<br>[35:24] up with other people and and obviously<br>[35:26] you know there's a wide gamut of what<br>[35:28] that could mean but organic search<br>[35:30] didn't seem to help. Premium products in<br>[35:34] a marketplace like WordPress.org didn't<br>[35:36] seem to help. there didn't seem to be a<br>[35:38] correlation in her data between making a<br>[35:40] free version and success in 2025 or<br>[35:43] organic search, you know, SEO<br>[35:44] optimization and success. The real<br>[35:47] success seems to have come out with with<br>[35:49] partnering with people. So, like-minded<br>[35:51] companies, you know, MainWP exemplify<br>[35:53] this. They're really good at partnering<br>[35:55] with other likeminded but not<br>[35:58] overlapping businesses. Wi-I which by<br>[36:00] the way plug number two anybody who<br>[36:02] wants to uh is interested in partnering<br>[36:05] with MainWP please contact me I'm open<br>[36:08] and all ears<br>[36:09] >> well yeah no but that's that's precisely<br>[36:12] I I remember I did a podcast episode<br>[36:14] with the um with the the analytics guys<br>[36:16] the independent analytics it just felt<br>[36:18] like a perfect overlap and I you've now<br>[36:21] ended up partnering with them which is<br>[36:22] absolutely perfect but that's that seems<br>[36:25] to be a real a real successful way<br>[36:27] partnering with other people I don't<br>[36:28] know if that means like partnering with<br>[36:30] you know like this kind of thing this<br>[36:32] sort of show whether you partner with<br>[36:33] media organizations or stuff like that<br>[36:35] don't know if that's rolled into it but<br>[36:37] it certainly seems to have um yeah and<br>[36:39] you can see in this graph the growth is<br>[36:41] the pink area and you can see really<br>[36:42] it's the the one that sort of dominates<br>[36:44] there was no decline in sales if you<br>[36:47] were to be partnering with people. So<br>[36:48] that's kind of the the long and the<br>[36:50] short. So, if you're looking at your<br>[36:51] numbers this year, um, or rather from<br>[36:54] last year 2025, and you think, gosh,<br>[36:56] it's flatlined or it's gone down,<br>[36:58] definitely have a look at this because<br>[36:59] Katie's got some, uh, some wisdom for<br>[37:01] you. So, I will link to that in the show<br>[37:03] notes. And Michelle, anything to add to<br>[37:05] that before we wrap on.<br>[37:07] >> I I talked to a lot of people and I'm<br>[37:09] not going to name names, of course, but<br>[37:11] there all the plug-in owners I have been<br>[37:13] speaking to lately are asking me, am is<br>[37:15] it just me or are sales down everywhere?<br>[37:17] >> Yeah, it's everywhere. And so it really<br>[37:19] is everywhere. And so if you are<br>[37:21] experiencing that sales are down, don't<br>[37:23] lose heart. It's not you, it's the<br>[37:25] market right now.<br>[37:25] >> Yep. Yep. Yep. But it would appear that<br>[37:28] there are clever things that you can do<br>[37:30] >> that Katie is now obviously beginning to<br>[37:32] do or has already done that might<br>[37:34] mitigate that problem a little bit for<br>[37:35] you. Yeah. Sorry, an<br>[37:37] >> Yeah, I Yeah. Okay.<br>[37:39] >> No, no, I was saying that I think I<br>[37:40] interrupted you, so I was Yeah.<br>[37:44] So yeah, um I um it just reminds me I<br>[37:48] think I shared the link with you in<br>[37:50] hindsight. There is this great interview<br>[37:53] um on Open Channels FM<br>[37:58] um where they did a talk with uh Tim<br>[38:01] Moner and Sandra Kersonen, Sandra Kurt<br>[38:04] from Grade and actually Grade is doing<br>[38:07] the opposite. So they are showing growth<br>[38:10] and growth but they're different.<br>[38:12] They're different from anyone. And I<br>[38:13] think they're also interesting to follow<br>[38:15] for anyone because they do talk about<br>[38:18] how they do that, where they go there.<br>[38:21] People I remember people laughing at<br>[38:23] them three years or four years ago when<br>[38:26] they saw great pricing because they're<br>[38:28] not the typical WordPress pricing and<br>[38:30] people were crying murder and saying,<br>[38:32] "Oh, they're way too expensive. They're<br>[38:35] going to die. They'll be off the grid<br>[38:37] within a year." They're not. But they're<br>[38:40] also very good at making these<br>[38:43] partnerships and um listening to Sandra<br>[38:46] Kurtza is really interesting. I can<br>[38:49] really recommend you do this. I learn<br>[38:50] from her all the time. I I am advising<br>[38:54] them on accessibility and stuff. Um but<br>[38:57] there is this is a great podcast that<br>[38:59] they did. Oh, you've got it on screen.<br>[39:02] >> Yeah, I got it on the screen. So, it's<br>[39:03] um it's on Open Channels FM.<br>[39:06] >> The episode that you're after 18th of<br>[39:08] December 25 if that helps. So, you can<br>[39:10] probably just Google open web<br>[39:12] conversations. Sorry, not Google in your<br>[39:14] podcast player of choice. You could<br>[39:15] probably just type that in open web<br>[39:17] conversations and it was<br>[39:18] >> yeah,<br>[39:18] >> episode 708. Um,<br>[39:20] >> it's um it's a brilliant episode and<br>[39:23] it's probably also confronting for some<br>[39:25] people, but you can learn so much from<br>[39:27] it. I mean, even I learned from it. I<br>[39:29] mean,<br>[39:29] >> yeah. Yeah. Yeah. Uh, okay. So,<br>[39:31] >> I'm not into that.<br>[39:32] >> Yeah, we will um we will I'll add that<br>[39:34] into the show notes as well. delivering<br>[39:36] customer value through collaborative<br>[39:38] ecosystem partnerships and interestingly<br>[39:41] Jonathan Wald is on the um he's doing<br>[39:43] the interviewing and I know that's one<br>[39:44] of his<br>[39:45] >> uh big things as well. He loves<br>[39:47] partnerships and all of that kind of<br>[39:49] stuff. So that's perfect. Right. So<br>[39:51] there we go. That was Katy Keith's<br>[39:53] article which ultimately led to this<br>[39:54] secondary piece. Let's move it on<br>[39:56] slightly. Going to social network. I'm<br>[39:59] not logged in so it looks a bit empty.<br>[40:00] There are lots of comments on this but<br>[40:02] you can't see them because I'm not<br>[40:03] logged in. But um this is Steve Burge.<br>[40:07] This is there isn't a story here.<br>[40:09] There's probably not much for us to<br>[40:10] discuss. But Steve Burge who is the I<br>[40:13] don't know if he's the founder. He's<br>[40:14] certainly the owner. I think he's the<br>[40:15] founder of Publish Press and a variety<br>[40:17] of other WordPress plugins. He being<br>[40:20] with Publish Press, which enables you to<br>[40:22] do all sorts of things around hitting<br>[40:23] the publish button in the WordPress<br>[40:25] editor. he's been very keen to to keep<br>[40:28] track of the collaborative editing, this<br>[40:30] sort of Google Docs style thing that we<br>[40:32] may may or may not yet get at some<br>[40:35] point. Um, we've had various<br>[40:37] conversations about it and honestly the<br>[40:39] whole enterprise felt like it was miles<br>[40:41] away until fairly recently and I just<br>[40:44] caught sight of this just the other day<br>[40:45] and I haven't got any I haven't tested<br>[40:47] it or anything but he's he's not a man<br>[40:50] to sort of throw incendurary stuff out<br>[40:52] there. So this is very positive. He<br>[40:54] says, "I've been testing collaborative<br>[40:56] editing experiments in WordPress for<br>[40:58] years. Those early versions never work<br>[41:00] smoothly. Now, and this was written, oh,<br>[41:03] I don't know, four or five days ago.<br>[41:05] Now, with the Gutenberg plug-in for the<br>[41:07] first time, it works great right out of<br>[41:09] the box. Google Docs style editing in<br>[41:11] WordPress is here. Give it a try." So,<br>[41:14] honestly, there's there's there's just<br>[41:16] news there. If you want to go and check<br>[41:17] it out, go and get the Gutenberg plugin<br>[41:20] um which adds<br>[41:22] like a beta version or a beta version if<br>[41:25] you like of features on top of your<br>[41:26] normal block editor and uh and it's in<br>[41:29] there and there's an image that's<br>[41:30] attached to it which I apparently can't<br>[41:32] zoom. There we go. Uh where you check a<br>[41:34] box collaboration add real time editing.<br>[41:37] You just tick that box and yeah, there<br>[41:39] you go. So, I don't know if anybody<br>[41:41] wants to add anything to that, but I<br>[41:43] just trust that Steve wouldn't have said<br>[41:44] that unless there was something worth<br>[41:45] looking at. So, go and check that out.<br>[41:47] >> No, I think it's it's really cool<br>[41:49] because if if agencies and anyone<br>[41:52] building websites would calculate<br>[41:54] through how much time they lose<br>[41:56] >> Yep.<br>[41:56] >> on um inefficient or efficient way of<br>[41:59] working. I mean um 12 times 5 minutes is<br>[42:03] an hour. People tend to forget that.<br>[42:05] >> Yeah. I had to just do the maths then<br>[42:07] and I was I was thinking is that right?<br>[42:09] That doesn't seem right. It's right. Uh,<br>[42:11] okay. So, there's Steve. Right. Let's<br>[42:13] move on then. Um, this is a sort of<br>[42:16] community-based piece if you like. Uh,<br>[42:18] Big Bite. It's an an agency, an<br>[42:21] enterprise agency. I I confess I don't<br>[42:23] know a lot about them, but I've heard<br>[42:24] the name banded about around lots and<br>[42:26] lots of times. I think they had, you<br>[42:28] know, like really large clients and<br>[42:30] things like that. They uh they began 15<br>[42:31] years ago in uh Teside, which is not<br>[42:34] that far from me, a little bit north<br>[42:36] where I live. um they have now uh joined<br>[42:39] forces with WP Engine. They've been<br>[42:42] consumed by WP Engine and and I'll just<br>[42:46] read out the the important bit. You<br>[42:47] know, this is a marketing piece just<br>[42:49] explaining what's going on and what have<br>[42:51] you. So, it says as we transition into<br>[42:53] WP Engine, we'll gradually shift from<br>[42:54] client services to product development.<br>[42:57] We won't be taking on new projects. will<br>[42:59] be putting our experience to work on<br>[43:01] tools and solutions that can benefit<br>[43:03] teams and organizations on a much larger<br>[43:06] scale. So, it's an interesting it's an<br>[43:09] interesting one from the WP Engine side<br>[43:11] of things taking on uh the the the stuff<br>[43:15] I guess from a great big enterprise<br>[43:17] level agency. I guess we'll wait and see<br>[43:19] where where that goes. There's there's a<br>[43:22] lot more but that was the most important<br>[43:23] paragraph I thought. Again, I don't know<br>[43:25] if anybody wants to comment on that, but<br>[43:29] no. Okay.<br>[43:30] >> No, I've tried I've tried to quickly<br>[43:33] find out who they are, but I got this.<br>[43:36] >> Yeah. Very very very credible agency. Um<br>[43:39] I've heard about them lots and lots of<br>[43:40] times, but they they they weren't one of<br>[43:42] those agencies, I don't think, which did<br>[43:44] a<br>[43:45] saw the importance in tons of marketing<br>[43:47] and things like that, you know,<br>[43:48] promoting themselves in the in the<br>[43:50] WordPress space, but I definitely heard<br>[43:52] of them lots and lots of times. So<br>[43:54] anyway, there we go. They're moving over<br>[43:55] with the WP Engine team. I guess<br>[43:57] effective immediately. They won't be<br>[43:59] taking on new clients, but they will<br>[44:01] instead be contributing to the endeavors<br>[44:03] at WP Engine,<br>[44:06] right?<br>[44:08] Okay, let's move over. So, I've put this<br>[44:11] on here. This is actually on X. Um, but<br>[44:15] I've had to put it on archive.ttoday<br>[44:17] because I was having problems getting it<br>[44:18] um getting it working.<br>[44:21] This is um I don't know 2025 2026 it<br>[44:25] feels like the year where maybe the AI<br>[44:28] gremlins take a hold of your brain and<br>[44:29] make you kind of worry that you have no<br>[44:31] job coming. You know the year is going<br>[44:33] to be hard. It's going to be difficult<br>[44:35] to justify using WordPress in the next<br>[44:37] years to come. Uh not everybody thinks<br>[44:40] that. And Nat<br>[44:42] help me with the surname please. An<br>[44:45] >> uh Milletic.<br>[44:46] >> Thank you. Milletic. Nat<br>[44:50] Milletic. There we go. There we go. Uh,<br>[44:52] he has listed out four reasons and the<br>[44:55] more I read them, the more I took um,<br>[44:57] the more I became sort of sanguin. I'm a<br>[44:59] bit of a bit of a worrier about AI in<br>[45:01] all honesty. And he's saying four<br>[45:03] reasons why he thinks he's bullish about<br>[45:05] WordPress in 2026. The first one is all<br>[45:07] about market dominance and momentum.<br>[45:10] There's bullet points underneath all of<br>[45:12] these, but I'll let you read those at<br>[45:13] your leisure. The next one is all about<br>[45:16] the economic ecosystem. the fact that<br>[45:18] Woo Commerce and WordPress and<br>[45:20] WordPress.com are just these massive<br>[45:23] entities. The fact that you can have a<br>[45:25] load of technical flexibility, that's<br>[45:27] his third point. You know, if you're on<br>[45:28] something um that's not flexible, then<br>[45:31] you're going to be, you know, you're<br>[45:32] going to have limitations. And also, uh<br>[45:35] developer opportunities. There's a<br>[45:37] constant or at least there has been a<br>[45:38] constant demand for WordPress developers<br>[45:40] and what have you. Uh, so I I was just<br>[45:42] pleased to see somebody um couching the<br>[45:46] future as being bright for the WordPress<br>[45:47] space. I know there are a few voices out<br>[45:49] there who do exactly that, but there's<br>[45:51] also seems to be a growing panic, if you<br>[45:54] know what I mean. There seems to be a<br>[45:55] lot of people getting online talking<br>[45:56] about how AI is doing this thing in<br>[45:59] onethird of a minute that used to take<br>[46:01] them three days and all of that kind of<br>[46:03] stuff. So anyway, Nat, uh, the voice of<br>[46:06] maybe reason. So again, I'm open it up<br>[46:08] to the floor if you've got anything you<br>[46:09] want to say about AI and WordPress. We<br>[46:12] got more to come about that. So<br>[46:15] >> you know what? I'm getting a little bit<br>[46:17] tired of all the blah blah blah around<br>[46:20] AI and WordPress where the Doom messages<br>[46:23] are concerned. You know, I love that Nat<br>[46:26] is is doing this and whoever else is<br>[46:29] doing it. Um because it's like people<br>[46:32] are saying buy an IKEA kitchen, you<br>[46:36] know, and put it in your professional<br>[46:37] hotel. Yeah, that'll work. You know,<br>[46:39] it's it's it's getting it's getting<br>[46:42] tiring. And then another thing that I<br>[46:44] I'd like to say about AI, what is tiring<br>[46:47] that people are probably not even<br>[46:49] conscious of is every time you see an<br>[46:52] article about WordPress,<br>[46:55] starting of it's not this, it's that.<br>[46:59] Yeah, the weather<br>[47:01] >> and then and then one, two, three<br>[47:03] points. Yeah,<br>[47:05] >> it's just I don't think I don't think<br>[47:06] people realize that. Well, I've been<br>[47:09] I've been listening to some interesting<br>[47:11] commentary about um how AI might be<br>[47:15] might it might be a difficult um a<br>[47:17] difficult thing to AI to propel itself<br>[47:18] in the way that it has been in the<br>[47:20] recent past just because of uh financial<br>[47:22] constraints in the year 2026 about how<br>[47:25] you know there's lots of venture capital<br>[47:26] that might need to be repaid and<br>[47:27] obviously the environmental cost and<br>[47:29] what have you and um and so it might be<br>[47:31] that we we don't have this sort of like<br>[47:33] continually it's getting better twice as<br>[47:36] good every month that may something that<br>[47:38] we don't experience anyway. So it it<br>[47:40] running away from us if you like might<br>[47:42] not be the case anyway.<br>[47:43] >> I think if people use it to as an<br>[47:46] assistant to create great stuff, that's<br>[47:49] that's what it's fantastic for.<br>[47:52] >> I was you remember a minute ago I said<br>[47:54] I'm doing the 200th episode of the of<br>[47:56] the Tavern podcast which is getting<br>[47:58] released this week. I was editing it<br>[47:59] this morning and it's with um we all<br>[48:01] know Corey Mass. Um, and Cory, it was<br>[48:04] Corey and it was Cory about AI and about<br>[48:07] how basically Cory loves it and he's<br>[48:09] using it where he can, but he's not<br>[48:11] using it where he can't. But he, one of<br>[48:14] the curious things that came out of what<br>[48:15] he's doing is he he gets it to do<br>[48:18] unexpected things like he he he said he<br>[48:21] used to have this pack of cards. I can't<br>[48:23] remember it was like a film director.<br>[48:25] No, it was Brian Enino. That was it. You<br>[48:27] know, the song, you know, the the music<br>[48:29] producer Brian Enino. Brianino produced<br>[48:31] this pack of cards for musicians in a<br>[48:33] studio who were getting a bit fed up.<br>[48:35] You know, they've been sitting there<br>[48:36] playing the same old song and you take<br>[48:38] this Brianino pack of cards and you'd<br>[48:40] flick the top one over of the deck and<br>[48:42] it would have something weird like, you<br>[48:44] know, play the song backwards or imagine<br>[48:47] that you're listening to this song and<br>[48:48] you're underwater. What would that be<br>[48:50] like?<br>[48:50] >> And so Corey's been getting AI to do<br>[48:54] that with his projects. He's been asking<br>[48:56] it to deliberately do weird stuff. And I<br>[48:59] just thought, gosh, that's so<br>[49:01] interesting. What what an interesting<br>[49:03] take that is because normally you think,<br>[49:05] you know, get it to do the sensible<br>[49:06] stuff, but no, he's mcking around with<br>[49:08] it and getting it to do things. In other<br>[49:09] words, he's leveraging its creativity,<br>[49:12] which is kind of curious. Uh the webinar<br>[49:15] in the comments, by the way, is saying<br>[49:16] WordPress has a great future. He's not<br>[49:18] scared of AI or they're not scared of.<br>[49:20] >> So there we go. Um and he's got another<br>[49:23] comment there. I can't make it come up.<br>[49:25] I don't know why. Oh yeah, there we go.<br>[49:27] the community is strong enough to<br>[49:28] develop it further without AI. It will<br>[49:30] assist us eventually but far from<br>[49:32] replacing uh is still um he says<br>[49:36] hallucinations are ways to frequently<br>[49:40] still something or other and always<br>[49:41] remember that AI is taught by us so it<br>[49:43] still has its limitations for how long<br>[49:45] that might be a question but you still<br>[49:48] know your subject and use AI<br>[49:50] efficiently. So there we go. Nice<br>[49:53] comments from Nat. Anybody else want to<br>[49:55] talk about N's Twitter feed or whatever<br>[49:57] that was?<br>[49:58] >> Well, all I can say is if you're not<br>[50:00] following the guy, um, just do. He's<br>[50:03] he's sharing so much positive stuff.<br>[50:06] He's um and and another guy that he<br>[50:09] seems I always see him in tandem with<br>[50:12] Marco Danic.<br>[50:14] >> Okay.<br>[50:14] Danic, some other people will say it's<br>[50:17] it's um they share so much information<br>[50:19] and I think they have this um community<br>[50:22] on Axe that has over 100,000 members,<br>[50:25] maybe 150,000.<br>[50:26] >> Good grief. Um the handle of Nat is Nat<br>[50:31] Mitellich and it's Nat M I L TC with no,<br>[50:35] you know, with no hyphens or dashes or<br>[50:38] anything like that in between. Um, and I<br>[50:40] will put that post into the show notes<br>[50:42] so that you can go and check it out. Are<br>[50:44] we staying on the AI thing?<br>[50:46] >> No. Well, yes, we are. Actually, we are<br>[50:48] staying on the AI thing. This is um th<br>[50:51] this is in equal measures frustrating<br>[50:53] and also kind of where we're at in the<br>[50:55] year 2026. So, this was from Reddit.<br>[50:58] Again, you can see I've put it into<br>[50:59] archive um.ph<br>[51:02] because for some reason the Reddit<br>[51:03] wouldn't allow I don't know why, but I I<br>[51:05] had to do it to get it on the screen.<br>[51:06] Here we go. So, this is somebody saying,<br>[51:09] "I I'm a plug-in team member. We don't<br>[51:13] use AI." And I'll just read a variety of<br>[51:15] the bits of it. Says, "I'm writing this<br>[51:17] post for two reasons. Number one, to<br>[51:19] dispel the myth that we use AI for all<br>[51:21] plug-in reviews. I've seen a recent post<br>[51:23] about this. Number two, I'm tired of I'm<br>[51:27] tired of reading AI generated email<br>[51:29] responses." Okay. They go on to say<br>[51:32] there is an exception. There's one place<br>[51:34] where they use AI and that's to check<br>[51:36] with AI if you're in trademark violation<br>[51:38] with something. So if you submit a<br>[51:40] plugin and there's some trademark<br>[51:42] violation, AI does that. However, the<br>[51:45] rest of the process for submitting a<br>[51:47] plug-in is not. But caution every other<br>[51:51] part of our review uses a com<br>[51:53] combination of realerson manual review<br>[51:55] and automated tooling. So that's not AI,<br>[51:58] that's automated tooling uh like PHPCS<br>[52:01] and reax checks. Today whenever this<br>[52:04] post was written, it was two days ago I<br>[52:06] think today we had the highest number of<br>[52:08] submissions in the history of the<br>[52:10] plug-in directory most of those were<br>[52:13] written by AI tools. You can see where<br>[52:16] this is going. um when an author consist<br>[52:19] so you imagine you submit a plugin to<br>[52:22] the uh repo it's written by AI you<br>[52:25] didn't do anything you just I don't know<br>[52:27] made a prompt got it submitted to the<br>[52:29] repository you're now using humans time<br>[52:33] and they're checking it and then if it<br>[52:37] gets declined there's an actual process<br>[52:39] that you have to go to through and it<br>[52:42] would seem that that is not being<br>[52:44] followed up so it's an AI submission<br>[52:46] it's reviewed Dude, it's rejected and<br>[52:49] then it just goes black. It's like a<br>[52:52] hole cuz you know it was an AI thing.<br>[52:54] Oh, I can't be bothered to reply to<br>[52:55] that. I'm just not I'll just submit<br>[52:57] another one. So, it says when the author<br>[52:59] consistently fails to implement our<br>[53:01] requirements, it's been a longunning<br>[53:02] policy since as far since before AI to<br>[53:05] first issue a warning and then close<br>[53:07] submissions. If your AI cannot keep up<br>[53:09] with our requirements, your plug-in will<br>[53:11] not be approved. Same goes for a human<br>[53:13] developer. And for the love of the open<br>[53:17] web is a plea at the end. And for the<br>[53:18] love of the open web, please do please<br>[53:21] capital letters do not reply with an AI<br>[53:24] generated email. I personally don't even<br>[53:27] bother to read them anymore. So what I'm<br>[53:30] trying to encapsulate here is this is a<br>[53:31] real human encountering what would<br>[53:33] appear to be a lot of AI generated<br>[53:36] stuff. And maybe in the next year or so,<br>[53:40] this is going to become a bit of a<br>[53:41] problem with plugins being submitted and<br>[53:44] there's just no human way of actually<br>[53:46] keeping on top of it. So, I don't have a<br>[53:48] solution, but um other than to say stop<br>[53:52] it. There you go. That's<br>[53:57] >> I'd like to say something about that.<br>[53:59] Yeah,<br>[54:00] >> one of the things that worries me, it<br>[54:02] was already worrisome with the human<br>[54:04] developers, and I don't mean that in a<br>[54:06] negative sense, just in the general<br>[54:07] sense, is there's something AI can't do<br>[54:11] even when you try to instruct it to do<br>[54:13] so. It will not generate accessibility<br>[54:16] ready code because it's learning from<br>[54:19] crap code online.<br>[54:21] And I'm not saying that it's the<br>[54:23] developer's fault who put that code out<br>[54:25] there now because this is just what<br>[54:28] happened through um uh component<br>[54:31] libraries and stuff that really need to<br>[54:32] be improved. Um, but that is is one of<br>[54:37] the things that worries me the most<br>[54:38] because people are building sites and<br>[54:41] they are following protocols and they're<br>[54:43] creating something accessible and<br>[54:45] suddenly they want something specific<br>[54:47] that they can't find and then they run<br>[54:49] into what are these plugins. They're<br>[54:50] like, "Oh yeah, this is doing what I<br>[54:52] want." Boom boom site rendered<br>[54:54] inaccessible right there. Because that's<br>[54:56] one thing you need to understand about<br>[54:57] accessibility. A site is not a little<br>[55:00] bit accessible. It either is accessible<br>[55:03] or it is not.<br>[55:07] >> Okay, thank you. Um, I'm just trying to<br>[55:10] uh figure out what's going on in the<br>[55:12] comments. There seems to be some twoing<br>[55:13] and throwing between Taco and some other<br>[55:16] people and I can't I can't quite keep up<br>[55:18] with it. And because I can't keep up<br>[55:19] with it, I can't figure out where it<br>[55:20] begins. So, I can't quite put it on the<br>[55:22] screen.<br>[55:23] >> I can I followed that too. Okay. Well,<br>[55:25] it started when um uh when we started<br>[55:27] talking about AI and um um Jimmy, also<br>[55:31] known as the webinar,<br>[55:33] >> yeah,<br>[55:34] >> uh mentioned that okay, you know, we<br>[55:36] don't have to worry about AI. Um<br>[55:39] WordPress has a great future. I'm not<br>[55:41] scared of AI and the community is strong<br>[55:43] enough to develop it further without AI.<br>[55:46] It will assist us eventually, but far<br>[55:47] from replacing it still. That's the one<br>[55:49] that you quoted.<br>[55:51] >> Yep. And then um the discussion went on<br>[55:53] and Taco said, "I think you're very<br>[55:55] wrong." And then Jim's like, "That's all<br>[55:58] right. We can share a different in<br>[56:00] opinion." You know, I love I love that<br>[56:02] when people are good at at having a<br>[56:04] dialogue.<br>[56:05] >> And so yeah. And then Taco said<br>[56:07] something that I'm really interested to<br>[56:09] hear about.<br>[56:10] >> What's this? Is it this one about<br>[56:11] Google?<br>[56:11] >> This one? Yes.<br>[56:13] >> I don't know anything about this this<br>[56:14] Sunday. So I'm reading. So that's in<br>[56:17] response to the the webinar's comment.<br>[56:19] So, Taco responded this Sunday. There<br>[56:22] was already an announcement from Google<br>[56:23] that's potentially problematic for WordP<br>[56:27] Does anybody know what that is? I<br>[56:29] literally taco. Will you share that with<br>[56:31] us?<br>[56:32] >> Yeah, if you're able to help us out,<br>[56:33] we'll we'll be able to get a handle on<br>[56:35] that. I don't know what that was. I'm<br>[56:36] presuming it's related to search or AI.<br>[56:39] I'm not entirely sure. Let's find out.<br>[56:41] Um D,<br>[56:44] anything else in there? No. Anyway, the<br>[56:48] point of that article, the reason that I<br>[56:50] was raising that one is if you if you do<br>[56:53] have the capacity to generate um a<br>[56:56] plug-in with AI and you submit it and<br>[57:00] you don't keep the whole process going.<br>[57:02] I'm I'm imagining this whole thing that<br>[57:04] we're looking at on the screen here is a<br>[57:06] bit of a plea for help. Um please don't<br>[57:09] do that because you you are essentially<br>[57:11] using up humans time. It's not like you<br>[57:13] submit it and AI then inspects it and<br>[57:15] you know drops you a yay or a nay. No,<br>[57:19] this is involving real people's time and<br>[57:21] if they get delugeed with an infinite<br>[57:23] number of plugins each day then the<br>[57:26] whole system sort of comes into question<br>[57:28] and collapses a little bit. So uh that's<br>[57:30] what I took from that anyway.<br>[57:32] Um D right okay so in which case we will<br>[57:36] move on uh and I'm going to go to this<br>[57:41] one. I'm going to miss one out now. Taco<br>[57:44] was on the show last week actually and<br>[57:46] Taco uh helpfully gave me four four um<br>[57:50] posts which Yoast like Yoast Devulk the<br>[57:54] person not Yoast the company uh had<br>[57:57] written and um and I knew I wouldn't<br>[57:59] have time to do all four of them. So<br>[58:00] again this is kind of interesting and it<br>[58:02] goes to like the future of WordPress<br>[58:04] being bright or not bright depending on<br>[58:06] where you sit in terms of AI. And I've<br>[58:08] picked this one out which he wrote on<br>[58:10] December the 21st. It's a little bit<br>[58:12] older, but um basically what what Yoast<br>[58:15] is saying and there is a thread of<br>[58:16] comments in this sits squarely in this<br>[58:19] bigger thread. So there's more to read.<br>[58:21] If you go to the bottom um of each of<br>[58:24] the posts, then he he links to the sort<br>[58:26] of following one or the preceding one or<br>[58:27] what have you. Um, and he's saying that<br>[58:30] in the like those people that are<br>[58:32] concerned about AI,<br>[58:34] if you're a developer, it would appear,<br>[58:37] well, Yos argument at least anyway is<br>[58:39] that the the cost of your line by line<br>[58:43] code that you used to write is going<br>[58:46] down. And it's really unrealistic in the<br>[58:49] future. If you're competing on lines of<br>[58:51] code written, you're in a losing battle.<br>[58:54] you are, you know, you can't compete<br>[58:56] against the output of an AI. Forget<br>[58:59] whether it does good stuff. Forget all<br>[59:00] of that. If it's just, you know, a<br>[59:01] contest of who can write a plugin in a<br>[59:05] given space of time, it's highly likely<br>[59:08] that an AI will beat you to it. Again,<br>[59:11] not saying it's secure, not saying it's<br>[59:13] perfect, it's just fast, right? So, his<br>[59:15] point is then in the future does this<br>[59:19] sort of trouble open source? and he's<br>[59:21] sort of thinking no because where we've<br>[59:24] got to pivot to as expert I'm not a<br>[59:26] developer so this is not me where<br>[59:27] developers and such like need to pivot<br>[59:30] to is and I've seen this word loads now<br>[59:34] I don't know if you're seeing it as well<br>[59:35] this word architect that seems to be a<br>[59:38] real buzzword in the year 2020 latter<br>[59:40] part of 2025 and the early part of 2026<br>[59:43] is you're going to be able to pitch your<br>[59:45] skills not because you can write code<br>[59:48] quickly but because you can architect<br>[59:51] the project. You're the one that knows<br>[59:54] what good looks like. You're the one<br>[59:56] that knows what failure looks like.<br>[59:58] You're the one that knows what the whole<br>[60:00] thing looks like. And again, leaning<br>[60:03] into Nat's piece where he's sanguin<br>[60:05] about the future. Yoast seems to be<br>[60:07] sanguin, but just it's a slightly<br>[60:09] different future. You've got to pivot.<br>[60:11] You've got to offer a different skill.<br>[60:12] You've got to be the architect. And<br>[60:15] there's more to it that you can see on<br>[60:17] the screen, but I just thought that was<br>[60:18] an interesting an interesting<br>[60:20] commentary. So, more like managing the<br>[60:22] whole thing, explaining your whole<br>[60:24] project expertise. So, again, I don't<br>[60:27] know if anybody Michelle or Mark or<br>[60:29] anybody wants to jump in there. If you<br>[60:31] want, go for it.<br>[60:36] going<br>[60:38] >> I was just say going back to the ADHD<br>[60:40] thing, you know, we all we all look at<br>[60:42] things from<br>[60:44] from the big picture point of view. So,<br>[60:47] this speaks to me.<br>[60:49] >> I I agree uh largely with what what he's<br>[60:54] saying here.<br>[60:56] >> Um you could definitely there's like I<br>[60:58] said, there's more to it. I can't<br>[60:59] remember the names of the articles, but<br>[61:00] there's three uh maybe this sits in the<br>[61:03] middle and there's two before and one<br>[61:04] after. I can't remember but go click on<br>[61:06] the links in the show notes and um and<br>[61:08] sorry again.<br>[61:08] >> Yeah, I think I think the main word here<br>[61:10] is is um being the architect. I think I<br>[61:13] would put that as if you can give it<br>[61:16] context.<br>[61:17] An architect knows context.<br>[61:20] >> Yeah. Yeah.<br>[61:21] >> And that's that's basically it. If you<br>[61:23] can give it the context in in every<br>[61:25] possible way and you work with others<br>[61:27] who can give context<br>[61:29] >> and then you work together.<br>[61:31] >> It's kind of interesting. So, I'm I'm<br>[61:33] sure that Yos wasn't trying to be um<br>[61:36] incendury, but he used the um he used<br>[61:38] the analogy of being brick layers about<br>[61:40] how kind of like a modern WordPress<br>[61:42] build is in fact, let's just read it<br>[61:45] out. He says, "In the past, the<br>[61:46] developer was often a glorified brick<br>[61:48] layer.<br>[61:49] >> Success was found in the manual labor of<br>[61:51] laying down stable reusable bricks of<br>[61:54] code. Uh but when AI can manufacture and<br>[61:57] lay those bricks instantly, the value of<br>[61:59] the brick layer Yeah.<br>[62:01] >> vanishes. So, so you know, but you still<br>[62:04] you can't build the house without the<br>[62:06] brick layer, but now the brick layer is<br>[62:08] an AI, but equally you can't build the<br>[62:11] house without the plan, the the plan<br>[62:13] supplied by the the qualified architect<br>[62:15] and what have you. And so that is where<br>[62:18] uh he's repositioning. So the value now<br>[62:20] now lies in again I'm quoting the value<br>[62:22] now lies in the architect. This<br>[62:23] architect this new role isn't about<br>[62:25] syntax. It's about providing the three<br>[62:27] things AI cannot yet originate. um<br>[62:30] intent, the the why, um direction,<br>[62:34] steering the solution, and finally the<br>[62:37] logic, the structural how of doing<br>[62:40] things as well. And so um so there's a<br>[62:42] beach head he's painting uh in the year<br>[62:45] 2026, the architect position, whether<br>[62:47] whether or not the architect position is<br>[62:49] still here in 2027 or that's been<br>[62:53] slurped up by the AI as well. Yeah, but<br>[62:55] this is this is the area that I still<br>[62:57] have a the the creativity side of things<br>[63:00] is where I have a hard time seeing AI<br>[63:03] ever catching up. But it has come so far<br>[63:06] in such a short time. I I would never<br>[63:08] say never. But um but you still have to<br>[63:11] feed into it into AI, hey, here's the<br>[63:14] problem. And you can discuss with AI<br>[63:17] what the solution might be, but it's<br>[63:19] still you're still the driver of all<br>[63:22] that. uh you know that solution. So it's<br>[63:26] a matter of of just<br>[63:29] taking you know a step back and and<br>[63:32] looking at it from a more panoramic view<br>[63:34] rather than you know at the at the micro<br>[63:38] level I suppose.<br>[63:40] >> Yeah.<br>[63:41] >> Um so WP thank you for your commentary.<br>[63:44] I see that you've written fair few<br>[63:46] things. Appreciate that. Uh this one<br>[63:48] though I think is in relation to what<br>[63:50] we've just been talking about. 100% he<br>[63:52] says I wrote uh this two years ago so I<br>[63:55] guess something else uh AI age AI age is<br>[64:00] a generalist age if you can understand<br>[64:02] many complex concepts and how everything<br>[64:05] works around you you will be the golden<br>[64:07] person to work and grow with AI um uh<br>[64:14] and then there's something about oh it<br>[64:16] looks like comments that contain a URL<br>[64:18] don't make it oh you mean into this<br>[64:20] platform yeah Maybe if you've got a URL,<br>[64:22] I don't know. I'm sorry about that. I'm<br>[64:24] not sure. Yeah, maybe it strips those<br>[64:26] out, Taco. But if you've got a follow-up<br>[64:28] and you want to give us the name of the<br>[64:30] article, maybe we could Google it. Um,<br>[64:32] and oh, we always get the fun Twitch<br>[64:35] comment that bears no relation to what<br>[64:37] we're talking about at all. So, thank<br>[64:38] you, whoever you are, for uh creating an<br>[64:41] AI bot, which drops a silly, pointless<br>[64:43] comment into into our show each week.<br>[64:45] Wonderful. So, there we go. That's that<br>[64:47] one. Um, I'm just seeing if those<br>[64:50] comments are catching up. Okay,<br>[64:53] something. It's on Yos blog, says T, but<br>[64:56] I don't know which one. All right.<br>[64:58] Right, right, right, right. Okay, let's<br>[65:00] move on. So Dave Gray, he's often on the<br>[65:04] show. Dave's been fabulous actually at<br>[65:06] dropping in at the last minute. I'm very<br>[65:07] appreciative of Dave when guests have<br>[65:09] canceled and things like that. He's<br>[65:10] always been around. He's in the UK, so<br>[65:12] his time zone overlaps with mine, but<br>[65:14] he's also very gracious with his time.<br>[65:16] So, thank you Dave. And um Dave has this<br>[65:20] which I thought you might like to see.<br>[65:21] Uh he's been on a bit of a clip creating<br>[65:23] little utility plugins um for the<br>[65:26] WordPress back end. And this is a great<br>[65:28] one. It's called Media Library<br>[65:29] Essentials. And um guess what it does?<br>[65:32] It adapts the media library so that you<br>[65:34] can do a whole bunch more stuff with it.<br>[65:36] I think in the near future the media<br>[65:38] library is going to get a bit of an<br>[65:39] overhaul, but for now um if you're<br>[65:41] dissatisfied with it, this is the sort<br>[65:43] of stuff it can do. You can view and set<br>[65:45] featured images. You can bulk download<br>[65:47] media and images. Add categories and<br>[65:49] tags to images. So in other words, you<br>[65:51] know, if you want to that for me is the<br>[65:53] big one. I can never find things because<br>[65:55] I can't put them in particular silos.<br>[65:58] Image usage counts and file sizes. You<br>[66:00] can get the image dimensions and also<br>[66:02] you can get a pop-up preview which is<br>[66:04] demonstrated just there. You can<br>[66:06] actually see what this is about. Um it's<br>[66:09] not a vast plugin that does a vast<br>[66:11] amount of stuff. And so Dave as he is<br>[66:13] want to do prices it effect prices it<br>[66:16] accordingly. You can get it for life one<br>[66:18] time price it's $20 $19.99 or 19.99<br>[66:25] and you know the number of sites goes<br>[66:26] up. You can buy one site for 20 bucks or<br>[66:29] you can buy 200 sites for uh 99 bucks.<br>[66:33] So maybe throw Dave a bone and uh go for<br>[66:36] the 200 site if that's your thing. There<br>[66:38] we go. Anything on that? I just wanted<br>[66:40] to give him a hat tip.<br>[66:43] >> Just it's just a great guy.<br>[66:45] >> Yeah,<br>[66:45] >> I remember he started I don't know if it<br>[66:47] was two years ago, maybe three even, I<br>[66:50] don't know.<br>[66:51] >> He I met him on on X online and we were<br>[66:54] talking and he was just constantly um<br>[66:57] sharing his thoughts and ideas about the<br>[67:00] plugins he's developing and the services<br>[67:02] he was um uh offering to people. And I<br>[67:06] this guy is is so helpful and he has<br>[67:10] these interesting ideas about marketing.<br>[67:13] >> Um I don't know whose show he was on. He<br>[67:16] was invited<br>[67:17] >> with a completely different view on<br>[67:19] marketing than everybody else has<br>[67:21] >> and how he wanted to market.<br>[67:23] >> Oh yeah, I did a podcast with him. That<br>[67:24] was me.<br>[67:25] >> That was me. Yeah. I remember sitting<br>[67:28] driving the car from Munich all the way<br>[67:30] back up north in Germany and and<br>[67:31] listening to that. That was insane.<br>[67:34] Don't ever listen to my podcast whilst<br>[67:36] driving a car just so that much. It<br>[67:39] brings on insom, you know, it removes<br>[67:41] insomnia and brings on sleep. So, uh,<br>[67:44] just be careful operating the wind.<br>[67:47] This is, this is Dave's website, by the<br>[67:49] way. It's friendly webbguy.co.uk. And in<br>[67:51] towards the latter part of 2025, he<br>[67:54] decided to um quit his sort of day job<br>[67:57] and get into making plugins and browser<br>[68:00] extensions and things like that his<br>[68:02] thing. So, he's just sort of beginning<br>[68:04] and obviously the more sales he gets,<br>[68:05] the more that he can do uh things. Yeah,<br>[68:08] it was around the pricing of some of his<br>[68:10] products. You've got this interesting<br>[68:11] way of uh pricing it and marketing it<br>[68:14] directly to hosting companies as opposed<br>[68:16] to individual sales.<br>[68:18] >> That was the that was the tactics. And<br>[68:20] >> so, you thought that we'd talked all we<br>[68:22] could about accessibility, but no, we<br>[68:24] haven't. This is the last one. Um, this<br>[68:26] is, um, isn't it funny when you go<br>[68:29] around the web and you use a particular<br>[68:31] theme and you can spot it straight away?<br>[68:33] I am going to bet that this site is<br>[68:35] built using Ollie. Um, I have no idea if<br>[68:39] it is. Let's have a just a quick scroll<br>[68:40] and see. I'm I think so. I would bet my<br>[68:43] life Yeah, that comment section is<br>[68:45] Ollie. Let's have a look. There you go.<br>[68:48] Look,<br>[68:48] >> it's um, it's the fog.<br>[68:50] >> It's Yeah, the spleing and Yeah,<br>[68:52] anything. Anyway, rah, go and check out<br>[68:55] Ollie. It's a very good blockbased<br>[68:56] theme. Um, this is the block<br>[68:59] accessibility checks website, blocks<br>[69:02] accessibility checks.com.<br>[69:04] And, uh, Troy on the 1 of January<br>[69:06] released this blocks accessibility<br>[69:08] checks 3.0, advanced validation control<br>[69:11] for WordPress. I confess I had not<br>[69:13] really heard of this thing, so it was<br>[69:16] all a bit new to me. And the first<br>[69:17] little section of the the post is, you<br>[69:20] know, it's technical, so we won't go<br>[69:22] into it, but I didn't realize that this<br>[69:25] tool even existed. You throw it into<br>[69:28] your WordPress website and then<br>[69:30] helpfully in the same way that Yoast got<br>[69:32] us all thinking about traffic lights and<br>[69:34] oh, that's a failure because it's red.<br>[69:37] Go and have a look at that thing. It<br>[69:38] would appear and and maybe you can speak<br>[69:40] to this or anybody else in fact um it<br>[69:43] would appear that it offers sort of like<br>[69:44] a similar functionality but on a<br>[69:47] blockby-block basis<br>[69:49] given the accessibility requirements of<br>[69:52] that block. So the button needs these<br>[69:54] things, the paragraph needs these<br>[69:55] things, the link needs this thing and on<br>[69:58] you go and um<br>[70:00] >> and so there's been an update to that.<br>[70:02] If you can see the screen, then we're<br>[70:04] looking at a screenshot of how the<br>[70:05] plug-in will kind of like add a layer on<br>[70:08] top of what you're looking at to call<br>[70:10] out on the block itself. Look, this<br>[70:13] button needs work or look, this table<br>[70:15] needs work. And it's kind of gets out<br>[70:17] the way, but is kind of also in the way<br>[70:19] so that you can't really avoid it. And<br>[70:21] then helpfully in the sidebar on the<br>[70:23] right hand side, it kind of groups<br>[70:26] problems into categories like errors and<br>[70:29] warnings and what have you. And then you<br>[70:31] just go through and fix them one at a<br>[70:33] time. So I'd not heard of this. They're<br>[70:35] on version 3.0. It just looked like a<br>[70:37] really cool project to give you a<br>[70:39] helping hand if accessibility is indeed<br>[70:41] not your thing. So<br>[70:44] >> it is.<br>[70:45] >> There we go.<br>[70:45] >> It is. Joy started working with this on<br>[70:48] this I think only a few months ago.<br>[70:50] >> Yep.<br>[70:51] >> And I remember I saw him post something<br>[70:53] about it on LinkedIn. So, um,<br>[70:57] immediately I yelled like, "Troy, I want<br>[71:00] to try that."<br>[71:02] Um, and, um, I also loved, um, the<br>[71:06] philosophy behind it because there's a<br>[71:09] comparable plug-in called the<br>[71:10] accessibility checker, uh, by Equalized<br>[71:14] Digital.<br>[71:14] >> Yes, that's the one I'd heard. Um the<br>[71:16] background of this is that Troy and his<br>[71:20] team manage 800 university websites in a<br>[71:25] multi-sight environment. Okay. Right.<br>[71:27] >> So we're talking about an environment<br>[71:28] where everything else has been set<br>[71:32] >> colors um branding everything. So this<br>[71:35] is purely focused on content itself.<br>[71:39] People literally writing stuff. They<br>[71:41] don't do anything in the design or<br>[71:43] anything else. So um I think originally<br>[71:46] he created that for them and then he<br>[71:49] decided to um remodel it into something<br>[71:53] that actually anyone can use. So um it's<br>[71:56] actually um a very lightweight uh<br>[72:00] plug-in um that uh if you already are<br>[72:05] where you have to be with everything<br>[72:06] else in accessibility, you could use<br>[72:09] this uh on your projects or you could<br>[72:12] use accessibility checker. But I I this<br>[72:14] is where it came from and I absolutely<br>[72:17] adore it.<br>[72:18] >> Yeah, it looks really nice. I mean,<br>[72:20] we've got um we've got somebody in the<br>[72:22] comment. I can't remember who it was. I<br>[72:23] think it might have been Courtney. Yeah,<br>[72:25] there we go. Courtney Robertson, who's<br>[72:28] off on the show last week, actually. Um<br>[72:30] using Troy's plugin on my site. I've<br>[72:32] also have it in a testing environment to<br>[72:34] be sure what I create passes. Um would<br>[72:38] recommend hitting TroP for UI UX<br>[72:41] brainstorming too.<br>[72:43] Uh, and then Taco makes the point that<br>[72:45] is it similar to the equal equalized<br>[72:47] digital accessibility checker? And from<br>[72:49] what Ann's saying, it sounds like it is<br>[72:51] fairly similar. Maybe there's a maybe<br>[72:53] there's some, you know, clear blue sky<br>[72:54] between the two. But, um, anyway, there<br>[72:56] we go. Um, but it was really that<br>[72:59] screenshot that made me kind of pause<br>[73:01] and think, even I can get that. Um, and<br>[73:06] Mark was saying earlier he's no<br>[73:07] accessibility expert. I hope you can<br>[73:09] join me in saying, yeah, I can do that.<br>[73:11] you know, that looks like something I<br>[73:13] could get into.<br>[73:14] >> Um, and there you go. So, check it out.<br>[73:18] >> I think um I think um the one of the uh<br>[73:22] differences between Equalized Digital is<br>[73:25] exactly this question. Does it only work<br>[73:27] with FSE? I think this is um a block<br>[73:31] plugin. Yes.<br>[73:33] >> Yeah. Okay. So, this one that's on the<br>[73:35] screen now from Troy, that's an FSE<br>[73:37] based solution, whereas the equalized<br>[73:39] digital one stretches a little bit<br>[73:40] further, does it? Does it go out to<br>[73:42] >> Yeah, digital works for everybody,<br>[73:44] >> right? Okay, great. Anyway, go and check<br>[73:47] that out. Um, I'll link to it in the<br>[73:49] show notes as I mentioned. And let me<br>[73:52] take that comment off. Um, this is for<br>[73:55] the the people who love their headless<br>[73:57] stuff. I confess I'm not an expert in<br>[74:00] any of this stuff, but I know that there<br>[74:01] are certain members of the audience who<br>[74:03] love all this. And it's a new tool. It's<br>[74:05] called Phantom WP and it's kind of SAS<br>[74:08] meets um WordPress meets Versel meets<br>[74:12] headless meets GitHub. There's a lot of<br>[74:15] spinning wheels here. It's still in beta<br>[74:17] and I think you have to um kind of if<br>[74:20] you want to jump on board, I think you<br>[74:21] got to submit an email and then um you<br>[74:24] know you'll get on boarded and you pay<br>[74:25] like a um like an opening price. You<br>[74:28] know, they've got this pricing at the<br>[74:30] moment which is going to be different to<br>[74:31] the one that you'll eventually pay. And<br>[74:33] essentially what it does is it allows<br>[74:35] you to have a a headless WordPress<br>[74:37] backend um somewhere online. Then their<br>[74:42] software does all the managing of<br>[74:43] putting that into a GitHub repo,<br>[74:45] connecting it to Versell and then<br>[74:46] Versell will then consume it and it will<br>[74:50] be published using Astro. So there's a<br>[74:53] lot going on.<br>[74:54] >> There's a lot of moving parts. But if<br>[74:56] you're into all of that, um, this tool I<br>[74:58] had a play I managed to and I really<br>[75:02] don't know what I'm doing and I managed<br>[75:04] to get a WordPress website up and<br>[75:06] running on Versel using Astro as the<br>[75:09] sort of theming layer and and it worked<br>[75:11] exactly as as I expected. It took<br>[75:14] minutes and man alive is that Astro<br>[75:17] stuff fast. um once it's actually<br>[75:20] published on the front end, that's<br>[75:21] obviously the the reason you're doing it<br>[75:23] is to make everything sort of more or<br>[75:24] less static and fast and what<br>[75:26] >> it's plain HTML.<br>[75:28] >> Yeah. Yeah. It's really really really<br>[75:30] brilliant. Anyway, so if if you if<br>[75:33] you're curious about that, it's called<br>[75:34] Phantom<br>[75:36] WP. What's the URL? Oh, it's exactly.<br>[75:39] >> Yeah, it's phantomwp with a ph.<br>[75:42] Phantomwp.com.<br>[75:44] Like I said, I've had a play. I'm going<br>[75:46] to try and get Oidu, who's the developer<br>[75:48] behind this, onto the podcast so he can<br>[75:50] explain to me actually what's going on<br>[75:52] because I just clicked the next button<br>[75:55] in most situations. Now, do this. Now,<br>[75:57] do this. Oh, you got a website. Yeah,<br>[75:59] sure enough. I do have a website. That's<br>[76:01] great. I'm not clever enough to know<br>[76:02] what's going on, but um go check it out.<br>[76:05] Anybody on that?<br>[76:08] Okay. Right. Another tool very quickly.<br>[76:12] Uh, I have a variety of tools in my kit<br>[76:15] which do what Falcon is doing. I've not<br>[76:17] heard of Falcon before. It's new. Um,<br>[76:19] essentially it allows you to, well, the<br>[76:21] claim is faster, cleaner, more secure.<br>[76:24] It it you install this into your<br>[76:26] WordPress uh website. It's a plugin and<br>[76:29] then they say it brings 49 carefully<br>[76:31] crafted optimization modules into one<br>[76:34] place. So, it is things like you can see<br>[76:36] on the screen here, disable and you<br>[76:39] won't be happy. uh disable Gutenberg.<br>[76:42] That's one of the options that you can<br>[76:44] do if you want to get rid of that. You<br>[76:45] can disable the heartbeat. Yeah, you can<br>[76:48] disable embeds. You can disable<br>[76:49] comments, remove the website field<br>[76:51] comment form, disable revisions, disable<br>[76:54] self pings, disable blah blah blah blah<br>[76:56] blah, you know, all of that kind of<br>[76:57] stuff. Uh but then there's a whole bunch<br>[76:59] of other things, you know, improvements<br>[77:00] to the media library, a bit like the<br>[77:01] plug-in we just mentioned. Uh they'll do<br>[77:03] SMTP for you so that you don't have to<br>[77:06] have a third party plugin for that.<br>[77:08] security. So presumably it's dealing<br>[77:10] with things like the rest API switching<br>[77:11] that on and WPM XML and WPL I can never<br>[77:15] say that the one ending oh there XML RPC<br>[77:19] that's what's trying to come out of my<br>[77:20] mouth<br>[77:21] >> uh I've not used it caveat mtor so there<br>[77:24] it is wp falcon<br>[77:27] uhpro if you want to go check it out<br>[77:30] >> again<br>[77:30] >> I'm just very curious um whenever<br>[77:33] someone creates a plugin that is not<br>[77:35] niche that is there's something like<br>[77:38] what what's the idea about I'd love to<br>[77:40] hear that from I have a different one<br>[77:42] called ASSE which is admin<br>[77:45] >> site enhancements which I think which I<br>[77:48] think basically maps a lot of the<br>[77:49] functionality here and I put it on<br>[77:52] everything now because it's just this<br>[77:53] one plugin which does a lot of the<br>[77:56] things that I would normally maybe use a<br>[77:58] snippet for like I don't want emojis in<br>[78:00] most of the sites that I'm touching. I'<br>[78:02] no need for that so I I use it for that.<br>[78:05] Plus it's got the SMTP stuff so I don't<br>[78:07] need a third party plugin for that.<br>[78:08] >> Oh yeah.<br>[78:09] >> You know all of that kind of stuff. So,<br>[78:10] it's pretty neat. Uh, anyway, there we<br>[78:12] go. Falcon, what was it called? WP<br>[78:15] falcon.pro. Go check it out. All right.<br>[78:19] I'm not going to uh I wish I had time<br>[78:22] for this. I might come back to this next<br>[78:23] week, but uh I think both me and<br>[78:25] Michelle agreed this is this is a tasty<br>[78:27] looking website.<br>[78:29] >> Um,<br>[78:29] >> absolutely. Oh, it's called WordPress<br>[78:32] security in good hands. And uh it's<br>[78:35] really long and I I read it, but then<br>[78:38] this morning I kind of realized I I need<br>[78:40] to do a whole show on just this one<br>[78:42] because it's quite long. But man, look<br>[78:44] look how nice this is.<br>[78:47] >> Look at it all.<br>[78:48] >> Michelle, you called it something really<br>[78:49] nice. I just forgot.<br>[78:52] >> I called it um Montipythonesque.<br>[78:54] >> Yeah, right. That's a great expression.<br>[78:58] has the Montipython feel, but it's long.<br>[79:01] Very, very long. But I love the<br>[79:03] aesthetic. It just makes me feel like<br>[79:04] I'm doing so much. That's the one.<br>[79:06] Right. You You're imagining if you can.<br>[79:10] >> If you can get past the um the killer<br>[79:12] rabbits at the very end, you get the<br>[79:14] Holy Grail.<br>[79:15] >> Oh. Oh, where? Where? Hold on.<br>[79:17] >> No, I'm kidding. I'm kidding. I'm<br>[79:19] >> just I want to see the I want to see the<br>[79:21] flying cow. I mean, if you're going to<br>[79:22] do all the flying cow,<br>[79:24] >> I'm just making a joke. I'm making<br>[79:26] >> I promise to do a deep dive into this at<br>[79:28] some point. We will definitely get it.<br>[79:30] But<br>[79:30] >> it's definitely long and involved which<br>[79:32] >> yeah got a lot out but<br>[79:34] >> um anyway I'll come back to that another<br>[79:36] week but because it was there and it was<br>[79:37] beautiful I thought we'd um raise it on<br>[79:39] the screen. Security<br>[79:42] >> uh Taco actually put this in my path I<br>[79:44] think towards the end of last week. Um<br>[79:48] >> fake WordPress domain renewal emails<br>[79:50] targeting admins to steal credit card<br>[79:53] data. So, you know, we've been there<br>[79:54] before, but we've got a new round of it.<br>[79:57] >> People sending out credible looking<br>[79:58] emails purporting to come from<br>[80:00] WordPress.com,<br>[80:02] >> um, claiming that your WordPress website<br>[80:04] is about to expire. You know, your.com<br>[80:06] renewal is coming up and what have you.<br>[80:08] And they look legit. Everything about<br>[80:10] them looks totally kosher. Uh, except of<br>[80:12] course when your bank account is emptied<br>[80:14] because you type in the details of your<br>[80:16] credit card number<br>[80:18] >> to a fake website. So, just be on the<br>[80:21] lookout and maybe warn your clients that<br>[80:23] this is due in the rounds. I don't know<br>[80:25] if it's been closed down now because<br>[80:27] this email, this post is like six days<br>[80:30] out of date now, but<br>[80:31] >> you know,<br>[80:33] don't ever<br>[80:34] >> It's a good reminder not Yeah. not to<br>[80:36] click the link. If you if you're getting<br>[80:37] a notification that you need to renew<br>[80:39] something, go log in<br>[80:41] >> through your normal login and see if<br>[80:42] that's accurate or not.<br>[80:44] >> Any of you ever done it? Have any of you<br>[80:46] ever accidentally done like have been<br>[80:49] the not just the recipient of but you've<br>[80:51] actually gone through all the steps and<br>[80:53] been defrauded?<br>[80:55] >> Thank god I haven't.<br>[80:56] >> No, you're all too savvy for that.<br>[80:58] That's good.<br>[80:58] >> I smell those a mile away.<br>[81:01] >> Yeah,<br>[81:01] >> I I'm I'm suspicious of everything all<br>[81:04] the time anyway.<br>[81:06] >> Yeah, even the legit stuff. Yeah, he was<br>[81:08] >> if my kids if my kids say good morning<br>[81:11] to me, I have to like verify<br>[81:14] >> to or it didn't happen.<br>[81:16] >> Oh, yeah. I love I love getting these<br>[81:18] WhatsApp messages from from the 25<br>[81:22] different kids that I never had.<br>[81:24] >> Yes. Yeah, that's right.<br>[81:25] >> They have a new phone number.<br>[81:26] >> But it's really clever, you know, that<br>[81:28] they look totally legitimate. You know,<br>[81:30] they got the correct logos and the fonts<br>[81:32] all correct and all that kind of stuff.<br>[81:33] So, just beware. But I think the the the<br>[81:35] central pillar of the argument is if you<br>[81:38] didn't ask for it, don't click it. You<br>[81:40] know, unless you literally said, "I want<br>[81:43] an email from you," then don't do it. In<br>[81:46] the um<br>[81:47] >> many of them will spoof the email<br>[81:48] addresses, but<br>[81:50] >> most of them are from some weird Gmail<br>[81:52] account. And I just you have to know<br>[81:54] that PayPal, your hosting sites,<br>[81:56] everything is not coming from Gmail.<br>[81:58] >> If it's coming from Gmail, just<br>[82:00] absolutely delete it right away. Um, so<br>[82:02] Sinan, no, sorry, this is Taco. Um,<br>[82:05] Taco's actually had he's been the victim<br>[82:07] of it. His card was skimmed at an ATM<br>[82:09] whilst he was using it.<br>[82:11] >> That's terrible.<br>[82:12] >> That whole thing where they put like an<br>[82:13] extra layer of something outside of the<br>[82:16] ATM, but it looks like the bit where you<br>[82:18] put your card in and it passes through<br>[82:20] that before it gets to the actual<br>[82:23] >> card rate. I mean, gosh, they get your<br>[82:25] money back.<br>[82:26] >> He says abroad. Abroad probably means it<br>[82:29] happened here in the United States. He<br>[82:31] uh<br>[82:31] >> I I actually I actually have a solution<br>[82:33] for that which is just have no money in<br>[82:35] your bank account.<br>[82:36] >> Yeah, that's a great way.<br>[82:38] >> Never a problem.<br>[82:39] >> Yeah. Um and then Sinan says even when<br>[82:42] he's too drunk to read the emails, he<br>[82:44] wouldn't fall for those. No. Good. But<br>[82:46] they obviously make an impression<br>[82:48] otherwise they wouldn't do it. I'm<br>[82:49] guessing, would they?<br>[82:50] >> Um sure.<br>[82:52] >> Nomad skateboarding says gets a lot of<br>[82:53] fishing attempts for renewal from my<br>[82:55] gravitar profile. Oh, that's because<br>[82:57] it's so public, right? It's scrapable.<br>[83:00] public data. There's a few times when<br>[83:02] I've definitely been the recipient and<br>[83:04] I've spotted it. So, I always just open<br>[83:07] I use Gmail and I don't know if you ever<br>[83:09] noticed there's a little like a like a<br>[83:11] details block at the in the header of<br>[83:14] your uh Gmail account where you can<br>[83:15] click it and it'll expose some limited<br>[83:18] but important data about who actually<br>[83:21] sent it. So, it'll say what domain it<br>[83:23] came from. Um, and if you read that line<br>[83:26] by line, um, you'll know, you know,<br>[83:29] because it's coming from google.com, not<br>[83:32] Google.com<br>[83:33] or something approximating it. And in<br>[83:35] that way, you can see what's going on.<br>[83:38] >> Uh, oh, he got his money back. Oh,<br>[83:39] that's all right. That's good. But they<br>[83:41] blocked my card, so I couldn't use the<br>[83:42] bank account for the next two weeks. Oh,<br>[83:44] no.<br>[83:45] >> That is something that I do recommend to<br>[83:47] people is especially with credit cards,<br>[83:49] you can actually freeze them. Yeah,<br>[83:51] >> I keep all my credit cards frozen all<br>[83:53] the time.<br>[83:54] >> Uh, and only unfreeze them when I need<br>[83:57] to use them.<br>[83:58] >> How does that work though if you've got<br>[83:59] like subscriptions like let's say for<br>[84:01] example, I don't know, Spotify or<br>[84:03] something like that?<br>[84:04] >> Do you use a separate one which is<br>[84:06] always on frozen or something?<br>[84:08] >> Yeah. Well, what uh what you can do is<br>[84:10] there's also these um one of the cards<br>[84:12] that I have actually allows for me to<br>[84:14] create a digital card specifically for a<br>[84:17] subscription.<br>[84:18] >> Oh, okay.<br>[84:20] and and that uh that also protects me.<br>[84:22] But um but I have gotten the only<br>[84:25] problem is there'll be times when I go<br>[84:26] to a restaurant and I put it on a credit<br>[84:28] card and I forget to unfreeze it and it<br>[84:29] gets declined and then I have to pull<br>[84:32] out my phone and you know<br>[84:34] >> bad moment where Yeah. Yeah.<br>[84:36] >> Um and then look at this. This is I I<br>[84:38] I'm sure I've seen this before, but I'd<br>[84:40] forgotten about it. Uh Webort says Oh<br>[84:43] no. Yeah. that one where a fishing email<br>[84:45] combined an R and an N in a font I guess<br>[84:48] which collided them quite close together<br>[84:50] to make it look like the letter M.<br>[84:53] >> Yeah. There's another one uh where<br>[84:55] people use cerillic characters.<br>[84:57] >> Yeah.<br>[84:58] >> Right.<br>[84:58] >> Or or a zero instead of an O. Um pretty<br>[85:03] common or a one instead of an I like I<br>[85:05] think City Bank. City Bank there was one<br>[85:08] where people were using a one instead of<br>[85:10] an I for City Bank. And<br>[85:12] >> you've got to think with the advent of<br>[85:14] like mobile banking that this whole<br>[85:17] fishing thing has become a lot more<br>[85:18] difficult because in in many situations<br>[85:21] now I'm getting a notification<br>[85:23] immediately on a phone the minute<br>[85:25] anything is like anything is purchased<br>[85:28] you know even if you spend a couple of<br>[85:29] pennies here there and every you get a<br>[85:31] notification to say that happened which<br>[85:33] is obviously wasn't the case back in the<br>[85:35] day and um and a lot of the um the<br>[85:38] confirmation steps you know where you'll<br>[85:39] go through you'll go through the click<br>[85:41] purchase and then the bank somehow gets<br>[85:44] in the way and says right now go to the<br>[85:47] app.<br>[85:47] >> Yeah.<br>[85:47] >> Click in the app. And you got to think<br>[85:49] that's that's helping.<br>[85:51] >> Well, but the thing that you have to<br>[85:52] also keep in mind is that this is like<br>[85:55] security people have to react to<br>[85:57] whatever the scam is. So, it's always a<br>[85:59] reactionary thing. So, there's always<br>[86:01] going to be like this sweet spot for the<br>[86:03] scammers<br>[86:05] before the security people come up with<br>[86:06] the solution for it. And then the<br>[86:08] scammers have moved on to the next<br>[86:09] >> Yeah. they got the next thing going.<br>[86:11] >> They got the next thing going. So, it's<br>[86:12] always when you're reacting rather, you<br>[86:15] can't always be proactive. You can to a<br>[86:17] certain degree, but you can't always be<br>[86:18] proactive when you're when you're the<br>[86:20] guys designing the security. So, there's<br>[86:22] always going to be that that person that<br>[86:24] comes up with the creative way to<br>[86:26] >> I am not going to endorse that<br>[86:28] lifestyle, but there must it must be<br>[86:30] quite fun. You know what I mean? being<br>[86:33] one of those people constantly trying to<br>[86:34] outthink these.<br>[86:36] >> You know, I always I always say I'd<br>[86:38] rather get scammed by the person who<br>[86:40] back to the architect, the person who<br>[86:42] architect it because at least they take<br>[86:44] pride in their craft and I can at least<br>[86:47] respect that.<br>[86:48] >> It's the people who just copy it that<br>[86:50] that I, you know, it's like the smash<br>[86:51] and grabbers I have no respect for. But<br>[86:53] the people who actually put the thought<br>[86:55] into it, I can at least at that level<br>[86:57] respect, you know, that they that they<br>[86:59] take pride in what they're doing even<br>[87:02] awful awful stuff.<br>[87:03] >> Yeah. So, Taco says, "Tell me tell tell<br>[87:06] me you have teenagers without saying you<br>[87:07] have teenagers notifications<br>[87:10] for every spend." Yeah. No, that's just<br>[87:12] that is the way this the app works. You<br>[87:14] can't step you can't turn it off. It's<br>[87:16] like that is how they that's durable.<br>[87:20] And then Elliot says, "If you have<br>[87:21] WordPress clients who are less<br>[87:23] techsavvy, yeah, good point. One thing<br>[87:25] to worry about is them getting fishing<br>[87:27] email scam related to their website. So,<br>[87:29] it's worth educating them about."<br>[87:31] >> Absolutely.<br>[87:32] >> Had a few clients, says Elliot, carrying<br>[87:34] on in the past, forward emails to me and<br>[87:37] ask to ask if it was legit. Well, good<br>[87:39] for them that they actually did that as<br>[87:40] well. That's brilliant that they<br>[87:42] forwarded the things because they were<br>[87:44] concerned. Right, we're going to round<br>[87:45] this show off with uh a few WordPressy<br>[87:48] events. In that case, let's do this. So,<br>[87:50] here's the first one. So, all of these<br>[87:52] are happening in the next month. It's an<br>[87:54] international spread, but uh here we go.<br>[87:56] First one is to say that if you fancy<br>[87:59] going to Word Camp Europe, which is in<br>[88:01] Kov in Poland, it's the 4th to the 6th<br>[88:03] of June, tickets are now um available.<br>[88:08] Uh you've got, you know, the usual<br>[88:11] general admission ticket, โ‚ฌ50, or you<br>[88:14] got a micro sponsor ticket. when we<br>[88:16] before we clicked go on this episode,<br>[88:18] somebody had something else to add to<br>[88:19] this one. I think seem to remember.<br>[88:21] >> Yeah. The call call for speakers is open<br>[88:23] till the end of this month.<br>[88:25] >> Okay.<br>[88:25] >> Yeah.<br>[88:25] >> So, if you want to be part of the<br>[88:27] speaker, here we go. The open call<br>[88:28] section here is what you want to. So, if<br>[88:30] you would like to speak at that event,<br>[88:32] you can. Um and<br>[88:36] Word Camp Nepal if you're listening to<br>[88:38] us in that part of the world. Um<br>[88:41] the that's now officially got a<br>[88:45] scheduled date and it's coming up soon.<br>[88:46] It's going to be the 23rd to the 24th of<br>[88:48] Jan. So if you're in that part of the<br>[88:50] world, it's happening soon. Uh two more<br>[88:55] word camp zarovsa which we all agreed<br>[88:58] was a marvelous word. Um, I can't read<br>[89:00] any of that because I don't speak<br>[89:02] whatever that is. Um, but I it's<br>[89:05] happening in the in the next the next<br>[89:07] small amount of time. It's definitely<br>[89:09] happening.<br>[89:09] >> It says a day for learning, connecting,<br>[89:12] and creating with WordPress.<br>[89:13] >> Oh, you're so good. Thank you.<br>[89:15] >> I'm learning Spanish.<br>[89:17] >> And what are the dates? I can't<br>[89:19] remember, but it's happening 24th. Let's<br>[89:22] let's imagine that 24th is 24th of<br>[89:25] January. I don't know, but I know that<br>[89:28] it's very soon. So, word camps are<br>[89:31] >> as January.<br>[89:32] >> Yeah. And by the way, um, quickly, uh,<br>[89:35] certain back to Word Camp Europe, um, we<br>[89:38] have the webinar with us. He's just been<br>[89:40] commenting, you know, we've been talking<br>[89:41] about that. It's Jimmy Tavaris, and he<br>[89:44] actually made a lovely video about why<br>[89:49] you should go to work Europe.<br>[89:51] >> Oh, okay.<br>[89:52] >> I'll share the link with you.<br>[89:53] >> Yeah, share the link and we'll stick in<br>[89:55] the next show.<br>[89:56] >> It was such a such a lovely video. I'll<br>[89:58] share it with you.<br>[89:58] >> Yeah, thank you. Um, uh, I've managed to<br>[90:01] translate it using the the button in the<br>[90:03] browser. So, yeah, there we go. 24th of<br>[90:04] January, Word Camp Sarakosa. And last,<br>[90:07] but by no means least, on today's<br>[90:09] agenda, right at the end of the month,<br>[90:10] 31st, spanning into February, se 1st of<br>[90:12] February, 31st of Jan, 1st of February,<br>[90:15] 26 is word camp.<br>[90:17] Again, apologies if I've butchered the<br>[90:19] name of that. So, there are the four<br>[90:20] international ones that I know about.<br>[90:22] There may be some more that I've missed,<br>[90:23] but uh, apologies for that. But, anyway,<br>[90:26] there you go. That's your smorggas board<br>[90:29] of WordPress events that you can take<br>[90:31] part in during the next few weeks.<br>[90:34] Right, last few comments just to clean<br>[90:36] up. What did we got? Um,<br>[90:40] there's a few coming in. Pinball. What?<br>[90:44] Reys has dropped in. Word word camp<br>[90:46] crackoff. Pinball museum. There's a<br>[90:48] pinball museum in Kov I think is what<br>[90:50] you're trying to say.<br>[90:51] >> That sounds pretty cool.<br>[90:52] >> Yeah, that is a cool I'm I'm up for that<br>[90:54] Ree if I'm going to go to that event.<br>[90:56] So, if you want to go to the pinball<br>[90:58] museum, I will come and I will play you<br>[91:00] at pinball and I will lose because I<br>[91:02] >> I actually hope they also have some<br>[91:05] susball tables or Yes. Oh,<br>[91:08] >> we've just organized the whole thing<br>[91:10] now. That's going to be great. Um, and<br>[91:12] then something about stroop waffles. Um,<br>[91:14] bring some strooles to remind us the<br>[91:16] good times. Oh, there's obviously a<br>[91:18] thing going on between taco and uh the<br>[91:20] weather not that's really nice. And then<br>[91:22] there's a few other comments that have<br>[91:23] dropped in. Pinball museum. I'm game.<br>[91:28] Uh D. I don't know why you have the<br>[91:30] numbers after your name either, but you<br>[91:32] know, maybe it's something to do with<br>[91:33] your age in weeks or<br>[91:36] I doubt it. That would make you really<br>[91:38] old. Uh I hope to meet you there,<br>[91:40] Nathan. Indeed, that would be nice. I<br>[91:42] will be there with bells on. I actually<br>[91:46] won't. I'm not going to be taking any<br>[91:47] bells, but<br>[91:48] >> I think you I think you should wear<br>[91:50] bells.<br>[91:50] >> Okay. It's a thing. I'm going to wear<br>[91:52] some bells. Uh we'll see. Um but yeah,<br>[91:57] okay. I'll be at Word Camp Asia as well.<br>[91:58] If anybody's going to that, I'm quite<br>[92:00] looking forward to that in the uh in the<br>[92:02] next few months as well. So if you want<br>[92:04] to hang out, I would love to hear from<br>[92:05] you. That's it. That's all we've got<br>[92:07] time for. It only remains for me to say<br>[92:09] firstly, thank you. Go around the panel.<br>[92:12] Thank you to Mark Benzerane who is I<br>[92:14] don't know where he is, but it looks<br>[92:16] lovely. And the sun hasn't moved in<br>[92:19] >> I I don't know where I am either. Yeah,<br>[92:22] but that sunset, it's cool. It goes on<br>[92:24] for hours. Uh Michelle down there, nice<br>[92:28] to have you with us as well. Thank you.<br>[92:30] And obviously and Mika Blet as well.<br>[92:32] There she is. Hopefully you'll come back<br>[92:34] and join us for another show. That would<br>[92:35] be really nice.<br>[92:36] >> And of course, it goes without saying if<br>[92:39] you if you opened up your keyboard and<br>[92:41] mouse and you typed something, uh we all<br>[92:44] love you very much. You are brilliant<br>[92:46] and uh we appreciate you joining us on<br>[92:48] this particular episode. But it'll come<br>[92:50] out as a podcast tomorrow morning. So,<br>[92:53] look out for that. And an I don't know<br>[92:55] if you know, we have this humiliating<br>[92:57] handwave thing that we do.<br>[92:58] >> I know.<br>[92:59] >> The end of every single episode. Oh, you<br>[93:01] know about it. Okay, that's fine. You're<br>[93:02] all prepared. Look at you.<br>[93:03] >> Oh, this makes my<br>[93:05] >> Oh, yeah. That is so weird.<br>[93:06] >> That's actually<br>[93:09] >> Oh, that's great. Uh, I love that. I'm<br>[93:12] going to zoom into that, I think. Um, in<br>[93:15] which case, we'll see you next week. You<br>[93:17] have a good time. And if the three of<br>[93:18] you want to hang out for a little bit,<br>[93:19] just stick around and we'll speak soon.<br>[93:22] >> But the rest of you, take care. Bye<br>[93:24] >> bye.<br>[93:25] >> Bye. <!-- deep-read:sections end -->