dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

Hi there,

there has recently been some nice contributions to the documentation
writing, which is great.


I was wondering about this:

1. Could we quickly and together come up with an overall table of contents?
This will be a useful starting point, give us an overview of what we need to
write and make it easier to delegate tasks.

2. Should we assemble all the xml files / modules into one file? To me its
more sensible to have all of it in one document. Or is there a mvn docbkx
goal for aggregating all the docs?


regards, Lars