comment on

Dear monks
I am trying to set up a simple CMS for my university department. We need a few simple things that no exisiting CMS supports, so I am drawn to Perl, because I know that I can do what I want. At the moment I use HTML:Mason, but I want to give my colleagues direct write access, and Mason, while I love it dearly, is way too low-level for them.

I've two strong core candidates Metadot and WebGui, and one outlier, Slashcode. WebGui looks neat, but the publcily available documentation is not good. Metadot has better documentation, but looks a little more complex. Slashcode has some obvious merits, but would be hard to customise for our needs.

Anyone got any experience with these two packages? Both claim to be widely used. Any unexpected gotcha's? Any other recommendations based on your personal experience of a Perl based CMS?

Ta,

-- Anthony Staines

In reply to Suggestions on Perl CMS by astaines

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.


Perl Monk, Perl Meditation
	PerlMonks