Category Archives: Uncategorized

Andrea Roenning 6:29 pm on March 3, 2026
Tags: , ,   

Documentation team meeting notes – March 3, 2026

Where: #docs channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
When: Tuesday, March 3, 2026, 14:00 UTC
Meeting Facilitator: @milana_cap
Note Taker: @awetz583
Find the complete meeting on Slack.

Next Meetings

Discussion Meeting

Where: #docs channel on Slack
When: Tuesday, March 10 2026, 14:00 UTC
Facilitator: @estelaris

Discussion Meeting

Where: #docs channel on Slack + Video call
When: Tuesday, March 17 2026, 14:00 UTC

View upcoming dates on the Documentation Team meeting calendar.

Facilitation Resources

Helpful resources for facilitating the meeting and writing the meeting notes.

Project Checks: Contributions

  • @awetz583 Worked on Video block, Verse block, Image block, and File block which are ready for review.
  • @milana_cap
    • Completed and closed Pullquote block and List block.
    • 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 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/ workflow to add issues with 7.0 label automatically and added access to release team to the project.
  • @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 and Code block.
  • @supernovia Contribution Pathways is now on Github and will continue to receive updates.
  • @parinpanjari Working on updates for Get started with WP article.

The team is now down to 657 open issues, with 28 issues closed in the past week.

Documenting WordPress 7.0 release

@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 asked the team to review the documentation review process and @estelaris and @milana_cap plan to provide feedback.

Switching to Video Meetings

@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:

#docs, #meeting, #summary

Milana Cap 6:37 pm on February 25, 2026
Tags: , ,   

Documentation team meeting notes – February 24, 2026

Where: #docs channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
When: Tuesday, February 24 2026, 14:00 UTC
Meeting Facilitator: @supernovia
Note Taker: @milana_cap
Find the complete meeting on Slack.

Next Meetings

Discussion Meeting

Where: #docs channel on Slack
When: Tuesday, March 3 2026, 14:00 UTC
Facilitator: @supernovia
Note Taker: @azharderaiya

Discussion Meeting

Where: #docs channel on Slack
When: Tuesday, March 10 2026, 14:00 UTC
Facilitator: @estelaris

Facilitation Resources

Helpful resources for facilitating the meeting and writing the meeting notes.

Project Checks: Contributions

The team is now down to 683 open issues, with 5 issues closed in the past week.

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. 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/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

The Documentation team is missing the table lead for the WordCamp Asia Contributor Day. The team has been discussing possible leads from the list of registered attendees: @sagargurnani, @anandau14, as possible table leads, with help from @bph and @clk87.

Documenting WordPress 7.0 release

