------art_10484_13218629.1127550991526
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Depending on the structure of the site, maybe you could just start with a
simple content editor that stores articles or newsitems in the database, and
a publish mechanism to wrap the content in an html template and publish it
as a static page to the website. If the pages on the site that need updating
are the same ones day in and day out I don't think it would be that much
work.

For instance you have an html template made up of a header and footer. To
create the final page you you start with the header, query the database to
get any content items for that page, then add the footer. The editor writes
out the final html page right there, and it's ready to be pushed to the
server when it's time to publish.

I would definitely use something else besides apache for serving the static
pages. Squid, thttpd, lighttpd, zeus (which also supports fastcgi), and
others will probably cut down on server resources being used and boost
performance.

Chris

------art_10484_13218629.1127550991526--