-
Notifications
You must be signed in to change notification settings - Fork 390
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
Awesome bar/landing page redesign #844
Comments
Tagging @cassiecardiff in case she's interested in mocking up a UI or two. |
2 tasks
At the Binder/Jupyter meeting in Oslo the last days, we discussed what "screens" a new BinderHub UI might entail, extending on the idea of the awesomebar, and here are the notes: https://hackmd.io/teR1MefxSjW9mLJTLSSCjw |
This was referenced Sep 9, 2019
There are more thoughts (in particular on the API binderhub has to expose) in #351 |
This was referenced Feb 7, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
BinderHub's current landing page is a form with a lot of fields, dropdown menus and options. You can do "everything" with it but it isn't very friendly for newcomers and hard to discover what the different options do/when you should use them.
In contrast there is https://addons.mozilla.org/en-US/firefox/addon/open-with-binder/ which let's you click a button when you are on any kind of page that could be launched on mybinder.org. It will try its best to figure out how to construct the URL to visit (basically what to put in which part of the form).
This issue is about designing and then implementing what we are calling "the awesome bar". Ideally the BinderHub landing page would only have a single text box into which people paste the URL of the repository/notebook/thing they want to run on Binder and it figures everything else out.
We could get a start on the "parse URL and do magic" part by reusing the code from the Firefox extension.
The Binder team doesn't have a huge amount of experience with frontend development so this is a call for help to those who have experience with UX/UI design and those who have skills on the web dev front.
There are a few constraints we should stick with: the colour scheme should fit with what we have now, we aren't looking for a radical colour/design change. The tech stack should somehow fit the following description: "modern JS, react based, opinionated, simple to maintain and deploy as part of a tornado app".
See #351 for previous discussions on the awesome bar.
See #777 for an existing suggestion and plan in terms of "tech stack" (its ideas have support so probably wise to stick with it or at least not deviate massively).
The text was updated successfully, but these errors were encountered: