Tag Archives: docs

Andrea Roenning 5:53 pm on March 17, 2026
Tags: docs, ,   

Documentation team meeting notes – March 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, March 17, 2026, 14:00 UTC
Meeting Facilitator: @milana_cap
Note Taker: @awetz583
Find the complete meeting on Slack.

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

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

Discussion Meeting

Where: #docs channel on Slack
When: Tuesday, March 31 2026, 14:00 UTC

View upcoming dates on the Documentation Team meeting calendar.

Updates

Preparing for 7.0 Documentation

@milana_cap shared videos for preparing tools and workflows, and outlined the plan to update docs this week following a guideline and a list of items in “Good Progress/Ready” status.

@sajib1223 confirmed he has watched the videos and will join the meeting to start working on the green list items.

Blocks articles overhaul

@awetz583 is working on updates to Media & Text 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.

Good first issues

@supernovia asked about the status of Good First Issues, and @milana_cap mentioned that some can be closed while others need updating. They plan to review these during the upcoming Contributor Day. 

Open Floor

Pathways and Handbook Updates

@supernovia and @milana_cap discussed moving the pathways work to GitHub, with the goal of keeping handbook pages as the detailed reference and the guides as checklists. They agreed this would make it easier for the community to contribute and review the content.

Handbook feedback

@estelaris raised an issue about a WP Credits student’s feedback on the handbook content, noting that some paragraphs read differently in Spanish compared to the English version. They requested help to compare the handbook content with the student’s suggestions and identify any areas that need improvement in the writing style.

Contributor Day Planning

@milana_cap mentioned that she will be available for 2 hours during the upcoming Contributor Day at Tuesday, March 31 2026, 14:00 UTC, and there will be no formal meeting notes or facilitators, just focused contribution time.

#docs, #meeting, #summary

Andrea Roenning 2:58 pm on March 10, 2026
Tags: docs, ,   

Documentation team meeting notes – March 10, 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/ + Video call
When: Tuesday, March 10, 2026, 14:00 UTC
Meeting Facilitator: @estelaris
Note Taker: @awetz583

Next Meetings

Discussion Meeting

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

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/

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

View upcoming dates on the Documentation Team meeting calendar.

Open Floor

#docs, #meeting, #summary

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

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 + Video call
When: Tuesday, March 10 2026, 14:00 UTC
Facilitator: @estelaris

Discussion Meeting

Where: #docs channel on Slack
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: docs, ,   

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: , docs,   

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: docs, ,   

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

Milana Cap 1:32 pm on February 3, 2026
Tags: , docs,   

Agenda for Discussion Meeting September 16, 2025

The meeting is scheduled with the following details:

When: Tuesday, February 3, 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. Proposal for Gamifying Docs contributions draft
  5. Open floor.

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

#agenda, #docs, #meetings

Ritika Roy 8:29 am on November 13, 2025
Tags: docs, ,   

Summary of Docs Team Meeting on 11th November

Housekeeping

Find the complete Transcript of the meeting on Slack.

Next meeting:

  1. Where: #docs channel on Slack
  2. When: Tuesday, November 18, 2025 at 07:30 PM GMT+5:30
    Participants and Their Contributions:
    @milana_cap
    1. Facilitated the meeting, welcomed @ritikaroy2830, and shared onboarding resources:
    Onboarding Sessions for Documentation Team
    2. Provided the meeting notes format template:
    Summary of Docs Team meeting Nov 4, 2025
    3. Led project updates, discussed contributor rewards, and explained documentation review roles (First and Second Reviewer).
    4. Closed 4 documentation issues for version 6.8, stating only one left:
    GitHub Issue Tracker.
    5. Announced planned GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ automation for review checklists and notifications.
    6. Clarified roles for HelpHub, DevHub, Handbook, and GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ releases documentation.
    7. Guided policy updates for documentation responsibilities on Themes and Plugins handbooks.
    8. Summarised action items: updating reviewing roles, renaming review roles, implementing GitHub automations, and updating the CONTRIBUTING documentation.
    9. Proposed automating replies for documentation issues outside Docs’ scope.
    10. Suggested a triage role for new and open issues classification.
    @atachibana
    Shared experience leading the Docs table at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Kansai and translation work. Confirmed willingness to continue as second reviewer for HelpHub.
    @Azhar Deraiya
    Reminded team about submitting contributions via the contributions form on the Docs blog sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.:
    Make WordPress Documentation
    Encouraged contributor submissions for badge assignments.
    @Arslan
    Led Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ and Docs Table at WordCamp Islamabad 2025; submitted contributions through the contributions form.
    @estelaris
    1. Discussed project responsibilities and defined roles within Docs projects.
    2. Proposed detailed roles for first and second reviewers with checklist requirements.
    3. Emphasised task distribution for efficiency.
    4. Agreed on policy directing off-scope handbook issues to respective teams.
    5. Highlighted the need to update HelpHub and DevHub roles with detailed responsibilities, including issue review and closure.
    6. Recommended asking draft writers for changes when necessary.
    @MosesCursor
    Supported having experienced reviewers fill roles to maintain consistency.

    Main Points Discussed in the Meeting:
    1. Documentation roles are clearly defined with reference to team roles:
    Docs team roles
    2. Two-tier review system agreed upon:
    3. First Reviewer: Checks grammar, structure, style, screenshots, with guides:
    Grammar Guide,
    Writing Tips,
    Tone and Voice Guide
    4. Second Reviewer: Fact-checking and final approval.
    5. GitHub automation planned for checklist reminders and review label notifications.
    6. Policy updates to clarify the Docs team’s scope and proper handling of documentation issues for Themes and Plugins.
    7. Expanded HelpHub and DevHub roles to include issue review, documentation updates, and closure.
    8. Proposal for an issues triage role to handle new and open issues.
    9. Checklist to be created for reviewers detailing responsibilities.
    The End 🙂

