Tools for Academic Writing
Scholarly writing workflows generally center around .docx
as the defacto standard.
However, traditional word processors are NOT the only way to write a paper, and can impose significant limitations on how we collaborate and communicate.
Below we look at some of the options and issues as a frame, before exploring about how Markdown can be used for academic writing.
Word Processors
- Desktop software: MS Word, Libre Office
- Collaborative cloud platforms: Google Docs, Proton Docs, Nextcloud, ownCloud
- Academic focused platforms: Authorea, SciFlow
MS Word has been the standard tool for writing academic papers for many years. However, being familiar and pervasive doesn’t mean it is truly easy to use! Anyone who has spent hours trying to figure out some odd formatting quirk, seen the entire theme disappear when pasting something in, or opened a document from an earlier software version will understand some of the limitations of these platforms.
First, in a WYSIWYG editor content and presentation are mixed, semantic structure of the document is easy to confuse with styling. Formatting is hidden in the interface and can be difficult to sort out, meaning often “what you see is not what you get” and you can’t figure out why.
Second, MS Word is a proprietary tool linked to proprietary formats. Tools like Google Docs are proprietary platforms with unclear privacy, security, and ownership. These situations presents challenges to collaboration, innovation, and sustainability.
You can write in Markdown and convert into DOCX and other formats…
Document Preparation Systems
- Software: LaTeX (ConTeXt, LuaTeX, or others that build on top of TeX)
- Visual editor: TeXstudio
- Collaborative cloud platforms: Overleaf
LaTeX is a system to separates the plain text content of your writing from the actual document design / typesetting presentation.
TeX and LaTeX have long been the standard for academic writing in fields that need to represent mathematical equations. They are extremely powerful for creating PDF/print documents, but are complex with steep learning curves which can make collaboration difficult. The source code of LaTeX documents are not necessarily easy to read or preview until compiled.
Importantly, LaTeX was designed for high quality PRINT preparation–unfortunately this means the PDFs it generates are often not accessible by default and might not be the best for digital distribution. If you are creating PDFs for courses or learning management systems, you will need to carefully ensure it meets accessibility requirements! (See Accessibility on Resources page)
Some new alternatives have been developing, such as Typst (or even LaTeX3), to provide a more modern approach.
You can write content in Markdown and use LaTeX to export print versions…
Code Notebooks
- R Markdown (with Bookdown for creating larger documents)
- Jupyter Notebook (share with nbviewer or nbconvert)
- Quarto (scientific publishing focus, with Python, R, Julia, or Observable code written in notebooks)
If you are writing about research involving code and visualizations, code notebooks are a great option. These systems integrate Markdown (or other lightweight markup language) with code blocks to create documents with live or rendered code. However, they are situated in ecosystems that require language specific skills, and can result in “dependency hell” if not correctly packaged, which are issues for sharing and sustainability.
These systems already integrate Markdown…
Lightweight Markup languages
Lightweight markup languages seek to be easy to write and read, while providing expressive semantic markup that can be used to transform the marked up content into different formats. Some popular examples (other than Markdown) include:
Opportunities:
- Simple(ish) to learn
- Plaintext and open standards -based
- shareable and useable by any device with no special software or license needed
- preservable / sustainable - easy digital preservation and human readable
- version controllable - you can use the full power of Git or other version control systems
- Separation of content/semantics and presentation
- spend less time formatting, more time writing - don’t waste time in complex and frustrating formatting in Word that will be deleted by publishers anyway!
- structure content as data = powerful
- Flexible outputs - ready for web, ebooks, blogs, not just PDFs.
Example: Karthik Ram, “Git can facilitate greater reproducibility and increased transparency in science”, Source Code Biol Med 8, 7 (2013), https://doi.org/10.1186/1751-0473-8-7. Available at https://github.com/karthik/smb_git
Markdown
Markdown is a quick and simple standard to create formatted documents in plaintext.
Originally developed in 2004 by John Gruber with Aaron Swartz based on how people intuitively write emails, it focuses on being human readable, yet designed to easily convert into HTML for the web.
Markdown files are plaintext, usually with the extension .md
, and can be edited by any text editor.
Think of it as source code for your document, that can be compiled to generate outputs such as HTML, .docx, or PDF.
Because of it’s simplicity and flexibility, a growing number of websites, note taking apps, code notebooks, and publishing systems use Markdown to format content, making it a powerful, cross-platform option for academic writing–there are applications through out the research and publishing ecosystem!