So That I can demo to other partners what skinning could look like
Acceptance Criteria
Given 2 datapoints exist on map from issue xxxx
When I navigate to the page for the 2nd map (any free map will do)
Then the same data is also displayed on that map
Given a rhythm associated with a location that can't be displayed on the map
When the map is shown
Then the rhythm is not displayed (this is not a bad thing -> it simply shouldn't crash)
PO notes
don't worry about amount of hard coding in frontend needed to represent skinnability of maps for now -> this will move to the backend in later iterations
Story
As a stakeholder
I Want to confirm the skinnability of the maps
So That I can demo to other partners what skinning could look like
Acceptance Criteria
PO notes
Implementation Notes
Checklist: