*grins* Somehow I get the feeling you're referring to this node. . . ;)

Personally, I'm very fond of HTML::Template for the sites I do. Most of my sites are written to be used by multiple clients, and by using templates, I can completely change the look and feel of the site without changing any code. I still have what I consider to be an annoying tendency of mixing a lot of CGI.pm methods with HTML::Template code though - but I don't typically work with a designer (which, I think, would help me almost completely transition myself over to templates). There's a lot you can do with HTML::Template, some of which I really need to learn how to do. I'm so used to having CGI.pm generate HTML for me at times that I can't quite think outside the box I've built for myself.

I use CGI.pm to generate HTML for anything quick and dirty that I need to get done. There's no real HTML in my scripts, but effectively non-programmers are prevented from changing the appearance of what those scripts present.

There's nothing wrong with the approach you've selected (TIMTOWTDI!). Only issues I see would be if (like in the situation I describe above) some non-programmer type needed to modify the appearance of your site. Depending on how your own functions are written though, it may not be much of a worry for you.

Hope I didn't ramble too far off topic for you ;)

Cheers!
MrCromeDome