Skip to main content
Be Better Blog
Strategy & Insights

Inside WordCamp Portland

By Bobby Lee
December 19, 2025
Members of the Noble Studios team attending WordCamp Portland with conference signage, session rooms and crowds in the background.

WordCamp Portland offered a clear reminder of what makes the WordPress community work: people who care deeply about how things are built. Across contributor tables, technical sessions, vendor hall strolls and informal conversations, the focus stayed on craft, sustainability, and the systems that support long-term growth.

Fellow Senior Web Developer Matt Crisp and I came to WordCamp Portland with a straightforward goal: spend time with the people building WordPress, contribute where it made sense and get a clearer read on where the platform is going. That approach informed everything we did while we were there.

Contributor Day and the Reality of Core Work

Contributor Day set the tone early as we chose to spend the day at the WordPress core table, which proved far more demanding than contributing to themes in previous years. Core work moves slowly. It requires local environments, testing workflows, review cycles and a lot of coordination with people who work in the codebase full-time.

Most of the day was spent setting up, testing older issues and working alongside the table lead to move a long-standing item closer to resolution. The final contribution was modest on the surface, but it counted, and it placed Noble on the contributor board for core work. More importantly, it offered a close look at how decisions move through WordPress and where help is actually needed.

That setup also made it easy to talk with developers from other agencies who are running into the samechallenges we are. A lot of the conversations felt familiar. Scaling block-based builds, managing performance expectations and working through workflows that were never meant for where WordPress is today kept coming up.

Contributor Day has a way of reshuffling priorities. You walk in with a list of things you want to learn and walk out with a different set of problems you actually want to work on.

WordCamp Portland collage showing speakers on stage, sponsor booths, local Portland scenery and informal conversations between attendees.

What the Sessions Made Clear

Across sessions, a few themes came up repeatedly. 

AI was a common topic in many of the presentations, often framed as a tool that can support developers when used thoughtfully rather than something meant to replace them. A common position among the presenters was that AI shows great promise as a tool to help humans, but if used as a replacement, the output is lackluster.

Tools are emerging that allow blocks to be generated from the command line, and WordPress itself is moving toward deeper AI integration. At the same time, speakers were clear that these tools amplify existing practices. They reward clarity and discipline and expose weak foundations quickly.

The SEO conversations followed a similar mindset. One session spent less time on rankings and more time on user experience. The takeaway was that chasing algorithm changes usually leads to short-term wins at best. Sites that load quickly, communicate clearly and actually serve real users tend to hold up better without constant tweaking.

System-based development also came up often. Instead of solving the same problems site by site, more teams are investing in shared foundations that can evolve. This approach reduces rework and makes it easier to adopt new WordPress features as they mature. It closely mirrors how Noble approaches WordPress and web development.

Being Ready for What WordPress Is Becoming

One of the more encouraging parts of the week was how familiar many of the ideas felt.

There was not much discussed that our Noble team could not already test, adopt or explore. That did not happen by accident. It comes from moving earlier into block themes and deeper Gutenberg work while many agencies are still figuring out that transition.

Those decisions came up often in conversation. Talks with core contributors and platform vendors naturally drifted toward how Noble made that shift and what it took to get there.

In one case, a casual conversation with the founder of Pantheon turned into an invitation to share our work more publicly. Even when the specifics stayed proprietary, it was clear the experience itself was relevant to a lot of teams navigating the same change.

Collage of WordCamp Portland scenes including conference sessions, sponsor areas, Portland streets, event signage and attendees networking.

Why Being There Still Matters

Outside of the sessions, WordCamp Portland showed its value in smaller but important ways.

The sponsor hall stayed busy, helped along by good food and a steady supply of coffee and Voodoo donuts. More importantly, it created space for meaningful connections. Conversations with vendors, contributors and other agencies felt easy and unforced, the kind that carry on beyond the event itself.

Portland also made getting around simple. Public transit connected the airport, hotel and venue so smoothly that rideshares were unnecessary. Even the closing event stood out. Getting there meant heading to the deepest subway station in North America and riding a long elevator up to the venue. It was one of those moments that sticks with you simply because of the experience.

By the end of the week, the days were full from morning through late evening. Between sessions, contributor work, vendor gatherings and informal conversations, there was very little downtime. Everyone came back tired but clear-headed, with a long list of ideas worth exploring further.

WordCamp Portland reinforced the value of staying close to the work itself. Contributing, listening and building alongside the community helps keep teams grounded as WordPress continues to change. That perspective is part of how Noble stays ready for what comes next, not just what works today.

If you are thinking about how your WordPress platform needs to evolve, Noble builds modern, scalable WordPress solutions designed to grow with the ecosystem. Let’s talk.


Editor’s Note: This article was written with significant contributions from Senior Web Developer Matt Crisp.

Up Next