My main concern is that it will be non-trivial to setup that type of feedback system, and I'm not sure how we would go about turning that type of data into actionable tickets. If anyone has experience with such a system, I'd be interested to hear about it.
On Sunday, December 27, 2015 at 10:19:05 AM UTC-5, Wim Feijen wrote: > > Hi Doug, > > I get lost regularly in Django's docs as well, so you are not alone there. > > I think it is a good proposal to add: > "find what you were looking for" or "was this page helpful" or "rate this > page on its organization, clarity, brevity, etc." data on every single > existing page of the documentation. > > I think it is a good thing to accumulate data. And if some page turns out > to be really bad or not helping, we have a choice to act on it. > > For me, that would be a good ticket which I would definitely accept, > because the scope is small and clear and it is something we agree on. The > best way to proceed in my opinion is to create an new ticket, to keep it > clear. Do you want to create this ticket? > > I have some other ideas on how to improve the documentation and layout as > well, but that is for another time. > > Bye, Wim > > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5e3ad3cf-d822-455f-862e-12cedfe8bb5f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
