Summary for Docs Team Meeting 15 October 2018

Attendance

@drewapicture @atachibana @g.allegretta @softservenet @jessecowens @milana_cap @clorith @joyously @coffee2code @kenshino attended

Codex MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. (for DevHub)

There is a list of function, class and hook that are due for migration / redirection on a Google Sheet.

We had a good discussion around priorities for redirection (since many Codex’s code examples have been migrated already to the relevant DevHub pages) and it was decided that the priority will be setup in such a fashion:

1. Mirrored content – redirect all
2. Migrate high traffic articles (We don’t need 100% migration, there doesn’t need to be 500 examples for one functionality)
3. Redirect migrated high traffic articles articles
   

@atachibana is managing the migration effort’s via Trello.

Codex Migration (for HelpHub)

This is not yet a thing as HelpHub is being launched over the next few weeks. But it will eventually need people to help redirect Codex articles to HelpHub ones

HelpHub

We cleared the upload hurdle. And we’re working on doing manual migrations, (really copy and paste) because even text based imports failed.

Kudos to @tellyworth getting us here.

@atachibana has a team working on doing the migration from Staging (wp-helphub.com) to Production (wordpress.orgWordPress.org 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. https://wordpress.org//support)

@netweb is finalising the last few code commits

DevHub

@coffee2code has made sure that the WP Code reference now has the latest source code and documentation parsed in. This means the DevHib has up to 4.9.8’s code references recorded.

He has also added a WP-CLI command so that anyone with a sandbox can reparse the source in the future. (https://meta.trac.wordpress.org/changeset/7717)

@coffee2code was also working on the DevHub homepage revamp which looks like the wireframe here – https://meta.trac.wordpress.org/ticket/3377#comment:5 (This has already been done before the minutes were posted (late))

He’s also working on allowing users to edit their own comments (Code examples) on DevHub – https://meta.trac.wordpress.org/ticket/3572

Inline Docs

Because WordPress 5.0 is designated a 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/ release (mostly). It is likely the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. inline doc changes won’t make it into the 5.0 release. If these changes are pushed, they will likely fall into the 5.1 release.

Docs Handbook Architecture

@milana_cap worked on recording the pages and fixed the paginations to show pages in proper order.

There still exist quite a few unfinished pages and @kenshino will take some days closer to the end of the year to write missing content

However,  work to improve the Docs team handbook shouldn’t stop and volunteers are free to help improve it.

WordPress Contextual Help system

The WordPress Contextual Help system looks like this if you need help reminding (it looks like this)

The Docs team is responsible for the strings present within and we’ve not been looking at it for some time.

We’ll be slowly bringing this back into the Docs Team meeting.

We noted that the Contextual Help system is missing in Gutenberg as well.

You can view the meeting history in detail starting from https://wordpress.slack.com/archives/C02RP4WU5/p1539615616000100