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

Always mention we're not the Scratch Team #439

Closed
Samq64 opened this issue Apr 29, 2024 · 5 comments
Closed

Always mention we're not the Scratch Team #439

Samq64 opened this issue Apr 29, 2024 · 5 comments

Comments

@Samq64
Copy link
Member

Samq64 commented Apr 29, 2024

The feedback page has a warning that can trigger telling users we're not the Scratch Team and links to their contact page but it's not completely effective. Why not just always mention it somewhere on the page?

@CST1229
Copy link
Member

CST1229 commented May 1, 2024

What if we add it straight to the homepage or to the welcome.html page?

Most people sending these kinds of "thinking we're the ST" messages through feedback probably got there through Google directly, so they wouldn't see either of those pages.

@WorldLanguages
Copy link
Member

What if we add it straight to the homepage or to the welcome.html page?

Let's not forget that all pages in the footer say: Scratch Addons is not affiliated, associated, or in any way officially connected with the Scratch website or the organizations that maintain it. that includes the homepage and welcome pages.

It is also true that we rank relatively high for some Scratch searches like CST said.

@Hans5958
Copy link
Member

Hans5958 commented May 2, 2024

Three reasons.

  1. I believe people would more likely to gloss over a static message (ie. a message that's always shown) than a message that's appear after the action of the user.
  2. I'm not sure how you define it being as "not completely ineffective." I saw there's barely any mention of the Scratch Team these days. It's also pretty hard to compare the effectiveness post-PSW and pre-PSW, so I digress.
  3. There is a disclaimer on the bottom, as mentioned before by the others, but this would also more likely to be glossed, so I also digress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants
@Hans5958 @WorldLanguages @CST1229 @Samq64 and others