Onboarding to Documentation team

Here is some quick info you need in order to start contributing to Documentation team.

Accounts:

Places:

  • Blog – for meeting agendas and summaries (and anything related to Docs team).
  • Slack channel #docs – where meetings are happening (and all communication regarding the team itself).
  • GitHub repository – where issues for all documentation are reported, discussed and worked on.
  • Handbook – how to contribute to the Documentation team (it’s a bit out of date).
  • Style guide – for how to write WordPress documentation.

Meetings (alternating every week) on Tuesdays at 2PM UTC:

  • Regular meeting with agenda published on our blog.
  • Issues triage where we discuss issues from the 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/ repository.

Live onboarding sessions

We recorded onboarding sessions for everyone interested in getting started with the Documentation team. We know that our “Getting started” documentation is out of date and getting involved can be very confusing and frustrating so we hope to ease the process with these sessions.

Overview

Recording: https://wordpress.tv/2022/06/21/milana-cap-overview-onboarding-for-wordpress-documentation-team/

A more recent onboarding session, recorded on 28th July 2023, can be found here: https://wordpress.tv/2023/08/01/jenni-mckinnon-milana-cap-wordpress-documentation-team-onboarding-july-2023/

End user documentation

Developer documentation

Developer documentation – PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party handbook

Developer documentation – Common APIs handbook

Developer documentation – Code reference handbook

Developer documentation – 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 handbook

Developer documentation – Themes handbook

Contributor documentation – Documentation team handbook

Github related roles

If you have any questions or you’d like to have an “in more detail” session, feel free to leave the comment below.

Summary for Docs Team Discussion Meeting (07-May-2024)

Attendance

@milana_cap @leonnugraha @sagargurnani @lumiblog @atachibana @estelaris @samanthaxmunoz @marcio-zebedeu

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meeting 

Project Checks

@lumiblog expressed commitment to working on #1496 and #1497 this coming week. 

@milana_cap has been writing an article for the code dev blog in the past week. 

@leonnugraha reviewed and closed #1289 and #701.  He combined and updated some unassigned and abandoned issues. He also updated some issues’ labels.

Open Floor

Members voted and finalized that the following would be the new meeting names:

@milana_cap was asked to update the meeting names on the Make WordPress Documentation page. 

@estelaris shared that she has been:

  • Creating the project plan and tickets for the translation project for the Spanish team. She mentioned that the project plan and tickets can be viewed at this link.
  • Reviewing and testing the mobile documentation. She expressed that she had never used the WP app before and found it quite cool, adding that testing takes time.
  • Creating tickets for screenshots/videos for the mobile app articles she reviewed. She mentioned that these tickets will be updated by @samanthaxmunoz and her team at WP Engine, noting that they are good tickets for new contributors.

@estelaris also announced that there will not be a Monthly Planning Meeting on June 11, as the team will be on their way to WCEU (WordCamp Europe) and will have a contributor day on June 13.

The members discussed renaming the “Installation” categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. on the WordPress documentation site, as the articles currently in that category do not really fit under installation. The articles are:

  • Hosting WordPress
  • SEO
  • Automated Installation
  • Troubleshooting Login Issues

@leonnugraha suggested renaming it to “Setup”. @sagargurnani thought “Automated Installation” could stay in that category, but the other articles should move elsewhere.

@milana_cap raised concerns that “Setup” is too broad and other things like installing themes/plugins, customizing, etc. could also fall under that category name.

The team decided to table the discussion for the next meeting to allow folks to think about a better category name. In the meantime, @estelaris moved the “Troubleshooting Login Issues” articles to the FAQs section.

#docs, #meetings, #summary

Agenda for Docs Team Biweekly Meeting (07-May-2024)

The next meeting is scheduled with the following details:

WhenTuesday, 07-May-2024 14:00 UTC

Where#docs channel on Slack

Agenda:

  1. Attendance.
  2. Note-taker and facilitator selection for the next docs team meeting.
  3. Facilitator selection for the next triage.
  4. Project check.
  5. Design updates by @estelaris.
  6. Open floor.
    • Finalize the new meeting names.

If there’s anything you’d like to discuss on the open floor, please leave a comment.

#agenda, #docs, #meetings

Summary for Docs Team Meeting (30-Apr-2024)

Attendance

@estelaris @milana_cap @lumiblog @shawncontant @pooja9712 @atachibana @marcio-zebedeu @ashiquzzaman @sagargurnani (async)

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meeting

Project Checks

