On Wed, 2012-01-18 at 11:16 -0500, Steven Hawkins wrote:
Yes, anything with nested or complex tables didn't import very
well. Also the xml examples sometimes have errors rather than showing the docs.
will see if I can correct some of these then.
For the grammar we have control over what docbook is generated, so I will take a look at
simplifying the structure and re-import. Ideally we would use a process built into the
release to update confluence.
Sounds good, only issue I have seen is there seems
to be no import of
HTML. They support richtext or markup. We need to some how generate that
Maybe we should just lock the documentation module for now rather than deleting so that
it will be easier to access the source until the docs are corrected. Will we still even
need separate downloadable pdf docs, or will we just want to put the pdfs in the kits?
OK, I do not think we need separate PDF downloads anymore, as any user
can export these docs into PDF if they want. Yes, we need to change the
release process such that at the time of release we make a copy of the
sub-space and assign the release number. As per adding the PDF to docs,
I have not seen Jboss AS doing the same, so I am OK if we do not include
them anymore for ease of doing the build in one step.