Clear questions and runnable code get the best and fastest answer |
|
PerlMonks |
Re: perl-based CMSby oakbox (Chaplain) |
on Jan 18, 2004 at 23:37 UTC ( [id://322236]=note: print w/replies, xml ) | Need Help?? |
You might want to take a peak at Plone http://www.plone.org it's a pretty web interface pasted over the (rather steep learning curve) Zope architecture. They were voted as one of the top Open Source projects of the year. I took a look at their home page and signed up for a demo account: Slick. Everything is a big engine to install and you have to have a hefty box to run it on. Javajunkies.org didn't start running smoothly until I had upgraded to a 2Ghz machine with 1G of ram. You can also export the contents of your Kwiki http://kwiki.org into a template based on your site. I'm using a Kwiki back end with write access to my developers and exporting the contents into the main site's documentation with a cron job (you might want to have a manual 'commit' process). The formatting rules for Kwiki are super easy and look good and exporting them is as easy as (code modified for publishing here, untested in this form): That "$Admin->Template_Canner" section at the end is my site's templating engine. This script is basically: Read each page of document repository > strip out headers and footers > dump content into site template with formatting > put in appropriate directory. The Kwiki site is heavily monitored so you can get hints and tips quickly. The Kwiki solution is good for flat web sites, but probably not a suitable solution for sites with a lot of directory depth. But, creating content repositories for each individual site is a breeze because it's so damn easy to install.
In Section
Meditations
|
|