general thoughts

[ryantuck]

mvp

currently at a decent point with this app, in that i can generate a DAG and can specify which steps are on the same 'level' as each other. manually re-ordering the steps/ingredients in the json allows me to create a prettier graph, with no overlapping edges between the nodes.

So the question becomes - what next? What could I do to get an MVP out the door and generate 10 recipes to share with people? This definitely wouldn't consist of spending my time creating an algorithm to automatically order ingredients etc.

do

• incorporate timing into the x-axis (should all steps have a time var? or only the ones that need it?)
• ingredients
  • photos
  • quantities
• incorporate edge cases (point one ingredient to two separate steps, incorporating quantities on edges)
• adjust sizing of everything to inherently require scrolling. or determine simple way of adjusting sizes of boxes depending on steps

  test out

• a separate view that puts ingredients immediately before the step where they're needed, to limit long nodes cutting through the graph.

and then of course stupid stuff, like make a title and link to an original article.

further improvements down the road would consist of scraping a webpage and hitting it with machine learning and natural language processing to automatically generate the visual recipe, as well as automatically generating the layout of the page.

[ryantuck]

node styling

ingredients can probably get away with wider widths for including images.

steps should probably have a greater height. for description purposes.

actually, steps should also include basic images for bowl, burner, pot, cutting board, etc.

[ryantuck]

orientation

vertical vs horizontal orientation? if i'll be appending text to nodes, this would benefit from a vertical layout. users are also used to scrolling vertically, as opposed to horizontally.

should at least test this out.