Thousand Leaves 2.0

I would build one in FileMaker.

A field each for ingredient name, ingredient unit-of-measure, and ingredient-quantity. A field for conversion unit-of-measure (i.e., “please convert metric units typed in to US units”) and a calculated display-ingredient-quantity field that contains the conversion formula. All that in the Ingredients table. A second table would contain Recipe Name, Description, Cuisine, Source, Date, Category, the Instructions of course, and also a multiplier field (i.e., “please scale up the quantities on this recipe that serves 4 to serve 12 people”) which would also be referenced by the formula of the display-ingredient-quantity field back over in the Ingredients table. Bingo, you’ve got a recipes database. Twenty minutes, plus another 20-30 to make it look pretty and look good when you print it. If you want a third table to keep track of what items you have in inventory and when purchased, and a script to generate a shopping list, another 20 minutes.

Add in a script that will let you paste in a recipe copied from email, word processor, or web page, and parse it out into field data, maybe another 30 minutes.

Built-in easy-to-use FileMaker searching & sorting. (i.e., “Bring me all the French recipes for capon that don’t use fennel and don’t use ingredients I don’t have on hand and show them to me in a list view sorted by entry date”).