Summary for Docs Team Meeting 13th January 2020

Facilitator & Attendance

Facilitator: @leogermani

Attendance: @bph, @atachibana, @milana_cap, @kartiks16, @kenshino, @audrasjb, @pbrocks, @WPZA, @aurooba, @ibdz, @nullbyte, @estelaris, @felipeelia, @tomf, @felipeloureirosantos, @marcio-zebedeu

Note-taker: @kartiks16

Next week Facilitator: @felipeelia


Discussion on the Docs team organization in general Workflows

We added current workflows to this trello card -> | If anyone wants access they can approach @milana_cap

For now, we have a few workflows defined. We are missing on reporting an issue: 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. for developers handbook | any dev handbook | docs team handbook | HelpHub content

@milana_cap will add workflow of reporting the issue in tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. and link to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook for contributing.

@leogermani will add info on DevHub

For Gutenberg dev handbook we have a workflow defined by @pbrocks


@milana_cap started the discussion in p2, all are requested to share their thoughts.

Docs Team Handbook
Workflows and badges pages:

Once we have all those things defined we can add those pages to docs team handbook

Progress of the survey :

@atachibana is working on the progress

Helphub Localization

We have it here:

@felipeloureirosantos suggested that they don’t have updates there so far as well. There will be in the next weeks.

We have slackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at channel #meta-helphub as a contact point between our team and 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 to get updates on this and speak with them about this issue.

@felipeelia mentioned here is a meta ticket for that too. @milana_cap will bring some more information on this in the next meeting. @kenshino suggested bringing @netweb to share thoughts

General topics

@joyously brought the topic of Custom Fields article in HelpHub (, which is missing some information on how to diplay the custom fields (original codex article:

@Kenshino (Jon) and others argue that this is end-user docs and should not have this kind of information. It should have a link instead.

@felipeelia suggests to link it to:

@leogermani will make the edits on this topic

Remove paragraph of BitNami in the multisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core. considerations article

Topic brought by @René Hermenau. The pege mentioned is Everyone agreed to remove it. @atachibana will do it.

Improve docs on Multisite

Also a topic that @René Hermenau suggested, make it clearer that Multisite is a choice that brings more complexity to the installation. A quick discussion came up on how to show pros and cons so people can make a informed decision. @nullbyte would be volunteering it.

Plugins Handbook i18n

@Pascal might be able to help.

Specific headers, this kind of stuff needs to be there, @milana_cap will do that.


Updates from @atachibana : We redirected 314 of 1069 (29.4 %) of Code Reference’s Functions part

Open Floor

@bph shared that we made progress on the meta-trac ticket. feel free to comment,

@bph asked should the documentation for Gutenberg End User have a section for features only available in 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? They are future features for Core, so it might make sense to have future features/changes. to which @leogermani responded as long as it’s clear that it’s not available in core yet, and @kenshino mentioned it should only feature Core info

@kenshino shared few small things i.e. He started a thread in the Advanced WordPress Facebook group, if you are in the group. Some interesting comments so far. It is noticed that many people still don’t know that we’ve stopped updating Codex. We ought to talk about WC Asia Contributor Day and plan properly for it very soon.

@leogermani mentioned In the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. of our page on 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. we have, under “Want to get involved” a phrase that says “the many Contributor handbooks” linking to our handbook. Shouldn’t it just say “Documentation team handbook”? Also, he thinks the contents of the header should also be subject to a review now that we are reviewing everything and to which @milana_cap & @kenshino suggested that we will alter it.

#meetings, #summary