Housekeeping
Attendance: @ninianepress @femkreations @milana_cap @colorful-tones @leonnugraha @dpknauss @lucp @estelaris @samanthaxmunoz
Where: #docs channel on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. Find the complete transcript of the meeting on Slack.
Agenda: https://make.wordpress.org/docs/2022/09/14/agenda-for-docs-team-bi-weekly-meeting-27-september-2022/
Meeting Facilitator: @ninianepress
Note Taker: @lucp
Next Meeting Facilitator (in two weeks): @estelaris
Next Triage Meeting Facilitator (next week): @milana_cap
Project Updates
The documentation for WordPress release 6.1 is getting off the ground. Adding a comment to this issue will ensure that you get pinged once it gets started.
@femkreations also reports that the issue gardening for 6.1 is in progress from the gutenberg 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/ PRs.
Currently they have 19 To do items and 1 In progress in the 6.1 Project board.
The team closed 5 issues in GH for 6.0 and more will be reviewed and closed this week.
@emmaht has reviewed these two issues:
https://github.com/WordPress/Documentation-Issue-Tracker/issues/225
https://github.com/WordPress/Documentation-Issue-Tracker/issues/226
This week @leonnugraha and his colleague will work on this issue and this one.
@colorfultones is keeping an eye on this issue to see if it gets backported with the 6.1 release correctly.
@lucp talks about the new Advanced Admin handbook and how old content-migrations from HelpHub have now been included as PRs, specifically these issues that @femkreations has submitted.
And @estelaris reports about the reclassification project:
The sitemap revision/comparison is finally finished. A post is in the works.
She did a lot of content revision and opened a lot of tickets.
FAQs at the bottom of HelpHub pages
This discussion was scheduled for this meeting and connected to this github issue. While everybody agreed that doing content-review for this content is smart (and filter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. out all the too technical stuff), the question remained on wether or not to put FAQs at the bottom of pages or give the FAQ its own section. The team eventually landed on creating a seperate FAQ section, which @estelaris will incorporate into the design.
Open floor
@samanthaxmunoz has compiled a list of high-priority issues mostly surrounding the documentation of WordPress 6.0, which can be found here
@femkreations has a similar list of WordPress 6.1, but it’s in a Github Project.
@samanthaxmunoz is also working on a block 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. pattern for block documentation as discussed in this Slack thread. It will get converted into an issue with the new label internal task
