I'm convinced that frames are a bad idea but loosing them is a case of two steps forward and one step back. Each page now contains a top banner, navigation side bars, common footer etc. with the obvious difficulties that arise if you need to make any changes to these elements.
Frames *are* a bad idea. "Deprecated" as we like to say around here. Why don't you consider HTML::Template's INCLUDEs. I use them for the header and nav bars, and then for address footers. The nice thing is that they can contain <tmpl_var >'s that get values from your Perl first.
Have you looked at CGI::Application? I heard a lot about it around the Monastery, and finally couldn't stand the guilt. The learning curve was about a week, but I'm a convert now. I recommend you look hard and long at it.
One question is where to keep the content (articles) - in the db or as HTML files without the common elements? And jpegs/gifs? I'm leaning towards files.
I keep all my plaintext content in the database and serve it up in <tmpl_var >'s. All my images and uploaded PDFs, etc., go in directories in the public area. I have discovered that the general wisdom is not to store images in the DB.
I envisage a setup where the CGI script would add all the necessary elements to each cut down page before serving it up.
Are talking about some type of content manager? That's what we have done. If you are storing the content in the DB I don't think the loathsome FrontPage will help (another way to update static content is with Macromedia's Contribute).
Good luck.
In reply to Re: OT: Migrating towards a Perl/MySQL/CGI website
by bradcathey
in thread OT: Migrating towards a Perl/MySQL/CGI website
by wfsp
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |