This setup, believe me or not, is cool. I’ve all my blog posts written in MarkDown, versioned on and kept safe on GitHub and when I’m ready to publish, I just need to make a pull request, merge it and a CI job will take care of using Pelican to build the pages and push them to the right place. You can find more information about my setup in this other post.
So, what’s the problem? Well, as you can imagine, to do all of this, you need a GitHub client, a MarkDown editor and you need to be able to commit, push and do pull requests.
Is this possible from an iPad? I believed it wasn’t (since the official GitHub client is very limited on what you can do, and online IDEs like VsCode.dev requires an internet connection, and I would like to be able to write also when I’m offline), but thanks to this blog post from Marco Gomiero, I recently found out it’s possible!
Working Copy: git client for iOS
The most important part of my workflow would not be possible without this amazing git client.
Working Copy is so far the best Git client you can find on iOS. It allows you to clone repositories and work offline. Checked out content is made available through the File explorer, so any iOS app has access to it and this means you can use any client to edit your files.
MWeb: a simple MarkDown editor for iOS
Following the suggestion from Marco’s blog post I decided to start using this editor. To be honest I’m still not sold on it (literally: I haven’t purchased it yet and I’m still using the free version), because I’ve found a couple of issues which I’ve promptly reported to the author (let’s see if and how long it will take for them to reply) but they are not bad enough to entirely disrupt my workflow.
iOS Shortcuts and Automations
Another idea I borrowed from Marco is the usage of iOS Shortcuts.
In my case I had to customise the flow quite a lot, either because I use Pelican instead of Hugo, and also because I’ve some conventions I want to follow when writing my blog posts, but overall I implemented similar features:
- “New Blog Post”: the first shortcut creates a new branch in my repository and creates a new MarkDown file, following my own convention. Then it fills the empty file with some headers which are normally used in Pelican MarkDown files.
- “Blog Photo”: this shortcut let me select a photo from my gallery, it converts it to JPEG (most of the time pictures taken with my iPhone had *.heic format, so they need to be converted) and place it in the expected folder in my repository.
Thanks for reading my first blog post, entirely written from my iPad, while I was relaxing on my sofa. If you have any questions or suggestions for a good MarkDown editor for iOS, feel free to leave a comment.