The Documentation team orientation form

Welcome to the WordPress Documentation team. We know it's overwhelming to start contributing to the Docs but don't worry. We will take you through every step. But first, we need to learn a little bit more about you. Let's get started.

Some or a lot of things have changed since your last visit, but worry not. We'll show you around and you'll get back on track in no time.

In case you missed it, we have some new roles which might be of interest to you. Let's first see what you know and what you like, and then we'll offer you some options.

Issues triage facilitator

Every other week, instead of the regular meeting, the Documentation team holds Issues triage (checking GitHub issues for tasks completeness). The goal is to move things forward and avoid staling of the tasks. You don't have to know how to complete all those tasks, just to ask what would be the best next step for the issue. You can read more about the role here. 

GitHub issues coordinator

As the number of issues grows, we need someone to watch them over and do the initial actions (apply proper labels, welcome contributors who want to work on issues, ping appropriate people etc). You can read more about the role here. 

GitHub issues reviewer

To make sure our documentation is written in the best possible way: with all the necessary screenshots, without grammar errors, clear and concise and following the documentation style guide; we like to have at least one review for created content. You can read more about the role here. 

Onboarding coordinator

This role is excellent for someone who has been around long enough to know what's happening and where but not too long to forget how it felt to be new. You'll be giving a helping hand to new contributors and releasing them into the wild of the documentation. You can read more about the role here. 

Contributor Day facilitator

This is not something you can do every day. For what is the Contributor Day facilitator without the Contributor Day? But when you see one, you'll know what to do if you read more about the role here. 

Design roles

Yes, we have design-related roles as well! You can read more about the role here. 

General end-user documentation

This role writes and updates general end-user documentation. General means anything that's not a block editor. You can read more about the role here. 

Block editor end-user documentation

This role writes and updates block editor end-user documentation, which means all the blocks, patterns and site editor functionality. You can read more about the role here. 

Feedback curator

We have a system for people to give their feedback about the end-user documentation but we need a person who's going to filter out that feedback and forward it to the right place. You can read more about the role here. 

More information curator

The Code reference handbook is mostly generated from the code itself. However, the "More information" section is created directly on the handbook page. It covers deeper explanations and code examples for utilising the function, hook, method or class. You can read more about the role here. 

User contributed notes curator

The Code reference handbook has a "User contributed notes" section. These are comments, submitted by the documentation users. Curator manages submitted pending comments. You can read more about the role here. 

Common APIs handbook

The Common APIs handbook covers all the APIs that are general for WordPress and not specifically used in themes or plugins. You can read more about the role here. 

Plugins handbook

The Plugins handbook covers APIs and best practices for developing plugins. You can read more about the role here. 

Themes handbook

The Themes handbook is created and maintained in collaboration with the Themes team. To contribute to the handbook you can contact either the Documentation or Themes team. The handbook covers APIs and best practices for developing themes, classic and block-based ones. You can read more about the role here. 

Block editor developer handbook

The Block editor developer handbook is created and maintained in collaboration with the Core team. To contribute to the handbook you can contact either the Documentation or Core team. The handbook covers APIs and best practices for developing with and on top of the block editor. You can read more about the role here. 

Advanced administration handbook

The Advanced administration handbook is created and maintained in collaboration with the Hosting team. To contribute to the handbook you can contact either the Documentation or Hosting team. The handbook covers APIs and best practices for administrating and maintaining hosting servers as well as WordPress installation. You can read more about the role here. 

The Documentation team handbook

The Documentation team handbook covers contribution processes, including descriptions for all these roles. Keeping it up to date is crucial for smooth onboarding processes and a satisfying contributor experience. You can read more about the role here. 

If nothing from our lists describes you, please contact us directly in the Slack channel and we'll find something for you. We will!

First, make sure you have all the accounts necessary. You don't have to do this now, we'll send you an email with all this info.

• WordPress.org account.
• WordPress Slack account (wordpress.org account is needed).
• GitHub account – connect your GitHub account to your WordPress.org profile.