Tag Archives: summary

Jenni McKinnon 9:42 am on March 16, 2023
Tags: , , summary   

Summary for Docs Team meeting, March 7, 2023

Attendance

@ninianepress @ninthcoder @leonnugraha @femkreations @atachibana @emmaht @estelaris @thisisyeasin @javiercasares

Housekeeping

Find the complete Transcript of the meeting on Slack.

Please note: @ninianepress wrote this summary as @femkreations was unavailable due to other high-priority Documentation Team tasks, and will also write the next summary for similar reasons in place of @estelaris.

Project checks

@wigno updated #497 and #496.

@emmaht reviewed the above tasks, and @leonnugraha published them.

@wigno also finished the draft for #283.

@leonnugraha added links in the End-User Inventory.

@femkreations added related tasks to the 6.2 Project Board in GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/:

@atachibana completed task #13.

@estelaris mentioned that the Documentation Sitemap was implemented on March 6th.

Discussion on application for Google Season of Docs

The discussion surrounding the application for the Google Season of Docs has been rescheduled to the next meeting.

Check out the additional details in the summary from the previous bi-weekly Docs Team meeting under the same heading.

Collaboration on HelpHub and DevHub redesign request

@estelaris noted the following for translating documentation:

  • The HelpHub and DevDocs redesign request post was published to gather information on processes and needs from locale teams.
  • @estelaris is presenting and discussing the new documentation sites (HelpHub and DevHub) in a recent WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. and will work with the Spanish team.
  • @javiercasares has ideas on how to test/try out ways of translating.
  • @estelaris is working on figuring out if we can use the Inventory as a tracker for polyglots so they are aware when we upload new articles.

How to improve the Glossary in WordPress

Also, in terms of collaboration with the marketing team:

  • @estelaris is looking into the marketing team’s initiative to move the WordPress Glossary to a different place as a single source of reference for WordPress terms.
  • The idea is to replace the many glossaries in the handbooks and make sure we are using the same definition for matching terms.
  • Make teams should be in charge of updating and adding new glossary terms, as needed.
  • @chanthaboune is aware of this initiative and has requested to be updated so support can be provided.

Update on the Docs inventory

This part of the meeting was unintentionally missed so it will be added to the agenda for the next bi-weekly Docs Team meeting.

Open floor

@estelaris has already reached out to the MetaMeta 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. team, but asked if any one had suggestions on how to get a page listing for the Support Articles page in Spanish. There are currently no sitemaps on the Rosetta sites:

  • @javiercasares suggested an alternate solution if other options aren’t available: Creating a page with the link list by using an APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.. One currently exists, though, it’s empty.

Please note: As a reminder, Daylight Saving is quickly approaching. In Europe it begins on March 26th and in North America Daylight Saving started on March 12th. Regardless, Documentation Team meetings remain at the same scheduled time of 14:00 UTC.

#docs, #meetings, #summary

Jenni McKinnon 2:24 pm on March 6, 2023
Tags: , , summary   

Summary for Docs Team meeting, February 21, 2023

Attendance

@ninianepress @ninthcoder @femkreations @estelaris @sereedmedia

Housekeeping

Find the complete Transcript of the meeting on Slack.

Project checks

@leonnugraha worked on the Navigation block article during the WC Asia Contributor Day. Because it’s so outdated, it requires a new document once the WordPress v6.2 release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. is out. Work on this article will continue then.

@femkreations completed gardening the closed pull requests in GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ from 14.2 through 15.1, and added the “User Documentation” label.

Additionally, 4 issues in 6.0 and 1 issue in 6.1 were closed.

@estelaris mentioned that the biggest ticket for the categorization project – moving technical articles to DevHub with issue #388 – is now closed. A big thank you goes out to @JavierCasares.

Discussion on application for Google Season of Docs

The discussion for a proposed application for the Google Season of Docs has been rescheduled to the next meeting.

Google has a program where you can apply as an open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project. If you get chosen, Google will help you with the project’s documentation.

In 2020, the Documentation Team participated, and our style guide was completed. We need to think of a good project in order to be chosen since the competition is high. @milana_cap is already making inquiries to see if we can participate again this year.

