Website 39 add onsite location details to where for events exhibits page template

[SalazarJosh]

Overview

This PR is specific to the "WHERE" for event details on the event template and the event cards as seen on the Today and Upcoming page and the "What’s happening?" section on the homepage.

There are three parts to this enhancement:

• Changing how we present the WHERE for events/exhibits in library locations to include the floor, room # (where relevant), and “view floorplan” link, modeled after the Designation page templates
• Adding a “View directions” link to the WHERE for events/exhibits non-library locations
• Adjusting the presentation for Hybrid events to align with the other changes

This pull request addresses WEBSITE-39.

How I went about it

The strings are built in eventFormatWhere in the event.js utility file. They're built by pushing a series of strings named label to an object array where. where is then mapped in the event template file and the locality is extracted and applied as a link if it's present.

The floor plans are loaded in the event template file using useFloorPlan from use-floor-plan.js.

The "View directions" link is generated from createGoogleMapsURL if there is a locality in there where object. Both non-library events and library events can have a "View directions" link, but non-library events should always have a "View directions" link.

Examples

Here are some current events that we can preview:

• A non-library location with a “View Directions” link.
• A library location with a “View floorplan” link.
• A library location with an address and “View Directions” link.

For other events, hybrid and online, we don’t have current examples, but I can edit event details before running the logic to see what that looks like:

• A hybrid event with a library location:
  
  And the card:
  

• A hybrid event with a library location and event link:
  
  And the card (same as above):
  

• An online event (no library location):
  
  And the card:
  

Testing

• Make sure the PR is consistent in these browsers:
  • Chrome
  • Firefox
  • Safari (the assignee was not able to test the pull request in this browser)
  • Edge
• Run accessibility tests:
  • ARC Toolkit
  • axe DevTools
  • NVDA

[erinesullivan]

👍🏻 I see the working links in comparison to the live site. I also love seeing a PR that deletes more code than adding. Great job!