Summary for Docs Team Meeting 21 October 2019


@atachibana @softservenet @fahimmurshed @kafleg @verygoode @kenshino @fierevere @ibdz @audrasjb @leogermani @themiked @felipeelia @milana_cap @nullbyte


Today we started with new meeting format. In order to make meetings more useful we want to try to keep updates as short as possible at the beginning of the meeting (or maybe even during day prior to the meeting).

Most of the meeting will be dedicated to one specific part of Docs team responsibility ― HelpHub is published and it will no longer have dedicated meetings every second week.

The rest of the meeting time will be used for quick discussions/decisions on any other part of Docs team work.

Also, whenever possible, it would be good to close the meeting with clear tasks for the next meeting.

Facilitators and note takers will be rotating. At every meeting one volunteer will be assigned for the next meeting.

Read more and leave feedback/suggestions on new format:

HelpHub Updates

  • Content: 241 of 1068 (22.6%) pages were redirected. Last week was 230 of 1068 (21.5%).
  • Design: The team for WCValencia prepared some designs, but @estelaris needs to go through and to clean them up before presenting. Leave feedback for Home and CategoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. pages here:
  • Development: Development is blocked and waiting for designs and GITGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the released code are all centrally managed through SVN. shared repo.
  • Localisation (Rosetta release): More Rosetta sites got HelpHub activated. We are waiting for #meta team to import original HelpHub content. @audrasjb is going to open TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. ticket to hide automatic link to forums for locales that don’t use forums at .org.

Common APIs

@leogermani is proposing moving all documentation on internationalizing 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. and localising WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., themes and plugins to newly published Common APIs Handbook. He will try to create all the necessary pages this week. After review the old pages from other Handbooks and Codex can be redirected.

Read more, leave feedback/suggestions and offer your help here:

Next Meeting

Next meeting will have focus on Docs Team Handbook. Everyone are invited to review their parts of Handbook and indicate things that are missing or are out of date. A plan on adding/fixing these should also be made.

What is my part of Handbook?

Every project has its part in Handbook. You know the best how to contribute to project(s) you are involved with and, therefore, you know better than the others if Handbook is complete and up to date for that specific project.

The team page is mapping responsibilities and will be used as general guide for Handbook parts ownership. If you are missing from the list or your responsibilities have changed since Team page was created, do let us know and we’ll fix it. Or you can fix it yourself.

Next meeting will be run by @felipeelia and will happen on

Monday, October 28, 2019, 15:00 UTC

Transcript of the meeting can be found here: