Hi,
I am the owner of Smartphone & Pocket PC magazine (www.pocketpcmag.com). Our current site has tons of great content, but is a mess on many levels -- with forums, blogs, magazine archives, a large product database, a how-to database, and much more. We have just created a new VIP site for subscribers - the Browse How-to db is in Drupal (www.PocketPCmag.com/vip).
We are in process of moving our data from various existing modules from our main site into Drupal. We are now faced with the task of creating a taxonomy (or more than one taxonomy). The taxonomy seems fundamental for our goal of creating various views of our content. So, we want to do it right the first time. We have a number of existing "taxonomies" in our current site, and we want to preserve the good information and translate it in a way that makes sense for the future.
First, I want to verify -- are these rules of thumb true, given to us by a contractor with familiarity with Drupal true?
- Better to have as few taxonomies as possible (ideally just 1)
- Better to keep taxonomy flat rather than in hierarchy
Here are a few examples of existing taxonomies on our current site:
- We have a product database and a software awards structure (Encyclopedia of Software and Accessories http://www.pocketpcmag.com/_enc/encyclopedia.asp and www.pocketpcmag.com/awards.)