Title: core-docs – Make WordPress Documentation

---

#  Tag Archives: core-docs

 [  ](https://profiles.wordpress.org/atachibana/) [Akira Tachibana](https://profiles.wordpress.org/atachibana/)
4:55 pm _on_ July 23, 2018     
Tags: core-docs   

# 󠀁[Summary of HelpHub Meeting 23 July 2018](https://make.wordpress.org/docs/2018/07/23/summary-of-helphub-meeting-23-july-2018/)󠁿

## Attendance

[@kenshino](https://profiles.wordpress.org/kenshino/) [@zzap](https://profiles.wordpress.org/zzap/)
[@mapk](https://profiles.wordpress.org/mapk/) [@felipeelia](https://profiles.wordpress.org/felipeelia/)
[@atachibana](https://profiles.wordpress.org/atachibana/) [@jeroenrotty](https://profiles.wordpress.org/jeroenrotty/)
[@tomf](https://profiles.wordpress.org/tomf/) [@clorith](https://profiles.wordpress.org/clorith/)
[@g](https://profiles.wordpress.org/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](https://profiles.wordpress.org/clorith/))

## Phase 2

### WordPress Version page (󠀁[Epic #249](https://github.com/Kenshino/HelpHub/issues/249)󠁿)

WordPress Version page is release notes in Codex (e.g. [Version 4.9.7](https://codex.wordpress.org/Version_4.9.7)).
Those pages should be migrated into HelpHub, and [Epic #249](https://github.com/Kenshino/HelpHub/issues/249)
and its sub tasks (#245 – #248) were created.

We have to endorse [#core-docs](https://make.wordpress.org/docs/tag/core-docs/) 
team so that they can create/manage the new Version page in HelpHub.

### Feedback functionality (󠀁[#240](https://github.com/Kenshino/HelpHub/issues/240)󠁿)

[@tomf](https://profiles.wordpress.org/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/](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](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](https://profiles.wordpress.org/pskli/) raised some issues for Phase 2.

[#254 Contributor Recognition](https://github.com/Kenshino/HelpHub/issues/254)
[#255 Gutenberg Blocks](https://github.com/Kenshino/HelpHub/issues/255)
[#256 Gutenberg template](https://github.com/Kenshino/HelpHub/issues/256)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2018%2F07%2F23%2Fsummary-of-helphub-meeting-23-july-2018%2F%23respond&locale=en_US)