Welcome to the official home of the WordPress Documentation Team.

This team is responsible for coordinating all documentation initiatives around WordPress, including the handbooks and other general wordsmithing across the WordPress project.

Want to get involved?

Start here to find out more about what we do and how to contribute:

Onboarding to Documentation Team: An overview of what we do and how to collaborate
Documentation Issue Tracker on GitHub: Submit any Documentation Team-related issues on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/

Weekly meetings

Join our discussions of documentation issues here on the blog and on Slack.

The documentation team holds weekly office hours and monthly Contributor Days on each Tuesday of the month in the #docs SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. It’s also where you can contact the team at any time outside meetings.

Home / Docs Handbook / Get Involved / Team roles / Project based / End-user roles

End-user roles

End-user documentation roles:

General documentation
Block editor documentation
Feedback curator

General end-user documentation

Project code name: HelpHub
Project URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org: https://wordpress.org/documentation/
Project GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ issues label: user documentation
Project GitHub issues URL: user documentation

Responsibilities

Work on end-user documentation issues in the Issue Tracker repo, whether it’s creating a new page or just fixing a part of an existing one.
Report on progress at the Documentation team meetings – Project updates agenda item.

How do I do this job?

Look for issues labelled with user documentation label.
Communicate with General end-user docs project reps for any clarifications on the tasks and review of your work. All questions can be asked in the actual GitHub issue, by pinging any of the project reps.
Updating the documentation page/article is usually done by one of the project reps or active contributors who have access to the dashboard where end-user documentation lives. Consistent contribution over time allows project reps to get to know you and gain trust in you, which can result in giving you access to the dashboard for updating the pages after the review is completed and content approved.
Report on your progress at the Documentation team meetings – Project updates agenda item.

Recommended onboarding sessions

Top ↑

Block editor end-user documentation

Project code name: HelpHub
Project URL: https://wordpress.org/documentation/article/blocks-list/
Project GitHub issues labels: user documentation, block editor
Project GitHub issues URL: user documentation + block editor

Responsibilities

Work on blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor end-user documentation issues in the Issue Tracker repo, whether it’s creating a new page or just fixing a part of an existing one.
Report on progress at the Documentation team meetings – Project updates agenda item.

How do I do this job?

Look for issues labelled with user documentation and block editor labels.
Communicate with Block editor end user docs project reps for any clarifications on the tasks and review of your work. All questions can be asked in the actual GitHub issue, by pinging any of the project reps.
Updating the documentation page/article is usually done by one of the project reps or active contributors who have access to the dashboard where end-user documentation lives. Consistent contribution over time allows project reps to get to know you and gain trust in you, which can result in giving you access to the dashboard for updating the pages after the review is completed and content approved.
Report on your progress at the Documentation team meetings – Project updates agenda item.

Recommended onboarding sessions

Top ↑

Feedback curator

Project code name: HelpHub
Project URL: https://wordpress.org/documentation/wp-admin/edit-comments.php
Project GitHub issues labels: user documentation, block editor
Project GitHub issues URL: user documentation, block editor, any of the version labels

Responsibilities

Regularly check on new Feedback (comments) being submitted to End user documentation, triage and create issues for them at the Issue Tracker repo.
Report on progress at the Documentation team meetings – Project updates agenda item.

How do I do this job?

Regularly check new feedback/comments at end-user documentation.
Delete spam and unrelated comments – anything that is not feedback on the actual article (good or bad).
Create an issue in the Issue Tracker repo. Use the HelpHub Feedback reports template.
The issue is automatically labelled with the HelpHub feedback label. Add user documentation label is applicable (At this moment, in April 2023, we still have content that will be redirected to Advanced Administration Handbook. For such content, the label should be advanced administration). If applicable add a block editor and any of the version labels. Labelling issues is important because some of the labels will send issues to appropriate GitHub projects via GitHub workflows.
Report on your progress at the Documentation team meetings – Project updates agenda item.

Recommended onboarding sessions

Last updated: April 28, 2023