I would certainly take a close look at using Template Toolkit as your template engine. It enables (encourages) the use of modular templates. So, you can have a "sidebar" template, a "navbar" template, and a "body" template; the first two would be "included" on every page while the third would vary based on what content you were serving.

Capitalizing on the template engine allows you to make changes to the presentation (even drastic changes) without changing any underlying data. Storing HTML as your "content" has a significant downside. If you ever want to change the content, which the client is probably making available as something other than HTML, you have to regenerate the content that goes to the site. With a templating solution, the content is stored in a raw form and just plugged into the template appropriately.

I would also agree with the first poster that CGI::Application is a good stepping-off point for developing such a site. I would add that I have found Catalyst useful in this regard as well. The two accomplish the same task, but take very different approaches. There are other web frameworks out there, as well.


Sean

In reply to Re: OT: Migrating towards a Perl/MySQL/CGI website by srdst13
in thread OT: Migrating towards a Perl/MySQL/CGI website by wfsp

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.