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.
Documentation for WP 7.1 is being updated, some comments:
@awetz583 has several articles for review. Thank you @atachibana for reviewing and closing them
the Zoom out view has been completed in order to close out the 6.8 tasks
There are several experimental issues which shouldn’t have documentation until they are finalized and in coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.. @estelaris to open 7.2 project and add these there to keep track of them. Including real-time collaboration.
TextControl – 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 Handbook
Issue reported on Slack by @flexseth: the component is essentially deprecated and a pretty significant interface (the text input) when making plugins and blocks for GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc.
https://wordpress.org/gutenberg/. The SEO links you to a deprecated component and there’s not a very clear redirect to the supported component.
In previous meetings, docs members were interested in using AI skills to help with documentation maintenance but there was not a final decision on how skills could be helpful. There were some suggestions during this meeting and @coreyhall93 will look into it.
A previous discussion about how inaccurate AI can be in writing documentation and how human writing and manual review should still be a priority.
@estelaris agrees with that sentiment and reminded the team that in previous meetings we agreed to write a note to the article whenever using AI to write it, something in the terms of “written by AI, reviewed by human”
Some ideas for the use of skills:
grammar & typos
that an article follows a template (what is it, what problem it resolves, how can I use it) – we can refine this
create ALT text for images & videos
help in closing issues instead of opening new ones
AI review before final human review, especially in new articles
an AI summary – work within the conversational context to see the checklist – what was needed vs. what was completed.
Overhaul of blocks
There are still 40 open issues, work needs to continue as we need to move to another section of the documentation overhaul.
The WordPress version changelog has also changed as of WordPress release 7.0: the list of wordpress packages is no longer specifically updated for each release. Instead, each release will include a note with more information where available.
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. article advanced settings update
The Advanced Settings section on individual block pages now links to a page of shared advanced settings to improve maintainability. Block-specific settings will continue to appear on their respective block pages. See issue #2287.
If you attended any Documentation team meeting in the past few years, you already met her. If you asked any question in #docsSlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ channel, there’s a high chance she gave you the answer. If you wanted to start contributing to the Docs team, she has probably onboarded you.
Estela has been an integral part of the Documentation team for years. She created and maintained collaboration with many other teams, she made sure the WordPress documentation is now at documentation.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/ subdomain, she documented WordPress releases and did many, many other things for the team and documentation.
We are extremely happy that she accepted our proposal to join the co-rep position for the Documentation team, and welcome her with open arms and hearts.
The documentation team needs help, especially from coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress., themes, and support contributors. As part of an overhaul, the Documentation Team has triaged and labeled nearly 800 issues in 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/ documentation issue tracker, closing 200 so far. Many of the open issues belong to your teams. Find your area below, then:
Close stale issues that are no longer relevant, or comment “Close this” if you don’t have access
Comment with corrections or updated information when you spot something wrong
If possible, draft doc changes and comment with markdown or a link to your draft
If you have permissions to close issues or update docs directly, even better. If not, your comments are exactly what’s needed to help the docs team take action.
Questions? 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 in #docs on SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
7.0 documentation and other projects
Besides the overhaul, the docs team is focusing on WordPress 7.0 documentation and a revision of the handbook to include the recommendations given by @rossanatrujillo, a student from the WPCredits program.
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://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!
Recorded 3 short videos for documenting the 7.0 release and uploaded them to wordpress.tv (these will be available soon.)
Created a Github project for 7.0 Documentation, added automation with 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/ workflow to add issues with 7.0 label automatically and added access to release team to the project.
@rollybueno Completing working on 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. overhaul including Quote block and Code block.
@estelaris proposed changes to the WordPress release day workflows, including reversing the order of the WordPress Versions page to show the latest version first, removing the Roadmap page from the team’s responsibilities, and updating the History and “Learn about WordPress origins and version history” pages. The team discussed the challenges and potential solutions, including exploring automation and using Contributor Days for manual updates.
@milana_cap proposed switching some of the team’s meetings to video calls, as video discussions tend to be more productive than Slack-only meetings. The team decided to add additional video calls to the monthly schedule.
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.
The Documentation team’s leadership has asked Jenni McKinnon to step away from the team.
Recent changes in the structure of the WordPress release squad started a discussion about the role of the Documentation team in documenting the release. While the team was working with the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. team, the release squad, and Mary Hubbard to find a solution for this and future releases, Jenni posted comments that were out of alignment with the team, including calls for broad changes across the project and requests to remove certain members from leadership roles.
This ran counter to the Documentation team’s intentions. Docs leadership reached out privately in an effort to de-escalate the situation and asked Jenni to stop posting such comments, but this behaviour did not stop. As a result, the team has decided to ask her to step away for a period of time to reassess her involvement. We will work with her to explore rejoining the team in the future, if it aligns with the best outcomes for both her and the team.
As a team, we apologise to the community and to the individuals mentioned for any inconvenience these comments have caused. These do not reflect the views of the Documentation team, and we are committed to ensuring that they are not perceived as such.
The Documentation Team holds an online, monthly Contributor Day on the fourth Tuesday of every month. Any one may join who wishes to contribute to the team and who follows the Code of Conduct.
Please also see the ongoing Contributor Day post 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/ for onboarding and other important details.
Onboarding
In addition to the details in the GitHub issue for this Contributor Day, folks who are in need of onboarding can ask 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/ or on the video call.
If at any time you have any questions, please feel free to ask in the #docs channel on Slack or on the video call throughout the day.
To all contributors
To every contributor and attendee: Thank you. We’re so grateful for your time, care, and dedication. Cookies 🍪🍪🍪 and kudos all around! While no token of appreciation could ever match the depth of your impact on the WordPress project and our community, we hope you know just how seen, valued, and celebrated you truly are – even when words fall short.
We may not be able to thank you enough today – but maybe one day we can, because we’re part of an incredible community that can make it happen. Whatever “it” is, we’ll do it. Together.
The release team is experimenting with a smaller team with the goal to reduce the overhead on the Release Squad.
” This streamlined structure places more emphasis on collaboration with the various Make Team Reps, who are encouraged to help coordinate efforts from within their respective teams. The goal is to reduce the overhead on the Release Squad while still ensuring each team’s contributions and priorities are represented throughout the cycle.” as explained in the Announcement the WordPress 6.9 Release Squad
The release team does not include representation from the documentation team. Why is this a problem? Because often documentation gets overlooked in release planning and project-wide coordination: Documentation is not a “nice-to-have,” it is a survival requirement. It’s not something we might do if someone has time; it’s something we must do — or the whole thing breaks down at scale. Removing the role from the release squad, we are not just sending the message that documentation is not important, we are showing new contributors that working on docs will never get them to the top of the credits page, therefore showing that we don’t even appreciate contributing to the Docs.
To support the smaller release team experiment, we agreed with @4thhubbard to compromise on having a Docs Liaison for this release. But this needs to be rethought on every release. Docs needs a structure/inclusion in future releases which should be a lead.
The feedback from the docs team so far on the experiment is the lack of communication from the release team and the perception that Releases are only open to coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. team members.
For now, we will not give access to the docs site to core committers who are not members of the docs team. @audrasjb@desrosj@jeffpaul@johnbillion@peterwilsoncc@poena and @sergeybiryukov currently have access and this will not be revoked. We can revisit this discussion after the experiment of a reduced release squad.
For short, not everyone is willing to understand and follow thru with the full process and pages remain incomplete, like this or this.
Documentation team lead role in past releases
In past releases, the documentation team lead has been given to anyone that asks for, even when they are not members of the documentation team. The results have been a mix of good and bad. There are two reasons, one is because of the misunderstanding of what the role is; and two, because the contributor chosen is not a member of the team thus they are unfamiliar with documentation.
Since 6.8, we have worked on updating sections in the core handbook related to documentation. Yet, the Role of the Documentation team lead is incomplete. Beginning with the Documentation Wrangling title, “wrangling” should not be on the title as it reads like the team only “wrangles” dev docs. It is also missing reference to the user documentation, whether is updating old articles or writing new ones for new released features.
The actual documentation process
This is a summary, the articles are linked for further explanation.
Open a project 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/ – Documentation Issue Tracker, example from 6.8
In this project, DevNotes and User docs are tracked.
DevNotes are written by core committers or whoever has been involved in a feature. User docs are written by the docs team members.
Who creates the lists? DevNotes list is created by either the release tech lead or the release docs lead. User docs list is written by the release docs lead.
Both DevNotes and User docs should be written during the release cycle. Although, there is never enough time and both lists can be incomplete by the end of the release cycle. Docs team continues working on user docs. Any missing devnote is only updated if requested.
When the release cycle ends, the docs team focuses on updating or writing new user documentation articles. The work is tracked in the GH documentation issue tracker for both, user docs and developer docs.
