Interesting idea. I never thought about sharing the code of the project documentation
But I don’t think that a good idea for this case. For me, I won’t help because of git commit (I don’t handle it).
Maybe a better option if they open the wiki on the github projet ?
We can try to seperate the 2 documentations to answer differently.
The community write on github for tips and tricks, and let them complete the docs.axelor
They just have to refer of generic informations, and let us handle « news » and « how to do »
With all versions Axelor have, with all modifications it hard work to handle all the documentation by the community. It will be more easier to update tips and tricks than the documentation for us (I guess)
They are some topics in this forum who can be add directly on the github.
I work on one more (VAT configuration)
My suggest is to categorize the github :
- installation (config server, docker, require …)
- a good start (what you have to know, avertising, how to start properly …)
- modules (description for every module, start configuration …)
- optimize configuration (tips and tricks advanced …)
OR (another subjection), they install a Xwiki on this link wiki.axelor.com and with request in this forum « we » authorize new peoples to help us to for write a documentation of Axelor.
Have a good day !