-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add map of locations to /starred page #888
Comments
@amynicole Do the colors of the map pinpoint reference the slot availability? Currently, on desktop we use green for slots available and yellow for limited availability. I think we can show that on the map if we explain it or match it in the chart. The other option is to use colors that are not green or gold but are within the style guide. |
I was just copying what I saw on the live site. I believe they should use the same logic on mobile that they do on desktop. |
Some tasks to complete based on what is currently on staging
|
@theandrewbriggs I am not sure if we need the map of starred locations on the desktop version. I do not think we discussed this before, but as I was reviewing staging I was thinking how that might not be necessary. If you agree, then we can also remove the numbers next to the rows, but it also doesn't hurt to have those numbers there. |
We want parents to make choices of early learning programs based on the characteristics of the program, but we also understand that making a final decision on which preschool my child should go to might be affected by location. Therefore, a parent might choose 6 sites to compare, all 6 are excellent and meet my needs, but the 2 a parent might choose to apply to are based on being in an ideal location.
We think adding a map of locations on the Compare & Apply page will help parents compare locations of multiple sites and help them make a final decision of which one(s) to apply to. We also want to show the parent's location marker of the location they searched (represented as the blue marker).
The text was updated successfully, but these errors were encountered: