|Perl: the Markov chain saw|
A modern Perl repalcement for Apache Server Side Includes?by punch_card_don (Curate)
|on Feb 10, 2013 at 16:25 UTC||Need Help??|
punch_card_don has asked for the wisdom of the Perl Monks concerning the following question:
Yet another website redesign project. This time you're given an old, static website. It has zero dynamic content. This is a brochure website whose only purpose is information delivery. That said, there are a lot of pages, a lot of sections and sub-sections, and four levels of navigation.
Every page has the same header, navigation bar and footer. So, the old website was done in shtml with server side includes on a linux/Apache box. The SSI inserts common header, nav bar and footer code. Plus, calls to external stylesheets. This way, each page file is really just the content with ssi calls, stylesheet calls, and minimal markup. Practically a templating system.
So now you're doing a complete re-design. Graphics, check. Probably going to a jQuery nav bar. And reducing content mark-up to bare bones semantics with as full CSS styling as possible.
But what do you recommend in terms of architecture?
This does not warrant the full MySQL/Template Toolkit treatment. But you'd think that in the last X years something better than SSI would have come along in the world of Perl.
A framework like Dancer? Is this not still overkill? Mojolicious? Even more so.
Or go the full CMS route - Galileo? (Even though cms is not a design spec, and this would be delivering way beyond the project scope.)
I guess the question is - is there a Perl-ish equivalent to the biblical simplicity of good old SSI these days? Something that would complete the separation of content and template, without going overboard.
Time flies like an arrow. Fruit flies like a banana.