For technical writers

A markdown editor 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 · one license, both desktops · lifetime $19 launch / $29 retail

The technical-writer pain

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.

Why Markd.ly fits docs-as-code

  • 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 (Pro)

    For writers who edit like engineers.

  • Pandoc-compatible export (Pro)

    DOCX/PDF/EPUB/Reveal.js when a doc has to leave the pipeline for a stakeholder who wants Word. Pandoc is the category standard your toolchain probably already assumes — Markd.ly uses the pandoc already installed on your machine rather than bundling its own.

  • CLI render path (Free, Mac)

    Scriptable rendering that fits a docs build / CI step.

  • MCP (read Free, write Pro / Mac)

    AI agents can operate on your local docs, not cloud copies. MCP write is Mac-only.

  • Mermaid + KaTeX (Free), one-time price

    Diagrams and math render in preview without plugins. $19/$29 lifetime — no subscription line item to justify on a tooling budget.

The honest misfit

  • 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 sync; Windows Pro rolling across 1.x

    Your repo and git handle distribution; Markd.ly does not sync anything. Mac is the deepest build today; if your team is Windows and depends on a specific Pro feature, verify its current Windows status.

  • 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 — fast, native, vim-capable, files-on-disk, Pandoc-out — it fits well. For pipeline/publishing/collab, you keep your existing tools.

Testimonial slot — intentionally empty until a real technical writer provides one. No invented quotes.

The editing surface for docs-as-code.

Native Mac & Windows editor that respects plain files and git. Vim, Pandoc, CLI render, MCP. Lifetime $19 launch / $29 retail.

Get Markd.ly

Related