
Increasingly now, I also save a copy of the final plain text file in the project folder with a. I tend to use Byword for bashing out the words because it presents a simple user interface that minimises distractions and then save it back to nvALT which is the 'bucket' or home of most of my content. This means I can seamlessly switch between my chosen editor and nvALT. Tables, footnotes, and citations, to name a fewĪs well as being a database and a plain text editor that is good for writing Markdown, nvALT supports external editors such as Byword and iA Writer.
NVALT FOLDERS PDF
pdf file attached to this article.įor my more complex documents I use a superset of Markdown known as MultiMarkdown which adds: This article and the entire blog and Web site is written in Markdown. The text I write is styled using Markdown, an easy to use set of conventions for marking up text that allows the creation of rich content. I save the files as plain text, a truly portable file format that is cross platform and more likely to be future proof than a Word. It is also very 'keyboard friendly' meaning I don't have to move my hands away from the keyboard to use the mouse a lot - my typing is slow enough as it is! As well as being a text editor, it stores them, and allows lightening fast searches. I start off by writing all notes (and eventually full reports) in a fast 'database' application for the Mac - nvALT. I am trying to build a workflow that is intuitive to me, that allows me to focus on content, and one where I do not have to worry about files getting lost or corrupted. I don't need to include many complex tables and figures or a detailed bibliography. I am not authoring a book or technical manual nor am I writing up a PhD thesis.

They might include a Table of Contents, a simple table or two, perhaps a graph, some images and a few citations.Ībove all, my work does need to look professional. My requirements are fairly modest - the documents I need to write for my consulting work are usually proposals and reports.
