51 | | A key advantage of the Web-based documentation is the comment section at the |
52 | | bottom of each document. This is an area for anybody to submit changes, |
53 | | corrections and suggestions about the given document. The Django developers |
54 | | frequently monitor the comments there and use them to improve the documentation |
55 | | for everybody. |
| 51 | A key advantage of the Web-based documentation is the ability for readers to |
| 52 | use the `ticket system`_ to submit changes, corrections and suggestions. The |
| 53 | Django developers actively monitor the ticket system and use your feedback to |
| 54 | improve the documentation for everybody. |
58 | | comments should explicitly relate to the documentation, rather than asking |
59 | | broad tech-support questions. If you need help with your particular Django |
60 | | setup, try the `django-users mailing list`_ instead of posting a comment to the |
61 | | documentation. |
| 57 | tickets should explicitly relate to the documentation, rather than asking broad |
| 58 | tech-support questions. If you need help with your particular Django setup, try |
| 59 | the `django-users mailing list`_ or the `#django IRC channel`_ instead. |
137 | | * Once a document is frozen for a Django release, we remove comments from |
138 | | that page, in favor of having comments on the latest version of that |
139 | | document. This is for the sake of maintainability and usability, so that |
140 | | users have one, and only one, place to leave comments on a particular |
141 | | document. We realize that some people may be stuck on a previous version |
142 | | of Django, but we believe the usability problems with multiple versions |
143 | | of a document the outweigh the benefits. |
144 | | |