devfort/nosebag

Yet another recipe management system

nosebag's Issues

Alternative ingredients

I have some recipes that list ingredients that can be substituted for others — eg the original gumbo recipe mine is based on allows for courgette instead of okra where it is hard to find.

Would Dr Syntax be open to representing alternate ingredients, and possibly alternate cooking steps as a result?

Schema

Was Dr Syntax planning on making a real schema at a real URL? As much as I enjoy the current value, it isn't exactly helpful.

Alternative preparation

I have some recipes for sodas that can be prepared in multiple ways — by brewing, mixing with seltzer water, carbonating with a syphon, or mixing with spirits to make a cocktail. The ingredients and preparation of the syrup are the same, just the final step(s).

While I can store them as separate recipes, would Dr Syntax be open to representing alternative steps?

Recipe descriptions

Many recipes are presented with prose descriptions. I suggest a key or keys at the top of the recipe object to represent this. Either keys like description / introduction / postscript / history... or a single key that contains an object.

The most common across my recipe books is a paragraph or several before the ingredients and steps, but I have also seen both a personal introduction to a recipe, then a description of it, the ingredients, the steps, then more prose afterward such as cooking tips and alternatives.

I would suggest they contain free text for the renderer to interpret as it will (eg I will be adding markdown to mine).

Media files

Dr Syntax states "Media files are referenced..." but is silent about how they appear in the recipe. My suggestion would be a media array that can be attached to the recipe as a whole or an individual step, each entry being an object containing the path to the media and optional extra keys (width, height, alt text, HTML class to apply...).

Recipe timing

I find it helpful to have a guide as to how long it'll take to cook a meal. Especially when the first step is "the day before, prepare…" such as when marinading chicken.

I suggest a key at the top of the recipe object time which contains an object containing timings, something like:

'time': {
    'advance': 3600,
    'prepare': 30,
    'cook': 60,
}

Keys could be arbitrary or specified.

At its simplest, values would be an integer representing the minutes. But I am also thinking of a recipe that has a prep which has rice refrigerate "for at least two hours, preferably overnight." and how that could be encoded with min/max values.

Adding more keys to recipe.json?

I've started experimenting with publishing my recipes on my site — http://marknormanfrancis.com/recipes/chicken-and-chorizo-gumbo

I don't use JSON to store posts, and was pleasantly surprised that just saving the gumbo JSON as TOML worked fine (assert json_object == toml_object). Anyway. If you look at the TOML I'm using for the page you'll see that I am using more keys than were in the original gumbo JSON as part of the recipe, and then some more for the metadata of my publishing system.

Questions:

1. Is Dr Syntax concerned about keys in the data that are unknown?
2. Would Dr Syntax like to adopt prep/cooking time? (now issue #3)
3. Would Dr Syntax like to adopt an introduction/description key? (and maybe footer/postscript) (now issue #4)
4. Dr Syntax states "Media files are referenced..." but is silent about how. Would Dr Syntax care to elaborate? (now issue #5)
5. Was Dr Syntax planning on making a real URL for the schema at all? (nb I am now listening to the Dr Horrible soundtrack, so that's fine) (now issue #6)