public inbox for [email protected]
help / color / mirror / Atom feedFrom: Gavin M. Roy <[email protected]>
To: [email protected]
Subject: Re: Hello and some questions
Date: Tue, 16 Dec 2003 14:38:47 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
Not that I'm trying to stir things up, but I do have a fairly solid php
cms infrastructure that can be used, and would love to have you guys
evaluate for use... it would require a php/pgsql setup for www hosts,
and we would use replication to drive the content down. Yes a major
change in how things are structured, but change can be good.
Gavin
Josh Berkus wrote:
>Robert,
>
>
>
>>3b) Move any remaining bits of techdocs into a new architecture (current is
>>crufty php manually maintained) I personally think it should be openacs, but
>>even homebrew php done correctly would be a major upgrade.
>>
>>
>
>The problem is that OpenACS is an architecture, it's *not* a content manager.
>Honestly, my first thought when Justin "handed over" techdocs to me (not that
>I;ve done anything with it) was to contact the OpenACS folks and see if there
>was a full-service CMS built on OpenACS. There's not.
>
>Also, Bricolage's setup of generating static files from dynamic content should
>work a lot better with our site setup. It would mean that the majority of
>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 of
>the amount of energy she's put into General Bits) we're going to want a real
>CMS so that we don't spend time debugging HMTL/PHP that could be better spent
>managing authors and writing.
>
>
>
view thread (26+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: Hello and some questions
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox