4 ms·
The edit wars would be horrible. Everyone has their own recipe for any given food item, plus endless variations.
by layer8 5y ago
The edit wars would be horrible. Everyone has their own recipe for any given food item, plus endless variations.
- kuschku 5y agoMake it a namespaced wiki. Every user can only create and edit recipes in their own namespace, or the namespace of groups they’re a member of (like GitHub treats repos for example). Then you could, as user, follow users you like. Each recipe would be in structured format, but could also have rich text introductions / explanations, if users wish to add such information. You could even let users add custom styling to their own namespaces/subwikis, as tumblr, myspace, wordpress, youtube and reddit used to do / still do (with a way to turn this off as user, if you just want the plain content)
- diogenesjunior 5y agothen it comes down to just building your own reddit style site centered around food recipes
- nybble41 5y ago> (like GitHub treats repos for example) This is the way. Publicly read-only repos with easy access to forking and pull requests are far superior to wiki pages with no access controls. Compared to current GitHub you would mainly need to add support for structured data, ratings, and indexing.
- y04nn 5y agoI'm not sure, is there not one standard, most accepted recipe and then N variations? Also, I would not except edits to be on ingredients, but mostly on the method. If a user would want to modify ingredients, he could create a his "regional" variation. But I see the wiki more as a reference book on recipes and their well known variations (which is mostly what I'm looking for when searching for a recipe) than a sharing platform/pseudo social network.
- lazyasciiart 5y ago> is there not one standard, most accepted recipe and then N variations? No. In many cases there are N variations that all claim to be the standard.