Markdown on Save Improved
[resolved] Why not merge with "Markdown on Save"? (3 posts)

  1. Manuel Schmalstieg
    Posted 2 years ago #

    Hello developers,

    If this plugin is essentially a version of @markjaquith's Markdown on Save with one added setting ("always on" vs "optional"), why not merge those plugins (and provide a settings page)?

    Wouldn't this help keeping your maintenance efforts lower, and allow for a better usage of your developer ressources ?


  2. Matt Wiebe
    Plugin Author

    Posted 2 years ago #

    Hey Manuel. In short, it wouldn't work, not in any way that Mark or I would be happy with. The opt-in vs opt-out logic is a lot more complex than it seems like on the surface and assumes that it's always been that way to work properly.

  3. Manuel Schmalstieg
    Posted 2 years ago #

    Ok, good to know. I was trying to get an overview of the variety of Markdown plugins in WP, and my impression is that the playground is extremely fragmented.

    What made me think about the whole thing: the editor mockup in John O'Nolan's fictional "Ghost" UI. It imagines a very pretty Markdown-capable editor, with syntax coloring: the dream of every MD user ;)

    What would it take to get there?

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • Markdown on Save Improved
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic