brycewray.com

iA for IO?

Evaluating iA Writer for use with an SSG

A re-consideration of using iA Writer in making Markdown files for this site’s posts.

published:  February 3, 2019
last modified:  October 2, 2019

My comments at the end of my previous post aside, I have to say iA Writer can be a halfway decent editor for Markdown, after all.

Once again, I’m not considering dropping Ulysses from my small collection of much-loved apps that I utterly must have when the muse is with me and I feel like writing. It’s just that I grow weary of the export-to-Markdown process inherent in writing something in Ulysses for this site, especially since I like to see my edits on my local version of the site as I save them to the target file.

(Yes, you can save directly to a Markdown file from Ulysses, but I get the impression that’s not really the best-practices way you’re supposed to do it, since so many reviews out there stress the “Don’t worry about files, just go to the Ulysses Library and find all your stuff there” approach. That approach is, indeed, wonderful for my non-SSG writing, but not so much for this.)

So this is yet another look at iA Writer as a potential “daily driver” for use with an SSG (stretching the definition of daily, obviously, since I write these posts just whenever).

Okay, I was YAMmering; sorry

Perhaps more to the point, I believe I was more concerned about how the TOML (like YAML) “front matter” looked in the iA Writer Preview window than how the SSG would handle the final Markdown file. (As I already explained, I get distracted by such things.) It turns out that doesn’t matter. You don’t have to enclose front matter in a code block for the SSG to know what to do with it—in fact, it doesn’t know what to do with it if you do put it in a code block.

Footnote follies

Screen capture from iA Writer software showing how footnotes look in it

That said, iA Writer’s inline footnotes, while fine for export from iA Writer, don’t fit Pandoc standards, which are baked into how some SSGs “think” when converting Markdown to HTML for a site. So, while Pandoc-standard inline footnotes look bad in iA Writer, they work fine in an SSG.^[“Inline notes are easier to write, since you don’t have to pick an identifier and move down to type the note.” See here—the source of that quote—for an example of what I mean.] However, that is something where Ulysses easily beats iA Writer for this stuff, since the inline footnotes in Ulysses—that is to say, all the ones I’ve included on my other posts before this one—work perfectly with an SSG. Same is true for Typora, as well.

Status quo, or no?

Bottom line: I still haven’t made up my mind about whether to go with a different editor for future Markdown work or stick with Ulysses for it as well as for my other creative writing (that WIP ain’t finishing itself). However, if you are an SSG user and you’re trying to decide about which editor to use for your writing, I hope these thoughts have been helpful.



One more thing before I end this quickie: if you haven’t already read Chris Rosser’s most recent review of iA Writer, I definitely urge you to do so. His workflow is quite different from mine since he actually coded his own text-to-HTML setup (whoa) but his observations are always keen and useful. ”Joe Bob says check it out.”

Comments powered by Talkyard.