Folio WriterMarkdown for serious scholars
Readable source. Git-compatible. Syncs with your data pipeline. Compiles to anything. This is why Markdown is the native language of academic writing.
Your source stays readable
LaTeX looks like line noise. Markdown reads like prose:
# Introduction is obviously a heading. **robust stress** is clearly bold. A citation like [@Smith2023] is instantly recognizable.
You can read your manuscript source six months later and understand it without learning a language.
Version control is native
Git handles Markdown beautifully. Your commit history is a real history—line diffs are readable, merge conflicts are solvable, branches are meaningful. You can see exactly what changed in each paragraph.
LaTeX diffs are gibberish. Markdown diffs tell a story.
It's the data scientist's standard
If your research involves Jupyter notebooks, R Markdown, or Python scripts, Markdown is already there. Your lab's computational work speaks Markdown. Your manuscript should too. Figure captions, analysis notes, data provenance—it all flows naturally from data to text.
One source, many outputs
Folio compiles your Markdown to:
- PDF via Typst (modern typesetting, fast compilation)
- PDF via LaTeX (if you have specific journal requirements)
- Word .docx (for collaborators stuck in Word)
- HTML (for preprints, blogs, web publishing)
One manuscript, infinite formats. No more copy-pasting into Word. No more rebuilding for preprint servers.
Collaboration without the apocalypse
When your coauthor edits Markdown, you can actually read what they changed. Track changes show real diffs. You merge contributions, not guess at what File_v3_FINAL_real.docx contains.