This week marked the official start of my WP Credits journey. Coming from the DAM (Multiplatform Application Development) course, I was excited but also a little nervous — WordPress’s open-source community is huge, and I wanted to make sure I started on the right foot.
What I did this week
I went through the Onboarding module: reading the communication guidelines, learning how decisions are made in the WordPress project, and being introduced to “the WordPress voice” for writing. I also joined the global Slack workspace, which honestly felt like stepping into a small city: so many channels and many conversations happening at once.
The most useful part of the week, though, was creating my WordPress.org profile. It’s the identity you’ll use across the whole contributor ecosystem, so getting it right matters.
What was hard — and how it went
The biggest source of confusion this week was, without a doubt, WordPress.org vs WordPress.com. They sound like the same thing, use the same logo, and even have similar-looking dashboards — but they serve completely different purposes. WordPress.org is the open-source software and the home of the contributor community (forums, teams, Slack, Trac); WordPress.com is a commercial hosting service built on top of that same software. I registered on the wrong one first, and only realized my mistake when my profile wasn’t showing up where the course expected it. I had to redo the sign-up on WordPress.org specifically, and double-check that my username there matched what I’d use in Slack and on my future site. It sounds like a small thing, but for someone brand new to the ecosystem, it’s a very easy trap to fall into.
The second thing I struggled with was simply the volume of information in the onboarding material — Slack etiquette, team structures, the “five for the future” philosophy, decision-making processes. I didn’t try to memorize everything; instead, I bookmarked the pages I knew I’d need to revisit and focused on understanding the big picture first.
Challenges & what I learned
This week taught me more than I expected for what was, on paper, just an “onboarding” week. The .org/.com mix-up was frustrating in the moment, but it forced me to actually understand the structure of the WordPress ecosystem instead of skimming past it — I now know that .org is where contribution happens, and that my identity there (username, profile, avatar) is something I’ll be building on for the rest of the course, so it was worth getting right early rather than fixing it later.
I also learned something less technical: that a community this size runs on written communication far more than I expected. Slack channels, decision-making docs, contribution guidelines — almost everything is text-based and asynchronous, which means clarity and tone matter a lot. Getting introduced to “the WordPress voice” made me realize that even a small thing like how you phrase a Slack message is part of participating well in an open-source project. Finally, I learned to resist the urge to “finish” onboarding perfectly in one sitting — treating it as a reference to come back to, rather than a checklist to rush through, made the whole week feel far less overwhelming.
Leave a Reply