Milana Cap 8:00 am on June 13, 2022  

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.

Estela Rueda 4:17 pm on June 11, 2025
Tags: make.wordpress.org/ai,   

X-post: AI Chat Agenda – 12 June 2025

X-comment from +make.wordpress.org/ai: Comment on AI Chat Agenda – 12 June 2025

Jonathan Desrosiers 11:49 am on June 4, 2025
Tags: ,   

X-post: Criteria for Creating or Migrating Repositories under the WordPress GitHub Organization

X-comment from +make.wordpress.org/project: Comment on Criteria for Creating or Migrating Repositories under the WordPress GitHub Organization

Nikunj Hatkar 9:40 am on May 7, 2025
Tags: , ,   

Summary for Discussion Meeting (06-May-2025)

Attendance

@estelaris @divyeshk71 @azharderaiya @ravigadhiyawp @karthickmurugan @nikunj8866 @Dhruvang21 @DilipModhavadiya @70_Sense

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meetings

Please notice the new meeting timings below.

Open floor

@estelaris explained the steps for contributing to documentation:

  • Find issues like outdated info, typos, broken links, or missing ALT text.
  • Report or pick issues from the GitHub Issue Tracker.
  • Share your updates in the comments or using a Google Doc in the GH issue.

Onboarding videos are available for more help.

#docs, #meetings, #summary

Milana Cap 10:01 am on April 29, 2025  

Summary for Discussion Meeting (29 April 2025)

Attendance

@milana_cap @nikunj8866 @azharderaiya @karthickmurugan @zluck @divyeshk71 @devmuhib @ravigadhiyawp @Sumit Singh @kafleg @Zeel Thakkar @Dhruvang21 @Parth @noruzzaman

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meetings

Please notice the new meeting timings below.

Project Checks

@milana_cap created issues for 6.8, is reviewing 6.8 issues.

@karthickmurugan also worked on 6.8 issues.

Open floor

Q: I want to know how to contribute in docs

A: Here we have a bunch of onboarding videos: https://make.wordpress.org/docs/2022/06/13/live-onboarding-sessions-for-the-documentation-team/. And here’s the “Get involved” chapter in our Handbook: https://make.wordpress.org/docs/handbook/get-involved/. Do take a look and if you still have any questions, do not hesitate to ask in #docs channel.

Milana Cap 8:39 am on April 29, 2025
Tags: , ,   

Agenda for Discussion Meeting (29 April 2025)

The meeting is scheduled with the following details:

When: Tuesday, 29 April 2025, 09:00 UTC

Where: #docs channel on Slack

Agenda:

  1. Attendance.
  2. Note-taker and facilitator selection for the next docs team meeting.
  3. Project check.
  4. Open floor.

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

#agenda, #docs, #meetings

Sagar Gurnani 9:12 am on April 20, 2025  

Summary for Discussion Meeting (15-Apr-2025)

Attendance

@milana_cap @sagargurnani @utsav72640 @nikunj8866 @azharderaiya @flexseth @karthickmurugan @estelaris @n8finch (async)

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meetings

Please notice the new meeting timings below.

Project Checks

@milana_cap created issues for 6.8, is reviewing 6.8 issues and she is also scheduling updates for articles which should be published soon. She also published an article – “What’s new for developers?“.

@atachibana is reviewing and working on issues associated to the older WP versions like 6.3.

@nikunj8866 contributed to the #1894 issue.

Open Floor

@estelaris is getting ready for 6.8 release. She also mentions that during a release, the docs team updates 2 pages in HelpHub.

  1. WP Versions
  2. And the version page itself, see 6.7 as an example

Then these 2 other pages are also updated. we need permission to access them because the updates are manually done then they have to be pushed via WordPress sandbox (WP.org‘s backend).

  1. Roadmap
  2. History

She would be adding the above process to the handbook soon.

