Templates Vs. Pages

Lance Arthur asks:

I'm confused about the new "Pages" feature in MT. I've been trying to sort out what they do and how they work within templates, but when I publish a page it isn't going anywhere, and I can't figure out how to manipulate pages so I can direct them to be used in different index templates.

The long and the short of it is that I am building a site in MT and I need to be able to provide the WYSIWYG interface for content, but it's not a Blog per se because I need more manipulation of the content than I get through a blog. If a page were saved like a Template Module so I could insert it into a template but also use the WYSIWYG input, that's the divine answer.

1. I think going the Page Archive Template route works best for this installation, but I'll likely need a few different Page Templates in order to account for the different types of Pages I need. They vary by things like navigation and some Includes. And I cannot figure out how to tell a page which Page Archive Template it needs to use to write to the server. Is that not an option? Can I even have multiple Page Archive Templates and, if so, how do I get MT to differentiate which template to use when saving Pages?

2. Is there a way to insert a variable into an MTInclude? Specifically, I have a series of template modules with employee info for every Partner in the company. Each partner has an industry specialization and I need to include Partner modules on their related Industry page. I am trying to do the following:

   <MTIfNonEmpty tag="pagedatapartner1"> <$MTInclude module="partner<MTpagedatapartner1>"$> </MTIfNonEmpty>

Partner 1 is a custom field on the Industry Page template allowing the author to include the Partner name in a field that MT uses to find the related module. MT interprets everything inside the Include literally, so it's not translating <MTPageDataPartner_1> into the data that's been entered into that field on the Page screen. Can it do that?