I’ve always wanted to make a GitHub for recipes. You can fork recipes. Submit pull requests. Public and private repositories. Versioning and commit history. Share with friends, Etc.
I have a little pet project from a long time ago that I tried to start with this, it lets me describe recipes like this:
Recipe|Turkey Stuffing
I|4 C==French bread hand torn into small pieces (about 1/4 inch pieces)
I|3/4 C==Butter
I|3/4 C==Onion (minced)
I|1 C==Celery
I|1 Tbsp==Salt (less if bird is butterball or self basting)
I|pinch==Pepper
I|2 Tbsp==Sage, thyme, and marjoram mixture
D|Melt butter in large skillet over low heat
D|Add onion and celery & spices, stirring often until it all smells great.
D|Pour 1/3 of the hot mixture over all the bread, then toss, then 1/3 more, toss, then last 1/3 and toss.
From there it can produce a pretty webpage to view the recipe, or produce an ingredient list for shopping (and it has some basic concept of combining shopping lists sanely), and lets me search by ingredient.
I always debate fleshing it out. 99% of the time spent with something like this is curating the recipes themselves, which I'm far from an expert in, and I don't want it to become a big time waster.
I used Markdown for recipes for more than a decade, where UL were ingredients, OL were steps, and you could use as many sets of both as needed. With some CSS and JS it worked pretty well, but wasn't super accessible for family members to add recipes to (but was great for me).
That looks like a recipe site inside GitHub. What I wanted to make is a standalone website with git like branching and such. Everyone has their own little twist on recipes. I think it would be fun! I just need the time!
I always debate fleshing it out. 99% of the time spent with something like this is curating the recipes themselves, which I'm far from an expert in, and I don't want it to become a big time waster.