#docs, #meeting, #summary

Milana Cap 4:05 pm on November 4, 2025
Tags: docs,   

Summary of Docs Team meeting November 4, 2025

Housekeeping

Find the complete Transcript of the meeting on Slack.

Next meeting:

1. Meeting Time Confusion

  • The meeting began one hour later than planned due to daylight saving time changes.
  • Action:

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.
  • A new contribution form was introduced to capture contributions not recorded anywhere else.
  • 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 to publish a detailed post explaining the recognition workflow and gamification proposal.

3. Regular vs. Release Contributions (led by @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., 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/. 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).
    • Final tasks are done during the release party (see: Documentation process during a major version release).
  • 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, #summary

    Estela Rueda 4:59 pm on September 18, 2025
    Tags: docs   

    Summary of Docs Team meeting September 16, 2025

    Attendance

    @estelaris, @milana_cap, @ninianepress, @sagargurnani, @atachibana, @azharderaiya, @mosescursor, @aialvi, @sirlouen, @rollybueno

    Housekeeping

    Find the complete Transcript of the meeting on Slack.

    Upcoming meetings

    Open Floor

    @milana_cap and @estelaris attended the #core meeting on September 10 and our conclusion is that coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team wasn’t aware of the tasks of the docs team during a release. For 6.9 release, @estelaris accepted a temporary Docs Liaison, to not interfere with release work and to have a proposal from the docs team on how we want to collaborate in future releases.

    The Docs Liaison will attend the release team meetings in the #6.9 release leads channel, review the roadmap to create the 6.9-related user documentation and to support the team during the final release day. DevNotes will be the responsibility of core committers, the 6.9 GH project has been created to track both DevNotes and User documentation.

    @estelaris will work with the 6.9 release team on final release day to create/update the release documentation. In order to mentor other documentarians on this workflow, during the next Contributor Day (September 23), docs will have a mentoring session on this topic and record videos to add to the handbook page Documentation process during a major version release day.

    Other topic discussed was how #docs team gives props to contributors and we agreed to review our process on this topic.

    As a summary, the team committed to discuss the following in the next discussion meeting on September 30:

    • Gather all the release-related documentation (from core & docs handbooks) and review the sections that are pertinent to docs. Update what’s needed, change the vocabulary/tone and length. We know people don’t read and sometimes handbooks are written in a difficult English.
    • Create a proposal of how docs wants to work in future releases (@estelaris to write a draft), including tasks and timing.
    • Define which contributors tasks should be recognized (is there an automatization we can add to GH/WP?)  eg. when they submit an issue, submit drafts, publish a new article, etc.
    • Decide what goes for noteworthy and what goes for “regular” release contributor.

    Among other handbook workflows we need to review:

    • Define team members vs team contributors
    • Update the team page
    • Documentation team profile badge
    • Add props and ask for peer reviews on meeting notes

    Gathering the list of updated files

    Thank you to @sirlouen for showing us how to gather the updated files list during a release cycle.

    Props to @milana_cap and @ninianepress for reviewing the notes