web analytics

Bill Bennett

Menu

How WordPress Gutenberg upsets writer’s flow

…he might also figure out how to dovetail them all together to make something more interesting and useful than Gutenberg, which has taken hundreds of developers and a magnitude larger amount of time to create.

Perhaps some additional competition against Gutenberg would help speed WordPress (and everyone else for that matter) toward making a simpler and more direct publishing interface?

Source: Chris Aldrich

“…he might also figure out how to dovetail them all together to make something more interesting and useful than Gutenberg, which has taken hundreds of developers and a magnitude larger amount of time to create.”

Gutenberg. Where can I start? This has done so much to disrupt my writing flow and my workflow.

Ironically it is all about blocks. I say ironic because when I teach people how to write, one of things I tell them is to remove all the roadblocks in front of readers. Gutenberg puts roadblocks in front of writers.

One roadblock is that it is now harder to export a post from my favourite Markdown editor (iA Writer) to WordPress. It works, but it’s not as smooth and seamless. The barrier may be small, but tiny barriers can disrupt flow.

At the same time, Gutenberg makes it hard for me to syndicate material to publisher sites with their own CMSs. In the past I could write a post, then pick it up as simple HTML and post that into the other CMS. Gutenberg allows you to copy HTML, but it’s badly broken and needs extensive editing.

«

»


12 thoughts on “How WordPress Gutenberg upsets writer’s flow

  1. Yes. And to cap it all, I found the so-called ‘classic editor’ plug-in was troublesome, but can no longer remember why. I do know I could no longer easily cut and paste my HTML into a new CMS.

  2. Gutenberg makes it hard for me to syndicate material to publisher sites with their own CMSs.

    That’s an interesting insight; one I didn’t know about! Thanks for sharing.

    I see a few others reported the problems with trying to copy all content:
    https://github.com/WordPress/gutenberg/issues/11739
    https://github.com/WordPress/gutenberg/issues/9018

    Hopefully, the Gutenberg team gets to iron out on these writer- and editor-friendly features soon. 🤞

  3. I advise all my users not to use Gutenberg for blog pages at all. I haven’t had any trouble with the classic editor. I understand why it was developed but a year after it was first added I haven’t changed that advice.

    1. @Jason – I can’t remember why I stopped using the Classic Editor. It seemed like a good reason at the time. But since I’ve gone back everything is working fine. Frankly, I think WordPress would work better if Gutenberg was the optional plug-in, not the default. But what do I know?

      1. Agree but we don’t have the overall data on what people are using as editors.

        I’m old enough to remember Pagemaker and DTP and I hated all those block editors then. Same reason I disliked quite a few other CMS systems.

        I can see the merit of using a page layout tool for the home page on many sites but as a long time WP user I’m just hoping the “new” editor gets better.

Leave a Reply

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

%d bloggers like this: