<aside> 🧭 Purpose

</aside>

A single place to collect recipes not only to help create the meal plan for the week, but to store the instruction for when you’re ready to cook.

<aside> 🗺️ How to Use

</aside>

1. Use the Gallery to see and add recipes
2. Additional views will quilckly sort the database depending on what you’re searching for:
   1. You can see only recipies for which you have all the ingredients on hand
   2. Your meal plan for the current week as well as the planned menu for the next week
   3. Staples for quick and easy reference during meal planning
   4. Sorted by meal type, if you’re looking for appetizers vs. main dishes, etc.)
3. Learn more about How-to | Add a Recipe which walks through a template to add recipes so that they are all uniform and easy to follow.
4. Links and references to original sources are always included!

<aside> ⚙ Technicals

</aside>

• A database gallery which includes a template for adding new pages.
• Each page in the database will show:
  • A cover photo of the dish
  • An icon representing the dish
  • A relation to the Grocery Shopping database so that any included ingredients can be connected and automated
  • A Rollup, in Relation to the Ingredients database, of the Status property for each ingredient listed in that particular recipe. Showing whether it is “In Stock,” “Out of Stock,” or on the “Shopping List”
  • A “Meal Type” including: “Snack,” “Beverage,” “Dessert,” “Sauce,” “Raw Meal,” “Cooked Meal,” “Ingredient.”
  • “This Week” Property: if tagged as “This Week” it will be included in the additional filters and Meal Planner automations
  • “Next” Property: if tagged as “Next Week” it will be included in the additional filters and Meal Planner automations
  • A checkbox to show whether this is a “Staple” meal or not
  • Two hidden properties (only used for automations):
    • “Done” is only used in the “This Week” filter view of the Meal Planner
    • “Status” which refers to the overall Status of ingredients needed. This is helpful as a database filter, but not as helpful looking on an individual level. If one ingredient out of twelve is missing it will be marked “out of stock” so it’s best to see what percentage of ingredients are out of stock. Maybe a future automation to build?
  • A view of the Ingredients table that will need to be manually filtered to show only ingredients used for the current recipe as well as a new property in the Ingredients database where the specific amounts for each recipe can be shown. Details on how to accomplish this can be found in How-To | Meal Plan