[wp-meta] [Making WordPress.org] #3593: Centralize GitHub Markdown importer

[Making WordPress.org]

#3593: Centralize GitHub Markdown importer
-------------------------+---------------------
 Reporter:  schlessera   |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Handbooks    |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by rmccue):

 Replying to [ticket:3593 schlessera]:
 > @rmccue has already done a lot of preliminary work for making this
 reusable in https://github.com/WP-API/markdown-sync, but some details are
 still missing.

 Happy to give access to this repo if anyone wants to help maintain, or
 move it to a different org if we want it somewhere else

 > Basic functionality could look like the following:
 >
 > 1. Field to enter a markdown source on GitHub. This could be a nice,
 proper UI, but simply accepting a custom field under a common field key
 convention would be enough for an MVP. Something like [https://github.com
 /WP-API/markdown-sync/blob/master/inc/class-importer.php#L17
 wporg_markdown_source] would do the trick.

 Right now, markdown-sync is just a library, so it has no opinions on this.
 In one of the themes I have using it, we've built the ability to supply
 the repo URL into the Customiser; I'm happy to bring this back upstream if
 we want to build this out into more of a plugin.

 I'd rather not allow the per-page meta to be editable, as this meant to be
 controlled by the manifest file instead. You can implement this in another
 plugin atop markdown-sync though, potentially.

 > 2. Refresh button in the post edit screen to fetch the latest version of
 the content from GitHub and make updates as needed.

 I think we may also have code somewhere for this (and API endpoints for
 the same).

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