It’s important to note that the application process has changed so this will also need to be considered in future discussion.

@sereedmedia mentioned asynchronously that the glossary may be a great project to apply for and @estelaris agreed.

Open floor

@estelaris is meeting with the Polyglots TeamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. to discuss collaboration on documentation updates.

#docs, #meetings, #summary

Jenni McKinnon 10:30 pm on February 10, 2023
Tags: , , summary   

Summary for Docs Team meeting, February 7, 2023

Attendance

@ninianepress @milana_cap @leonnugraha @femkreations @estelaris @ninthcoder @JavierCasares @magaliechetrit

Housekeeping

Find the complete Transcript of the meeting on Slack.

Project checks

@milana_cap finished the WordCamp Asia Contributor Day Plan.

@femkreations completed reviewing the closed pull requests (PRs) in GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ for Gutenberg from 14.2 through 15.0, and the User Documentation label was added. Femy also reviewed and closed one WordPress 6.1 issue.

@estelaris posted #652 and #651, but it was later moved to the MetaMeta 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. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. Ticket #6740.

@leonnugraha reviewed and published #502 and #176.

Discussion on what can be done for the WCAS Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

@milana_cap is working on an interactive plan to onboard new contributors.

@milana_cap also organized onboarding sessions for the new non-project roles: Issue Triage Facilitator, Issues Coordinator, and Issues Reviewer. The session will be recorded, and posted on WordPress.tv.

Open floor

@JavierCasares mentioned two meta trac tickets – #6411 and #6714. Both need follow-ups and @milana_cap will leave a comment on the ticket for updates or ask about them in an upcoming meta meeting.

Props to @leonnugraha for writing this meeting summary.

#docs, #meetings, #summary

Jenni McKinnon 3:28 pm on January 31, 2023
Tags: , , summary   

Summary for docs team meeting, January 24, 2023

Attendance

@leonnugraha @ninianepress @milana_cap @estelaris @ninthcoder @atachibana @femkreations

Housekeeping

Find the complete Transcript of the meeting on Slack.

Project checks

@milana_cap is working on crafting the WCAS Contributor Day task list.

@ninianepress finished issue #128.

Status update for HelpHub

@estelaris walked through the recently finished updates to the End-User Documentation (HelpHub, internally).

For full details of these changes, please see New look, new site, new HelpHub.

Status update for DevHub

@estelaris noted that @javiercasares (not in attendance) is the project lead for the Developer Handbook (DevHub, internally) redesign. She mentioned that the design has been finalized, and development work has begun.

Open floor

@milana_cap mentioned there is a new non-project role in the team that no one has been doing before: GitHub issues coordinator.

@femkreations would also like to note that issue gardening for v6.2 is in progress from the GutenbergGutenberg 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/ pull requests (PRs).

#docs, #meetings, #summary

Jenni McKinnon 6:00 am on January 9, 2023
Tags: , , summary   

Summary for Docs Team meeting, January 10, 2023

Attendance

@ninianepress @milana_cap @leonnugraha @femkreations @atachibana @thisisyeasin @estelaris @wigno @vanpariyar @kartiks16 @samanthaxmunoz @ninthcoder @daisyo @webtechpooja @onlykawshar

Housekeeping

Find the complete Transcript of the meeting on Slack.

Moving HelpHub to the New Site

@estelaris is working with the MetaMeta 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. team to replace the /support site with the /documentation site. The new URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org is expected to be ready after January 17, 2023. In the meantime, contributors should refrain from adding, editing, or publishing content on the /support site as they will be lost.

Read this post for more information.

Project Checks

@leonnugraha – Reviewed and published #234 and #314

@milana_cap – Almost completed the Team roles page(s)

@ninianepress – Finishing an update that was supposed to be done by the end of 2022

@wigno – Completed #506, and it’s now ready for review. Will plan to work on #508 and #502 this week

Topics for the 2023 WordPress Community Summit

We should think, as a team, of possible topics for the Community Summit. What are the Documentation team needs that can, in full or partially, be solved in an environment where all other teams are present? 

