-
Notifications
You must be signed in to change notification settings - Fork 83
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
Menu item and interface for data download #334
Comments
I would like to work on it, andrewtavis can you assign me to this issue? |
Assigned, @marekviktor! Please let me know if there's anything I can do to support :) |
Via email @marekviktor sent along:
I'd say that we don't need to worry about actually doing the download for this issue. Just the interface is fine. And as far as the various elements of the download page, we can also make separate issues for those for you! For this one let's just focus on making the element that says |
#382 has been brought in finally. Sorry for the wait, @marekviktor :) Lots going on. @SaurabhJamadagni, are you able to finish up re-applying the work to get it up and running again? |
Hey @andrewtavis! Sorry I am a bit occupied with college work and finals. I don't think I will be able to get to it until after the 9th may. Will that be affecting the release timeline? |
It's not a problem, @SaurabhJamadagni :) We can get to it later. |
Terms
Description
This issue would implement an option on the installation screen of the Scribe menu to take the user to a screen where they can download data for Scribe keyboards. The menu option would be directly below the keyboard installation steps as shown below:
We'll be checking the UI for the data installation screen in a future Scribe Weekly, but for now the current version can be seen in Figma. I'll post an image of the finalized installation screen designs after they're checked with the rest of the team 😊
Contribution
I'll be doing the designs for this, and am happy to implement the menu option as well when we start to work on #89 🚀
The text was updated successfully, but these errors were encountered: