DocsWP — WordPress Help

Test Chat Summary: October 8, 2025

On 8 October 2025 at 2PM GMT, <test-chat> started in #core-test facilitated by @sirlouen The agenda can be found here.

1. Attendance

@mosescursor @nikunj8866 @agulbra @dhavalkapadane @fakhriaz @muddassirnasim @passoniate (async) @dilip2615 (async)

2. Volunteer

This week’s note-taker was @sirlouen

3. WordPress Ecosystem Announcements

4. Test Team Announcements

5. Call for Testing

6. Test Team Discussion, Questions, and Blockers

1. Handbook Overhaul—Task Assignments

  • The meeting began with the launch of the Handbook Overhaul project, focusing on assigning tasks to contributors.
  • Each participant will be assigned at least one new page to create and two or three pages to review.
  • The objective is to ensure every single documentation page is properly replicated before the originals are deleted—anything not replicated will be lost.
  • Tasks for contributors fall into three categories:
    • Create: New pages to be created, primarily copied from the originals.
    • Review: Existing pages requiring review and verification.
    • Discuss: Pages to be discussed in any meeting, like the Archive section.
  • A second call-out will be made for more volunteers, who will then be assigned tickets.

2. Proposal: Archiving Old Sections

  • A proposal was presented to create an “Archive” section in the documentation for obsolete content.
  • The specific example raised was archiving the “FSE Outreach Experiment” page and similar sections not currently useful.

3. Section Review: “Crawl your test site for errors”

  • A specific section, “Crawl your test site for errors”, was discussed.
  • The group debated whether this section is still relevant to keep, with some members expressing doubts.
  • The decision was left open for further review and comments. Removal will be approached in the next meeting unless there are any arguments against it.

7. Closing and Open Floor

  • @fakhriaz commented about ongoing testing, such as a category dropdown not meeting accessibility standards (#63531), and a problem with classic widgets.
  • Also, members were informed, that during testing (e.g., “Accordion block”), participants can report that no issues were found after comprehensive checks.
  • A proposed change in the meeting structure: start with discussions and open floor items, and save announcements for the end. This aims to capitalize on initial engagement and ensure action points aren’t overlooked.

8. Next Test Team Sessions

Props to @nikunj8866 and @mosescursor helping review these notes and offering feedback.

#core-test