Summary of HelpHub Meeting 23 July 2018

Attendance

@kenshino @zzap @mapk @felipeelia @atachibana @jeroenrotty @tomf @clorith @g.allegretta

Phase 1 Updates

We’re waiting on content to go into the CDN (media stuff), we’re not doing the text migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. until that’s done because doing content twice is a waste of resources and we won’t know the paths etc until it’s been uploaded so doing prep-work and having 404’ed media until it’s there doesn’t seem an option. (@clorith)

Phase 2

WordPress Version page (Epic #249)

WordPress Version page is releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. notes in Codex (e.g. Version 4.9.7). Those pages should be migrated into HelpHub, and Epic #249 and its sub tasks (#245 – #248) were created.

We have to endorse #core-docs team so that they can create/manage the new Version page in HelpHub.

Feedback functionality (#240)

@tomf has been working on a proof of concept using 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. https://wordpress.org/gutenberg/ and Attachment Blocks.

DevHub Suggestion Piece: Since the Gutenberg Attachment Blocks piece might take longer than utilizing the existing DevHub piece, timewise, it seems to make sense to implement DevHub solution first.
https://github.com/WordPress/meta-environment
*will need to reference DevHub Repo
*isolate code to be used to add feature

Gutenberg Attachment Blocks: Will continue to technically outline this and move forward. Team decided to require a user to be logged in to submit a suggestion vs. being able to do so without being logged in from the front end.

New Issues (#254 – #256)

@pskli raised some issues for Phase 2.

#254 Contributor Recognition
#255 Gutenberg Blocks
#256 Gutenberg template