Title: summary – Make WordPress Documentation --- # Tag Archives: summary [ ](https://profiles.wordpress.org/awetz583/) [Andrea Roenning](https://profiles.wordpress.org/awetz583/) 7:53 pm _on_ April 7, 2026 Tags: [docs ( 150 )](https://make.wordpress.org/docs/tag/docs/), [meeting ( 20 )](https://make.wordpress.org/docs/tag/meeting/), summary    # 󠀁[Documentation team meeting notes – April 7, 2026](https://make.wordpress.org/docs/2026/04/07/documentation-team-meeting-notes-april-7-2026/)󠁿 **Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) ** When:** [Tuesday, April 7, 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260407T1400)** Meeting Facilitator:** [@estelaris](https://profiles.wordpress.org/estelaris/)** Note Taker:** [@awetz583](https://profiles.wordpress.org/awetz583/)Find the complete meeting [on Slack.](https://wordpress.slack.com/archives/C02RP4WU5/p1773756150749509) ## Next Meetings ### Planning Meeting **Where**: [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack + Video call **When**: [Tuesday, April 14, 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260414T1400) ### Discussion Meeting **Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack ** When:** [Tuesday, April 21, 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260421T1400) [View upcoming dates on the Documentation Team meeting calendar.](https://make.wordpress.org/meetings/#docs) ## Updates ### Blocks articles overhaul * [@estelaris](https://profiles.wordpress.org/estelaris/) compiled open issues related to blocks and features [into a spreadsheet](https://docs.google.com/spreadsheets/d/1KxjFLh98pY00VdpRK8zSqDpLiHtetpcl9SUgrOTAQ_g/edit?gid=0#gid=0) for the Blocks Overhaul Project. She finished labeling, reviewing the 26 pages of issues in 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 by the repository owner. [https://github.com/](https://github.com/) and closed issues that were resolved or repeated. * [@awetz583](https://profiles.wordpress.org/awetz583/) is working on updates to the [Buttons Block page](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2096). * [@supernovia](https://profiles.wordpress.org/supernovia/) made [changes to the Docs Handbook](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2205). ### Issue label discussion 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](https://make.wordpress.org/docs/handbook/github-repository-and-projects/documentation-issue-tracker/). ### Advanced Admin & DevHub issue tracking planning [@estelaris](https://profiles.wordpress.org/estelaris/) discussed the need for someone to focus on the [DevHub](https://github.com/WordPress/Documentation-Issue-Tracker/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22developer%20documentation%20(DevHub)%22) and [Advanced Admin](https://github.com/WordPress/Documentation-Issue-Tracker/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22advanced%20administration%22) areas. * 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 coreCore Core 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 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](https://central.wordcamp.org/about/). Europe on June 4th. [#docs](https://make.wordpress.org/docs/tag/docs/), [#meeting](https://make.wordpress.org/docs/tag/meeting/), [#summary](https://make.wordpress.org/docs/tag/summary/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F04%2F07%2Fdocumentation-team-meeting-notes-april-7-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/awetz583/) [Andrea Roenning](https://profiles.wordpress.org/awetz583/) 5:53 pm _on_ March 17, 2026 Tags: [docs ( 150 )](https://make.wordpress.org/docs/tag/docs/), [meeting ( 20 )](https://make.wordpress.org/docs/tag/meeting/), summary    # 󠀁[Documentation team meeting notes – March 17, 2026](https://make.wordpress.org/docs/2026/03/17/documentation-team-meeting-notes-march-17-2026/)󠁿 **Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) ** When:** [Tuesday, March 17, 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260317T1400)** Meeting Facilitator:** [@milana_cap](https://profiles.wordpress.org/milana_cap/)** Note Taker:** [@awetz583](https://profiles.wordpress.org/awetz583/)Find the complete meeting [on Slack.](https://wordpress.slack.com/archives/C02RP4WU5/p1773756150749509) ## Next Meetings ### 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/](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://2017.us.wordcamp.org/contributor-day/)󠁿 󠀁[https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/)󠁿 **Where**: [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack + Video call **When**: [Tuesday, March 24 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260324T1400) ### Discussion Meeting **Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack ** When:** [Tuesday, March 31 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260331T1400) [View upcoming dates on the Documentation Team meeting calendar.](https://make.wordpress.org/meetings/#docs) ## Updates ### Preparing for 7.0 Documentation [@milana_cap](https://profiles.wordpress.org/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. * [Create GH project](https://wordpress.tv/2026/03/08/documenting-wordpress-release-create-github-project/) * [GitHub automation](https://wordpress.tv/2026/03/09/documenting-wordpress-release-github-automation/) * [GH project access](https://wordpress.tv/2026/03/09/documenting-wordpress-release-manage-github-project-access/) [@sajib1223](https://profiles.wordpress.org/sajib1223/) confirmed he has watched the videos and will join the meeting to start working on the green list items. ### Blocks articles overhaul [@awetz583](https://profiles.wordpress.org/awetz583/) is working on updates to Media& Text blockBlock Block 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](https://github.com/orgs/WordPress/projects/267/views/1). ### Good first issues [@supernovia](https://profiles.wordpress.org/supernovia/) asked about the status of Good First Issues, and [@milana_cap](https://profiles.wordpress.org/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](https://profiles.wordpress.org/supernovia/) and [@milana_cap](https://profiles.wordpress.org/milana_cap/) discussed [moving the pathways work to GitHub](https://github.com/WordPress/contributor-handbook/tree/feature/pathways), 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](https://profiles.wordpress.org/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](https://profiles.wordpress.org/milana_cap/) mentioned that she will be available for 2 hours during the upcoming Contributor Day at [Tuesday, March 31 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260331T1400), and there will be no formal meeting notes or facilitators, just focused contribution time. [#docs](https://make.wordpress.org/docs/tag/docs/), [#meeting](https://make.wordpress.org/docs/tag/meeting/), [#summary](https://make.wordpress.org/docs/tag/summary/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F03%2F17%2Fdocumentation-team-meeting-notes-march-17-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/awetz583/) [Andrea Roenning](https://profiles.wordpress.org/awetz583/) 2:58 pm _on_ March 10, 2026 Tags: [docs ( 150 )](https://make.wordpress.org/docs/tag/docs/), [meeting ( 20 )](https://make.wordpress.org/docs/tag/meeting/), summary    # 󠀁[Documentation team meeting notes – March 10, 2026](https://make.wordpress.org/docs/2026/03/10/documentation-team-meeting-notes-march-10-2026/)󠁿 **Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) + Video call **When:** [Tuesday, March 10, 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260310T1400)** Meeting Facilitator:** [@estelaris](https://profiles.wordpress.org/estelaris/)** Note Taker:** [@awetz583](https://profiles.wordpress.org/awetz583/) # Next Meetings ### Discussion Meeting **Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack ** When:** [Tuesday, March 17 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260317T1400) ### 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/](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://2017.us.wordcamp.org/contributor-day/)󠁿 󠀁[https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/)󠁿 **Where**: [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack + Video call **When**: [Tuesday, March 24 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260324T1400) [View upcoming dates on the Documentation Team meeting calendar.](https://make.wordpress.org/meetings/#docs) ## Open Floor * [@parinpanjari](https://profiles.wordpress.org/parinpanjari/) discussed updating an image for [Get Started with WordPress](https://wordpress.org/documentation/article/get-started-with-wordpress/) documentation * [@estelaris](https://profiles.wordpress.org/estelaris/) and [@awetz583](https://profiles.wordpress.org/awetz583/) discussed documentation ready for review in the [Blocks articles overhaul project board](https://github.com/orgs/WordPress/projects/267) [#docs](https://make.wordpress.org/docs/tag/docs/), [#meeting](https://make.wordpress.org/docs/tag/meeting/), [#summary](https://make.wordpress.org/docs/tag/summary/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F03%2F10%2Fdocumentation-team-meeting-notes-march-10-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/awetz583/) [Andrea Roenning](https://profiles.wordpress.org/awetz583/) 6:29 pm _on_ March 3, 2026 Tags: [docs ( 150 )](https://make.wordpress.org/docs/tag/docs/), [meeting ( 20 )](https://make.wordpress.org/docs/tag/meeting/), summary    # 󠀁[Documentation team meeting notes – March 3, 2026](https://make.wordpress.org/docs/2026/03/03/documentation-team-meeting-notes-march-3-2026/)󠁿 **Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) ** When:** [Tuesday, March 3, 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260303T1400)** Meeting Facilitator:** [@milana_cap](https://profiles.wordpress.org/milana_cap/)** Note Taker:** [@awetz583](https://profiles.wordpress.org/awetz583/)Find the complete meeting [on Slack](https://wordpress.slack.com/archives/C02RP4WU5/p1772546760576869). # Next Meetings ### Discussion Meeting **Where**: [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack + Video call **When**: [Tuesday, March 10 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260310T1400)** Facilitator**: [@estelaris](https://profiles.wordpress.org/estelaris/) ### Discussion Meeting **Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack ** When:** [Tuesday, March 17 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260317T1400) [View upcoming dates on the Documentation Team meeting calendar.](https://make.wordpress.org/meetings/#docs) ### Facilitation Resources Helpful resources for facilitating the meeting and writing the meeting notes. * [Non-project roles → **Meeting facilitator**](https://make.wordpress.org/docs/handbook/get-involved/team-roles/non-project-roles/#meeting-facilitator) * [Facilitating weekly meetings](https://make.wordpress.org/docs/handbook/workflows/facilitating-weekly-meetings/) workflow page, including the [writing agenda](https://make.wordpress.org/docs/handbook/workflows/facilitating-weekly-meetings/#writing-agenda) section. ## Project Checks: Contributions * [@awetz583](https://profiles.wordpress.org/awetz583/) Worked on [Video block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2157), [Verse block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2140), [Image block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2151), and [File block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2155) which are ready for review. * [@milana_cap](https://profiles.wordpress.org/milana_cap/) - Completed and closed [Pullquote block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2138) and [List block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2132). - 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](https://github.com/orgs/WordPress/projects/286), added automation with 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 by the repository owner. [https://github.com/](https://github.com/) workflow to add issues with 7.0 label automatically and added access to release team to the project. * [@rollybueno](https://profiles.wordpress.org/rollybueno/) Completing working on blockBlock Block 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](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2133) and [Code block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2134). * [@supernovia](https://profiles.wordpress.org/supernovia/) [Contribution Pathways is now on Github](https://github.com/WordPress/contributor-handbook/blob/feature/pathways/pathways/index.md) and will continue to receive updates. * [@parinpanjari](https://profiles.wordpress.org/parinpanjari/) Working on updates for [Get started with WP](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2184) article. The team is now **down to 657 open issues**, with [28 issues closed in the past week](https://github.com/WordPress/Documentation-Issue-Tracker/pulse). ## Documenting WordPress 7.0 release [@estelaris](https://profiles.wordpress.org/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. ## Open Floor ### Reviewing the Documentation Review Process [@supernovia](https://profiles.wordpress.org/supernovia/) asked the team to review the [documentation review process](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.9qo6qd7g64ww#heading=h.ndba4wg45kgd) and [@estelaris](https://profiles.wordpress.org/estelaris/) and [@milana_cap](https://profiles.wordpress.org/milana_cap/) plan to provide feedback. ### Switching to Video Meetings [@milana_cap](https://profiles.wordpress.org/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. #### New schema for docs meetings: * 1st in month – Slack chat * 2nd in month – Video call * 3rd in month – Slack chat * 4th in month – 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/](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://2017.us.wordcamp.org/contributor-day/) [https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/)( video) * 5th in month – Video call [#docs](https://make.wordpress.org/docs/tag/docs/), [#meeting](https://make.wordpress.org/docs/tag/meeting/), [#summary](https://make.wordpress.org/docs/tag/summary/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F03%2F03%2Fdocumentation-team-meeting-notes-march-3-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/milana_cap/) [Milana Cap](https://profiles.wordpress.org/milana_cap/) 6:37 pm _on_ February 25, 2026 Tags: [docs ( 150 )](https://make.wordpress.org/docs/tag/docs/), [meeting ( 20 )](https://make.wordpress.org/docs/tag/meeting/), summary    # 󠀁[Documentation team meeting notes – February 24, 2026](https://make.wordpress.org/docs/2026/02/25/documentation-team-meeting-notes-february-24-2026/)󠁿 **Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) ** When:** [Tuesday, February 24 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260224T1400)** Meeting Facilitator:** [@supernovia](https://profiles.wordpress.org/supernovia/)** Note Taker:** [@milana_cap](https://profiles.wordpress.org/milana_cap/)Find the complete meeting [on Slack](https://wordpress.slack.com/archives/C02RP4WU5/p1771941622625369). # Next Meetings ### Discussion Meeting **Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack ** When:** [Tuesday, March 3 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260303T1400)** Facilitator:** [@supernovia](https://profiles.wordpress.org/supernovia/)**Note Taker:** [@azharderaiya](https://profiles.wordpress.org/azharderaiya/) ### Discussion Meeting **Where**: [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack ** When**: [Tuesday, March 10 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260310T1400)** Facilitator**: [@estelaris](https://profiles.wordpress.org/estelaris/) ### Facilitation Resources Helpful resources for facilitating the meeting and writing the meeting notes. * [Non-project roles → **Meeting facilitator**](https://make.wordpress.org/docs/handbook/get-involved/team-roles/non-project-roles/#meeting-facilitator) * [Facilitating weekly meetings](https://make.wordpress.org/docs/handbook/workflows/facilitating-weekly-meetings/) workflow page, including the [writing agenda](https://make.wordpress.org/docs/handbook/workflows/facilitating-weekly-meetings/#writing-agenda) section. ## Project Checks: Contributions * [@milana_cap](https://profiles.wordpress.org/milana_cap/)**:** Almost done with issue [#2138](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2138)( recording video is remaining). Plans to complete another issue this week. * [@awetz583](https://profiles.wordpress.org/awetz583/): Worked on [Details block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2135) and [Table block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2139), which are ready for review. The team is now **down to 683 open issues**, with [5 issues closed in the past week](https://github.com/WordPress/Documentation-Issue-Tracker/pulse). ## 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](https://central.wordcamp.org/about/)󠁿. Asia 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/](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://2017.us.wordcamp.org/contributor-day/)󠁿 󠀁[https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-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](https://wordpress.slack.com/archives/C02RP4WU5/p1771942589577359) possible leads from the list of registered attendees: [@sagargurnani](https://profiles.wordpress.org/sagargurnani/), [@anandau14](https://profiles.wordpress.org/anandau14/), as possible table leads, with help from [@bph](https://profiles.wordpress.org/bph/) and [@clk87](https://profiles.wordpress.org/clk87/). ## Documenting WordPress 7.0 release With the smaller [release squad](https://make.wordpress.org/core/2026/01/22/announcing-the-wordpress-7-0-release-squad/), the Docs team has two representatives volunteered to work on updating end-user docs for 7.0, [@sajib1223](https://profiles.wordpress.org/sajib1223/) and [@milana_cap](https://profiles.wordpress.org/milana_cap/). The team will follow [instructions](https://docs.google.com/document/d/1SoUds02wiBCjmPJR5xu_GdbnkQfyCGn_spYtugebpcM/edit?tab=t.0) drafted by [@estelaris](https://profiles.wordpress.org/estelaris/), while working on this new workflow together with [@annezazu](https://profiles.wordpress.org/annezazu/) on 6.9 release. In this scenario, [@milana_cap](https://profiles.wordpress.org/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](https://make.wordpress.org/docs/tag/docs/) channel), starting from next week. A very helpful resource is provided by [@annezazu](https://profiles.wordpress.org/annezazu/) in [the comment](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#comment-48392) on the planning post for 7.0. ## Open Floor ### Contribution Pathways [@supernovia](https://profiles.wordpress.org/supernovia/) noted that, by WordCamp Asia, we should have several contribution pathways ready. These will be moved to 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 by the repository owner. [https://github.com/](https://github.com/) and available to new contributors at Contributor Day. [@estelaris](https://profiles.wordpress.org/estelaris/) shared the [general GitHub issue](https://github.com/WordPress/Documentation-Issue-Tracker/issues/1920) the team uses for Contributor Days. Previously, [@supernovia](https://profiles.wordpress.org/supernovia/) shared three“ contribution pathway” one-pagers created by [@clk87](https://profiles.wordpress.org/clk87/): * **[Reviewing an Issue](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.9qo6qd7g64ww)**— for more advanced contributors; needs critique and correction before publishing. * **[Work on Existing Issues](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.ikn705tefvek)**— ready to publish pending final review. * **[File High Quality Issues](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.9e580h1eicew)**— ready to publish pending final review. **Goals for these guides:** * Provide clear, step-by-step entry points for new and existing contributors. * Eventually be linked from the [main contribution index](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.398bqf8dq2ro)( final location still to be decided). * Support a growing pool of **200+ student contributors** looking for ways to contribute, with more students coming. ## AI-powered documentation assistant for WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks [@estelaris](https://profiles.wordpress.org/estelaris/) shared the draft about the [AI-powered documentation assistant for WordPress core blocks (draft)](https://docs.google.com/document/d/14ws7j5r_iiH3b9PNIRrzZiNbxJcsTE8eEOMfklziYyU/edit?usp=sharing) that she will be working on with the [#core-ai](https://wordpress.slack.com/archives/C08TJ8BPULS) team, and hopefully will be ready for 7.1 It will be trained to give recommendations based on existing blockBlock Block 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. [#docs](https://make.wordpress.org/docs/tag/docs/), [#meeting](https://make.wordpress.org/docs/tag/meeting/), [#summary](https://make.wordpress.org/docs/tag/summary/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F02%2F25%2Fdocumentation-team-meeting-notes-february-24-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/supernovia/) [Velda](https://profiles.wordpress.org/supernovia/) 11:12 pm _on_ February 17, 2026 Tags: [docs ( 150 )](https://make.wordpress.org/docs/tag/docs/), [meeting ( 20 )](https://make.wordpress.org/docs/tag/meeting/), summary    # 󠀁[Documentation team meeting notes – February 17, 2026](https://make.wordpress.org/docs/2026/02/17/documentation-team-meeting-notes-february-17-2026/)󠁿 **Where:** [#docs](https://make.wordpress.org/docs/tag/docs/) channel on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) ** When:** Tuesday, February 17, 2026 at 14:00 UTC**Meeting Facilitator:** [@sagargurnani](https://profiles.wordpress.org/sagargurnani/)** Note Taker:** [@supernovia](https://profiles.wordpress.org/supernovia/)Find the complete meeting [on Slack](https://wordpress.slack.com/archives/C02RP4WU5/p1771336973646589). # Next Meetings ### Discussion Meeting **Where:** [#docs](https://make.wordpress.org/docs/tag/docs/) channel on Slack ** When:** Tuesday, March 3, 2026 at 14:00 UTC**Facilitator:** [@supernovia](https://profiles.wordpress.org/supernovia/)** Note Taker:** [@azharderaiya](https://profiles.wordpress.org/azharderaiya/) ### Discussion Meeting Where: [#docs](https://make.wordpress.org/docs/tag/docs/) channel on Slack When: Monday, March 10, 2026 at 14:00 UTC**Facilitator:** [@estelaris](https://profiles.wordpress.org/estelaris/) ### Next Meeting Volunteers & Facilitation Resources After a request for facilitators and note-takers for the March 3 meeting, [@supernovia](https://profiles.wordpress.org/supernovia/) agreed to facilitate, and [@azharderaiya](https://profiles.wordpress.org/azharderaiya/) will take notes. This will be the first time for each of them in these roles, so [@zzap](https://profiles.wordpress.org/zzap/) shared these guides: * [Non-project roles → **Meeting facilitator**](https://make.wordpress.org/docs/handbook/get-involved/team-roles/non-project-roles/#meeting-facilitator) * [Facilitating weekly meetings](https://make.wordpress.org/docs/handbook/workflows/facilitating-weekly-meetings/) workflow page, including the [writing agenda](https://make.wordpress.org/docs/handbook/workflows/facilitating-weekly-meetings/#writing-agenda) section. [@zzap](https://profiles.wordpress.org/zzap/) also noted that the team **no longer keeps a roll-call style attendance list** in meeting notes, and [@sagargurnani](https://profiles.wordpress.org/sagargurnani/) will connect with [@azharderaiya](https://profiles.wordpress.org/azharderaiya/) privately to help guide him through the note-taking process. ## Project Checks: Contributions * **[@zzap](https://profiles.wordpress.org/zzap/):** Almost done with issue [#2138](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2138)( recording video is remaining). Plans to complete another issue this week. * **[@awetz583](https://profiles.wordpress.org/awetz583/):** Closed three issues: [Classic block (#2141)](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2141), [Paragraph block(#2129)](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2129), and [Preformatted block (#2137)](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2137) * **[@estelaris](https://profiles.wordpress.org/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. * **[@atachibana](https://profiles.wordpress.org/atachibana/):** Closed 2 issues for WordPress 6.2. * **`@sajib1223`**: Closed 2 issues and 1 spam issue: [#2186](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2186), [#2160](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2160) * **[@rollybueno](https://profiles.wordpress.org/rollybueno/):** Closed the [Heading Block Overhaul (#2131](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2131)) and its sub-tasks, plus 1 spam issue. The team is now **down to 689 open issues**, with 64 issues closed in the past week alone. [@zzap](https://profiles.wordpress.org/zzap/) and [@estelaris](https://profiles.wordpress.org/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](https://profiles.wordpress.org/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 blockBlock Block 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](https://profiles.wordpress.org/rossanatrujillo/):** [@estelaris](https://profiles.wordpress.org/estelaris/) shared that [@rossanatrujillo](https://profiles.wordpress.org/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: * [Google Doc — Handbook Review Draft](https://docs.google.com/document/d/1ixhpmZXX_GNAjzbWJyYnknEO64zsRvmgBMG3-DqvFgY/edit?usp=sharing) * 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](https://profiles.wordpress.org/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](https://profiles.wordpress.org/supernovia/) shared three “contribution pathway” one-pagers created by [@clk87](https://profiles.wordpress.org/clk87/): * **[Reviewing an Issue](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.9qo6qd7g64ww)**— for more advanced contributors; needs critique and correction before publishing. * **[Work on Existing Issues](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.ikn705tefvek)**— ready to publish pending final review. * **[File High Quality Issues](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.9e580h1eicew)**— ready to publish pending final review. **Goals for these guides:** * Provide clear, step-by-step entry points for new and existing contributors. * Eventually be linked from the [main contribution index](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.398bqf8dq2ro)( final location still to be decided). * Support a growing pool of **200+ student contributors** looking for ways to contribute, with more students coming. [@zzap](https://profiles.wordpress.org/zzap/) thanked the team for this work and plans to review the documents and possibly adapt them for the Docs **gamification** initiative. ### 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 by the repository owner. 󠀁[https://github.com/](https://github.com/)󠁿 Automations, /assign, and Workflow Improvements [@awetz583](https://profiles.wordpress.org/awetz583/) reported another instance where `/assign` failed to assign an issue in GitHub. [@zzap](https://profiles.wordpress.org/zzap/) clarified that `/assign` can fail when: * Someone is already assigned to the issue, **or** * The issue has a status label other than “To do.” All current automations (including `/assign` behaviors) are custom-built by [@zzap](https://profiles.wordpress.org/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](https://profiles.wordpress.org/zzap/) expressed openness to revisiting these workflows and [@clk87](https://profiles.wordpress.org/clk87/) may be able to assist with this effort. [@supernovia](https://profiles.wordpress.org/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](https://profiles.wordpress.org/zzap/). #### Review Process [@supernovia](https://profiles.wordpress.org/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](https://profiles.wordpress.org/zzap/) noted it’s difficult to give a blanket answer; it depends on what is being reviewed and what needs attention. * [@estelaris](https://profiles.wordpress.org/estelaris/) confirmed that **anyone can review**, and that the team will be reviewing more often now that systems are getting back in order. * [@supernovia](https://profiles.wordpress.org/supernovia/) suggested the idea of a **preliminary review** step. * [@estelaris](https://profiles.wordpress.org/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, pingPing The 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](https://profiles.wordpress.org/zzap/) directly. * Revisit and possibly redesign current workflows and automations. * [@clk87](https://profiles.wordpress.org/clk87/) may be able to help with automation improvements. * Work through the backlog of abandoned or stalled issues. * [@sagargurnani](https://profiles.wordpress.org/sagargurnani/) to connect with [@azharderaiya](https://profiles.wordpress.org/azharderaiya/) to guide him through note-taking. * [@zzap](https://profiles.wordpress.org/zzap/) to review [@clk87](https://profiles.wordpress.org/clk87/)‘ s contribution pathway documents and explore gamification integration. * Team to revisit assignment/abandonment workflows and work through the backlog of stalled issues. * Anyone interested is welcome to review [@rossanatrujillo](https://profiles.wordpress.org/rossanatrujillo/)‘ s [handbook draft](https://docs.google.com/document/d/1ixhpmZXX_GNAjzbWJyYnknEO64zsRvmgBMG3-DqvFgY/edit?usp=sharing)( ES) and leave feedback. [#docs](https://make.wordpress.org/docs/tag/docs/), [#meeting](https://make.wordpress.org/docs/tag/meeting/), [#summary](https://make.wordpress.org/docs/tag/summary/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F02%2F17%2Fdocumentation-team-meeting-notes-february-17-2026%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/ritikaroy2830/) [Ritika Roy](https://profiles.wordpress.org/ritikaroy2830/) 8:29 am _on_ November 13, 2025 Tags: [docs ( 150 )](https://make.wordpress.org/docs/tag/docs/), [meeting ( 20 )](https://make.wordpress.org/docs/tag/meeting/), summary    # 󠀁[Summary of Docs Team Meeting on 11th November](https://make.wordpress.org/docs/2025/11/13/summary-of-docs-team-meeting-on-11th-november/)󠁿 ## **Housekeeping** * Where: [#docs](https://wordpress.slack.com/archives/C02RP4WU5/p1746522044589239) channel on [Slack](https://make.wordpress.org/chat/) * When: [Tuesday, November 11, 2025 at 07:30 PM GMT+5:30](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20251104T1500) * Meeting Facilitator: [@milana_cap](https://profiles.wordpress.org/milana_cap/) * Note Taker: [@ritikaroy2830](https://profiles.wordpress.org/ritikaroy2830/) _Find the complete [Transcript ](https://wordpress.slack.com/archives/C02RP4WU5/p1762869617307809) of the meeting on _[_Slack_](https://make.wordpress.org/chat/)_._ Next meeting: 1. Where: [#docs](https://wordpress.slack.com/messages/docs/) channel on [Slack](http://www.slack.com/) 2. When: [Tuesday, November 18, 2025 at 07:30 PM GMT+5:30](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20251111T1400) ** Participants and Their Contributions:**[@milana_cap](https://profiles.wordpress.org/milana_cap/) 1. Facilitated the meeting, welcomed @[ritikaroy2830,](https://profiles.wordpress.org/ritikaroy2830/) and shared onboarding resources:[Onboarding Sessions for Documentation Team](https://make.wordpress.org/docs/2022/06/13/live-onboarding-sessions-for-the-documentation-team/) 2. Provided the meeting notes format template:[Summary of Docs Team meeting Nov 4, 2025](https://make.wordpress.org/docs/2025/11/04/summary-of-docs-team-meeting-november-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](https://github.com/WordPress/Documentation-Issue-Tracker/issues?q=is%3Aopen%20is%3Aissue%20label%3A%226.8%22). 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 by the repository owner. [https://github.com/](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/](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**](https://profiles.wordpress.org/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](https://central.wordcamp.org/about/). Kansai and translation work. Confirmed willingness to continue as second reviewer for HelpHub.[@**Azhar Deraiya**](https://profiles.wordpress.org/azharderaiya/)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](https://make.wordpress.org/docs/) 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/](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://2017.us.wordcamp.org/contributor-day/) [https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-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](https://profiles.wordpress.org/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**](https://profiles.wordpress.org/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](https://make.wordpress.org/docs/handbook/get-involved/team-roles/)2. Two- tier review system agreed upon:3. First Reviewer: Checks grammar, structure, style, screenshots, with guides:[Grammar Guide](https://make.wordpress.org/docs/handbook/documentation-team-handbook/handbooks-grammar-guide/),[Writing Tips](https://make.wordpress.org/docs/handbook/get-involved/writing-tips/),[Tone and Voice Guide](https://make.wordpress.org/docs/handbook/documentation-team-handbook/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](https://make.wordpress.org/docs/tag/docs/), [#meeting](https://make.wordpress.org/docs/tag/meeting/), [#summary](https://make.wordpress.org/docs/tag/summary/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2025%2F11%2F13%2Fsummary-of-docs-team-meeting-on-11th-november%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/milana_cap/) [Milana Cap](https://profiles.wordpress.org/milana_cap/) 4:05 pm _on_ November 4, 2025 Tags: [docs ( 150 )](https://make.wordpress.org/docs/tag/docs/), summary    # 󠀁[Summary of Docs Team meeting November 4, 2025](https://make.wordpress.org/docs/2025/11/04/summary-of-docs-team-meeting-november-4-2025/)󠁿 ## **Housekeeping** * Where: [#docs](https://wordpress.slack.com/archives/C02RP4WU5/p1746522044589239) channel on [Slack](https://make.wordpress.org/chat/) * When: [Tuesday, 04 November 2025, 3PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20251104T1500) * Meeting Facilitator: [@milana_cap](https://profiles.wordpress.org/milana_cap/) * Note Taker: **AI** 🤩 _Find the complete [Transcript](https://wordpress.slack.com/archives/C02RP4WU5/p1762268448170989) of the meeting on _[_Slack_](https://make.wordpress.org/chat/)_._ Next meeting: * Where: [#docs](https://wordpress.slack.com/messages/docs/) channel on [Slack](http://www.slack.com/) * When: [Tuesday, 11 November 2025, 2PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20251111T1400) ### **1. Meeting Time Confusion** * The meeting began one hour later than planned due to daylight saving time changes. * **Action:** - [@milana_cap](https://profiles.wordpress.org/milana_cap/) will update the [global calendar](https://make.wordpress.org/meetings/) to reflect the new time. ### **2. Contributor Recognition Initiative** * Discussion focused on improving recognition for contributions and clarifying the process for tracking them. * Reference post: [Rethinking Contributor Recognition in Documentation Team](https://make.wordpress.org/docs/2025/11/04/rethinking-contributor-recognition-in-documentation-team/). * A new **contribution form** was introduced to capture contributions not recorded anywhere else. - **Demo shared:** [Slack thread + video demo](https://wordpress.slack.com/archives/C02RP4WU5/p1761312844268409). * **Proposal:** - Contributors to submit their activities every week via the form. - Meeting leads will collect and announce the contributions during the meeting. - Weekly contributor badges will be issued and announced. - Contributions will be gamified: each submission earns points and titles, contributing to a leaderboard. * **Action:** - Contributors are asked to submit their contributions via the form. - [@milana_cap](https://profiles.wordpress.org/milana_cap/) to publish a detailed post explaining the recognition workflow and gamification proposal. ### **3. Regular vs. Release Contributions (led by 󠀁[@estelaris](https://profiles.wordpress.org/estelaris/)󠁿)** * Continuing previous discussions around defining _regular_ and _release_ contributions. * **Regular contributions** include: - Attending meetings, writing up meeting notes, or leading meetings. - Attending contributor days (e.g., 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](https://central.wordcamp.org/about/)., MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through [https://www.meetup.com/](https://www.meetup.com/). A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area., external events). - Submitting issues to update documentation articles. - **Note:** Fixing typos is important but does not count as a regular _meaningful_ contribution. * **Release contributions** refer to tasks related to specific WordPress version releases (e.g., the current 6.9 release). These contributions include: - Creating and managing project repositories (e.g., WP 6.9 documentation). - Updating articles, submitting new screenshots, reviewing documentation. - For developer docs, interacting with the release team, ensuring devnotes are documented (though not writing them). - ). * **Discussion around devnotes:** - Currently, responsibilities for devnotes are unclear and need to be revisited after the 6.9 release. * **Action:** Clarify and document the specifics of release contributions after the 6.9 release. ### **4. Conclusion & Next Steps** * **Action items:** - All contributors should submit their contributions using the form on the Docs blog. - The team will review feedback and questions over the next week. - A follow-up discussion about contributions will take place in the next meeting. * **Next Meeting:** - **Date:** November 11, 2025 - **Time:** 14:00 UTC (new time due to daylight saving time). [#docs](https://make.wordpress.org/docs/tag/docs/), [#summary](https://make.wordpress.org/docs/tag/summary/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2025%2F11%2F04%2Fsummary-of-docs-team-meeting-november-4-2025%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/ninianepress/) [Jenni McKinnon](https://profiles.wordpress.org/ninianepress/) 3:01 pm _on_ September 16, 2025 Tags: [docs ( 150 )](https://make.wordpress.org/docs/tag/docs/), [meetings ( 169 )](https://make.wordpress.org/docs/tag/meetings/), summary    # 󠀁[Summary of Docs Team meeting September 9, 2025](https://make.wordpress.org/docs/2025/09/16/summary-of-docs-team-meeting-septermber-9-2025/)󠁿 ## Attendance [@estelaris](https://profiles.wordpress.org/estelaris/), [@milana_cap](https://profiles.wordpress.org/milana_cap/), [@ninianepress](https://profiles.wordpress.org/ninianepress/), [@sagargurnani](https://profiles.wordpress.org/sagargurnani/), [@jdy68](https://profiles.wordpress.org/jdy68/) ## **Housekeeping** * Where: [#docs](https://wordpress.slack.com/archives/C02RP4WU5/p1746522044589239) channel on [Slack](https://make.wordpress.org/chat/) * When: [Tuesday, September 9, 2025, 2:00 PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250909T1400) * Meeting Facilitator: [@ninianepress](https://profiles.wordpress.org/ninianepress/) * Note Taker: [@ninianepress](https://profiles.wordpress.org/ninianepress/) _Find the complete [Transcript](https://wordpress.slack.com/archives/C02RP4WU5/p1757426411202299) of the meeting on _[_Slack_](https://make.wordpress.org/chat/)_._ ## Upcoming meetings * **Docs Team planning meeting** - Where: [#docs](https://wordpress.slack.com/messages/docs/) channel on [Slack](http://www.slack.com/) - When: [Tuesday, August 16, 2025, 2:00 PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250819T1400) - Facilitator: [@milana_cap](https://profiles.wordpress.org/milana_cap/) * **[Online monthly Contributor Day](https://make.wordpress.org/docs/2025/09/18/online-monthly-docs-team-contributor-day-september-23-2025/)** - Where:  [#docs](https://wordpress.slack.com/messages/docs/) channel on [Slack](http://www.slack.com/) and [Google Meet](https://make.wordpress.org/docs/2025/09/18/online-monthly-docs-team-contributor-day-september-23-2025/) - When: [Tuesday, September 23, 2025, 2:00 PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250923T1400) for 3 hours - Facilitator: [@ninianepress](https://profiles.wordpress.org/ninianepress/) ## Open floor [@estelaris](https://profiles.wordpress.org/estelaris/) shared these updates about the next release, which was discussed: 1. “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is experimenting with a smaller release team to avoid pitfalls. The experiment will be re-evaluated after this release. 2. There seems to be no need to have docs team as a named lead in releases, I argued the importance that it has to us, mainly we want to mentor other contributors and releases are like an “extra” benefit for the team. 3. Also, the release team needs to plan better so they can ask us for someone to update the HelpHub pages – known to us as the [WP version pages](https://wordpress.org/documentation/article/wordpress-versions/) For releases, Mary recommended that we name a **Docs Liaison** person that will commit to update in documentation anything related to the releases (User documentation, WP version pages, etc.). Docs will not be in charge of wrangling/writing any **DevHub** articles related to releases. Updating issues that are posted in the Docs Issue Tracker is still on the balance, as I found out that many core committers had no clue that issues were reported to us, so they don’t update anything util someone from docs reports the issue on TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.[https://core.trac.wordpress.org/](https://core.trac.wordpress.org/).. And the biggest issue that we need to decide is the updating of the WP version pages. The last 3 minor releases, I have done it. 1 time I was asked when the release was being planned and the other 2 times, at the last minute. So I mentioned that we need to plan better and find a way to work together and create a process that works for both teams. The response from core is that we give access to all core committers so they can update the WordPress version pages, that is a list of [40 people](https://docs.google.com/spreadsheets/d/1e6hfydL-JtRp2uQEPCJmq3Eh31VZLS65eAeAqCUXq9E/edit?usp=sharing). And I said I wasn’t comfortable in giving access to everyone, perhaps a few, my reasons the version pages are in the same site as the rest of the documentation and the docs team is in charge of maintaining the version pages also. Giving access to everyone, means we will be called less and less to help on releases or anything else. Here is the [chat to the main conversation](https://wordpress.slack.com/archives/C02RQBWTW/p1756914956446299).” [#docs](https://make.wordpress.org/docs/tag/docs/), [#meetings](https://make.wordpress.org/docs/tag/meetings/), [#summary](https://make.wordpress.org/docs/tag/summary/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2025%2F09%2F16%2Fsummary-of-docs-team-meeting-septermber-9-2025%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/atachibana/) [Akira Tachibana](https://profiles.wordpress.org/atachibana/) 2:20 pm _on_ August 3, 2025 Tags: [meetings ( 169 )](https://make.wordpress.org/docs/tag/meetings/), summary    # 󠀁[Summary of Docs Team meeting July 29, 2025](https://make.wordpress.org/docs/2025/08/03/summary-of-docs-team-meeting-july-29-2025/)󠁿 ## Attendance [@milana_cap](https://profiles.wordpress.org/milana_cap/), [@atachibana](https://profiles.wordpress.org/atachibana/), [@azharderaiya](https://profiles.wordpress.org/azharderaiya/), [@jadavsanjay](https://profiles.wordpress.org/jadavsanjay/), [@dhruvang](https://profiles.wordpress.org/dhruvang/), [@areziaal](https://profiles.wordpress.org/areziaal/), [@nikunj8866](https://profiles.wordpress.org/nikunj8866/), [@vasantrajput](https://profiles.wordpress.org/vasantrajput/), [@areziaal](https://profiles.wordpress.org/areziaal/), [@estelaris](https://profiles.wordpress.org/estelaris/), [@Mosescursor](https://profiles.wordpress.org/mosescursor/), [@rollybueno](https://profiles.wordpress.org/rollybueno/), [@ravigadhiyawp](https://profiles.wordpress.org/ravigadhiyawp/), [@dilip2615](https://profiles.wordpress.org/dilip2615/) ## **Housekeeping** * Where: [#docs](https://wordpress.slack.com/archives/C02RP4WU5/p1746522044589239) channel on [Slack](https://make.wordpress.org/chat/) * When: [Tuesday, July 29, 2025, 2:00 PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250729T1400) * Meeting Facilitator: [@milana_cap](https://profiles.wordpress.org/milana_cap/) * Note Taker: [@atachibana](https://profiles.wordpress.org/atachibana/) _Find the complete _[_Transcript_](https://wordpress.slack.com/archives/C02RP4WU5/p1753797649913719)_ of the meeting on _[_Slack_](https://make.wordpress.org/chat/)_._ ## Open floor ### Reminder to Proposal [Responsible AI workflow for creating new documentation for WordPress 6.9](https://make.wordpress.org/docs/2025/07/24/proposal-responsible-ai-workflow-for-creating-new-documentation-for-wordpress-6-9/) [@estelaris](https://profiles.wordpress.org/estelaris/) is working on the second part of that proposal so she can present it Mary. If anyone has any comment for the proposal, please leave them on the link. ### Summer break [Plan] Meetings will resume on September 2. This is the same as the winter break: no meetings, but feel free to contribute. [#meetings](https://make.wordpress.org/docs/tag/meetings/), [#summary](https://make.wordpress.org/docs/tag/summary/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2025%2F08%2F03%2Fsummary-of-docs-team-meeting-july-29-2025%2F%23respond&locale=en_US) # Post navigation [← Older posts](https://make.wordpress.org/docs/tag/summary/page/2/?output_format=md)