-
Notifications
You must be signed in to change notification settings - Fork 12
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
Requests phone line should be prominent in base.html #54
Comments
It would be nice if we had the top banner alternate between the current DJ and the requests line info, e.g. with a CSS animation |
Not only is it not prominent, it is also not visible anywhere on the site right now. Should it show up all the time, or only when a DJ is on air? |
I would argue all the time. It should be clear that Automation isn't going to pick up the phone. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
So where should this go on the site? I think yet another trackman option is probably too much. People already somehow struggle with the auto-logoff feature. I'm thinking one of four places: in between the current track and the DJ name, in the speech bubble, right under the current DJ name, or directly to the right of the current DJ. The first one would have real problems with long track names, the second would probably fit, but would add clutter, the third would probably look weird with spacing between the header and the nav features, and the 4th may have similar problems as the first, but at least wouldn't move around. |
We could have a settings button that would let DJs change their name and similar options. We could have the checkbox for this there. (It could also be an option during the initial signup process.) |
No description provided.
The text was updated successfully, but these errors were encountered: