Ingredient Field
Categories
Component ID
Component name
Component type
Maintenance status
Development status
Component security advisory coverage
Component created
Component changed
Component body
The ingredient field module will provide a compound field using the Field API for anyone that would like to create a custom recipe content type. I am aware that there is a Recipe module (http://drupal.org/projects/recipe) with excellent ingredients support. However, the Recipe module does not use the Field API for the majority of the custom fields, including ingredient - the idea of moving the Recipe module in this direction was expressed in an issue for the Recipe module: http://drupal.org/node/1141992#comment-4436862. Although in that case, jvandervort talks of turning everything into a field, except for ingredients; rather to use a node reference paradigm of some sort to associated ingredients to your recipe content type. I feel that a compound field, similar to the Link Field or the Address Field would be a better fit for ingredients of a recipe.
Furthermore, the Recipe module, for better or worse, takes the 'kitchen sink' approach for modules, providing a ton of functionality by itself, rather than working with existing modules that offer similar functionality (and most likely weren't even available when the Recipe module development began). Case in point is the outstanding RecipeML and RDFa support that the Recipe module has - but at the same time it is somewhat rigid. What if you wanted to use an emerging standard like Microdata, that wouldn't be easy with the Recipe module's non-Field API approach. Using the Field API would make it easy to integrate with any module that supported field, like http://drupal.org/project/microdata or http://drupal.org/project/rdfx.
