Practical Documentation: What the Indieweb Needs for WordPress

What the Indieweb really needs is some practical, plain language documentation to lead end users through the forest of plugins, jargon and bailing wire setups to get the mainstream blogger to the promised land of Indieweb goodness.

Example: If I use Jetpack to post to Twitter, will that give me all the same Indieweb Webmention, commenting type goodies as using  If not, what specifically won’t work?

It’s all fine to say “Install this and don’t worry” but then Bridgy suddenly breaks and won’t post to Twitter.  What then?  Will Jetpack do just as well?

And what about G+?

I know some have been diligently trying to provide guides to this stuff  but there are problems.

  1. To many links in the chain. Weakest link breaks, then we have a Scudhunt trying to find which link is broken.
  2. There are X number of ways to syndicate (crosspost) content. What are the strengths and weaknesses of each way?
  3. Indieweb plugin by plugin practical guides for WordPress. Like the problem of empty Titles on microposts and WordPress wanting to assign a number as the title. Getting around that.
  4. What works best for what.
  5. Don’t send me to Github.  That’s for developers. You don’t want the general public bouncing around there.

The point is if the Indieweb is ever going to grow beyond a small niche thing for developers it really needs some refining, documentation and streamlining. Their goals are noble, their efforts worthy but barriers for broader adoption do exist. And we are hitting those.

Liked this post? Follow this blog to get more. Follow

2 responses on “Practical Documentation: What the Indieweb Needs for WordPress”

  1. I agree with you about the frustration associated with #IndieWeb. However, if there was a simple answer then I think that it would have been implemented by now. I really respect the work being doing at the moment by Chris Aldrich and Greg McVerry, I am also mindful that many of these plugins and approaches are seemingly managed by a handful of individuals. Fine there could be additional documentation, but unless more people are willing to put their hands up (myself included) then it will likely remain this way.
    In regards to G+, do Google even offer the appropriate APIs to connect? For example, SNAP doesn’t provide direct link. IndieWeb is awesome, but isn’t it still dependent on third party silos. That is why it no longer works with Facebook, right?

    1. Aaron, thanks for replying. I think we are in almost total agreement on all points. My main goal was to point out that if we want the mainstream user to adopt both the philosophy and the mechanics of the IndieWeb then it needs to be more user friendly in all aspects. Word is leaking out into the mainstream, so we have to prepare.

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.