Are there any live examples of this mod that I can see?

I believe these sites use this module:
http://www.thenewhomemaker.com/recipe
http://davesowerby.org/recipe

I'm sure there are more out there - if you have such a site, feel free to link to it in a followup comment!

I'm the person behind TheNewHomemaker.com and we do indeed use the recipe module. However, we're still using 4.7.x. I'm waiting for 5.x to become very boring and obsolete (read: mostly bugfree and caught up on modules) before upgrading. Plus also, it's a big hassle I'm not willing to undergo right this minute. ;)

Here's one: it's a new site I'm developing to replace a phpNuke installation on the .com extension:

http://organizedhome.org/recipe

Haven't added too many recipes yet, but so far, it's functioning well.

Sure, you can see on:

http://tatxe.org/recipe

http://tatxe.org/comunidad/recetas

We are using it at http://www.favoritecocktails.com/fav/

I'm using it on my D5 site: http://missions.ritchietribe.net/recipe. Looking forward to a D6 upgrade.

Hey flickerfly, just visited your site and though, IMO, that your recipe setup looks great! I have a question about it if you don't mind. I'm trying to setup a recipe book on my site, D6 and I just installed the recipe module. But, it seems that all recipes end up on one page /recipe. How did you get yours to catagorize the submissions into different nodes? Or, do you do that manually?

Thanks,
Roger

Sorry about that last post flickerfly, I didn't read enough to see what you were doing. I was under the impression you had your recipes grouped in different categories when I see that you post the new listings on one page, /node/recipe instead. This is what I have and I was trying to have them posted in different nodes to have them categorized. Still like your site though...Great Mission!

Thanks :-) Glad to see you figured out what you could. The Recipe section is certainly the largest draw to our website.

I'm not sure what you want, but could you possibly use Taxonomy for what you want? Taxonomy would allow a categorization of your recipes and then you'd have views of your recipe book that would be based on taxonomy as a result.

Man, your so intuitive! That's just what I'm trying to figure out.

But, I'm having a hard time understanding how taxonomy works. I mean I understand categorizing but visualizing the layout, or as you say, "have views of your recipe book...based on taxonomy" is boggling my mind! You might say, I can't build something that I don't know what it's supposed to look like! :)

I'll keep playing around with it until it finally clicks in my head!

Anyway, thanks for your input and keep up the good work on your site! And, if you have any tips on taxonomy, I'd be more than willing to take a look and listen.

Thanks

:-) I've not had a project that could really take advantage of taxonomy so haven't built up an extensive understanding. I'll try to paint a basic picture for you though. Taxonomy is the reason the newspaper industry is getting behind drupal as heavily as it is. It is like categories but much stronger. Basically, you can setup a list of vocabularies that then can have sub-vocabularies. These describe the "node" or in this case the recipe.

For recipes, you might have an ethnicity taxonomy, a main ingredient taxonomy and and a type taxonomy. The type might be 'main dish', 'dessert' or 'appetizer'. When you create the recipe, you'd set the taxonomy that is most appropriate for each. This then becomes a way to segment out certain types of items. In order for these vocabularies to be applied to the recipes, you'd have to edit the recipe content type.

Once each recipe is tagged with the appropriate items in each of the vocabularies, you have the option of using links like this: http://drupal.org/taxonomy/term/14. The problem becomes, if you use that same vocabulary in non-recipe content types you'll get more than just recipes. Perhaps you also have a listing of shoes that you use the ethnicity vocabulary on. You wouldn't want middle-eastern footware showing up in your recipe. This is where views comes in. It is basically a saved query that is fed into a saved format for display. Therefore, you could create a view attached to the URL http://yoursite.com/recipes/middle-eastern that will pull all the recipes with middle eastern ethnicity for you and displays it in the style you requested.

Clear as mud?

answered.. closing the issue