Did AI Just Kill WordPress Let's Chat About It.

Did AI Just Kill WordPress? Let's Chat About It. ![rw-book-cover](https://img.youtube.com/vi/SyU9h8tDnVc/maxresdefault.jpg) 🔗 **Source:** [Did AI Just Kill WordPress? Let's Chat About It.](https://www.youtube.com/watch?v=SyU9h8tDnVc) > [!note]+ Document Notes > tags: #wordpress #artificial-intelligence #cms #web-development > author: Mike > source: YouTube > reference: https://www.youtube.com/watch?v=SyU9h8tDnVc > date created: 2024-12-28 10:30 > > # 🏷️ Title: Did AI just kill WordPress? Let's chat about it. >  ## 🧰 Action Inbox - [H1] Evaluate WordPress as AI-agent endpoint for programmatic site management — ecosystem resilience #wordpress #artificial-intelligence - [H2] Modernize plugin architecture to expose APIs for AI agent interactions — product development #wordpress #artificial-intelligence - [H3] Position design systems as intelligent primitives for AI-native workflows — business strategy #artificial-intelligence ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [WordPress Developer Documentation](https://developer.wordpress.org/) - [WordPress AI Initiative](https://make.wordpress.org/core/tag/ai/) ## 📝 Summary - Mike from Ollie addresses claims that AI will kill WordPress, arguing the platform's massive scale and reach make it resilient - WordPress core team is prioritizing AI integration, potentially changing WordPress 7.0 scope to accommodate AI features - WordPress's value lies in its primitives: decades of APIs, documentation, and open-source infrastructure that AI agents can leverage - Plugin ecosystem must modernize to expose AI-friendly APIs for WordPress to remain competitive - Bottom line: WordPress's size, open-source nature, and rapid AI adoption position it as a viable backend for AI-powered web experiences ## 📖 Main Content The video tackles the question of whether AI will make WordPress obsolete. Mike argues that while AI tools can generate websites quickly, WordPress has structural advantages that ensure its continued relevance. WordPress powers hundreds of millions of websites and serves use cases from small businesses to major publishers like NASA. This massive install base creates inertia that won't disappear overnight, even as AI tools become more sophisticated. The WordPress core team is actively integrating AI capabilities, potentially prioritizing this work over other features like admin redesigns in WordPress 7.0. This represents a strategic pivot to remain competitive in an AI-driven web development landscape. Mike reframes WordPress not as a traditional CMS but as a collection of valuable primitives: mature APIs, extensive documentation, and battle-tested infrastructure. AI agents could use WordPress as a backend endpoint, handling site management programmatically while users interact through conversational interfaces. The success of this vision depends on the plugin ecosystem modernizing to expose AI-friendly interfaces. Legacy plugins using older architectures may limit WordPress's viability for AI agents. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/SyU9h8tDnVc?t=0) — [H1] WordPress death claims and ecosystem context - Key idea: Claims about WordPress being dead often come from specific use cases or outside observers - Evidence: "People saying WordPress is dead... oftentimes from people who are outside the ecosystem" #### ⏱️ [01:30](https://youtu.be/SyU9h8tDnVc?t=90) — [H2] WordPress scale and reach - Key idea: WordPress powers hundreds of millions of websites with immeasurable web reach - Evidence: "100 500 million or something... the reach WordPress has on the web is just almost immeasurable" #### ⏱️ [03:00](https://youtu.be/SyU9h8tDnVc?t=180) — [H3] Long tail user base persistence - Key idea: Millions of WordPress users in specific use cases will continue using it for years - Evidence: "Small businesses in corners of the world... this kind of use of WordPress... this is going to last a while" #### ⏱️ [04:15](https://youtu.be/SyU9h8tDnVc?t=255) — [H1] Enterprise and institutional adoption - Key idea: Major organizations choose WordPress for specific standards and compliance requirements - Evidence: "Huge publishers... NASA like they all use it... very specific standards that have to be met" #### ⏱️ [05:30](https://youtu.be/SyU9h8tDnVc?t=330) — [H1] WordPress as web operating system - Key idea: WordPress functions as an operating system for a large portion of the web - Evidence: "It is an operating system unto itself for part of the web, a large chunk of the web" #### ⏱️ [06:45](https://youtu.be/SyU9h8tDnVc?t=405) — [H1] WordPress core team AI commitment - Key idea: WordPress leadership is seriously and rapidly implementing AI integration - Evidence: "WordPress core team is serious about AI... changed the scope of WordPress 7.0... to accommodate AI" #### ⏱️ [08:00](https://youtu.be/SyU9h8tDnVc?t=480) — [H1] WordPress primitives for AI era - Key idea: WordPress's APIs and maintained infrastructure create valuable building blocks for AI agents - Evidence: "Dozens of APIs, good APIs for decades... actively maintained over time by thousands of people" #### ⏱️ [09:30](https://youtu.be/SyU9h8tDnVc?t=570) — [H2] AI agents using WordPress as endpoint - Key idea: AI agents could use WordPress programmatically while users interact conversationally - Evidence: "Agent... just chose to do it in WordPress... because they can do everything programmatically" #### ⏱️ [11:00](https://youtu.be/SyU9h8tDnVc?t=660) — [H2] WordPress documentation advantage - Key idea: Extensive WordPress documentation makes it easier for AI agents to work with the platform - Evidence: "WordPress has so much information about it... technologies that it has chosen are widely documented" #### ⏱️ [12:15](https://youtu.be/SyU9h8tDnVc?t=735) — [H2] Open source competitive advantage - Key idea: WordPress's open-source nature gives it advantages over private AI web-building tools - Evidence: "WordPress as an open source platform that's about to be AI native is way more competitive than you think" #### ⏱️ [13:30](https://youtu.be/SyU9h8tDnVc?t=810) — [H2] Ollie's AI strategy - Key idea: Ollie positions itself as an MCP with design system primitives for AI agents - Evidence: "Ollie will just be an MCP that you hit that has a certain flavor of style, design, tools" #### ⏱️ [15:00](https://youtu.be/SyU9h8tDnVc?t=900) — [H1] Plugin ecosystem modernization requirement - Key idea: WordPress plugins must modernize their architecture to remain viable for AI agents - Evidence: "Product makers... have to get serious about modernizing... AI agent friendly product suite" #### ⏱️ [16:30](https://youtu.be/SyU9h8tDnVc?t=990) — [H3] Building agent-first products - Key idea: New WordPress products should prioritize AI agent compatibility from the start - Evidence: "Think agent first... simplify this feature down to basically data... a data transaction" #### ⏱️ [18:00](https://youtu.be/SyU9h8tDnVc?t=1080) — [H2] Active adaptation strategy - Key idea: WordPress ecosystem participants must actively build and iterate rather than wait - Evidence: "I'm not sitting around waiting to see what happens... I'm changing the course as we go" ## 📚 References - [WordPress Core AI Development](https://make.wordpress.org/core/tag/ai/) - [WordPress REST API Documentation](https://developer.wordpress.org/rest-api/) - [Ollie WordPress Theme](https://olliewp.com/) ## 🗣️ Paraphrase - WordPress's massive scale and institutional adoption create resilience against AI disruption, even if specific use cases become obsolete - The platform's value lies not in its current interface but in its mature APIs and infrastructure that AI agents can leverage programmatically - Success depends on the plugin ecosystem modernizing to expose AI-friendly interfaces and WordPress core continuing aggressive AI integration ## 📰 Newsletter **WordPress + AI: Evolution, Not Extinction** While some claim AI will kill WordPress, the reality is more nuanced. WordPress's massive install base and mature API ecosystem position it well as infrastructure for AI-powered web experiences. The key insight: think of WordPress less as a user-facing CMS and more as a backend service that AI agents can operate programmatically. With hundreds of millions of sites and decades of battle-tested APIs, WordPress offers something new AI tools can't match: proven scale and extensive documentation. **What this means for developers:** - Consider building plugins with AI agent compatibility from day one - Expose functionality through REST APIs and structured data - Design features as simple data transactions rather than complex user interfaces The WordPress core team is prioritizing AI integration, potentially reshaping WordPress 7.0's roadmap. Now's the time to modernize your approach and think agent-first. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### WordPress - Core AI: Accelerate AI integration roadmap, prioritize agent-friendly APIs - Core: Document programmatic capabilities for AI agent consumption - Community: Create guidelines for AI-compatible plugin architecture - Documentation: Develop AI agent integration guides and best practices - Meta: Ensure WordPress.org APIs support AI agent workflows #### OSPO - Community Engagement: Monitor AI tool integration with WordPress ecosystem - Developer Support: Training on building AI-compatible WordPress products - Strategic Alignment: Track AI adoption metrics across WordPress projects #### DevRel - Developer advocacy: Promote WordPress as AI backend platform - Education: Workshop on building agent-first WordPress products - Developer marketing: Content strategy around WordPress AI capabilities - Community management: Facilitate AI integration discussions ## 🧪 Hypotheses - WordPress sites with modern API-first architectures will see higher AI agent adoption than traditional plugin-based sites - Plugin developers who modernize for AI compatibility will capture disproportionate market share as agents become prevalent - WordPress's open-source nature will give it competitive advantages over proprietary AI web-building platforms - The long tail of existing WordPress sites will persist for 5-10 years despite AI advancement ### 📊 Methodology - Survey WordPress developers on AI integration plans and challenges - Analyze plugin architecture patterns for AI agent compatibility - Track adoption metrics of WordPress AI features in core - Benchmark WordPress API performance against other headless CMS options ### ❓ Questions - How quickly can the WordPress plugin ecosystem modernize for AI agent compatibility? - What specific API patterns work best for AI agent interactions with WordPress? - Will WordPress's AI integration maintain backward compatibility with existing sites? ### 🔮 Future Research - Comparative analysis of headless CMS platforms for AI agent compatibility - Study of enterprise WordPress adoption factors in AI-driven development workflows - Investigation of WordPress performance optimization for programmatic AI usage ### 💡 Implications - Practice: Plugin developers need to rethink architecture for programmatic access - Policy: WordPress governance may need standards for AI agent compatibility - Security: Increased programmatic access requires enhanced authentication and rate limiting - Education: Developer training must include AI agent integration patterns - Funding: Resources should prioritize AI infrastructure over traditional user interface improvements ### 🧠 Learning Styles Assessment Reading level estimate: 10th Grade (Flesch-Kincaid) #### 👀 Visual learners - Present: Video format with speaker presentation - Improve: Architecture diagrams showing WordPress as AI backend, API flow charts #### 🔊 Aural learners - Present: Full audio discussion format available - Improve: Podcast-style summary with key takeaways #### 🗣️ Verbal learners - Present: Clear explanations of technical concepts, analogies to operating systems - Improve: Glossary of AI agent terminology, comparison tables #### 🧩 Kinesthetic learners - Present: Conceptual framework for thinking about WordPress primitives - Improve: Hands-on lab for building AI-compatible WordPress plugin #### 🧠 Logical learners - Present: Structured argument flow, cause-and-effect reasoning - Improve: Decision trees for plugin modernization, competitive analysis matrix #### 🧑‍🤝‍🧑 Social learners - Present: Community discussion format, ecosystem perspective - Improve: Group exercises on AI strategy planning, peer review sessions #### 🧘‍♀️ Solitary learners - Present: Individual reflection on business strategy implications - Improve: Self-assessment checklist for AI readiness, personal action planning template #### 🌿 Naturalistic learners - Present: Ecosystem thinking about WordPress community evolution - Improve: Lifecycle analysis of web platform adoption patterns ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Video has natural speech patterns and clear topic transitions - Improve: Structured transcript with headings, timestamp navigation #### Keyboard navigation - Present: Standard YouTube video controls - Improve: Chapter markers for keyboard-based navigation #### Contrast and readability - Present: Video format may have visual elements - Improve: High-contrast transcript version, adjustable text size #### Text resizing and reflow - Present: Responsive transcript formatting - Improve: Ensure 200% zoom compatibility without horizontal scrolling #### Media and captions - Present: Audio content with transcript provided - Improve: Professional closed captions, downloadable transcript #### Forms and interactions - Present: Basic video interaction only - Improve: Accessible comment forms for community discussion #### Standards reference - Map improvements to WCAG 2.2 AA success criteria 1.2.1 (Audio-only), 1.2.2 (Captions) ### 🌍 DEIB Assessment #### Cultural breadth - Present: English-language discussion from US WordPress perspective - Improve: Examples from global WordPress communities, multilingual considerations #### Inclusive language - Present: Generally accessible technical discussion - Improve: Define technical jargon consistently, avoid assumptions about developer experience level #### Neurodiversity support - Present: Conversational pace allows processing time - Improve: Clear section breaks, consistent topic structure #### Representation - Present: Single speaker perspective - Improve: Diverse voices on AI impact across different WordPress use cases #### Psychological safety - Present: Encouraging tone about WordPress future - Improve: Acknowledge legitimate concerns about job displacement, provide supportive resources ### ✅ Logical Validity #### Strong reasoning - Deductive strength: WordPress scale → resilience against disruption (strong premises, valid conclusion) - Inductive strength: Historical WordPress adoption patterns → future persistence (moderate, based on limited sample) - Causal reasoning: AI integration efforts → competitive positioning (plausible but uncertain) - Analogical strength: WordPress as operating system → backend service (helpful analogy with limitations) #### Fallacies - Appeal to numbers: "Hundreds of millions of sites" doesn't automatically ensure relevance - Hasty generalization: Claims about "people outside ecosystem" based on limited Twitter observations - False dichotomy: Presents WordPress survival vs death without considering partial displacement scenarios #### Tone of voice - Overall tone: Optimistic and encouraging with realistic acknowledgment of challenges ### 🛡️ DARVO Analysis - Deny: No denial patterns present - Attack: No attacks on critics or competing platforms - Reverse victim/offender: No victim/offender reversal - Emotional cues and rhetoric: Positive framing focuses on opportunity rather than threat, uses inclusive community language ## 🎯 Conclusion WordPress's future lies not in competing with AI web builders on user experience, but in becoming the infrastructure layer that AI agents use to create and manage websites. The platform's massive scale, mature APIs, and open-source nature create unique advantages, but success depends on rapid modernization of both core features and the plugin ecosystem. Rather than viewing AI as an existential threat, WordPress stakeholders should embrace it as an opportunity to evolve from a user-facing CMS into a powerful backend service for the AI-driven web. ## 🧱 Refactor Appendix ### 📚 --- ## Full Transcript [00:00] Hey folks, Mike here from Ollie. So, is WordPress dead? Is this thing over? Should we go find different jobs? Maybe, possibly, yes, no, I don't know. [00:09] I think there's some really great commentary happening, and, you know, for sure this is going to be a big thing that hits our ecosystem just like it hits every single ecosystem out there. [00:20] So, yeah, I thought we'd just talk a little bit about it today. [00:23] It's been on my mind a lot, obviously. [00:26] It's on everyone's mind. [00:28] But particularly in how it affects both the ecosystem that I play in, that's WordPress, [00:33] and, you know, I have a popular product in this space. [00:36] And so how does it affect us as a product as well? [00:42] So, yeah, I'm seeing a lot of tweets out there. [00:44] Not a lot, maybe a dozen. [00:46] People saying WordPress is dead. [00:48] and there's definitely something to that line of thinking. [00:52] I get it. [00:54] And oftentimes I feel like the people who are making those claims, [00:58] there's like a very specific use case they use WordPress for. [01:03] And oftentimes I don't even know who these people are actually. [01:06] I'm not saying I know everyone, [01:08] but it's often from people who are outside the ecosystem say that. [01:12] And that makes sense too. [01:13] You know, perception is king. [01:15] People see WordPress one way [01:16] and then people who are in it every day, we see it, you know, a little bit differently. [01:21] But without that context, I see where they're coming from. [01:25] At the same time, there are facts about WordPress, [01:30] about its size and scale and reach that are important to the conversation. [01:37] I don't even know what the numbers are. I should have pulled them up. [01:40] But, you know, millions and millions and millions of WordPress sites out there. [01:45] 100 500 million or something maybe maybe i'm i'm just guessing um from memory but that's a ton [01:54] of websites and on top of that it's just used in so many other ways that we maybe can't track [02:03] and sure so maybe um you know a bunch of those those sites that i mentioned are dead sites or [02:08] whatever that's not the point the point is that the reach wordpress has on the web is [02:15] is just almost immeasurable. It's so big. And that matters a lot when you talk about something [02:23] about saying something like WordPress is dead. WordPress might be dead for your use case [02:30] and your capability level, where you can go off and build the thing that you want and ditch your [02:35] tools. I do it too. It feels awesome. But it totally leaves out of the conversation and context [02:43] the many millions of people who use WordPress every day to run their sites that like [02:48] they're not you will never hear about these people they are using them for very specific [02:53] use cases and little sites and they they have their their plugins and their tools that they use [02:58] and they they know small businesses in corners of the world you'll you you could never even imagine [03:05] um AI is going to come along and cause a lot of disruption but for years and years [03:12] still 10 years maybe this kind of use of of wordpress and how people use it um this is [03:22] going to last a while these people aren't always just automatically going to regenerate their sites [03:27] on astro or or whatever so the long tail reach of wordpress is just it's incredible and the size [03:36] alone will keep it relevant even if they didn't modernize it at all even if they did nothing [03:42] except for where it's at right now the block editor site editor people just use that to [03:48] build their sites i mean huge publishers use wordpress as is pure research nasa like they [03:55] all use it in these different ways and of all the tools out there they still choose this now and [04:00] there are very specific and serious reasons they do this is not just like oh it's like the coolest [04:06] or whatever. They're very specific standards that have to be met in rules and security and [04:12] compliance and all these things. And WordPress ends up in the mix because of things like that. [04:17] All of these things kind of add together to a bigger picture of WordPress than I think most [04:23] people have. And I'm not saying that to defend it or say we do anything right. That's just to add [04:27] context of like, that's how big this thing is. It is an operating system unto itself for part of the [04:34] web, a large chunk of the web, like it or not. So all these cool AI tools are awesome, and I've [04:40] used a bunch of them. They don't have that. They won't have that for a long time, if they ever do. [04:46] And they're private, they're not open source, and that limits to a certain degree how they can grow. [04:54] So all these things are true about WordPress. But the thing is, the WordPress core team [05:02] is serious about AI and implementing it into WordPress. [05:08] Very serious, very on the cutting edge. [05:09] You know, despite what WordPress is now [05:12] or how slow it's kind of moved [05:14] or the perception of how it's moved, [05:17] they are undoubtedly moving into AI super fast. [05:23] Super fast. [05:24] They're even like changed the scope of WordPress 7.0, [05:28] at least it seems like they did, [05:30] to accommodate AI over some other things. [05:33] Some other things that I thought were super important, [05:36] like admin redesign and things like that. [05:39] But they chose AI. [05:41] So they are serious about it. [05:43] And James and his team are on the cutting edge. [05:46] They're always putting new stuff out there, [05:47] trying new things, getting rid of things. [05:51] They are serious about making WordPress a place [06:00] native to and can work with and this gets into how i've been thinking about wordpress [06:09] and ollie and how that fits into wordpress and what we have been so if you think about wordpress [06:15] as it has been as like a cms you can easily be like yeah that's irrelevant uh ai could just [06:22] create that or whatever and uh maybe that's true for some people i know a lot of people don't want [06:28] to build around CMS, many people, most people. [06:33] So when I think about WordPress and how it exists [06:37] like in the AI world, I think of it less of like what it was [06:41] or what it is now, but more of like, what is, [06:44] what are the primitives of WordPress [06:47] that are super valuable to this era? [06:49] Well, we have dozens of APIs, good APIs [06:58] for decades and built upon and extended like it's a it's a pile of technology that has been actively [07:07] maintained over time by thousands of people and made better and debated and put through the ringer [07:17] so all of that when i think about all those assets that i think about wordpress as a more interesting [07:26] like entity in the AI world. [07:29] Like to an agent, [07:31] like if WordPress is, [07:33] all the features of WordPress are exposed [07:35] in their abilities API [07:37] and agents can very easily [07:41] know how to do anything on a WordPress site, [07:44] change posts, create pages, [07:47] change settings. [07:49] You can see a world where [07:51] a person just describes the site they want, [07:54] describes the scope. [07:56] Maybe I need content management. [07:57] I need to be able to add users, [07:59] things like that. [08:01] Well, the agent, [08:03] instead of just creating their own thing, [08:05] creating all this and burning tokens [08:07] and energy and everything, [08:08] they might just see WordPress [08:10] as the node, [08:12] the endpoint that they use to build the site. [08:14] The user doesn't ever mess with WordPress. [08:17] They don't have to hop in and do the, [08:19] you know, the admin onboarding [08:23] and they just talk to their agent, the agent changes it, [08:26] and they just chose, the agent just chose to do it in WordPress [08:29] for all these reasons, because they can do everything programmatically. [08:33] It's been documented well for over 10 years. [08:37] WordPress has so much information about it, so much. [08:41] And the technologies that it has chosen are widely documented as well. [08:49] So all of these things together, when I think about how [08:53] an agent can work with WordPress and use it as the tool and not inundate the user, [08:58] which I think is what a lot of people, their biggest complaint is, the user experience. [09:04] What I think about it as a pile of technology like that, [09:07] well, I don't think we can very quickly say WordPress is dead or make any kind of [09:13] sweeping claims about it. [09:16] But if I had to guess, [09:20] based on the momentum so far, [09:23] I would say WordPress as an open source platform [09:27] that's about to be AI native [09:29] is way more competitive than you think it is. [09:36] And I think these platforms [09:38] that are building really cool stuff like Astro [09:40] and some of these other ones, which are awesome, [09:42] I love using those things too for certain things. [09:46] They're smart enough to know. [09:48] They're looking at WordPress and watching what happens. [09:51] To some degree, they are. [09:54] So I don't know. [09:55] I think there's some really interesting kind of things to dig into there. [10:01] So that's WordPress. [10:04] And then as Ollie is a product in this space, [10:08] we have to figure out how we fit into that as well. [10:10] but we're kind of thinking about it just the same way we are WordPress. [10:14] WordPress is like a node, an endpoint that is hit, [10:16] that has these resources that can be useful to agents. [10:20] Ollie is the same thing. [10:21] Within the WordPress ecosystem, [10:24] Ollie will just be an MCP that you hit [10:30] that has a certain flavor of style, design, tools, extensions, [10:35] and the agent will know how to work with those [10:40] build the site you want that way. [10:43] So it's really, again, it goes back to the primitives. [10:45] The primitives of Alio are that we have like a really good design system [10:50] and patterns and designs and templates [10:53] that all fit together in unison. [10:56] It's like an intelligent design system. [11:00] So that bodes well for us [11:02] because we're a lightweight modern product [11:06] built with these kind of different primitive entities. [11:13] That's super helpful for us. [11:14] It helps us scale and try different things, [11:17] and we'll keep doing that. [11:18] So the other important part about this growth for WordPress [11:23] is that, like, sure, the core team is doing this stuff [11:27] and adding AI, but that doesn't matter much [11:33] if the product ecosystem around it isn't rapidly evolving to start using it. [11:39] Because agents, like the success of WordPress in an agent's eyes [11:43] is probably that it can pull off the thing it wants to do. [11:47] But if like, you know, 75% of the product ecosystem [11:52] is using the old kind of plugin architecture [11:54] and it's not exposed through abilities and things like that, [11:58] it becomes less viable. [12:00] So the product makers out there have to get serious about modernizing the products for this era. [12:08] So that within the WordPress ecosystem, we have this growing kind of AI agent friendly product suite alongside of it. [12:20] That will be important. [12:23] I'm seeing a little bit of it, but WordPress, especially these huge plugins, you know, I don't know if they have much incentive. [12:30] to change how things are they're making good money uh change is hard it's expensive so [12:40] uh but if you were building new product in the space i would encourage you to think [12:43] agent first how can an agent work with this will it be able to how can i simplify this thing down [12:50] um to something an agent can understand and easily do how can i like [12:57] how can I simplify this feature down to basically data you know a data transaction [13:04] that's I think an important way of thinking about things too because that's what this all is so [13:09] anyway these are just some uh random ideas um I've been thinking about it a lot every day [13:16] and I know a lot of people are so I I would just say there's some words of encouragement [13:23] for my fellow WordPress comrades, [13:27] I would be less worried about [13:29] what WordPress has been [13:31] and maybe what that means [13:32] compared to everything else. [13:35] I would say, [13:36] look at this tech stack [13:38] that we've built up over time [13:39] and how can we use that [13:40] and modernize it [13:41] and lean on that [13:43] to grow into this new era, [13:45] which is going to change things [13:46] for the web indefinitely. [13:49] So, yeah, [13:50] I'm encouraged and I'm out there building stuff in this space and trying to, you know, push the [13:57] envelope in my own way and then pushing some of those things to WordPress. And I think that's the [14:03] way. We just got to get out there and do it ourselves and be clever and stay on the pulse [14:09] and build and build and build and delete and delete, iterate. That's just part of it. That's [14:13] what we're doing. We're not sitting here just waiting to find out what happens. I'm not. [14:18] I'm not sitting around waiting to see like what happens. [14:21] No, I'm changing the course as we go. [14:24] That's just the way I'm wired and I have to build. [14:29] So I'm going to build. [14:30] Anyway, I hope this was helpful. [14:32] Let me know what you think. [14:34] Doom or gloom, what do you think? [14:36] Is WordPress doomed or is this thing actually much more interesting than people are saying? [14:43] All right. [14:43] Anyway, thanks for hanging out. [14:44] I'll see you in the next one.  📄 **Full text:** ![[Full Document Contents/Articles/Did AI Just Kill WordPress Let's Chat About It.|Did AI Just Kill WordPress? Let's Chat About It., YouTube]] ## Highlights - web, a large chunk of the web, like it or not. So all these cool AI tools are awesome, and I've used a bunch of them. They don't have that. They won't have that for a long time, if they ever do. And they're private, they're not open source, and that limits to a certain degree how they can grow. So all these things are true about WordPress. But the thing is, the WordPress core team ([View Highlight](https://read.readwise.io/read/01kkvv9awepy48sjmt7r7kkz2r)) - Tags: 👻 ai highlighted - So that's WordPress. And then as Ollie is a product in this space, we have to figure out how we fit into that as well. but we're kind of thinking about it just the same way we are WordPress. WordPress is like a node, an endpoint that is hit, that has these resources that can be useful to agents. Ollie is the same thing. Within the WordPress ecosystem, Ollie will just be an MCP that you hit ([View Highlight](https://read.readwise.io/read/01kkvv9ax03hdaw54bxa5d4c65)) - Tags: 👻 ai highlighted