How I Earned My WordPress Meta Contributor Badge (And How You Can Too!)

A badge of network icon wrapped in pink color with text describing the purpose.

If you’re involved in the WordPress community, you’ve probably come across contributor badges, those cool little icons next to usernames that recognize contributions to WordPress projects. Recently, I earned my very own Meta Contributor badge, and I’m excited to share how it happened, what I learned, and how you can do the same!

Check my WordPress.org profile to check it!

My Journey to the Badge

It all started when I noticed an accessibility issue on the Polyglots Team page at WordPress.org. Specifically, the “Download WordPress in [Locale]” button was using white text on a very light gray background, making it difficult to read and failing WCAG contrast standards.

You can see the original ticket here: Meta Trac #7986.

My initial report clearly outlined the accessibility issue and included screenshots to illustrate the problem. I also provided a simple CSS patch on https://github.com/WordPress/wordpress.org/pull/490 to correct the color contrast by removing the problematic CSS rule.

Engaging with the maintainer

What made this experience particularly rewarding was the collaborative effort that followed. Community maintainers quickly reviewed the issue, validated it, and encouraged me to move forward.

I created a pull request on GitHub to clearly document my suggested changes:

PR #490.

The PR clearly explained the adjustments, and after some helpful exchanges and review, the maintainers acknowledged my concerns and decided to update within the day.

Getting Recognized

Although my specific patch wasn’t directly merged, since the committer opted for a different approach, updating the link to a button, the issue I highlighted was effectively resolved. Impressively, within just 24 hours, I proudly received the Meta Contributor badge on my profile, acknowledging my valuable contribution to WordPress.org’s accessibility efforts.

How You Can Do It Too

Want your own badge? Here’s what you need to know:

  • Identify an Issue: Explore Meta Trac for open tickets or identify issues yourself on WordPress.org.
  • Report Clearly: When creating a ticket, clearly describe the issue, provide screenshots if necessary, and explain its importance.
  • Engage Actively: Respond promptly to feedback, remain open to suggestions, and revise your contribution as needed.
  • Submit a PR: Once your issue is acknowledged, create a concise, well-documented pull request on GitHub.
  • Celebrate: After your PR is merged or your issue addressed, keep an eye on your profile—your badge will appear soon!

Contributing to WordPress isn’t just about badges, it’s about joining a vibrant community, gaining new insights, and enhancing a platform that millions depend on. So, why wait? Jump in, share your skills, and enjoy the rewarding experience of contributing.

Have you made contributions or do you have insights to share? I’d love to hear your story in the comments!


  • Contributor Highlights v1.1.0 Released

    I’m excited to announce that Contributor Highlights has been updated to version 1.1.0. This release introduces new badges, resolves dependency issues, and improves layout alignment for a smoother and more consistent experience. ✨ What’s New Why This Update Matters My goal for Contributor Highlights is to continuously evolve alongside the WordPress community. The new badges…

  • Chronicle Journal Theme Demo Now Live

    I’m happy to share that the Chronicle Journal theme demo site is now live at chronicle-journal.rollybueno.com. Chronicle Journal is a modern, editorial-style WordPress theme built for writers, storytellers, and publishers who want a timeless and focused reading experience. It’s designed around clean typography, balanced layouts, and subtle spacing that lets your words take the spotlight.…

  • Joined WCUS 2025 Contributor Day Remotely – Hosting Team Wins

    This year I got the chance to join WordCamp US 2025 Contributor Day remotely, and I’m really happy to share that I was able to contribute to the Hosting Team. Even though I wasn’t there in person, it honestly felt like being part of the action. The collaboration, support, and energy from everyone made it…

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *