WordCamp US (WCUS) 2026 just wrapped up after 4 days at the Phoenix Convention Center in Phoenix, Arizona. Over 1,100 people from around the world registered to attend, and thousands more watched online through livestreams. Contributor Day and Showcase Day opened the week before two main conference days, featuring over 50 speaker-led sessions across 4 tracks, including multiple workshops.
The temperature reached 111°F (44°C), but ferried attendees between the Sheraton Phoenix Downtown and the convention center. Inside, attendees moved between session rooms, the Sponsor Hall, and the Happiness Bar.
It’s hot, but it’s not Florida hot.
– Loyal Pyczynski
Sessions covered artificial intelligence (AI), accessibility, publishing, business, site ownership, and the open web. Speakers in different rooms often found common ground, noting the importance of good judgment and trust-building in the age of AI.
Real Artists Ship
Contributor Day followed the motto “Real artists ship,” and a new format to match. The 425 participants, including 29 first-time contributors, formed 26 teams around goals they could complete that day. Experienced contributors moved between groups and helped newer participants shape goals. Then, goal owners gave 30-second pitches, and contributors could move between teams when that work caught their interest.
By day’s end, contributors had closed tickets, opened and shipped pull requests, and reviewed themes for accessibility. One team created description-list blocks for glossaries and product details, and another added email settings, a test tool, and checks for account, password-reset, and recovery messages.
Other teams built a Photo Directory importer and updated Notes in the WordPress dashboard and Multisite documentation. More work covered PHP, PHPUnit testing, and guidelines for AI work within the project. New contribution pathways became a course on Learn WordPress, open to people who could not be in Phoenix.
Every team ended the day with a 30-second presentation of what it had made, tested, fixed, or moved closer to release.
Showcase Day Put Real Sites First
If Contributor Day was about shipping in a day, Monday’s Showcase Day was about what happens after the shipping. Sites have to keep working smoothly for the people who publish, maintain, and depend on them. The case studies came from public services, independent publishers, community platforms, training systems, and large content operations.
Manny Costa covered the first of those: civic websites where residents find services, apply for programs, read emergency information, and report problems. In that work, accessibility, governance, and editor workflows are part of the service rather than a final check box.
Two of the case studies were about publishers taking back ownership of their content. Both sites now appear in the WordPress Showcase.
Nicola Catton’s session described how The Ankler moved 15 newsletters to WordPress and took direct control of its content, subscriber data, revenue rules, and reader experience. Nicola detailed the massive migration, the thousands of rebuilt paywall boundaries, and the site’s brand-new block theme.
The Daily Kos migration was a similarly large-scale move. Ben Greeley and Allison McHenry centered their session on a community that writes as well as reads: 1.5 million posts, 88 million comments, and 2.7 million users, with a public beta that involved more than 500 community members.
Other sessions dealt with the people who do the publishing once a site is live. In Aviral Mittal’s session, an AI agent built a page from a Google Doc using patterns the team had already defined. Andrew Adam described a library of about 100 written and video guides, with accessibility guidance included. Shared foundations covered repeat questions, while project-specific help and tips inside the editor handled the rest.
Human Judgment in the Loop
Early on, Bo English-Wiczling had opened Showcase Day by addressing the gap between rapid AI adoption and trust. Her keynote covered the move in developer work toward setting intent and supplying context.
AI doesn’t remove your work. It moves it.
– Bo English-Wiczling
A first draft can now arrive in seconds, but an almost-right block of code may still miss keyboard navigation, use the wrong theme styles, or bring an unsafe dependency into a project.
The importance of good judgment is familiar to the WordPress community. Bo tied it to habits WordPress contributors already have: reading other people’s code, submitting small changes, reviewing pull requests, and accepting critique in the open.
The next morning, Loyal Pyczynski drew on his work at Disney and Meta for a keynote about tests, time, and creative confidence. His talk returned to a phrase from an Imagineering colleague.
We need to make sure that we make better mistakes tomorrow. Success is an iterative endeavor, and time is our most precious resource.
– Loyal Pyczynski
Loyal described Disney teams that paired creative and technical leads early, then brought in experts for work another team could do better or faster. The goal was not to know everything but to know what the team should own.
Design and publishing sessions drew similar conclusions as the keynotes. Michelle Hunt framed design systems as living feedback systems that need to preserve intent as production gets faster.
K Adam White’s session centered on moving large stores of content into block patterns, with editors staying involved where automatic conversion still needed judgment. Nik McLaughlin’s Abilities API session looked beyond AI integrations to the broader structure the API gives WordPress developers. Brian Coords made a related case through block themes: approved patterns, templates, and real content offer a starting point, and design tokens add guidance that a blank-page prompt cannot provide.
Machine translation got the same treatment. In a multilingual WordPress multisite case study of AI translation for technical content, native-speaking colleagues found output that was correct word by word and could still miss the intended meaning. Human review covered the gap between translating language and translating intent.
The judgment question even reached hiring. The Making of a WordPress Certification introduced a standards-based certification and covered how the credential was created, checked, governed, and delivered.
Trust Becomes a Product Practice
Wednesday morning took the trust question outside the WordPress world. The day opened with a fireside chat between Amanda Ventura of Waymo and David Levine on what it takes for people to trust technology that moves through their streets.
Ventura described trust as repeated work. Teams can publish safety data and listen before arriving in a new city, and they need a path for product teams to act on feedback. Her example came from accessibility testing. Screen-reader support helped blind and low-vision riders use the Waymo app, but it did not solve the physical problem of finding the right car. Feedback led to step-by-step directions and a horn control with a distinct musical tone that was easier to identify on busy city streets.
Other sessions applied that standard to WordPress sites. WordPress Core committer Jonathan Desrosiers focused on supply-chain safety while Robert Abela’s session explored login security. AI tools can find security flaws faster than ever. That speed raises the need for careful checks.
The rest of Wednesday’s schedule included sessions on security, accessibility, design, AI tools, and work for site owners.
- Kathy Zant’s session proposed an audit for AI use, covering plugins, themes, content pipelines, and client sites, and it named consent, data location, disclosure, and legal review as questions teams should settle before launch.
- Another case-based session compared two responses to navigation problems: one client received an AI search tool, and another received a predictable interface that editors could control. The planned lesson was simple. AI can be the right choice without being the automatic choice.
- Joseph LoPreste’s session explored accessibility work no single plugin can complete: navigation, forms, headings, images, content, and interactive elements.
Learning With Your Laptop Open
WordPress beginner workshops ran throughout the event for first-time builders, with no hosting account or prior WordPress experience required. Participants made pages, posts, logos, and menus, and each person left with a WordPress site, a year of hosting, and a domain. These sessions laid groundwork to work with plugins, styles, and additional features. The beginner program, office hours, and Happiness Bar gave people several places to ask questions and get hands-on experience.
More advanced technical workshops offered even experts the chance to hone their skills.
- Łukasz Wilczak focused on reusable WP-CLI commands. They handled bulk content changes, block and shortcode migrations, link cleanup, and safe batch processing.
- Vedanshu Jain designed a workshop around roles and review paths for AI-only teams. The planned outputs included a plugin stub, publishable content, or another real result.
- Rob Ruiz built his workshop around WP Rig and automatic checks for preparing block-ready themes for the Theme Directory.
Like all WordCamps, these sessions gave attendees skills and tools to bring home to their own projects.
Simplicity Gets the Last Word
The closing session started with city business. Michael Hammett, Phoenix’s first Chief Innovation Officer, read a proclamation from Mayor Kate Gallego declaring August 19 Phoenix WordPress Day, and then presented the signed document to WordPress Cofounder, Matt Mullenweg. The proclamation credited WordPress with supporting the small businesses, developers, designers, educators, and creators in the city’s growing digital and creative economy.
What followed was a dynamic presentation and conversation between Mullenweg and Robert Jacobi, ending with a traditional Q&A. Matt’s thesis was simple: Tech needs to be simpler.
I want WordPress to be known for simplicity, not just complexity.
– Matt Mullenweg
After a detour through why AI models now prefer simple, self-contained HTML files, the argument became tangible with WordPress Piplets, a 2007 idea built around a single self-modifying PHP file that stores its own data, with no database and no third-party packages. One file can hold up to 25 megabytes, about four million words, and load in about 50 milliseconds. For Mullenweg, it extends the experiments that took WordPress from MySQL to SQLite to Playground, and he floated the idea of a WordPress.org directory where people could publish, fork, and remix.
Speaking of WordPress.org, it was announced that profile links are getting shorter, with w.org/username redirects like w.org/@matt already live, with full support just a few days away.
Midway through, release leads were called up to press the button on the WordPress 7.1 release, and were awarded with applause as “Mary Lou” received hundreds of thousands of downloads.
On contribution, Mullenweg expressed his desire to reward impact instead of pledges. The Five for the Future directory shows two million self-sponsored hours pledged each week from 150,000 contributors, and he questioned whether that reflects reality. The project already records what actually happened (commits, posts, tickets closed, WordCamps organized), and he wants recognition built on that record. He asked the same of the plugin directory, suggesting a focus on fewer better-working things.
Audience questions covered AI licensing, data centers, and why open source communities compete more than they collaborate. On that last one, Mullenweg invited other open source leaders to speak at WordCamp, and encouraged working together. Copying good code between projects, he said, is the entire point of open source.
Jacobi closed by asking who was at their first WordCamp; he had met more first-timers here, he said, than in the past ten years. One of them found the event by asking an AI chatbot for the coolest thing happening in Phoenix, came to Contributor Day, and left with one of its awards.
Beyond the Session Rooms
So much happens outside the session rooms. At the WCUS Happiness Bar, volunteers sat with attendees and worked through plugin questions, CSS problems, ecommerce setup, and new-site questions. An AFK (Away From Keyboard) room offered a quiet place away from the crowds. In the Sponsor Hall, people painted Wapuus with a local Phoenix artist, watched screen-printing, and talked between product demonstrations.
The Connect art installation used photographs from the WordPress Photo Directory. Forty postcards paired images by contributors who may never have met. Color, composition, or subject linked each pair. Attendees could take several cards and a blank one, then add a connection of their own.
Lunch did something simpler. People changed tables, picked up open seats, and started conversations with one question: “What do you do with WordPress?”
Organizers and volunteers kept four days of rooms, shuttles, meals, and livestreams moving. Thank you to them, and to the speakers, sponsors, contributors, attendees in Phoenix, and everyone watching online.
What Comes Next
If you missed this year’s WordCamp US, you can find recordings of sessions on us.WordCamp.org/2026/. Be sure to sign up for email notifications, so you don’t miss out next year. Next stop, State of the Word, followed by WordCamp Asia 2027 in Penang, Malaysia, and WordCamp Europe 2027 in Málaga, Spain.
Photo credits: Jaron Quach, Emily Chan, Wini Lao, Kendra Stowe, and
Jennifer Swisher
