[wp-meta] [Making WordPress.org] #5020: Source block editor docs from WP branch

[Making WordPress.org]

#5020: Source block editor docs from WP branch
----------------------------+--------------------
 Reporter:  chrisvanpatten  |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:
Component:  Developer Hub   |   Keywords:
----------------------------+--------------------
 Once #5019 lands, we'll be back to using `manifest.json` for the sole
 build of the block editor docs.

 Now that we're past the confusion of `manifest.json` and `manifest-
 devhub.json`, I'd like to propose "locking" the block editor docs to the
 current version of WordPress. Docs for the "bleeding edge" Gutenberg
 plugin will still be available in the repo. This has been a source of
 confusion in the past (including for myself, and I know it's happening!)
 because the developer.wordpress.org site is expected to be the
 documentation for core, not the plugin.

 The easiest way to implement this will be to wait for Gutenberg to create
 the WP release branch for the 5.4 cycle, and use that in the manifest URL,
 e.g.:

 `https://raw.githubusercontent.com/WordPress/gutenberg/wp/5.4/docs/manifest.json`

 This will mean the process is somewhat manual (it will require a meta
 commit every time a new major core release occurs) but I think it's the
 easiest way to make sure the primary documentation source reflects what's
 in core, rather than the latest changes in the plugin. If this solution is
 suitable, perhaps there could be an effort during the 5.4 release cycle to
 see if this can be automated.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5020>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org