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

Modify "Why use sign.mt?" Section on the about page #187

Open
TimothyRbz opened this issue Dec 4, 2024 · 7 comments
Open

Modify "Why use sign.mt?" Section on the about page #187

TimothyRbz opened this issue Dec 4, 2024 · 7 comments

Comments

@TimothyRbz
Copy link
Contributor

TimothyRbz commented Dec 4, 2024

At the moment, the information, pictures, text, and setup of the "Why use sign.mt?" section are not complete, up-to-date, or specific enough. I would suggest we hide it for now and bring it back once the individual elements are more complete.

@TimothyRbz TimothyRbz converted this from a draft issue Dec 4, 2024
@AmitMY
Copy link
Contributor

AmitMY commented Dec 4, 2024

Why not complete them instead? specific points you want to change per "slide"?

@TimothyRbz
Copy link
Contributor Author

TimothyRbz commented Jan 18, 2025

1st screen: "Real Time Translation"

  • Title Bold
  • "40+ signed and spoken languages" also bold
  • Double arrow icon violet (both in screen and ribbon below)
  • Replace Images with

Image
Image
Image

@TimothyRbz
Copy link
Contributor Author

TimothyRbz commented Jan 18, 2025

2n screen: "Multilingual Support"

  • Redundant, since we already say we have +40 languages
  • Replace with more important information

Titel: "API Integration"
Icon: (suggestion below) Bold and Violet
Text: Our API integrates seamlessly with your systems, workflows and platforms, so you can choose the best use case for real-time sign language translation
Picture: Suggestion

Image

Image: suggestion: Image

@AmitMY
Copy link
Contributor

AmitMY commented Jan 21, 2025

Only commenting for: "Real Time Translation"

  1. Bold - we don't use bold anywhere else. *except for the title of the FAQ which is a bug and is now fixed
original bold
Image Image
I think it looks nicer, and more consistent, to not have bold (again, no where else we have it)
  1. Replace Images with ... - that's not our interface though. it was a mockup, that is "bad" because the woman is not actually doing sign language

  2. Double arrow icon violet - changed color scheme to purple in theme(): change to purple #200 - let me know what you think

@TimothyRbz
Copy link
Contributor Author

TimothyRbz commented Jan 21, 2025

  1. Bold - ok (the figma design are super bold thats where my suggestion comes from, but if we don't have it anywhere else, not here to start)

  2. Right now, it looks like it failed to load. Here are three options:

  • a) Use the Figma design provided (best looking and most time-efficient).
  • b) Replace the model with our 3D skeleton (a solution I’d be happy with).
  • c) Add text visuals like "Hello, how are you?" (first two letters written, the rest greyed out and separated by a cursor).
  1. Great on the icons!

@TimothyRbz
Copy link
Contributor Author

4th screen: "Customisable appearance"

  • Add missing picture

Image

@TimothyRbz
Copy link
Contributor Author

5th screen: "Offline Functionality"

  • Hide for now

(Becasue I know you will have objections here my argumentation:
We don't have it anywhere in our pitch, in the last 3 month we mentioned it only once on the google impact application around the topic data protection by design, I don't have competence on answering questions about it... so better hide it)

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

No branches or pull requests

2 participants