So Krang will use the same set of templates as my cgi-app?
Well, this is what we did...
Sorry if someof this doesn't make sense as I will be talking some krang specific stuff. The navigation on the home page is built dynamically at publish time, but served to the users as a static page. We wanted the dynamic section to have the same nav, etc from the home page no matter what the people using the cms decided to do with the content.
Krang has a category template that is used to place the individual stories into (providing, common header, footer, nav). So we added something to the publish of the home page so that when it fills in the template to create the home page it also splits the result into two templates (header.tmpl and footer.tmpl) which are then placed in the site tree.
The templates of our dynamic site all <tmpl_include header.tmpl> and <tmpl_include footer.tmpl> so that they look exactly the same as the home page (with regard to nav, etc). Since the krang publish root is different than the template root for our dynamic section, we have to tell our C::A based apps to have multiple values in TMPL_PATH. (Which is why I provided that patch just a few weeks ago).
Does that make sense? It's really nice since the publish generates our common templates that the dynamic site uses. And we never have to worry about keeping them in sync.
HTH
Michael wrote:
What we did recently for just such a project was install the krang cms (written by sam tregar (HTML::Template) and jesse erlbaum (CGI::Application) just to name a few) to let the content people manage the static pages. It generates the static pages from templates and element classes that write.
Then the dynamic portion was written using C::A. To merge the two (ie, login/logout buttons on static pages, etc) we used some SSI that we wrote as mod_perl handlers. I think overall it came together rather nicely.
Joel Gwynn wrote:
I'm working on a web site that will be a combination of static pages and application pages, and I'd like to use cgiapp to build the static pages. I've been browsing the archives, and can't find any real answers.
Should I be considering a separate utility or CMS based on HTML::Template?
--------------------------------------------------------------------- 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]
-- Michael Peters Developer Plus Three, LP
--------------------------------------------------------------------- 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]
