Hi guys!
I have really enjoyed your podcasts about Drupal! I am a new Drupal user and I am doing pretty well figuring things out so far, but I am really stumped on how to make the best use taxonomy for the church's website. I'm getting to the point where I will be adding a lot more content to the site I want to set up the taxonomy correctly from the beginning if I can!
Is there a "right" and "wrong" way to set up taxonomy? Right now we have a lot of static content to put up (which will likely be "page" nodes) but we are working towards having blogs, events, etc. as well.
Should I set up a vocab just for "pages"? Should one vocab be "category" and include terms like ministry, worship, about us, etc.?
I think I understand how taxonomy works but the Drupal handbook and the info I could find online don't explain very well how to do it.
Any advice would be appreciated!
Thanks!
-Felicia
Taxonomies
This might be a little technical so please let me know if there is something I didn't explain well.
Let's start with what a taxonomy is. I'd suggest reading the wikipedia article at http://en.wikipedia.org/wiki/T.... The gist is that ti's an organizational system. It could be kinds of dogs, it could be ministries, or anything you like.
So, before you apply it to your website create a system of organization for how you would like to organize some piece of content. An example might be you wanted to have ministry type on your ministry pages with types like youth, young adult, and over the hill folks. Then, when you create pages for the ministries you could choose the appropriate category.
You can, also, have more than one type of taxonomy on a site. So, in this case you might have ministry type as one vocab with the different ministry types as terms. But, you want to have a pastors blog with blog categories. So, create another vocab and add the categories to blog about there.
In each of these cases only assign the vocab to the node types using them.
There is one way to go terrible wrong with taxonomies. Don't overdue them, expect them to define your site architecture, or try and come up with a unique one for each page. There is potential for them to get out of hand.
Think of them as a way to implement some form of structured organization you want on something specific on a site.
That's my 2 cents.
Matt Farina
Geeks and God Co-Host
www.innovatingtomorrow.net
www.mattfarina.com