After the release of Drafts 5.5, I’ve been using Critic Markup even more for the writing I’m doing.1 I hadn’t really used it before now, so leave it to Drafts to provide me some tools to improve the way in which I write.
In that post about the improvements in Drafts 5.5, I had shared updates to my actions for standard and linked posts. These have been super useful for me. But there are others out there that need to use plain Markdown for their posts. I had a follower pose this request on Twitter, and I decided it would be a small challenge to tackle and share. More “A Little More on Critic Markup”→
The latest Drafts update brings some improvements with Markdown syntax. In addition to the standard Markdown (which has been simplified to represent the original Markdown specification), there are two additional syntax options: MultiMarkdown and GitHub Markdown. MultiMarkdown is a flavor which allows for footnotes, tables, citations, etc. GitHub Markdown is a different flavor of Markdown which supports extensions created by GitHub for rendering on their website, and includes the extensions for strike-through text and tables. I personally use MultiMarkdown, the format with which I’ve been most comfortable writing.
One thing that is included with MultiMarkdown as an option is Critic Markup. Looking through the guide, there are several helpful elements that can be used for editing my writing utilizing Critic Markup. I can highlight some substitutions, additions, and deletions. I can highlight text to show something I might want to work on later. I can also add a basic comment somewhere that won’t be shown in a preview. And with this action, I can easily add any of them with a tap and a text entry, which inserts it in the proper format. This is helpful for creating and previewing the documents in Drafts, and gives users the flexibility to mark up files and save them back to a cloud service. I can see myself using this a lot for longer posts or large reviews. I’ve even modified my own site preview action to render the MultiMarkdown via scripting, as well as updating both my standard and linked post WordPress publishing actions to do the same.
There are additional Workspace options for sorting. You can now include flagged drafts in the archive tab – the same way it is done today with the inbox – as well as optionally sort the flagged drafts at the top. And of course, support for using these is also added to the script object. This allows you to give a bit of priority to Drafts in your inbox, depending on how you have your workspace configured. I liken it to something like Gmail: there’s a giant inbox of drafts, and you have a starred list that can be used to filter priority; you can also option to have the starred emails on top to bring them into focus, or have them in their separate list. This smart addition enables more focus on key drafts in your list.
Drafts 5 was recently updated to version 5.4, which brings a host of new features. While there is support for iOS 12's Siri shortcuts and all that they have to offer, there are also other important features that have improved the app's capabilities significantly.
It’s a really great release. And I was thrilled to write it for MacStories. If you haven’t checked it out, head on over and read it there.
I’ve been using Todoist for almost two years now. I started integrating it into my system for work-only purposes, and it has served me very well. I have to use a PC for work, so the cross-platform support was essential in this process; with the Outlook add-on, it has really elevated my work flow of task management.
But it never really clicked for me on iOS. I’m not sure what it was. Perhaps it was the un-iOS-like interactions or the swipe to complete. I knew that there were some nice automation possibilities through various apps like Drafts, Workflow, Slack, and others, but it again, it didn’t really grab my attention.