Summary of HelpHub meeting 03 December 2018


@kenshino @atachibana @sergey @mapk @milana_cap @felipeelia @pbiron @abrightclearweb @mkaz @hlashbrooke @clorith @chrisvanpatten

Phase 1 Launch

Phase 1 was softly launched at It was featured in Hugh’s post The Month in WordPress: November 2018 and, thanks to @drewapicture and @mapk, will be mentioned in Matt Mullenweg’s State of the WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US coming up this weekend. For State of the Word’s slides (made by @mapk) @atachibana prepared Phase 1 statistics and list of content contributors, while the list of development contributors is prepared by @milana_cap.

Search functionality on doesn’t include new HelpHub articles while it does the old Codex ones – track ticket. This is a big problem and we need to, first and foremost, include HelpHub in search and find a healthy way for smooth shutting down the relevant Codex pages. It was proposed to turn Codex to read-only state, improve the notice to clearly state where new information can be found and then redirect relevant Codex pages to HelpHub ones as Codex is pretty good indexed.

On a matter of naming it’s been decided that we’ll keep HelpHub as a project code name while official name will be “User Docs“. It will stand next to “Forums” and “Developer Docs” in main menu for

All issues for Phase 1 will move to track while for Phase 2 remain on Github. To create new ticket go here: and select “Support Hub” component.

Phase 2

@mapk started with mapping 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. blocks for publishing HelpHub content – github issue. Here’s the demo:

Transcript of meeting can be found here: