[terrabitz]

I like having my recipes in digital format, but the lack of notes, annotations, and editing history is a big weakness in most of them. I would love one that offered a git-like interface for recipes: it could track the "diff" of a recipe as you tweak it, and you could "commit" each variation along with notes about the outcome.

[toast0]

I'm not much of a cooker, but I helped my spouse organize her recipes into a little site. The backend is just a SMB file share with one text file per recipe. And there's a perl script that looks for changes, generates the HTML, and pushes it out to the web, so it's easy to reference on the go, maybe while at the grocery store or something. The perl script needs to do a bit of magic around character set detection, because windows likes to do dumb things, but otherwise, it's pretty straight forward, other than kqueue is a bit arduious for watching a whole directory tree (I think Linux has a better api for that, but it's doable in kqueue).

No diff tracking, but you can put notes in as you like, it's just text. You could use git as others suggested too. It's just text, git is good for changes in text files.

[TheCondor]

I started transcribing them. I’ve been using typst, could probably change back to latex or context or something if needed. I have a git repo, organized in to several sections. I found a template and hacked it to my liking, including a section for comments and remarks and then organized the sections in to chapters.

Took an hour or so to kind of get the framework in to place. We do family meals regularly (eat with your kids, it’s a good thing) and I record the ones they like, add notes as we change them. It’s sort of a secret project, I plan on giving it to my kids as a wedding gift or something. Only about 30 in it so far but I add one or two a month, I try to capture some pictures to go with it.

[SoftTalker]

Why not just put your recipies in a text editor and then use git?

[morkalork]

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.

[pessimizer]

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

[downut]

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

[terrabitz]

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

[daotoad]

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

[SoftTalker]

> 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.

[batch12]

That's what the idea was. Something you could diff and fork (heh) other recipes using git.