# How to improve Tryton's visibility for newcomers

**URL:** https://discuss.tryton.org/t/how-to-improve-trytons-visibility-for-newcomers/2350
**Category:** Communication
**Created:** [February 19, 2020, 7:43pm UTC](https://discuss.tryton.org/t/how-to-improve-trytons-visibility-for-newcomers/2350 "2020-02-19T19:43:41Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![dave](https://discuss-cdn.tryton.org/letter_avatar_proxy/v4/letter/d/ee7513/32.png) [@dave](https://discuss.tryton.org/u/dave)
#### Post date: [February 20, 2020, 1:29pm UTC](https://discuss.tryton.org/t/how-to-improve-trytons-visibility-for-newcomers/2350/8 "2020-02-20T13:29:18Z")

</div>

> [@pokoli](#):
>
> Build end user documentation

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](https://discuss.tryton.org/t/call-to-arms-end-user-docs/261), on [more than one occasion](https://groups.google.com/forum/#!topic/tryton/oxofO4OzMUc) 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/](https://tryton-documentation.readthedocs.io/en/latest/)
- [Welcome to the Tryton Administration Manual! — Tryton Administration Manual 2.0 documentation](https://tryton-administration-manual.readthedocs.io/en/latest/)
- [https://bitbucket.org/trytonspain/trytond-doc/src/default/](https://bitbucket.org/trytonspain/trytond-doc/src/default/)
- [GitHub - tryton-ar/documentacion-tryton-ar](https://github.com/tryton-ar/documentacion-tryton-ar)
- [MBSolutions](http://www.m9s.biz/doku/)

I also think that, although the [official Tryton documentation](https://docs.tryton.org/) 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](https://discuss.tryton.org/t/tracking-changes-to-records/1645/4) 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.

> [@pokoli](#):
>
> Are you interested in contribution (with work or money) to some of the topics?

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](https://xkcd.com/927/)), I am trying to take the best ideas/parts of that documentation and create a comprehensive [Administration and Configuration Guide and User Guide](https://bitbucket.org/libateq/tryton-documentation/src/development/) for Tryton, which I am planning on working on when I get time. Any comments, help or contributions would be most welcome.

---

_[View the full topic](https://discuss.tryton.org/t/how-to-improve-trytons-visibility-for-newcomers/2350)._