18 Comments

  1. Alain Aubry

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

    Report

  2. Rob Ruiz

    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

      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

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

    Report

  4. Leonardo Losoviz

    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

    • Justin Tadlock

      One of the other reasons I often write in Atom (besides Markdown support) is that I don’t need to be online. Far too often, out here in a rural area, I lose internet access. The power goes out every time the wind blows is a saying we have around here. The electric companies can’t seem to keep up with keeping the trees cut back and away from the power lines. So, offline support is definitely a high priority.

      Report

  5. Amanda Rush

    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

    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

      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

      • Cynthia Freyer

        I think what he meant was: Is this discussion a good use of that nonrenewable resource called time? People can dream here all they want — it’s stimulating — but personally, I do not believe Matt / Automattic cares one iota about anyone’s ideas here if they don’t translate into ROI for his company’s investors. As a result, I have to conclude that discussion takes every one to the same spot: a dead-end and nothing to show for the time expended.

        Report

        • Justin Tadlock

          I hope that all discussions we have here are a good use of our time. Otherwise, what are we all doing?

          Not every idea is going to make the cut. Sometimes, it’s the collection of ideas and discussions that leads us to the places we need to go. We might be talking about an editors registry here that never lands in WordPress. Over time and over various discussions, the community builds up an even better idea that does make it in.

          We have to have some level of belief that all these roads lead to the same place — a future where WordPress is even better than it is now. And, part of that is having discussions such as these.

          As for the belief that Matt is only concerned with ROI for investors, I simply have not found that to be the case over the years. I’m asking that we veer away from that line of discussion and that we focus on the topic of the article. We’re getting a bit off track now.

          Report

  7. Tom Jackson

    Yes!

    Report

  8. Prateek

    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

    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

  10. Jason

    If blocks themselves had a proper server side registry (much like register_post_type, register_taxonomy) where the full block attributes were registered, sanitize callbacks for saving blocks, etc, we could have many different versions of UIs that interact with blocks. Gutenberg could be just one version of interacting with blocks.

    I wrote about this in 2017 in this issue: https://github.com/WordPress/gutenberg/issues/2751#issuecomment-330930741

    “Let’s be honest. Gutenberg is not going to solve everyones’s problems. No matter how awesome it is or will become, it simply will not meet everyone’s needs. There will still be a market for creating content in different ways. Page builders currently completely dismiss the Post Edit screen, and these alternative post creation solutions will continue to exist post-Gutenberg.

    With a solid Server Side schema, hopefully the Page Builders could at least start to adhere to a standard way of interacting with “Blocks”. . .that way, if Page Builder A thinks using Modals to edit content makes more sense than the fixed-right sidebar of Gutenberg, they could build their own UI to interact with Gutenblocks, but still ensure the blocks are saved in the same way.”

    Report

  11. Patty Ayers

    I have no real opinion on the Classic Editor vs. the new Block Editor as far as how convenient they are to use. I’m not a blogger; I put together websites for clients. The issue for me is that I have no desire to convert dozens of existing client sites to using the Block Editor, and then to spend hours training them to use it. And I just did not need to be forced to learn what is basically entirely new software on top of all the other work I have. The Classic Editor was fine, and using a theme like Divi improves my WordPress experience 1000%. I just don’t need this big hassle and massive extra work. There’s so much more to what I do than which Editor I’m using. I’m trying to run a business :-)

    Report

Comments are closed.

%d bloggers like this: