Another successful WordPress Accessibility Day is in the books! This year’s 24hr event brought together 2,210 registered attendees from 77 countries to learn, share ideas, and help make the web more accessible for everyone.
I’m proud to have been a sponsor of this year’s event, supporting an important effort to advance accessibility across WordPress and the broader web. Accessibility isn’t a one-time effort or a box to check, it’s an ongoing commitment to making the web work for everyone, and events like this help move that work forward.
A huge thank you to the organizers, volunteers, and speakers who shared their time, expertise, and energy to make this year’s event possible. Special appreciation as well to my fellow sponsors and individual donors whose generosity helped keep the event free and accessible to a global audience. Check out the official 2026 event recap to learn more about the event and the people who made it possible.
Congratulations to everyone involved in another successful WordPress Accessibility Day! Here’s to carrying that momentum forward throughout the year and into 2027.
I recently had the chance to join the Crossword podcast for a conversation about open source, WordPress, and what meaningful contribution really looks like beyond writing code.
On this episode of Crossword.fm, we talked about how I got involved in the WordPress project, why non-technical contributors play such a critical role in open source, and what I’ve learned from spending nearly a decade working at the intersection of product, community, and engineering within the open web.
A few of the themes we explored include the value of organizers and facilitators in large open source projects, how text-first and asynchronous collaboration (meaning Slack-based meetings and regular meeting summaries and decision documenting via WordPress.org posts) helps WordPress scale globally, what sponsored contribution looks like inside agencies, and how to think about the future of WordPress in a way that brings people along rather than leaving them behind.
As with most good conversations, there were a few things I wanted to expand on but simply ran out of time during the recording.
One important example worth calling out is the continued leadership coming from Human Made, particularly through the work of John Blackbourn. During the episode we touched on agencies noticeably contributing to the project and I would be remiss without plugging John’s work. Their sustained investment in leading and supporting the WordPress Security Team is a strong example of what high-impact, long-term contribution looks like when a company aligns its expertise with a critical need in the project.
We also touched briefly on the question of how to get companies to agree to contribute to open source. In practice, the most realistic path forward usually starts with business alignment. What improvements to WordPress would directly support a company’s products, services, or clients? Advocating for and contributing toward those outcomes is often the clearest way to earn leadership buy-in. That contribution may not always be in core, and that’s completely fine. Sustainable participation tends to start where incentives overlap.
Finally, a quick clarification on a phrase used during the conversation. When Luke referenced “skating to where the puck is going to be,” that’s a sports reference that means anticipating demand rather than reacting to it. For folks like my dear friend Weston Ruter and others who do not live in the world of sportsball, that was what Luke meant.
If you’re interested in contributing to WordPress, supporting open source from inside an organization, or just want a grounded look at how large community-driven projects actually function, I think you’ll enjoy the conversation.
There is a moment every year when the lights dim, the livestream timer counts down, and the room settles into that familiar mix of quiet and anticipation. This year, State of the Word left me with a feeling I have not had in a long time. It felt like all the threads of AI work happening across WordPress finally came together.
If you have not watched the replay, it is worth it.
Before I dig into the part I had the privilege of contributing to, here is a quick sense of how the event landed for me.
The WordPress AI panel and the shift happening in real time
One of the highlights of my year was joining the AI panel hosted by Mary Hubbard, alongside Matt Mullenweg, Felix Arntz, and James LePage. Sitting on that panel, hearing how each of us approached AI from different angles, I realized we were not just discussing features. We were describing a shift in how people will build and maintain sites in the coming years.
This is where the “obvious and surprising things” came up. These were ideas I shared during the panel, because they reflect what I have seen across Fueled (and 10up) client work, ClassifAI development, and now the AI Experiments plugin.
The obvious things
These are the patterns everyone expected to see, and they are becoming mainstream faster than many predicted.
Chat-based search showing up as a natural extension of site discovery
Local and in-browser models that run privately, offline, and at very low cost
AI-driven brand visibility (aka “GEO” or Generative Engine Optimization)
Content distribution and translation workflows that used to require entire engineering teams now becoming almost trivial
These trends feel obvious only because the groundwork has been quietly laid for years.
The surprising things
The twist this year came from watching how people are starting to use the new Notes feature in WordPress 6.9.
I mentioned this on the panel because it caught me off guard when I saw it bubbling up within the community during the 6.9 release cycle. People are already experimenting with AI-driven content review inside Notes. Imagine WordPress calling out accessibility issues, shifts in tone, or sections where your writing reads differently than you intended. These are editorial tools that used to require specialized software. Now they are emerging directly inside WordPress.
That is when it hit me. The AI conversation in WordPress is no longer about novelty. It is about workflow, quality, and confidence.
A journey that started long before this State of the Word
For me, this work did not start with the AI Experiments plugin. It started in 2018 when the 10up team built the first version of ClassifAI for a client who needed content classification at scale. We open-sourced it in 2019 and kept evolving it as real publishers and agencies pushed its limits.
Those years shaped everything I know about AI inside WordPress. They taught me how AI fits into editorial workflows, when AI should require human review versus full automation, how permissions and provider selection affect trust, and how failure states must be designed with care. Those lessons are now embedded in the AI Experiments plugin.
ClassifAI will continue serving enterprise use cases with deep configurability. It will adopt the Abilities API, MCP adapter, and WP AI Client as those stabilize in the ecosystem.
The AI Experiments plugin takes a different path. It offers simple, approachable example AI experiments for non-technical users, while also serving as a reference for developers, agencies, and hosts who want to build AI powered features for their customers.
Each of these experiments helps us learn how people want to use AI inside their workflows, and which features could grow into stable tools inside core one day.
Looking ahead
This year’s State of the Word left me excited about something simple.
We are not racing toward AI.
We are shaping AI so it fits naturally into the way people already work in WordPress.
We are building an ecosystem where:
open tools remain the default (I’m specifically passionate about open source, local LLMs)
user choice stays central
and AI enhances creativity instead of replacing it
If you want to explore the AI Experiments plugin or get involved, you can follow everything in the open: https://github.com/WordPress/ai. And if you have ideas or want to push the boundaries of what is possible, I would love to hear them.
I’m thrilled to share how the Shipping WordPress Without Shipping Code talk went at WordCamp Canada 2025 (aka “WCEH”; get it WC, eh?). For folks who couldn’t attend, here’s a summary of what we covered, insights from the audience, and next steps you can try yourself.
If you’d rather watch than read, here’s the full WordCamp Canada 2025 talk:
In the talk I walked my own path, from helper to release deputy to AI team lead, all without ever having commit access. Along the way I shared how non-developer roles often get overlooked, practical patterns I’ve used to keep releases moving, and encouragement for designers, strategists, writers, or project leads who want to jump into this space. Here’s how the session unfolded, with some highlights and sample quotes.
Opening & Framing
I started by confronting the myth that only engineers lead in open source. My aim was to shift perspectives: YOU can lead, even if your strengths lie outside code.
The Historical Gap
We talked about how WordPress projects have historically lacked project and product management support, and how that gap creates friction. I quoted from the WordPress release handbook:
“The main focus of the release team is to lead the release from its beginning through to launch … to act as connectors and facilitators.”
It resonated: many in the audience nodded when I called out that non-developer contributions are often invisible or undervalued.
My Journey
I shared my own timeline: involvement in WordPress 4.7, then 4.8, 4.9, 5.8, 6.1, and 6.8. I also noted that WordPress 4.7 had 482 contributors, including 205 first-timers, to emphasize how major release cycles need more scaffolding than code alone in order to support that many new contributors.
What “Glue Work” Looks Like
This was a core section of my talk. We broke down how “glue work” such as triage, alignment, decision logging, and volunteer motivation is the connective tissue in a release. I used the quote:
“Triage is the practice of reviewing existing issues to be sure they are relevant and actionable.”
And I referenced how Apache PMC members and Kubernetes maintain non-coding roles, showing that this isn’t just WordPress-specific but a pattern in mature open source communities.
Tools, Patterns, & Gotchas
Here, the audience got actionable advice. Some highlights:
Use GitHub issues and projects with clear labels (needs-decision, punt, etc.)
Maintain decision logs so the same debates don’t repeat
Establish scope gates (feature freeze, RC readiness) to protect the release timeline (go/no go decisions)
Beware burnout and invisible labor
I referenced Karl Fogel’s Producing Open Source Software from my notes in a recent WordPress Book Club hosted by Aaron Jorbin roughly as ~“If it’s not written down, it didn’t happen.” And Nadia Eghbal’s note that “Maintainers simply don’t have the energy to onboard every person who shows passing interest.”
From Contributor to Leader
We laid out a three-step path:
Start small: take notes, triage, run a meeting agenda.
Own a lane: coordinate docs, dev notes, or release notes.
Lead a release: coordinate across teams, make decisions, facilitate.
I also referenced the Kubernetes “leads and shadows” model as something WordPress could use to mentor future contributors.
Practical Playbook
Seven habits you can take into your own contributor journey:
Write the agenda, end on time
Keep a decision log
Guard scope with labels
Close stale issues
Default to public and async
Give credit often
Leave breadcrumbs
I urged the audience to pick one habit and try it immediately.
Takeaways and Q&A
I wrapped up by reinforcing that leadership lives outside the repo and glue work makes shipping possible. I invited folks to pick a lane, join a triage session, or help curate the next release.
The question period surfaced great stories: people surprised they could participate in release work without code, and others asking how to balance contributions with full-time jobs.
What I Learned from the Room
Many talented people hesitate because they don’t see non-developers in core.
The “playbook” habits resonated; people wrote them down quickly.
There’s appetite for more structured mentorship paths for project contributors.
Some folks suggested pairing systems (non-developer lead and developer lead) to onboard new contributors.
Next Moves You Can Try
Join the next WordPress core triage or bug scrub session.
Volunteer to take notes for a devchat.
Pick one of the seven playbook habits and try it in your own project or team.
Consider how your current job or project might adopt glue roles, like coordinating features, managing scope, or writing decisions.
Final Thoughts & Thanks
Before wrapping up, I have to say how special it was to experience WordCamp Canada in Ottawa. The Carleton University campus was absolutely stunning, with crisp fall air, the leaves just starting to turn, and Richcraft Hall overlooking the canal and nearby lake creating an incredible setting.
Ottawa itself is a beautiful mix of history and energy, with old architecture and monuments along the Ottawa River that show how much care the city puts into preserving its character.
And of course, none of this would have been possible without the amazing organizers, volunteers, and sponsors who made WordCamp Canada feel every bit like the flagship event it is becoming. The warmth and generosity of the Canadian WordPress community really stood out, from hallway conversations to contributor day collaborations.
Running this talk in Canada felt meaningful. It’s part of a larger conversation: WordPress needs more voices who see beyond code, people who connect, facilitate, and help the system work. I can’t wait to see what happens when more contributors realize they are leaders already.
If you were in the session, thank you. If we met, thanks again. If not, I hope you’ll drop me a line, try one small piece of this playbook, and remember that leadership doesn’t always look like a commit; sometimes it’s the work no one sees, but everyone depends on.
A group presentation from the Core AI team on what we’re building. Progress since the team formation, next steps, implementation examples, and an open Q&A.
AI is becoming standard in content workflows—but too often, it comes at the cost of data privacy, long-term ownership, and open standards. What if WordPress could help you do AI differently?
In this workshop, we’ll go hands-on with ClassifAI and local LLMs to explore how AI features can be built ethically and scalably—from alt text generation to semantic classification to content summarization. You’ll learn how to configure ClassifAI with a local model via Ollama or any compatible runner, using the new AI Services plugin developed by the WordPress Core AI Team.
We’ll walk through real-world use cases and show how teams can reduce third-party dependencies while speeding up editorial flow—especially useful for enterprise content teams, agencies, and hosts. You’ll leave with a working configuration (or clear path to one), plus a roadmap of how these tools are evolving across the WordPress ecosystem.
Bring your laptop and a local or staging WordPress site if you’d like to follow along. Whether you’re building for one site or 10,000, this workshop will help you make AI work for you—not the other way around.
If you missed the workshop or had troubles following along (sorry!), then below are my slides as well as a reference to the prerequisite setup steps to be prepared for the workshop.
If you’re joining my Scalable, Ethical AI workshop at WordCamp US 2025, we’re going hands-on with building privacy-friendly, locally-powered AI workflows right inside WordPress. By the end of the workshop, you’ll leave knowing how to own both your content and your AI.
This guide will help you prepare your laptop ahead of time so you can spend less time troubleshooting and more time experimenting with tools like ClassifAI and Ollama. By doing this setup in advance, you’ll spend more time exploring the features and asking questions and less time downloading files during the workshop.
Step 1. Set Up Your Local WordPress Environment
The fastest way to get started is with tools like WordPress Studio, LocalWP, or DevKinsta that spin up a fully functional local site in minutes. If you’ve got something else you like/use, then by all means use that!
Download and install WordPress 6.8 (PHP 8.1 or newer recommended)
Create a new local site
Confirm you can log into your WordPress dashboard
Step 2. Install the ClassifAI Plugin
ClassifAI is the AI integration plugin we’ll use throughout the workshop.
Step 4. (Optional) Configure ClassifAI to Use Ollama
We’ll work through this during the workshop, but if you’re wanting to get ahead of things then feel free to set up these features. Once ClassifAI and Ollama are installed, we’ll connect each feature to a local model:
Feature
Model
Purpose
Content Generation
qwen2.5:3b-instruct-q4_0
Drafts high-quality content locally
Title Generation
phi3:mini
SEO-friendly, engaging post titles
Excerpt Generation
phi3:mini
Clean, concise summaries
Content Resizing
phi3:mini
Expand or condense paragraphs on demand
Key Takeaways
phi3:mini
Extract key insights automatically
Classification
all-minilm:l6-v2
Suggests categories and tags locally
Alt Text Generation
moondream:v2
Privacy-safe image descriptions
Step 5. Test Your Setup
To confirm everything is working:
ollama run phi3:mini "Hello from WCUS workshop setup"
The above should respond with a simple message from Ollama (via the phi3:mini model), though in my testing it will almost certainly NOT get the WCUS acronym correct ;).
If you did the optional ClassifAI configurations in Step 4, then test those are working as expected:
Create a new draft post in WordPress.
Use Title Generation or Content Generation from ClassifAI.
Verify that a response comes back successfully.
If something isn’t working, try restarting Ollama:
ollama run
Step 6. (Optional) Load Sample Content
If you’d like extra material to test during the workshop, you can download the sample content that I’ve assembled. I’ll provide USB drives with this sample posts, images, and taxonomy terms on the day of the workshop as well.
ClassifAI – Ollama Timeout: a small ClassifAI extension to increase the HTTP timeout for requests to Ollama on localhost
WordPress AI team: whether you’re an engineer, designer, researcher, or just curious about AI, we’d love to have you involved as we shape the future of AI in WordPress
See You at WCUS!
I can’t wait to connect with folks in-person at WordCamp US 2025 and dig into how we can own our content and our AI using WordPress, ClassifAI, and locally-powered workflows.
Whether you’re a developer, editor, or site owner, you’ll hopefully leave the workshop with a hands-on understanding of how to bring scalable, ethical AI into your publishing stack without handing your data over to external platforms.
The WordPress.org plugin directory requires that all plugins must be compatible with the GNU General Public License (“GPL”) and recommends GPLv2 or later as the same license as WordPress itself. This includes third-party libraries, code, and images. With today’s modern development practices and easier contributions on git-based systems like GitHub, you may not even notice a dependency being added to your project. I will show you how to utilize a GitHub Action to scan your current codebase and ensure that all future pull requests and commits similarly ensure that all third-party libraries (aka dependencies) are GPL-compatible so that you can rest safe that your plugin can properly maintain its GPL-compatible claim.
Feel free to reach out with any questions on the topic via comments on this post or contacting me directly.
This morning Finley, Gavin, and I went to Feed My Starving Children (FMSC) and volunteered by packing bags and boxes of their Manna Rice product that is specifically designed to assist in reversing and preventing undernutrition worldwide.
Earlier today I sat in on a webcast that Joi Ito from MIT Media Lab hosted with David and Tom Kelley from IDEO where they discussed how to foster a culture of innovation and maximize the creative potential of said innovative organization. Then this evening I attended an intimate discussion hosted by the Hollywood Chamber of Commerce at WeWork between Kevin Winston of Digital LA and Eric Garland of Live Nation Labs. I’ve excerpted some of both discussions below, but more interestingly I’d like to analyze some commonalities. The brothers Kelley came at the discussion from an agency, teaching, and author/public speaker background while Eric had an entrepreneur turned corporate research & development background, but both ended up hitting on some similar topics. Namely: hiring the best people, fostering their communication, and then getting the hell out of the way.
A common thread has emerged lately in articles I’ve read, videos I’ve watched, and events I’ve attended where managers response to the general question of “what was most important to your success?” is almost always along the lines of “I had a great team”. Clearly some people long for a shortcut to success, but the common answer tends to be “hire great people”, “set your team up for success”, “rinse & repeat”. So then how do you go about hiring great people and setting them up for success? The Kelley brothers seemed to say that having a diverse background was valuable for their team members (I seem to recall one of the brothers noting an opera singer on staff) and that diverse employee base allowed for a wide-ranging set of experiences from which to draw upon during creative sessions. That approach may work well for an agency in that they often work on varying projects and clients and need to have a different approach on a regular basis. However, I wonder how that applies to someone like an entrepreneur or someone locked into a specific marketplace (e.g., Eric Garland’s focus on the music industry and advancing Live Nation’s business via his Labs team). Can those teams afford the luxury of a diverse employee base or must they stick to the “engineers and designers with pre-existing experience in the music industry” bit that seems to permeate job postings? The answer, in reality, seems to be against a diverse employee base (see Live Nation Labs job postings for an answer to that). But this is a small sample size, so if you’re aware of teams who hire specifically for diverse candidates I’d love to hear about them to compare their success and failures against organizations who hire for job-specific talents with marketplace experience. My second question of “how to set up your team for success” was hit on by Eric during his discussion; he seemed to say that allowing the team to work when, where and on what they wanted while keeping them physically and mentally separated from upper management was a key to success. Any additional thoughts you have on this topic would be warmly welcomed in the comments section below; let’s chat!