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

Terms of Service and Community Standards aren't publicly accessible #4133

Closed
bjester opened this issue Jun 13, 2023 · 4 comments · Fixed by #4609
Closed

Terms of Service and Community Standards aren't publicly accessible #4133

bjester opened this issue Jun 13, 2023 · 4 comments · Fixed by #4609
Assignees
Labels
DEV: frontend P1 - important Priority: High impact on UX

Comments

@bjester
Copy link
Member

bjester commented Jun 13, 2023

Desired behavior

The 'Terms of Service' and 'Community Standards' documents should be publicly accessible so that we can link to them and users can view them prior to starting the account creation process.

Current behavior

The documents are only visible when you're logged in or are creating an account. They show with a modal, and aren't dedicated pages to which we can share links to.

Value add

  • Ability to share links to these documents
  • Public visibility
@bjester bjester added P1 - important Priority: High impact on UX DEV: frontend labels Jun 13, 2023
@bjester
Copy link
Member Author

bjester commented Jun 13, 2023

If we can wrangle strings to make this happen without translation issues, this should be a straightforward task for our upcoming release or patch.

@radinamatic
Copy link
Member

Community standards page has been translated to all 4 locales we support on Studio, but after I translated the ToS into Spanish, we decided to keep them in English, as there is a lot of legalese involved which would require translators to have experience in legal terminology for the translation to have real value (my Spanish version would also require some review).

@bjester
Copy link
Member Author

bjester commented Jun 13, 2023

@radinamatic Ah good to know. I figured we had translated them entirely. That sounds like it'll push this to the next major release.

@radinamatic
Copy link
Member

Not necessarily, if we decide to keep the ToS in English. I doubt our current translation partner has capacity for legal translation, and the rates for those services are significantly higher.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DEV: frontend P1 - important Priority: High impact on UX
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants