On 8/31/05, Andreas Hartmann <[EMAIL PROTECTED]> wrote: > Felix Röthenbacher wrote: > > Maybe we should reconsider introducing the notion > > of a 'publet' in the sense of an out-of-the-box publication module > > that can be integrated in other publications. There will be some > > open questions like > > what URL space should a publet allocate and > By default, the URL space of the publication. > > As the mapping from URLs to documents is done by the DocumentBuilder, > I don't know how a publet could ship with a custom DocumentBuilder > (who should decide which one to call?) > > how it may be integrated smoothly and easily into an existing > > publication. > > At the moment, you declare it in publication.xconf and get all the > menu items provided by the publet. > > In the case of the blog publication, this would mean: > - declare it in cocoon.xconf > - a "Blog" menu section appears with an entry "Create new Blog" > - you create a blog page > - on the blog page, the menu contains an item "Create new Entry" > The rest is quite straightforward.
To paraphrase: It would make sense to extract the Document functionality into a module. Then it can be used in the "blog" or any other publication as well. We already discussed: - renaming the "File" menu to "Document". - having a section on the Site page for documentType-specific information. Rename "Document" to "XHTML". Extract the functionality. Be able to create a Publication that contains "XHTML", "Blog", and many other Document Types. IMO, all this functionality should be implemented at the server level, with each Publication able to override it. solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
