Summary for Docs Team Meeting 15 April 2019


@kenshino @milana_cap @atachibana @chrisvanpatten @katebolin @makewebbetter @mkaz @joyously @chetan200891 @softservenet @subrataemfluence @otto42


@atachibana reported that more progress is needed for the items discussed at the last meeting:

Summary for HelpHub Meeting 8 April 2019

@atachibana is working on documenting detailed steps of transfer of Codex Pages.


@milana_cap reported that phase 1.5 issues on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. have started being confirmed. There are coming bug scrubs to make the final list and then it will be handed over (the list) to 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 so that they know what to expect in TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.

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. DOCS

@kenshino and @mkaz started discussion on Dev Handbook. @mkaz pointed out that there was a process for publishing from GitHub to specific locations. @kenshino suggested the migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. could be done by the Team manually as had been done in other cases successfully.

@kenshino pointed out that DevHub should be the repository for all Documentation vs. parting it out between locations.

@milana_cap has already announced that this might be a focus on the upcoming Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of There are many teams that people can participate in, each with a different focus.

@kenshino agreed that the main contribution point can be GitHub, but the output (display to public) should be DevHub. @kenshino and @chrisvanpatten pointed out that controlling the UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing./UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. of the documentation is also easier in DevHub.

@kenshino proposed:
1. Manually move all 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. to DevHub handbook
2. Point GitHub -> Handbook syndication to the correct spot (#1 can be skipped if this is easy enough)
3. Edit templates with content in place

@kenshino will write up a meta ticket after the consensus with the Gutenberg Team at this meeting and bring in @coffee2code to sort the workflow out.


@milana_cap and @kenshino will be volunteering. A volunteer from the USA was asked for and @mkaz asked to be included on the list for the USA volunteer needed to better cover timezones.


@kenshino is working on a P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at post which will be the discussion point for more specifics on badges.


WCEU opened registration for Contributor Day. @kenshino will be attending and @milana_cap is organizing, both will be drumming up interest for the Docs Team!

Meeting Time: This may not be working best for all. Those in Asia are having to stay up very late into the early morning hours (12:00am and later). People in USA are attending in the morning (8am). West Coast USA also has a time change that makes this meeting at 7am parts of the year. @milana_cap will write a P2 post for discussion to see if there might be a different time schedule that will allow more people to participate and be better optimized for those who regularly attend.

Inline Docs: @subrataemfluence asked about where to start for inline docs. @atachibana provided this link:

Inline Documentation

Codex Page Redirects: @joyously asked about how these are being handled and pointed out some inconsistency in links coming from different sections (link in the blue bar for Documentation is to Codex, whereas the one in the main menu is to Support). @kenshino suggested that @joyously raise the issue with the Support Team or that we can possibly also put in a Meta ticket for the link issue.

@kenshino is working on a patch for an anchor link to Dev Documentation from the upper left corner flyout menu.

@atachibana provided the link for the spreadsheet with redirect progress:
Column J = Done for transferred page
@softservenet offered assistance with additional redirects pending

Search for Redirected Pages: @joyously asked about how the two different pages (Codex, DevHub) would be handled in search. They are being redirected as there is valuable content still in Codex. @otto42 reiterated that Google will handle the search where the pages are redirected, while still allowing for other valuable content on the Codex to be found.


@kenshino Ticket created for Gutenberg handbook to DevHub – The discussion will likely continue in #meta-devhub

@Milana Cap Documentation Team Meeting Time P2 Post:

Documentation Team Meeting Time