GitLab

requires some details from #227 and some time to ferment.

purpose/motivations (to be edited and/or broken into individual issues as required as we approach more structural details...)

the site should focus on ways of collecting and connecting information about food as more than just instructions in an open, extendable, conversational manner. direct where appropriate, ambigouos and adventurous where possible.

presented in a way that can organise and contextualise the range of material practically and conceptually, with capactiy to translate and interconnect between different "resolutions" within wider food systems (e.g. ingredients -> dishes -> meals -> cuisines )

explore methods of cooking that are not recipe-centric. (e.g modular cooking, engineering maps)

test & itterate using material from the open sauces book as starting point

open to annotation and commentary, but easy to distill the instructions ("how do I make it?") community sharing of recipes, techniques and stories in context.

easy to input and find information, but simultaneously interconnected and entangled (yeah right!) see #248

not just about cooking but the eating experience: spontaneous serving, performing and eating moments

an API as a way of enabling other ppl to create thses features, extend and/or mogrify. soon as practical

• organisation and levels of detail

  • ingredients -> dishes -> meals -> cuisines
  • cross cuttling (i.e commonalities between cuisines)
  • ingredient pairing and connections (c.f. foodpairing)
  • combination & replacements
  • translations (names of ingredients & measures)
  • annotations
  • use opensauces book as starting point
  • context / textual elaboration available each 'level of detail'

• posts / notes/ context

• about measurment

• what makes a cuisine?

• ingredients?

• flavour pairing

• experimentation

• recipeces and improvisation

• automated extraction and analysis