morphy VS tinyjam

This is so true but my biggest struggle. Everything I have just shipped before I thought it was ready did really well, yet I still struggle to do it. I built my own static site generator, which I use for my own blog: https://github.com/kiramclean/morphy

I need to at least add documentation, and obviously there's a million other things I think I need before I tell anyone else about it.

I recently set up code coverage reporting with Codecov for a Clojure project of mine that uses tools.deps and builds on CircleCI. It turned out to be pretty easy but the documentation for the various parts was a bit ambiguous, so I wrote down the steps here in case you're looking to do the same. You can see all the changes it took together in context in this commit where I set it up for my project.

I have a ton of unfinished open source projects, but here's a recent small one I believe can take off:

https://github.com/mourner/tinyjam — a bare-bones, zero-configuration static site generator that deliberately has no features, an experiment in radical simplicity.

Essentially a tiny, elegant glue between EJS templates and Markdown with freeform structure (enabling incremental adoption) and convenient defaults, written in under 120 lines of JavaScript.

I also made a modern EJS implementation specifically for this: https://github.com/mourner/yeahjs