Skip to content

Status of this repository, possible changes #4

Open
@nylen

Description

@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: ClassicPress/site-docs@15a8c75, ClassicPress/site-docs@d083b83
  • Disable editing content, title, and slug in wp-admin (classic editor only): ClassicPress/site-docs@5c8810d
  • 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: ClassicPress/site-docs@eecfdb7
  • Improved debug messages for what happens when importing content: ClassicPress/site-docs@9e25b76
  • 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions