What Makes a Great Contributor Day Workshop?

Step into a WordCamp Contributor Day, and you will find an electric, high-energy environment. People gather from all over the world with a shared goal: to build, translate, test, document, design, and support the open-source project.

But for a long time, walking into Contributor Day as a newcomer could feel like stepping onto a moving train. You found an open table, stared at a blank screen, and tried to figure out local server environments, contribution workflows, Slack channels, or Git repositories while everyone around you already seemed to know where they were going.

Contributor Day workshops are designed to bridge that gap.

They are practical, guided sessions where participants can learn by doing, ask questions, and leave knowing how to take the next step.

At WordCamp Asia 2027, we are planning workshops for both technical and non-technical contribution paths. Depending on the final event setup, some may happen onsite, some on the main event days, and some may be offered online before WordCamp Asia.

The format may change. The promise should not: practical work, clear guidance, reusable materials, and real help when you get stuck.

Whether you are a newcomer deciding if a workshop is worth your time, or a contributor thinking about stepping up as a facilitator, here is what we believe makes a great Contributor Day workshop.

Table of Contents

For Attendees: Entering the Room

1. You Build Instead of Listening

The biggest misconception about a conference workshop is that you will sit quietly through a long slide presentation.

Contributor Day workshops flip that model.

From the moment you open your laptop, you should be doing something: testing, translating, building, reviewing, configuring, writing, or working through a real contribution workflow.

The goal is not to leave with a page of notes.

It is to leave having actually done something yourself.

“The hands-on format is the thing I’d definitely keep. Getting people actually building rather than sitting through a presentation seems to work particularly well for beginners.” — Jamie Marsland

2. You Know What You Are Trying to Achieve

A good workshop has a clear outcome.

Instead of trying to teach everything about a Make WordPress team or contribution area, it focuses on one practical result participants can realistically reach.

That might mean:

• setting up a contribution environment;
• testing a WordPress feature and reporting what happened;
• submitting a translation;
• building a block pattern;
• reviewing a learning resource;
• understanding and completing a contribution workflow.

A useful question for every workshop is:

What should a participant be able to do after this session that they could not confidently do before?

Clear outcomes also help with pacing. Participants know where they are going, facilitators know when the group is falling behind, and everyone can measure progress against something concrete.

3. Contribution Is More Than Code

One of the most persistent misconceptions about WordPress contribution is that it belongs mainly to developers.

Code matters, but WordPress also needs testing, translation, accessibility, documentation, design, support, training, community work, photos, video, and many other skills.

Historically, many Contributor Day workshops have focused on technical setup because that is one of the biggest barriers for development teams. But that should not limit what a workshop can be.

For WordCamp Asia 2027, we are intentionally staying open to a wider range of topics.

We already have promising proposals in several areas, including beginner-friendly and AI-related sessions, and the final programme will be shaped by the strongest workshop ideas we receive.

The important question is not “Is this technical enough?”

It is:

Does this workshop remove a real barrier and help someone contribute?

4. Help Is Built Into the Workshop

Getting stuck on a software installation, missing account, broken setting, or unfamiliar tool during a live workshop is frustrating.

A good workshop should expect that to happen.

Our planned format uses a Lead Facilitator supported by Co-Facilitators. The Lead can keep the session moving while Co-Facilitators help individual participants who hit problems or fall behind.

That support matters because not everyone has the same laptop, operating system, experience, or setup.

The aim is not to promise that nobody will ever get stuck.

The aim is to make sure getting stuck does not mean the workshop is over for you.

5. The Workshop Should Still Be Useful Afterwards

A workshop is only one session.

Good workshop materials should continue helping people after it ends.

That may include:

• step-by-step instructions;
• setup guides;
• exercise files;
• examples;
• troubleshooting notes;
• useful links;
• next-step contribution tasks;
• information about where to ask for help.

The best workshop does not disappear when the room closes.

It gives you something you can return to the next day, next week, or when you are ready to make your next contribution.

As Co-Facilitator lead Muhammad Ridha Ridwan observed, robust step-by-step guides ensure that “they can also still learn it even after the session ends.”

For Facilitators: Designing a Workshop That Actually Helps

A great workshop is not defined by how much information the facilitator can fit into 90 minutes.

It is defined by what participants can actually do with that information.

1. Start With One Clear Outcome

Before building slides, exercises, or setup instructions, decide what success looks like.

Ask:

What should participants be able to do by the end?

