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:
Documentation Issue Tracker on GitHub: Submit any Documentation Team-related issues on GitHubGitHubGitHub 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.
To get the most out of contributions, get recognition for contributions and help the team as much as possible, contributors working on projects are advised to closely collaborate with representative for the project. This is the best way to avoid working on something that is not priority or maybe won’t even be used in documentation.
All contributors have earned their Contributor badges by performing these contributions. Badges are manually added so if you have contributed to the Documentation team but don’t have one, please contact one of the team reps. Read more about the Documentation team profile badges.
A Project rep is a person who takes responsibility for the Documentation team’s projects, in parts or in whole.
This means that this person is a go-to person for all new contributors on the project. Also, a rep is monitoring progress of the project, or its parts, and reports on it during team meetings.
One person can be rep for one or more projects but also can be rep for one project and contributor for others. There is no limit to the number of reps per project. The more people take responsibility, the less pressure on one person there is.
Representative is a team member; one performing the role has both Documentation badges, contributor and team.
Monitor and perform work on GitHub issues for their project.
Guide contributors who want to help with the project.
Update project documentation based on completed work in GitHubGitHubGitHub 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.
Create a list of contributors who should receive Contributor profile badges and post it at the Documentation team meetings – Project updates agenda item.
Organise work on the project (priorities, good first issues etc) and develop a plan for improving the project if room is found. Always keeping the interest of the documentation users as the top priority.
All Project reps have earned their Team badges by performing these contributions. Badges are manually added so if you have contributed to the Documentation team but don’t have one, please contact one of the team reps. Read more about the Documentation team profile badges.
Team RepTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. is a leadership role that is mostly administrative in nature; it is not a Lead role. Letting go of the Team Rep title is not a loss of status, just a handing off of responsibilities. Someone who is a leader in a team can lead whether they are doing the team rep job or not. […] The primary Team Rep is responsible for posting a weekly update of the team’s activity to the make.wordpress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//updates blog, as well as raising any issues or red flags that other teams should be aware of or discussing.