I would suggest not to store the HTML contents in a database. It just makes it inconvenient to view and edit the pages.

I would rather make a distinction between logic data and physical layout. Build a two layer system:
  • A logical data layer that represents the data to be shown;
  • A physical presentation layer that builds the webpage;
    and separate the two layers as much as possible.

    For example, I would classify the member's information as logical data, and store them in database table(s). I would use modules like CGI, HTML::Template, etc to build the look & feel of the webpage - the physical layer.

    
    +-----------------+
    |  HTML TEMPLATE  |  presentation layer
    |                 |
    +-----------------+
             |
             | HTML::Template
      +-------------+
      | PERL SCRIPT |---------> build the final HTML page
      +-------------+  CGI
             | DBI, DBD
             |
    +-----------------+
    | MEMBER's INFO   |  logical data layer
    +-----------------+
    | DATABASE        |
    +-----------------+

    [download]

    In reply to Re: pulling content from db - is it a good idea? by Roger
    in thread pulling content from db - is it a good idea? by kiat

    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.