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 by the repository owner. https://github.com/
Weekly meetings
Join our discussions of documentation issues here on the blog and on Slack.
While writing and updating HelpHub articles for 6.9, the team discovered that many articles have not been updated making it difficult to maintain the quality of the documentation. For this reason, the team is incurring in an overhaul of the documentation with 3 main goals:
Improve the quality of the documentation.
Use the changelog to recognise contributors.
Update the blocks articles before WP 7.0 is released.
What is the overhaul and how it works
A project has been created 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 by the repository owner. https://github.com/ for each of the categories plus the blocks – see links below. In each categoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. there is a READ FIRST issue with instructions.
Basically, a new issue is open per blockBlockBlock 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./feature with the title “Overhaul XX block documentation”. Look at the related open issues, see what’s still useful, and close anything that’s ancient/irrelevant. For other details, follow the instructions in the READ FIRST article.
Key things to remember:
Self-assign the issue you decide to tackle.
Close those outdated issues! Don’t let them hang around.
Write your final updates in the comments first, before you update the actual article in WordPress.
Need to edit the docs site? PingPingThe act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.”@estelaris or @milana_cap for access.
Don’t forget the contributors! Add anyone who suggested something (even if you don’t use it) to the changelog. You only need to contribute once to become a Docs contributor!
If you can’t figure out a contributor’s WordPress username, just ask in the SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. docs channel.
Note: if there is only one issue open for a feature/block, only the title has been edited to add the word “Overhaul”. This is done to avoid extra issues and extra work.
The list of the overhaul projects in GitHub:
Note: the audit on the GH docs issue tracker is still happening, thus projects below will be updated as soon as possible.
@milana_cap informed the team that there will be a holiday break and docs team will reinitiate activities on the 13 of January 2026 at 14:00 UTC.
@milana_cap also let the team know that next year, there will be a new gamification contribution system, where contributors can collect points for every single contribution, from attending the meeting to writing articles, documenting releases and leading docs tables at Contributor Days. There will also be special titles, leader board, and points could be deducted. More information will be posted in the Make blog in January.
A new project to overhaul the blocks documentation is starting. The goal is to update the blockBlockBlock 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. articles before WP 7.0 is release and fix any outdated information, broken links, broken images, etc. Instructions will be up in the upcoming weeks. https://github.com/orgs/WordPress/projects/267/views/1
@tobifjellner, a global mentor for the polyglots teamPolyglots TeamPolyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. joined, he is interested in understanding the documentation workflow to continue the translation project. Docs contributors interested in translating documentation are invited to join the #polyglots-multilingual-community
Previous work has been done in the documentation translation project, read the notes from the last meeting in WCEU 2024 in Torino.
The workflow currently used by the Docs team to update user documentation is likely a key reason why documentation is often not ready by release day.
Current Workflow Overview
The 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 by the repository owner. https://github.com/ project template contains 13 status columns, intended to reflect multiple review stages before publishing on 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/. Some columns are used for Dev Notes, while others are for user documentation:
No Status
Unknown
To Do
In Progress
F.G. and Misc.
Needs 1st Review
Needs 1st Review (Peers)
Edits After 1st Review
Needs 2nd Review
Needs 2nd Review (Copy)
Reviewed: To Revise / Migrate
Ready to Publish: Make CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.
Done
Problems with the Current Workflow
Currently, once the Source of Truth article is available, contributors begin writing drafts—usually in Google Docs. These drafts often sit more than a week waiting for a first review. After revisionsRevisionsThe WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision., they then wait again for a second review.
Sometimes the second reviewer publishes the article in WordPress; other times, articles wait weeks longer, and by the time they are updated, the release has already shipped, forcing additional updates.
This process leads to:
A growing backlog of unfinished documentation,
articles being updated out of release order (e.g., 6.4 → 6.6 → 6.5), resulting in confusion,
inconsistent documentation when users report outdated content
Proposed Workflow Change
For WordPress 6.9, the HelpHub documentation was written directly in WordPress, scheduled for release day, without review waiting time.
To ensure accountability, issues were still created in GitHub to track both new and updated articles, and reviews should occur after publication.
Recommendations
Skip most review stages before release.
Form a small writing team dedicated to each release.
Reviews should be optional before publishing (if a reviewer is available.)
Schedule completed articles to publish on release day.
Perform a second review after publishing, correcting any issues as needed.
Simplify the GitHub project template to remove unnecessary review columns.
