Soup Generator
each soup has:
Title [string]
Description [string]
Chef [string]
List of ingredients [array of strings]
- First ingredient
- Second ingredient
- ...
List of instructions [array of strings]
- First instruction
- Second instruction
- ...
TODO short term:
- 💻 Receive recipe as a form ?
- 🔍 Ingredients list and filter!!! (like chat reader)
- 💬 Different types of entries for the cms: recipe, diary, ecc.
- 📷 Add recipe picture ?
- 🎨 Design
TODO long term:
- 💾 Better CMS (and not just a JSON file ah ah)
- 🦥 Recipes lazy loading :P
- 📔 Web to print design
- 📃 Soup pagination
Questions:
-
What is the best solution to receive recipes from users??? We imagine it to be
something like an HTML form that the NGNIX server could parse and then put in
the cms.json file??? or there's a better way to do it? is this dangerous???
-
What is the best solution to add images?? Can we upload them on the soupboat
from the form? We need to process them with something in order to reduce size?
Or just put a limit in the file upload maybe? (to avoid a server mental
breakdown)
-
Can we setup something like a CI/CD pipeline for deploying the Cookbook directly
from the git repo??? Maybe it could just be setting up some hooks in git to
transfer and replace the static file to the soupboat public_html/soup-gen/
folder on new commit?