Components — why use them and how

A component is simply one of your own recipes, embedded inside another recipe as a single "ingredient". A typical example: you have "Garlic Sauce" as a separate recipe, and you use 60 g of that sauce inside "Shawarma". Instead of retyping the sauce's ingredients into every recipe that uses it, you cost the sauce once and then just reference it by weight. Why this matters: — Cost cascades automatically: if the price of garlic in the sauce changes, both the sauce and every recipe using it recalculate — no manual edits needed anywhere. — No need to duplicate a long ingredient list (dough, broth, marinade) in every recipe that uses it. — On the recipe page, the component can be expanded — a visitor sees exactly what it's made of without leaving the page. How to add one: in the builder, click "+ Recipe component" (visible when Pro mode is on). Start typing a name — the site searches only YOUR OWN recipes (you can't turn someone else's recipe into a component — it's your personal reusable sub-recipe). If no matching recipe exists yet, a "+ Add ingredient" option appears right there, letting you build the component's ingredient list on the spot without leaving the page; on save it becomes a separate draft in "My Recipes" (the "Components" tab). Components inside components (two levels of nesting) aren't supported yet — only one level.