|Perl: the Markov chain saw|
Organizational strategies when using HTML::Templateby Hagbone (Monk)
|on Jan 10, 2004 at 21:17 UTC||Need Help??|
Hagbone has asked for the
wisdom of the Perl Monks concerning the following question:
Was hoping for some input, opinions, etc., regarding organizational strategies used by others using HTML::Template.
I'm just getting my feet wet with the Module, and am finding it *very, very* cool.
Since I'm just starting to incorporate it into my site management plan (I have to retrofit it gradually into a relatively complex site), I'm trying to establish some ground rules in the interests in getting off on the right foot - and maybe equally important, not painting myself into a corner due to inital organizational mistakes.
One concept I'm considering is placing all the HTML::Template related template files in an entirely different area then the main site that they will service ... the template files would be housed on the same box, but in a diiferent user (in the ftp log in sense) area. My rationale is that this would allow a HTML designer full ftp access to the templates, but without handing over the "keys" to the real site, maybe avoiding a potential (likely unintentional) hosing of the real site.
As I said, I'm a full blown rookie when it comes to HTML::Template, so maybe my approach is crazy ... hence the question.
FWIW, I have (just) signed on to the HTML::Template mailing list in the hopes of learning more.