A year ago, I was still learning what it meant to be part of a WordCamp organizing team.
My first time as a WordCamp organizer was at WordCamp Asia in Manila last year. At that time, I was still getting a feel for how everything worked behind the scenes. I had attended WordCamps before, contributed where I could, and volunteered in different ways, but organizing gave me a different view of the community.
I started to see the work that attendees do not always notice: the planning, the follow-ups, the signs, the schedules, the small reminders, the design requests, the volunteer coordination, and the many quiet decisions that help make the event feel smooth.
This year, that journey continued in a much bigger way.
WordCamp Asia 2026 was only my second time as a WordCamp organizer, not to mention flagship WordCamp and I found myself stepping straight into a leadership role as Contributor Day Team Lead. Aside from that, I also helped organize YouthCamp and supported the Design Team by managing Contributor Day materials, visuals, and assets.
It was exciting, but I would be lying if I said it was not overwhelming at times.
Contributor Day is one of the most meaningful parts of WordCamp for me because it gives people a doorway into the WordPress project. For some, it is their first time seeing how WordPress is built and supported beyond using it as a website tool. For others, it is a chance to reconnect with a team, continue contributing, or help someone new get started.
And that is what made the role feel important. It was not only about schedules, tables, floor plans, signs, or materials. It was about helping people feel welcome enough to participate.
From volunteer to lead
My earlier volunteering and organizing experience helped me understand how much small details matter.
When you are an attendee, you usually see the event from the front. When you volunteer or organize, you start to notice the work behind it. You see the planning, the last-minute changes, the table arrangements, the questions from attendees, and the people quietly helping in the background.
That experience shaped how I approached Contributor Day.
I kept thinking about the first-time contributor walking into the room, unsure where to go or what to do. Contributor Day can be intimidating at first. There are experienced contributors, table leads, laptops, Slack channels, GitHub issues, Trac tickets, translations, documentation tasks, and so many moving parts.
So one question stayed with me throughout the planning:
How do we make this easier for someone who is just starting?
Contributor Day is not only for developers
One thing I always want people to know is that Contributor Day is not only for people who write code.
Yes, there are technical teams. But WordPress also needs writers, designers, translators, testers, photographers, support contributors, documentation contributors, community builders, and people who are simply curious enough to ask, “Where can I help?”
That is what makes Contributor Day special.
People come in with different skills, backgrounds, and levels of confidence. Some already know where they belong. Others are still figuring it out. A good Contributor Day makes space for both.
For WordCamp Asia 2026, we wanted the day to feel organized, but not overwhelming. Helpful, but not too formal. Structured, but still human.
That also applied to the design work. The materials, signs, maps, and visual guides were not just there to make things look nice. They helped people understand where to go, what was happening, and how to move through the day with a little more confidence.
The work behind the scenes
A lot of the work happened before Contributor Day itself.
There were table leads to coordinate with, schedules to prepare, team assignments to think through, workshops to support, floor plans to review, and attendee guidance to organize.
I also helped manage the Contributor Day assets and materials with the Design Team. That part reminded me that design is also a form of communication. A clear sign, a readable slide, or a simple map can make a big difference for someone who is already nervous or unsure.
Aside from Contributor Day, I also helped organize YouthCamp. That was a different but equally meaningful experience. Seeing younger participants get introduced to WordPress and open source reminded me that community work is not only about the contributors we have today, but also about the people we welcome next.
The Open-Source Library was another part of the day that I really appreciated. It created space for people to learn from real stories and conversations. It showed that contribution does not always begin with a task. Sometimes, it begins with hearing someone else’s journey and realizing that there is room for your own.
Learning to lead with trust
Leading Contributor Day came with pressure.
There were many moving parts, and not everything had a perfect answer right away. Some things changed. Some things needed quick decisions. Some things required patience and several conversations before they became clear.
That is part of organizing.
I learned that leadership in community work is not about controlling everything. Most of the time, it is about listening, connecting people, removing confusion, and trusting others to do what they do best.
It was not just my role that made the day work. It was the co-leads, organizers, table leads, volunteers, workshop facilitators, Open-Source Library contributors, YouthCamp facilitators, the Design Team, and the attendees themselves.
Contributor Day is built by many hands.
The day itself
When Contributor Day finally happened, it was special to see months of preparation turn into real moments.
People arrived with laptops, questions, excitement, and sometimes a little uncertainty. Some knew exactly which team they wanted to join. Others were still looking for the right place to start.
I saw table leads patiently guiding new contributors. I saw workshops helping people understand things that may have felt too technical before. I saw conversations happening around the room. I saw young participants at YouthCamp exploring what they could create. I saw people using the signs, maps, and materials we prepared to find their way.
Those small moments mattered to me.
Because that is where Contributor Day becomes more than a program. It becomes a place where someone can say, “Maybe I can do this too.”
What I learned
The biggest lesson I took from WordCamp Asia 2026 is that people contribute better when they feel welcome first.
Before someone opens a ticket, translates a string, writes documentation, tests a patch, submits a photo, or joins a discussion, they need to feel that they belong in the room. They need to know that questions are okay. They need to feel that being new is not a problem.
I also learned that clear guidance matters. A beginner-friendly Contributor Day does not happen by accident. It takes planning, patient table leads, useful materials, visible support, and people who are willing to help.
And I learned that leadership is not about having all the answers. It is about helping people move together, even when things are not perfect.
Sometimes, the most meaningful part of Contributor Day is not the number of tasks completed. It is the person who leaves feeling confident enough to come back.
Looking back
WordCamp Asia 2026 gave me a deeper appreciation for the WordPress community.
I have worked with WordPress for many years, but community work always reminds me that WordPress is more than software. It is people. People who write code, test patches, translate strings, design materials, answer questions, organize events, guide beginners, and keep showing up.
Serving as Contributor Day Team Lead on only my second WordCamp organizer experience, while also helping organize YouthCamp and supporting the design work for Contributor Day, taught me that contribution can happen in many forms.
Sometimes it is technical. Sometimes it is creative. Sometimes it is logistical. Sometimes it is simply helping someone feel less lost.
And all of it matters.
If you are thinking about joining Contributor Day someday, I hope you do.
You do not need to know everything before you start. You do not need to be a developer. You do not need to arrive with full confidence.
You can arrive curious.
You can arrive with questions.
You can arrive unsure.
That is okay.
Sometimes, the first contribution is simply showing up.
