What we do is to place them in a directory at the same level as docroot
and cgi-bin in a directory called templates.

During development, we have a secondary docroot set up point to that
directory so the designers can see the templates in a browswer.  When we
go to production, the secondary docroot is dropped.

We also duplicate the directory structure under the templates directory
to match as closely as we can the directory structuce of the cgi-bin
directory to make maintenance easier.  This doesn't always work out, but
for the most part it does.

We also place the name of the template in a comment at the top of each
template so the template can be identified from a browser.  Otherwise we
would have to trace back through perl code to know which template is
being used. Again, it makes maintenace much easier.

Hope this helps.

Keith Jackson

On Tue, 2002-07-02 at 15:39, Will wrote:
> Greets Folks,
> 
> Does anyone here place their .tmpl files in a special
> directory assigned just for templates, like maybe: 
> 
> /cgi-bin/templates
> 
> I was thinking of doing this for organizational
> purposes, but I wasn't sure of what problems I might
> run into, or what path I would have to use in the CGI
> programs, etc...
> 
> Any advice appreciated.
> 
> Thanks,
> 
> Will
> 
>  
> 
> __________________________________________________
> Do You Yahoo!?
> Sign up for SBC Yahoo! Dial - First Month Free
> http://sbc.yahoo.com
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Html-template-users mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/html-template-users
> 




-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Html-template-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/html-template-users

Reply via email to