What problem is this solving? #1
Description
There will be a directory full of TOML files. Each file will be a unique recipe.
There will be a feature for weekly planning. The TUI (likely via https://github.com/jroimartin/gocui) will allow searching by name, tags, etc. It should also allow searching by prep/cook/total time to prepare. A search might return results for entrees that use chicken and take less than an hour to prepare. It should then be able to build a shopping list. There should be a way to always exclude a given ingredient from the shopping list (such as water).
Meal plans should be saved somewhere for later reference. For example I may want to know how often I have cooked a certain recipe.
Recipes can depend on other recipes as well. While "habanero bbq sauce" should be its own recipe, the "bbq chicken" entree should take its ingredients and prep steps in to account. Dependencies are able to be optional, so when meal planning it can include or not. When making bbq you may not want to go through the trouble of a special sauce, but sometimes you might.
When viewing a meal plan for a given week it should show any prep steps at the appropriate time. For example if Tuesday is pizza then it should know that dough needs to be made on Monday.
Additionally the application can generate a full HTML cookbook from the given recipes. It will generate very basic files with a table of contents. It will be easy to package in to a basic nginx container and hosted on a local network for ease of access while cooking.
It should also be able togenerate a meal plan in HTML that will look similar to a whiteboard meal planner that would stick to your fridge. It would include any prep times, instructions to do on the day before (example "make pizza dough"). This sheet is meant to be printed and attached to the fridge with a magnet.