generated from hackforla/.github-hackforla-base-repo-template
-
-
Notifications
You must be signed in to change notification settings - Fork 52
Closed
Labels
Interface: Food SeekerPriority - MedNeeds to be in the next releaseNeeds to be in the next releaseRelease Note: EnhancementShows on Release Notes under "Enhancements"Shows on Release Notes under "Enhancements"Role: Front-endFront End DeveloperFront End Developercomplexity: missingp-feature: MapFood seeker map viewFood seeker map viewpriority: MUST HAVEsize: 3ptThe lift to complete this user story 4-8hrsThe lift to complete this user story 4-8hrs
Milestone
Description
Context
With our split-screen view that shows both a list organizations and the map, it’s impossible to tell which pins correspond to which list item.
This makes it difficult to pick and choose an item, and to identify items.
How is it now?
Hovering a cursor over a list item has no effect on the map. Hovering over a map pin isn’t reflected by anything in the list.
Proposed new feature
- When hovering a cursor over a list item, highlight the corresponding map pin. This will help food-seekers know where a service is located.
- When hovering over a pin, highlight the row in the search results. Perhaps scroll to that item, if that’s possible.
- On mobile, there is no way to hover, so replace the ‘Details’ button with a ‘Show on Map” button, which when tapped, highlights the map pin.
- Number the results and the map pins, similar to Yelp
This will require a new highlight state for the map pin, and for result rows.
Here’s how Yelp does it — we could do something similar.
https://www.yelp.com/search?find_desc=tacos&find_loc=San+Francisco%2C+CA
Discussion
An added benefit of numbering our pins is that our search results become printable!
References:
Metadata
Metadata
Assignees
Labels
Interface: Food SeekerPriority - MedNeeds to be in the next releaseNeeds to be in the next releaseRelease Note: EnhancementShows on Release Notes under "Enhancements"Shows on Release Notes under "Enhancements"Role: Front-endFront End DeveloperFront End Developercomplexity: missingp-feature: MapFood seeker map viewFood seeker map viewpriority: MUST HAVEsize: 3ptThe lift to complete this user story 4-8hrsThe lift to complete this user story 4-8hrs
Type
Projects
Status
Done