Summary of Docs Team Meeting on 11th November

Housekeeping

• Where: #docs  channel on Slack
• When: Tuesday, November 11, 2025 at 07:30 PM GMT+5:30
• Meeting Facilitator: @milana_cap
• Note Taker: @ritikaroy2830

Find the complete Transcript of the meeting on Slack.

Next meeting:

1. Where: #docs channel on Slack
2. When: Tuesday, November 18, 2025 at 07:30 PM GMT+5:30
   Participants and Their Contributions:
   @milana_cap
   1. Facilitated the meeting, welcomed @ritikaroy2830, and shared onboarding resources:
   Onboarding Sessions for Documentation Team
   2. Provided the meeting notes format template:
   Summary of Docs Team meeting Nov 4, 2025
   3. Led project updates, discussed contributor rewards, and explained documentation review roles (First and Second Reviewer).
   4. Closed 4 documentation issues for version 6.8, stating only one left:
   GitHub Issue Tracker.
   5. Announced planned GitHubGitHub GitHub 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/ automation for review checklists and notifications.
   6. Clarified roles for HelpHub, DevHub, Handbook, and GutenbergGutenberg The 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/ releases documentation.
   7. Guided policy updates for documentation responsibilities on Themes and Plugins handbooks.
   8. Summarised action items: updating reviewing roles, renaming review roles, implementing GitHub automations, and updating the CONTRIBUTING documentation.
   9. Proposed automating replies for documentation issues outside Docs’ scope.
   10. Suggested a triage role for new and open issues classification.
   @atachibana
   Shared experience leading the Docs table at WordCampWordCamp WordCamps 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. Kansai and translation work. Confirmed willingness to continue as second reviewer for HelpHub.
   @Azhar Deraiya
   Reminded team about submitting contributions via the contributions form on the Docs blog sidebarSidebar A 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.:
   Make WordPress Documentation
   Encouraged contributor submissions for badge assignments.
   @Arslan
   Led Contributor DayContributor Day Contributor 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/. and Docs Table at WordCamp Islamabad 2025; submitted contributions through the contributions form.
   @estelaris
   1. Discussed project responsibilities and defined roles within Docs projects.
   2. Proposed detailed roles for first and second reviewers with checklist requirements.
   3. Emphasised task distribution for efficiency.
   4. Agreed on policy directing off-scope handbook issues to respective teams.
   5. Highlighted the need to update HelpHub and DevHub roles with detailed responsibilities, including issue review and closure.
   6. Recommended asking draft writers for changes when necessary.
   @MosesCursor
   Supported having experienced reviewers fill roles to maintain consistency.
   
   Main Points Discussed in the Meeting:
   1. Documentation roles are clearly defined with reference to team roles:
   Docs team roles
   2. Two-tier review system agreed upon:
   3. First Reviewer: Checks grammar, structure, style, screenshots, with guides:
   Grammar Guide,
   Writing Tips,
   Tone and Voice Guide
   4. Second Reviewer: Fact-checking and final approval.
   5. GitHub automation planned for checklist reminders and review label notifications.
   6. Policy updates to clarify the Docs team’s scope and proper handling of documentation issues for Themes and Plugins.
   7. Expanded HelpHub and DevHub roles to include issue review, documentation updates, and closure.
   8. Proposal for an issues triage role to handle new and open issues.
   9. Checklist to be created for reviewers detailing responsibilities.
   The End 🙂
   
   

#docs, #meeting, #summary