Special interactive recipes

david commented

2020-05-21 06:52:43 +00:00

(Migrated from dev.cryptec.at)

Some recipes are more complex than others. Bread or Pizza for example can be made in a variety of ways and there is not the best way to do it. I propose a kind of interactive recipe for that. Each interactive recipe has to be uniquely designed to fit the dish it is about. As such a special frontend component will have to be created for each recipe. These recipes are part of the regular search results and look like normal recipes from everywhere except their detail view.

Example for bread:

There are at least two kinds of bread I would like to feature in Claypot:

A very simple "do it like this, get a reasonable bread"-recipe, yeast-based for simplicity.
A more complex form that allows you to adjust water-content and amount of sourdough.

Some recipes are more complex than others. Bread or Pizza for example can be made in a variety of ways and there is not *the* best way to do it. I propose a kind of interactive recipe for that. Each interactive recipe has to be uniquely designed to fit the dish it is about. As such a special frontend component will have to be created for each recipe. These recipes are part of the regular search results and look like normal recipes from everywhere except their detail view. Example for bread: There are at least two kinds of bread I would like to feature in Claypot: 1. A very simple "do it like this, get a reasonable bread"-recipe, yeast-based for simplicity. 2. A more complex form that allows you to adjust water-content and amount of sourdough.

david commented

2020-05-21 06:53:03 +00:00

(Migrated from dev.cryptec.at)

@root Any opinion on this that you would like to share?

root commented

2020-05-21 07:15:44 +00:00

(Migrated from dev.cryptec.at)

From the user perspective there should way to save those configured recipes, maybe they get converted to "real" recipes that simply are not shown in the normal recipe list? How do you imagine the technical implementation?

david commented

2020-05-21 10:09:24 +00:00

(Migrated from dev.cryptec.at)

I like the idea of saving configurations of these special recepies.

From a technical point of view I imagine a new field on the recipe model, maybe called special_recipe, CharField, can be blank. It can be set to a vue component name and if it is set, this component will be rendered by the frontend.

To achieve something like saving (and restoring, obviously) of special recipes I propose a simple interface that these special recipe vue components must comply with: Have them support v-model and let the data be JSON serializable. We can handle all the CRUD operations in some generic components that way.

I like the idea of saving configurations of these special recepies. From a technical point of view I imagine a new field on the recipe model, maybe called `special_recipe`, `CharField`, can be blank. It can be set to a vue component name and if it is set, this component will be rendered by the frontend. To achieve something like saving (and restoring, obviously) of special recipes I propose a simple interface that these special recipe vue components must comply with: Have them support `v-model` and let the data be JSON serializable. We can handle all the CRUD operations in some generic components that way.

Rows
Columns

Special interactive recipes #66