If done properly, this is a massive task, not just because creating good documentation in the first place is time consuming and requires in depth knowledge of Tryton, but much more importantly it needs to be kept up to date and maintained. I also think that this maintenance is not something that the core developers should be burdened with or even have to think about.
I know this is something that has been discussed before, on more than one occasion and from what I can see there have been quite a few different attempts at creating user / administrator documentation with varying degrees of success, but many are now out of date or seem to be unmaintained, here are a few:
- https://tryton-documentation.readthedocs.io/en/latest/
- Welcome to the Tryton Administration Manual! — Tryton Administration Manual 2.0 documentation
- https://bitbucket.org/trytonspain/trytond-doc/src/default/
- GitHub - tryton-ar/documentacion-tryton-ar
- MBSolutions
I also think that, although the official Tryton documentation is an excellent up to date reference point (especially for developers), some potential users go looking for more detailed user / administrator documentation and come across some of this documentation listed above. This then may be confusing some people or giving them a impression of Tryton as it was 5+ years ago. So having up to date, well maintained, end user documentation would then fill that gap.
Although, and I am fully aware/concerned this may end up just adding to the list I gave above (so a bit like this: xkcd: Standards), I am trying to take the best ideas/parts of that documentation and create a comprehensive Administration and Configuration Guide and User Guide for Tryton, which I am planning on working on when I get time. Any comments, help or contributions would be most welcome.