The benefits are that you get distinct ingredient lists for each component but they get aggregated when you create a grocery list.
Check out the discussion from last year here: https://news.ycombinator.com/item?id=31201528
So, are the components different files? That'd definitely help if there's a component that applies to several recipes, like a sauce or crust. However, it could make things more complicated than some would like if they're working on a smaller project, like a reference notebook or a family cookbook.
Power vs simplicity is often a balancing act.
Thanks for making an account! You can only edit you own recipes, but I (the admin) can edit any recipe. I guess you tried to edit a recipe you liked, would you like a "Copy and Edit Recipe" feature?
> So, are the components different files?
Components are what CookTime recipes are made of. A recipe has at least one component, and if necessary the author can add additional components to indicate different ingredient quantities for different components. I have thought about having re-usable components across recipes, I just haven't given thought to how to design the UX for it. Glad to hear that someone else would find it useful, I think I'll reprioritize this.
> I can't figure out how to look at the markdown.
In CookTime there isn't a simple textual representation of a recipe (unless you count the big JSON object the browser sends over the wire.). The backend is a relational database of recipes, components, ingredient requirements, nutrition data, etc...
> Power vs simplicity is often a balancing act.
100%, my primary user is my mother-in-law and I have to be extra careful to make everything easy to use for an enthusiastic retiree.
The idea would be a recipe generator the uses taste profiles, food textures, but has no standard ingredients. If one only had taro root for flour all recipes would sub that in...
Can you tell me more about what you're looking for? CookTime's recipe object modeling is very flexible, maybe I can make what you're looking for in a generic way.
[1] - https://researcher.watson.ibm.com/researcher/view_group.php?...
I have read through this thread to try to make myself more articulate. I guess I'm thinking of it as an ingredient centered approach. The recipe is secondary to whatever is available. The idea would be the ingredients would have tags for properties. The properties would be the nutritional content, cultural references, mouth feel, taste profile, allergens, ...
The combining of ingredients might have less to do with recipes and more to do with necessities and circumstances.
The flour example is probably the most illustrative. Many grains and roots can be used as flour. If one was using taro root flour all recipes would just accommodate that substitution.
The idea is not commercial in nature
The system wouldn’t need to be exhaustive. The data that is already in databases would probably suffice to get started.
The system would be tailored and refined by individuals and groups.
There would be a mechanical turk aspect for graphing/validating “recipes”.
Thanks for commenting.