[haiku-web] Re: CMS

Charlie Clark wrote: 
It is also feature-complete and tried and tested. It can also be slow as a
pig under heavy load but there are ways of dealing with this.

Slow? It was unusable on my computer. That's why I hoped that it can be
optimized. There seemed to be a few articles on the Plone website.
Somehow, the site even slows down Firefox... :(

It shouldn't be slow on a single 

Well, I still have a dual-Celeron-466... :)

The Plone guys have put a lot of effort into making it easy to work with
Plone. But you also have to consider the needs of the site maintainers and
in my experience none of the alternatives come close to Zope for add-ins
and stability. As I've said, you can use Mailboxer to integrate mailing
lists, XUF to hook up to external memberships. As it's sitting on a
full-blown application server you can write what's missing fairly easily.
But we can easily integrate all of that into Plone if we have to, right?

Yes, Plone is just a "skinning" of Zope + CMF. 

Is it bad that Plone does not yet support Zope 3?

What your looking at is the ZMI - which is for admins and programmers. All documents have to have IDs. Whether these are generated by the author or a computer is another matter. Zope's object structure is often quite helpful as

Definitely they should be auto-generated from the title. It doesn't matter much if it could look a little bit better by specifying the exact ID. In most cases the human-chosen and computer-generated ID would be the same, anyway. In general, the ID is not very important as long as it is readable.

Internationalization can be very simple, but it is important to reach
new markets. When you switch the language it must not mix with English
content.

Yes and no - I don't like things offering to switch between languages on a single page but if you only have a subsection of content in a particular language then it needs to be made clear. For the time being English is a sine qua non for Haiku developers who are the most important customers of a site.

No, I don't want to switch within a single page, either. The translations may behave like totally distinct websites that use the same design. That would suffice. Most pages won't need to be translated, anyway.

We can host the mailing lists assuming someone can maintain them. Of course, migrating from ecartis to Mailman might be a real pain...
So the cosmetic solution you suggesting might be the only one.

We can add that later. For now, a better separation should work, so we don't have to answer on forums *and* ML. We could even link to the most important mailing lists from within the forums, so people know how to contact the developers...

What do you mean with "the most work"? :)

Development. 

What did you have in mind, exactly?

... Tic has no Zope experience and tends to go with the latest Python fashions (I hope he'll forgive me for that) but I'm sure he'd be able to help me with some of the low level stuff. Plus we really should have as few systems as possible. Regarding content administration and creation: I am convinced that TALES makes this relatively easy and, more importantly, safe.

Isn't TALES a template language? You are talking about customizing Zope, I guess.

Which low-level stuff do you mean? I'd like to know what has to be done in detail.

RailFrog 0.5 was released today. It's not targeted at production use.
Just a first step. Let's wait a little bit longer and see if their
query-based idea can be made usable enough...otherwise, go with Plone.

mm, Michael prioritises the CMS which would mean getting something up and running fairly soon.

ASAP would be nice, of course. :)
But if, on the long run, Plone/Zope means having a lot of problems (performance, limited into Zope space, maintenance, ...) then it is better to wait.

Bye,
Waldemar
-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List

Other related posts: