Matt’s session was kicked off with Michael Hammett, Chief Innovation Officer of the City of Phoenix, who announced that August 19th has been proclaimed Phoenix WordPress Day by Phoenix Mayor, Kate Gallego.
Then we got into the meat of Matt’s keynote. He was joined on stage by Robert Jacobi. Together, they had a conversation about some “Thoughts & Ideas” Matt has for the project – w.org profile names, Piplets, and rewarding impact for contributions to WordPress.
WordPress 7.1 was released during this session with a big red button.



Recordings will show you the sessions. They won’t show you what the hallways, the sponsor floor, and the community booth felt like on the ground, so here’s the part you had to be there for.
Merchant Corner. Tucked into the venue this year was a lineup of Phoenix-area businesses, all running on WordPress, all proof that the platform shows up far outside the tech world. If you didn’t get a chance to stop by their tables, their sites are worth a visit:
Salsa Morita Rica | OMG PetArt | SMILE Biscotti | Cultivate Coffee | The Merchantile | Bookmans Entertainment Exchange | The Toasted Mallow | The Poisoned Pen Bookstore | Dr. Ginger’s | Desert Towel | Sonoran Sanctuary Candle Studio | Craft Nights | Cheri’s Desert Harvest | Arizona Art Supply | Stoneman Climbing Co
The Wapuu Scavenger Hunt. All week, attendees have been on the hunt for Wapuus hidden out in the wild, meaning somewhere in the convention center. We hid 48 Wapuus for Arizona, being the 48th state.
LEGO WP Logo Build. Piece by piece, attendees at the community booth built the WordPress logo out of LEGO over the course of the week — the kind of thing that only works because a conference full of builders can’t resist finishing something once they see it started.






The week wrapped up with a closing party at On Jackson. Attendees enjoyed food, drinks, games, and live music. We spent the evening catching up on all we learned and experienced this week.
None of this week happens without the sponsors who made it possible, from the hosting discounts on the ticket itself, annual hosting for every WP 101 attendee who went home with a live site, to the ever-popular sponsor hall, the coffee, the golf carts, and too much more to name.
We are so grateful for the partnership!
Thank you to everyone who showed up this year: attendees, speakers, volunteers, sponsors, and everyone who’s been part of WordPress long before this week and will be long after it. See you at WordCamp US 2027.
]]>Day 3 opened with a keynote from Loyal Pyczynski, a former executive at Walt Disney Imagineering and Meta. The session framed creativity and technology as a division of labor rather than competitors: focus on what you do best, source the rest, and protect the resource that actually matters: time. The central reframe was to make better, not fewer, mistakes tomorrow. Make the kind of mistakes that come from trying with intention instead of playing it safe. The talk turned personal from there, naming the vulnerability of creative work and imposter syndrome without hedging, which drew visible recognition from the room. The practical takeaway was to take inventory of what you are trying to do and what you are good at, resist the urge to let one piece of feedback blot out everything else, and build confidence by starting rather than waiting for the fear to pass.
Elsewhere in the convention center, the sponsor hall was lively on its first day open. Sponsors were busy talking with customers and potential customers and handing out swag. This year, some of the most popular swag items were activity-based: coloring postcards, watching a screen print demo, and taking photos in a photo booth.
The biggest story in this room, though, was the conversations between attendees. Overheard conversations spark new ones, new connections are made, and we all leave a little richer for it. This event went from being purely informational to being the biggest, nerdiest family reunion in short order by leaving room for others to join the conversation.

WordCamp US partnered with local Phoenix artist, Dina Murphy, and her business, The Painters Lounge (her site is on WordPress). Attendees could join a class to learn how to paint their own Wapuu. She’ll be back tomorrow to to lead a few more classes.
The Happiness Bar, a free, drop-in help desk, returned this year. Attendees could sit down with a volunteer WordPress expert and work through whatever’s been blocking them, from plugin questions to CSS issues, to ecommerce setup, and even “I don’t know where to start.” It’s consistently one of the most-cited reasons people say WCUS is worth attending.


Career Corner sat inside the Sponsor Hall as a low-pressure space for anyone thinking about what came next. Attendees browsed the job board, talked with company reps during open hours, or simply got a sense of what companies were actually hiring for, with no appointments and no formal pitch required. Alongside the conversations, the space offered practical help: resume tips, interview framing, and a read on what the ecosystem needed right now.
The Mercantile opened on site today, with attendees browsing store favorites alongside exclusive WordCamp US merchandise. This year’s limited-edition collection drew inspiration from a traveler’s journey down Route 66, blending Americana with the spirit of Phoenix.


