- Rolled Oats – 400g
- Pecans – 2 Handfuls
- Coconut Flakes – 2 Handfuls
- Olive Oil – 6 Table Spoons
- Honey – 6 Table Spoons
- Candied Ginger – 2 Handfuls
- Pre-heat the oven to 250ºF.
- Crunch the coconut flakes and pecans into smaller, irregular pieces by hand.
- Combine the oats, nuts, and coconut flakes and spread them evenly over a baking tray.
- Mix the honey and olive oil in a bowl until you have a uniform syrup.
- Pour the honey and olive oil mix evenly over the oats, nuts, and coconut flakes.
- Using a spatula, ensure an even coating of honey and oil.
- Bake for 1 hour 20 minutes, turning every 20 minutes, breaking up larger chunks when they form.
- Allow the granola to cool and then mix in the candied ginger.
- Working Copy for editing content and templates
- Safari and Split Screen for live previews while editing
- Photos and Shortcuts for managing and exporting photos
Over the past few years, I’ve continued to tweak and adjust my granola recipe. Sarah recently asked me for a ginger and pecan version and enjoyed the opportunity to make some adjustments.
I find this makes roughly two weeks of granola; adjust quantities to your own tastes and needs.
A few weeks ago, I was again motivated to record some of the glorious color palettes we encounter in every day life. The output of the k-means technique I’m using still needs some tweaking, but it is a good starting point for use in other projects. In time, I hope to put together a light-weight service to automate the generation of these palettes.
Over the past couple of years, I have been slowly working towards using iOS exclusively to update my website–it’s liberating being able to publish posts and photos with just an iPhone or iPad. Now that it’s all working, I’ve been asked to describe my workflow, and the tools I use.
The site itself is stored in GitHub as a collection of Markdown1 and media files–one per page. Whenever a change is pushed, it’s built and deployed automatically. While I use a homegrown solution for this process, it’s a very common approach: GitHub Pages offers this behaviour out-of-the-box with Jekyll and it’s a great place to start.
With an automated build and deploy process like this in place, publishing becomes all about efficiently managing a git repository of Markdown files. For this, I make use of a few apps and workflows:
Since starting this post, I’ve also been experimenting with iA Writer for dedicated Markdown editing and offline previews.
Working Copy has been around for some time now and is the git client for iOS. It’s fully featured enough to be the only tool you really need, providing a great built-in editor, while also playing nicely with other apps through Files integration, Shortcuts, and open-in-place.
The integrated editor provides syntax highlighting for a comprehensive set of languages (including Markdown), allowing me to edit content, templates, and even the build scripts for my site. Publishing those changes is then simply a matter of pushing to master. This is where Working Copy’s comprehensive set of keyboard shortcuts come in, allowing quick turn-around when editing drafts: you can commit and push right from the editor with ⌘ + Shift + C.
Since I include a number large media files on the site, I make extensive use of git-lfs to stop them slowing down the repository, and Working Copy excels here too, offering out-of-the-box support.
While I can edit (and preview) in Working Copy, it’s useful to be able to see the content as it will appear in my website. To achieve this, I publish draft posts to a separate section of my website, commit and push regularly during editing, and use Safari for previewing.
Using Split screen–one of the features that really allows iOS to shine on the iPad–I can keep both Safari and Working Copy side-by-side without having to worry about excessive screen furniture or other distractions.
Since I like to control the publishing experience for my media, things like Google Photos, Instagram, or even Flickr aren’t options. Instead, I follow the same model as the rest of my website, adding the files to my git repository, and using templates to display albums and individual photos and movies. This can be achieved with Jekyll, but only with many custom plugins and templates, and that complexity is the main reason I wrote my own site builder. Perhaps one day I will publish the code but, for now, I’ll cover briefly how I manage my media and get it into git.
For my media library, I use the built-in Photos2, which syncs across all my devices, meaning everything is available irrespective of the device I choose to use for publishing. Here, I organise everything into albums to make it easy to prepare for publishing.
When it comes to storing media in my site, the approach I take is very pragmatic: folders are created for the year, month, and album, and the corresponding photos and movies live there, sorted by date, and numbered sequentially. A sidecar Markdown index file contains the album metadata.
/photos/2018/10/prge/ index.markdown 1.jpg 2.jpg 3.jpg ... 7.m4v ...
Using Working Copy, it’s easy to manually create this directory structure and Markdown file–I only need to do this once for each album so it doesn’t represent significant effort.
Numbering the files correctly on export does take a little more work however and, for this, I use Shortcuts: with a simple workflow, it’s possible to rename files sequentially, and then prompt the user for a location to save them. Adding my photos to Working Copy, is then a matter of selecting the Shortcut from the share sheet in photos, instead of exporting directly to Working Copy. And, of course, just like the rest of the site, pushing to GitHub triggers the build and redeploy.
While Working Copy does provide a way to edit and preview Markdown, it can can be a little cumbersome–it’s strength is breadth, not depth. For specific tasks, it’s nice to be able to kick-out to a dedicated tool, and iA Writer is a great option, allowing direct editing of files in Working Copy. It offers a nice, minimal UI for editing with a quick keyboard shortcut (⌘ + R) for previews, making for a rapid editing experience. Those previews are even customisable with templates allowing you to tweak how it appears to match your publishing platform.
I have found that I need to tweak the options a little to disable things like smart quotes and smart dashes in the editor (this can really mess up adding code to posts, and HTML tags), but it’s good to have that flexibility. It’s been a great addition to the toolbox.
Undoubtedly my workflow will change over time as iOS evolves and new apps are written, but already, these apps offer a wonderfully light-weight solution for editing on-the-go.