@shawncontant had completed #978 and which is now ready for the 1st review. As per his request @leonnugraha assigned him another issue i.e. #1500.

Open Floor

  1. @shawncontant asked that the issue which is assigned to him is getting updated to WP 6.3 but WP 6.5 is the latest version. So, isn’t the 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/ issue itself supposed to be labelled as 6.5, to which @milana_cap answered that sometimes the feature hasn’t changed so updating to earlier versions is still valid for current version. On other times, when we have the same features updates marked for current and earlier versions, then we ignore the earlier version and document only the current one.
  2. @milana_cap had mentioned that in the last 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/. meeting which was held on Tuesday 23-Apr-2024 at 14:00 UTC the attendees had discussed and suggested alternate names for the docs team meetings. And, then she had requested the team members to provide their suggestions or if they have any questions regarding the new meeting names.
    • Biweekly Meeting -> Discussion Meeting
    • Contributor Day -> (We will keep it as it is)
    • Issues Triage -> Monthly Planning Meeting

#docs, #meetings, #summary

Summary for Docs Team Meeting (16-April-2024)

Attendance

@milana_cap @leonnugraha @sagargurnani @lumiblog @atachibana @shawncontant @estelaris @vishalmukadam @ppeeranatd @jeffr0

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meeting

Project Checks

@estelaris is working on all her tickets at Yoast 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 has been mostly reviewing Playground docs in anticipation of Yoast’s Contributor Day, where we’re going to help improve them.

@leonnugraha reviewed and updated #1323.  He also reviewed and closed #1342 and #1341.

@sagargurnani is doing a 2nd review of  #490 and will look into other urgent issues. 

@shawncontant expressed commitment to working on #978 this coming week. 

@atachibana shared progress on #464.

@ppeeranatd is working on #1514

Open Floor

@estelaris shared that it’s official that 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. for Documentations will be happening in October 2024. The WordCamp will be a 24-hr online event to cover all time zones.

She will post a general plan on the Make WordPress Docs Blog and then open a website with a call for organizers.

Will officially invite other teams that work on documentation like support, training and anyone that updates a handbook under dev.wp.org to join.

Anyone who wants to be an organizer or a speaker is encouraged 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.” @estelaris.

@estelaris also noted that next time on the agenda will not be an @estelaris update, but a WCDocs update.

On another topic, @estelaris updated that The Spanish community is ready to start translating HelpHub.

@milana_cap shared that Yoast Contributor Day will happen on Thursday, 18th April, and everyone is welcome to join. 

Props to @estelaris and @sagargurnani for helping with reviewing the post.

#docs, #meetings, #summary

Agenda for Docs Team Biweekly Meeting (16-April-2024)

The next meeting is scheduled with the following details:

WhenTuesday, 16-April-2024 14:00 UTC

Where#docs channel on Slack

Agenda:

  1. Attendance.
  2. Note-taker and facilitator selection for the next docs team meeting.
  3. Facilitator selection for the subsequent triage.
  4. Project check.
  5. Estela’s (@estelaris) updates
  6. Open floor.

If there’s anything you’d like to discuss on the open floor, please leave a comment.

#agenda, #docs, #meetings

Summary for Docs Team Meeting, 2 April 2024

Attendance

@milana_cap @leonnugraha @sagargurnani @lumiblog @noumantech @pooja9712 @matteoenna @calolan @ppeeranatd @flexseth @estelaris

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Biweekly Meeting

Project Checks

@sagargurnani completed #954.

@milana_cap mainly focused on Playground – reading existing docs and making plans with @zieladam and @flexseth on how to improve it. @milana_cap also closed a couple of used docs issues during 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/..

@lumiblog shared the progress of #1492.

@Leonnugraha expressed commitment in working on the ‘needs review’ this coming week 

@calolan shared the progress of #1291 and #1198. @estelaris shared the list of open issues for the 6.5 release – HelpHub: #1490, #1491, and #1492.

Open Floor

@estelaris   shared an update that The Spanish community had begun updating their style guide and had established weekly meetings on Fridays at 9 UTC. A post is already in draft and will be published soon (both in Spanish and English).

@flexseth sought clarity on documentation issues within WordPress Playground, facing challenges with PR submissions. @milana_cap suggested specific 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/. channels for support.

@estelaris highlighted ticket management, referencing #1525, and stressed understanding team procedures to avoid burnout.

@milana_cap advised @flexseth to attend relevant meetings, suggesting the #marketing team for SEO concerns. 

props to @lumiblog for taking notes during the meeting.

#meetings

Translation of End-user documentation project started at WordCamp Torrelodones (Spain)

