[wp-meta] [Making WordPress.org] #4388: Move Gutenberg Dev Handbook to DevHub

[Making WordPress.org]

#4388: Move Gutenberg Dev Handbook to DevHub
---------------------------+--------------------------
 Reporter:  Kenshino       |       Owner:  coffee2code
     Type:  enhancement    |      Status:  accepted
 Priority:  high           |   Milestone:
Component:  Developer Hub  |  Resolution:
 Keywords:                 |
---------------------------+--------------------------
Changes (by coffee2code):

 * keywords:  needs-patch 2nd-opinion =>


Comment:

 As of now, all of the tasks and issues from @nosolosw's
 [https://meta.trac.wordpress.org/ticket/4388#comment:13 comment] have been
 addressed.

 The current status was discussed in
 [https://wordpress.slack.com/archives/C02RP4WU5/p1557761120365100 today's
 #docs team chat].

 @chrisvanpatten
 [https://wordpress.slack.com/archives/C02RP4WU5/p1557761983388500 wrote
 up] a list of next steps:

 >1. we'll get that branch merged so the manifest can come from `master`
 (@nosolosw / @chrisvanpatten)
 >2. handbook is rebuilt, and presumably goes live after a final sanity
 check, temporarily there are two handbooks
 >3. redirects get enabled (@coffee2code)
 >4. some indeterminate testing period just to make sure we're all happy,
 updates are successful, etc.
 >5. handbook gets updated to point to `wp/{version}` branch

 Everyone, please review the [https://developer.wordpress.org/block-editor/
 Block Editor handbook] for any issues that remain.

 I just have to (locally) test redirects from the legacy handbook. Once the
 manifest gets merged into `master` and the green light is given, I'll
 update the handbook's manifest source and enable redirects, which should
 resolve this task.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4388#comment:22>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org