Summary of Docs Team meeting September 9, 2025

Attendance

@estelaris, @milana_cap, @ninianepress, @sagargurnani, @jdy68

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming meetings

Open floor

@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

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/..

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. 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.”

#docs, #meetings, #summary

Agenda for Discussion Meeting September 16, 2025

The meeting is scheduled with the following details:

When: Tuesday, September 16, 2025, 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. Open floor.

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

#agenda, #docs, #meetings

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

Summary of Docs Team meeting July 15, 2025

Attendance

@ninianepress, @milana_cap, @atachibana, @dilip2615, @rollybueno, @estelaris, @ravigadhiyawp, @nikunj8866, @azharderaiya

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming meetings

Project check

@atachibana reviewed, edited, and closed 4 end-user documentation issues.

Open floor

@estelaris shared these updates about the next release:

For the 6.9 release, I would like to add a process for HelpHub where we can use AI to help us write faster and perhaps have the articles on time for the release. More on that soon as I still need to confirm this with the release team.

#docs, #meetings, #summary

Agenda for Discussion Meeting July 15, 2025

The meeting is scheduled with the following details:

When: Tuesday, July 15, 2025, 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. Open floor.

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

#agenda, #docs, #meetings

Summary of Docs Team meeting July 1, 2025

Attendance

@dilip2615, @estelaris, @sagargurnani, @atachibana, @rollybueno, @mosescursor, @abdulwahab610, @nikunj8866, @zeelthakkar, @masteradhoc

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming meetings

Project check

@rollybueno completed these issues during our Docs Team Contributor Day last week — now ready for review:

@atachibana reviewed 7 issues and updated the corresponding articles.

Open floor

@estelaris had the following update to share:

If you want to learn how the release parties work, help with testing, or you’re scheduled to be one of the upcoming minor (or major) release leads, please join us with the details below.

Please note: As a friendly reminder, @kenshino and @ninianepress will be trained by @estelaris to be the Docs Team leads for the next WordPress minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality..

@rollybueno mentioned and agreed to the proposed solution @masteradhoc communicated before the meeting:

@estelaris and @atachibana approved of the suggestion, and @atachibana suggested that @masteradhoc open a GitHub issue for Gutenberg.

The corresponding issue #70584 was created by @masteradhoc immediately following the meeting.

#docs, #meetings, #summary

Summary of Docs Team meeting June 17, 2025

Attendance

@milana_cap, @estelaris, @ravigadhiyawp, @rollybueno, @dilip2615, @atachibana, @ninianepress, @hemant-ahir

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming meetings

Project check

@estelaris had the following updates to share:

Summary of WCEU Contributor Day accomplishments:

  • Issues closed: 19
  • Articles updated: 8
  • Contributors: 12

Open floor

@estelaris was in a meeting last week with the Core AI Team and is working on a process for using AI for writing documentation. It will also be a blueprint for future AI integration into WordPress. Project updates will be provided as they become available.

@kenshino and @ninianepress will be trained by @estelaris to be the Docs Team leads for the next WordPress minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality..

#docs, #meetings, #summary

Agenda for Discussion Meeting (17 June 2025)

The meeting is scheduled with the following details:

When: Tuesday, 17 June 2025, 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. Open floor.

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

#agenda, #docs, #meetings

Summary for Discussion Meeting (06-May-2025)

Attendance

@estelaris @divyeshk71 @azharderaiya @ravigadhiyawp @karthickmurugan @nikunj8866 @Dhruvang21 @DilipModhavadiya @70_Sense

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meetings

Please notice the new meeting timings below.

Open floor

@estelaris explained the steps for contributing to documentation:

  • Find issues like outdated info, typos, broken links, or missing ALT text.
  • Report or pick issues from the GitHub Issue Tracker.
  • Share your updates in the comments or using a Google Doc in the GH issue.

Onboarding videos are available for more help.

#docs, #meetings, #summary

Agenda for Discussion Meeting (29 April 2025)

The meeting is scheduled with the following details:

When: Tuesday, 29 April 2025, 09: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. Open floor.

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

#agenda, #docs, #meetings