Online monthly Docs Team Contributor Day May 23, 2023

The Documentation Team holds an online, monthly Contributor Day on the fourth Tuesday of every month. Any one may join who wishes to contribute to the team and who follows the Code of Conduct.

The next Docs Team 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/.

The next monthly online Docs Team Contributor Day will be:

When: Tuesday, 23 May 2023, 1:00-4:00 PM UTC

Where: #docs channel on Slack, and on Zoom.

Please also see Contributor Day — 23 May, 2023 on 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 onboarding and other important details.

Onboarding on Zoom

In addition to the details in the GitHub issue for this Contributor Day, folks who are in need of onboarding can ask 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/. or on the Zoom call. In Zoom, a breakout room will be started where contributors can be onboarded.

If at any time you have any questions, please feel free to ask in the #docs channel on Slack or in Zoom throughout the day.

After Contributor Day

Other than celebrating with some 🍪🍪🍪 after Contributor Day is over, please also comment on the corresponding GitHub issue with:

  1. Your 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/ profile username
  2. What you worked on and include links when possible.

Or, just comment anything (such as your WordPress.org username) to let the team know you attended.

#contributor-day, #docs

Summary for Docs Team meeting, May 2, 2023

Attendance

@ninianepress @milana_cap @hilayt24 @chaion07 @femkreations @sereedmedia @medesigngood @leonnugraha @kafleg @sonalithakkar @ninthcoder @estelaris

Housekeeping

Find the complete Transcript of the meeting on Slack.

Project checks

@milana_cap closed 7 issues.

@femkreations completed issue 485.

@leonnugraha reviewed #695.

@larassattidn and 281.

Reminder about Docs Team 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/.

For all those that attended the last Docs Team Contributor Day, please be sure to comment on the corresponding GitHub issue with what you worked on that day.

The next Docs Team Contributor Day is May 23, 2023 from 1 PM UTC to 4 PM UTC.

Open floor

@milana_cap asked if there was any feedback from our last Contributor Day.

@ninianepress suggested breakout rooms in Zoom so that contributors who need it can be onboarded. At the next contributor meeting, we will ask if any one is in need of onboarding, then open a breakout room, as needed.

The team decided to continue with a 3-hour long Contributor Day and that the fifth Tuesday in May will be a triage meeting, following the week after our next Contributor Day.

@estelaris wrote Explorations for a notification form between documentation and Rosetta sites and would love contributor feedback in the comments.

#docs, #meeting, #summary

Monthly online Docs Team Contributor Day starts April 2023

In a bi-weekly Docs Team meeting, a quarterly and independently-led docs team 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/. was proposed, much like the first ever one that was held in 2022.

The docs team decided on a more frequent monthly schedule.

Other details were also discussed and decided on in the following bi-weeky Docs team meeting:

  • These contributor days would be three hours long each,
  • they would be facilitated by any one and every contributor in attendance who wants to do it including team reps, leads, and other key contributors who are able to facilitate,
  • a Zoom link will be made available for contributors to meet as well as the #docs Make WordPress 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,
  • the contributor day would be announced,
  • an issue would be opened 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/ with onboarding details similar to the first iteration, and
  • contributors who attend need to comment on the GitHub post with the tasks they will work on during the allotted time or else note that they are in attendance.

New monthly structure to bi-weekly meetings

In the meeting previously mentioned, the docs team agreed upon a new monthly structure that would incorporate the monthly contributor day.

Previously, there was an ongoing rotation of the team and triage meetings week-by-week so that each worked out to be a bi-weekly meeting in Slack.

The new structure for these two docs team meetings are as follows:

  1. Week one: Docs Team meeting
  2. Week two: Triage meeting
  3. Week three: Docs Team meeting
  4. Week four: Online Contributor Day
  5. Week five: If there is a fifth week in the month, the docs team will have an extra week to catch up or it will be a triage meeting, as needed.

Please note: Week five is sometimes referred to as the “overeating” week by docs team contributors. It’s in reference to team meetings and the first online Docs Team Contributor Day where it’s common for kudos to be given when issues are noted by contributors as being completed by them. Kudos is often given in the form of 🍪 (cookie) emojis. Cookies and other desserts are sometimes also offered at the Docs Team table of the Contributor Day for in-person WordCamps.

The next Docs Team Contributor Day

The first monthly online Docs Team Contributor Day will be:

When: Tuesday, 25 April 2023, 1:00-4:00 PM UTC

Where: #docs channel on Slack, and on Zoom.

