Chris Withers <chris <at>> writes:

> I hate to say it in this context, but not if it's Plone based.

Somehow I don't think you dislike saying that :-)

> Once 
> bitten, twice shy and all that. Plone was the big promise for the 
> current and it simply hasn't delivered...

Considering it's a heavily customised, unmaintained version of pre-Plone-2 (from
what I'm told) it's not suprising that there have been problems. I'm not
actually quite sure which problem you're referring to, so the answer is
necessarily generic. has fairly minimal technical requirements - a skin, perhaps a content
type or two, and a bit of information architecture. Neither the problem nor the
challenge should be in the technology. Plone (i.e. a current, maintained
version, not FrankenPlone) would have no problem handling that, neither would
CPS or probably Tiks or Drupal or whatever else you wanted. This shouldn't be
about technology, it should be about designing an information architecture,
considering requirements carefully, designing a user friendly interface and skin
... all the things we do for our customers every time.

I'll note that runs on Plone 2.1, handles a high load very well, and
has solved some of the product/software listing and documentation handling
problems that will have to solve as well. I'm happy to help share the
experiences from with others, and I'm sure wiggy, limi and the others
are too.


Zope-web maillist  -

Reply via email to