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 |
+-----------------+
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|