I think they all should be moved over, but we should keep short chapters in the user manual explaining their purpose and a few examples, with pointers to the new dev manual for further detail On Aug 21, 2014 11:12 AM, "Jason Pickering" <jason.p.picker...@gmail.com> wrote:
> Hi there. Based on some good feedback last week during the Oslo DHIS2 > Academy, I have made a first cut of a developer manual. As I see it, this > basically involves slicing out all of the stuff really aimed more at > developers (and in some cases implementers) and less so, users. The chapter > on the WebAPI is being constantly expanded by the core developers, but in > many cases, far exceeds the level of information required by most users. > Some of the developers/implementers which I spoke with last week wanted > more information in the developers manual. So, I think moving the really > technical stuff to a dedicated developer manual would be a good idea, and > allow even more detailed technical stuff to be written, without necessarily > addressing the needs of the users. > > I have , for the time being, left the sections (Technical architecture, > Web API, Apps, and the appendix on R) in the main manual, but I think > (depending on feedback from the community) that we can slice these out of > the main user manual, and put them in a dedicated developer document. > > Thoughts? > > Regards, > Jason > > > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-devs > Post to : dhis2-devs@lists.launchpad.net > Unsubscribe : https://launchpad.net/~dhis2-devs > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
