Recipe management done by the book

Credit: https://hay-kot.github.io/mealie

Part Five

Don’t miss next issue – subscribe on page 14!

Everyone loves food, and there’s a good chance that somewhere in your house there’s a stack of recipe books or magazines gathering dust. Maybe you inherited them, or perhaps you’ve been acquiring a collection over the years. At Chez Rutland, there’s only one recipe book in regular use: The Curry Guy Bible by Dan Toombs

For everything else, we turn to the internet. Need ideas for an impromptu 100-person impromptu garden party and already fed up with cheese and wine (careful now–Ed)? Hit up a search engine for ideas and recipes. No clue what to do for date night? DuckDuckGo it (as always, other search engines are available).

Doing all this leads to comfortably full stomachs, and more questions. How do you keep track of what you’ve cooked, how well it was received, and, more to the point, how do you find it again once the initial sated satisfaction has subsided?

Sure, you vaguely recall that the salmon wellington you made at Christmas was particularly popular, and you’d like to impress your new girlfriend with your culinary skills, but where on earth are the instructions?

For some people, it seems like a great idea to painstakingly print out recipes directly from the site, laminate them, and store them in a binder. Others prefer to rely on browser bookmarks to store the location of their preferred puttanesca.

Neither of these approaches is good enough. Printed recipes take up space and are only searchable using the