i prefer to just have a 'templates' subdirectory in each application's directory that contains the templates and use CVS to let the designers tweak them. then i'm the only one who can update the production site and i only do so after testing on a staging site. that will prevent the designers from ever really screwing up something production. when you first try to teach your designers how to use CVS, they may kick and scream a bit and don't be alarmed if blood streams out of their eyes and ears, but eventually they'll usually manage to understand enough to do a basic 'cvs commit' and 'cvs update'.

however you do it, i'd also recommend having a function somewhere in a common library that lets you just call it like my $template = template("foo_template.tmpl") and returns the loaded HTML::Template object with all the options you want and with the template file from whatever template directory you've settled on. this will prevent you from accidently forgetting to add 'die_on_bad_params' or 'loop_context_vars' every time (if you want them) and it makes it easier if you change your mind on where your templates live later on.

anders pearson

In reply to Re: Organizational strategies when using HTML::Template by thraxil
in thread Organizational strategies when using HTML::Template by Hagbone

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.