Summary for Docs Team Meeting 5 August 2019


@kenshino @milana_cap @atachibana @netweb @clorith @ibdz @leogermani @casiepa @kartiks16 @softservenet

Content Migration from Codex to HelpHub & DevHub:

@atachibana provided update spreadsheet:

Redirection has been started from Codex to DevHub (Code Reference) and writing down detail steps so that other contributors can follow.
There are two types of items:
1. simple redirection
2. After some inline docs modification and redirection
*in case of 2, contributors need knowledge of Trac

@kenshino asked for statistics. @atachibana reported below:
18.93% (170/898) of Functions have been redirected.
@kartiks16 offered to help with the continuance

@kenshino asked if Hooks had progress. @leogermani reported that he’s started working on them, mapping what needs to be done.
(Hope to get 50 most accessed ready to redirect this month)

@leogermani posed a question:
see this example:
There is a related article section down below, and other related links to the docs.
What do you think is best to do? Keep the links pointing to the codex? are they being migrated as well?
*”related articles” section

@kenshino replied that most are already likely in DevHub.
(The Loop is likely an article in Theme/Plugin handbook for example
Code Documentation – some of them could already be redirected)
@kenshino suggested to take this as an overall epic task to redirect/migrate code references that aren’t already
*and also finish the example posed in the question at the same time

@leogermani looked for this one and didn’t find. “query overview” ->
@atachibana suggested it should be included in Common API handbook.
*general programming topics are covered by it

@leogermani asked for another tab to be added to the tracking spreadsheet in order to track these, @atachibana confirmed he will do this.

@kartiks16 offered to help in this process

@kenshino asked if WP_Query was redirected yet. @leogermani reported it is and pointed out that some h3 titles are not being added to the TOC for some reason.

@atachibana pointed out that If there are no other I18N pages, then automatic redirection tag will be inserted. In this case, other language pages exist so there is a link

HelpHub Development:

@milana_cap: While working on trac patches I realised that having separate git and svn repo is a small nightmare so I’ve been looking for a way to work on them in the same local repo. I’m writing bash script to make it easier for everyone else to get this set up in their locals, for both, first timers and people who already have installations.

@netweb reported that he has making these synced to make contribution easier on his task list.

@milana_cap posed her idea to have one branch in out github repo dedicated to production, where we would create the actual svn patches. @netweb liked the idea.

@kenshino and @milana_cap agreed since @netweb has already been working on a plan for this scenario, that he and @sergey be involved.

@kenshino and @mailana_cap reported lost ssh access on HelpHub Staging. @clorith reported that he has it and should be able to add back, will look at when back from being off.

Docs Team Handbook:

@milana_cap suggested that in order to get this together, that it be split so that appropriate people are responsible for their part of it. @atachibana is already spearheading editing HelpHub content parts.

@kenshino suggested a Zoom call after the HelpHub Meeting.

Rosetta Sites – HelpHub Deployment Progress:

@casiepa reported Japan is done:
*Meta is waiting for some fixes before further installs, such as the planned Serbia.

@netweb was asking for documentation on this. @kenshino reported one of the issues were the article slugs, which is done now.

@casiepa reported being ready to deploy all active from the moment the green light is given (and some basic instructions if required)
Serbia is planned first, then there are 6 or 7 following that are on the list. Then there will be a transition to deploying all the Rosetta sites that have /support active.

@kenshino suggested giving the proper time to gather feedback after Japan and Serbia.

Centralised API Handbook:

@kenshino asked for updates on the API Handbooks and also the API inclusions. @casiepa reported these are actively on his task list and @atachibana reported he will be following as well.

@kenshino suggested @atachibana nominate somebody to lead the effort. First step could very well be moving the common topics over e.g. – The Loop, Internalization, etc.

@leogermani offered to help with the internationalization topic (he’s already been looking into this and had discussions with Polyglots at WCEU).

Who’s in the Docs Team:

@kenshino reconfirmed the list of current Docs Team Members from July.

-HelpHub Development Lead: @milana_cap, @clorith
-HelpHub Developers: @felipeelia @ajitbohra @audrasjb @carl-alberto @kafleg @wizzard_ @softservenet @mukesh27 @william68
-Content Lead: @atachibana
-User Notes (DevHub) Curator: Open
-Theme Handbook Lead: Open
-Plugin Handbook Lead: Open
-More Info (DevHub) Curator: @juliobox
-Regular Contributor: @aurooba, @leogermani
-Design Lead: @ibdz, @estelaris
*Since then, @acalfieri has come in as Theme Handbook Lead
*Docs Team Handbook Lead will also be @milana_cap and other leads are expected to help in relation to their parts

@milana_cap and @kenshino will work to define details on Doc Team Handbook on Zoom call.

@kenshino suggested that the label “Lead” may be redefined as it can cause confusion with the Make /WordPress Team Leads.