Editorial workflows for Jekyll blogging

I decided to switch my blog engine to Jekyll and host it at GitHub. Square Space is good, but kind of bloated and sometimes slow. Also I’m trying to fully leverage my iPad – love Editorial and would like to use it for blogging as well. Did it and … it does work. Also saved some money, because my blog is in public repository.

Everything is stored in git in my case (GitHub) and I have to access it somehow. I can use applications like Working Copy, leverage x-callback-url, iOS extensions, etc. But I don’t like when iPad is switching between lot of apps to do a simple task. Python support in Editorial is superb and I decided to write my own workflows.

Post editing

Editorial does support Markdown and there’s no need to do anything special. Except one thing and it’s YAML Front Matter. Matter contains blog post settings like category and I would like to reuse them. Here comes the first workflow I made to insert or edit YAML matter and save entered values for future use:

Authorization

Decided to go with personal access token. Not the best way, but suits all my needs for now. Two workflows to make it simpler:

Both were designed to be used as subworkflows. The first one tries to get personal access token from iOS keychain and asks for it if not found. The second one just removes personal access token from iOS keychain.

Repository picker

We can access GitHub contents now. Next step is repository picker:

This workflow was designed to be used as subworkflow.

Used by following workflows (image and post upload). These two workflows store last used repository in .jekyll-repositoryfile. You can confirm it or pick another one:

Image upload

Blog post without images? No. Another workflow to upload image:

This workflow asks for image (iOS picker), filename, resizes it if it’s wider than 800 pixels, uploads it and automatically inserts image link in Markdown format. Don’t like it? Open workflow and edit Python script. Behavior is driven by constants defined at the same beginning.

Post upload

Images uploaded, text prepared, … Time to upload post itself. Another workflow:

This workflow asks for post filename, uploads it and copies link to clipboard.

Conclusion

iPad is for content consumers only? Meh. Nonsense. As you can see you’re able to do lot of things. Mainly because of Pythonista and Editorial existence.

Everything mentioned in this post was created entirely on iPad along with this post itself. It’s a bit rough now, UI is not pixel perfect, but it works. Install all workflows and all you need to do is to just tap the wrench icon: