This is an example of people trying to use technology to fix a social problem.<p>I don't know who is editing or curating these recipes. Taste is subjective. At least with Wikipedia, I can point X sources and back my claims up. On here, I could just add random family ad-hoc recipes and no one can really debate them. Which leads to: Mac n' Cheese 1. Mac n' Cheese 2.<p>Traditional cookbooks solve a problem: people may not know any recipes (or want to learn new ones) and want a <i>curated</i> collection from a chef that knows what they're talking about. Not random people online. Sure, books aren't guaranteed to be quality, but they're far less likely to be junk than random websites. They're even better if you only go by word of mouth- ask your parents/grandparents what they used!<p>This wikicookbook idea doesn't solve any problems because it's no better than randomly searching "how to make tres leches cake" and picking some web page that had good enough SEO to get to the first page of duckduckgo.<p>---<p>Things people actually want and/or need:<p>* a website that matches (curated) recipes based on your ingredients. i.e. I can input "chicken bouillon, kale", and have it show me various recipes.<p>* a standardized schema for recipes, i.e. in json. This way we can programmatically build apps, share recipes with friends, and maybe have browser/site integration.<p>* a digital, open source collection of recipes <i>only</i> from chefs/etc with credentials. aka a curated collection.<p>* a website that parses said recipes and can display multiple types of units depending on your preferences.<p>* a website/app that lets you bookmark recipes and automatically parses them with said schema. and lets you categorize/tag recipes so you can filter by "favorites" or "want to try", etc.<p>Bonus points if your app can interface with Apple's Homepod / Alexa, etc, so I can confirm a recipe while I'm cooking or washing dishes. This is the biggest let-down by far for the homepod.