Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: Robert Treat <xzilla@users.sourceforge.net>,
	"Gavin M. Roy" <gmr@ehpg.net>, pgsql-www@postgresql.org
Subject: Re: Hello and some questions
Date: Tue, 16 Dec 2003 14:07:20 -0800
User-Agent: KMail/1.4.3
References: <3FDE28DA.5070902@ehpg.net>
	<200312151951.06917.xzilla@users.sourceforge.net>
In-Reply-To: <200312151951.06917.xzilla@users.sourceforge.net>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200312161407.20475.josh@agliodbs.com>

Robert,

> 3b) Move any remaining bits of techdocs into a new architecture (current =
is=20
> crufty php manually maintained) I personally think it should be openacs, =
but=20
> even homebrew php done correctly would be a major upgrade.=20

The problem is that OpenACS is an architecture, it's *not* a content manage=
r.=20=20=20
Honestly, my first thought when Justin "handed over" techdocs to me (not th=
at=20
I;ve done anything with it) was to contact the OpenACS folks and see if the=
re=20
was a full-service CMS built on OpenACS.  There's not.

Also, Bricolage's setup of generating static files from dynamic content sho=
uld=20
work a lot better with our site setup.  It would mean that the majority of=
=20
the Techdocs material could be mirrored just like the rest of www.

If I end up running Techdocs, or if Elein does (I've suggested it becuase o=
f=20
the amount of energy she's put into General Bits) we're going to want a rea=
l=20
CMS so that we don't spend time debugging HMTL/PHP that could be better spe=
nt=20
managing authors and writing.

--=20
-Josh Berkus
 Aglio Database Solutions
 San Francisco