> >> > >> A CMS includes things like content authoring, content auditing, > >> workflow management, presentation logic, *and* content repositories. > >> The repository is only a (critical! important! vital!) piece of the > >> CMS > >> puzzle, but it's foolish to consider a content repository enough to > >> implement a serious CMS. > > > > This is true for the current stage of development but we hope to get > > this > > features in the future. We will port our process engine (for rendering > > and > > workflow management) to slide and are going to donate it to the slide > > project > > if the public likes it. > > So I think it should still remain under the flag of CMS. > > I humbly yet strongly disagree. Both presentation logic and workflow > management are things that are almost impossible to standardize. Those > who tried failed rather miserably in the market. > > All commercial CMS vendors and the major open source CMSs (Zope, for > example), are moving away from a CMS toward a CMF (content management > framework), a toolkit where the frontend/repository/backend stages are > clearly separate (and interoperable!) and the various pieces can be > changed independently. > > I think it would be silly for slide to do the exact opposite.
It's nice to have you around on this list Stefano, you're able to point out things very clearly. I'm propagating the idea of moving from a CMS to something like a CMF in our company for quite a while. But I think that Slide should be more than just a content repository. If we don't provide some bundled CMS build on top of slide (JSP-based, Cocoon-based or whatever), many people don't see the potential of Slide. But first we have to get Slide running as a content repository and it's still a way to go. My favorit issues are: - Getting the stores to work as expected (at least file/db-stores) - Implement internal locking (should not be transactional) - Improve and fix caching. It's not fully transactional in some places and can be improved (especially lock/permission-cache) - (lateron) real XA-support to use different stores (a great feature of slide) in one transaction - Extendable event mechanism (that is essenital for 'inverted caching' in the presentation layer or to distribute changes in a clustered environment) - Implement fast searching capabilities (properties and full text search, perhaps using lucene) - Internal link checking (so that if you check out some revision of a document that uses others you're informed and get the choice to check out the used documents in the right revision as well). I don't know, if the current content interceptor concept allows such a feature as an optional module, otherwise it should be improved to allow something like this. On the other hand I still won't drop my idea to donate our rendering/process-engine (maybe into proposals-section) and implement some demo-project to give users a better starting point and a full featured framework to implement projects. But I see that this have to be discussed. Daniel > > -- > Stefano. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
