Drupal: Add VetCenter Banner Image to VetCenter Centralized Content

[Agile6MSkinner]

Add VetCenter Banner Image to Drupal as Centralized Content

Description:

To support the differentiation of Vet Centers from VA Medical Centers, we need to add the approved VetCenter banner image to Drupal as centralized content. This will allow us to consistently use the image across all Vet Center facility pages.

Vet Center banner

Acceptance Criteria

• 1. The VetCenter banner image is uploaded to Drupal's media library as embedded image
• 2. Update vet center facility content type adding banner image from centralized content
• 3. VetCenter banner image does not show on node edit or node view We will show this field, per comment.

[Agile6MSkinner]

Hey team! Please add your planning poker estimate with Zenhub @davidmpickett @dsasser @omahane @jv-agile6

[aklausmeier]

@Agile6MSkinner This work is blocked may be further informed by design revisions in #18389

[davidmpickett]

@aklausmeier I thought we agreed we weren't waiting for additional stakeholder feedback before moving forward with shipping small improvements to Vet Centers.

In story mapping earlier this week @Agile6MSkinner made a product call to go forward with the logo in order to start delivering value rather than trying to do the image exploration

[aklausmeier]

stakeholder has requested we explore an alternative image solution over a logo, also stated in design revision ticket, likely there will be an image here but it's not confirmed what it will be

[davidmpickett]

@Agile6MSkinner @jv-agile6 @jilladams @mmiddaugh - I would recommend pulling this ticket out of sprint and marking as blocked

I just got out of a meeting with Amanda and Jordan. @aklausmeier emphasized that the stakeholders were have not approved moving forward with the logo. They want to first explore the image approach and only use the logo if that is untenable.

If we go with the image route, it's possible that this ticket would be unchanged aside from it being one national image rather than a one national logo, but there's also the possibility that we might need to support images specified at regional / local level.

[omahane]

@davidmpickett

but there's also the possibility that we might need to support images specified at regional / local level.

Does that mean an image for the main Vet Center that would pertain to it and other facilities?

[jilladams]

Making the sprint change, so we don't churn.

[jilladams]

Scrum discussion: https://dsva.slack.com/archives/C079GFKN50D/p1721857502492419?thread_ts=1721857395.422269&cid=C079GFKN50D

[Agile6MSkinner]

@thejordanwood Please add the image to this story.

[omahane]

@jilladams @davidmpickett @Agile6MSkinner @mmiddaugh I looked at this last night. I believe, there's no way through the UI to populate the default content without showing the field on node:edit (at least). I'm wondering what the reasoning is behind not showing the image, as we try to mirror the FE as much as possible normally. In any case, unless we want to write custom code, we'll need to show the image to editors.

Were we to show them on node:view and node:edit, the fields would still be locked down like the other centralized content fields.

[aklausmeier]

Since it's not editable, I would advocate for showing it to mirror FE but not sure if there was reasoning behind the AC that I'm not aware of.

VetCenter banner image does not show on node edit or node view

[omahane]

Decision on AC about hiding the field on node:view and node:edit

Per conversation in Slack, we will show this field as uneditable. I will edit the ACs.

[omahane]

Confirmed that this is visible on prod: