in reply to Building html site maps

It is a static web site updated up to 4 times a day. Rebuilding all the site maps every time is easier, in my opinion than trying to update them.

Don't quite understand the above sentence. What is the difference between "rebuilding al the site maps every time" and "trying to update them."?

That aside, H::T can do the job for you happily whether you want to dynamically build your site on every hit, or you want to build static versions periodically. Just write to a file in the case of the latter. I do that with a website I've built that doesn't get updated that often.

One generic template page with TMPL_LOOP within TMPL_LOOP will work happily for you. After that you can muck around with the physical looks of the page as you please.

I like H::T for its sheer simplicity, and very little provision for logic on the display side. That helps enforce a clear MVC separation. With a little bit of care, you can eliminate all display-side logic.

And, it is very fast.

I have looked at HTML::Template and believe that although it could be used I'm afraid it would be very difficult to maintain.
Any particular reason behind that thinking you want to share?

Replies are listed 'Best First'.
Re^2: Building html site maps
by wfsp (Abbot) on Jan 31, 2005 at 18:45 UTC
    punkish

    Thanks for your quick reply and apologies for my late response (the day job!).

    "What is the difference between "rebuilding al the site maps every time" and "trying to update them."?"

    I should have said trying to update one page.

    It looks like I need to take another look at H::T (but I have a feeling I'll be back with more questions!).

    Again, many thanks
    John