Open seyfeb opened 11 months ago
This would be a great feature, as right now, I currently use keywords to accomplish, but there's kind of a LOT of keywords, so this would make it all more organized.
A suggestion would be that if/when this goes into the frontend, you be able to click the cuisine to then show other recipes of that cuisine.
Another note would be that the current field type is Text, but it would be great if we allowed this to be a comma or space seperated list or something, that way cuisines that overlap with other cuisines can be accounted for. Example: Sometimes Puerto Rican
can be labeled as Latin American
, or Vietnamese
maybe labeled as Asian
due to using nationality vs region vs sub-region.
The standard would allow for multiple values as far as I get it.
According to the standard (https://schema.org/recipeCuisine) the cuisine is of type text. However, as Christian correctly pointed out, multiple values can be assigned
The cuisine information is present in the standard, I know but is currently not supported by the app. This can be implemented in the app.
Originally posted by @christianlupus in https://github.com/nextcloud/cookbook/issues/1235#issuecomment-1265032001
The
recipeCuisine
is a text property of the schema.org standard but currently not supported by this app. When adding support for this new property several things should be considered:cuisine
property of a recipe in the editorcuisine
in the full recipe viewcuisine
?cuisine
s?