Diagrams as text
Mermaid flowcharts and sequence diagrams written inline. The diagram is the source — it diffs, it reviews, it can’t go missing.
Keep methods and reports as Markdown, results in calculating sheets, and interactive findings as HTML Arts. Co-authors and AI refine the work together with comments and version history.
Plain .md files. Readable in fifty years, not just this decade.Three ways technical writing loses its provenance — and what keeps it.
The write-up sits in a cloud drive; the code sits in a repo. Neither knows the other’s version.
Both are files in one repository, moving together through the same commits.
The pipeline diagram is an image exported from a tool whose source file is on a dead laptop.
Mermaid: the diagram is text in the document, edited and reviewed like prose.
“Which threshold did we use in the March draft?” — and nobody can say.
Version history with a visual diff. Open March, read the number, move on.
Everything below ships today. We’d rather list three real things than twelve aspirational ones.
Mermaid flowcharts and sequence diagrams written inline. The diagram is the source — it diffs, it reviews, it can’t go missing.
Results tables backed by a 80-function engine with cross-sheet references — summary statistics stay in the document, not a stray spreadsheet.
Several authors in one document at once with live cursors and CRDT sync. No check-out, no “are you in the file?”, no lost paragraphs.
Being straight with you: DotMD does not render LaTeX equations and has no citation manager. If your writing depends on either, it isn’t the right tool for that document yet.
Portable Markdown and self-contained HTML keep the work accessible, while namespaces, permissions, and versions preserve its context.