RE: [Wyonacms-dev] Re: Getting started (going in circles)
"Brian Topping" <[email protected]>
| Newsgroups | gmane.comp.cms.wyona.user |
|---|---|
| Message-ID | <[email protected]> |
> -----Original Message----- > From: Michael Wechner [mailto:[email protected]] > Subject: [Wyonacms-dev] Re: [Wyonacms-users] Getting started (going in > circles) > > Small pieces are certainly easier to read, but on the other hand the > navigation will grow. Yes, but the edits are more manageable. We are interested in the edits, not the navigation, right? If people contribute documentation at the short-term expense of navigation, IMHO it's worth it. When the documents start getting overwhelmingly large, the navigation will disappear as a cost of the longer pages. Does the cost-benefit change when considered that way? It would also be a walk in the park to have the documents aggregated in Cocoon and run through FOP to PDF for those that want to see it in a single document. If they weren't considering this already as a part of Forrest, I would be *really* surprised. > Apache Forrest would certainly help. I had the idea to make the > Documentation of Cocoon "editable" with Wyona. This way people from > Cocoon itself might get more interested into Wyona. You could > also plug > in the CVS and the official website into the editing/publishing > process. By doing this you would guarantee, that the website > and the CVS > are "synchronized". I posted this to the Forrest list earlier today actually and they were very receptive. My idea was that the edits are actually posted to the bug database (Scarab, if we/they are lucky enough to get that), as documentation bugs with a patch, so the comitter can take a look at it and approve it through the standard channel for that kind of thing. It works well in a development environment because it unifies the workflow of the development process with the workflow of the documentation process. > No. But you can ask Lon [email protected] for permission and then we > can send > you a version. > > > How can I activate it? > > Just place it within the Tomcat ROOT directory: > webapps/ROOT/xps/xopus > (where you have to create the directory "xps"). Cool, I'll do that, thanks! > All the best > > Michael As well! :b