Here's a demo instance: https://doersino.github.io/nyum/_site/index.html
Nyum is somewhat opinionated, expecting recipes to be written as a series of steps, each with the relevant ingredients alongside an instruction. I first came across this way of doing it via the cuisine LaTeX package (which I then, many years ago, built a custom LaTeX template around), ending up preferring this structure over the more commonly found all-ingredients-first-then-a-block-of-instructions approach. (In the process of recently graduating from university, I found myself contemporaneously graduating from wanting to use LaTeX for everything, which was part of the impetus for cobbling this thing together.)
1. Up and down arrows for the search box autocomplete don't work.
2. The cornerstone of static sites is their timeless simplicity. The software stack here is complicated. The authoring and publishing experience deserves to be as stable and timeless as reading any of the stuff that gets put inside. The process for putting new stuff in should be described in full detail in a document that lives on the same site. <https://news.ycombinator.com/item?id=25676628>
2. I generally agree – but in the comment you've linked, it seems to me like you're arguing in favor of conveniences that CLI-focused static site generators can't easily provide. I've tried to keep things as simple as they can be in the CLI context I'm targeting: Pandoc has been around for quite a while, it's available for pretty much any system as a stand-alone binary, and it's one of the leaders in its niche. And Bash is everywhere. Compare with, say, Jekyll, which requires Ruby and Bundler. That can be a whole can of worms if your OS supplies an outdated version of Ruby (I've been burned before!).
However, I am very interested in using shared markdown standards for various special use cases. I encourage you to focus a little thought on presenting your Markdown for Recipes as it’s own thing.
