Mingling Monks,

As mentined in other recent threads, I have an old static html website to update. The many helpful replies to those threads has lead me to a basic strategy:

A two-stage update. The reasoning is business related, so not much use to diuscuss the obvious technical reasons to do it all in one step.

Step 1: Layout re-design and update navigation - that is, remove frames and go to frameless design; replace old navigation system with a CSS menu system, apply external CSS style formatting, update graphics.

Step 2: Move to a Perl-based Content Management System

So, my question: What can be done in phase 1 to prepare for phase 2? Now, the reason this is somehwat of a Perl question is that whatever can be done to prepare for phase 2 will depend on what Perl CMS is used, so I guess part of this question is for a recommendation of a top Perl-based CMS.

The reason for the CMS is that there is an increasing desire for employees who supply page content to manage that content themselves. They should be able to:

• make changes to existing textual content on an html page
• change an image on an existing html page
• create a new html page within an existing section, but not create a whole new section
• delete a page
• create a new PDF page (that is, upload a PDF file with a link to it from the navigation bar)
• update an existing PDF with a new version of the file

I imagine taking existing html pages to something like

[server side include for all pre-content html]
[comment tag]
CONTENT
[comment tag]
[servert side include for all post-content html]
[download]

That way, whatever the mark-up requirements of the CMS, I could write a little Perl script that would wander through the hierarchy finding these pre-contenet and post-content tags and automatically insert whatever tags the CMS system needs.

So, in summary, what's a good Perl-based CMS, and what can I do during a re-design/update to make moving to that system later on as easy as possible?

Thanks.