Jesse Erlbaum wrote:
I was actually thinking that static pages that are re-rendered occasionally would load faster, be easier to link to, and show up better on Google.Hi Tim, Joel --
If you're ok with going the somewhat commercial route I've used Movable
Type in this scenario which is for all intents and purposes a CMS. Its
template engine is not optimized for dynamic generation though. It does
use HTML::Template for its own application templates. With the smart
use of includes and a shared stylesheet it can be pretty seamless.
I hadn't through that Joel would want to statically render the site. (I got the impression from his original message that he didn't want to serve static pages.) If he doesn't mind statically rendering pages, but just needs a dynamic way to do so, then MT would work.
If your content management needs are more sophisticated, you could also use Krang:
http://krang.sourceforge.net/
It's free (as in freedom, AND beer), all Perl, uses HTML::Template, and was written in part by a few people who are regulars on this list. ;-)
TTYL,
-Jesse-
Since I need to use cgi-app to build the dynamic parts of the site, and I've already set up my templates, I thought it would make sense to use cgi-app to render static pages from the same set of templates. For example, each page is built from a main template, which has a menu, header and footer, and a body section, which is another template which is loaded into the main template. Some body templates will be static pages.
I'm using HTML::Template. Perhaps I'll look into MT or Krang, or just write a simple script using lwp-simple to call the cgi-app to render each static page and I'll save it with a different name..
--------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
