Lately I've been nosing around looking for a pure Perl CMS/BLOG. For my purposes, I'm really just interested in more of a framework for journalesque entries rather than a full blown news and commentary site.

So what is everyone's favorite (free) Perl solution, whether it be an enterprise-level CMS, mid-range BLOG, simple journal maintenance suite, or template-level publishing tool? I'm not too concerned about mod_perl usage vs CGI, but I'd like to avoid any JavaScript and overreliance on cookies.

Up with the big boys, there is of course Slashcode, Movable Type, and Bricolage. Of these, Moveable Type seems nice, but apparently is a bit happy with JavaScript and cookies. Slash, of course, is well known, but for me is a bit of overkill. I'm not too familiar with Bricolage other than knowing it's built around Mason.

On a more modest level, there's YaWPS (Yet another Web Publishing System) which seems okay though I haven't played with it to see how flexible its configuration is.

On a really basic level, I find Apache::BLOG, which basically prints one journal entry per page. Way too limited.

And of course there is rolling my own using HTML::Template or some equivalent, which is probably what I'll ultimately do since I never seem to be quite satisfied with canned solutions.

Some of the big boys, BTW, seem to be covered in the new Essential Blogging from O'Reilly; I'm not sure on what level it approaches the topic.

Thoughts, additions, reviews?

Thanks for your time,
Matt

---

---

• 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.