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.
@estelaris compiled open issues related to blocks and features into a spreadsheet for the Blocks Overhaul Project. She finished labeling, reviewing the 26 pages of issues 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/ and closed issues that were resolved or repeated.
The team discussed removing the automatic “to-do” label on new issues in Github, as it did not provide value. The label process is currently outlined on the Documentation issue tracker page.
If a new page is requested and it now exists > close ticket
If a broken/missing link is reported > update link and close ticket
If a code review is requested > check if a solution has been provided. If not, add solution to ticket, test if you can and create PR for Advanced Admin. For Code Review, we may have to report to coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.
The Docs team goal is to close as many issues as possible before WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe on June 4th.
We’re excited to see you, collaborate, and reconnect in person at WordCamp Asia 2026in Mumbai, India. Events like this offer a unique opportunity for contributors across the Asia-Pacific region and beyond to gather, exchange experiences, and support each other in strengthening the WordPress project — both locally and on a global scale.
This year, WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia 2026 takes place in Mumbai, India, and will feature Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/, conference sessions, networking, and community-building activities. If you’re planning to attend, we’d love to see you at the Documentation Team table during Contributor Day!
Contributor Day is one of the most welcoming and energizing parts of any WordCamp. It’s a dedicated day for attendees to contribute to the WordPress open-source project by joining one of the many Make WordPress teams.
For the Documentation Team, Contributor Day is a chance to:
Welcome new contributors,
Reconnect with existing contributors,
Review and write WordPress documentation for end users and developers,
Review and write documentation for WordPress release 7.0
First time at Contributor Day? No prior experience is needed to get involved. The Documentation Team table is the perfect place to discover how the team operates, explore the different ways you can contribute, and find out how your skills and interests can make a meaningful impact within documentation.
Detailed Contributor Day Schedule
Location: Documentation Team Table, Lotus Hall, Jio World Convention Centre, Mumbai Date: April 9, 2026
08:00 am IST Registration Open and Networking Time
09:00 am IST – Opening Remarks 09:30 am IST – Family Photo 09:45 am IST – Contributing to WordPress/Workshop/Open-Source Library 10:00 am IST – The Making of a WordPress Release: Conversations with Past Release Squad Members
12:00 pm IST Long Break and Networking Time
01:45 pm IST – Table Leads Photo 02:00 pm IST – Contributing to WordPress/Workshop/Open-Source Library 04:30 pm IST – Closing Remarks
05:00 pm IST Contributor Day Wrap-up
What to Expect at The Documentation Team Table
At the Documentation Team table, participants may work on:
Onboarding new contributors,
Reviewing and updating documentation for coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks,
Reviewing and/or writing user documentation for WP 7.0 release
Table Leads
This year’s Contributor Day at WordCamp Asia, the Documentation Team will be led by @clk87 with both @bph and @rollybueno will help with the onboarding of new contributors.
If you have experience contributing to the Documentation Team, we would love to invite you to take part in the new initiative introduced by Contributor Day Team – Contributor Buddy.
Contributor Buddy is a new initiative that makes Contributor Day feel more approachable, especially for newcomers. Experienced contributors volunteer at team tables to help others understand how the team works, find beginner-friendly tasks, and get started with confidence.
If you are planning to join the Documentation Team and have previous contribution experience, simply reach out to @clk87 or @rollybueno and express your interest in becoming a Contributor Buddy. If appropriate, they will provide you with a Contributor Buddy badge.
Things to prepare before WC Asia
If this is your first time contributing to the Documentation team, please make sure you have the following accounts:
WordPress Slack account (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/ account is needed).
For general details on how 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/ works, check out GitHub’s Getting Started Guide.
For example, if your task is for 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. Editor End-User documentation, you would tag @atachibana.
Whether you are an experienced contributor or completely new to the WordPress project, we’d love to see you at the Community Team table during Contributor Day.
Come learn, contribute, connect, and help shape the future of WordPress communities.
Joining us in Mumbai? Stop by the Documentation Team table and be part of the conversation. Let’s build community together!
@milana_cap shared videos for preparing tools and workflows, and outlined the plan to update docs this week following a guideline and a list of items in “Good Progress/Ready” status.
@sajib1223 confirmed he has watched the videos and will join the meeting to start working on the green list items.
Blocks articles overhaul
@awetz583 is working on updates to Media & Text 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. documentation and has others ready for review on the Blocks articles overhaul board.
Good first issues
@supernovia asked about the status of Good First Issues, and @milana_cap mentioned that some can be closed while others need updating. They plan to review these during the upcoming Contributor Day.
Open Floor
Pathways and Handbook Updates
@supernovia and @milana_cap discussed moving the pathways work to GitHub, with the goal of keeping handbook pages as the detailed reference and the guides as checklists. They agreed this would make it easier for the community to contribute and review the content.
Handbook feedback
@estelaris raised an issue about a WP Credits student’s feedback on the handbook content, noting that some paragraphs read differently in Spanish compared to the English version. They requested help to compare the handbook content with the student’s suggestions and identify any areas that need improvement in the writing style.
Contributor Day Planning
@milana_cap mentioned that she will be available for 2 hours during the upcoming Contributor Day at Tuesday, March 31 2026, 14:00 UTC, and there will be no formal meeting notes or facilitators, just focused contribution time.
WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/
The Documentation team is missing the table lead for the WordCamp Asia Contributor Day. The team has been discussing possible leads from the list of registered attendees: @sagargurnani, @anandau14, as possible table leads, with help from @bph and @clk87.
Documenting WordPress 7.0 release
With the smaller release squad, the Docs team has two representatives volunteered to work on updating end-user docs for 7.0, @sajib1223 and @milana_cap. The team will follow instructions drafted by @estelaris, while working on this new workflow together with @annezazu on 6.9 release. In this scenario, @milana_cap will act as a mentor due to her experience with working on release docs in previous releases. As the others expressed the interest, this will be done publicly (in the #docs channel), starting from next week.
A very helpful resource is provided by @annezazu in the comment on the planning post for 7.0.
Open Floor
Contribution Pathways
@supernovia noted that, by WordCamp Asia, we should have several contribution pathways ready. These will be moved to 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/ and available to new contributors at Contributor Day. @estelaris shared the general GitHub issue the team uses for Contributor Days.
Previously, @supernovia shared three “contribution pathway” one-pagers created by @clk87:
Reviewing an Issue — for more advanced contributors; needs critique and correction before publishing.
Support a growing pool of 200+ student contributors looking for ways to contribute, with more students coming.
AI-powered documentation assistant for WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks
@estelaris shared the draft about the AI-powered documentation assistant for WordPress core blocks (draft) that she will be working on with the #core-ai team, and hopefully will be ready for 7.1 It will be trained to give recommendations based on existing 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. docs. This is one of the reasons why Overhaul has been pushed for the block docs to be updated.
Any comments, ideas, questions, and reviews for the draft are welcome. Please, leave them in the document.
Where:#docs channel on Slack When: Tuesday, March 3, 2026 at 14:00 UTC Facilitator:@supernovia Note Taker:@azharderaiya
Discussion Meeting
Where: #docs channel on Slack When: Monday, March 10, 2026 at 14:00 UTC Facilitator:@estelaris
Next Meeting Volunteers & Facilitation Resources
After a request for facilitators and note-takers for the March 3 meeting, @supernovia agreed to facilitate, and @azharderaiya will take notes. This will be the first time for each of them in these roles, so @zzap shared these guides:
@zzap also noted that the team no longer keeps a roll-call style attendance list in meeting notes, and @sagargurnani will connect with @azharderaiya privately to help guide him through the note-taking process.
Project Checks: Contributions
@zzap: Almost done with issue #2138 (recording video is remaining). Plans to complete another issue this week.
@estelaris: Closed 40+ issues for 6.4 dev notes. All work had been done previously but none of the issues were formally closed. Each was reviewed and missing links were added.
The team is now down to 689 open issues, with 64 issues closed in the past week alone. @zzap and @estelaris both thanked everyone for their hard work, with special recognition for those working on the blocks overhaul.
Open Floor
Handling Old & Deprecated Issues
@estelaris raised a question: since the inventory work is surfacing very old issues (6.3 and older), should issues for blocks that have already been updated to 6.9 be closed?
Decision:
Yes — close them, referencing the newer issue number where applicable.
Exception: If a feature was introduced in an old version and was never documented in later updates, keep it open.
For deprecated blocks with broken images from old versions: remove the broken image from the article and close the issue with a comment noting 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. was deprecated and will no longer be updated. Contributors are encouraged to follow this same approach when encountering similar issues.
WP Credits Program Updates
Handbook Review by @rossanatrujillo:@estelaris shared that @rossanatrujillo, her mentee from the WP Credits program, is reviewing the Docs handbook in both Spanish and English and has submitted her first draft for review:
Anyone is welcome to read and leave notes. The first part is in Spanish, the second in English.
The goal is for this review to help update the handbook.
@estelaris expressed appreciation for the program, noting that mentoring is a mutual learning experience around best approaches, goals, and reasons behind handbook content.
Contribution Pathways
@supernovia shared three “contribution pathway” one-pagers created by @clk87:
Reviewing an Issue — for more advanced contributors; needs critique and correction before publishing.
Support a growing pool of 200+ student contributors looking for ways to contribute, with more students coming.
@zzap thanked the team for this work and plans to review the documents and possibly adapt them for the Docs gamification initiative.
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/ Automations, /assign, and Workflow Improvements
@awetz583 reported another instance where /assign failed to assign an issue in GitHub.
All current automations (including /assign behaviors) are custom-built by @zzap. There are many edge cases that can’t be covered, or are too expensive to run because GitHub would need to process all issues. The automations are good for getting things started but need refining and/or re-doing. @zzap expressed openness to revisiting these workflows and @clk87 may be able to assist with this effort.
@supernovia raised a related question: can contributors be unassigned if they self-assign and then abandon an issue?
Current situation:
No automatic unassigning for inactivity.
Admins can manually unassign people from issues.
If someone uses /assign on an already assigned issue, they receive an automated notice advising them to contact @zzap.
Review Process
@supernovia asked whether anyone can review issues, or if a certain status is required first — and whether allowing broader reviews could help clear the backlog.
@zzap noted it’s difficult to give a blanket answer; it depends on what is being reviewed and what needs attention.
@estelaris confirmed that anyone can review, and that the team will be reviewing more often now that systems are getting back in order.
@supernovia suggested the idea of a preliminary review step.
@estelaris explained that related issues are being gathered together, with the goal of updating as much as possible up to 6.9 so the team is ready for 7.0.
Action Items
For any /assign misbehavior, 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.”@zzap directly.
Revisit and possibly redesign current workflows and automations.
@clk87 may be able to help with automation improvements.
Work through the backlog of abandoned or stalled issues.
The team is exploring the idea of contributors submitting their contributions via a form in the Docs team’s blog sidebarSidebarA sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.. However, as with any form, we are facing a lot of spam submissions. The workflow in SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ is another option, but only few in Slack can create those.
The team rewieved proposal draft and left valuable feedback. @supernovia noted that new contributors might feel intimidated by the low likelihood of “win”.
As the purpose of gamification is to encourage new contributors to start contributing, as well as trying out different ways of contributing to the Docs team, in order to find what suits them the best, the proposal is going to be modified as follows:
The most points will be added for “getting started” tasks,
Special bonus points will be added for doing the type of task for the first time,
Achievements will be reflected in 2 ways: total points and/or title pathway,
Once the contributor earns a team membership, competition stops for them, and they are considered to have reached the game finish line.
@estelaris offers her mentorship to anyone interested in becoming a team member ❤️
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.
