Upgrade feedback page

[GrahamSH-LLK]

Templates

Add templates or more textboxes for bug reports and feature requests. In most cases, users don't give very clear feedback that doesn't help us repro.

Link to FAQ

People might have questions that are answered on the FAQ

Suggest existing GH issues

We can parse text to find relevant GitHub issues. The VSCode repo does something like this with a GitHub action on new issues.

[Hans5958]

There also my suggestion where we have the ?source=... query so we don't need -notif on the version.

Linking to FAQ might be something that I can do ASAP.

Templates: I'd rather have text template like the ones we have on issues, instead of adding more elements. We could start using Markdown instead of having them in code blocks.

Suggest GH issues: That would be too heavy for our scale at the moment.

[Hans5958]

Alright, let's get this done and closed.

• We already got ?utm-source on it so this is nice.
• FAQ has been linked on it.
• Templates and GH issues still has the same stance'

Other than that, what else can we do? I want to explore the loading icon if we haven't, but what else?

[WorldLanguages]

Repro is easier now, because users can share their list of enabled addons. Only enhancement I can think of, is having predefined templates, have the user choose if they're reporting a bug, feature, or something else. Then we can have custom text depending on what the user chose. Also, many users send feedback twice, probably because our glitch server isn't awake. Could we wake it up as soon as the user types more than 5 chars on the input?

[CST1229]

Maybe clarify that the username field may be used for a response and is not a title field (possibly by placing it lower)? EDIT: Maybe even note that your OS and browser language will be sent?

[Secret-chest]

And say that if you can use GitHub, then it's better to post an issue.

[Hans5958]

Can we move Glitch into Workers?

[cobaltt7]

And say that if you can use GitHub, then it's better to post an issue.

github > discord > feedback page > scratch

although, we don't really need the github to be full of suggestions, maybe those would be better in the discord every time 🤔

Can we move Glitch into Workers?

or maybe use scradd (discord bot we use in the community server)

or i could just add a simple page to scradd's server to run the feedback page webhook

(scradd is hosted on https://openode.io btw)

[WorldLanguages]

Can we move Glitch into Workers?

Well, I wanted to use Glitch because it proves we can't link sent feedback to IP addresses.

[Secret-chest]

although, we don't really need the github to be full of suggestions, maybe those would be better in the discord every time 🤔

Why?

[Hans5958]

although, we don't really need the github to be full of suggestions, maybe those would be better in the discord every time 🤔

If you say so then we should start moving the "new addons" issues from the issue board to Discussions under the Ideas topic for the sake of not having suggestion on the board.

This should be discussed further in the project repo. In the moment, suggestions are accepted on the issue board.

[DNin01]

I think improving this feedback page is a great idea because it's the only way to send feedback without creating any accounts. Most Scratch Addons users probably don't have a GitHub or Discord account, especially since Scratch, our extension's target audience, is made for and used by kids.

We could have a selection screen of types of feedback, like Suggestion, Bug Report, etc., each with their own feedback template.

Some tips like "Make sure the bug doesn't happen when Scratch Addons is not running. This will prove if Scratch is causing the issue or if Scratch Addons is" would also be useful.

It'd also be nice to link to the Feedback section of the website privacy policy in case the user is unsure about what information will be collected.