@flexseth asked whether it is still the best practice to install the the repo locally, then create a PR for submitting changes to the developer.wordpress.org? What’s the best way to submit simple fixes and also contribute code samples?

To which @milana_cap replied that if he wants to contribute to the installation itself, that’s #meta and he needs to install it locally. But, if he wants to contribute code samples, he just needs to submit the user notes to reference and someone will review and publish it from #core. 

Sagar Gurnani 1:52 pm on April 15, 2025
Tags: , ,   

Agenda for Discussion Meeting (15-Apr-2025)

The meeting is scheduled with the following details:

When: Tuesday, 15-Apr-2025 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. Open floor.

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

#agenda, #docs, #meetings

Milana Cap 8:43 am on April 10, 2025
Tags: announcements,   

[Announcement] New meeting times for the Documentation Team

Currently active Documentation team contributors voted on meeting times and we have a new set on trial:

Please note that these meeting times can and will be changed again if the team finds them unfit.

Meetings in April:

Meetings in May:

If you have any questions or concerns, do post them in the comments below.

#announcements, #meetings

Milana Cap 4:47 pm on April 2, 2025  

Proposal – the Documentation team meetings time

Lately, it has been noticed that the majority of attendees of Documentation team meetings are from Europe and Asia. Currently, team meeting time is 2 PM UTC, while online Contributor Days are from 1 PM to 3 PM UTC. This is not the most convenient time for the Asian community, especially from the Far East.

During the last meeting, it was concluded that Tuesday, as the meeting day, fits everyone. For the timing, moving back up to 5 hours could improve everyone’s experience and overall attendance.

Therefore, we propose the following options (NOTE: we will not apply a new time to the next meeting):

  1. Tuesday, 9AM UTC
  2. Tuesday, 10AM UTC
  3. Tuesday, 11AM UTC
  4. Tuesday, 12PM UTC
  5. Tuesday, 1PM UTC
  6. the same as it was
  7. something completely different (please, explain in comments)

Please let us know which option is the best for you in the comments. Also, keep in mind that Contributor Days last for 3 hours. They start 1 hour before the usual meeting and end one hour later.

Voting will be open until the next meeting, 8th April, to make sure everyone has enough time to add their vote.

Next meeting timeTuesday, 8 April 2025, 2PM UTC
Next online 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/. time
Tuesday, 22 April 2025, 1PM UTC

to

Tuesday, 22 April 2025, 3PM UTC

Sagar Gurnani 6:18 am on April 2, 2025
Tags: , ,   

Summary for Discussion Meeting (01-Apr-2025)

Attendance

@milana_cap @sagargurnani @estelaris @karthickmurugan @kafleg @Dhruvang21 @nikunj8866 @snilesh @sirlouen @stephenaturner999 (async)

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meetings

Project Checks

@milana_cap reviewed the issues completed by @karthickmurugan and she also has a list of duplicate issues to sort out.

@karthickmurugan had completed many issues which can be seen by here.

Open Floor

@milana_cap raised a concern that the majority of the team at the moment is from Asia. She believes 14:00 UTC is not the best time for the team to attend the meeting because it becomes very late for the team members living in APAC timezones. So, she would propose a poll for new meeting time that will include earlier hours on Tuesdays. The poll would be held today i.e. 02-Apr-2025 and would be initiated by herself.

@sagargurnani discussed how to attract more contributors to be the part of the #docs team and to work on the  #docs. To which @milana_cap said that it needs pushing and announcing it regularly on social media and every single 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. maybe we can work on docs per project, and treat every project as “job posting” create a call, share it everywhere record videos how we do stuff, so that people can be onboarded more easily maybe we need new onboarding stuff.

@estelaris mentioned Matt’s plan for one major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. per year and this will give us opportunity to catch up with all issues and documentation and there’s a need for a plan for that.

P.S. – Please drop your comments with your ideas for attracting more new contributors to the #docs team.

#meetings, #summary