Keep the outcome realistic.

“Understand Core contribution” is too broad.

“Set up the development environment, find a suitable ticket, and understand how to test it” is much easier to design around.

“Learn Polyglots” is vague.

“Log in to the translation platform, understand the basic workflow, and submit your first translations” gives everyone a destination.

2. Keep It Hands-On

Demonstration is useful.

Practice is better.

Participants should spend a meaningful part of the session actually doing the work themselves.

Show only what they need to get started, then give them room to try it.

Pause at logical checkpoints.

Let people ask questions.

Make space for things to go wrong.

The workshop should feel less like watching someone else drive and more like taking the wheel yourself.

3. Plan for People to Get Stuck

Assume that someone will:

• use a different operating system;
• already have conflicting software installed;
• forget a password;
• miss a setup step;
• move faster than everyone else;
• move slower than everyone else;
• encounter an error nobody predicted.

That is normal.

A good workshop plan includes not only the happy path, but also what happens when things do not work.

This is where Co-Facilitators become essential.

Before the session, facilitators should agree on roles: who keeps the main workshop moving, who watches the room, who helps with setup problems, and who handles questions.

Previous facilitators found that this division of roles becomes particularly important in busy sessions. Nimesh Agrawal described a successful setup with one main facilitator leading the session and two Co-Facilitators making sure participants could keep up.

Technical workshops also need to expect local setup differences. Muhammad Ridha Ridwan recalled participants arriving with environments such as LocalWP or XAMPP that conflicted with the tools used in the workshop, requiring active troubleshooting to keep everyone moving.

4. Design for Different Speeds

Not everyone will finish at the same time.

It helps to think in three layers:

Minimum outcome
What should everyone ideally achieve?

If you finish early
What optional next step can you try?

If you get stuck
What simpler checkpoint still lets you understand the workflow and continue later?

This prevents faster participants from becoming bored and slower participants from feeling abandoned.

5. Respect the Clock While Protecting Practice Time

Standard 90-minute time slots are tight. Facilitators may be able to cover the core concepts in that window, but participants still need enough time to practice.

Keep the conceptual introduction focused and protect as much hands-on time as possible. If half of a 90-minute workshop is spent talking, participants may not have enough time to actually complete the exercise.

When a workshop runs out of time while participants are still in the middle of the exercise, the session can feel unfinished. Protect enough time for people to practice, ask questions, and reach the workshop’s minimum outcome.

6. Leave a Clear Path Forward

Contributor Day workshops exist to help people contribute.

At the end, participants should know:

• which Make WordPress team or workflow the workshop connects to;
• where that team communicates;
• where to find suitable tasks;
• where to ask for help;
• what they can do next;
• how to continue after WordCamp Asia.

If possible, the workshop should connect naturally to the related Make Team table or contribution activity.

A good workshop does not end with:

“Thanks for coming.”

It ends with:

“Here is what you can do next.”

Onsite or Online: The Same Promise

We are currently planning workshops as part of WordCamp Asia 2027, and we are keeping the format flexible. Workshops may take place onsite, online before the event, or in a combination of formats.

Wherever the workshop happens, the experience we want to create remains the same.

A Lead Facilitator can guide the main session while Co-Facilitators help through chat, breakout rooms, screen sharing, or other suitable tools.

Pre-event online workshops can also offer some advantages: participants can prepare earlier, solve setup problems before travelling, meet contributors in advance, and arrive at WordCamp Asia already knowing where they want to go next.

Whatever the format, we want the same things to remain true:

• participants do real work;
• facilitators provide clear guidance;
• help is available when someone gets stuck;
• materials remain useful afterwards;
• the workshop leads somewhere beyond the session itself.

A Great Workshop Helps You Catch the Train

Contributor Day can still feel fast-moving.

There are teams already working, conversations already happening, tools you may never have used, and people who seem to know exactly where they belong.

A great workshop does not stop that train.

It gives you a platform, a map, and someone standing beside you saying:

Start here. We’ll help you get on.

If you are thinking about attending a workshop, come ready to participate, ask questions, and try things yourself.

If you are thinking about facilitating one, design around what participants will actually be able to do when the session ends.

We are currently reviewing workshop proposals for WordCamp Asia 2027 and will share the final programme as it develops.

In the meantime, explore Contributor Day, find the Make WordPress teams that match your interests, and start thinking about what you would like to learn — or teach — when we meet in April 2027.