12 Comments

  1. Alain Aubry
    · Reply

    Great, great, great !!!
    At last a solution is coming… Yes, please!

    Report

  2. Rob Ruiz
    · Reply

    Is it possible that the REAL underlying problem is the the_content approach to storing document data? I believe that problem should be solved first. Imagine a future where the_content is pulled from its own API that can optionally be stored in a noSQL database. A hybrid db approach. So continue to use MySQL, but use a noSQL db just for post/page/cpt content. Then allow such an API to interact with that instead. Just my 2 cents.

    Report

    • Phil Johnston
      · Reply

      A nice thing about an Editor API (as proposed here) is that you could load your own Editing interface which pushes/pulls/stores data however your system needs it. WordPress would not need to dictate that for each Editor.

      Report

  3. ar
    · Reply

    A LibreOffice extension to post directly to wordpress ?
    Open source rules !

    Report

  4. Leonardo Losoviz
    · Reply

    I write my posts in Markdown, using VS Code: it’s as simple as it can get, and I don’t need to be online to use it. If there could be an extension for VS Code that already synchronized the content with my WordPress site, and allowed me to access the images from the media gallery, that would be amazing!

    Report

  5. Amanda Rush
    · Reply

    In short, yes, WordPress should provide an API for third-party editors. I remember third-party clients being one of the promises of the WordPress REST API but that hasn’t appeared. And I think that users should have a choice about how they publish. I use micropub clients a lot, and rarely touch the editor anymore, for example, and I think if someone else wants to do that an API for editing would make that easier.

    Report

  6. Rod Olman
    · Reply

    Has this question been sanctioned by Matt, or will this idea be shot down the same way he banned the whole WP Governence project?

    Report

    • Justin Tadlock
      · Reply

      The ideas presented here are my own and those of the people I quoted. Authors at WP Tavern are given freedom to independently explore ideas, regardless of whether they become a part of the core platform or sanctioned in any way. The goal is to point out interesting ideas, start a discussion, and see where it takes us.

      Report

  7. Tom Jackson
    · Reply

    Yes!

    Report

  8. Prateek
    · Reply

    While I really like the Gutenberg experience, I have recently split my writing and publishing processes. It’s quite nice to be able to write offline (in Atom or VS Code as others have suggested, though I’ve recently discovered Notable) without worrying about how I am going to typeset this or align that.

    The two things — writing & publishing — require different mindsets and it would be great if the the tools we use are aware of that context. A change that would bring us closer to that reality (Micropub already does a little) would be welcome!

    Report

  9. Josh Kohlbach
    · Reply

    Speaking as a website owner, I basically do this already. Preferring to use Elementor for pages and Gutenberg for posts and others.

    Speaking as a plugin developer, I think this would be very welcome by developers. Creating proper support and standards for plugin companies to create unique editors that all play nicely with WordPress would be great. Then natively giving the site admin the choice of which editor to load for which post type, of course with Gutenberg leading the way as the default editor out of the box with WordPress when you install.

    I’m all for it and I think a lot of others would be too. It’s very much in the spirit of WordPress.

    Report

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: