Comment by squirtlebonflow

It's much more complicated than that and that's it's biggest downside. I've been trying to learn how to use it but it's quite confusing figuring out their terminology and UI.

One thing that I did with it was make a Recipe type that has any number of Ingredient types in it, takes any number or arbitrary Dietary Restriction tags (e.g. Gluten, Dairy, Vegan), and takes parameters like cooking time and number of servings etc. So not only is a Recipe a note that explains how to make it, but it has a template with the boilerplate information pre-filled so when writing down a new Recipe, it's faster, and it has all that metadata, which allows you to construct Sets from the Recipes.

For example, I can have a document called Quick Vegan Crowd-Pleasers that is a Set of all vegan Recipes with cooking time under 30 minutes and 8+ servings. If I really wanted to go psycho mode with it, I could track every ingredient currently in my kitchen and filter recipes by what I can make with what I have on hand.

You can really do a lot with it. It's just time intensive to set up and also to keep up with entering data.