Replied to Flow in WordPress for writers by Dave WinerDave Winer (Scripting News)
Flow is the writer's problem for blogging. I have been working on this since I started in 1994. I solved the problem for myself in 1997, and ever since I've been working on solving it for everyone else.
Dave has some solid points about the UI and process of writing here. Speed is key! WordPress is pretty deplorable in this way. Some of the more advanced user may simply write the word “new” in their browser and tab down once to the correct URL to begin creating. Others may have some browser bookmarklets set up to jump right to creation. Still, for the unwashed masses–and I include myself in this, things should be far easier and more direct. I’ve recently been experimenting with the Narwhal plugin that puts a writing interface right up top on my website (and only appears when I’m logged in) and provides a pretty solid experience the way Twitter, Facebook, and other social sites do.

I have played around with many of Dave’s tools over the years and appreciated his UI and particularly some of his outliner tools. Given that he’s built and tested some very strong tools and interfaces, I’d be really curious to see him implement a Micropub client back end on some of them so that they not only allow one to post to his sites, but so that one could use them to create, edit, and publish to almost any website out there. Some of his tools are already set up to post content to Twitter, why not set them up to post to WordPress and many others too?

Given that CMSs and static site services like WordPress, Drupal, Craft, WithKnown, Jekyll, Kirby, Hugo, and Blot all support Micropub either natively or with simple plugins, Dave could easily take his various publishing interfaces and make them broadly available to almost any website on the planet. How many times have I desperately wished I could use Radio3, Little Outliner, Little Card Editor, pngWriter and others to be able to post to other websites instead of just Twitter?!

He might even implement them as Micropub clients just so that he could use his own interfaces to publish directly to his WordPress sites instead of worrying about their interface. I suspect that in day or two’s worth of work he could not only have half a dozen or more micropub clients, but 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? Micropub seems like a designer’s dream for making better posting interfaces, especially since it’s got such broad endpoint support.

Published by

Chris Aldrich

I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history. I'm also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.

2 thoughts on “”

  1. Thanks for the kind words Chris, I’m not working so much these days. Learning how to enjoy life more, not banging my head on the wall which is what software development is like these days, for me at least.

    I do support RSS in all my tools, maybe that would be of help.



    Also you guys might want to package up your protocol the way I’ve released server-side support for RSS.

    https://www.npmjs.com/package/daverss

    Maybe that would be of some help.

    RSS support for me is pretty automatic these days.


    Also I’ve got a simplified API for reading feeds.

    https://www.npmjs.com/package/davefeedread

    It supports all the popular formats. It’s something I built on top of
    @danmactough‘s feed parser package.

    Really simple to use, give it a feed URL and it calls you back with a JSON object.

    Syndicated copies:

  2. …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.
    Like Loading…

    Related

Leave a Reply

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