Recommended handling of sites with subdirs?

[Stephan Petersen <nospam@thanx>]

Hi everybody,

I've been using wml for a couple of years now, mostly for the site at
www.aspetersen.de

So far the site was small enough to have all html files in the root
dir of the site. But with further additions coming up, I want to
structure the new material into subdirectories.

The question is, what's the best way to support such a directory
structure, meaning what's the best way to get all the paths and links
right?

Using subdirectories affects the template file, the navbar code, and
some general "macros". Sometimes you need to know the name of the
subdirectory to prepend it to links, sometimes you need to know how
many levels you are away from your document root dir to prepend the
correct number of "../"s.

I'll still have my one standard template, navbar, and misc. include
files loaded into each wml file. I'm using Gnu make and Makefiles to
process all wml files, but I would like to stick with one Makefile,
not resorting to recursive make calls. I also automatically create
text-only versions of the pages, which are stored in a textonly/
subdirectory. And last but not least, I like to stick with relative
links and path info, if possible, because this way the ready-made site
can be checked easier locally.

What's the recommended way to do it, or your favorite way? What's the
best way to get all the proper path and subdir information into the
various #include-d wml files?

Thanks in advance for any pointers,

Stephan


--
Stephan Petersen                           sp@gtt.lth.rwth-aachen.de

>-=-=-=- Visit GTT's Technical Thermochemistry Web Page at =-=-=-=-<
>-=-=-=-      http://gttserv.lth.rwth-aachen.de/gtt/       =-=-=-=-<
______________________________________________________________________
Website META Language (WML)                www.engelschall.com/sw/wml/
Official Support Mailing List                   sw-wml@engelschall.com
Automated List Manager                       majordomo@engelschall.com