Leading up to the launch of The Sweet Setup, we were wrangling about 20 active documents. I was working with half-a-dozen different authors on their app reviews along with writing several reviews and blog posts of my own, and Jeff Abbott was editing everything.

To manage all of these documents we use Editorially.

It’s awesome. Here’s why.

  • Markdown support: All the writers we work with prefer to write in Markdown. I prefer markdown. And, well, Editorially supports markdown syntax highlighting in the browser. It also displays images inline. When you’re done writing you can export your writing as an html, markdown, plain text, Latex, rich text, MS Word, or ePub file. Wow.

  • Collaboration: invite people to join the document as read-only privileges or with editing privileges. You can highlight words and passages to make notes about, and you can comment on the document in general.

  • Track changes and version control: Editorially auto-saves as your working on a document, so if your browser crashes you don’t lose your work. It also keeps all the versions of a document, and allows you to compare the changes of one version with another.

  • Document status: Documents start as “Draft”, and as you progressively work on them you can change their status to “Reviewing”, “Revising”, “Copyediting”, and “Final”.

These states worked perfectly with our workflow, and followed perfectly the progression of our articles from the initial submission by a contributor, my reviewing of it, the author’s revising of it, and then Jeff’s editing of it. When visiting my Editorially dashboard I could see instantly what the state of each document was, and knew which ones I needed to attend to myself.

  • Dropbox support: you can link Editorially to a folder in your Dropbox and then send an article to that folder. This is Editorially’s answer to “archiving” since there is nowhere to move documents that are in their final state and which have been published and that you no longer need to keep on your dashboard. This is how I archive all of our published articles, and it works very well.

  • Pasting into a document: Copy rich or formatted text from one place and when you paste it into Editorially it will format in Markdown. Even images. Amazing.

  • iPad and iPhone friendly: Editorially is a web app only with no native apps. However, it has a responsive design that works great in Safari on the iPad and iPhone. It can be a bit clunky if you’re making lots and lots of notes and annotations, and I wouldn’t want to spending hours a day, every day, working in Editorially on my iPad. But I edited several documents from my iPhone and iPad with no trouble.

Our Editorially Workflow

Being editor-in-chief, I was reaching out to potential writers asking them if they’d like to do an article for the site. Once they submitted their draft to me I would paste it into Editorially and read through it.

Because Editorially lets me make highlight words and passages, it was easy to make comments about what I felt were good, what needed improvement, and what was missing altogether. I would also make general comments on the document itself such as, “All done. Your turn.”

If I hadn’t already, I would then invite the author to join the document so they could see all my comments and edits, and then they make any changes and leave comments of their own.

Some articles were done after just one pass. Others took several rounds of back and forth work to get it to a place where we were completely happy with it.

Once the article reached the point where the author and I were happy with it, then I would invite Jeff to join. (Jeff is the editor for The sweet Setup.) He would then read through the article for the first time, making sure it had a good flow, made sense, covered all the bases, and was free from typos and other grammatical errors.

When Jeff was done, he’d set the article’s status to “Final”. I would then export the markdown out of Editorially and paste it into our CMS. Editorially also supports publishing to WordPress, but I don’t use this feature — we have quite a few custom fields and other metadata tables set up in our WordPress install that hinder us from just publishing straight to the site from Editorially.

Technically, Editorially is still in beta. There are a few bugs here and there (for example, the dashboard doesn’t remember my preference for displaying documents in a grid format or a list) and there are some other features I’d love to see added (such as the ability to transfer ownership of a document from one user to another, or an “inbox” that listed all the recent activity on all my documents). But these are small issues, and Editorially has proven to be an invaluable tool for us.

We are using it to get a lot of work done without losing our minds. I can’t imagine what our workflow would look like without Editorially.