There's the interactive use case while editing markdown where a UI is very nice, but there's also the use case of putting static site generation into an automated build and deployment process. Command line tools that respect standard command line conventions (exit nonzero meaning error, etc) offer an obvious pathway to automation. Often running a static site generator is but one of many steps in a repetitive process, and one part of usability is how easy it is to call the tool from a bash script or use it inside a rule in a makefile.

I can see you're offering self-contained prebuilt single-file binary releases. From my perspective those are a fine way to address the user request of "I want it to be easy to install without needing to first install and configure n other tools". That's one thing that I reckon hugo got right.

Out of curiosity I downloaded a linux binary md2blog release, and apart from needing to unzip and `chmod +x` it, it ran fine without dependencies -- i don't have any tooling related to deno or typescript installed locally.

Are you using `deno compile` [1] to build these self-contained release binaries?

[1] https://deno.land/manual/tools/compiler