Converting to Drupal

I'm beginning a project to convert a large, static HTML site (1000+ pages) to Drupal. My question is how should I set up the structure in the most efficient manner? I'm new to Drupal and still trying to absorb all of the new concepts and options. There often seems to be multiple ways of performing tasks in Drupal so I'm looking to be pointed in the right direction so I go do more research.

Existing site:
The existing site is set up the old-fashioned way: about 20 categories that are menu items from the home page. Each category is a separate directory with an index.html file describing the contents of that section and links to the 10-50 pages of content, also contained in that directory. For the most part we never go more than two levels deep but sometimes an article will have links to another page. One of the big problems we have now is some pages are relevant to multiple categories. The site was developed in Dreamweaver and each category uses a slightly different template to aid in navigation. Only a few editors have access to change this mostly static content.

Goals for new site:
I'm excited about using taxonomy so that I can cross-reference articles from one category to another. But do I use taxonomy to build the hierarchy or do I create new content types for each category?

I've been looking through the node relationship modules, but I don't find exactly what I'm looking for, which probably means I skipped over something or just didn't get the full feature set of something. So I'm going to ask the brilliant world out there for some guidance.

What I have is two kinds of nodes, Entities (people, companies, groups) and Projects (theater production, concert, CD, Video).
Now any Entity is likely to be linked to multiple Projects, and Projects are linked to Multiple Entities.
So I'm looking for a many to many sibling relationship. (though Parent to multiple child is OK too, just fast lookup one way, slow lookup the other I'm guessing)

But here's the extra wrinkle: the relationship type of each Entity-Project can be different, so I imagined using a taxonomy, which has many features that I want to include in the relationship (such as synonym, and a hierarchy of relationship types)

So I imagine that what I'm looking for is Node - Term - Node relationship, though if someone even has a better moniker for this that might just help me search my way to something close to what I'm looking for.

Hello All!

I am using the Book module to drupal-ize the employee handbook for my company. Maybe this is a non-issue here, but I am having trouble with sections and chapters. The handbook we use has a lot of chapters with sections within them. The chapters have no text, and are just used to group the sections together. I would like to preserve the grouping that the chapters provide, without having to create empty book pages to be the 'parent' page of all the sections. Does that make sense? I basically want sections or groups for my book pages, without the introductory page.

I want to change the design of every self created page via URL-aliase to use an individualle page-.tpl.php.
The following snippet of the template.php does not really work.
drupal_set_message(''. print_r($_GET['q']) .''); --> path of the site , without alias e.g. note/...
drupal_set_message(''. print_r($alias) .''); --> 'nothing'

Das Snippet:

Hello,

I was wondering if anyone could help me out with the following problem: I currently have a drupal site running on test.example.com/test.
I would like to move the site to subdomain.example.com (where subdomain is NOT equal to test).

What steps should I follow?

Thank You

I am setting up vBulletin for my forums and using drupal for my custom pages that VB will not support. I am wanting to have a single login for both and have found a resource that does this Drupal vB http://drupal.org/project/drupalvb.