@estelaris proposed the following topic: How will we collaborate with polyglots to translate the documentation and help them create the new sitemap? We need to push for translations. Otherwise, a lot of our work will stagnate as an English version only

@ninianepress wants to submit a topic that @milana_cap mentioned during last year’s WCEU – about a waterfall solution across teams for everyone to be able to collaborate on projects across all teams. @milana_cap added an example that the Training/Learning team has been discussing for a long time with the Docs team on how to make a tool that would help us all communicate better about release changes.

@atachibana pointed out several workflow issues for the HelpHub that can be improved. Through the discussions, we agreed that we could discuss these issues internally within the Docs team.

Open Floor

@wigno volunteered to review and publish documentation content. @leonnugraha will help him to get going.

@milana_cap has an idea for three little tools that should help with some workflows and will build something to test out:

  • Meeting agenda generator
  • Meeting summary generator
  • New contributor orientation tool/onboarding tool

@estelaris will ask the meta team about the users’ access when the /documentation site is live.

Props to @leonnugraha for writing this meeting summary.

#docs, #meetings, #summary

Milana Cap 3:40 pm on December 22, 2022
Tags: summary   

Summary for Docs Team meeting, December 13, 2022

Attendance

@ninianepress @milana_cap @leonnugraha @femkreations @atachibana @thisisyeasin @emmaht @juanmaguitar @estelaris @bph @themiked @psykro

Housekeeping

Find the complete Transcript of the meeting on Slack.

Documentation team holiday schedule

It has been decided that the Documentation team will have a 3 weeks long time off for the holidays. This means that no meetings will happen during this time, as well as the response in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel can be slower.

The time of is starting on Monday, December 19th 2022; and ends on Sunday, January 8th, 2023. The first meeting in 2023 will be on Tuesday, January 10th, at 2PM UTC. The format will be regular biweekly meeting.

Projects checks

