{"id":12231,"date":"2014-12-08T15:18:46","date_gmt":"2014-12-08T22:18:46","guid":{"rendered":"http:\/\/doycetesterman.com\/?p=12231"},"modified":"2017-01-26T22:45:39","modified_gmt":"2017-01-27T05:45:39","slug":"my-plain-text-workflow","status":"publish","type":"post","link":"https:\/\/doycetesterman.com\/index.php\/2014\/12\/my-plain-text-workflow\/","title":{"rendered":"My Plain Text Workflow"},"content":{"rendered":"

Lately, I\u2019ve had (or created<\/a>) several opportunities to talk about using plain text file (and markdown syntax) – how great I think it is for writing and (more importantly, really) how perfect it is for making sure your stuff remains ubiquitously compatible and futureproof.<\/p>\n

Now, simply saying these things isn\u2019t enough to make everyone (or anyone) suddenly slap their forehead and switch to plain .txt files; to be honest, my<\/em> conversion wasn\u2019t an overnight thing – yes, I can find plain text back as far as I have<\/em> files, and even .md (markdown) files from two or three years ago, but in most cases the pattern until recently has been pretty clear: use those \u2018primitive\u2019 formats to do some initial work and note-jotting but, once the serious<\/em> work begins, copy the whole thing into something like Word.1<\/a><\/sup><\/p>\n

I\u2019ve changed my methods, though; my outlook has shifted. I\u2019ve started to see more benefits from working in plain text, all the time. Here are the big wins for me:<\/p>\n

Universal Availability<\/h3>\n

I can edit chapters on my phone while I\u2019m at Grease Monkey, poke at them on my tablet while the kids watch Super Why, open them in a half dozen apps on my mac, windows, or linux machines, and (and this is really<\/em><\/strong> important) I don\u2019t lose any fidelity or formatting because I opened them in different programs on different platforms.<\/p>\n

Imagine what your word document would look like after a few days of bouncing it between \u201cword-compatible\u201d programs on your PC, Mac, Linux box, iPad, iPhone, Chromebook, and Android tablet. Even RTF, which is supposed to be multi-platform, would suffer grave deformations over time, given this kind of abuse.<\/p>\n

Because that\u2019s what this sort of situation is for those kinds of files – bouncing them around to different systems and opening in different programs is abuse. (And heaven help you if you want to go multi-platform with cloud sharing on something like Scrivener.)<\/p>\n

Text files? Text files don\u2019t care<\/em>.<\/p>\n

Universal Transferral<\/h3>\n

Eventually, you need to ship, and you probably<\/em> need to ship in something other than plain text.2<\/a><\/sup> When I need stuff to go out, I can take my lovely markdown-enhanced text and put it out into the world in whatever format is needed.<\/p>\n

As an example, I finished an academic paper last week with a couple dozen footnotes and within about four minutes I\u2019d published it with full, pretty formatting to a Word doc, PDF, a forum post, and my blog, again without losing any fidelity in the formatting, without needing to do any additional formatting, and without changing the core document (a .txt file) in any way.<\/p>\n

Also last week, I sent my work in progress (which comes in at somewhere north of seven hundred pages) off to a couple folks. One of them got it as a word .doc, one of them got it as an .epub (took me about a minute, total, to create), and when I get their feedback, I\u2019ll be right back to working on the text files. Those other files are just outputs<\/em> to me – something I create, but don\u2019t work<\/em> in; like exporting to PDF.<\/p>\n

That said, the fact that I can export to Word, or epub, or html, or pdf, or rtf, or odt or\u2026 well, whatever\u2026 means that the work gets out in the best way possible, right away.<\/p>\n

The Challenge<\/h2>\n

I said something similar to those two points a couple weeks ago on Google+ and Ryan Danks (who\u2019s been struggling with plain text and markdown) said:<\/p>\n

Could you maybe do a blog post on your workflow? I think this might help out a lot of people I know who are still trying to find their groove.<\/p><\/blockquote>\n

The answer, of course, is yes. Sorry it took so long.<\/p>\n

1. Dropbox is my Co-pilot<\/h3>\n

I honestly don\u2019t know what my working\/writing environment would be like without Dropbox. It seems like hyperbole to say \u201dMy life would be completely different without Dropbox<\/a>.\u201d<\/em> and it is, sort of.<\/p>\n

Except that, at the micro-level, Dropbox touches so many of the individual elements that make up my day that I can\u2019t see how, at a macro-level, it isn\u2019t<\/em> true: a big, big chunk of the stuff that makes of my life would be fundamentally different without Dropbox.<\/p>\n

Now, these days, there are other options that give you similar functionality – I could probably manage the same basic workflow in OneDrive or Google Drive or SpiderOak (not iCloud, since I’m using a lot of non-Apple stuff, but lots of other people could) – and that\u2019s great, but since I\u2019m talking about my real workflow, I\u2019ll be talking about Dropbox, and simply trying to point out when and where other options are also available.<\/p>\n

My Dropbox<\/em><\/strong><\/p>\n

\"Dropbox\"<\/a><\/p>\n

Here\u2019s where I do pretty much all my work.<\/p>\n

I want to make this clear: I work inside my Dropbox folder and, while I certainly appreciate<\/em> that it both backs up and provides versioning of all the files therein, the critical thing for our purposes is this: Dropbox makes sure that everything stays up to date on all my devices.<\/p>\n

That\u2019s critical; I need all my stuff to be ready-for-work, regardless of whatever thing I pick up to work on<\/strong>.<\/p>\n

2. (Almost) All the Tools, All the Time<\/h3>\n

Once I\u2019ve got to the point where everything is at least theoretically available on all my devices, step two is giving myself basically the same tools and options.<\/p>\n

This is really where the choice to work in plain text pays off, because since I\u2019m working without the requirements and limitations and\u2026 fragility<\/em> of file formats like .doc or .rtf, when it comes to writing and editing, I get full functionality no matter where I am.<\/p>\n

I do<\/em> have to sacrifice a bit in terms of shipping<\/em><\/strong> when it comes to different platforms: it\u2019s simply not as easy to export from markdown\/plaintext to some other file format if I\u2019m on my phone, for example. I\u2019m sure in three years, it\u2019ll be a piece of cake to export right from markdown to .epub while I’m sitting in the doctor’s office, but at the moment, that\u2019s what I give up, and I\u2019m fine with that; I don\u2019t need to be able to ship every minute of the day.<\/p>\n

Come to that, there are tools I like better for different kinds of exporting. Pretty much any markdown editor outputs to html just fine, but rtf and pdf is a little bigger deal, word docx export gets a little more rare, and there\u2019s really only one program I have that\u2019ll go right to epub, no waiting.<\/p>\n

Again, I\u2019m fine with that. I\u2019ve looked at the options that were available even three years ago, and I think it\u2019s clear this is an evolving and constantly maturing environment: I expect my options in the future will always be better than they are at this moment, and I\u2019m pretty happy with them now<\/em>, so I\u2019m very comfortable hitching my wagon to the markdown star.<\/p>\n

Anyway: enough talking. Here are some examples of the options I\u2019m talking about.<\/p>\n

3. Tools<\/h3>\n

Mac<\/h4>\n

I\u2019m starting with Macs because (for some historical reasons I\u2019m not particularly interested in) Markdown was taken up by the Mac community sooner than elsewhere. It\u2019s making huge inroads elsewhere, with surprising speed, but Mac and iOS still have some of the best Markdown tools.<\/p>\n

My tools:<\/strong><\/em><\/p>\n

\"Markdown<\/a><\/p>\n

I\u2019m going to break these down in Right to Left order: nvALT, iA Writer, MacDown, and Ulysses III.<\/p>\n

nvALT<\/a><\/strong><\/p>\n

nvAlt is my \u201cNote taking\u201d tool. It opens with a keystroke, and all I have to do to create a new file is start typing: it names the new file the same as whatever I type into the first line, and lets me view both the current file and everything else in the working directory3<\/a><\/sup>, right from the main window, like so:<\/p>\n

\"nvALT<\/a><\/p>\n

The program is compatible with Markdown, and provides a nice preview window that will show you what your text will look like when you export it somewhere\u2026<\/p>\n

\"nvALT<\/a><\/p>\n

As an added bonus, if you\u2019re working in this screen and decide you need something more robust, there\u2019s a simple keystroke option that automatically opens whatever file you\u2019re working on inside whatever \u201cbigger\u201d editor you set up as the default, which brings me to\u2026<\/p>\n

iA Writer<\/a><\/strong><\/p>\n

Probably the easiest way to explain iA Writer is \u201cWritemonkey for Mac, but different.\u201d<\/em><\/p>\n

\"iA<\/a><\/p>\n

It\u2019s set up to be a \u2018distraction free writing environment,\u2019 but what it really is is friction<\/em> free – you just open something and get to work. What it lacks in Writemonkey’s “kick you in the ass to get you writing” features, it more than makes up for with great workflow tools and incredibly robust support for markdown, multi-markdown (footnotes, bibliographies, tables), and both the importing and exporting of files \u2014 I\u2019ve been going through some of my old stuff and transferring it from (for example) .docx files to plaintext, and iA Writer has been invaluable for this process: literally all I have to do is drag a Word file onto the iA Writer icon, and I suddenly have a nice, clean text file with all the formatting syntax preserved.<\/p>\n

It is, if you\u2019ll pardon me, fucking magic.<\/p>\n

(Editing to add: While adding web links through this document, iA Writer gave me yet another reason to love it – it vastly simplifies the process of adding links to a document, and makes writing posts like this one much easier<\/em>. So much love.)<\/p>\n

MacDown<\/a>\/Byword<\/strong><\/p>\n

iA Writer has a very nice preview window, but sometimes I like to work with the preview open all the time in a side-by-side arrangement, and for that I use MacDown.<\/p>\n

Also, and this isn\u2019t nothing, I really do like the fact MacDown \u201ccolor codes\u201d my text while I\u2019m working on it. Ulysses III does this as well, and it\u2019s pretty great for those times when you want to make sure your italics are right where you meant them to be. I imagine this is a slightly bigger deal for developers than writers, but the fact is I sometimes go to MacDown over iA Writer simply because the MacDown screen is more interesting to look at.<\/p>\n

\"MacDown\"<\/a><\/p>\n

For those of you who use Byword<\/a> and can\u2019t believe I don\u2019t list that in here somewhere, just pretend this entry is for ByWord – the two programs have similar inspirations and ancestors, and feel pretty much identical to me. I just use MacDown because it\u2019s free, and I spent all my App-allowance on\u2026<\/p>\n

Ulysses III<\/a><\/em><\/strong><\/p>\n

\"Ulysses\"<\/a><\/p>\n

How should I explain Ulysses?<\/p>\n

Let\u2019s go with \u201cScrivener, for plain text.\u201d<\/p>\n

Basically, Ulysses is a very good Markdown and Multi-markdown editor that is also very good at managing big writing projects. I will provide an example.<\/p>\n

When I finished up the first draft of current work in progress, I had a single text file that was thirty-one chapters and about 700+ pages long. There\u2019s nothing wrong<\/em> with that, but it\u2019s a bit of a pain in the ass to open the thing up on your phone and scroll down to chapter twenty-three, you know?<\/p>\n

What I did once I had Ulysses was take the original file, open it up, then jump to each chapter heading and say \u201cSplit the file here.\u201d In the three-panel view in Ulysses, that gave me something that looked like this (click to embiggen):<\/p>\n

\"What<\/a><\/p>\n

And in finder\/explorer, looked like this:<\/p>\n

\"What<\/a><\/p>\n

Basically, Ulysses chopped the big file up into a bunch of little files that are much more manageable in other programs, while still being treated by Ulysses as one complete meta-entity.<\/p>\n

(Those last two files are docx outputs I created for workshop feedback by selecting specific chapters and telling Ulysses to export them to Word.)<\/p>\n

The cool thing is the program also lets you fiddle with the structure of the meta-document and then stitch things back together in whatever order you like. Here\u2019s a shot of me rearranging some chapters into a different order, simply by dragging things around in the preview window.<\/p>\n

\"Rearranging<\/a><\/p>\n

It has no effect on the files themselves, except in Ulysses, until I recombine all the files, or export stuff.<\/p>\n

And it’s worth noting Ulysses exports are really quite pretty. Here\u2019s the epub version of the work in progress.<\/p>\n

\"\"<\/a><\/p>\n

Now, Ulysses\u2019 ability to chop up a big project into smaller bits is great – very<\/em> useful for me, right now – but with a little forethought early-on (or a LOT of cutting and pasting, today), I could have accomplished the same thing with notepad. I\u2019m glad I didn\u2019t have<\/em> to, but I could have.<\/p>\n

The main value<\/em> of working on things in smaller pieces is more easily navigable files, which are much easier to work on when I\u2019m using my phone or tablet.<\/p>\n

So let\u2019s talk about working on a phone or tablet.<\/p>\n

Phone or Tablet<\/h4>\n

Before I get into specific tools, I want to talk philosophy of use<\/em>.<\/p>\n

Here\u2019s the main thing you need to keep in mind when you\u2019re looking at tools to use on a handheld device:<\/p>\n

It isn\u2019t about whether the App can open a file of the right type, it\u2019s about whether it can work right inside<\/em> Dropbox, without downloading files.<\/strong><\/p>\n

Dropbox, as you probably know, doesn\u2019t download EVERYTHING to your mobile devices, the way it does on your laptops or desktops. Instead, it mirrors the directory, shows you what\u2019s there, and only downloads something if you really, really want it.<\/p>\n

That\u2019s kind of useless for what we\u2019re doing. I do not want to download a file, fiddle with it, save it, then reupload\/overwrite\/update the Dropbox version, when I\u2019m working on my phone. I want fast, reliable, and as frictionless as possible; I want Dropbox to be Dropbox.<\/p>\n

In other words, I need a program that works right inside my online Dropbox folder, effectively making Dropbox as useful as Google Drive with it’s built-in editor. (And, once again, that\u2019s a lot easier when I\u2019m using plaintext files, and a lot HARDER when I\u2019m using .docx or whatever.)<\/p>\n

Android<\/strong><\/p>\n

For Android devices, I use Jotterpad<\/a><\/strong>, which pretty much hits every target I place for mobile writing: reliable, edits directly in Dropbox, and understands markdown (all the little formatting buttons it provides format things using markdown syntax).<\/p>\n

Here\u2019s Jotter looking at my Writing folder inside Dropbox:<\/p>\n

\"Jotter,<\/a><\/p>\n

Here\u2019s the view of the nvALT directory\u2026<\/p>\n

\"Jotter<\/a><\/p>\n

And this is working on edits, in portrait.<\/p>\n

\"Jotter<\/a><\/p>\n

iOS<\/strong><\/p>\n

I don\u2019t work on any iOS devices at this time, but I know iA Writer has an iOS version (my daughter has it on her iPad) and I\u2019ve heard very good things about Drafts<\/a> – just make sure it works inside the online version of your cloud service (iCloud or Dropbox or whatever – Drafts does), or (at worst) actually downloads full versions of the drive down to the device, and you\u2019re good.<\/p>\n

Online Tools<\/h4>\n

There are a number of online Markdown editors, especially awesome when you\u2019re working on a Chromebook (because Google Docs get a disappointing ZERO on markdown support), and for those I use the same criteria as the mobile devices: I only use something that syncs with and effectively works entirely inside my online Dropbox drive.<\/p>\n

My current favorite is Dillinger<\/a><\/strong>, which syncs with Dropbox, Google Drive, Microsoft\u2019s OneDrive, and GitHub, pretty much giving you full markdown writing functionality wherever you\u2019ve got web access. Here\u2019s Dillinger asking which file to open in Dropbox:<\/p>\n

\"Dillinger<\/a><\/p>\n

Plus, if you don\u2019t have another option, it provides a pretty good list of export options, if you can\u2019t ship any other way.<\/p>\n

The writing interface with Dillinger is also good, with a solid preview window that\u2019s pretty much just like any other markdown editor app on a desktop.<\/p>\n

Windows\/Linux<\/h4>\n

Speaking of desktops, here\u2019s what I use on my Windows and linux machines.<\/p>\n

First, MdCharm<\/a>, which was originally built for Linux and ported to Windows. I like it because I can use it on multiple platforms, the \u201cproject\u201d window that lets me use multiple directories and my working space (it makes it quite compatible with the stuff created by Ulysses), and it has good options for importing and exporting.<\/p>\n

One of the other things I like about MdCharm is its longevity – it\u2019s been around long enough to still describe itself as a \u201cwiki editor\u201d that \u201cnow supports Markdown\u201d \u2014 that\u2019s a program that\u2019s been around the block a few times, and it still actively supported. Good stuff.<\/p>\n

\"MdCharm\"<\/a><\/p>\n

Finally, there\u2019s Writemonkey<\/a>, which I put to use when I\u2019m doing first drafts. It\u2019s a great program that is absolutely one of the best for getting me to sit my ass down and WRITE<\/em>, but the problem is I do a huge amount of my first draft writing on my macbook air now, so this program doesn\u2019t see as much use has it has in the past (my current WIP was pretty much all written in Writemonkey, but it may be the last big story that is, unless the developer creates a Mac version, or someone else makes something very much like it).<\/p>\n

Conclusion<\/h2>\n

So that\u2019s my workflow. Rather than try to sum it up, I\u2019m going to leave this as is and put it up where people can ask questions and get clarification.<\/p>\n

Hope this helps.<\/p>\n

Edit to add: <\/strong><\/p>\n

Here’s a quick video tutorial to illustrate some of the things I mentioned above.<\/p>\n

\n
\n
    \n
  1. The exception to this has been my long-form writing of first drafts – almost all the stories I\u2019ve written in the last decade and a half have been written in text, mostly thanks to Writemonkey and other similar tools. ?<\/a><\/li>\n
  2. Just try submitting stuff to a publisher in anything but Word. End. Of. The. World. ?<\/a><\/li>\n
  3. The only real downside to nvALT is the fact it\u2019s only able to see a single directory, and that\u2019s where it has<\/em> to work, so I have an nvALT directory in my Dropbox folder, just for this thing, and don\u2019t especially like it. ?<\/a><\/li>\n<\/ol>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

    Lately, I\u2019ve had (or created) several opportunities to talk about using plain text file (and markdown syntax) – how great I think it is for writing and (more importantly, really) how perfect it is for making sure your stuff remains ubiquitously compatible and futureproof. Now, simply saying these things isn\u2019t enough to make everyone (or … <\/p>\n

    Continue reading “My Plain Text Workflow”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_import_markdown_pro_load_document_selector":0,"_import_markdown_pro_submit_text_textarea":"","footnotes":""},"categories":[8,42],"tags":[554],"class_list":["post-12231","post","type-post","status-publish","format-standard","hentry","category-resources","category-writing","tag-markdown"],"_links":{"self":[{"href":"https:\/\/doycetesterman.com\/index.php\/wp-json\/wp\/v2\/posts\/12231","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/doycetesterman.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/doycetesterman.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/doycetesterman.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/doycetesterman.com\/index.php\/wp-json\/wp\/v2\/comments?post=12231"}],"version-history":[{"count":3,"href":"https:\/\/doycetesterman.com\/index.php\/wp-json\/wp\/v2\/posts\/12231\/revisions"}],"predecessor-version":[{"id":15670,"href":"https:\/\/doycetesterman.com\/index.php\/wp-json\/wp\/v2\/posts\/12231\/revisions\/15670"}],"wp:attachment":[{"href":"https:\/\/doycetesterman.com\/index.php\/wp-json\/wp\/v2\/media?parent=12231"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/doycetesterman.com\/index.php\/wp-json\/wp\/v2\/categories?post=12231"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/doycetesterman.com\/index.php\/wp-json\/wp\/v2\/tags?post=12231"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}