Attendance
@zzap, @atachibana, @mkaz, @DaisyO, @clorith, @tacitonic, @estelaris, @ashiquzzaman
Housekeeping
Where: #docs channel on Slack
Find the complete Transcript of the meeting on Slack.
Meeting Facilitator: @kenshino
Note Taker: @nahidsharifkomol
Note Reviewer: @ashiquzzaman
Next Meeting Facilitator: @kenshino
Project Updates
@tacitonic is currently writing the article for D. He has completed 24/28 articles in the final section remaining, that is the word list.
@zzap didn’t check all the tickets yet but so far this is what we’ll have, But the block editor end-user and dev docs excluded.
HelpHub updates:
– Remove the “Featured” tab in the Add Themes screen
– Rename “Summary” to “Excerpt” in Reading Settings
– Remove IE11 from the list of supported browsers
– Twenty Fifteen, Twenty Fourteen, Twenty Thirteen, Twenty Twelve: Add Block Patterns
– Customize: Bulk delete widgets
– Add a copy-link button at the media upload page
– Add ability to delete multiple menu items
– Enable revisions for the reusable block custom post type
DevHub updates:
– Ability to mark the plugin as unmanaged
– Remove IE11 from the list of supported browsers
– Add new actions to Site Health navigation
– Remove the “Featured” tab in the Add Themes screen
– Add capability to set the default format for image sub-sizes.
– Standardise the terminology used for hooks, actions, and filters in documentation
Anyone who wants to get involved with her, you can ping her through this doc. Once she has all the list of updates completed she’ll publish p2 with kind words and cookies, begging for help. But the shocking news is, there are no docs whatsoever about Site Health and that should be changed, regardless of the release.
@mkaz basically the block editor and FSE updates for 5.8 reaching a finalized state, and he’ll work on updating the dev docs for those parts in the spreadsheet.
@kenshino agreed to @zzap and said when he tried to look for “What the hell is the endpoint for Site Health” and couldn’t find any official information
@zzap talked to @clorith about it. Apparently, they asked for dedicated space, didn’t move further with the request, and gave up
No new block editor update
@clorith wasn’t sure with an ingrained knowledge of that issue, but so far we’ve been very good about documenting filters and actions that it has, as well as dev notes with releases under the site-health tag on make/core at least
@zzap wasn’t sure whether folks within here are tickets for the end-user as well. Here is the link for the tickets
@kenshino it looked like they can at least have an easy page created that kinda says “We have a Sitehealth piece” and this is what you can do
New Member Mentoring
No updates so far
Theme Handbook Changes
No updates so far
Open Floor
@kenshino was talking about @Courtney’s proposal and @zzap has been talking to @mkaz about this and he thinks it could be a good thing to propose once we get the team-reps channel. The doc team thinks that core dev should be paired with someone from docs as soon as the new feature is started developing. Or perhaps each component should have someone from docs looking after it and working with devs. Of course, we don’t have enough people but I’m thinking that this might actually attract more contributors due to close work with devs.