Re: CMSystem written in PHP (clarification)
| From: | Hans Lellelid | Date: | Mon, 02 Dec 2002 15:17:20 +0000 |
| Subject: | Re: CMSystem written in PHP (clarification) | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-11295@lists.php.net to get a copy of this message | ||
Hi Neil,
> First off (correct me if I'm wrong), some people seems to have
> misunderstood me; calling Raven a `CMS' is actually a misnomer, but
> `CMS' is the closest term I could think of. Let me explain:
Perhaps CMF (Content Management Framework) would then be a more accurate
description of your product.
> Sadly, though, Raven does not use any existing PEAR classes. My haste
> to come up with a CMSystem of my own discouraged me from diving through
> my local copy of PEAR classes, since I already knew what I want, and had
> an idea of how to go about it.
I guess I would read that as a warning sign. Not saying that you're not
an excellent coder, I would still assume that your codebase would have
stood to benefit from tools out there: db abstraction, templating
systems, caching frameworks, etc.
> But I guess this would be better left off to actual inspection of my
> code, if anybody is willing and has time to look at it.
I would *love* to look at your code. I'm not a PEAR code approver, but
I've been working on a PHP CMF called PHlexDB -- and I know I could
stand to learn a lot from other tools out there. Obviously you are also
welcome to have a look at my stuff -- that's the point of OS software,
afterall :-): http://phlexdb.org/
On the side -- what sort of CMS features does Raven support? In
particular, I'm wondering about things like localization, versioning,
and workflow. These are all problems that I've been tackling myself and
would love to see some PHP solutions that handle these well
(particularly the latter 2, as there are lots of good 18n solutions out
there).
Cheers,
Hans