..."create an interface for a website, to allow content management"... "Being a novice to perl"...
Eek! :-)
I've built several interfaces along the lines you have described and here is the best advice I can give you on the subject. The difficult part is error trapping, building a CMS is pretty easy* if you don't care about input from the lusers that use the system.
Get to know perl well before attempting this, also learn the Db system you will be using inside-out (you will be using a relational Db, not flatfiles?).
*Getting back to the point, you will be amazed, nay, dismayed by the utter rubbish (and potentially dangerous) content that people will put in using a web based CMS. I can personally guarantee that. So, learn all you can about what is suitable and safe to allow, parse that first, then, and only then allow writing to the Db.
-
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.
|
