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.

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

Changes to FAQ #285

Draft
wants to merge 5 commits into
base: master
Choose a base branch
from
Draft

Changes to FAQ #285

wants to merge 5 commits into from

Conversation

WorldLanguages
Copy link
Member

@WorldLanguages WorldLanguages commented Dec 21, 2022

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 WorldLanguages marked this pull request as draft December 21, 2022 18:54
@WorldLanguages
Copy link
Member Author

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

@WorldLanguages
Copy link
Member Author

Google also gets this one wrong:

image

@Hans5958
Copy link
Member

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
Copy link
Member

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

@WorldLanguages
Copy link
Member Author

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.

@Hans5958 Hans5958 added type: enhancement New feature or request scope: content Related to the contents of the website, excluding blog and docs labels Jan 6, 2023

### Will my account be safe when using Scratch Addons?

Yes. Features related to your Scratch account are thoroughly reviewed by Scratch Addons contributors to ensure that they will not harm your Scratch account. Scratch Addons keeps your account credentials secure, and it will not modify or delete your projects or assets without your permission. However, you may use the extension without any account-related features if you so choose.

Addons on Scratch Addons also have been audited by multiple contributors on the repository, so no-one can just slip some malicious code under our eyes.
Addons on Scratch Addons also have been audited by multiple contributors on the repository, so no one can just slip some malicious code under our eyes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer "nobody" over "no one" but that's more of a personal preference

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Controversial. I suggest you open a new PR after this one gets merged if you think it's worth it.

@Samq64
Copy link
Member

Samq64 commented Feb 18, 2023

ScratchAddons/ScratchAddons#5289 (comment)

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
Copy link
Member Author

WorldLanguages commented Feb 20, 2023

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
Copy link
Member

Samq64 commented Jun 9, 2023

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

@Samq64
Copy link
Member

Samq64 commented Aug 20, 2023

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
Copy link
Contributor

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
Copy link
Member Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: content Related to the contents of the website, excluding blog and docs type: enhancement New feature or request
Projects
Status: Long Term
Development

Successfully merging this pull request may close these issues.

5 participants