-
Notifications
You must be signed in to change notification settings - Fork 1
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
Navigation > Progress Bar Colors #10
Comments
Yep that works for me! I did notice after returning to the homepage after searching that it marks existing children as currently on the "Search" step — shouldn't that be set to wherever you left off, instead? Maybe it's just not finished yet. I also think you ought to be able to jump to any step for a child by clicking on it from the homepage. |
We reworked the progress bar functionality and I'm pretty happy with the direction. The remaining tweaks are to use the light blue and dark blue in the diagonal style (in order to represent in progress as a mixture of "complete" and "incomplete"). I would also like to see the steps on the home page progress bars function as buttons. |
Just tweaked the student list code so that each stage in the student's progress bar is a link. It still needs the proper "href" value though. |
looks good to me! |
The only thing that feels weird to me is that "step 1 - search" is highlighted on the homepage's existing students' progress bars. I see the logic there, but I feel like it's competing with the "active" step (the furthest one reached so far) within that student's progress. |
@samrgray Kirk and Joel have been tweaking the progress bar colors. They felt that the diagonal texture line red too much like caution tape / added dimensionality.
They also tried switching the dark blue and gray colors so that the value of “current” (yellow) and “visited” (gray) are a little closer in value, whereas ‘un-visited’ is darker and less visually related.
We're not sure this is reading well and we'd love to get your eyes on it.
The text was updated successfully, but these errors were encountered: