For technical writers
You already know the constraints: docs live in a repo, they are plain markdown, they get reviewed in pull requests, and they ship to a static site or a docs pipeline. This page is the honest fit — and the honest misfit — for that workflow.
Mac · Windows · Linux · iPhone & iPad · Android · one purchase, every platform · $19.99 one-time
Docs-as-code means your prose lives next to code: .md files in version control, edited in branches, reviewed as diffs. Most “nice” markdown editors fight that — they want to own your files in a vault or a database, or they are so prose-focused they don't respect that the file is the source of truth and git owns it. You end up in a code editor for safety and lose the focused writing surface.
Files on disk, plain .md, nothing in between
Markd.ly edits the files in your repo. It does not import, vault, or containerize them. Git stays the source of truth; diffs stay clean.
Vim mode (desktop)
For writers who edit like engineers: normal, insert, visual and command-line modes with the core motions and operators.
DOCX, EPUB, LaTeX and slides export (desktop)
For when a doc has to leave the pipeline for a stakeholder who wants Word, plus HTML and PDF. Nothing to install: the Linux app converts on your machine, and on Mac and Windows our conversion service converts the text and keeps nothing.
Command-line converter (Windows, Linux)
--render turns a markdown file into HTML, DOCX, EPUB, slides or LaTeX on the machine, with no window, so it can sit in a docs build step.
Search the docs folder (desktop)
Find text across every markdown file under the current document's folder, with a case-sensitive option.
Mermaid + KaTeX, one-time price
Diagrams and math render in the preview without plugins. $19.99 once, so there is no subscription line item to justify on a tooling budget.
No docs-site framework
Markd.ly edits markdown; it is not a static-site generator, a docs portal, or a publishing pipeline. It sits next to those, editing the source files — it does not replace MkDocs / Docusaurus / etc.
No collaboration or review features
Review happens in your VCS / PR tool, not in Markd.ly. There is no in-app commenting or co-editing.
No folder sync
Your repo and git handle distribution. Markd.ly's stable releases do not sync folders; its cloud library holds only the documents you add to it, one at a time.
No plugin ecosystem
If your workflow needs a specific editor plugin, Markd.ly won't have it.
Stated plainly: Markd.ly is the editing surface in a docs-as-code stack, not the whole stack. For the writing itself (native, vim-capable, files-on-disk, DOCX out) it fits well. For pipeline, publishing and collaboration, you keep your existing tools.
Testimonial slot — intentionally empty until a real technical writer provides one. No invented quotes.
A native editor for Mac, Windows and Linux that respects plain files and git. Vim mode, DOCX, EPUB and LaTeX export, and a command-line converter on Windows and Linux. One-time $19.99.
Related