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.
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).
Regular meeting with agenda published on our blog.
Issues triage where we discuss issues from 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/ repository.
Live onboarding sessions
We recorded onboarding sessions for everyone interested in getting started with the Documentation team. We know that our “Getting started” documentation is out of date and getting involved can be very confusing and frustrating so we hope to ease the process with these sessions.
Developer documentation – PluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. handbook
Developer documentation – 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
Changes to existing documents will be drafted in Gitlab issues. For new features, we can create new pages ahead of time if we leave them in draft.
New blocks in 7.0 that will need new documentation pages:
Breadcrumbs 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.
Icon block
@aialvi will be working on adding updates to issues identified 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/
It would be nice to have a full list of which blocks exist in the block editor. We have access to the block code in GitHub but not all of the blocks are currently active and not all are user-facing.
Documentation in some of the sections in the spreadsheet such as WP Overview @estelaris and @milana_cap will update due to access and background in the project. @estelaris has access to edit the tooltips for keywords that are driven by the glossaries.
Dev Hub Issues
The documentation team needs Help closing DevHub issues. Please close anything related to missing documentation that was created when the parser was run.
How to get documentation badges?
@estelaris will look into the new process and ensure those who helped at 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 will receive WordPress.org documentation profile badges.
@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.
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.
