I realised that, instead of having to live with a subpar academic writing experience, I could forge my own. ![]() After fiddling around with it for a few days, I figured that I could both load in Pandoc and use it to have a graphical user interface for using it 1, and also that I could spin up a code editor that lets me edit Markdown files. Its idea is simple: Write a web-application, and load that into some binary so that it looks as if you had a native application on your computer. All experiments with actually writing longer texts using Markdown were just that: experiments.ĭuring the late summer of 2017, I played around a little bit with a framework I recently discovered, called Electron. ![]() And back in 2017, although Markdown was already 13 years old at that point, it was being used mainly as additional formatting for README files. So what I found was that there is a disconnect between a bunch of new opportunities that come with Markdown and the ways research works in general. But then, since Markdown is, strictly speaking, source code, you could basically edit it even with your operating system’s built-in text editor. First, Markdown itself requires a completely different style of working than, for instance, a Word document. However, none of these tools immediately appealed to me. I played around with Ulysses, nvALT, Atom, Abricotine, and some online-tools whose names I have long forgotten. Already back then, in the summer of 2017, there were plenty of Markdown editors out there. It all started almost four years ago, when I began discovering the benefits of a Markdown-based workflow and tested out various methods of making this useful for research.
0 Comments
Leave a Reply. |