Agenda for Gutenberg docs meeting 13 November 2018

Hello all,

Looking forward to another Gutenberg docs meeting today!

Tuesday, November 13, 2018, 17:00 UTC

Today’s meeting is in #docs in Slack.

Agenda

  1. Attendance
  2. Status update/call for help: documentation PR
  3. Bug scrub
  4. Open floor

Hope to see you in #docs!

Agenda for Docs Team meeting 12 November 2018

The next Documentation Team meeting is scheduled on

Monday, November 12, 2018, 15:00 UTC

in the #docs channel on Slack.

If we do not get any attendance, open floor will be held instead

Current Projects Updates:

  1. Codex Migration (DevHub) – @atachibana
  2. DevHub – @drewapicture & @coffee2code
  3. HelpHub – @kenshino
  4. Inline Docs – @drewapicture & @atimmer
  5. Gutenberg Handbook – @chrisvanpatten

Open Floor

Feel free to comment if you have items to add to the agenda.

Summary for HelpHub Meeting 5 November 2018

Below is a summary of last week’s meeting.

Attendance

@milana_cap @wizzard_ @poena @yuli-yang @felipeelia @atachibana

Phase 1 Updates

@kenshino posted Call for Volunteers, and so many new contrbutors helped us to migrate staging site to production.
Contributors: @akhrayaprolu @softservenet @malice1332 @mehul0810 @howdy_mcgee @jessecowens @pskli @william68 @yuli-yang @poena

Stats:

  • Done 80 (69.6%)
  • In Progress 9 (7.8%)
  • Remains 26 (22.6%)
  • Total 115

For more details, refer this spreadsheet.

We are editing those contents with Gutenberg (of course :-)) and will report some difficultlies and issues that we found to https://github.com/WordPress/gutenberg.

Phase 2 discussion

Phase 2 work will start after migration for Phase 1 is over as that is priority. Phase 2 issues are here. If you want to join this project, please contact to @milana_cap.

AOB

@netweb and @clorith are working hard to setup production site for HelpHub. Thank you!

Agenda for HelpHub meeting 5 November 2018

Hello all,

Next HelpHub meeting will happen on

Monday, November 5, 2018, 15:00 UTC
  1. Attendance
  2. Phase 1 Updates (if any)
  3. Phase 2 discussion
  4. Bug Scrub
  5. AOB

Helpful Links

  • HelpHub Staging – https://wp-helphub.com/
  • GitHub repo – https://github.com/kenshino/helphub
  • State of HelpHub (read for Phase 2) – https://make.wordpress.org/docs/2018/02/26/state-of-helphub-february-2018/

Call for Volunteers – HelpHub Migration

Hello!

As you might know from our meeting updates – HelpHub has taken awhile to finally materialise. One of the hurdles was working out a migration plan. Unfortunately, because of WordPress.org’s unique setup, we were not able to get things automated or even use WordPress’ import mechanisms.

This means that we actually need to specifically do manual migrations from the Staging site – wp-helphub.com to the Production spot WordPress.org/support

How are we doing it?

Specifically – we are doing the following

  1. Use the Copy All Content function of the Gutenberg editor on an article on the Staging site
  2. Paste it the content onto the Production site
  3. Do the same for the title and check the correct taxonomies
  4. In the case that it’s still using a Classic block, we’ll have to switch it to Gutenberg blocks
  5. Ensure that all media used (pdfs, images etc) are downloaded and re-uploaded back to WordPress.org/support
  6. Check it for irregularities
  7. Save the draft

You might be able to appreciate that it is a pretty tedious process. By the time you read this post, we should be up to 30 of 170 articles completed. Another 140 articles is a lot to migrate for a team of 5.

Why the rush?

We want HelpHub to be ready for the Gutenberg team to drop in their user documentation. Given that WordPress 5.0 is designated to ship November 19, we don’t have a lot of time left.

We don’t want to leave users in the cold. And you could help us.

What can I do?

If you have some copy pasting skills, a keen eye for detail and an hour free over the next 2 weeks; you can help us!

Drop @atachibana (who’s the Content Lead) a line with your wordpress.org account and registered e-mail address. He will sort you out with the correct access and the know how.

If you have any questions, just ask in #docs on Slack.

Reference

P.S. If you received this call of volunteers earlier, we accidentally published it earlier!

Agenda for Gutenberg docs meeting 30 October 2018

Hello all,

Looking forward to another Gutenberg docs meeting today!

Wednesday, October 30, 2018, 17:00 UTC

Today’s meeting—and all future meetings—will happen in #docs.

Agenda

  1. Attendance
  2. Establish tracking tickets
  3. Parsing Gutenberg JS docs — how do we move this forward?
  4. HelpHub documentation — can it be sourced from markdown?
  5. Schedule bug scrub for next week
  6. Open floor

Hope to see you in #docs!

Summary of Gutenberg docs meeting 24 October 2018

Thanks to everyone who joined us for the kick-off Gutenberg docs meeting!

Below is a summary of last week’s meeting.

  1. Opened with introductions and hellos, and a description of @chrisvanpatten‘s goals for the group
  2. Set future meetings for 1pm ET/17:00 UTC on Tuesdays, in #docs on Slack
  3. Discussion of where documentation would “live”
  4. Goal is to continue allowing docs to be prepared in GitHub
  5. @drewapicture raised some questions about what the Gutenberg handbook represents, suggesting it not exist as a mono-doc when merged into core
  6. @kenshino raised the idea of splitting into separate handbooks: auto-parsed documentation in DevHub, developer handbook in DevHub, and user handbook in HelpHub
  7. (@chrisvanpatten also added a contributor handbook to be considered too, likely to live on GitHub for now)
  8. Established next steps:
  9. Lock down high level documentation outline
  10. Open a PR to reorganise the documentation
  11. Determine list of holes in documentation
  12. Begin assigning writing tasks in GitHub issues/high level project/milestone
  13. Established next meeting for Tuesday, 30 October at 1pm ET/17:00 UTC in #docs
  14. </meeting>

I’ll post an agenda for our next meeting tomorrow a few hours before the meeting. Thank you everyone who joined us!

Agenda for Docs Team meeting 29 October 2018

The next Documentation Team meeting is scheduled on

Monday, October 29, 2018, 15:00 UTC

in the #docs channel on Slack.

If we do not get any attendance, open floor will be held instead

Current Projects Updates:

  1. Codex Migration (DevHub) – @atachibana
  2. DevHub – @drewapicture & @coffee2code
  3. HelpHub – @kenshino
  4. Inline Docs – @drewapicture & @atimmer
  5. Gutenberg Handbook – @chrisvanpatten

Documentation Team’s handbook

  • We’ll check on the progress of Docs Team’s handbook improvements

Open Floor

Feel free to comment if you have items to add to the agenda.

Summary for Docs Team Meeting 15 October 2018

Attendance

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

Codex Migration (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.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 Gutenberg release (mostly). It is likely the core 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

Agenda for Gutenberg docs meeting 24 October 2018

Hello all,

We’re holding our first meeting for Gutenberg handbook work!

Wednesday, October 24, 2018, 18:00 UTC

This week’s meeting will be in #core-docs as previously announced.

Next week’s meeting—and all future meetings—will happen on Tuesdays at 1pm EST/17:00 UTC in #docs.

Sorry about the confusion everyone; that’s on me.

Agenda

  1. Attendance & Introductions
  2. Discuss handbook location
  3. Review handbook outline
  4. Break down interest areas and priority tasks
  5. Open floor