-
Notifications
You must be signed in to change notification settings - Fork 4
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
Sidebar - Move course options to "Print & Export" #2
Comments
I agree on the workflow, and that's sort of how I thought about the UI. Moving the print area settings to print makes a lot of sense, but there is one issue: the print options can be set per course. I think in most cases you'd use the same area/options for all courses, but also want to have the possibility to change that. So what I want to avoid is to have another list of all courses under the print & export section. So, I'd say I'm positive to your suggestion, just have to think a bit on how to do it without making it too complicated to handle different settings per course. |
Hi!
Just a suggestion to make the UI a bit more tidy (IMHO).
Current:
![Screenshot 2022-07-20 at 14 41 13](https://user-images.githubusercontent.com/10381866/179984481-d2061ed2-912e-40a1-be6d-54d2fc55af83.png)
P.t. the sidebar UI is as following:
As we can see, each course has an "Options"-section with settings related to print.
Suggestion:
Move the course options related to print to the "Print & export" section. The reasoning for this is in a workflow print & export is often the last thing you do, and the sidebar invites to follow that workflow by starting with the foldables at the "top" and "working" its way down.
E.g. my workflow would optimally be:
I've included a quick mockup (i.e. not implemented nothing, just played around with devtools) for a suggestion of what moving the "options" to "Print & Export" might look like.
In the mockup I've changed the
Print selection
to a drop down such that selecting the right course might be easier. I'm not sure how doable this is from a technical point, as I'm not familiar with the code.The text was updated successfully, but these errors were encountered: