You know, I'm leaning towards not fixing what's not broken. It might not be hip or sexy, but for this application SSI has much to recommend it.
- Zero learning curve
- already installed, ready to go, proven, stable
- No more resource hungry than a templating system
- While it does use resources each page serve, this is a low-traffic site on a private server that won't even notice the minor load
- Although it is static, the content and the nav bar do change from time to time. An off-line generator would mean having to re-generate the entire website each time any page was updated, adding steps of complexity in a a situation where pages may be edited by multiple authors who have limited web skills to being with. Or I have to develop an interface for that function too. Whereas with SSI, edit the file directly once, and that's it, done.
- same for the nav bar, which changes occasionally;
Time flies like an arrow. Fruit flies like a banana.
-
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.
|