The beauty of using Obsidian for this kind of thing is that I can attach metadata to each recipe or ingredient note. This allows me to query notes as if they were in a big database, which can be used to look at my cooking knowledge from several different angles

all the lunch recipes under 20 mins long:

When making a recipe the creator will try and find the combination of ingredients that will work best for most people. But I am not cooking for most people, I am cooking for myself.

The internet is full of different ways to achieve the same end goal. Its always funny to see one youtube video say "you must absolutely avoid this" after just seeing the same tip in another video. After trying to recipe out for myself, I will include a embedded link to my favourite website and write warnings to myself if I messed something up. In this way, I can keep building on my skills and technique and not accidentally create a chemical weapon by putting 3 tbsp, instead of 3 tsp, of fish sauce in my Thai green curry.

How many times have you taken a picture of a restaurant dish and left if lost in your cluttered camera roll? Since Obsidian keeps track of all the links between files, I can have a dataview query to show all the times I have had this meal in a restaurant. That way I can judge if I have hit RQ (restaurant quality).

Each recipe has its own list of ingredients set out like
#ingredients

• Bolognese
• bechemel
• pasta
• mozzarella
• parmesan

This means they can be collected and shown by the Checklist plugin. This setup also works really well for keeping track of the Pantry, if I run out of something I just untick it from the list and it will automatically pop up when I go to buy the ingredients for some recipe...magic