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
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.