@themiked – all the security related stuff is rewritten and consolidated now (#622, #623)

@femkreations – Reviewed, updated and closed 8 tasks for 6.1 Project and 9 tasks for 6.0 Project

@leonnugraha – Closed and published one high-prio 5.9 issue.

@atachibana – Tackling opened issues from the bottom (the oldest). Closed two issues and working #13.

@estelaris – working with metaMeta 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. on the redesign for HelpHub and DevHub. We are testing the breadcrumbs and waiting on a resolution from coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. on next steps to do the reclassification of the articles, title changing and lots of 301s. May not have a holiday break.

@milana_cap – started working on Estela’s issue, did some reviewing of dev blog posts, a bit of onboarding docs (really hope to get that done before the next meeting).

Open floor

@estelaris – we need to add props for meeting facilitators and note takers so that everyone gets acknowledge.

@femkreations – saw this posting in the Make blog. Anything we can come up with for the Docs team?

Topics for the WordPress Community Summit 2023

We should think, as a team, of possible topics for Community Summit. What are the Documentation team needs that can, in full or partially, be solved in an environment where all other teams are present? This should be the first agenda item at the next meeting. Format:

  • Topic description
  • Why would this topic particularly benefit from in-person discussion/work at the Community Summit?
  • Who needs to participate in the discussion described above?(In other words, without these people in the room, the discussion may be incomplete. This may include specific Contributor Teams, roles, individuals, etc.)

Have a wonderful holidays and a good rest, team. See you in 2023.

#summary

Niels Lange 2:24 pm on November 2, 2022
Tags: , , summary   

Summary of Docs Team Meeting November 1, 2022

Housekeeping

Attendance: @milana_cap, @chaion07, @atachibana, @nielslange, @kafleg, @leonnugraha, @lucp, Malcolm, @femkreations, @colorful-tones, @dpknauss, @bph, and @estelaris
Where: #docs channel on SlackSlack 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: n/a
Meeting Facilitator: @milana_cap,
Note Taker: @nielslange
Next Meeting Facilitator (in two weeks): @femkreations
Next Triage Meeting Facilitator (next week): TBD

Project updates

  • @nielslange fixed broken code formats of the theme-related docs (see https://github.com/WordPress/Documentation-Issue-Tracker/issues/531).
  • @femkreations worked on WordPress 6.1 pages (see https://wordpress.slack.com/archives/C02RP4WU5/p1667311973175699).
  • @colorful-tones created a Trac ticket related to Block Patterns (see [#6556: Consider allowing Make teams to create block patterns](https://meta.trac.wordpress.org/ticket/6556) ).
  • @leonnugraha is planning to work on [HelpHub Remove redundant block name from “settings” panels · Issue #513 · WordPress/Documentation-Issue-Tracker · GitHub](https://github.com/WordPress/Documentation-Issue-Tracker/issues/513).
  • @femkreations mentioned that 44 pages of [6.1](https://github.com/orgs/WordPress/projects/45/views/2) and 14 pages of [6.0](https://github.com/orgs/WordPress/projects/28/views/11) have the status `Todo` if all issues for 6.0 should be moved to 6.1. @milana_cap then raised the question if the issues can be merge theme seamlessly.
  • @nielslange mentioned that a few issues of 6.0, that are in `Todo` should be in `Ready for Review` and volunteered moving the corresponding issues to the correct column.
  • @milana_cap mentioned that the [Yoast Contributor Day](https://yoast.com/about-us/events/yoast-contributor-day-november-2022/) will take place on November 3rd, 2022.
  • @estelaris mentioned that @ninianepress finished adding terms to the docs glossary project in GitHub (see https://wordpress.slack.com/archives/C02RP4WU5/p1667313612480669 and https://github.com/orgs/WordPress/projects/20/views/1).

Open Floor

  • @nielslange asked about how to follow-up after working on a doc and `Save it for later`. @milana_cap suggested to pingPing 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.” the corresponding team lead.
  • @milana_cap mentioned that she saw the docs team small, then big, then small and now growing again and that she’s very happy with the current documentarians that are very dedicated.
  • @estelaris and @milana_cap had a brief discussion about the Handbook’s Glossary and @estelaris mentioned the link to [WordPress Glossary update](https://github.com/orgs/WordPress/projects/20/views/1).

#docs, #meetings, #summary

Sam Brockway 5:04 pm on October 11, 2022
Tags: , , summary   

Summary of Docs Team Meeting October 11, 2022

Housekeeping

Attendance: @ninianepress @femkreations @milana_cap @colorful-tones @atachibana @estelaris @samanthaxmunoz @mayankgupta @webcommsat @bph
Where: #docs channel on SlackSlack 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/10/10/agenda-for-docs-team-bi-weekly-october-11-2022/
Meeting Facilitator: @ninianepress
Note Taker: @samanthaxmunoz
Next Meeting Facilitator (in two weeks): @estelaris
Next Triage Meeting Facilitator (next week): @ninianepress

Project Updates

It was a busy week for the 6.1 release cycle – many dev notes are published and some are still in review.

Release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1 is ready today as reported by @milana_cap.

@samanthaxmunoz has been working on a blockBlock 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 and the pattern is ready for review before it is added and documented – see Issue #474.

@femkreations reviewed 333 closed PRs in GutenbergGutenberg 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/ from 13.1 through 14.1 with the User Documentation label and created 78 issues in GitHub for 6.1 User Documentation.

@femkreations also reviewed the About page draft and listed top priority tasks for the November 1st release. There are 25 items to do that ideally will be completed before the release of WordPress 6.1. The list is pinned to the #docs Slack channel.

Reclassification of End User Documentation

The reclassification of end user documentation has been finalized and there are now articles ready for content review.

In summary, the goal of the reclassification project is to re-organize the end user documentation and remove “too technical” content from end user documentation and/or merge it into developer docs.

An inventory of technical parts from end user documentation can be found here.

Related, WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Support is being renamed to Documentation – more information about that is available here, “Renaming WordPress.org Support to Documentation”.

Equal priority should be given to WordPress 6.1 documentation and the reclassification project.

Process in Project Boards Discussion

The team discussed the process for documentation project boards at length. As it stands there are only 2 columns, “In Progress” and “Review”, which are not clear and were discussed last week.

Various ideas were suggested about how to organize the project boards including separating into “new documentation” and “existing documentation”.

A consideration is that during Contributor Days often issues get screenshots and content updates in the comments of the issue, but the articles are not updated or assigned.

New columns have been added with temporary names such as “Text in progress” and “Screenshots in progress” but will likely continue to be refined.

The discussion will continue asynchronously or during the next meeting.

Open Floor

An Online Contributors Day for the Docs Team was discussed and will take place on October 25th starting at 10 am UTC.

@mayankgupta mentioned that DesktopServer has been discontinued yet is referenced in several documentation articles and has created an issue where mentions of DesktopServer are being noted.

#docs, #meetings, #summary

Jenni McKinnon 12:43 pm on September 14, 2022
Tags: , summary   

Summary of Docs Team Meeting September 13, 2022

Housekeeping

Attendance: @estelaris @ninianepress @femkreations @robinwpdeveloper @leonnugraha @colorful-tones @samanthaxmunoz @chaion07 @javiercasares
Where: #docs channel on Slack. Find the complete transcript of the meeting on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
Agenda: https://make.wordpress.org/docs/2022/09/12/agenda-for-docs-team-bi-weekly-meeting-13-september-2022/
Meeting Facilitator: @estelaris
Note Taker: @ninianepress
Next Meeting Facilitator (in two weeks): @ninianepress
Next Note Taker (in two weeks): TBD
Next Triage Meeting Facilitator (next week): @milana_cap

Project Updates

WCUS Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

@femkreations shared contributor day successes at WCUS which was on September 11, 2022:

WCNL Contributor Day

Yoast hosted a WCNL contributor’s day on September 14, 2022 at 10 AM – 4:30 PM UTC +2. It was available to join in-person, or online.

Open Floor

Issue When Editing Docs

@samanthaxmunoz pointed out that there’s an issue when you edit documentation pages in the back end:

  • Many pages are displaying the error message: “This blockBlock 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. contains unexpected or invalifd content.”
  • The error is also displayed for pages that have recently been updated.
  • If you continue seeing this issue, please open a ticket in Meta.

There was also an issue brought up by @emmaht:

  • Some documentation has the block name italicized, while others don’t. (Post Author Block vs Post Author Block)
  • There doesn’t appear to be an answer in the Documentation Style Guide.

Answers are awaiting upon @femkreations’s return.

Reclassification Project

@estelaris let new contributors know that part of the redesign of end-user documentation (HelpHub) is removing any articles that are for developers and/or to remove any developer jargon that is in the articles. These such articles are being reclassified into categories that make more sense and migrating others to DevHub or developer documentation.

@javiercasares spoke about successes with the Advanced Administration Handbook over WCUS Contributor’s Day online over the past weeked:

  • @javiercasares opened 38 tickets, and 20 pages were formatted.
  • Content is being copied in HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. from the HelpHub index, then created in markdown, and redirected to the Advanced Admin Handbook.

@javiercasares noted that the process for this is as follows:

  1. Create the structure. (empty files)
  2. Copy the original content into the new files, (using markdown) while changing the least amount as possible.
  3. Check all the pages for links, and old content, and try to renew it.
  4. Launch the new Handbook.

Noting that old pages in HelpHub will be redirected to the new ones in the Advanced Admin Handbook.

#meetings, #summary

Abha Thakor 11:30 am on August 17, 2022
Tags: , summary   

Summary of Docs Team Biweekly Meeting August 16, 2022

Housekeeping

Attendance: @milana_cap, @chaion07, @javiercasares, @ashiquzzaman, @atachibana, @femkreations, @greenshady, @piermario, @brightemeka, @krupalpanchal, @emmaht. Asynchronous updates from @lucp and @estelaris.
Where: #docs channel on SlackSlack 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/08/16/agenda-for-docs-team-meeting-16-august-2022/
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

Project Updates

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 pingPing 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:

Reclassification project

@estelaris: no new updates

Other 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 blockBlock 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-CLIWP-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 MetaMeta 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. 

Open Floor

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.

#meetings, #summary