Lot's of good points others have made. Just one note, lots of people will
say by using templates, you can have designers work on the HTML and
you as a dev can concentrate on code. While I think that's great, I think the
even greater power is the ability to easily re-skin a site. Combine multiple
templates with some well structured CSS reliant html and it becomes very
trivial to re-skin a site.
Right now, I have such a site up and running. Basically
the back-end is XML, then a combination of a very simplistic mod_perl handler
sitting on top of a CGI::Application app that uses HTML::Embperl
to provide different skins based upon configurations. The mod_perl handler
inspects the url, reads a config file based on url parameters and then jams
the appropriate params into the HTTP stream (embperl templates, XSLT stylesheets, CSS stylesheets, other data ...). Sounds complicated but the neat thing is the CGI::Application is free of lots of conditional code.
The only real conditionals are built-in default templates and stylesheets.
-derby
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
