Where Elementor Is Headed in 2026 - CourtneyR.dev's 2nd Brain

Where Elementor Is Headed in 2026 🔗 **Source:** [Where Elementor Is Headed in 2026](https://www.youtube.com/watch?v=w9WvEvY_hRY) > [!note]+ Document Notes > tags: [elementor, ai-integration, wordpress-development] > author: Matt Medeiros (WP Minute) > source: YouTube > reference: https://www.youtube.com/watch?v=w9WvEvY_hRY > date created: 2025-01-05 08:00 > > # 🏷️ Title: Where Elementor Is Headed in 2026 >  ## 🧰 Action Inbox - [H1] Test Elementor's Angie AI assistant (still in beta) — free to use, no credit limits #ai-testing - [H2] Explore Site Planner for website briefs and wireframes — chat-to-website tool #productivity - [H3] Review Ally accessibility tool for automated fixes — makes accessibility more accessible #accessibility ## 🧭 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 - [Elementor](https://elementor.com) - [Site Planner](https://planner.elementor.com) ## 📝 Summary - Miriam Schwab from Elementor discusses WordPress AI developments and State of the Word 2024 - Elementor has launched multiple AI products: integrated AI features, Site Planner, and Angie assistant - WordPress core AI team achieved all objectives within 6 months for version 6.9 infrastructure - Discussion covers AI adoption challenges, vibe coding acceptance, and future cost concerns - Elementor expanding beyond page building into full website lifecycle management ## 📖 Main Content Miriam Schwab, Head of WordPress Relations at Elementor, shares insights from State of the Word 2024 and Elementor's strategic direction for 2026. The conversation covers WordPress's rapid AI infrastructure development, Elementor's evolving product ecosystem, and industry perspectives on AI-assisted development. The State of the Word event, held on the 58th floor of Salesforce Tower, featured impressive production quality that wasn't visible to livestream viewers due to photography restrictions. Technical issues with the livestream resulted from Salesforce infrastructure problems, not poor planning. WordPress's AI team accomplished remarkable speed in delivering core infrastructure within six months for version 6.9. The Abilities API provides foundational architecture for AI extensibility while reducing plugin conflicts—a dual benefit for the platform. Elementor's AI journey began immediately after ChatGPT's launch, with product development pausing to assess implications. Their current AI portfolio includes integrated page-building assistance, Site Planner for website briefs and wireframes, and Angie, an agentic AI assistant for WordPress management. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/w9WvEvY_hRY?t=0) — [H1] State of the Word Event Experience - Key idea: Event had high production quality invisible to livestream viewers - Evidence: "Everything was about this kind of record like a vinyl record design the coasters the mugs" #### ⏱️ [02:15](https://youtu.be/w9WvEvY_hRY?t=135) — [H2] Photography Restrictions Impact - Key idea: Venue restrictions made livestream appear bare-bones - Evidence: "We weren't actually allowed to take photos inside the venue" #### ⏱️ [04:30](https://youtu.be/w9WvEvY_hRY?t=270) — [H3] Livestream Technical Issues - Key idea: Infrastructure failure was venue-related, not poor planning - Evidence: "Salesforce's infrastructure went down something like that in the building" #### ⏱️ [07:45](https://youtu.be/w9WvEvY_hRY?t=465) — [H1] WordPress AI Team Success - Key idea: Core AI team achieved all objectives within six months - Evidence: "AI team was set up six months ago, had like a few clear objectives and they achieved all of them" #### ⏱️ [09:20](https://youtu.be/w9WvEvY_hRY?t=560) — [H2] Elementor's AI Development Timeline - Key idea: Elementor immediately pivoted to AI after ChatGPT launch - Evidence: "ChatGPT launched and within a very short amount of time Elementor's product development kind of stopped" #### ⏱️ [12:30](https://youtu.be/w9WvEvY_hRY?t=750) — [H3] Current AI Product Portfolio - Key idea: Three main AI products launched with different purposes - Evidence: "Site planner, Angie which is an agentic AI assistant, and integrated AI features" #### ⏱️ [15:45](https://youtu.be/w9WvEvY_hRY?t=945) — [H2] Open Source Model Limitations - Key idea: Open source LLMs don't yet match paid model quality - Evidence: "Open source LLMs the results that they bring just aren't the quality that we would want" #### ⏱️ [18:10](https://youtu.be/w9WvEvY_hRY?t=1090) — [H1] Abilities API Infrastructure Value - Key idea: WordPress AI infrastructure enables extensibility and reduces conflicts - Evidence: "Creating infrastructure for extensibility so that all AI tools of any kind can eventually hook into WordPress" #### ⏱️ [22:30](https://youtu.be/w9WvEvY_hRY?t=1350) — [H3] AI Support Challenges - Key idea: Guard rails essential for preventing disasters in AI integrations - Evidence: "I managed to lead the AI to delete the admin level user of my own site" #### ⏱️ [26:15](https://youtu.be/w9WvEvY_hRY?t=1575) — [H2] Vibe Coding Historical Context - Key idea: AI coding resistance mirrors past technology adoption patterns - Evidence: "When they said we should start building with WordPress pre-ele he was like no I'm gonna handcode it myself" #### ⏱️ [29:40](https://youtu.be/w9WvEvY_hRY?t=1780) — [H3] Natural Language Development Benefits - Key idea: AI democratizes development by removing language barriers - Evidence: "Why should only someone who's managed to learn the language be able to create something" #### ⏱️ [32:20](https://youtu.be/w9WvEvY_hRY?t=1940) — [H2] AI Development Cost Reality - Key idea: AI development costs still significantly lower than human developers - Evidence: "This very comprehensive app that he vioded and how it cost him $800...if he had hired a team, it would have cost way more" #### ⏱️ [35:50](https://youtu.be/w9WvEvY_hRY?t=2150) — [H1] Elementor Product Ecosystem Expansion - Key idea: Moving beyond page building to full website lifecycle management - Evidence: "Web creators journey doesn't just start and end with actually building the website" #### ⏱️ [38:30](https://youtu.be/w9WvEvY_hRY?t=2310) — [H3] Ally Accessibility Tool - Key idea: AI-powered accessibility fixes make compliance more achievable - Evidence: "Makes accessibility accessible...you can go through them and fix fix fix" ## 📚 References - [Elementor](https://elementor.com) - [Site Planner](https://planner.elementor.com) - [WordPress.org](https://wordpress.org) - [State of the Word](https://wordpress.org/news/) ## 🗣️ Paraphrase - WordPress's AI infrastructure development in 2024 exceeded expectations with the core team delivering foundational Abilities API within six months - Elementor has evolved from a page builder into a comprehensive website lifecycle platform with AI-powered tools for planning, building, and maintaining sites - The resistance to AI-assisted coding mirrors historical patterns seen with CMS adoption and page builders, suggesting eventual mainstream acceptance ## 📰 Newsletter **WordPress AI Infrastructure Reaches Production Ready** The WordPress community achieved a major milestone in 2024 with the core AI team delivering production-ready infrastructure in just six months. The new Abilities API doesn't just enable AI features—it reduces plugin conflicts and strengthens WordPress as an extensible platform. For WordPress professionals, this infrastructure opens doors for AI integrations across the ecosystem. Elementor's rapid deployment of AI tools like Site Planner and Angie demonstrates what's possible when building on solid foundations. The democratization of development through AI assistance continues the WordPress mission of making publishing accessible to everyone. Whether you're coding with AI or building with visual tools, the platform adapts to support your workflow. Resources: [WordPress AI Documentation](https://developer.wordpress.org/), [Elementor AI Tools](https://elementor.com/ai/), [Site Planner](https://planner.elementor.com/) ## ✅ Action Items #### WordPress - Core AI: Promote Abilities API adoption through developer documentation and examples - Core Performance: Profile AI-generated code patterns for optimization opportunities - Community: Develop AI ethics guidelines for plugin directory submissions - Training: Create curriculum for AI-assisted WordPress development #### DevRel - Developer advocacy: Demonstrate AI infrastructure capabilities at WordCamps and meetups - Education: Workshop series on Abilities API integration patterns - Developer experience: Improve documentation for AI extensibility - Community management: Moderate discussions around AI adoption concerns #### Community - Contributors: Onboard AI-assisted contributors with code review protocols - Maintainers: Establish guidelines for AI-generated contributions - Sponsors: Fund AI infrastructure development and security auditing ## 🧪 Hypotheses - Open source LLMs will reach production quality within 12 months as hardware costs decrease - AI development costs will increase substantially once adoption becomes mainstream - WordPress market share will strengthen due to early AI infrastructure investment - Page builders will become AI orchestration platforms rather than just visual tools ### 📊 Methodology - Comparative analysis of open source vs proprietary LLM outputs for WordPress development tasks - Cost tracking of AI-assisted development projects over time - Usage metrics analysis for WordPress AI infrastructure adoption - User experience studies comparing traditional vs AI-assisted site building ### ❓ Questions - How will WordPress maintain security as AI integrations proliferate across plugins? - What governance models will emerge for AI-generated content in open source projects? - How will traditional developers adapt their skills for AI-collaborative workflows? ### 🔮 Future Research - Impact assessment of AI democratization on professional developer employment - Security implications of widespread AI code generation in WordPress ecosystem - Economic analysis of AI cost scaling effects on small agency operations ### 💡 Implications - Practice: Developers need to learn AI collaboration skills alongside traditional coding - Policy: WordPress needs AI contribution guidelines for core and ecosystem - Security: Enhanced code review processes required for AI-generated contributions - Education: Traditional development curricula must integrate AI assistance methods - Funding: Investment needed in AI infrastructure security and performance optimization ### 🧠 Learning Styles Assessment Reading level estimate: 12th Grade (Flesch-Kincaid) #### 👀 Visual learners - Present: Product screenshots and interface examples - Improve: AI workflow diagrams, architecture visualizations #### 🔊 Aural learners - Present: Full podcast discussion available - Improve: Timestamped audio segments for key concepts #### 🗣️ Verbal learners - Present: Clear definitions of AI terms and WordPress concepts - Improve: Glossary of technical terminology #### 🧩 Kinesthetic learners - Present: References to hands-on testing of AI tools - Improve: Step-by-step tutorials for trying Elementor AI features #### 🧠 Logical learners - Present: Cost-benefit analysis, timeline comparisons - Improve: Decision matrices for AI tool selection #### 🧑‍🤝‍🧑 Social learners - Present: Community discussion context and meetup references - Improve: Discussion prompts for WordPress meetups #### 🧘‍♀️ Solitary learners - Present: Self-reflection on AI adoption patterns - Improve: Personal assessment checklist for AI readiness #### 🌿 Naturalistic learners - Present: Evolution analogies for technology adoption - Improve: Ecosystem thinking about WordPress AI development ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Proper heading hierarchy and descriptive links - Improve: More descriptive alt text for any embedded media #### Keyboard navigation - Present: Logical content flow and skip links - Improve: Ensure all interactive elements are keyboard accessible #### Contrast and readability - Present: High contrast text and readable font sizes - Improve: Test with actual contrast measurement tools #### Text resizing and reflow - Present: Responsive design supporting zoom - Improve: Verify no content clipping at 200% zoom #### Media and captions - Present: Full transcript provided for video content - Improve: Timestamped captions synchronized with video #### Forms and interactions - Present: Clear action items and navigation - Improve: Consistent interaction patterns ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global perspective on WordPress adoption - Improve: Include diverse geographic examples of AI impact #### Inclusive language - Present: Gender-neutral technical terminology - Improve: Avoid technology-centric assumptions about user capabilities #### Neurodiversity support - Present: Well-structured content with clear headings - Improve: Consistent formatting and predictable information architecture #### Representation - Present: Discussion includes different perspectives on AI adoption - Improve: Include voices from underrepresented groups in tech #### Psychological safety - Present: Respectful treatment of different technical skill levels - Improve: Acknowledge concerns about AI displacement without dismissal ### ✅ Logical Validity #### Strong reasoning - Deductive strength: WordPress AI infrastructure success logically supports broader ecosystem innovation - Inductive strength: Historical technology adoption patterns suggest AI acceptance trajectory - Causal reasoning: Clear connection between early AI investment and competitive advantage - Analogical strength: CMS/page builder adoption parallels effectively illustrate AI resistance patterns #### Fallacies - Appeal to authority: Over-reliance on single perspective from Elementor representative - Hasty generalization: Extrapolating from one company's AI success to industry-wide conclusions #### Tone of voice - Overall tone: Optimistic but realistic about AI challenges, balancing enthusiasm with practical concerns ### 🛡️ DARVO Analysis - Deny: No significant denial patterns observed - Attack: No attacks on critics or skeptics - Reverse victim/offender: Not applicable to this technical discussion - Emotional cues: Appropriate enthusiasm balanced with acknowledgment of legitimate concerns ## 🎯 Conclusion Elementor's 2026 roadmap reflects the broader WordPress ecosystem's rapid adaptation to AI technologies. The combination of solid infrastructure development, practical AI tools, and recognition of adoption challenges positions WordPress well for continued growth. The key insight is that successful AI integration requires both technical infrastructure and thoughtful user experience design, with appropriate guard rails to prevent disasters while maximizing productivity benefits. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] WordPress AI infrastructure enables rapid ecosystem innovation > [!quote] [Where Elementor Is Headed in 2026](https://youtu.be/w9WvEvY_hRY) by [[WP Minute]] via [[YouTube]]. Published 2025-01-05. Accessed 2025-01-05. > "AI team was set up six months ago, had like a few clear objectives and they achieved all of them by the end of the year for rolling out in 6.9." WordPress core team delivered production-ready AI infrastructure in record time, demonstrating platform adaptability. [view highlight](https://youtu.be/w9WvEvY_hRY?t=465#H1) #wordpress-ai #infrastructure ID:rw_elementor_ai_2026 --- ## Full Transcript [00:01] Miriam Schwab, welcome back to the WP [00:03] Minute. [00:04] >> Thanks. Nice to be back. [00:06] >> It's always It's always good to see you. [00:07] The last time we saw each other in [00:09] person was at Press Comp uh back in [00:12] April this year. You travel about 3,000 [00:15] times more than I do, thankfully. [00:19] Uh yeah, I just saw you at uh the State [00:22] of the Word. H how was that? How was the [00:24] How was the vibe there, as they say? Um [00:28] it was a like a very [00:30] nice event. It was uh you know people [00:33] who care about WordPress coming out [00:35] there getting together to talk about [00:37] what was and what you know we look [00:41] forward to. [00:43] As usual the event you know was uh set [00:46] up really nicely. Also [00:49] we weren't actually allowed to take [00:50] photos inside the venue [00:53] >> the Salesforce tower. Yeah, it was in [00:56] the Salesforce tower. Um, so we were [00:59] like on like the 58th floor, like some [01:02] really high floor, but the way they set [01:04] up the space for the event was really [01:07] actually beautiful. Like there was like [01:09] these big lettering for Say the word and [01:10] there was this wall of jazz records that [01:13] you could listen to and there was this [01:14] art like kind of um [01:18] craft thing like you actually could make [01:19] art there. I I did it. I actually have [01:22] it in my living room. Um, and it's a [01:24] shame that we couldn't take photos of [01:25] that because I would have loved to have [01:26] shared, you know, what it looked like in [01:28] there and how they set up. There were [01:29] mugs with state of the word branding. It [01:31] was very, it was a very beautiful event [01:35] and I came out of it feeling inspired, [01:38] which I think, you know, we always need [01:39] a little shot of inspiration to keep [01:41] going and doing doing what we're doing. [01:43] Uh, especially around AI. So AI is on [01:48] the one hand uh a huge opportunity but [01:50] also potentially a threat for a space [01:53] like ours where we're you know we've [01:55] been around for over 20 years. We're [01:56] like kind of legacy in some ways [02:00] doing things what's considered like the [02:02] old school way. So what does AI mean for [02:04] us? But what's impressive is that the AI [02:07] team was set up six months ago, had like [02:10] a few clear objectives and they achieved [02:12] all of them by the end of the year for [02:14] for rolling out in 6.9. super impressive [02:17] speed um and focus and that that is also [02:21] inspiring to know that the project [02:23] leadership and those leading the way for [02:27] how we implement AI uh are very focused [02:30] and um [02:33] dedicated to making WordPress uh not [02:37] only like on like have parody with the [02:40] world of AI but potentially leading the [02:41] world of AI. So yeah, so I came away [02:43] feeling good and it was it was really [02:45] nice event and it was great to, you [02:47] know, catch up with people and yeah, it [02:50] was uh I'm glad I went. It was [02:52] unfortunate that you couldn't take those [02:53] photos cuz that was actually one of my [02:55] criticisms of of the event was uh you [02:58] know I didn't obviously I did not attend [03:00] but uh I would have liked to. It just [03:02] you know logistically it just wasn't [03:04] going to work out. But one of the things [03:07] that I noticed is just the way it was [03:09] shot and presented on the live stream. [03:11] Even though the live stream kept [03:12] breaking, it really just looked like [03:14] we're in this room talking to like 12 [03:16] people. Whereas like Tokyo last year was [03:19] on a stage, there was multi- camera [03:21] angles and I was like, oh man, we're [03:23] we're going into Apple day with [03:26] WordPress event like this and I love [03:28] that. And I was like, this is great. I [03:29] mean, the temperature in the room was [03:31] tough back in Tokyo last year, but I was [03:33] like, I can't wait to see what's going [03:35] to happen this year. And I was like, [03:36] what are we are we just in a side office [03:38] somewhere? Like, what's happening? Oh my [03:40] gosh, I didn't think of it from that [03:42] perspective. [03:42] >> Yes, [03:43] >> but that you're right because the only [03:45] thing we were allowed to take photos of [03:46] and I guess the camera angle was based [03:48] on that as well was the view, [03:50] >> right? [03:50] >> So that's why on camera you saw like a [03:54] smattering of us in a room which by the [03:56] way the room went farther back [03:58] obviously. Um and all you could see was [04:00] whoever was speaking and the window [04:01] behind them because they weren't allowed [04:03] to show anything. By the way, I don't [04:04] know why uh we weren't allowed to take [04:06] photos in there. It was a space like any [04:08] other space, meaning like it was very [04:10] nice. I've been in other very nice [04:11] spaces. [04:14] By the way, I don't think that this uh [04:16] regulation about taking photos was an [04:17] automatic thing. It was related to the [04:20] space that we were using. And by the [04:22] way, just about the live stream [04:24] this the you know the talks start and [04:29] there's you would think that we didn't [04:31] know that there was issues there were [04:32] issues with live stream but uh pretty [04:33] quickly people started messaging me [04:35] actually to tell me uh the live stream [04:38] isn't working. So I started messaging [04:40] people there that I know had something [04:42] you know had were connected to the [04:44] logistics or whatever. basically [04:47] Salesforce's [04:49] infrastructure went down something like [04:52] that like in the building like something [04:54] really crazy and terrible in terms of [04:56] timing obviously and they were like [04:59] struggling with it to get it back up and [05:00] running. They even had some kind of [05:01] redundancy and that also didn't manage [05:04] to kick in. Basically, it wasn't that [05:05] they didn't care and that they didn't [05:07] know. They did know and there were a lot [05:08] of people scrambling around, right, to [05:10] get things up and running and they just [05:12] they just couldn't. And it was because [05:13] it was related to the venue. [05:16] >> Yeah. [05:16] >> So that was so unfortunate also um [05:20] because I don't know if we could have [05:21] any indication of how many people were [05:23] interested in trying to view it remotely [05:24] because they couldn't even get through, [05:26] >> right? [05:27] >> And like people just gave up eventually [05:29] because why should they try to watch [05:30] this thing they can't watch? So that was [05:33] a shame. But um you know it's recorded. [05:36] At least that worked so people can see [05:38] it that way. And yeah, I guess it's [05:40] important to share that we weren't [05:42] allowed to take photos of the the [05:44] interior and that's why it looked so [05:46] bare bones. It wasn't bare bones. [05:48] >> Yeah, it definitely would have changed [05:49] my criticism. [05:51] >> No, it's totally genetic criticism. [05:53] >> Yeah. [05:54] >> Yeah. No, and and you know, I know it [05:56] can sound like a nitpicky thing, but uh [05:59] I criticize an event like that and I [06:01] said this in the podcast because like I [06:04] want automatic to represent us in the [06:06] best way. So, if that's like our Apple [06:09] day, let's say, uh, state of the word, [06:12] um, you know, and Techrunch and other, [06:14] you know, bigger media outlets are [06:16] covering it, I pro I want to see a [06:18] little bit more so that people are like, [06:20] are they running out of money? [06:27] >> I have to I'll show you what I have. [06:29] But, so, you're totally right and I [06:31] agree with you. uh want WordPress to [06:33] lead us in in a strong way and we should [06:35] look like we're a thriving ecosystem and [06:37] in some ways this type of event is that [06:39] but look this the branding was so [06:41] beautiful [06:44] >> I have this weird blur thing going on [06:45] but [06:46] >> it says that anyways everything was [06:47] about this kind of record like a vinyl [06:50] record um design the coasters the the uh [06:54] mugs um the swag we got very nice [06:56] t-shirts and hats and then also the art [06:58] the art was like um you picked the vinyl [07:00] record and then you like painted it [07:03] >> and it actually turned out really cool. [07:05] So, so it was on the level of Tokyo from [07:09] that that perspective. It was a very [07:10] high quality event. It's just I guess [07:12] the only people who could enjoy that [07:14] were the people that were there. [07:15] >> Yeah. [07:16] >> Well, it's good to know. I mean, I I [07:18] know they did like this marketing [07:19] montage of Tokyo last year like leading [07:21] into War Camp and I couldn't find that [07:23] video again. I forgot where it was even [07:24] posted. U but maybe they'll do something [07:27] you know maybe there were some [07:28] videographers there and you know [07:30] >> maybe but again can they even show [07:32] anything [07:33] >> right [07:34] >> like what can you show people standing [07:36] against the windows that's really [07:38] >> it's crazy [07:40] >> um well let's let's take it to [07:43] >> let's take it to AI um AI is a core uh [07:46] part of like I guess a lot of innovation [07:48] happening across many companies uh in in [07:50] our sector you know this this year and [07:53] of course years before [07:55] I know AI uh Elementor's AI integration [07:58] for Elementor the site building product [08:01] um when it first came out there was just [08:02] a lot of criticism like oh my god like [08:04] because it was early like Elementor was [08:06] ahead of the you know AI building space [08:08] and it's just like how do I turn this [08:10] thing off but AI has gotten arguably [08:14] much better and I'm sure the experience [08:16] has gotten much better. Um, is there a [08:19] core guiding principle at Elementor on [08:23] integrating AI and how you approach it [08:25] in an open way so it's not just we're [08:28] not just getting AI taxed I guess is is [08:30] my best phrase for it. [08:33] So from the start basically [08:36] basically I think it was something like [08:38] chat GPT launched and within a very [08:40] short amount of time Elementor's product [08:43] development kind of stopped not exactly [08:45] stopped but there was like a kind of [08:47] hold on what does this mean for us and [08:50] an AI team was like very quickly set up [08:53] in element there was like an [08:54] understanding that u whatever AI means [08:57] for us and for the industry we have to [08:59] be part of it now and we can't wait [09:01] another second. So that's why we [09:04] launched the the first the first like [09:07] approach or uh version of AI in [09:10] Elementor/WordPress [09:12] which was it kind of straightforward um [09:15] which is like here create an image [09:16] create some HTML create CSS write a blog [09:19] post whatever that kind of stuff. Um, [09:22] there were some interesting pieces of [09:24] functionality that were part of the AI [09:25] then which was like this uh if you were [09:29] like building a page then it would [09:31] suggest to you the next section of the [09:33] page and then like kind of lay it out [09:35] for you. Didn't do a great job of that [09:37] but it was like you can the thinking [09:39] behind that was okay let's also be [09:41] proactive for our users and uh try to [09:44] like hold their hand while they're [09:46] building [09:47] because it's also new. our team and all [09:50] of us were just like trying to figure it [09:52] out as we go along and try to find the [09:53] best uh and most valuable application. [09:56] So we started with that and basically [09:58] because we started early even if the [10:00] first uh application wasn't amazing and [10:02] people were like turn it off. a lot of [10:04] people want to turn off because of that [10:05] suggestion thing because they're like [10:06] stop it why are you building this next [10:09] section of my page but um since then [10:12] we've been learning a ton and you know [10:14] that we can learn we have a lot of data [10:16] around the usage so we can then uh [10:19] improve the applications since then [10:21] we've launched a few more AI products we [10:24] have this one called site planner which [10:26] is an external tool which is free to use [10:29] uh planner. and people can go and chat [10:33] their way to a website brief site map [10:36] and uh what we call the wireframe of a [10:38] site. But the wireframe is like what the [10:41] way I see it is like 80% of the way [10:42] there to website and then like the [10:44] professionals can come in and tweak it [10:46] and polish it and and wrap it up in and [10:48] bring their vision to the to the like [10:50] the final leg of the project. So there's [10:52] that and then you can launch directly uh [10:54] into hosting or downloaded zip or [10:57] whatever. Um and then we also launched a [11:00] product which is still in beta which is [11:02] called Angie which is an agentic AI [11:05] assistant for WordPress. So it sits [11:06] there next to you in the dashboard and [11:08] it can do all sorts of things in many [11:11] ways with that the sky is the limit but [11:13] also because the sky's is the limit it [11:16] can still do weird things and so that's [11:18] why it's still in beta. So on the one [11:20] hand you can do things with it and [11:21] you're like oh my gosh that's amazing. [11:23] And then on the other hand you'll try to [11:25] do things with it and it's still like a [11:26] bit wonky. Um, but we hope to like [11:30] fine-tune that pretty soon and bring it [11:32] out of beta. But people can test it. [11:33] It's in the WordPress repo and it's free [11:35] to use. There's no limitations because [11:38] AI costs, right? Like not because of us, [11:42] but because AI just costs. So at some [11:44] point there's credits involved in this [11:46] stuff. But at the moment like Angie and [11:48] Site Planner, although there's obviously [11:50] cost to us uh for use, we are not [11:52] charging anyone. So feel free to test it [11:55] out. curious if like from what you can [11:57] reveal and I'm not asking you to reveal [11:59] anything secret but one of the other [12:02] criticisms I have of the um AI [12:05] initiatives at automatic and and of [12:07] course through WordPress.org and such um [12:10] like James team and whatnot is I'm not [12:12] hearing a lot about open-source models. [12:15] I'm hearing a lot about like, oh, you [12:16] know, grab a token from ChatgBT, grab a [12:18] token or OpenAI, grab a token from [12:21] Anthropic, for Claude, and like you [12:24] said, these all cost. I mean, there will [12:26] be a cost for open source models anyway [12:28] because you have to run it somewhere. [12:30] But I'm just curious like is there an [12:32] initiative to use any of the open- [12:33] source models that aren't tied to, you [12:36] know, these companies raising trillions [12:38] of dollars and only arguably going to [12:40] raise the price like all streaming [12:42] services do to us, uh, you know, [12:44] throughout the year? Um, is there any [12:46] thought process on like which models to [12:48] select? Can you talk about which models [12:50] you select and is open source any part [12:52] of that discussion internally at [12:54] Elementor? So I think everyone aspires [12:57] to using open- source uh LLMs but here's [13:00] what I understand and I also see from [13:02] the experience with our own team even [13:04] with the paid models the more advanced [13:08] models bring way better results like [13:11] significantly better results than the [13:13] lower models and so with open source [13:17] LLMs the results that they bring just [13:20] aren't the quality that we would want [13:23] for a valuable experience in using AI as [13:26] part of your web building, web [13:27] management experience. It's just not [13:28] there. So theoretically, you could you [13:31] could hook hook into them, right? Like [13:33] um a lot of AI tools and ours I think [13:37] will have that option as well. You can [13:39] hook into different LLMs of your choice. [13:44] other tools and actually actually I [13:46] think this is how we're going to do it [13:47] will use a particular LLM depending on [13:51] what it is that you're trying to do [13:52] because Claude might be better for one [13:54] thing and Gemini might be better for [13:55] another thing and it will like make that [13:56] decision for you. Um, so we're in this [14:00] world where [14:02] even like very high level LMS can be [14:05] trickier to use than others and really [14:09] the results uh can vary w wild wildly [14:12] almost [14:13] >> in terms of the quality. So I think even [14:17] though being part of an open source [14:19] world and or leading the open source [14:21] world even with WordPress [14:23] um and and Elementor being a significant [14:26] uh player in that world and us all [14:28] generally aspiring to open source in [14:31] currently it's not realistic in order to [14:34] make AI useful unfortunately but it's [14:36] it's possible that it will get there [14:38] things move so fast that uh in six [14:40] months time a year the open source LMS [14:43] might be good enough for people to, you [14:45] know, for it to suffice. But yeah, at [14:47] the moment it's just not there. [14:49] >> When you stepped away from the uh state [14:52] of the word, feeling inspired about the [14:53] AI stuff, if you take your elementor hat [14:56] off for a moment, what was the most [14:59] aspiring part of that AI discussion for [15:02] you? Like what gives you renewed energy [15:05] for WordPress because of AI? [15:09] >> So, first of all, the speed definitely [15:11] plays a role. meeting. Just the fact [15:12] that they like said they were going to [15:14] do something and they did it, it's very [15:16] um reassuring and inspiring. Also, the [15:19] the thinking behind it, I think, is [15:20] really great. The team that's leading [15:22] AI, uh James, uh Felix, Jason, Jeff, I [15:28] think that's who's on the team, and some [15:30] others, sorry if I'm forgetting people. [15:32] They're all bringing really um valuable [15:36] perspectives to it and um they're I [15:39] think they're making really good [15:40] decisions and uh taking things in a [15:42] really good direction. In particular, [15:44] the abilities API [15:47] um so on the one hand the work that [15:50] they've done on AI is very [15:51] infrastructure level. You can't see it. [15:55] Um it's almost like another world of [15:58] WordPress. Meaning WordPress itself on [16:00] its own in core is essentially an [16:02] infrastructure for extensibility. And [16:04] that's where a lot of the value comes [16:05] into play. And that's what they're doing [16:08] with AI. It's creating infrastructure [16:10] for extensibility so that uh all AI [16:13] tools of any kind can eventually hook [16:15] into WordPress and get it to do stuff [16:17] which is amazing. [16:20] Um the abilities API also is great in [16:24] general for um reducing conflict issues [16:28] between products and plugins in [16:30] WordPress. It's actually got this [16:32] additional benefit not just for AI. So [16:35] that's a really smart perspective. It [16:36] pulls WordPress forward not just for AI [16:38] but also as a platform. On the on the [16:41] flip side, the challenge with what [16:43] they've been doing until now is that you [16:45] it's invisible. meaning everyone who [16:48] downloaded 6.9 doesn't see the AI uh [16:51] implementation. It's just, you know, [16:53] under the hood. So, I'm hoping that [16:55] we'll start to see more developers, [16:58] product creators. By the way, you don't [17:00] even have to be a developer anymore. [17:01] Vibe coders creating like, you know, [17:05] experiments, PC's, like tooling that [17:08] utilizes the the abilities API so that [17:10] people can start to see the power of it. [17:13] Um, so yeah. So yeah, so that's what I'm [17:15] inspired about the fact they did it so [17:17] fast. They did what they set out to do. [17:18] It's a very smart approach in my [17:21] opinion. Um they're very passionate and [17:23] energized about it too, which gives [17:25] which energizes others. It's it's uh [17:28] they're a good team. [17:29] >> Yeah. Yeah. And and I fully agree with [17:31] that. That was you know, one of the [17:33] criticisms I mean look this one of the [17:35] criticisms I wrote about and I didn't [17:37] mean to turn I don't mean to turn this [17:38] into like a review of State of the Word, [17:40] but you were boots on the ground, didn't [17:41] we? [17:42] Here. um was was just that like this [17:46] year was [17:49] in a sports term like it's a rebuilding [17:51] year, right? Like we [17:54] we're we're getting these features that [17:55] are just setting the groundwork for, you [17:57] know, version 7 and beyond in 2026, you [18:00] know, and future stuff. It there wasn't [18:02] anything tactile that people could touch [18:04] except for like the cool notes feature, [18:06] which, you know, hey, I appreciate, but [18:08] it's not like whoa, we're not [18:09] earthshattering anything with that [18:10] stuff. Um, but in the same sense at what [18:13] I wrote in the piece was to give us give [18:16] WordPress some grace because how 2025 [18:19] started [18:21] compared to where we've ended was a lot [18:23] different because 2025 started with like [18:26] what is even happening to WordPress [18:28] anymore and now we're like okay we've [18:30] got some direction and people are [18:31] inspired by it. So, uh, that is a good [18:34] thing. Uh, you know, in my opinion, [18:36] >> I was talking to Brian Cords because I I [18:38] started just like you said, I'm not a [18:40] developer and cloud code is so darn [18:43] powerful. It's doing some stuff that is [18:45] just I mean, it's getting it right and [18:47] it's doing it right and I'm testing [18:49] things against the plug-in checker and [18:51] I'm I'm talking to other WordPress [18:52] developers like, "No, this thing what [18:54] you've built is working." And so, two [18:56] things. Um, I'm actually a little [18:59] worried about the abilities API as [19:01] exciting as it is. It almost sounds like [19:03] we're opening the door, like the support [19:05] doors for people to be like, I connected [19:07] my, you know, MCP up to my WordPress [19:09] site and Elementor, you're not building [19:11] the pages the way I'm telling AI and [19:13] it's like, whoa, whoa, whoa. Like I now [19:15] I can't support you through your MCP and [19:18] whatever AI tool you're using. Um I you [19:21] know no real question here but I just [19:22] wonder if you have any thoughts of like [19:24] what the world looks like for supporting [19:26] WordPress when cuz I see the future that [19:29] you see like I can just chat with my [19:31] chatbot and say build me these 20 pages [19:33] insert this content put these images on [19:36] these product pages here hit enter and [19:38] let it go and then if it doesn't work [19:40] somebody submits a ticket to Elementor [19:42] and says hey uh this isn't working. uh [19:45] any thoughts on like what that vibe code [19:47] world looks like for the those of us who [19:49] support customers with with WordPress? [19:53] >> So when people are creating their MCPs [19:57] for their own products, they need to put [19:59] guard rails in place. That's a really [20:01] important part of AI in general. [20:03] >> Just even for the LLN's, you know, [20:05] they're constantly talking about how [20:06] they can keep us secure um without [20:08] exposing, you know, dangerous [20:10] information or getting access to private [20:12] information, right? there's like a [20:14] constant struggle between being a very [20:16] open form of communication essentially [20:18] with access to a lot of information [20:20] while keeping guardrails in place to uh [20:22] keep us all safe and secure. So it's the [20:25] same with your own product. For example, [20:27] Elementor's uh Angie uh plugin uh [20:31] solution um allows you to do all sorts [20:34] of stuff with Elementor, but the team [20:36] has put guard rails in place to make [20:38] sure that you don't like delete all your [20:40] site. I at one point found something [20:42] that led to guardrail. For example, in [20:44] the early days of Angie, I managed to uh [20:47] lead the AI to delete the admin level [20:50] user of my own site, [20:53] which is obviously something we don't [20:54] want to happen. So, if we want people to [20:57] be able to create MCPs for WordPress or [20:59] for our own products, we need to have [21:01] guards in place that don't allow them to [21:03] push the product past a point of [21:06] disaster. Um, and so with regards to [21:09] support, that's going to be a big part [21:11] of it. And we'll keep learning and [21:12] tweaking as we go along because like I [21:14] said, the sky's is the limit in a way. [21:15] So we don't because there's infinite [21:17] like things that people can ask AI to [21:19] do, we can't uh take them all into [21:21] account and then while we try to take as [21:23] much as possible into account, we only [21:24] often learn things like when I managed [21:26] to do that to my own site. So um but [21:29] there's another interesting angle of [21:30] support which came up with Angie because [21:32] Angie allows other products to integrate [21:36] uh creative recipes and integrate with [21:38] Angie. So we have integrations from KCO [21:41] block from WS form and the events [21:43] calendar and um some other uh stellar WP [21:47] plugins that can be managed through the [21:49] Angie in interface. But this question [21:52] came up. What if there's an issue? Who [21:55] is responsible for the support there? [21:57] And how can we identify where the issue [22:00] is coming from? So that that's another [22:02] learning for our team. Our team put in [22:03] place a UI which tells the user, okay, [22:06] right now you're actually interacting [22:07] with the events calendar or with a [22:10] crocco product or whatever and it [22:13] indicates whether that will like help [22:16] reduce uh support issues and streamline [22:18] things. Who knows? Um, but it's like [22:21] learning and trying to constantly [22:23] improve and create uh greater clarity [22:25] and transparency, guard rails, all of [22:28] that is something that product [22:29] developers just need to take into [22:31] consideration. [22:32] >> Yeah. Because I think it's going to be [22:34] and and again, this is just healthy [22:37] criticism. I think what what we're [22:40] talking about right now is an end user [22:42] who goes and does something and like [22:44] they're more techsavvy right now because [22:46] AI is still, you know, for the general [22:48] population it's cutting edge. Not a lot [22:49] of people are still using it, but I [22:51] think what automatic and WordPress is [22:53] going to strive for is a like openness [22:57] everywhere. And we're not going to have [23:00] a say of I mean, we're going to have a [23:02] say in in terms of like open source. The [23:05] point I'm getting at is I think what [23:07] WordPress is going to strive for is say, [23:09] "Hey, any chat system talk to WordPress, [23:11] which means they're going to let [23:13] everybody in through the doors." And [23:16] then we as product people are going to [23:17] have to be like, "Okay, hold on [23:18] everybody, before you come down this [23:20] aisle, I need you to understand that uh [23:23] you can't do this, that, and the other [23:24] thing if you come down this aisle." [23:27] >> And that's going to be kind of [23:28] interesting. I think while WordPress [23:30] pushes us to that openness for the web, [23:33] we're going to have to be the ones, like [23:34] you said, to get those guard rails [23:37] correct. Um, [23:39] >> yeah, there will be guards [23:40] >> experience. [23:41] >> It's definitely a new experience. There [23:42] will be guard rails that are like to [23:45] protect users and their websites, but [23:47] there also just be uh functionality that [23:50] like at certain at certain points along [23:52] the way won't be manageable by AI. like [23:55] you have to create uh the tools they're [23:57] called tools like for your product that [23:59] makes them accessible to AI and if you [24:01] haven't exposed all the functionality of [24:03] your product all the tools then some [24:05] things just won't be doable. So um like [24:09] in Angie for example uh our team [24:12] recently implemented functionality where [24:14] Angie will tell you if it can't do [24:15] something rather than like pretend or [24:18] lead you on. It will just be like that [24:20] that's something I can't do. And it's [24:23] it's again a matter of greater [24:24] transparency and clarity. Um but also [24:27] realizing that while AI seems infinite [24:30] and like can be all and do all there are [24:34] there are going to be limits. Um I'm you [24:36] know AI moves so fast that whatever is [24:38] limit today might not be in limit in a [24:40] month but that's just how it's going to [24:42] be because also especially if you take [24:44] plugins into consideration that are like [24:46] almost platforms in in of themselves [24:47] like element I mean the capabilities [24:50] behind the scenes of element in the [24:51] element page builder is just enormous. [24:54] >> Yeah. [24:55] >> Um so you know it's uh it's a whole [24:59] world. [25:00] >> Yeah. There's another thing I'd like to [25:02] get your your thoughts on. Again, no [25:04] direct question, but um when I was [25:06] talking to Brian, and I'll try to link [25:08] up that uh live stream in in the show [25:10] notes here. We were talking about how I [25:13] use Claude Code and how I I I talk to [25:17] it. I again, I'm not a developer, but I [25:19] I know what needs to be done from like a [25:22] product perspective. I mean, 90% needs [25:24] knows what needs to be done from a [25:26] product perspective, from a WordPress [25:28] sustain sustainable perspective. and I [25:31] talked to it like I'm helping it learn [25:34] and understand this thing that I'm [25:36] building, right? And we were chatting [25:38] and it like it dawned on us like it's [25:40] not that much different than if we [25:42] hired, you know, some freelancer and [25:45] we're like, "Hey, we got a task for you. [25:47] Go and build it." And even sometimes the [25:49] human doesn't get that right. And and [25:52] we're there are people out there [25:54] criticizing folks for using AI to build [25:57] simple pieces of software. It's like, [25:58] well, you know, even if I gave this to a [26:00] human, I bet I'd be going back and forth [26:03] with them and they'd be getting it wrong [26:05] or trying to cut corners. [26:08] Should we be upset at the folks? And I [26:10] guess here's the question where I want [26:11] your remark is, should we be upset at [26:14] the folks who are adopting this to build [26:16] stuff with? I remember and you remember [26:19] 15 20 years ago when some when page [26:21] builders first came out, people like, [26:23] "Oh god, you're using a page builder. [26:25] You're doing it wrong." Here we are in [26:27] 2025 where it's like if you're not using [26:29] a page builder, you're doing it wrong [26:32] and like the whole script was flipped. [26:35] Like I I don't know if you have any [26:36] thoughts on like the vibe coding thing [26:38] right now. Is it bad? Like how do you [26:41] perceive it? Especially at Elementor [26:43] where there's like now you're [26:46] responsible for that freelancer [26:48] agencies, everything, the site, the [26:50] accessibility, the AI, the email [26:53] sending. Like there's so much that [26:54] Elementor does now. [26:56] thoughts on people leveraging AI. [26:59] >> So, by the way, that like uh conflict of [27:02] how can you do it this new fangled way [27:04] even goes back to the early days of [27:06] CMS's. [27:08] >> Sure. [27:08] >> We were just uh talking at Elementor. [27:10] So, one of our um veteran WordPress [27:15] developers like he's been like working [27:17] with WordPress for a very long time. Uh [27:20] they were joking that when they said we [27:22] should start building with WordPress um [27:25] pre-ele he was like no I'm gonna [27:28] handcode it myself right [27:30] >> like what I'm not going to use this [27:32] thing I'm going to do it from scratch [27:34] and then people were like oh of course [27:36] you can use a CMS and then page came [27:37] along they're like ah what is this how [27:39] can you do that it's so unprofessional [27:40] we need to handcode it ourselves but in [27:42] a different way and then they became [27:44] comfortable with page buildilders more [27:45] or less and now we have vibe coding And [27:49] I think vibe coding is amazing. Like in [27:52] the end, what is a developer writing a [27:55] language? It's but it's like uh French. [27:59] Well, to me or I don't know, you know, a [28:01] foreign language uh where if I was told [28:04] to do all my stuff in French, I would be [28:07] breaking my teeth and it would be hard [28:09] on my brain because I don't know the [28:10] language. So people who don't know how [28:12] to develop and I I'm not like it's it's [28:15] obviously more uh there's more deficit [28:19] than what I'm saying but like the [28:21] difference between a developer and a [28:23] non-developer is that the developer [28:24] knows the language and the non-developer [28:26] doesn't know the language. So just like [28:29] open AI uh or LLM's now kind of uh make [28:34] all languages accessible like I was [28:36] watching someone at work like a few [28:39] months ago. I don't know. It had never [28:40] dawned on me building vibe coding a like [28:43] a little app in uh Chachi PT in Hebrew. [28:47] I was like you do that in Hebrew and [28:48] then obviously OpenAI doesn't care what [28:52] language you write you're speaking in or [28:54] writing in because to them to it all [28:56] languages are whatever it's just flat. [28:58] So the same with vibe coding like why [29:01] should only someone who's managed to [29:02] learn the language be able to create [29:05] something. Why? If I have a vision in my [29:07] head and I can say it in natural [29:10] language, why shouldn't that also lead [29:12] to an end result? Um, I think it creates [29:15] great opportunities for everyone. And [29:18] just like, by the way, it's just like [29:20] WordPress, right? With WordPress, you [29:21] have people who build terrible sites and [29:23] people who build super polished, super [29:25] performance, super secure sites. And [29:27] that's all fine because it's the web. [29:29] And the web is a crazy thing. And you [29:30] can do things however you want. and you [29:32] have the right to publish your terrible [29:34] site and you have the right to publish [29:35] your amazing site. So, same here. People [29:37] are going to create uh vibecoded apps or [29:40] whatever and some of them are going to [29:42] be bad and some of them are going to be [29:44] great and that's going to be it's going [29:45] to be the same story. It's like can you [29:47] communicate your vision? Do you [29:48] understand product and user experience [29:50] enough to create amazing things with it? [29:52] Or are you just like an amateur who's [29:54] doing your own thing which is also fine [29:56] and great and legitimate and you do you [29:58] and it's all good. The one thing that [30:00] mostly concerns me about all of this is [30:02] security. I don't know if you saw this [30:03] major React um vulnerability that [30:06] happened last week. [30:07] >> Yeah. [30:07] >> So, you know, that's a major [30:10] vulnerability that's out of that was out [30:11] of the hands of pretty much everyone, [30:12] but like who knows what's being put out [30:15] there with that's connected to private [30:18] sensitive information. Like, that's [30:20] something that is going to need serious [30:21] attention. But that build your crappy [30:23] app, build your great thing. [30:25] >> Go for it. You know, [30:26] >> I'm putting that on a t-shirt. build [30:29] your crappy app and I'm go and I'm gonna [30:31] go to all the AI conferences with it. [30:34] There you Schwab. Build your crappy app. [30:36] Uh [30:37] uh no, I mean, yeah, it's it is I I I [30:42] I've been swinging back and forth on, [30:45] you know, the adoption of AI. Of course, [30:46] when it first came out, I was like, "Oh [30:48] god, no. I don't think this is going to [30:50] be it." [30:53] And then I started using it and I was [30:55] like, "Okay, this is starting to to go [30:57] pretty well." and and then like halfway [30:59] through that I was like, nah, this is [31:00] not it again. But now with Claude 45 [31:03] Opus, I'm like, man, this this is doing, [31:06] you know, some really killer stuff with [31:09] with at least WordPress plug-in [31:11] development. And, you know, I I think [31:13] it's it's going to get better. I think [31:14] the cost is going to rise substantially [31:17] um that we haven't realized yet for like [31:19] the real good stuff um in the future. [31:22] But um yeah, like I I think that that [31:26] lower end is is going to get dried up [31:28] and uh and um I think we'll all benefit [31:32] from it at the end of the day, at least [31:33] on the coding and development side. [31:35] >> I agree. And also, by the way, with [31:37] regards to cost, we we've been doing uh [31:39] WordPress meetups at our office, so like [31:41] we just started in 2025. And at the last [31:43] one, we talked about vibe coding, and [31:44] one guy talked about this very [31:46] comprehensive app that he vioded and how [31:49] it cost him $800. And we're like, "Oh my [31:51] gosh, $800." But then for if you think [31:54] about it, if he had hired a team, it [31:57] would have cost way more than $800. I [31:58] think we're going to have a long period [32:00] of time where even with the higher [32:02] costs, it's still going to allow us to [32:04] do incredible things that in the past [32:06] would have cost us multiples more. So [32:08] >> yeah, I think [32:09] >> yeah, I yeah, I think the next shoe to [32:11] drop, this is again is my crazy, [32:13] >> you can't leave one of my episodes [32:15] without getting a crazy uh tin foil hat [32:17] uh prediction is that the next price [32:20] jump will be just another zero on the [32:22] end of of these uh LLMs like Claude [32:26] Code. Uh so like Claude Code, it I think [32:29] when everything was like 20 bucks or [32:31] $20. Oh, okay. All right. Like where do [32:34] we spend this money? And then once [32:36] people started using it and they came [32:38] out with the $100 and $200 model, you're [32:40] like, "Oh, okay." Like I see where this [32:42] is going. Um, but now like if if if it [32:45] because basically what you're doing, [32:46] this is a little bit of a side tangent, [32:48] is you're trying to get this thing to [32:50] work. And the caveat is it's never [32:53] getting it right 100% of the time. It's [32:55] never giving you the the best way to do [32:57] it unless you keep iterating and [32:58] spending more tokens. And I think what [33:01] they're going to say is once these [33:02] things get even better, they're going to [33:04] say, "Okay, it's $2,000 a month, [33:07] >> but guess what? Your best engineer cost [33:09] you 10 times that. So, you know, why not [33:14] spend the $2,000 a month to get this [33:16] thing?" And that's when we're going to [33:18] start to see that separation of [33:22] >> bigger people with more money being able [33:24] to deploy a lot faster. And even if that [33:27] faster is literally only 30 days, [33:30] they'll get to market 30 days faster [33:33] than the competition because they're [33:34] able to to spend. [33:36] >> So anyway, that's [33:37] >> could be [33:38] >> that's what I think. [33:39] >> elementor.com. Lots of stuff now. We'll [33:42] wrap it up here, but one last question. [33:44] Go to elementor.com and you go into the [33:46] product section. There's a nice new drop [33:48] down with all the stuff that Elementor [33:50] does. Website building, Angie, site [33:52] planner. I used I did a video on site [33:53] planner. It is really awesome. Of [33:55] course, the hello theme. There's a [33:57] hosting column, hosting for WordPress, [33:58] hosting for Woo Commerce, and now a new [34:00] domains uh domains. On the run and grow [34:05] uh column, we have image optimizer, site [34:08] mailer, ally, web accessibility, and [34:11] send. [34:13] Going into 2026, your final question is [34:16] which of those many products are you [34:19] excited for uh when we roll into 2026, a [34:23] few short weeks away? [34:26] So that's a lot of products as you know [34:28] because you just read them all out and [34:30] the thinking behind them is that the web [34:32] creators journey doesn't like just start [34:34] and end with actually building the [34:36] website. First of all they want to build [34:37] the website in a high quality way. So [34:39] implementing accessibility at that stage [34:41] making sure sites as accessible as [34:43] possible is important. Optimizing for [34:47] performance is important. But then once [34:49] the site launches that's not the end [34:50] that's just the beginning. So, how can [34:52] you maintain that site in like uh an [34:55] ideal way and what tools can help you [34:56] along the way? So, that's the thing [34:58] behind those products. Personally, you [35:00] know, and they're all great, but I'm [35:01] just going to say which personally I'm [35:03] most excited about. So, I'm I'm really [35:05] excited about our AI products. Um I [35:08] think uh when we get them uh to where we [35:12] want them to be uh because let's say [35:14] Angie is still in beta um it will be g [35:19] they'll be game changers um for our [35:21] industry and I and I'm excited about [35:22] that also for WordPress. All you know [35:26] all the tools that are being built in [35:27] WordPress for AI are important. [35:28] Elementor powers 30% of WordPress sites. [35:32] So the faster we can get our kind of [35:35] market share to an AI place, I think [35:37] it's better for everyone in the [35:39] industry. Um, and hopefully we'll keep [35:41] WordPress strong and uh, you know, going [35:44] forward for the future. The other tool [35:46] that I really love of ours is Ally. Ally [35:50] does something really great with access [35:51] with accessibility and this is how I put [35:53] it. It makes accessibility accessible [35:55] which is ironic but if you use it you [35:59] get very clear understandable [36:02] um you know uh description of issues and [36:06] how to fix them also AI powered many of [36:08] those issues so that instead of just [36:11] getting a laundry list of these things [36:12] are all bad good luck to you you can go [36:14] through them which is like often the [36:16] situation [36:18] >> um so you can go through them and fix [36:20] fix fix and really bring your site to a [36:23] much more accessible place there. You [36:25] know, we're not saying it's 100% [36:27] accessible. I don't know if that's even [36:28] a thing, but it will definitely take [36:31] your site forward in a way and make it [36:33] um more accessible to an audience that [36:36] might currently be having trouble uh [36:39] accessing your site. So, so I think Ally [36:41] is really great and the you know the [36:43] team is uh releasing new updates pretty [36:45] regularly and they're really cool. So, [36:47] so I'm excited about that one. [36:49] >> Awesome stuff. Miriam Schwab from [36:50] Elementor, thanks for hanging out today. [36:53] Thanks for having me.