Portland buzzed with energy as WordCamp US 2025 brought together the makers and dreamers of the WordPress community. For four days, developers, designers and everyday site builders swapped stories, shared knowledge and pushed the open web forward.
In the middle of that momentum was Bluehost. We showed up not just as a sponsor, but as an active participant. From booth conversations to technical talks, the focus was clear: make contributions more approachable for everyone.
Spotlight on Evan Mullins
That spirit shone brightest in a session led by Evan Mullins, Senior Software Engineer at Bluehost.
Known for sharing insights across WordCamps and meetups worldwide, Evan has spoken on topics ranging from theme modifications to web development for WordPress. You can check out the full list of Evan Mullins’ talks here.
At WCUS 2025 in Portland, he posed a simple question with big implications: What if contributing to WordPress didn’t start with code, but with curiosity?
The myth-buster: you don’t need to be a developer
Mullins opened by tackling the biggest misconception head-on: “Who can test WordPress?” His answer was immediate and disarming,
“You can test it. It doesn’t take any special skills or certificates. It’s something anyone can do and I really think anyone should get involved. Testing helps you understand the product better and you can really contribute that way.”
This reframes what contribution means. Testing isn’t just for seasoned developers; it’s about curiosity, persistence and the willingness to click around, spot issues and share feedback
The community also makes it worthwhile. Testers earn profile badges and see their names credited in release notes, turning simple acts of feedback into visible recognition within the project. And as Mullins reminded the audience,
“If we don’t test it, it’s not going to get better. But if we do, hopefully it will.”
Understanding that anyone can test is just the beginning. The real impact comes from knowing how the testing process works, step by step.
Inside the WordPress testing cycle: Simple ways to contribute without writing code
Mullins explored the lifecycle of testing. Let’s examine the step-by-step process involved in testing.
1. Key Stages in the bug and patch testing lifecycle
Mullins walked the audience through the journey every bug takes in WordPress, showing how community involvement keeps the cycle moving forward. Here’s how the process unfolds:
- Bug reporting: It begins when someone spots an issue. He/she checks for duplicates in Trac or GitHub. Afterwards, a clear report with steps to reproduce is created. This report includes details about their setup (WordPress, PHP, browser, OS) and ideally a screenshot or short video. Security issues, Mullins reminded, are handled privately through HackerOne.
- Reproducing the bug: Testers then step in to confirm the problem on a clean setup that includes a core theme, no plugins and different environments. It is essential to document exactly how to reproduce the issue to ensure others can observe the same result.
- Developing a patch: Once confirmed, a developer proposes a fix. In Trac, that usually means uploading a .diff or .patch file; in GitHub, it takes the form of a pull request. Either way, it’s linked back to the original ticket.
- Validating the patch: The fix doesn’t stand on its own. Testers apply it using local tools such as WP-CLI, the Beta Tester plugin or even one-click Playground. This way, they verify the issue is resolved. They also check related flows to guard against regressions, posting concise reports with results and supporting media.
- Core committer approval & merge: Only after sufficient review and successful testing do core committers step in to merge the change into WordPress.
- Shipping in a release: Finally, the fix is deployed in a beta or release candidate and then rolled into the general release. Contributors who played a part in the process receive credit and the cycle moves on to the next issue. It shows that every small contribution shapes WordPress for millions of users.
Where to start (today): Ride the release cycle
One of the easiest ways to get started with testing is by following the release cycle. Each stage, Beta 1, Beta 2, Beta 3 and the Release Candidates, drops about a week apart. This creates a cadence of short sprints where the community can dig in, explore and give feedback.
The process is straightforward: install the beta, use WordPress as you normally would and flag anything that feels off.
Mullins reminded the audience, it’s not enough to just check that the update runs. Real insights come from everyday actions.
“It’s important to test more than just, ‘the update worked.’ Try creating a post, editing a post, actually use WordPress.”
He pointed to the WordPress 6.9 timeline (pictured above) as a live example of how structured and accessible the testing cycle has become.
It maps out the testing windows, from Beta 1 on October 21 through RC1 (Nov 11), RC2 (Nov 18), RC3 (Nov 25), a dry run (Dec 1) and the general release (Dec 2)
He noted that each release milestone is more than a calendar event, it’s a live opportunity to test alongside others.
These “release parties,” hosted in the official WordPress Slack (#core), allow contributors to install the build in real-time, share feedback and help catch last-minute issues before the update goes public.
The most social way to contribute: Release parties on Slack
Do you prefer to learn by doing with others? Join the #core release parties on the WordPress Slack. They’re scheduled sessions where release deputies announce a build, share exact update links and call for testing. You’ll see people post quick “✅ tested” notes with what they tried and where.
Mullins recommends a non-production site for these (never your client’s live site!). Many hosts, including Bluehost WordPress hosting, allow you to spin up additional WordPress installations on a single account specifically for testing. It’s zero-drama, high-impact participation.
And the opportunities don’t stop there. The main WordPress bug tracker currently lists more than 8,000 + open tickets. That’s thousands of chances for contributors to step in and make a difference.
The ticket graph above shows ticket activity over the past 90 days. Green bars mark new reports, red bars show closed issues and the steady line above 8,000 represents open tickets. It’s a clear snapshot of the ongoing workload and a reminder of how valuable every tester’s contribution is.
From GitHub to browser in 10 seconds: How is Playground transforming WordPress contribution?
The demand is huge. But as Mullins emphasized, you don’t need to be a developer to help. With tools like WordPress Playground, you can test fixes directly in your browser, with no coding knowledge required or local environment setup needed.
One of the biggest breakthroughs Mullins highlighted was WordPress Playground: a full WordPress site that runs entirely in your browser. With Playground, testing no longer requires local setups, command-line tools or patch files.
Instead, on any GitHub pull request, you’ll see a link to “Test this PR with WordPress Playground.” Click it and within seconds you’re inside a live WordPress instance with the code changes already applied.
This one-click flow removes the steepest barrier to contribution. You can reproduce bugs, verify fixes and even switch PHP versions or languages, all without installing anything. For testers, validating patches is faster, simpler and more accessible than ever.
Also read: A Beginner’s Guide to Using Git with WordPress
The workflow makes it clear how simple the process is:
- Find PR: Start with the pull request in GitHub that contains a proposed fix.
- Locate bot: Look for the GitHub Action Bot’s comment, which automatically adds a Playground link.
- Click link: Hit “Test with WordPress Playground.”
- Wait ~10s: Playground spins up a browser-based WordPress site with the fix already applied.
- Start testing: Use the site as you normally would. Create posts, edit pages or check settings to confirm the patch works.
In less than a minute, you’re contributing without ever leaving your browser. This is definitely a game-changer for making testing accessible to everyone.
Inside the Bluehost booth at WCUS 2025: Tools, SEO insights and a buzzing crowd
Evan’s talk was a reminder that our presence in the WordPress ecosystem goes far beyond sponsorship. On stage, he demonstrated how contributions can be made easier for everyone, lowering barriers with tools like Playground and encouraging non-developers to get involved.
At our booth, the focus was on discovery and innovation.
- WonderSuite: Many attendees flocked to explore WonderSuite, our AI-powered site creator. It drew consistent curiosity from builders of all levels.
- Agency Partner Program: Freelancers and agencies packed in to learn more about our Agency Partner Program. The attendees were excited to explore the exclusive benefits tailored to their business needs.
- Affiliate Program and Bluehost Cloud platform: Others stopped by to get insights into our Affiliate Program and the newly launched Bluehost Cloud platform, sparking numerous conversations about performance and growth.
- Yoast SEO collaboration: Alongside our friends at Yoast, we demonstrated how SEO best practices and powerful hosting work hand-in-hand. Attendees appreciated the opportunity to see how Yoast SEO and Bluehost tools can work together to help websites grow smarter and faster.
Of course, it wasn’t all business. The booth buzzed with activity thanks to the Buzz Wire game and live demos. Our booth also featured an epic raffle that sent lucky winners home with exciting prizes like a Nintendo Switch 2, a LEGO Treehouse set and a VR headset.
Takeaways for the community
WordCamp US 2025 reminded us that contribution isn’t reserved for developers or power users. It is practically open to anyone willing to explore, ask questions and share feedback.
From Evan Mullins’ inspiring session to the buzz at our booth, the week in Portland proved that progress happens when curiosity meets community.
For us, it was never just about sponsoring the event; it was about showing up as teachers, teammates and builders alongside the people who make WordPress thrive.
Tools like Playground, programs like WonderSuite and the Agency Partner Program and the collaborative spirit of events like WCUS all point to the same truth: contribution has never been more accessible.
There you have it, the old barriers to entry have vanished. The tools are here, the community is ready and waiting and the need for testers is crystal clear.
So, the next time you run into a weird glitch on a WordPress site, rather than complaining, you can be a critical part of the solution. The only question left is, will you step in?
Write A Comment