Thanks for your note. My main reason for loving Markdown is that it is an excellent way to organize and format text documents. As a software developer, I do a lot of work in GitHub, Visual Studio Online, and other collaboration platforms. The teams I work with use Markdown as our common text format for documentation, instructions, reference, and even online discourse such as this forum. Because it’s plain text, it’s easy for both humans and computers to work with. It can be read by humans without special software, imported and transformed by computers, and easily version-controlled.
I also use Markdown in my personal note-taking, because it allows me to focus on the content of the text (e.g. headings, tables, and emphasis) without getting distracted by the appearance of the text (font family, size, margins, etc.). In graphical text editors such as Word, I sometimes get distracted by trying to make a document look perfect instead of finishing the content. Using Markdown helps me to focus instead on what needs to be communicated and leave the formatting to the many excellent tools available.
I don’t just write in Markdown, I think in it.
I love Dynalist because it not only gives me powerful tools for organizing my thoughts into a hierarchy, but also supports the formatting I use every day. I use Dynalist to organize my to-do lists, plan projects, draft documentation, compose messages, write prose, and a dozen other things – all using Markdown. And the best part is, when I need to export out these documents to GitHub, VSOL, Discourse, etc., it’s already in the format the target system wants, no conversion required.
So these are a few of the reasons I love Markdown. As you might guess, Dynalist’s support of Markdown is one of its most important features for me, and I’d be very sad to see it dropped.