Keep it simple / reduce friction. Value the individual document, but also the way the individual document dynamically connects to others (metadata). Support easy resequencing (for managing collections, set lists, submission packs) etc. Portable, non-proprietary, application agnostic and robust metadata (tags and keywords in the body of the document). Low level tech vs high level of control so it's easy to fix something when it goes wrong. A system that supports workflows that match the way you think, rather than forcing you into an unintuitive way of working. Respect the throughline from first thought, through first draft and successive edits, to publication and/or performance. ...

First thoughts (draft manifesto?) for a computer/tablet based writing system for poets
Jacob Sam-La Rose

Just recently refined my writing/publishing workflows on iOS. It occurs to me that so many tools for writers ignore the needs of poets. Let's talk about Markdown, for example. All the cool kids use Markdown. But it's completely counter-intuitive for me to double-space every time I need to force a line-break. And indents? Forget about it. (Quick hint, Markdown poet: the "pre" tag is your friend, if you don't already know.)

Currently, I write in plain text files, with a bit of Markdown for easy formatting. As my iPad is my primary creation tool, I use Drafts for quick capture and Editorial for any editing or other heavy lifting. In Editorial, I've been able to design workflows that compile collections and set lists or "scripts" for performances from individual documents. But I'm wedded to the idea of devising a set of baseline principles that might support any other poets who struggle trying to find a system that makes sense, or who simply make do with what they've got because they don't have the time or energy to fuss with the tech in order to figure out a potentially better way of doing things...