Housekeeping
- Attendance: @ninianepress, @greenshady, @welcher, @estefany, @emmaht, @mburridge, @kenshino
- Where: #docs channel on Slack. Find the complete Transcript of the meeting on Slack.
- Meeting Facilitator: @estelaris
- Note Taker: @lucp, @greenshady
- Next Meeting Facilitator (in two weeks): @lucp
- Next Note Taker (in two weeks): @greenshady
- Next Triage Meeting Facilitator (next week): @milana_cap
Projects checks
- Helphub redesign project: https://make.wordpress.org/docs/2022/03/07/first-review-on-the-new-sitemap-for-helphub-or-documentation
- Josepha is reviewing tickets to be resolved with Meta team for the new Design and Reclassification project: https://docs.google.com/document/d/1IdjKFqKHARw6RvfNB0XmbyaG1hZBulPoFImK6UO0G3c/edit?usp=sharing
- @lucp has been working on user-contributed notes in the code-references, but it’s a lot of work. Anybody interested in helping out can find the ticket here
- @ninianepress is working her way through the on-boarding videos. she’ll have updates this week.
- @estelaris linked to older onboarding videos for new volunteers that can be found here
- @emmaht has been assigned to this ticket
DevHub & Learn WordPress development
- The #meta team is working on improvements to DevHub (the developers documentation). If you have any suggestions, please comment on this post
- There is also an x-post from the Learn team. Again, if you are interesting in either collaborating or have ideas, please comment. The docs team is actively contributing with the Learn team.
Open Floor
- @mburridge wanted clarification on whether to continue creating Block Editor Handbook issues in the Documentation-Issue-Tracker. (see issues #379 and #75).
- While the Block Editor Handbook falls under the Gutenberg team, @milana_cap mentioned in one of the issues that we might as well gather all issues regarding the Block Editor Handbook in the Documentation-Issue-Tracker while the docs team is preparing to send over a larger issue to the Gutenberg team with all sorts of improvements.
- Similar issues as #379 and #75 should be posted in #docs so the team can take a look at it. @milana_cap later clarified the point on slack
Props to @greenshady for helping with notes.