Summary for HelpHub meeting 14 January 2019

Attendance

@kenshino @atachibana @dryanpress @zzap @clorith @softservenet @greensteph @fahimmurshed @subratasarkar attended.

Closing of Phase 1 Launch

Contents migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. were completed.

Phase 1.5 was newly defined to solve high priority issues of Phase 2.

1. Fix styling problems of sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme., TOC and language locator to existing articles (@zzap)
2. Migrate Codex language links to HelpHub (@atachibana)
3. Setup redirect from Codex articles to HelpHub (@atachibana)
4. Update 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/ related articles (Status)
5. Migrate WordPress Version articles (Status)

Phase 2 discussion

By introduction of Phase 1.5, Phase 2 discussions were paused until February at least.

HelpHub contents

Phase 2 migration target was listed up here.
@atachibana will create all Codex pages table with help of #meta team.

Voice & tone – Writing Style

@kadair wrote the 1st edition, and now calling for the review. Please refer this article.

Maintaining Classic Editor & BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor docs

@dryanpress and @clorith discussed about the soulution. plans were to identify all content in HelpHub and rename/re-slug i.e. Writing Content ==> Writing Content in the Classic Editor and create redirects to new equivalents.