comment on

Dear neilwatson

At $DayJob we evaluated Metadot for a major rewrite of our user-interaction site. It exceeded all of our requirements _except_ being easy to translate/have multilingual sites. While having a content management interface in english is not important to us, the elements you place in the pages are (or were, at the time of the evaluation) not available in spanish.

IMHO, it's not trivial to add i18n as it is. Other than that, performance can be on par with other alternatives based on dynamic pages, depending of course on how many gizmos you put in your pages.

We ended up basing our site in http://www.template-toolkit.org and writing a few Template::Plugin modules (which we will place in the public domain once the rewrite is complete and the code is tested in production).

<plug class="PerlPlug">Please stay away from PHP based CMSes!!! - They're evil and chances are that they will become incompatible with newer releases of PHP.</plug>

Best regards

-lem, but some call me fokat

In reply to Re: Experiences with Metadot? by fokat
in thread Experiences with Metadot? by neilwatson

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: the Markov chain saw
	PerlMonks