Please also see Contributor Day – 25th April, 2023 on GitHub for onboarding and other important details.

Summary for Docs Team meeting, April 18, 2023

Attendance

@leonnugraha @milana_cap @bph @atachibana @james-roberts @ninthcoder @ninianepress @cristianozanca @javiercasares @mujuonly @estelaris

Housekeeping

Find the complete Transcript of the meeting on Slack.

Project checks

@leonnugraha reviewed and closed five HelpHub issues.

@milana_cap worked on fixing six issues we got via HelpHub feedback form at the 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. Torino 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 is also monitoring HelpHub for new feedback.

@atachibana has completed issues #739 and #744.

@estelaris posted Integrating the Mobile app documentation into HelpHub.

Monthly Docs Team online contributor days

In the last bi-weekly Docs Team meeting, @ninianepress proposed a quarterly and independently-led docs team contributor day, much like the first ever one that was held in 2022, which was @milana_cap‘s idea.

@milana_cap suggested a monthly day, which was decided upon.

In the meeting mentioned above, the docs team discussed a new structure for weekly meetings that would include the monthly contributor day.

For details on this, check out Monthly online Docs Team Contributor Day starts April 2023.

Next Docs Team contributor day details and onboarding

The next meeting will be a monthly online Docs Team Contributor Day, following in suit with the new structure above.

WhenTuesday, 25 April 2023, 1:00-4:00 PM UTC

Where#docs channel on Slack, and on Zoom.

Please also check out Contributor Day – 25th April, 2023 on 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 onboarding and other details.

If you plan on attending and also on the day, be sure to comment on the GitHub issue with:

  1. Your WordPress.org profile username
  2. Link(s) to the issue(s) you were working on during the Contributor Day

Mobile app documentation structure

@estelaris posted on the Docs Team blog about the WordPress mobile app end-user documentation being integrated into HelpHub:

  • Two options for including the mobile app documentation include:
    • Create one categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. mobile app and all the topics as subcategory
    • Add each article inside the categories/subcategories we have now
  • The first option to create a new category was the final team decision.

WCEU Contributor Day Docs Team facilitator

For WordCamp Europe (WCEU) 2023 there will be a Docs Team table and @milana_cap will be leading it.

#docs, #meeting, #summary

Introducing the Advanced Administration handbook

During the recategorization of the documentation, the team removed several articles that were developer-focused or included a lot of developer-jargon. All these articles are now part of the Advanced Administration Handbook and will be removed from /documentation/devhub/.

The redirects have been applied as indicated in issue #59. Some articles have been merged to provide better explanations. Although, the maintenance is still ongoing, most of the articles have been updated.

Please report any issues to the documentation GitHub issue tracker.

Props to @ryelle and @javiercasares for working on this issue.

#docs

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

Call for volunteers to help with 6.2 end user documentation

The Docs team needs your help to update and revise the End User Documentation (HelpHub) for the upcoming WordPress 6.2 release, expected on March 28, 2023.

You can find a list of all the tasks in the 6.2 project board in the Documentation’s repo on 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/.

The tasks have been sorted into medium priority tasks and high priority tasks. The team plans to complete the high priority tasks by the 6.2 scheduled release date.

How you can help

If you are new to the Docs team, you can select from the list of good first issues.

If you are new to contributing to WordPress, you can review this onboarding post with training videos and links to help you get started.

Based on what you are interested in, review the medium priority tasks, high priority tasks or good first issues.

Mention in a comment on the GitHub issue you would like to work on and someone on the Docs team will assign it to you.

Once a task is assigned to you, the following two videos show how to help with updating the existing articles in End User Documentation (HelpHub).

Video onboarding to End User documentation

Video showing how to help with updating the existing articles on GitHub

If you have questions or need help, ask in the docs channel on the Make WordPress 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/. or directly in the GitHub issue itself. If your meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. or firm can give 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. of time to help, do include the Release co-leads for 6.2 documentation in your message: (Slack IDs) @bph, @zzap, @Femy, and @abhanonstopnewsuk.

Resources

If you need a test site with WordPress 6.2 pre-installed, you can use this app provided by InstaWP to spin up a new temporary website set. It is preloaded with Theme Test data and other pre-configuration, ready to go. This new site will be available to use for four hours. After that, if you need another test site to contribute to docs, you can visit the link again and create a new temporary site.


Props to @bph @webcommsat @milana_cap for collaborating and reviewing this article.

#6-2, #docs, #helphub

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

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

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