After backing Manton Reece’s microblogging kickstarter I decided not to wait any longer and setup a MicroBlog section on my website where I would keep my short form updates. This post covers my goals and the approach I took to achieve these goals.
There are just a handful of things that I thought I’d need:
- I own my content. I don’t mind posting to Twitter (or Medium) but the canonical location for my content is my own website
- It’s easy. I can easily separate short form content (ie. statuses) and long form writing (ie. this post)
- I still engage via Social Media. I can publish short form updates to my own website, and then the entries get cross-posted to Twitter
- I can post from my iPhone without needed to make edits from WordPress before publishing
I tried a few approaches (involving a range of apps such as IFTTT and various WordPress plugins) before I settled on the approach below.
It’s easy to own my content
My website is currently running on a self-hosted WordPress installation. There were two options here:
- I import all my Twitter posts under a special Category, or
- I post on my website first and then cross-post to Twitter
Option 2 feels more like “doing it right”, and, should anything go wrong in my setup, I never lose any posts I made from my own website.
What I decided to do was to:
- create a new Category called MicroBlog
- update the Menu to include this new category
- replace the stock RSS widget with Category Specific RSS and use it to surface the MicroBlog RSS feed into the side bar
- exclude the MicroBlog posts from the main page using the Ultimate Category Excluder plugin
- make all posts in Category use the post format “status” so they looks consistent and timeline-like
- remove all extra post decorations (ie. sharing) from the list of posts, but leave it on the post page itself
- not use a post title, in order to mimic a status post more accurately
With these changes in place I ticked the first couple of boxes. What was left was to sort out cross posting to Twitter and publishing while on the go.
Sharing status updates to Twitter / Social Media
Posting to Twitter proved to be more difficult than I thought it would be. The obvious way, via Jetpack’s Publicize feature, seems to share only the link to the post when a title is not present. Therefore I had to look for other options, although I’d much prefer to just use Publicize.
The choice I settled on is an IFTTT rule: “when a new feed item is added to parfene.com/category/microblog/feed post a new tweet to @nicktmro”. The issue with this approach is that IFTTT doesn’t have a smart way of appending a URL to the post when it is over 140 characters, so I was “forced” to append a URL to the original post. It’s not very tidy but the counter argument is that it drives traffic (and search engines) back to the canonical location of the status update.
Posting while on the go
I carry an iPhone and a Pixel with me all the time. Posting updates to my website is a task I assigned to my iPhone.
I seek speed and simplicity when it comes to capturing my thoughts, which is why I use Drafts for almost every form of text capturing. This text sometimes ends up in iMessage, or in OmniFocus, or in an email, or in my Clipboard, or in WordPress… You get the idea.
I looked at the existing Drafts actions but I soon realised that I needed to be able to post exiting text and snippets, too. I needed an extension point. Enter Workflow. By delegating the communication with WordPress to Workflow I managed to increase the ways in which I drive content to my website.
Here’s how it all works:
- I have a workflow that expects text input (or extracts it from the clipboard)
- The workflow presets the WordPress category, post format, etc
- This workflow is added as an action to Drafts
Now I’m good to go. When I choose to share my next status update all I do is go to my usual app (Drafts), write a snippet of text, and choose the Post to Parfene.com action.
I encourage you to try microblogging for yourself. My post is lengthy but you don’t have to do everything in one sitting. You don’t even need to fully automate everything, like I have.
This approach has made me feel more involved, engaged, and responsible with regards to the things I share with everyone. As somebody who oftentimes doesn’t count to five before he speaks, this should be a positive outcome…