Changes to FAQ - Githubissues

ScratchAddons / website-v2

The website for Scratch Addons. (version 2)

https://scratchaddons.com

GNU General Public License v3.0

51 stars 39 forks source link

Changes to FAQ #285

Open WorldLanguages opened 1 year ago

WorldLanguages commented 1 year ago

In progress

Goals of this PR:

Avoid including information that is already found in other places, and may change in the future. For example, I almost forgot there's a question about security vulnerabilities! We should not include the email right in the FAQ, because if we change it in the future, we might forget to change it here too.
Using some Google Search Console information, I've found phrases that are typically searched by users, such as "is scratch addons free", "are scratch addons allowed", "is scratch addons made by scratch", "is scratch addons free", and "scratch addons unblocked". I think we could try our best to summarize the answers and get Google to show a "featured snippet" which will be useful for users asking Google these questions.
Technical questions do not belong on the FAQ. My intention is to have this FAQ be exclusively for end-users. If there's not enough consensus about this change, we should at least try to rephrase these 2 year old questions and answers.

WorldLanguages commented 1 year ago

Fun fact: many people search on Google for what the "mod" block does on Scratch :P

WorldLanguages commented 1 year ago

Google also gets this one wrong:

Hans5958 commented 1 year ago

Technical questions do not belong on the FAQ. My intention is to have this FAQ be exclusively for end-users.

I beg to differ. I still think this is still useful for some people who want to know what they do, without going too deep to the tech side. Thing is, you should also remove the contributing questions if you want it to be "end-user", which, again, I don't think that's how it should go.

Hans5958 commented 1 year ago

If we somehow can add more questions (e.g. #274), then I would appreciate it.

WorldLanguages commented 1 year ago

you should also remove the contributing questions if you want it to be "end-user"

Contributing by translating and sending feedback is typical for the average end-user. Contributing through source code is not.

Still, I think I agree with what you said. We can explain some technical aspects without going too deeply.

Samq64 commented 1 year ago

https://github.com/ScratchAddons/ScratchAddons/issues/5289#issuecomment-1435378222

One of the first proposed solutions was to try restarting the browser. Try typing chrome://restart into the address bar and see if that solves the issue.

Could an FAQ for the extension crashing be added with that as a possible solution?

WorldLanguages commented 1 year ago

Could an FAQ for the extension crashing be added with that as a possible solution?

It would be better if we handled background errors properly instead - see #5306 We could recommend the user to restart the browser in an upcoming error page

Samq64 commented 1 year ago

I think there should be an FAQ for "Why don't I have the update yet?"

Samq64 commented 1 year ago

Could ScratchTools be added to the incompatible list? It's reasonably popular at this point and I've seen bug report screenshots with it enabled.

Secret-chest commented 1 year ago

Could ScratchTools be added to the incompatible list? It's reasonably popular at this point and I've seen bug report screenshots with it enabled.

If you choose the right features it's OK.

WorldLanguages commented 1 year ago

I don't think we've ever mentioned in the FAQ that you don't need to do anything to get extension updates, browsers should handle it for you assuming you downloaded from the stores. But we could mention how to force the update checking in chrome://extensions