The very worst thing you can do with frequently asked questions is make a list of them on your web site. Frequently asked questions are bugs, and the only satisfactory answer to them is to fix the problem so the questions don’t get asked again.¹

One of the great things about the month of december is the wide array of awesome advent calendars for geeks. This year I added PHP Advent to my list of essential reading. However december was one of those months where I barely had time to sleep, let alone actually read, so a lot of articles were left in my Instapaper cue. A few days ago I read through one of them and found this great quote from Drew McLellan. The whole article is very well worth a read.

This review was written and edited exclusively in Byword.

I began this article on a Tuesday night from my iPhone around 11:30 pm while my son, Noah, was up for his late-night feeding. On Wednesday morning I picked up where I left off by opening Byword on my MacBook Air while in my office. After lunch, I grabbed my iPad and a Bluetooth keyboard and visited my favorite local coffee shop where a latte accompanied me as I finished the article.

This is exactly the sort of writing workflow that I’m looking to adopt.¹

This workflow appeals to me as well. I like being able to work device agnostically. Especially I’d like to be able to seamlessly work on blog posts from my computer(s), iPhone and iPad.

Since the blogs publishing interface is web based it’s possible, but that is not the way I’d like to write. I find myself being much more productive in something like Byword than in the WordPress Admin panel. Therefore I think I need to bolt some hacks together to be able to write in whatever application that I want, save the result in Dropbox and have the blog itself pick up the articles from a certain Dropbox folder and publish them. I’d like it to be like the post workflow in Marco Arment’s Second Crack², but still using WordPress as the CMS.