Code for the People, a documentary created by Bao Nguyen in collaboration with Automattic, has a screening room in the sponsor hall. The film invites attendees to learn about open source and get involved with the WordPress open source project.

This year’s installation, Connect, was built entirely from photographs contributed to the WordPress.org Photo Directory, pairing images from photographers around the world who had likely never met into a single collaborative work. Attendees first saw the photos as a minimal gallery labeled only with contributor names, giving them a chance to spot their own connections before the curated pairings were revealed across 40 postcards, each linking two photos through color, composition, or subject. Everyone left with five or six postcards plus one blank card, an invitation to make a connection of their own or contribute a photo to the Directory.
A huge thanks to our contributing photographers:
Allan123456789 | Alina Kakshapati | Angielina Haurylkova | appealdahal | Arata Takami | Arief Burhanuddin | Bigul Malayi | Christopher Kurth | Deepak Vijayan | genepine | Iyundhu Kennedy | Jackson Monichan | Jennifer Bourn | Krupa Nanda | LeifQ | Midhun P | Mohammed Arif | Mohammed Kateregga | Mohammad Shoeb Ansari | Nikul Valani | Nilo Velez | Nusrat | Pitam Bahadur Sen | PRABIN M | Rashed Hossain | Roberto Vazquez | Roman Khadka | Sakin Shrestha | Shaddam Hossain | Shirish Poudel | systxema | Vishnu Chandra
On day 3, attendees started branching out from the groups they’d stuck to for the last couple of days. Lunchtime seemed to make it happen. Instead of sitting alone, people picked up an empty seat, chatted about what’s been going on over the last few days, and asked the age-old question, “What do you do with WordPress?” Conversation flowed, new friends were made, and we discovered that we have far more in common than we previously thought.
The day’s sessions kept circling two related problems. The first was what changes when AI agents start acting on sites directly instead of just reading them, and what gets lost when building becomes effortless. The second was how anyone in the ecosystem proves they are trustworthy, whether that means a host, a plugin, or a developer.
AI moved from novelty to infrastructure, with machine agents becoming active participants rather than passive visitors, submitting carts, initiating payments, reshaping discovery, and rearchitecting the platform itself. But production became almost too easy, so design systems drifted to intent rather than appearance, and machine translation produced output that was technically correct and completely wrong. The answer, repeatedly, was to keep human oversight deliberately in the loop.
The second thread was trust, and who gets to claim it. The tools surfacing vulnerabilities faster were equally available to attackers, making supply-chain discipline and plugin audits non-negotiable, while a hosting trust seal and a new developer certification framed trust as something that could be earned and proven. Running alongside was a quieter question of professional identity, from the person who became their company’s sole WordPress owner by default to the agencies that stopped selling WordPress expertise and started selling outcomes.
Today’s sessions are available to view on WordPress’ YouTube channel.
This year, that question showed up everywhere, including in a keynote about the taste it takes to work well with AI, in a handful of themes that kept resurfacing across completely unplanned sessions, and in a room full of first-time builders who left with a live site before lunch. Here’s how the day unfolded.
For starters, it was 111°F outside but between the cheap thrill of the golf cart ride from the hotel to the convention center and the blast of AC waiting at the other end, nobody seemed to mind. This sounds unhinged but honestly being indoors for most of the day, the breaks outside in the heat felt really good.
A big theme across the day was AI and community. Understanding AI has always felt like a solo process with just you, a browser tab, and a lot of trial and error. Not today. Showcase Day’s hallways were full of people stopping each other mid-walk to compare notes, work through a stuck problem out loud, or just admit they were figuring it out too. The community showed up for each other as much as it showed up for the sessions.
Bo English-Wiczling opened Showcase Day with a puzzle: AI adoption has climbed past 84%, yet developer trust in the output keeps falling. She argued this isn’t a tooling problem; it’s a taste problem. AI doesn’t eliminate developer work; it relocates it. The time saved typing reappears in specifying intent, assembling context, supervising agents, and owning whatever ships.
Real WordPress examples made it concrete: the “almost right” bug that survives every glance-test, the security debt hiding in AI-suggested dependencies. Her model was specify, delegate, verify. The developers who thrive won’t be the best prompters; they’ll be the ones with the sharpest taste.
Constraints are the feature. Showcase Day’s biggest theme was AI shifting from demo to discipline. The sessions worth attending weren’t about what models can do; they were about how to work with something fast, useful, and occasionally confidently wrong. Project contracts, required plans, verification loops, structured scaffolding. The recurring point was that constraints aren’t a limit on AI; they make it usable at all.
Build it for editors, get agents for free. This one showed up in multiple rooms, apparently unplanned. The clear blocks, sensible defaults, and guardrails that make an editor’s life easier are exactly what an agent needs to publish well. Good structure serves humans and machines equally.
Own your stack. Ownership was the day’s quiet argument. Publishers leaving rented platforms, companies consolidating their tools behind one login, developers picking their own build environment over legacy defaults. Different talks, same instinct: control over your content, data, and stack is worth the migration pain. And the migration stories all landed the same way. The numbers were enormous, but the hard parts were community trust and editorial habits, not databases.
It’s the interface, not the platform. Teams leave WordPress for other tools and spend months rebuilding capabilities it already has, just hidden behind an admin experience built for developers.
The work starts after launch. The rest of the day pushed past the obvious. Security has moved beyond the perimeter, since firewalls and 2FA are table stakes and the real gaps are in what happens after authentication succeeds. Reach was framed as underserved demand rather than a values checkbox, whether that meant bilingual audiences, accessibility, or civic services. And stewardship kept beating launches: training systems instead of training sessions, automated checks instead of manual review, maintenance workflows instead of one-time scripts.
The beginner track’s build-your-own-site session did exactly what it promised. Attendees showed up with a laptop and a browser, and left with a real WordPress site: pages, a post, a logo, a menu, all live in the room. No hosting account, no prior experience, no setup homework. The room was full of first-time builders, students, designers, and marketers who had never touched WordPress before, which was the whole point.
Along the way, the session slipped in the habits that are hard to retrofit later, covering the basic building blocks alongside beginner-friendly accessibility and SEO practices. Everyone walked out with a copy of their site, plus a free year of hosting and a domain, and headed for Go-Live Office Hours to make it official. The real deliverable was less the site than the confidence to keep building on it.
Missed a session? Want to rewatch? You can view all of today’s recordings here.
An idea is worth almost nothing until someone decides to finish it. Sketches don’t ship, good intentions don’t ship, the plugin you’ve been meaning to build, the doc page you’ve been meaning to fix, the translation you’ve been meaning to submit…none of it counts until the ideas in your mind actualize.
Come build WordPress is the quiet dare buried inside Contributor Day. You sit at a table with strangers who share your six hours and nothing else, and by the time the lights come up on demos, you have something to show for it.
That kind of vulnerability matters. A finished thing can be judged in a way an idea never can. It’s easier to keep something in draft forever, safe from critique, than to open a pull request and let it exist in the world. Today, hundreds of people chose the harder, better option anyway. They shipped.
WordPress itself is proof this works. Nobody was born knowing how to write a patch for Core, translate a string into Xhosa, or fix a broken heading in the Docs. The WordPress community has been dedicated to continuously evolving and did something about it over and over for twenty-plus years, until 40% of the web stood on the sum of everyone’s small, finished contributions. Today, we added a few more.
We started the day by taking stock of who was in the room, then brainstormed the goals we wanted to accomplish. Our experienced contributors moved around the room, helping newer contributors shape their goals into something more realistic to accomplish in a single day.
Once everyone had goals, we gave every goal owner thirty seconds to pitch their goal to the room. Then we spent the rest of the day building, with each goal team gathering around a table. We didn’t require anyone to stay with the same team all day, and we encouraged contributors to move around if something caught their interest.
At the end of the day, each team gave a demo. Each team had thirty seconds to share their project and where it ended up by the end of the day.
The test runner and reporter only supported one environment, so hosts with multiple PHP, MySQL/MariaDB, or web server combinations couldn’t report results per environment. The team tested and merged a PR from a Cloudfest hackathon two years ago, then updated the reporter to accept multi-environment results.
AI tools are now part of how people build with WordPress, but we didn’t know if users could evaluate and use them well. This project measured AI literacy through a short Quick-Check that produced an individual profile and an anonymous community dashboard. The team shipped the assessment, scoring logic, and a dashboard prototype.
Education built contribution tracks for software development, design, translation, communications, community and event management, and more. The team opened these to all new contributors, not just students, and published the day’s work as a course on Learn.WordPress.org for anyone worldwide.
Static analysis had flagged thousands of spots where the code hinted at deeper design problems. Contributors picked baseline files, fixed issues, and shipped PRs, which made great first contributions.
This team created a plugin that lets you import any photo from the photo directory straight into your media library. They wrote code, tested it, and created documentation.
Theme developers who requested accessibility testing got feedback to help improve their products and accessibility in WordPress. Participants also learned to set up a WP install, import themes, and contribute to a Trac ticket, plus plenty of hands-on accessibility practice.
A PR added a Notes section to the admin dashboard’s Activity widget, listing posts with the most recent unresolved note threads from the block editor, each row showing the post title, its open note count, and the date of the newest note or reply. It’s open against trunk for Trac ticket 65890, with test coverage and query optimizations added during review.
Committed gzip compression opt-in for the core dev environment. Benchmarking showed disabling concatenation in favor of prefetch improved Dashboard load from the Login screen by 72%, and a PR to implement prefetch is now open.
Added support to the WordPress admin for AI assistants running in the user’s browser, using tools WordPress already had and work others had already done. This lets an AI take actions on a site directly from the browser instead of through a server.
WordPress email delivery was unreliable. The team added built-in SMTP settings, a test email tool, and a helper that confirms account, reset, and recovery emails actually arrive.
Improved documentation for WordPress Multisite by asking users how they use the feature in their daily life.
Fixed or removed useless PHPUnit tests, upgraded PHPUnit, and saved PHPUnit timing artifacts to find and fix slow tests.
Client Side Media ships this week, so the team identified edge cases that needed fixing.
Helped WordPress users prepare for AI search with an evidence-based guide separating proven SEO from unsupported AEO and GEO claims.
Description lists give editors the right markup for glossaries and key-value metadata like product specs. Adding them as a block lets editors build those directly in post content.
Healthcare providers face a critical challenge: delivering accessible websites while maintaining HIPAA compliance. The team built a WordPress solution with a comprehensive, patient-centric platform.
AI Client now supports vectorization, which let the team bring Smart Search to the canonical AI Plugin.
The revisions system needed to be extensible so Core or third parties could build on it, for things like future revisions or public versions. The pitch was to add slotfills to the revisions sidebar so others can add their own UI elements.
Figured out how to conditionally autoload WP-CLI via Composer so installing it as a dev dependency in a project doesn’t interfere with it running in wp-env.
A two-person team worked with an ASU student to build a website.
Created a formalized draft version of the WordPress AI guidelines. An initial version existed at make.wordpress.org, but it needed review before a community-feedback version could be created.
Plugin installation now requires loading as a canonical plugin, with the deprecated Composer path noted in the docs. The team also cleaned up and polished the docs ahead of the .org release.
Tested the bleeding-edge release using the new contributor tool.
Used WP Bench to test against skills and evaluate their scores. This led to refinement and iteration of both skills and WP Bench, making AI agents better at using WordPress.
Developed an interactive Block Map iPad demo for the Core AI WCUS website. This tool guides WordCamp attendees through the AI Building Blocks in Core AI, clarifying their purpose, function, and placement.
The team worked through the challenges of being a new contributor, specifically the jargon barrier to getting started.
Let agents patch one sentence in a post without reading the whole field back. Revised the surgical edit-content ability.
No Contributor Day ends without a little recognition, including the biggest wins, the quirkiest wins, and the wins nobody saw coming. These aren’t the awards you’d find on a résumé. They’re the ones you only earn by actually being in the room, elbow-deep in a goal, for the last six hours.
Today, a room full of attendees proved that WordPress really can go from idea to live site in half a day. WP 101 kept things hands-on all morning to learn a concept, apply it immediately, keep building and by the end, attendees weren’t just watching WordPress work, they’d built real sites around their own ideas: blogs, portfolios, business sites, whatever brought them into the room. No account, no code, and no prior experience required, just a laptop and a willingness to try. WP 101 runs again tomorrow, and WP 202 picks up where today left off later this week.
If this is what a room full of people can ship in a single day, we can’t wait to see what Day 2 brings.
See you tomorrow.
Contributor Day is the part of WordCamp where the software gets built. A full day set aside for writing code, fixing bugs, improving documentation, translating WordPress into more languages, designing, testing, and supporting the people who use it. Everything in WordPress was made by someone who decided to contribute. Today we invite everyone to be that someone. There’s no development experience required, and no need to have contributed before.
Contributor Day has traditionally been organized by team. You’d find the Core table, the Documentation table, the Polyglots table, and join the one matching your skills.
This year, we’re organizing around goals, specific things we want to finish before the day is out. Each has an owner who proposed it, the skills it needs, and a short pitch for why it matters:
Contributors will choose a goal rather than a team. Someone who writes documentation might spend the day working alongside a designer and two developers, because that’s what the work requires. The question shifts from “Which team am I on?” to “What are we building?”
Come with an idea or come without one. Much of today’s best work will come from people who joined someone else’s goal because the pitch was compelling. If you do have something in mind, propose it here. Proposals are open until pitches begin.
“Real artists ship.” That’s the phrase we kept coming back to while planning this. The measure of a good Contributor Day isn’t how much we discussed. It’s what exists at the end that didn’t exist at the start.
Thank you to everyone contributing today, and to everyone who has before.
WordPress works because contributors show up.
WordPress Executive Director, Mary Hubbard
Wednesday, August 19, 2026 at 9:30am
Amanda Ventura is joining WCUS 2026 for a fireside chat, sitting down with David Levine to talk about what it takes to build public trust in AI that shows up in the physical world.
Amanda works on the public affairs team at Waymo, the autonomous driving technology company on a mission to be the world’s most trusted driver. Her team sits at the intersection of AI and community, working directly with road safety and accessibility advocates to build a future of safer, more inclusive journey powered by autonomous driving.
That’s a genuinely different kind of “user research” than most of us are used to. It’s not A/B testing a checkout flow. It’s earning trust from the people whose streets, safety, and daily lives are directly affected by what you build and doing it in public, with real stakes, before that trust is given.
Hosting this conversation is David Levine, an award-winning nonprofit founder and a member of the WordPress Core AI Team who bring AI functionality to nearly half the web. He’s spent more than a decade working with not-for-profits, NGOs, and local government. Today, as Director of Growth Engineering at rtCamp, he uses WordPress to solve complex problems for enterprise clients, but the throughline hasn’t changed: build things people can actually rely on.
Both Amanda and David have spent their careers earning trust in public, at very different scales which makes for exactly the kind of fireside chat worth clearing your calendar for.
Most of us building on WordPress are used to thinking about trust in fairly familiar terms: uptime, security, accessibility, whether the thing we shipped actually works the way we promised. This fireside chat takes that same question and moves it from the digital world to the physical one, specifically on the road.
Open source has always been a conversation about trust: trusting contributors, trusting maintainers, trusting a platform to keep running the way it’s supposed to for the 40%+ of the web that depends on it. Autonomous driving is that same conversation, just with far higher stakes and a much more skeptical public to convince. However this fireside chat unfolds, expect it to surface something worth sitting with regardless of what you build: how do you earn trust from people who didn’t ask for the technology in the first place, and how do you keep it once you have it?
Wednesday, August 19, 2026 at 9:30am
Check out the full schedule and speakers page for the latest, and grab your ticket if you haven’t yet.
See you in Phoenix.
Skip the registration line at the convention center and pick up your conference badge early! If you’re staying at the Sheraton Hotel, we’ll offer a satellite registration desk in the Sheraton lobby on Sunday, August 16, from 7:00 a.m. to 12:00 p.m.
Need help getting around? Check out our venue maps. We’ll be utilizing three levels at the Phoenix Convention Center. Use our venue maps to find which rooms are where. Venue map room numbers correspond to the room numbers on the schedule.
Check out this post for other local information.
Golf Cart Shuttles will be on a continuous loop outside of the Sheraton Phoenix Downtown and Phoenix Convention Center. You can meet the golf carts outside the Sheraton Hotel lobby and in front of the Phoenix Convention Center Guest Entrance on Third Street from 8:00 AM to 5:30 PM each day of WCUS.
Back this year at WordCamp US is the WordPress Mercantile shop. On August 18 and 19 from 9:00 a.m. to 5:00 p.m., you’ll be able to stop by our Mercantile Pop-up in the Sponsor Hall and check out drinkware, patches, stationery, accessories, and more. Grab something to commemorate your first WordCamp US or add to your growing collection of WordPress merch. Treat yourself! All shoppers will receive a 20% discount for a future online order.
We have four days of activities and content waiting for you. Here’s a day-by-day breakdown:
Be sure to check out the full schedule for details.
This all-day hackathon and networking event brings new and existing contributors together to work on various WordPress-specific projects. For folks new to contributing, it is a great opportunity to meet with different teams, observe, and potentially start contributing.
Learn more about Contributor Day.
Showcase Day is where we learn about all the amazing things people are doing with WordPress. In the past, we’ve seen live demos, case studies, and presentations on actionable strategy for your own site.
Our last two days of the conference will be sessions. You can pick and choose your sessions as you see fit, or you can choose one of our four paths:
Wrap up WordCamp US 2026 in style! Join us for the Closing Party on Wednesday, August 19, 7 to 10 PM at On Jackson (245 E Jackson St, Phoenix, AZ 85004). On Jackson is about a 5-minute walk from the Convention Center. The Closing Party is the perfect way to celebrate an incredible week!
Your WordCamp US 2026 badge gets you into the Closing Party (and two free drink tickets!), so don’t leave home without it!
Following along from home? There’s a couple of ways to keep up with what’s going on:
Follow along on our social media accounts to catch the highlights each day:
The event hashtag is #WCUS on all platforms.
This year, we will be recording all sessions, and they will be available on each sessions’ page on the website, or you can view all session recordings in this playlist.
All keynotes will be livestreamed on YouTube. You can access these via the WordCamp US 2026 website, or from the WordPress YouTube channel’s streams page.
It’s not too late to join us. Get your ticket for four days of learning and community celebration
]]>While you’re exploring, be sure to catch a ride on the WordCamp US golf carts to the convention center, stop by the photo booth to snap a photo with your team, and grab a cup of coffee at the JavaScript Diner. And if you need help finding your way, keep an eye out for wayfinders and mirror clings throughout the venue.
For more information about some of our sponsors, please read the descriptions below and check out the Sponsor Hall map. We can’t wait to see everyone next week!
Pressable is the managed WordPress hosting platform built to keep agencies, ecommerce stores, and growing businesses secure, fast, and ready. Backed by Automattic, our human WordPress experts are minutes away and treat every problem like their own. We’re not just keeping up with what’s next. With AI-powered tools, we’re building it. Some hosts support WordPress. We are obsessed with it.
Visit the friendly humans at the Pressable booth to see how to control your WordPress hosting with AI. We’ll show you how agencies, developers, and growing businesses are using Pressable MCP to turn afternoons of manual work into done. In just minutes. Have a hosting headache you want us to solve? Stop by to book dedicated time with our experts.
WordPress.com is building the future of WordPress.
WordPress.com is a fully managed WordPress hosting platform built for performance, reliability, and scale. Upload plugins and third-party themes on all paid plans and get unlimited bandwidth and traffic, too. WordPress.com hosting is designed to handle sites of any size, with built-in security, automatic real-time backups, and 99.999% uptime, helping protect millions of websites around the world.
At WordCamp US, we’ll share how WordPress.com is evolving for the next era of site building.
Visit our booth to explore WordPress Studio, our agentic development environment, and WordPress Agent, a native AI experience built directly into WordPress.com’s editor that helps you create, edit, and manage sites using natural language.
Together, these demos show how we’re bringing more agentic workflows into WordPress while staying true to what makes WordPress powerful: flexibility, openness, and extensibility.
Whether you’re a developer, agency, designer, or creator, stop by to see the demos, meet the team, share feedback, and pick up some swag. We’d love to hear how you build today and where we can help make building with WordPress even better for you.
WordPress essentials, intelligently connected.
Jetpack brings practical tools for security, performance, growth, and content creation together in one trusted suite. Protect your site, understand and grow your audience, improve performance, and create better content—with the flexibility to use only what you need.
Across Jetpack, we’re making the experience simpler, faster, and smarter. That means clearer ways to find and use the right tools, continued performance optimization, and thoughtful AI and modern workflows that help you accomplish more with less effort.
When essential tools work together, you can rely less on a patchwork of disconnected plugins. That can mean fewer overlapping subscriptions, less compatibility and maintenance work, reduced dashboard confusion, and more value from the tools powering your site.
At WordCamp US, stop by to meet the people building what’s next for Jetpack, tell us what would make managing WordPress easier, and pick up a tote featuring original artwork by Phoenix-based designer and illustrator Sage Aune.
WooCommerce is the open-source ecommerce platform that powers 4 million stores globally, built for merchants who want to grow without platform lock-in, revenue share, or growth taxes. We help brands build flexible commerce experiences around any business model, with full ownership of their data, customer relationships, and technology stack.
We partner closely with developers and agencies worldwide to support custom builds, high-growth merchants, and projects that don’t fit inside rigid SaaS constraints.
This year at WordCamp US, visit the Bluehost booth to discover the Bluehost AI Suite: a powerful collection of AI-driven tools designed to help you spend less time on repetitive tasks and more time creating, building, and growing your business.
Whether you’re launching a new site, supporting clients, or scaling an online business, the Bluehost AI Suite helps you:
Our team will showcase live demos throughout the event and be available to answer your questions, share best practices, and help you explore how AI can fit into your workflow.
Whether you’re a developer, agency, freelancer, or business owner, we’d love to show you what’s possible. Visit the Yoast & Bluehost booth at WordCamp US 2026.
We look forward to meeting you in Phoenix.
Automattic for Agencies is the partner program that connects your agency to Automattic’s full product stack through a single relationship. And that stack just became agent-operable. WordPress.com, Pressable, WooCommerce, VIP, and Jetpack each shipped MCP, the open standard that agents like Claude, ChatGPT, and Gemini use to take real action on live sites. Apart, they look like five product updates. Together, a single agent can run a full client workflow across the entire stack. Automattic for Agencies is the one program, one relationship, one protocol end to end that makes that practical, and the agencies who build on it first get a head start.
One open protocol runs identically across all five products, from a personal WordPress.com site to a FedRAMP-ready VIP install, owned by no single vendor. Other platforms have shipped AI, but none can match that.
For your agency, that means no model lock-in and no five integrations to maintain. One agent can provision on Pressable, import a catalog into WooCommerce, scaffold and draft on WordPress.com, then tail server logs through week one, on your auth and approval gates. Agents propose, you ship.
Stop by the booth to see it live, sign up, and book time with our team.
We’re excited to be at WordCamp US 2026.
Search is changing, and so is the way people discover brands. At the Yoast & Bluehost booth, we’ll show you how Yoast helps you stay visible across traditional search and AI answers, with tools that support SEO, structured data, and brand visibility in AI platforms.
If you stop by, you’ll see how Yoast helps marketers, content teams, and online stores build stronger foundations for discovery. You’ll also get a look at Yoast SEO AI+, including AI Brand Insights, which shows how your brand appears in AI-generated answers and what you can do to improve it.
We’d love to chat about your site, your content, and where search is heading next.
Come say hello and see what’s new.
At Elementor, we’ve been working on a few things for a while that are coming together and represent a meaningful shift in what’s possible for web creators.
The first is the Atomic Editor, Elementor’s Editor version 4. The core idea is architectural: instead of building sites from isolated elements, you’re working with structured, predictable building blocks that function as a system.
Design system tools like Classes and Variables let you define styles once and apply them across an entire site. Components are reusable sections that update everywhere simultaneously, with built-in controls over what clients or collaborators can touch.
For anyone managing multiple projects, this can dramatically change how long your work takes. Work that used to span hours or days can now be done in a few clicks. And it doesn’t require abandoning existing workflows. Version 3 widgets and Atomic Elements coexist on the same site, so creators can adopt the new foundation gradually.
The second is Angie Code, Elementor’s agentic AI for WordPress. Angie Code does more than generate assets; it generates working, production-ready WordPress assets. Widgets, front-end snippets, admin customizations, and interactive features.
Things that once required a developer can now be built, reviewed, and refined directly in a creator’s workflow, in the Editor or in WordPress. Everything runs in a sandboxed environment, so you can experiment freely without risk.
This combination of capabilities unlocks many opportunities for freelancers and agencies: the Atomic Editor makes sites easier to build and maintain at scale, while Angie Code expands what’s technically achievable without increasing team sizes. Together, they’re pushing the boundaries of what web creators can deliver.
We’ll have both on display at our booth. Come find us.
Google is excited to connect with the vibrant WordPress community at WordCamp US 2026 in Phoenix.
Stop by our space to meet our experts for hands-on guidance. Discover Site Kit, Google’s official WordPress plugin that brings the best of Google’s insights directly to your dashboard, and explore Nano Banana 2, our next-gen AI model that makes generating custom imagery for your web content effortless.
While you’re here, demo our products and take our survey to collect an exclusive Google swag bundle. Your feedback also enters you into our raffle to win one of three grand prizes. Stop by to connect with our team, gain actionable tips, and take home some swag. No purchase necessary. (Raffle: Void where prohibited. Open to non-government employees only. See Official Rules at the Google booth).
You might not recognize the name Nexcess. You’ll recognize the people.
Nexcess is the new name behind LearnDash, GiveWP, The Events Calendar, and Modern Tribe — the same teams you’ve built businesses alongside for years, now working together under one roof.
Come by the Nexcess Lounge at WordCamp Central to connect with the people behind the tools you already use and see what’s new!
We’d like to thank all our sponsors again for all your support! We’re looking forward to seeing everyone in Phoenix!
View the full schedule and speakers to plan your time with us.
Grab your ticket if you haven’t already!
And join the conversation online using #WCUS #WordPress
]]>Loyal Pyczynski is taking the WCUS stage this year, and if his résumé reads like a highlight reel, that’s because it basically is one: autonomous drone spectaculars, award-winning robotics, generative AI, virtual reality experienced by millions (just to name a few).
Tuesday, August 18, 2026 at 9:15am.
As Vice President of R&D at Walt Disney Imagineering, Loyal led the development of Disney’s first autonomous drone spectaculars and the Stuntronics robotic platform. This is the kind of project where “it’s never been done before” isn’t a warning, it’s the whole point. From there, he became Head of Metaverse Emerging Technology at Meta Reality Labs, leading AI and virtual reality initiatives built for billions of people. Two of the most ambitious technology organizations on the planet, and he was the one figuring out how to turn what they imagined into something real.
Loyal was born a congenital amputee, and he’s built a career-spanning framework called the “10% Gap” around what he’s learned from it including how to move past self-perceived limits, turn imposter syndrome into authentic leadership, and treat uncertainty as fuel instead of a warning sign. He’s also a World Champion triathlete and IRONMAN World Championship division winner, which means the discipline behind his technology career is literally how he trains.
Drawing on his work at Disney Imagineering and Meta, Loyal’s session looks at how AI can help teams build digital products that are genuinely more useful, more engaging, and more distinctly human. He’ll dig into what it actually takes to move past the hype: bringing creators, developers, researchers, and communities into the process early, letting real experimentation guide decisions instead of assumptions, and keeping human judgment and trust at the center of the work.
For a community that’s spent years building tools meant to be used by real people, this is a keynote that speaks directly to the work already happening in this room.
Catch Loyal Pyczynski’s keynote at WCUS 2026 in Phoenix.
Check the full schedule and speakers page to plan your week, and grab your ticket if you haven’t yet.
]]>A friend invited me to a WordPress meetup. I showed up expecting to have somebody to sit with, and they bailed at the last minute. I was already there, so sneaking out wasn’t an option anymore. I got my laptop out and sat down at a table by myself.
The first part of the meetup was set aside for people who needed help with their WordPress questions. A friendly face sat down next to me and asked if I needed any help. I asked about child themes, and he pointed me in the right direction.
That was Chris. More than fifteen years later, I’m still here and still contributing because he sat down and said hi.
Every WordPress person has some version of this story. They had a need, WordPress turned out to be the answer, and somebody helped them with the part they couldn’t figure out alone.
Under normal circumstances, none of us would have crossed paths. We don’t live in the same places, we didn’t go to the same schools, and most of us don’t do the same work. WordPress is the only reason we know each other at all. It isn’t an industry. It’s a congregation of people who volunteered for the same responsibility.
Nobody assigned Chris to help me that night. He had no obligation to help me; just a genuine willingness to help. He explained child themes the way you’d explain them to someone who was definitely going to build one, which at the time was generous to the point of being inaccurate. He knew a thing, I didn’t, and in this community that turns out to be the entire prerequisite.
I saw Chris around for years after that, but we didn’t have a real conversation until 2014, and it happened because of a fire drill in a building two thousand miles away. We were at a WordCamp San Francisco watch party in St. Louis. At the event in San Francisco, an alarm went off and everyone had to evacuate the building. The livestream went dead. So there we were, a room full of people who’d come for the talks, with no talks. We talked to each other instead.
I’ve thought about that day a lot in the years since. The fire drill wrecked the schedule, and without it I don’t know that Chris and I would have ever really gotten to know each other. That was the day he talked me into joining the WordCamp St. Louis 2015 organizing team. I wasn’t qualified to plan a WordCamp. As it turns out, nobody checks. That’s the part that’s hard to explain to people who haven’t contributed to open source before; there’s no gate, no approval, nobody whose job is deciding when you’re ready. You’re ready when you see the work and pick it up.
What makes you an open source contributor was never skill or experience. It’s generosity; the willingness to put time and effort into something bigger than you.
The person on stage right now was wiping down tables this morning. That speaker is someone else’s mentee. The people helping at the Happiness Bar gave up a session they wanted to see so a stranger could have the same aha moment they had a few years ago. At least one organizer took PTO from a job that has nothing to do with WordPress in order to be here.
There are opportunities to contribute all week. Some of them are literal, at Contributor Day. Most of them are just small acts of kindness in the halls of a convention center. Lending a hand to someone who needs one counts as much as a line of code. Both things sustain us.
Organizing a WordCamp comes with a long list of thankless jobs, and the most thankless of all is dealing with the venue. Somebody arranged the space, the furniture, the food, and figured out how much coffee two hundred people drink before noon. I have never once heard that person thanked from a stage, and I’ve helped organize almost a dozen of these events, so I’ve had plenty of chances to notice.
You don’t notice either, and that’s not a criticism; it’s by design. Nobody walks into a room and thinks about the room. You think about the room only when something isn’t the way you expected it to be.
I sat down to make a list of the people who’ve helped me get here and I couldn’t finish it. I couldn’t even come up with most of their names. That isn’t a failure of memory. Invisible work is invisible; that’s the deal. Forty percent of the web runs on the labor of people I cannot name and will never meet.
The first time I came to a WordCamp US Contributor Day, I didn’t know where to sit. I ended up at the Community table and spent the day updating documentation, which is about as unglamorous as contributing gets. Parts of those changes are still there today. If they weren’t, you’d notice.
I didn’t say yes to organizing a WordCamp because I had the skills. I said yes because someone invited me to come along. I didn’t believe I could do it. Chris did. Now I’m the one saying it to other people.
That’s the actual mechanism keeping this project alive. Not governance or funding; people believing in each other slightly ahead of the evidence.
At some point this week, somebody will be standing somewhere by themselves. Don’t let them linger. Invite them in.
At WordCamp US, nobody is just an attendee. Not even you. Contributing to open source can start with simply saying hello.
]]>