Attendance: @milana_cap, @chaion07, @javiercasares, @ashiquzzaman, @atachibana, @femkreations, @greenshady, @piermario, @brightemeka, @krupalpanchal, @emmaht. Asynchronous updates from @lucp and @estelaris.
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.
Meeting Facilitator: @chaion07
Note Taker: @webcommsat. Review: @milana_cap and @femkreations
Next Meeting Facilitator (in two weeks): @brightemeka
Next Note Taker (in two weeks): @greenshady
Next Triage Meeting Facilitator (next week): @milana_cap
Documentation Issue Tracker Updates
@milana_cap shared: there have been a lot of updates for Team roles tickets. This is hoped to be completed by end of next week: GitHub ticket #385
WordPress 6.1 release
WordPress 6.1 release has started, docs focus folks working in triage and collecting tickets for documentation.
Useful links for documentation
Anyone who wants to join in or learn how a release is documented, can contact @milana_cap in the documentation release team. She will ping The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” contributors once there is work available. Currently, everything is being prepared. A checklist is being created. An additional volunteers tracker for WordPress 6.1 release docs contributors has been set up too.
The post from the first meeting of the WordPress 6.1 release docs team: @bph, @milana_cap, @femkreations, @webcommsat, @mburridge. YouTube video from the meeting.
Project boards updates
@femkreations shared an update from the projects boards:
@estelaris: no new updates
@emmaht: we are working on (waiting to be reviewed)
The following items should be finished next week
@femkreations: highlighted contributions from @wigno and @leonnugraha who have been doing a great job with the 6.0 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. editor documentation. Thanks for their contributions.
@themiked: fixed a few minor issues, found a problem with the GitHub importer and logged it.
Collaborations between docs and hosting team
@javiercasares: last week Milana was on the #hosting-community channel explaining this new project / handbook / documentation about separating some of the most technical documentation from the Hubs.
There is a new label in the Issue Tracker ‘advanced administration’.
Initial check of the tickets, first idea on categorization can be found in this Google doc. This is a first “structure” with all the links and everything I found on those tickets. As this is a first idea, it will probably change a lot.
Thanks to @JavierCasares for structuring the new handbook.
First pull request for the Advanced Administration Handbook
#1 Create a first possible File Structure – a first level possible structure, with the “big categories”. This may change as we start creating and updating content, but this is a place to start.
Second pull request (technical one, for the #meta team)
#2 First Manifest file – a first manifest file, created manually because we will need to have the WP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ software configured… but we will have that when Meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. creates it.
Those files will help us start creating new content and migrating the actual one. Then sync everything with the site automatically (so every time we do a merge, the content will be updated). These are first ideas, help and suggestions welcome.
@lcup sent an update to the meeting:
– added articles to move from HelpHub to DevHub docs for the new advanced administration handbook in: Documentation Issue Tracker, ticket 388 in GitHub. Thanks to @estelaris and @femkreationsfor doing all of the look-up work on this.
@milana_cap shared context: parts of “too technical” docs from HelpHub will end up in this new handbook.
Updates on the Five for the Future program and proposed improvements – post from July 28, 2022.
@shetheliving shared async: wanted some additional views on Documentation Issue Tracker issue on Tidy up suggested object caching plugins #410, for @tillkruess and the Performance team.