With the smaller release squad, the Docs team has two representatives volunteered to work on updating end-user docs for 7.0, @sajib1223 and @milana_cap. The team will follow instructions drafted by @estelaris, while working on this new workflow together with @annezazu on 6.9 release. In this scenario, @milana_cap will act as a mentor due to her experience with working on release docs in previous releases. As the others expressed the interest, this will be done publicly (in the #docs channel), starting from next week.

A very helpful resource is provided by @annezazu in the comment on the planning post for 7.0.

Open Floor

Contribution Pathways

@supernovia noted that, by WordCamp Asia, we should have several contribution pathways ready. These will be moved to 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/ and available to new contributors at Contributor Day. @estelaris shared the general GitHub issue the team uses for Contributor Days.

Previously, @supernovia shared three “contribution pathway” one-pagers created by @clk87:

Goals for these guides:

  • Provide clear, step-by-step entry points for new and existing contributors.
  • Eventually be linked from the main contribution index (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 shared the draft about the AI-powered documentation assistant for WordPress core blocks (draft) that she will be working on with the #core-ai team, and hopefully will be ready for 7.1 It will be trained to give recommendations based on existing 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, #meeting, #summary

supernovia 5:40 am on February 24, 2026
Tags: , ,   

Agenda for Discussion Meeting on February 24, 2026

The meeting is scheduled with the following details:

When: Tuesday, February 24, 2026, 14:00 UTC

Where: #docs channel on Slack

Agenda:

  1. Attendance.
  2. Note-taker and facilitator selection for the next docs team meeting.
  3. Project check.
  4. Prepping for 7.0
  5. Open floor.

If there’s anything you’d like to discuss on the open floor, please leave a comment.

#agenda, #docs, #meetings
supernovia 11:12 pm on February 17, 2026
Tags: , ,   

Documentation team meeting notes – February 17, 2026

Where: #docs channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
When: Tuesday, February 17, 2026 at 14:00 UTC
Meeting Facilitator: @sagargurnani
Note Taker: @supernovia
Find the complete meeting on Slack.

Next Meetings

Discussion Meeting

Where: #docs channel on Slack
When: Tuesday, March 3, 2026 at 14:00 UTC
Facilitator: @supernovia
Note Taker: @azharderaiya

Discussion Meeting

Where: #docs channel on Slack
When: Monday, March 10, 2026 at 14:00 UTC
Facilitator: @estelaris

Next Meeting Volunteers & Facilitation Resources

After a request for facilitators and note-takers for the March 3 meeting, @supernovia agreed to facilitate, and @azharderaiya will take notes. This will be the first time for each of them in these roles, so @zzap shared these guides:

@zzap also noted that the team no longer keeps a roll-call style attendance list in meeting notes, and @sagargurnani will connect with @azharderaiya privately to help guide him through the note-taking process.

Project Checks: Contributions

The team is now down to 689 open issues, with 64 issues closed in the past week alone. @zzap and @estelaris both thanked everyone for their hard work, with special recognition for those working on the blocks overhaul.

Open Floor

Handling Old & Deprecated Issues

@estelaris raised a question: since the inventory work is surfacing very old issues (6.3 and older), should issues for blocks that have already been updated to 6.9 be closed?

Decision:

  • Yes — close them, referencing the newer issue number where applicable.
  • Exception: If a feature was introduced in an old version and was never documented in later updates, keep it open.
  • For deprecated blocks with broken images from old versions: remove the broken image from the article and close the issue with a comment noting the 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: @estelaris shared that @rossanatrujillo, her mentee from the WP Credits program, is reviewing the Docs handbook in both Spanish and English and has submitted her first draft for review:

  • Google Doc — Handbook Review Draft
  • Anyone is welcome to read and leave notes. The first part is in Spanish, the second in English.
  • The goal is for this review to help update the handbook.

@estelaris expressed appreciation for the program, noting that mentoring is a mutual learning experience around best approaches, goals, and reasons behind handbook content.

Contribution Pathways

@supernovia shared three “contribution pathway” one-pagers created by @clk87:

Goals for these guides:

  • Provide clear, step-by-step entry points for new and existing contributors.
  • Eventually be linked from the main contribution index (final location still to be decided).
  • Support a growing pool of 200+ student contributors looking for ways to contribute, with more students coming.

@zzap thanked the team for this work and plans to review the documents and possibly adapt them for the Docs gamification initiative.

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/ Automations, /assign, and Workflow Improvements

@awetz583 reported another instance where /assign failed to assign an issue in GitHub.

@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. There are many edge cases that can’t be covered, or are too expensive to run because GitHub would need to process all issues. The automations are good for getting things started but need refining and/or re-doing. @zzap expressed openness to revisiting these workflows and @clk87 may be able to assist with this effort.

@supernovia raised a related question: can contributors be unassigned if they self-assign and then abandon an issue?

Current situation:

  • No automatic unassigning for inactivity.
  • Admins can manually unassign people from issues.
  • If someone uses /assign on an already assigned issue, they receive an automated notice advising them to contact @zzap.

Review Process

@supernovia asked whether anyone can review issues, or if a certain status is required first — and whether allowing broader reviews could help clear the backlog.

  • @zzap noted it’s difficult to give a blanket answer; it depends on what is being reviewed and what needs attention.
  • @estelaris confirmed that anyone can review, and that the team will be reviewing more often now that systems are getting back in order.
  • @supernovia suggested the idea of a preliminary review step.
  • @estelaris explained that related issues are being gathered together, with the goal of updating as much as possible up to 6.9 so the team is ready for 7.0.

Action Items

  • For any /assign misbehavior, 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 directly.
  • Revisit and possibly redesign current workflows and automations.
  • @clk87 may be able to help with automation improvements.
  • Work through the backlog of abandoned or stalled issues.
  • @sagargurnani to connect with @azharderaiya to guide him through note-taking.
  • @zzap to review @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‘s handbook draft (ES) and leave feedback.

#docs, #meeting, #summary

Estela Rueda 2:05 pm on December 2, 2025  

Proposal to change the user documentation workflow

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 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/ project template contains 13 status columns, intended to reflect multiple review stages before publishing on WordPress.orgWordPress.org The 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 CoreCore Core 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 revisionsRevisions The 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.

Key improvements shown by the new workflow

BeforeAfter
Multiple review bottlenecksStreamlined review — optional pre-release
Work stored in Google DocsWork completed directly in WordPress
Delayed publishingRelease-day publication
Articles often outdated before launchQuick updates post-launch
Large backlog that rarely clearsContinuous improvement, smaller backlog

Milana Cap 9:35 am on September 19, 2025  

The stepping away of a team member

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 CoreCore Core 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 reps: @kenshino, @atachibana, and @milana_cap.

Milana Cap 9:46 am on August 5, 2025  

The Documentation team meetings summer break

Due to low meeting attendance and a lack of topics to discuss, the Documentation team has decided to take a summer break from meetings, which will take effect in August. The team will continue to contribute and communicate asynchronously in the Slack channel.

During August, the primary focus for the team will be on preparing for the use of AI in documentation processes, building a system for gamifying contributions, and completing as many issues as possible from past WordPress releases.

If you have any questions, please feel free to post them here in the comment section or the SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. Other than taking a break from meetings, business is as usual for the team.

The next meeting will happen on Tuesday, 2nd September 2025, 2PM UTC.

Akira Tachibana 2:20 pm on August 3, 2025
Tags: ,   

Summary of Docs Team meeting July 29, 2025

Attendance

@milana_cap, @atachibana, @azharderaiya, @jadavsanjay, @dhruvang, @areziaal, @nikunj8866, @vasantrajput, @areziaal, @estelaris, @Mosescursor, @rollybueno, @ravigadhiyawp, @dilip2615

Housekeeping

Find the complete Transcript of the meeting on Slack.

Open floor

Reminder to Proposal

Responsible AI workflow for creating new documentation for WordPress 6.9
@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, #summary

Milana Cap 10:01 am on April 29, 2025  

Summary for Discussion Meeting (29 April 2025)

Attendance

@milana_cap @nikunj8866 @azharderaiya @karthickmurugan @zluck @divyeshk71 @devmuhib @ravigadhiyawp @Sumit Singh @kafleg @Zeel Thakkar @Dhruvang21 @Parth @noruzzaman

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meetings

Please notice the new meeting timings below.

Project Checks

@milana_cap created issues for 6.8, is reviewing 6.8 issues.

@karthickmurugan also worked on 6.8 issues.

Open floor

Q: I want to know how to contribute in docs

A: Here we have a bunch of onboarding videos: https://make.wordpress.org/docs/2022/06/13/live-onboarding-sessions-for-the-documentation-team/. And here’s the “Get involved” chapter in our Handbook: https://make.wordpress.org/docs/handbook/get-involved/. Do take a look and if you still have any questions, do not hesitate to ask in #docs channel.

Sagar Gurnani 9:12 am on April 20, 2025  

Summary for Discussion Meeting (15-Apr-2025)

Attendance

@milana_cap @sagargurnani @utsav72640 @nikunj8866 @azharderaiya @flexseth @karthickmurugan @estelaris @n8finch (async)

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meetings

Please notice the new meeting timings below.

Project Checks

@milana_cap created issues for 6.8, is reviewing 6.8 issues and she is also scheduling updates for articles which should be published soon. She also published an article – “What’s new for developers?“.

@atachibana is reviewing and working on issues associated to the older WP versions like 6.3.

@nikunj8866 contributed to the #1894 issue.

Open Floor

@estelaris is getting ready for 6.8 release. She also mentions that during a release, the docs team updates 2 pages in HelpHub.

  1. WP Versions
  2. And the version page itself, see 6.7 as an example

Then these 2 other pages are also updated. we need permission to access them because the updates are manually done then they have to be pushed via WordPress sandbox (WP.org‘s backend).

  1. Roadmap
  2. History

She would be adding the above process to the handbook soon.

@flexseth asked whether it is still the best practice to install the the repo locally, then create a PR for submitting changes to the developer.wordpress.org? What’s the best way to submit simple fixes and also contribute code samples?

To which @milana_cap replied that if he wants to contribute to the installation itself, that’s #meta and he needs to install it locally. But, if he wants to contribute code samples, he just needs to submit the user notes to reference and someone will review and publish it from #core.