|
I've been using Calibre for recipes for years. It may not have been designed as a recipe catalog program, but it sure seems that way. A recipe has certain qualities that makes Calibre an ideal system for storing it.
Recipes are usually self-contained documents; i.e. everything you need to know is stored in one file. Calibre works well with self-contained documents, not so well with documents spanning more than one file. (HTML is a special case, which Calibre handles great)
Recipes that you store on the computer will usually be in standard formats, such as pdf, docx, or html. Calibre can read most of these with its internal viewer, but it can send the others to the operating system to handle.
A recipe will often be ambiguously categorized if you can only put it in one category. If you're looking for your favorite chicken pasta recipe, do you look under Main Dish, Pasta, or Chicken? Calibre lets you tag it with all three and look it up by any of them.
Calibre lets you define custom columns in its database. You can be as obsessive/compulsive as you want. If you want to track every ingredient in every recipe, you can set up an "ingredients" field. If you want to track calories, go right ahead.
Finally, Calibre lets you send documents to portable devices. Want to put your recipes on your tablet so you can take them into the kitchen with you? Easy enough.
Aside from ebooks, I can't think of another type of file more suited to Calibre's interface.
|