During the 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/. at 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. Torrelodones 2024, the Spanish documentation team started the translation for the end-user documentation.

The initial objectives were:

  • Decide the day and time for the weekly team meeting
  • Define responsibilities for meeting facilitators
  • Technical requirements for a documentation team member
  • How to effectively coordinate with the Spanish translation team
  • Review the Style Guide for translation
  • Define the translation process
  • Suggest new words to the Spanish (Spain) Glossary

Conclusions of the Spanish documentation team

Weekly meetings

Responsibilities for meeting facilitators

  • The team agreed that @estelaris will run the first few meetings and then it will be rotated among contributors
  • Whoever runs the meeting must prepare the agenda based on the previous meeting

Contributor technical requirements

  • Know sufficient English to understand the content that is being translated
  • Be familiar with the Spanish style guide and glossary
  • Basic understanding of 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/

Translation Style Guide

Another goal is to improve the Spanish Style Guide to be able to write the documentation, following the rules already instilled by the translation team. This work will be based on the Documentation Style Guide written by the global team. Follow the work in GitHub Spain Handbook #288.

Translation process

The translation process the team will follow includes:

  • Update the style guide and have it reviewed and approved by the translation team
  • Prioritize articles for translation (high, medium, low) as well as add tasks to the issues (content, screenshots, videos, etc)
  • Work with #meta team to open the es.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//documentacion site
  • Translate the articles and pass them to the Spanish 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/. for review
  • Make the documentation available in Spanish from Spain as soon as the site is set

This post will be updated accordingly and it is a translation of the post in Make Spain Blog.

props to @josepmoran for taking notes during contributor day and to help write this post in Spanish

#contributor-day

Agenda for Docs Team Biweekly Meeting (02-April-2024)

The next meeting is scheduled with the following details:

WhenTuesday, 02-April-2024 14:00 UTC

Where#docs channel on Slack

Agenda:

  1. Attendance.
  2. Note-taker and facilitator selection for the next docs team meeting.
  3. Facilitator selection for the subsequent triage.
  4. Project check.
  5. Estela’s (@estelaris) updates
  6. Open floor.

If there’s anything you’d like to discuss on the open floor, please leave a comment.

#agenda, #docs, #meetings

Summary for Docs Team Meeting (19-March-2024)

Attendance

@estelaris @milana_cap @leonnugraha @sagargurnani @hellosatya @marcio-zebedeu @lighthouse79 @atachibana @anandau14 @noumantech @sheebaabraham @matteoenna @lumiblog  @Calolan

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Biweekly Meeting

Project Checks

 @sagargurnani completed #430 and #935 and waiting for the review of #954.

@leonnugraha reviewed the drafts of the dev notes and published the Miscellaneous Editor changes in WordPress 6.5.

 @Calolan shared the progress of #1308 and #1476.

@milana_cap shared the update on the CloudFest hackathon contribution but could not contribute to docs projects.

 @sheebaabraham shared the progress of #1371 and showed commitment to complete it soon.

@estelaris started the user documentation for the 6.5 release and needs help from new contributors to get screenshots and a small video

@lumiblog shared the list of in-review issues (#1299, #1313, #1281, and #1280) and closed issues.

Open Floor

@estelaris shared the list of open issues for the 6.5 release – HelpHub: #1490, #1491, and #1492. He would also open more issues.  @sagargurnani and @estelaris discussed the March 5, 2024 updates post; @sagargurnani responded that he contacted Adam to help him document the playground.

@estelaris explained that two main items need help: users’ and developers’ perspectives in the documentation and review on the last item to improve the changelog in the articles. He also plans to write end-user cases after I finish the 6.5 release docs.

@sagargurnani asked a question about a few articles that have change logs and a few haven’t. @milana_cap explained that Changelogs were made when @bph ran 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 end-user docs, and she had them in an article template. The rest of the docs never caught up. @estelaris said changes are happening at design side, will look into it later.

#docs, #meetings, #summary

Agenda for Docs Team Biweekly Meeting (19-Mar-2024)

The next meeting is scheduled with the following details:

WhenTuesday, 19-Mar-2024 14:00 UTC

Where#docs channel on Slack

Agenda:

  1. Attendance.
  2. Note-taker and facilitator selection for the next docs team meeting.
  3. Facilitator selection for the next triage.
  4. Project check.
  5. Estela’s (@estelaris) updates
  6. Open floor.

If there’s anything you’d like to discuss on the open floor, please leave a comment.

#agenda, #docs, #meetings