I have some experience with the PDF generation of javadoc. I can look into that. As for website documentation we are using forrest see src/documentation/content. We do have a template for component documentation. In the components folder you can make a copy of component-template.xml and fill in.
Please use forrest to do a test build of your changes before you commit (basically to make sure that everything is "valid.") You'll probably want to do that anyways so that you can view your handi-work. sean On 4/26/05, Manfred Geiler <[EMAIL PROTECTED]> wrote: > 2005/4/26, Grant Smith <[EMAIL PROTECTED]>: > > > > Are there any guidelines for documentation we should be following ? > > > > I would like to improve our documentation; the extended components in > > particular. Should everything be done through Forrest ? > > Yes, please. > We could also try to enable the pdf generation and automatically > generate offline docs. > Anyone experience with that? > > -Manfred >
