Summary for Docs Team Meeting: April 6, 2020


@milana_cap, @chaion07, @sasiddiqui, @atachibana, @christiano.zanca, @kafleg, @softservenet, @ataurr, @marcio-zebedeu, @bph, @yui, @sukafia, @aion11, @estelaris, @nobnob, @stefanocassone, @kenshino, @themiked, @joyously

Notetaker & Facilitator Selection

Note @chaion07

Notes Reviewed by: @milana_cap

Facilitator for the next meeting: @sukafia

Next Meeting will be held on: April 13, 2020

Categorization Project, Alterations Workflow (discussion)

@estelaris shared the link of the spreadsheet for the project. She suggested that the entire team should start adding stories to that page, so we can conclude on the main categories and the subcategories the idea is that we can think as a user, following the workflow to build a site. The names in brackets were meant more like the article, not the categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging..

@milana_cap advised that the text in brackets should be of raw categorization and if it can be moved to a separate column and there was no mention of User.

@softservenet asked if any decisions were made to use themes on those 3 labels.

@themiked added saying that he wants to pay better attention at his local WP beginner meetups (whenever that takes place the next time) and see if there are questions asked which would be a good fit here.

@softservenet pointed that we had 3 main categories decided from the previous meeting.

@milana_cap emphasized moving it to a separate column as it can possibly be a mess after over 10 stories has been written.

@themiked warned as soon as we start to try and funnel towards predefined categories, those categories will start to define the questions. Categorization should be the last step, if it’s even needed at all.

@milana_cap invited everyone to add more user stories and use existing ones as an example.

@estelaris further added categorization is needed to improve search but yes, that is the goal for this exercise. She also encouraged everyone to bring a predefined categorization for the next meeting so that we can discuss it.

@milana_cap asked @estelaris about the deadline for ‘User Stories’ to which @milana_cap suggested to have 7 days to add as many stories as possible.

Project Updates

@atachibana provided updates on Re-routing of the Codex page to Code Reference for Functions, where 443 out of 1069 that is 41.4% is complete Thanks to @stevenlinx (as always). He also mentioned that @collinsmbaka and @sukafia had also contributed to the cause.

@estelaris reminded everyone to add their respective WordPress Usernames to the working document so that it can be added to the contributors list at the end of the project.

@chaion07 reported that he had applied for the HelpHub for BN_BD to be added to the site with a support ticket.

@christiano.zanca informed that the Italy HelpHub Team is using the italian Polyglots way of translating: using Google docs and some sorts of per-translation methods. Thus it is taking longer than usual. @milana_cap asked if it would be moved to Rosetta later and if so then it should be alright. This is a huge project and every team should find their own way to be most productive. @christiano.zanca shared the link of the tool they are using: ttps:// to which @milana_cap suggested of another one that she had developed which compares locale with original including the last modified dates so you can see if your version is outdated or not. Link:

@themiked provided updates on the 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 Plugin Directory or can be cost-based plugin from a third-party handbook that he is 20% through reviewing content and converting from classic blocks into actual blocks. He discussed having 2 items specifically. The first one is the external linking, which is also being discussed in the blog. While visiting the cpt section it seemed natural to link to generatewp, but we need a decision beforehand. So this is more of a reminder. The second one is that the plugin related content in the codex seems to be much more feature complete, so if it should be rolled into the plugin handbook, or we should be referring to it. Either way, having the same or similar content in two places may seem confusing and wasteful. @milana_cap shared the associated link: She further added that it is wasteful and a nightmare for maintenance. She further suggested that the next step should be to create the list of exact content and then we can decide if it should be moved to developer handbooks or somewhere else or just leave it as is.

@joyously questioned on the perspectives of the write up should be either on using a plugin or writing  for a plugin. To which @themiked replied with both revolve around writing and suggested a link: and more generally

@atachibana added that our big goal is the retirement of Codex. So the required portion should be moved to the Plugin Handbook or appropriately handbook, developer hub or so.

@themiked summarized with a suggestion that he’ll get through the existing content and then slurp it in and eventually get through the existing handbook content, then slurp in the Write a Plugin content.

Handbook Revamp

  1. Facilitating weekly meetings
  1. Reporting an issue workflow
  • @milana_cap shared the link to TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the team uses for example: board: further added, the second one is not really a draft and requested others to add their items and steps. The idea is to help people report issues for every docs project by following simple step-by-step instructions.
  • @softservenet shared the idea of creating a card for each discussion issue (with the minimum summary information) and posting it in SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at, same for new issues. Eventually we’ll work on transferring the information to the actual document. That way, for new issues, we can always direct to the card for required information and we’ll have a better understanding of it hopefully.
  • @bph didn’t report any progress. Except discussing with @jdy68 about reusable blocks in English pages, that don’t show up for translators. Link:

Open Floor

  • Google Season of the Docs

@kenshino reported that he reached out to @chanthaboune to talk about the Season of Docs and is currently waiting to hear back. He is assuming to maybe get some updates in the coming week. @milana_cap agreed and also added that we wanted to do it last year as well but now it’s a good time for us to get professional help on writing technical docs. Link: @softservenet inquired on what would our suitable position be in this? @milana_cap shared the idea as a reply that the Docs Team to be working with professional technical writers. We will explain to them what WordPress is and how it works and they will help us write better technical docs. @kenshino shared the details with the organization terms. Link:

  • Categorization

@estelaris was interested to join in the discussion of categorization as she thinks that she has lots of info to provide and we will need help to finish up that part of the project. @softservenet replied, If @milana_cap takes the lead, I’d be willing to accept some type of position in this structure.

  • Mentoring Program Proposal

@sukafia felt the need to have someone who would focus on helping with the on-boarding of new members. That’s instead of everyone focusing on contributing to docs, helping new members settle in and this role should be recognized as a contribution to the Docs team. Updates should be given for new members and they should be followed up until they find a footing. He further added that it was difficult to settle in and had recently discussed with new members who feel the same way. @milana_cap agreed, that we are aware of it and we have been thinking about that problem for years. One solution could be to have mentoring program as suggested. She further added saying, every team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. should be mentor for their project but we don’t have enough people to mentor and do the work and if we have one mentor for all, it wouldn’t work. She even requested @sukafia to write a p2 post about that and we can all discuss it there. @kenshino suggested that the person doesn’t have to know everything about all projects – just where they can get started and a general high level understanding would be good enough. @sukafia expressed his interest in volunteering for this role if we decide it’s necessary. @softservenet A newer person would be better in tune with the challenges of getting started. Many of us have the history from meetings and the continual process, so they would better understand that challenge

  • Handbook

@estelaris asked if there is a page in the handbook that discusses the projects that the team is working on? The design team has a FOCUS page only for that. I assume it’s often updated. Here is the page and yes, it is often updated @milana_cap said that she’ll add this to ‘the to do list’ for Handbook.

Transcript of the meeting can be found here on slack

Thank you all & please stay safe!

#meetings, #notes