Paul Everitt wrote: > I have some work I've been doing on splitting CMS into content > production and content delivery. I'm working on the latter, with > something for mod_python to do assembly and skinning. Thus: > > 1) Is content delivery a topic that is in scope for Z3 ECMS? Sure, this also relates strongly to exporting of content in a clean awy (zip file with XML and some binary stuff is my preference), and perhaps part of the infrastructure that'll exist for this could be reused. > 2) If so, is anybody interested in me moving this under the aegis of Z3 > ECMS and putting it in the z3lab SVN at Nuxeo? Sounds good. > 3) If so, I propose a layout where top-level directories reflect that > major subsystems people expect in an ECMS. In Nuxeo's diagram, these > are the circles near the bottom. Flat is better than nested. I don't want to move into speculative package layout yet, where we try to separate the packages by major components. We don't really know the shape of this yet, and we don't want to end up with an empty structure. Let's stick to simple top-level packages for the time being, I'd suggest. It's relatively easy to move them around in the future should the need arise. We should think grandly when we design, but in code I'd like to move to get practically useful bits relatively soon, and grand design in code doesn't tend to be conductive to that. Regards, Martijn
Hosting: Nuxeo: Zope service provider