← Back to Ideas

Github for Recipes

April 6, 2022

Recipes evolve and change over time. People add their own twists and find small improvements. So where is version control for recipes?

The Spark Notes Version

---------

Everyone loves recipes. But there are 10s of millions on the internet. No one is able to verify which are best and you can't save your own changes.

This is Github for recipes. Search for the right recipes, and find the most referenced / contributed to. If you find a way to improve it, you can fork your own branch, or request to change the original. You can see all the past variations.

If you're a company working on a food product, you can keep all of your recipes in one repository. You can see all the past versions, and keep track of changes.

Ideas like this, right in your inbox.

Let's be honest. You don't want to have to come to our site every time you want a new idea. Let us send ideas like this one right to your email, for free, every week.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

The Long Version

---------

Recipes are some of the most shared things on the internet. Whenever any of us want to cook something new, we Google for the best recipes. Some of us have favorite chefs or influencers who we go to for their concoctions.

But the thing is, recipes really don't have a great internet infrastructure. They're all overly optimized for SEO. It's a cliche at this point to mention it, but no one wants to read your life story to finally get to your recipe for banana bread.

There also isn't a great way to find recipes, evaluate their quality, or get a sense of the community reaction to the recipe. Of course you can try to parse blog comments, but good luck with that.

This idea fundamentally changes the way that recipes work on the internet, for the better. Let's first go over what it is.

The idea is Github for recipes. If you don't know what Github is, it's a website where programmers can upload their code. Any time they make any changes, it is saved as a version. Anyone can go back and see every previous version. This means you don't lose your work, and if you make a mistake you can always revert to a previous version.

Github also provides what are called repositories. These are folders where a programmer can upload a whole bunch of different pieces of code, to organize them.

Finally, Github is built for community collaboration. Anyone can take a piece of code in a Github library, and either fork it (where they create their own copy and can make changes), or create a pull request (where their changes are adopted into the main code).

We would implement each of these features into recipes. Companies who make food products would be able to keep their recipes in one central repository. Their chefs would be able to update them and see all previous versions.

Communities could collaborate on the best chocolate chip cookie recipe. Anyone can then fork the recipe and make their own changes.

There would be a robust search where people could find the best recipe for a given food product, based on number of contributors, age, upvotes, etc.

This product would fundamentally change the way we cook. I hope you make it.