Summary for Docs Team meeting 13 May 2019


@kenshino, @milana_cap, @chrisvanpatten, @justinahinon, @atachibana, @naveenkharwar, @audrasjb, @ibdz, @mkaz, @aurooba, @asif2bd, @truongwp, @coffee2code

Content Migration from Codex to HelpHub & DevHub

@atachibana remembers that the first priority is redirecting Codex Pages to matches HelpHub Page. The guidelines for migration have been updated here: The WP_Version pages are redirected at 50%.

The Docs Team is also still focusing on redirection on HelpHub before moving to the redirection on DevHub.

HelpHub development

@milana_cap is working on creating a guide for contributing with the code for HelpHub on Trac. The next thing to focus on will be to get it to a state where the installation script sets the project up easily.

Gutenberg Handbook

@coffee2code announced that the technical side of the migration of Gutenberg Handbook is almost ready and is now released on There are still a couple of things to test including the redirects that currently syncs from a branch.

Use of the More Info section in Code reference

@juliobox previously introduced a question about the best way to use the More info section:

The suggestion is interesting since that area could be useful as the user notes section, that can often be tricky and confusing. @atachibana and @kenshino thus suggested we should think about a better implementation for the More Info section. It could whether be a link to a handbook page that explains it further or some selected examples (self made or taken from user notes).

Any other comments or suggestions for this section are welcome and can be done into @juliobox post here:

Centralised API Handbook

@kenshino suggested the entire API section (or most of it) inside a proper handbook that will cover both WordPress and APIs. Since there are not a lot of APIs, it will make sense to have all of them in one place.

Who’s in the Docs Team?

The Docs Team currently have a lot of contributors and many don’t stay long among other things because what is expected from them is not always very clear. This could be fixed by naming contributors a portion of the Docs Team duty to take charge of.

More informations about the Docs Team can be found here:

It could also be useful to assign contributors that want a team to lead, as:

  1. Docs Team Lead
  2. HelpHub Development Lead
  3. Content Lead
  4. User Notes Curator?
  5. Theme Handbook Lead?
  6. Plugin Handbook Lead?
  7. And more?

You can read a transcript of the meeting at :slack: