Status of this repository, possible changes

[nylen]

I've implemented this on https://docs.classicpress.net.

It's working well, and I've made some changes that could be incorporated upstream. However it looks like the version of this code being used on wordpress.org is different / outdated so I thought I'd check on whether this is still being maintained first, and if there is interest in one or more of these changes I can write them up into PRs:

• Improved debugging for what happens when importing a manifest file: https://github.com/ClassicPress/site-docs/commit/15a8c755c91303971149d907f022f549a7055329, https://github.com/ClassicPress/site-docs/commit/d083b833bf1282b8aa74757adae323c6449d49ce
• Disable editing content, title, and slug in wp-admin (classic editor only): https://github.com/ClassicPress/site-docs/commit/5c8810d9c750cfbf01b412acb66fe2d3a655371b
• Expose the protected function Editor#get_markdown_edit_link publicly so that themes can implement their own front-end edit links. This will cause a back compat issue if the visibility is changed, but a new method could be added instead.
• Do not require jetpack_require_lib() to exist on the site, allow including and manually loading the required Jetpack code instead: https://github.com/ClassicPress/site-docs/commit/eecfdb77f2865410b1416ae3950ffe18dc6a3de4
• Improved debug messages for what happens when importing content: https://github.com/ClassicPress/site-docs/commit/9e25b76c92122bf52629c08607d85424332a651a
• Create a new method Importer#is_markdown_post that can be overridden to allow more fine-grained logic for whether a post should be managed by the Markdown sync system.

If this repository isn't being actively maintained, then at least this can serve as a reference implementation for others. More information about our setup is here: https://github.com/ClassicPress/site-docs/tree/master/wp-content/mu-plugins/markdown-sync