best way to work with templates?

[Natan]

I have been using an implementation of that Paul Wilson`s master pages
for asp.net 1.1. It`s nice, but there is a problem that generally in big
sites, templates must be based on other templates, or i would end with
50 template files...

I have seen another implementation that puts one layer between the
content and the template, so there is one template more. But i think
it`s still not enough.. some sites will still require lots of template
files.

What i`m suppoising is an structure like this (example) :

Global Site Base Page
|
\-> Sports Section Base Page
| \-> Soccer Base Page
| | \-> page 1
| | \-> page 2
| | \-> page 3
| \-> Baseball Section Base Page
| \-> page 1
| \-> page 2
\-> Economy Section Base Page
\-> World Economy
| \-> Asia Section
| | \-> page 1
| | \-> page 2
| \-> Europe Section
| \-> page 1
| \-> page 2
\-> National Economy
\-> page 1
\-> page 2

No default number of steps between the base and the implementation..

I know all about asp.net 2.0 and it`s master pages implementation, but
NOW, with asp.net 1.1, what is the best solution for this? Is there any
good template system or should i start working on my own inplementation?

Thanks in advance.

[Natan]

Cowboy (Gregory A. Beamer) - MVP wrote:

If you have complete UI and code separation, you can use the Dynamic Web
Templates of either Dreamweaver or FrontPage. You will have to use one of
these products when you update the HTML portion to resynch, but it is far
simpler than the programatic methods I have seen under 1.1.

Anything you do now will likely be incompatible with 2.0, so an HTML
template method that requires resynching is better, IMO, than a programatic
setup that has to be refactored. The DWT method can migrate to 2.0 as long as
you continue editing pages in WYSIWYG.

I suspect, one day, FrontPage, or similar, will be folded into VS as the
IDE, but that is just a wild guess.

Hmm... i`ll need to create something better than paul wilson`s master
pages that allow me ot use that kind of structure...

I can`t wait until asp.net 2.0... when it`s out we use it, now i need a
practical solution. Dreamweaver templates are not that good, and I
couldn`t think about frontpage even in my worst nightmares...

By the way, i don`t use vs.net neither...

[Natan]

Just to take note, based on the masterpages idea, i created another
system to work with templates, just like i needed. You can have
templates over templates in any level you want... this means I can have
1 or 10 nested templates and achieve exactly the structure i proposed in
the other post...

thanks for your help anyway.