fix: map view dynamic cards

[ludtkemorgan]

This PR addresses #5987

• Addresses the issue in full
• Addresses only certain aspects of the issue

Description

On the listing map search below listing results a set of content cards can now be displayed

This is similar to what Doorway currently has

The three resource cards from the home page will appear here if they are turned on for the jurisdiction. Additionally a new custom content card can be added. This card(s) will display if the text string exist in the general overrides file.

How Can This Be Tested/Reviewed?

This is only visible in the map view so the easiest way to do that is to use the Bridge Bay jurisdiction:

1. Seed using the "region" configuration: yarn db:setup:staging-region
2. Set the jurisdiction env variable for the public site to be "Bridge Bay".
3. Go to the listings page and see the cards at the bottom of the right rail.
4. To test all of the cards you will want to also turn on enableAdditionalResources and enableResources

Author Checklist:

• Added QA notes to the issue with applicable URLs
• Reviewed in a desktop view
• Reviewed in a mobile view
• Reviewed considering accessibility
• Added tests covering the changes
• Made corresponding changes to the documentation
• Ran yarn generate:client and/or created a migration when required

Review Process:

• Read and understand the issue
• Ensure the author has added QA notes
• Review the code itself from a style point of view
• Pull the changes down locally and test that the acceptance criteria is met
• Either (1) explicitly ask a clarifying question, (2) request changes, or (3) approve the PR, even if there are very small remaining changes, if you don't need to re-review after the updates

---

[netlify]

✅ Deploy Preview for bloom-angelopolis canceled.

Name	Link
🔨 Latest commit	11d3e9e
🔍 Latest deploy log	https://app.netlify.com/projects/bloom-angelopolis/deploys/6a565f8260c2dd000876d388

[netlify]

✅ Deploy Preview for partners-bloom-dev ready!

Name	Link
🔨 Latest commit	11d3e9e
🔍 Latest deploy log	https://app.netlify.com/projects/partners-bloom-dev/deploys/6a565f82edf37b000838257a
😎 Deploy Preview	https://deploy-preview-6431--partners-bloom-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[netlify]

✅ Deploy Preview for bloom-exygy-dev ready!

Name	Link
🔨 Latest commit	11d3e9e
🔍 Latest deploy log	https://app.netlify.com/projects/bloom-exygy-dev/deploys/6a565f82cf99c8000801533d
😎 Deploy Preview	https://deploy-preview-6431--bloom-exygy-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[netlify]

✅ Deploy Preview for bloom-public-seeds ready!

Name	Link
🔨 Latest commit	7278ea5
🔍 Latest deploy log	https://app.netlify.com/projects/bloom-public-seeds/deploys/6a3ee5061876fa00082d79ad
😎 Deploy Preview	https://deploy-preview-6431--bloom-public-seeds.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[emilyjablonski]

(1) Looks like there's a visual regression on the pin popup
Main:

Branch:

(2) Testing this in the browser, I really prefer the behavior on main - can you remind me what is driving this change?

Main:

Branch:

[ludtkemorgan]

@emilyjablonski The change is a recommendation from Hannan. The furthest right version is what was decided.

It looks like I need to fine tune the results because there are a couple of cases the images are shorter than the max height when addresses are short and there are no tags

[ludtkemorgan]

@emilyjablonski this is ready to be re-reviewed. Let me know if you have any questions

[emilyjablonski]

Those updates look good! I'm seeing a regression on the padding on the mobile card though

[emilyjablonski]

@ludtkemorgan It looks like it's still the case that not all images in the list are the same height, not sure if that's an issue or acceptable given the updates to design, but this otherwise lgtm! Lmk if you wanna move forward, it's only like a 10% difference in height

[ludtkemorgan]

@emilyjablonski I should have updated the PR description. Having every image be the exact same height ran into a few weird cases depending on the content. So instead it was decided that there is a little bit of wiggle room. The images can now be between 176px and 192px. That way it's more likely to align with the bottom of the content but the small content cards and large content cards don't have it aligned

[emilyjablonski]

Sounds great!