41–42 of 42 posts
It would be nice if as part of the zero config effort, programs (esp. programs that aim to be easy-to-use Web-authoring tools) would focus even more on being as close to zero setup/zero installation as possible, too. To wit: This program is written in TypeScript, a browser-incompatible dialect of JS that is nonetheless regularly compiled to standard JS, e.g. to transform a given module into a form that can run in the…
Earlier quoted context omitted.
> I think a command line tool is better Why not both? It doesn't need to be mutually exclusive; write md2blog.html so it can run either from the command-line or be opened in the browser—whichever is preferable (easiest) at the time. I don't understand your comment about durable storage. If you have a directory of Markdown files on your disk, that's already durable storage. I'm just talking about tweaking the developm…
Perhaps your use case is already supported in a different way, by downloading a single self-contained binary md2blog release, and then > To build and test the site locally (with automatic reloading), run: > md2blog --clean --serve > And open a browser to the "localhost" URL that is written to the console. You can kill the server with Ctrl+C. as described in https://jaredkrinke.github.io/md2blog/quick-start.html
> Perhaps your use case is already supported in a different way
It wasn't a support request.