Attendance
@crs1138, @bph, @kenshino, @estelaris, @chaion07, @cbringmann, @Daisy, @tacitonic, @atachibana, @sukafia, @justinahinon, @collinsmbaka, @themiked
House Keeping
Agenda: Agenda for Docs Team meeting 28 October 2020
Facilitator: @estelaris
Note-takers: @crs1138
Notes Reviewed by: @chaion07
Facilitator for the next meeting: @chaion07
Next meeting: 2 November 2020
Find the complete Transcript of the meeting on Slack.
Project Updates
- @bph: 🐝-docs no project update, we will lose two pages Facebook & Instagram Embed. We will update them with the API Change this week.
- @atachibana Migrating an re-routing Codex to Code reference Classes: 43 of 43 (100% < – 83.7%) Hooks: 90 of 355 (25.4% < – 17.5%) by @stevenlinx, @collinsmbaka and @atachibana Note: Though we reached 100% migration of classes, we need some improvements.
- @themiked: Plugin handbook is now fully blocked.
The team couldn’t discuss the following agenda items due to dependency on @milana_cap and others:
New Member Mentoring
@sukafia reported that:
- 3 new people joined in the week 19-25th October 2020.
- There’s plan for a meeting to brainstorm ways to move the team forward
Monthly Coffee Break Reminder (October 2020)
@sukafia invites everybody to the coffee break Topic: Docs team Coffee Break Time: Oct 29, 2020 11:00 UTC Join Zoom Meeting https://us02web.zoom.us/j/81733187709?pwd=WXBjbXZBdGhiSUpWMnJzK0JxRGV0dz09 Meeting ID: 817 3318 7709 Passcode: Docs
Google Season of Docs 2020
@tacitonic completed the Language and Grammar section and is currently working on the Punctuation section. @tacitonic updates his progress in the README file daily: https://github.com/WordPress/WordPress-Documentation-Style-Guide
@dmivelli provided a long list of suggestions.
Meeting Times
- @crs1138 shared the WP Docs Team Meeting times poll
Discussion
Outdated Documentation
@estelaris and @kenshino suggested the following options to deal with outdated documentation pages:
- Delete it and redirect the URL to a similar/relevant resource (via a 301)
- Delete it and serve a 410 status (‘gone forever’), ideally coupled with a nice template explaining to the user that the thing is gone
- Use a meta robots tag / HTTP header to noindex it, if we think it’s still useful to users but want to keep it out of search engines.
- @kenshino: Setup a legacy section and move docs there that are outdated for x versions but still relevant for a good percentage of our user base?
@themiked will sum up his thoughts on how to proceed in a post and ask the community for feedback.