-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add user Comments #8
Comments
@poltrian Yeah, could be neat. Comments are actually supported in the schema.org standard. We can use the NextCloud user credentials for the user information. |
Where would you add the user credentials to a comment? to |
@Teifun2 the schema.org standard has a "comment" field we could use |
@mrzapp Yes i did see that. But if we want to store the credentials of the user + its comments, how do we do this? According to schema.org a Comment can have a Text (which would be the actual comment?) but what field would contain the user credentials? author?
|
@Teifun2 exactly, the |
Although i think this is a very good feature i would leave it aside for the moment and first focus on #116 #47 and potentially #11 . I think the aspect of storing your own recipes and using them should be the main task. Sharing and collaborative work can come when the individuals database is at a certain level. |
I second this one. One could use the tagging to indicate stars already but it would be nice for that the be represented visually. I would really like to see dated comments that would enable technical notes. E.g. "needs 60min cooking not 45 in our shitty oven". Less worried about the collaborative side of comments. |
May if you Update a Cooking step a popup appear which request to check if comments are out of date and could be removed. |
"needs 60min cooking not 45 in our shitty oven" This. Or comments like: "Jan. 21: Used ordinary onion instead of scallion, and butternut pumpkin instead of hokkaido. Pumpkin took a bit longer to soften, but turned out great." Or: "For some reason, meat turned out tough. Screw the supermarket. Buy at the butcher next time. Also, try less heat." For me, keeping track of success and failure is an important part of recipe evolution - it's what helps you improve. To me, this isn't related to rating or collaboration - just a simple area for private notes. Probably, comment field would be best at the bottom (after all, that's where you'd scribble manual notes on a printed recipe). [Of course, if everyone could arrange order to their liking, that would be even better, but let's not be too greedy now. :-)) ] |
Hi,
comment like stars or Like, or better you can write something "worst ever" "love" "you could add ... to ... make it better
The text was updated successfully, but these errors were encountered: