#30780: Make "Getting Help" documentation much more prominent.
-------------------------------------+-------------------------------------
     Reporter:  Shai Berger          |                    Owner:  Gabriel
         Type:                       |  Augendre
  Cleanup/optimization               |                   Status:  assigned
    Component:  Documentation        |                  Version:  master
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  1
Easy pickings:  1                    |                    UI/UX:  1
-------------------------------------+-------------------------------------
Description changed by felixxm:

Old description:

> Issues like https://github.com/django/djangoproject.com/issues/947 show
> up very often, I think they are more common than actual website issues.
> Each and every time we close such an issue with "go get help in proper
> channels", it's a little failure -- for the submitter, of course, but
> also for us. I think we can try harder to make the correct channels more
> prominent. Here's a list of potential action items:
>
> 1. The whole "Getting Help" section on the documentation front page sits
> only in the side bar, below obviously-less-interesting stuff like the
> navigation tools. It is easy to miss it entirely.
>     1. We could make it one of the first sections in the list -- I
> suspect that the first three sections should be "First steps", "Getting
> help", and only then "How the documentation is organized".
>     2. I'd also consider making a link to .../faq/help/ float on the
> documentation page, like the language and version selectors do now.
>
> 2. The tutorial mentions "where to get help" in an admonition very close
> to its beginning, but then it is never repeated, and it is easily
> forgotten by the time anyone actually needs it.
>     1. Make the admonition link to the faq, and mention the links to get
> help which are present on every documentation page
>     2. Repeat the admonition, at least once on every tutorial page
>
> 3. (moved to [https://github.com/django/djangoproject.com/issues/948
> relevant repo]) ~~The ticket-creation form for the Django code -- the one
> I'm filling in now -- has a list of things for a (first-time) submitter
> to consider, under the heading "Please read this first"; I believe this
> list greatly reduces the amount of support-tickets filed on this tracker.
> A similar thing can be done for the djangoproject.com repo using
> [https://help.github.com/en/articles/manually-creating-a-single-issue-
> template-for-your-repository issue templates].~~

New description:

 Issues like https://github.com/django/djangoproject.com/issues/947 show up
 very often, I think they are more common than actual website issues. Each
 and every time we close such an issue with "go get help in proper
 channels", it's a little failure -- for the submitter, of course, but also
 for us. I think we can try harder to make the correct channels more
 prominent. Here's a list of potential action items:

 1. The whole "Getting Help" section on the documentation front page sits
 only in the side bar, below obviously-less-interesting stuff like the
 navigation tools. It is easy to miss it entirely.
     1. We could make it one of the first sections in the list -- I suspect
 that the first three sections should be "First steps", "Getting help", and
 only then "How the documentation is organized".
     2. ~~I'd also consider making a link to .../faq/help/ float on the
 documentation page, like the language and version selectors do now. ~~
 [https://github.com/django/djangoproject.com/pull/969 Fixed in PR969].

 2. The tutorial mentions "where to get help" in an admonition very close
 to its beginning, but then it is never repeated, and it is easily
 forgotten by the time anyone actually needs it.
     1. Make the admonition link to the faq, and mention the links to get
 help which are present on every documentation page
     2. Repeat the admonition, at least once on every tutorial page

 3. (moved to [https://github.com/django/djangoproject.com/issues/948
 relevant repo]) ~~The ticket-creation form for the Django code -- the one
 I'm filling in now -- has a list of things for a (first-time) submitter to
 consider, under the heading "Please read this first"; I believe this list
 greatly reduces the amount of support-tickets filed on this tracker. A
 similar thing can be done for the djangoproject.com repo using
 [https://help.github.com/en/articles/manually-creating-a-single-issue-
 template-for-your-repository issue templates].~~

--

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30780#comment:11>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.6d31f166857deaf8e973de0578cf6aef%40djangoproject.com.

Reply via email to