Ideally one would be able to learn language with the same kind of etymological study, however I put it to you that is FAR more complex and boring and doesn't have more fact / science based rules than cooking does.
Also, cooking is a very personal / familial / cultural experience. Recipes can be passed down a single family, whereas language is much more broad.
I guess what I'm trying to say is that the knowledge graph for cooking is smaller and more personal, and is better served as a personalized note taking system as opposed to a gamified interface to a public database.
For example, if I would prefer recipes with eggs and potatoes as opposed to recipes with spinach and mushrooms, I should be able to cater my knowledge graph to learning more about recipes that use those ingredients (ideally with some balance in nutrients).
One thing at a time, though! This is just an MVP.
HN is going to tend to attract more of the individuals who prefer the deep dives.
As always, the trick is finding that first customer base, and figuring out how you can grow with them to keep them, and get them to spread the word.
https://www.reddit.com/r/cookingforbeginners/comments/vbgqq6...
Here's the technical approach we're taking with the goal of taking a very hairy knowledge graph and turning it into a remarkably simple, even magical, user experience: https://parsnip.substack.com/p/a-new-hope