Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

link to bug tracker in Support menu #220

Closed
fastfasterfastest opened this issue Mar 5, 2013 · 8 comments
Closed

link to bug tracker in Support menu #220

fastfasterfastest opened this issue Mar 5, 2013 · 8 comments
Assignees
@Krinkle

Comments

@fastfasterfastest
Copy link

I think it would be helpful if the Support menu (upper right) contained a link (or links) to "Browse or Submit bugs". If possible it would be nice if such link was "context sensitive" so when you are on jquery.com it takes you to the jquery bug tracker, when you are on jqueryui.com it takes you to the jqueryui bug tracker, etc.
@gnarf
Copy link
Member

gnarf commented Mar 5, 2013

i think there might be a page on contribute with links to bug trackers and explaination of each

@ajpiano
Copy link
Member

ajpiano commented Mar 5, 2013

http://contribute.jquery.org/triage/ has it, but it needs an anchor. context specific bugs link would actually be kind of useful anyway....the "Bugs/Issue Tracker" link in the footer is already sort of useless/strange on certain sites, e.g., jquery.org, where it still links to jquery core issues.

@fastfasterfastest
Copy link
Author

That page (http://contribute.jquery.org/triage/) sounds like a good target for a new link in the Support menu, perhaps directly to one of the last sections on that page.

I think it is quite common to find links to help/tech-support/report-a-problem etc. in "support" sections on various web sites. Currently you can find that/those links on the "home page" of the jquery.com, jqueryui.com etc., but I think it would be helpful and useful if they existed in the Support menu as well - accessible from any page. If such new link/links cannot be "context sensitive" as described above, then a link to http://contribute.jquery.org/triage would be useful, I think.

@ajpiano
Copy link
Member

ajpiano commented Mar 5, 2013

Yeah, I meant to say that as well -- I think we should definitely link to that triage page, with an anchor to the actual list, in the Support menu

@ajpiano
Copy link
Member

ajpiano commented Mar 5, 2013

In short, 👍

@scottgonzalez
Copy link
Member

The triage page isn't geared toward users submitting bugs. Even if we linked directly to the list of issue trackers, the text at the top of the section would be confusing for users who are looking for support.

@Krinkle
Copy link
Member

Krinkle commented Apr 4, 2024

In jquery/jquery.com#237, we consolidated many support pages into https://jquery.com/support/ which is linked from the "Support" menu and includes a section at the bottom about bug reports.

https://jquery.com/support/#found-a-bug
Found a bug?
For reporting bugs in libraries, documentation, or content, the project's GitHub issues tracker should be used. All jQuery projects can be found at https://github.com/jquery

Screenshot

I propose adding a "Report a bug" explicilty in the Support menu, but am unsure which of these three destinations to pick:

  1. https://github.com/jquery/ - Let the user land here, and pick their repository, and follow the same discovery path that probably most people need to follow regardless, assuming our git repo is a fairly common landing place. They then find their way to "Issues", potentially performing a search first, then click "New issue". There, now three steps further, they are greeted with a template about minimal test cases, and latest jQuery version etc.
  2. https://contribute.jquery.org/bug-reports/ - This contains a more fleshed out version of the information in the template, with the benefit of receiving it immediately upon the jquery.com menu link, instead of after several steps. Also, on this page starts with how to ask for support from chat/StackOverlow first. Do we still prefer that? Also, the URLs are actually clickable/linked so people are more likely to follow "how to reduce a test case" and e.g. use CodePen/JSBin. This web page then sends you to https://github.com/jquery/jquery/issues once done.
  3. https://jquery.com/support/ - Linking this would take the recommendation to ask for support first and literally drop people there first. If they go past the Learning Center, API Docs, Chat, StackOverflow, they then find the "Found a bug" heading and go to https://github.com/jquery from there.

Thoughts?

@Krinkle Krinkle self-assigned this Apr 4, 2024
@Krinkle
Copy link
Member

Krinkle commented Apr 5, 2024

Summary of jquery_dev Matrix chat today:

  • Between these three links, @timmywil prefers https://contribute.jquery.org/bug-reports/.
  • Timmy raisees that despite this page doing a good job to discourage invalid bug reports, adding exposure from a prominent link on the site, may increase bug reports, especially invalid ones, beyond our capacity to triage (the team isn't as large as it used to be).
  • @mgol suggests we try it. We agree to try it and see how it goes.

@Krinkle Krinkle closed this as completed in 43bc52a Apr 5, 2024
Krinkle added a commit to jquery/jquery.com that referenced this issue Apr 17, 2024
@Krinkle
Download: enable h1, reduce decisions, remove old info
fafd1f1 
* Enable the h1 heading. The page content has no custom h1 of its own
  so looks out of place with other pages on jquery.com.

* Invert the order of some paragraphs so that links are clear and at
  the top, with a single recommended option each time and then other
  links in a bullet list after it.

  E.g. there is now an actual "Download jQuery 3.7.1" button,
  describing over top that it is the compressed production version,
  and then a list of other links.

  Explanations of these files now follow the list instead of being in
  front of it, thus burying the links less.

* Promote link to browse releases.jquery.com to the first section.

  I've personally never used the links that were in the first section
  previously as they always felt like too much text to read. When
  I land on the releases list, I know what each variant is and feel
  more confident that I'm getting the right one instead of reading the
  long link labels. If we like this direction and shorter links, taking
  into account that many people probably already "start" at
  releases.jquery.com based on links to there from other places and
  thus only see the short versions there, we could also explore
  shortening the labels here. I've not done that in this commit yet.

* Remove outdated info about source maps still being a future/emerging
  technology.

* Remove instructions for Bower.

* Improve "Yarn" CLI link readability by giving it the full term as
  its link label, "Yarn CLI" instead of only partly linked.

* Improve "npm" sentence by linking "npm" and then naming
  "jquery package" in the second link.

* Update Pre-Release section to link to releases site instead of
  to a single file, since there are now quite a lot of variants of
  this file that people may want to choose between.

* Update "jQuery CDN" section heading to link to the releases site
  from its name, and remove outdated sponsorship mention.

* Improve "Other CDNs" by applying the bolding more focussedly
  (when an entire paragraph is bold, it's the same as bolding nothing,
  is my rule of thumb). Ensure the bolded portion is readable and
  understandable by itself.

* Remove "Build from Git" section, covered by README where it is
  presumably more up to date. This is linked to from "About the code".

* Remove mention of closed jQuery Forum from "About the code",
  instead link to "Report a bug", matching the link chosen at
  jquery/jquery-wp-content#220.

* Remove mention of plugins.jquery.com from "About the code".
  Ref jquery/infrastructure-puppet#29.
Krinkle added a commit to jquery/jquery.com that referenced this issue Apr 17, 2024
@Krinkle
Download: enable h1, reduce decisions, remove old info
d70de29 
* Enable the h1 heading. The page content has no custom h1 of its own
  so looks out of place with other pages on jquery.com.

* Invert the order of some paragraphs so that links are clear and at
  the top, with a single recommended option each time and then other
  links in a bullet list after it.

  E.g. there is now an actual "Download jQuery 3.7.1" button,
  describing over top that it is the compressed production version,
  and then a list of other links.

  Explanations of these files now follow the list instead of being in
  front of it, thus burying the links less.

* Promote link to browse releases.jquery.com to the first section.

  I've personally never used the links that were in the first section
  previously as they always felt like too much text to read. When
  I land on the releases list, I know what each variant is and feel
  more confident that I'm getting the right one instead of reading the
  long link labels. If we like this direction and shorter links, taking
  into account that many people probably already "start" at
  releases.jquery.com based on links to there from other places and
  thus only see the short versions there, we could also explore
  shortening the labels here. I've not done that in this commit yet.

* Remove outdated info about source maps still being a future/emerging
  technology.

* Remove instructions for Bower.

* Improve "Yarn" CLI link readability by giving it the full term as
  its link label, "Yarn CLI" instead of only partly linked.

* Improve "npm" sentence by linking "npm" and then naming
  "jquery package" in the second link.

* Update Pre-Release section to link to releases site instead of
  to a single file, since there are now quite a lot of variants of
  this file that people may want to choose between.

* Update "jQuery CDN" section heading to link to the releases site
  from its name, and remove outdated sponsorship mention.

* Improve "Other CDNs" by applying the bolding more focussedly
  (when an entire paragraph is bold, it's the same as bolding nothing,
  is my rule of thumb). Ensure the bolded portion is readable and
  understandable by itself.

* Remove "Build from Git" section, covered by README where it is
  presumably more up to date. This is linked to from "About the code".

* Remove mention of closed jQuery Forum from "About the code",
  instead link to "Report a bug", matching the link chosen at
  jquery/jquery-wp-content#220.

* Remove mention of plugins.jquery.com from "About the code".
  Ref jquery/infrastructure-puppet#29.
@Krinkle Krinkle mentioned this issue Apr 17, 2024
Merged
Krinkle added a commit to jquery/jquery.com that referenced this issue Apr 19, 2024
@Krinkle
Download: enable h1, reduce decisions, remove old info
25595b9 
* Enable the h1 heading. The page content has no custom h1 of its own
  so looks out of place with other pages on jquery.com.

* Invert the order of some paragraphs so that links are clear and at
  the top, with a single recommended option each time and then other
  links in a bullet list after it.

  E.g. there is now an actual "Download jQuery 3.7.1" button,
  describing over top that it is the compressed production version,
  and then a list of other links.

  Explanations of these files now follow the list instead of being in
  front of it, thus burying the links less.

* Promote link to browse releases.jquery.com to the first section.

  I've personally never used the links that were in the first section
  previously as they always felt like too much text to read. When
  I land on the releases list, I know what each variant is and feel
  more confident that I'm getting the right one instead of reading the
  long link labels. If we like this direction and shorter links, taking
  into account that many people probably already "start" at
  releases.jquery.com based on links to there from other places and
  thus only see the short versions there, we could also explore
  shortening the labels here. I've not done that in this commit yet.

* Remove outdated info about source maps still being a future/emerging
  technology.

* Remove instructions for Bower.

* Improve "Yarn" CLI link readability by giving it the full term as
  its link label, "Yarn CLI" instead of only partly linked.

* Improve "npm" sentence by linking "npm" and then naming
  "jquery package" in the second link.

* Update Pre-Release section to link to releases site instead of
  to a single file, since there are now quite a lot of variants of
  this file that people may want to choose between.

* Update "jQuery CDN" section heading to link to the releases site
  from its name, and remove outdated sponsorship mention.

* Improve "Other CDNs" by applying the bolding more focussedly
  (when an entire paragraph is bold, it's the same as bolding nothing,
  is my rule of thumb). Ensure the bolded portion is readable and
  understandable by itself.

* Remove "Build from Git" section, covered by README where it is
  presumably more up to date. This is linked to from "About the code".

* Remove mention of closed jQuery Forum from "About the code",
  instead link to "Report a bug", matching the link chosen at
  jquery/jquery-wp-content#220.

* Remove mention of plugins.jquery.com from "About the code".
  Ref jquery/infrastructure-puppet#29.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Krinkle Krinkle

Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@scottgonzalez @ajpiano @Krinkle @gnarf @fastfasterfastest