In the editor, make sure to M-x org-mode. Lots of dated annotations, and a lot of results, in my many recipe files.

A generational git repo of family knowledge is a fun idea to think about.

>Hey grandpa, can you show me the family brisket recipe?

>Sure grandson. But first, let me tell you what git is.

Throw pandoc into the workflow, and have a new edition printed every year or three at your local print shop.

Honestly, not a bad idea. I'd just have to deal with figuring out a good, standardized text-based format. I already use a git-backed Obsidian markdown knowledge base for most of my notes, so it would make a lot of sense to incorporate recipes too.

I think my current recipes app stores entries in the Recipe JSON Schema format[1]. This format is also useful since many websites will offer recipes in that schema. If I could make a conversion layer that transformed between a markdown version and the JSON recipe schema, that would probably be all I need.

* [1] https://schema.org/Recipe

> I'd just have to deal with figuring out a good, standardized text-based format

Why? Recipes are for humans to read, and we're good at accomodating a wide variety of formats as long as they are reasonably sane.

I've looked at a few and I haven't loved any of them. They all have some kind of shortcoming that makes them not usable.

For example, the schema.org schema puts quantities, units, and ingredients in a single field. Fail, IMO.

Other issues include things like not being able to group ingredients or procedures.

I don't have my notes on what I thought of each of the ones I've reviewed handy, but here are some I've looked at:

- https://cooklang.org/

- http://www.formatdata.com/recipeml/

- https://recipemd.org/index.html

EDIT - for clarity, added examples of standards