🥣 Soup Generator

Hey this is a Soup + Diary Cookbook and it is meant to be collaborative! For now you can add a recipe only if you are from XPUB 🤧, but we are working to make it open access.

To add a recipe:

Enter your Jupiter, and go to ~/shared/html/soup-gen/
Open the notebook add_recipe.ipynb
Run the first snippet, it will ask you for some info about the recipe.
Run the second snippet, it will save the recipe in the Soupboat.
You added a recipe!
__CONGRATS__

Each soup has:

Title

Description

Chef

List of ingredients

First ingredient
Second ingredient
...

List of instructions

First instruction
Second instruction
...

TODO short term:

🔍 Ingredients list and filter!!! (like chat reader)
🚫 Inclusive / Exclusive filters
💬 Different types of entries for the cms: recipe, diary, ecc.
🎨 Design
💻 Receive recipe as a form ?
📷 Add recipe picture ?

TODO long term:

💾 Better CMS (and not just a JSON file ah ah)
🦥 Recipes lazy loading :P
📔 Web to print design
📃 Soup pagination
🐱‍🐉 Generative soups, starting from existing ingredients, and instructions, and tags

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?
Or maybe we can try and use Flask?