Design vs. Code vs. Maintenance. I seek the best-practices wisdom of fellow perl monks on a semi-technical issue. Picture the following scenario:

We have 1 Project manager, 4 HTML designers/artists, and 2 perl programmers. The project manager knows close to nothing about perl, and the designers/artists don't want to learn (I can see their point). The programmers are stuck with the job of maintaining fancy sites written by people that have very little regard for there pain-stricken job of taking all the HTML and making functional code out of it. (The 2 programmers work with assorted types of databases and DBI.)

For now, I've managed to convince the designers to write out some special tags where data should be replace in the HTML, thus making it possible to extend the workflow of things just a bit. Our HTML comes out looking something like this: 
…
<tr>
    <td><font fancy stuff>Name</td>
    <td><font fancy stuff> {name} </font></td>
  </tr>
  <tr>
    <td><font fancy stuff>Address</font></td>
    <td><font font stuff> {address} </font></td>
  </tr>
…

[download]
Then we (the programmers), place this template on the server and do something in the lines of: So far, so good? My question (finally) is,

"Considering that most webhosting companies do not offer solutions such as embperl, Mason, Apache::ASP or others of the sort, what is the most efficient way to work with, build and maintain these websites?"

TIA

In reply to Design vs. Code vs. Maintenance by BBQ

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.