Kevin ClarkDesign Lead, Shopify
09.12.14

My Ideal Setup

Now that I’m trying to post more to my site, I’m re-evaluating my setup. I’m currently using Jekyll which has been mostly great, but has a few shortcomings.

Here’s what my ideal setup would be:

  • Is built on Ruby1.
  • Uses static Markdown files for each blog post.
  • Has some sort of (REST?) API endpoint that allows me to write an iOS client2 to post from my iPhone.

I was thinking of switching over to a Rails app and using a database, which would take care of point 1 and 3, but that means I would also have to design and build a web app to manage the content, which I’d rather avoid.

Another avenue would be to stick with Jekyll (or write my own flat file compiler) and use Dropbox to sync just the posts, but honestly I’ve had this setup before and it’s pretty flaky. Plus, I’d love to get my content versioned controlled if possible, this way I’m a lot less likely to lose data in the future.

Could I keep a workflow that is similar to now, where all the content resides in static files in my site’s repo and have some way for the iOS app to commit changes to the flat files directly? Is that even possible?

I’m just starting to dabble into that stuff, so if you have any ideas on what the best approach would be, it would be greatly appreciated if you could tweet or email me. Of course, I’ll be keeping you updated on what I end up doing.


  1. I already know a bit of Ruby, and want to get better at it. I have no desire to use any other languages for this.
  2. I have a few ideas for an iOS client that I could make relatively easily. For example, one of the things I really want is a sharing extension to post links from within any app.