They're Getting This WRONG With WordPress AI

They're Getting This WRONG With WordPress AI ![rw-book-cover](https://img.youtube.com/vi/KosUzqJn6hw/maxresdefault.jpg) 🔗 **Source:** [They're Getting This WRONG With WordPress AI](https://www.youtube.com/watch?v=KosUzqJn6hw) > [!note]+ Document Notes > tags: #wordpress #artificial-intelligence #wordpress-core #api-integration #developer-tools > author: WP Minute > source: YouTube > reference: https://www.youtube.com/watch?v=KosUzqJn6hw > date created: 2024-03-02 14:30 > > # 🏷️ Title: They're getting this WRONG with WordPress AI >  ## 🧰 Action Inbox - [H1] Test AI Experiments plugin with WordPress 7.0 beta — current implementation not functional #wordpress-testing - [H2] Advocate for open-source AI provider support — limited to big three providers #open-source - [H3] Monitor WordPress AI roadmap development — follow experiments for core integration insights #wordpress-development ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [WordPress 7.0 Beta](https://wordpress.org/news/category/releases/) - [AI Experiments Plugin](https://wordpress.org/plugins/) ## 📝 Summary - WordPress 7.0 introduces AI connectors for OpenAI, Claude, and Gemini integration - Users will input API keys once for multiple plugins to leverage - AI Experiments plugin shows future AI features but currently non-functional - Limited to three major providers, excluding open-source alternatives - Represents centralized approach to AI integration in WordPress ecosystem ## 📖 Main Content WordPress is implementing AI integration through a connector system that allows users to set API keys once for OpenAI, Claude, and Gemini services. This centralized approach aims to prevent duplicate API implementations across multiple plugins. However, the current beta implementation has significant limitations: it only supports three major commercial providers, excluding open-source alternatives, and the accompanying AI Experiments plugin is non-functional despite proper API key configuration. The experiments plugin previews future AI features including title generation, excerpt creation, alt text generation, and image generation capabilities. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/KosUzqJn6hw?t=0) — [H1] WordPress 7.0 AI Integration Overview - Key idea: WordPress 7.0 introduces AI connectors, not full AI prompting capabilities - Evidence: "This is what the final product might look like when it ships into WordPress 7" #### ⏱️ [00:45](https://youtu.be/KosUzqJn6hw?t=45) — [H2] Connector System Architecture - Key idea: Single API key setup for multiple plugins to use - Evidence: "Instead of having all of these plugins or themes have their own API connector" #### ⏱️ [01:30](https://youtu.be/KosUzqJn6hw?t=90) — [H3] Limited Provider Support Concerns - Key idea: Only three major commercial providers supported initially - Evidence: "We're only recommending OpenAI, Claude and Gemini" #### ⏱️ [02:15](https://youtu.be/KosUzqJn6hw?t=135) — [H2] Open Source Provider Gap - Key idea: WordPress lacks support for open-source AI alternatives - Evidence: "For the world's most popular open source product... would really love to see more providers" #### ⏱️ [03:00](https://youtu.be/KosUzqJn6hw?t=180) — [H2] Settings Integration Location - Key idea: AI connectors accessible through WordPress settings - Evidence: "This is going to be under your settings and connectors" #### ⏱️ [03:30](https://youtu.be/KosUzqJn6hw?t=210) — [H1] AI Experiments Plugin Features - Key idea: Separate plugin showcasing future AI capabilities - Evidence: "Abilities explorer, excerpt generation, alt text generation, image generation, content summarization, and title generation" #### ⏱️ [04:45](https://youtu.be/KosUzqJn6hw?t=285) — [H3] Content Generation vs Summarization - Key idea: Current focus on summarization rather than full content creation - Evidence: "We have content summarization. I assume one of the experiments will be content generation" #### ⏱️ [05:30](https://youtu.be/KosUzqJn6hw?t=330) — [H1] Implementation Problems - Key idea: AI Experiments plugin currently non-functional with connectors - Evidence: "AI experiments plugin combined with the connectors feature in this beta just simply does not work" #### ⏱️ [06:15](https://youtu.be/KosUzqJn6hw?t=375) — [H2] Error Messages and Testing - Key idea: Consistent failure across all AI experiment features - Evidence: "Failed to generate prompt. No model found that supports text generation for this prompt" #### ⏱️ [07:00](https://youtu.be/KosUzqJn6hw?t=420) — [H2] Future Development Monitoring - Key idea: AI Experiments plugin indicates future WordPress core features - Evidence: "If you really want to watch what is going to be incorporated into WordPress core in terms of AI, this is a great plugin to follow" #### ⏱️ [07:45](https://youtu.be/KosUzqJn6hw?t=465) — [H3] Technical Testing Configuration - Key idea: Comprehensive testing setup still produces failures - Evidence: "Nightly build of WordPress 7, both plugins, API keys put in. I tried all three API keys. None of it works" ## 📚 References - [WordPress 7.0 Beta Downloads](https://wordpress.org/news/category/releases/) - [AI Experiments Plugin](https://wordpress.org/plugins/) - [WP Minute Community](https://wpmin.com) ## 🗣️ Paraphrase - WordPress 7.0 will introduce a centralized AI connector system that lets users configure API keys once for OpenAI, Claude, and Gemini, which multiple plugins can then access - The AI Experiments plugin demonstrates future AI features like title generation, excerpt creation, and image generation, but currently doesn't work properly with the connector system - There's concern about limiting WordPress to only three major commercial AI providers while excluding open-source alternatives, which seems inconsistent with WordPress's open-source philosophy ## 📰 Newsletter WordPress 7.0 is bringing AI integration through a new connector system! Instead of every plugin managing its own AI API keys, you'll soon be able to configure OpenAI, Claude, or Gemini once in your WordPress settings. Other plugins can then tap into these connections for AI features. The AI Experiments plugin gives us a preview of what's coming: automated title suggestions, excerpt generation, alt text creation, and even image generation right in your WordPress admin. While the current beta isn't fully functional yet, it shows WordPress is taking a thoughtful, centralized approach to AI integration. This could be a game-changer for WordPress users who want AI features without managing multiple API configurations across different plugins. Keep an eye on the AI Experiments plugin to see what AI features might land in WordPress core. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### WordPress - Core AI: Expand provider support beyond big three, test beta integrations - Core: Review AI connector architecture for extensibility - Community: Gather feedback on AI provider preferences - Documentation: Create AI connector integration guides for developers - Accessibility: Ensure AI-generated content meets accessibility standards ## 🧪 Hypotheses - Centralizing AI API management will reduce duplicate implementations across WordPress plugins - The AI Experiments plugin features will eventually be integrated into WordPress core - Open-source AI provider support will be added due to community pressure - WordPress AI features will focus on content assistance rather than full automation ### 📊 Methodology - Beta testing with multiple AI providers to validate connector functionality - Plugin ecosystem analysis to identify common AI integration patterns - Community feedback collection on AI provider preferences and use cases ### ❓ Questions - When will WordPress add support for open-source AI providers like local LLMs? - How will WordPress handle AI ethics and content moderation for generated content? - Will the AI connector system support custom or self-hosted AI models? ### 🔮 Future Research - WordPress AI governance and ethical guidelines development - Performance impact analysis of AI features on WordPress sites - Integration patterns for WordPress AI with existing content workflows ### 💡 Implications - Practice: Developers need to prepare for centralized AI API management - Policy: WordPress may need AI content policies and guidelines - Security: Centralized API key storage requires robust security measures - Education: Users will need training on AI feature usage and limitations - Funding: AI API costs may become significant for WordPress site owners ### 🧠 Learning Styles Assessment Reading level estimate: 8th grade #### 👀 Visual learners - Present: Screenshots of WordPress admin interfaces and plugin settings - Improve: Flowcharts showing AI connector architecture and data flow #### 🔊 Aural learners - Present: Video format with narrated explanation - Improve: Audio-only version for accessibility #### 🗣️ Verbal learners - Present: Clear explanations of technical concepts and API terminology - Improve: Glossary of AI and WordPress-specific terms #### 🧩 Kinesthetic learners - Present: Step-by-step plugin installation and configuration walkthrough - Improve: Hands-on tutorial with downloadable test environment #### 🧠 Logical learners - Present: Systematic comparison of AI providers and feature breakdown - Improve: Decision tree for choosing AI providers and implementation timeline #### 🧑‍🤝‍🧑 Social learners - Present: Community discussion encouragement and Slack channel promotion - Improve: Forum discussion threads and collaborative testing opportunities #### 🧘‍♀️ Solitary learners - Present: Individual exploration of plugin features and settings - Improve: Self-assessment checklist for AI integration readiness #### 🌿 Naturalistic learners - Present: WordPress ecosystem perspective and organic feature development - Improve: Evolution analogy for WordPress AI integration development ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Video has descriptive narration of visual elements - Improve: Full transcript with screen reader-friendly formatting #### Keyboard navigation - Present: Standard WordPress admin keyboard navigation - Improve: Ensure AI features maintain keyboard accessibility #### Contrast and readability - Present: WordPress admin interface meets contrast standards - Improve: Verify AI-generated content maintains readability standards #### Text resizing and reflow - Present: WordPress responsive design supports text scaling - Improve: Test AI feature interfaces at various zoom levels #### Media and captions - Present: Video content with audio narration - Improve: Add closed captions and video transcript #### Forms and interactions - Present: Standard WordPress form handling - Improve: Ensure AI prompt inputs have proper labels and error handling ### 🌍 DEIB Assessment #### Cultural breadth - Present: English-language focused content - Improve: Consider multilingual AI capabilities and international AI providers #### Inclusive language - Present: Technical content uses accessible terminology - Improve: Define technical jargon and provide context for newcomers #### Neurodiversity support - Present: Structured content with clear headings - Improve: Add content warnings for rapidly changing screen content #### Representation - Present: Focus on technical implementation - Improve: Include diverse use cases and accessibility considerations for AI features #### Psychological safety - Present: Constructive criticism of WordPress implementation - Improve: Balance critique with appreciation for development efforts ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Clear connection between connector architecture and plugin integration benefits - Inductive strength: Reasonable conclusions about future WordPress AI direction based on current experimentation - Causal reasoning: Logical link between centralized API management and reduced duplication - Analogical strength: Appropriate comparison to other WordPress standardization efforts #### Fallacies - Appeal to popularity: Questioning "big three" providers based on usage rather than technical merit - False dilemma: Implying WordPress must choose between commercial and open-source providers rather than supporting both #### Tone of voice - Overall tone: Constructively critical but supportive of WordPress development efforts ### 🛡️ DARVO Analysis - Deny: No denial patterns present - Attack: No attacks on accusers present - Reverse victim/offender: No victim/offender reversals present - Emotional cues and rhetoric: Balanced technical critique without inflammatory language ## 🎯 Conclusion WordPress 7.0's AI connector system represents a thoughtful approach to centralized AI integration, though current limitations around provider diversity and functionality gaps need addressing. The AI Experiments plugin provides valuable insights into WordPress's AI future, emphasizing content assistance over full automation. For the WordPress community, this development signals the beginning of native AI capabilities while highlighting the need for broader provider support and robust testing before production release. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] WordPress centralizes AI API management through connector system > [!quote] They're getting this WRONG with WordPress AI by WP Minute via YouTube. Published 2024-03-02. Accessed 2024-03-02. > "WordPress is saying you can just set up your API key once and then pull from there." Demonstrates WordPress's architectural approach to reducing API duplication across plugins. [view highlight](https://youtu.be/KosUzqJn6hw?t=180) #xref #articleseed ID:rw_wp_ai_connectors ### [H2] WordPress AI features focus on content assistance tasks > [!quote] They're getting this WRONG with WordPress AI > "Excerpt generation, alt text generation, image generation, content summarization, and title generation." Shows WordPress prioritizing practical content workflow improvements over complex AI interactions. [view highlight](https://youtu.be/KosUzqJn6hw?t=210) #xref ID:rw_wp_ai_features ### 🔖 Atomic Split Pad (Zettel Candidates) #### [Z1] Centralized API management reduces plugin duplication - Applies to WordPress plugin ecosystem architecture decisions - Reference: 01:30 timestamp discussion of connector benefits - Links: [[WordPress-Architecture]] [[Plugin-Development]] #### [Z2] Open-source platforms face provider diversity tensions - Relevant when major platforms integrate third-party services - Reference: Discussion of "big three" provider limitation - Links: [[Open-Source-Philosophy]] [[Vendor-Lock-in]] ### ✏️ Fleeting Queue - [F1] Test WordPress 7.0 beta AI features when functional — https://youtu.be/KosUzqJn6hw?t=375 #fleeting #inbox - [F2] Research open-source AI providers for WordPress integration — provider diversity concerns #fleeting #inbox - [F3] Monitor AI Experiments plugin updates for core integration signals — https://youtu.be/KosUzqJn6hw?t=420 #fleeting #inbox --- ## Full Transcript [00:00] Today's video is not as complete or [00:02] well-rounded as my normal videos, but I [00:04] wanted to get something out because I [00:06] see a lot of confusion on the socials [00:08] about what's coming into WordPress 7 and [00:11] AI and how the team is integrating AI [00:14] into WordPress and people starting to [00:17] question like, oh, we're going to be [00:17] able to prompt inside of WordPress. We [00:19] manipulate content and code and all this [00:21] stuff. Not yet. At least not of this [00:24] recording on March 2nd in beta 2 of [00:27] WordPress. What you see on the screen [00:29] right now is something called connectors [00:31] and you see OpenAI Claude in Gemini. [00:34] This is what the final product might [00:37] look like when it ships into WordPress 7 [00:41] where users can input their own API keys [00:44] for these three services and then other [00:46] plugins can leverage those API keys to [00:50] do things with AI. It's sort of a way to [00:54] set a standard to instead of having all [00:57] of these plugins or themes have their [01:00] own API connector to various services um [01:03] and having it multiple times throughout [01:06] the dozens of plugins that you're using. [01:08] WordPress is saying you know what you [01:10] can just set up your API key once and [01:12] then pull from there. So there's a few [01:16] what you know a few issues I have with [01:18] that is well right now we're only [01:20] recommending open AAI claude and Gemini. [01:23] I see a lot of open- source stuff out [01:25] there. I see a lot of other third party [01:27] vendors. I mean, I'm not here to talk [01:29] about like who's leading in the frontier [01:31] modeling these days, but for the world's [01:35] most popular open source product, [01:37] obviously like Apache and other stuff [01:39] are very popular, very important, but [01:41] from an end users perspective, I don't [01:43] know many open-source packages that are [01:46] used as much as WordPress. So, we're [01:48] kind of just saying out of the gate [01:50] like, hey, the big three are the big [01:51] three, no matter where you are in the [01:53] world at and at least at this time would [01:55] really love to see more providers here, [01:58] uh, and more ways to leverage the [02:00] open-source providers for sure. Okay, so [02:04] once this ships, and again, we're only [02:06] in beta 2, March 2nd, as the time I'm [02:09] recording this, what you'll do is you'll [02:11] put your either one of your API keys in [02:13] here, and other plugins will be able to [02:15] say, "Hey, give me this stuff. let me [02:16] access this API key and then we'll do [02:19] the AI stuff that we're building, right? [02:21] So developers won't have to have [02:23] theoretically that API key in there. And [02:25] this is going to be under your settings [02:27] and connectors. And this is where you'll [02:29] see this. Here's the problem. This is [02:30] why I wish this video was a little bit [02:32] more well-rounded, a little bit more put [02:34] together is I've tried all three of [02:36] these. I have accounts on all these. [02:37] have API keys on all of these and I've [02:40] put them in and I've doubled this up [02:43] with automatics or the AI team from [02:46] WordPress.org their AI experiments [02:49] plugin. So this is a separate plugin. If [02:52] you go and add a plugin, we'll go add [02:55] plugin. You'll see it as one of the [02:57] recommended plugins here. You can [03:00] install and activate this and that'll [03:02] activate this experiment and you can [03:03] kind of glimpse into the window of where [03:06] the AI team is thinking of what embedded [03:09] AI looks like in WordPress. So we have [03:11] the abilities explorer, excerpt [03:13] generation, alt text generation, image [03:15] generation, content summarization, and [03:17] title generation like I guess the [03:19] standard stuff besides that abilities [03:21] explorer. the standard stuff that you [03:23] would expect to do with with AI in [03:26] WordPress. Though we don't have uh [03:28] content generation here, we have content [03:30] summarization. I assume the one of the [03:33] experiments will be content generation, [03:35] right? To create blog posts and such or [03:38] at least modify drafts and whatnot. U [03:40] but if you install this experiment [03:43] plugin with the understanding that it's [03:45] an experiment, we go to posts. [03:49] You can kind of see this in action. So [03:52] here we have this post. If I click into [03:55] the title, you can see this is one of [03:58] the AI experiments. It just says [04:00] regenerate. And theoretically the user [04:02] will click on that. It'll give you some, [04:05] you know, ideas on regenerating that [04:07] regenerating that title. If I zoom out [04:11] and I come to the post side, what we'll [04:14] see here is we also have a generate [04:16] featured image and an generate exerpt [04:20] and then a generate AI summary. Problem [04:22] is AI experiments plugin combined with [04:26] the connectors feature in this beta just [04:30] simply does not work. If I click [04:33] generate featured image, I get that [04:35] warning. If I click on regenerate, I get [04:38] that warning. It says failed to generate [04:39] prompt. No model found that supports [04:41] text generation for this prompt. Uh, and [04:44] it does it with all of these AI [04:45] experiment features in this plugin. So, [04:48] that's unfortunate, but I did want I [04:50] would love to show that in a more [04:51] complete video, but I wanted to get out [04:54] more of the understanding of how they're [04:56] implementing AI inside WordPress for [04:59] 7.0, at least as of right now. [05:01] Connectors is what's coming to WordPress [05:04] 7. This will allow the user to put in [05:07] their own API keys which hopefully other [05:11] other plugins and other themes will be [05:13] able to leverage your single API use [05:16] right here. The AI experiments is just [05:18] another plug-in from the AI team. And [05:21] this is where I think if you really want [05:23] to watch what is going to be [05:24] incorporated into WordPress core in [05:27] terms of AI, this is a great plugin to [05:30] follow and experiment with. I guess once [05:33] it gets working here, like it's right [05:34] now it's just not working. And I don't [05:36] know why, but nightly build of WordPress [05:39] 7, both plugins, API keys put in. I [05:42] tried all three API keys. None of it [05:44] works, but it's going to work at some [05:46] point. Let me know what you think in the [05:48] comments below. Thumbs up if you like [05:49] the video. Subscribe to the channel if [05:52] you want more. Don't forget the [05:53] wpmin.com. If you're a freelancer, [05:55] agency owner, or just somebody who [05:57] really loves talking about WordPress, we [05:59] got some free courses over at the WP [06:01] Minute. And guess what? If you register [06:02] for a free course, you can join our free [06:04] Slack channel, too, and talk to other [06:06] motivated WordPress users like yourself. [06:09] Whether you're a freelancer or an agency [06:10] running a business, check out the [06:11] wpmin.com. See you in the next video.  📄 **Full text:** ![[Full Document Contents/Articles/They're Getting This WRONG With WordPress AI|They're Getting This WRONG With WordPress AI, YouTube]] ## Highlights - simply does not work. If I click generate featured image, I get that warning. If I click on regenerate, I get that warning. It says failed to generate prompt. No model found that supports text generation for this prompt. Uh, and it does it with all of these AI experiment features in this plugin. So, that's unfortunate, but I did want I would love to show that in a more complete video, but I wanted to get out more of the understanding of how they're implementing AI inside WordPress for 7.0, at least as of right now. ([View Highlight](https://read.readwise.io/read/01kjt90xej5w9bbme2aexnvjwk)) - Tags: 👻 ai highlighted