|
|
|
|
<!DOCTYPE html>
|
|
|
|
|
<html lang="en">
|
|
|
|
|
<head>
|
|
|
|
|
<meta charset="UTF-8" />
|
|
|
|
|
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
|
|
|
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
|
|
|
|
|
<link rel="stylesheet" href="style.css" />
|
|
|
|
|
<script src="cms.js" defer></script>
|
|
|
|
|
<title>🥣 Soup Gen</title>
|
|
|
|
|
</head>
|
|
|
|
|
|
|
|
|
|
<body>
|
|
|
|
|
<div class="cookbook">
|
|
|
|
|
<h2>Soup Gen Cookbook</h2>
|
|
|
|
|
<div class="cookbook-info" id="cookbookInfo"></div>
|
|
|
|
|
<div class="recipes" id="cookbook"></div>
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
<div class="intro">
|
|
|
|
|
<div class="description">
|
|
|
|
|
<h1>Soup Generator</h1>
|
|
|
|
|
each soup has:
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
<div class="recipe">
|
|
|
|
|
<div class="info">
|
|
|
|
|
<h2 class="title">Title [string]</h2>
|
|
|
|
|
<div class="description">Description [string]</div>
|
|
|
|
|
<div class="chef">Chef [string]</div>
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
<div class="ingredients">
|
|
|
|
|
<h3>List of ingredients [array of strings]</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>First ingredient</li>
|
|
|
|
|
<li>Second ingredient</li>
|
|
|
|
|
<li>...</li>
|
|
|
|
|
</ul>
|
|
|
|
|
</div>
|
|
|
|
|
<div class="instructions">
|
|
|
|
|
<h3>List of instructions [array of strings]</h3>
|
|
|
|
|
<ol>
|
|
|
|
|
<li>First instruction</li>
|
|
|
|
|
<li>Second instruction</li>
|
|
|
|
|
<li>...</li>
|
|
|
|
|
</ol>
|
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
<div class="todo">
|
|
|
|
|
<ul>
|
|
|
|
|
<em>TODO short term:</em>
|
|
|
|
|
<li>💻 Receive recipe as a form ?</li>
|
|
|
|
|
<li>🔍 Ingredients list and filter!!! (like chat reader)</li>
|
|
|
|
|
<li>💬 Different types of entries for the cms: recipe, diary, ecc.</li>
|
|
|
|
|
<li>📷 Add recipe picture ?</li>
|
|
|
|
|
<li>🎨 Design</li>
|
|
|
|
|
|
|
|
|
|
<em>TODO long term:</em>
|
|
|
|
|
<li>💾 Better CMS (and not just a JSON file ah ah)</li>
|
|
|
|
|
<li>🦥 Recipes lazy loading :P</li>
|
|
|
|
|
<li>📔 Web to print design</li>
|
|
|
|
|
<li>📃 Soup pagination</li>
|
|
|
|
|
</ul>
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
<ul class="questions">
|
|
|
|
|
<em>Questions:</em>
|
|
|
|
|
<li>
|
|
|
|
|
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???
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
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)
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
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?
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
</div>
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|
