The Process and the Platform

The effort required to actually publish that last post was... considerable. Several factors contributed to this:

In the end, I wrote the text of the post in Evernote on my iPad (using an external keyboard), since I'm supposed to install an absolute minimum of third party software on the laptop. Next, I did a copy paste into BlogPress, a blogging app which lets you insert images inline. In theory the official WordPress app also does this, except that the upload always fails for me. As you may have gathered, I inserted the images here. This also rescales them, so you don't need to upload all 12 megapixels. Next, I uploaded it to my actual blog as a draft, and used the web interface to fix any formatting errors and add any extra formatting, since BlogPress doesn't allow bold or italic text (that I've found). That done, I hit the publish button, and: presto!

Needless to say, this is not an ideal workflow. I like using Evernote for writing the actual text (on both iPad and Mac) because it has about the right amount of functionality and it backs everything up and synchronises it between all of my devices. I like having that always available record which I can look back over and search as I see fit. I also like being able to drop one device, pick up another and keep working on the same document more or less seamlessly.

Digression: I also like that I can use it as a permanent record of my notes. Before I moved down to London I was part way through scanning my notebooks from my PhD into Evernote. Evernote runs OCR on the images, finds the text (when my handwriting makes this feasible) and make it searchable. Brilliant. It's like being able to carry all of my old note books around with me, all of the time.

What Evernote doesn't allow you to do is freely mix text and images, however. The WordPress interface does (obviously), but that leaves me with the problem of uploading the images. This is where the low bandwidth and lack of iPhoto were became problems. I suspect the cleanest workflow would be to immediately upload an album to Flickr (or other photo sharing site) and then use the appropriate URL to include the image in the blog post. Searching through the iPhoto library manually sure as hell isn't ideal, and that's the only real option for doing it image by image in the web interface.

The most pleasant experience I've had for putting together blog posts with both text and pictures was actually iWeb, and by a metric mile. iWeb uses the built in OSX controls and lets you select images according to meta-data and what they look like, rather than their file name, as though you were working with a file system specifically designed for serving you images. The iPad does more or less the same thing, in fact, so that part wasn't actually too bad. Using iWeb leaves you with very limited options for your blog, however. It's made me think I should look at using a dedicated program, such as MarsEdit, for writing my posts, or at least for the final stages.

Ideally, I need to find a decent workflow, which doesn't break down when I'm away from home and likely to actually have semi interesting things to blog about, but doesn't restrict me when I am at home. Ideally, it should allow me to jump between different machines with a minimum of effort, and not require me  to always add the final touches from the same machine. The workflow should also not break down when no internet connection is available. Text is fairly easy. Images make things more difficult, especially if the images were recorded using my own camera.

Lastly, I'm giving some consideration to porting this blog over to Blogger (only if I can transfer all of my posts and comments, however). It's not a coincidence that I now work for the company responsible for Blogger's infrastructure. Becoming more familiar with that platform can only really be a good thing for me here. Blogger also gives me a couple of options which WordPress doesn't, though. Thoughts?