# Documentation blues **URL:** \ **Category:** Message Board\ **Created:** [September 11, 2024, 10:49pm UTC](https://discuss.tryton.org/t/documentation-blues/7844 "2024-09-11T22:49:43Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![dotbit](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/dotbit/32/2093_2.png) [@dotbit](https://discuss.tryton.org/u/dotbit)\ **Post date:** [September 12, 2024, 5:47am UTC](https://discuss.tryton.org/t/documentation-blues/7844/3 "2024-09-12T05:47:11Z")
> [@cjm51213](#): > > Maybe there is a secret set of docs that are more illuminating? Maybe a document that explains how the documentation works? (-: Seems like a problem to me too. The official documentation at [docs.tryton.org](http://docs.tryton.org), while technically accurate, is too technical for people not familiar with tryton. There is [Howto - Tryton Discussion](https://discuss.tryton.org/c/howto/30) where anyone may write a Howto, but very few do, and usually the documentation is rejected as not being the right quality. You may find out how a module is supposed to be used by checking the tests directory inside the module directory. By looking at how the tests scenarios are written one can usually understand how the module is intended to be used. But this is technical too, so I guess Tryton is a technical product. There are some efforts: > [@Sponsoring of 2 weeks to write the documentation](https://discuss.tryton.org/t/sponsoring-of-2-weeks-to-write-the-documentation/7271/5): > > Of course we will reach out everyone who contributes to send the proper invoice What do you think should be improved using the existing documentation infrastructure? --- _[View the full topic](https://discuss.tryton.org/t/documentation-blues/7844)._