Drupal: Add "Mission Explainer" Content Block to VetCenter Centralized Content

[Agile6MSkinner]

User Story

As a content manager, I want to add a blue information box to Vet Center pages with editable content in Drupal so that I can provide consistent information across all Vet Centers.

Description

Add content blocks to VetCenter centralized content. The copy for the box will be editable in Drupal, but it will be the same for all Vet Centers.

Draft content for blue box

Content will be revised by CAIA, but first draft from department-of-veterans-affairs/va.gov-team#83961 (comment) is:

Title: Our services
Body:
We offer these confidential services at our Vet Centers:

• Mental health counseling and a range of other social and mental health services
• Referrals to a VA medical clinic or community provider for medication and other services
• Connections to more support in VA and your community

Note: You may be eligible for these services no matter your discharge status or eligibility for VA health care. And we won't share anything about you or the services you receive at a Vet Center without your permission.

ACs:

Preview Give feedback

1. 1. Add centralized content descriptor content block to VetCenter Centralized Content
2. 2. Add "Rich text - char limit 1000" content block to VetCenter Centralized Content
3. 4. Content block is populated with the following copy: @aklausmeier to provide the draft content
4. 5. Content block shows on node:edit and node:view(if low LOE) on VetCenter Content Type

QA

Preview Give feedback

1. Content block is editable by user with appropriate permissions on VetCenter centralized content.
2. Content block is not editable on VetCenter content type

Review

Preview Give feedback

1. Design review in PR environment for Helptext / field labels, etc., before merge

[Agile6MSkinner]

@omahane @dsasser mind taking a look at this and validating?

[Agile6MSkinner]

@aklausmeier @thejordanwood In order to get this across the line we need final copy for the blue summary box at the top of the VetCenter facility pages.

[aklausmeier]

@Agile6MSkinner Final copy will be provided by CAIA for blue summary box in the related CAIA ticket #83961.

@thejordanwood @davidmpickett We could go ahead and provide this request to CAIA. I wouldn't expect any additional stakeholder feedback on this area. If we do we can always make additional minor tweaks.

[davidmpickett]

Update from convo with @aklausmeier she is going to own making som revisions to the content and then providing copy to CAIA for their review.

[jv-agile6]

Moved ticket to in-progress. Reviewing scope and context.

[aklausmeier]

Draft copy below sent to CAIA, revisions are expected. For context, how this appears in Figma design.

Our services

We offer these confidential services at our Vet Centers:

• Counseling and a range of other services for individuals, families, and group sessions
• Alternative therapies and events may be offered such as art, equine, yoga, or fly fishing
• Connections to more support in VA and your community

Note: You may be eligible for these services no matter your discharge status or eligibility for VA health care. And we won’t share anything about you or the services you receive at a Vet Center without your permission.

cc @Agile6MSkinner

[jilladams]

@jv-agile6 I added an AC to this ticket to have Jordan (or Dave) take a look at your implementation in Tugboat, once it's in PR / before you merge. Many times we would have a design for the UI. In this case we didn't go that route, so we want to make sure that UX has eyes on it before we merge, for any feedback / changes.

cc @thejordanwood @Agile6MSkinner (based on thread with Amanda in Slack here)

[jv-agile6]

After much discussion the AC on this ticket has changed.

• "char limit 1000" for the rich text field is no longer a requirement for acceptance.

• A title field is an added requirement.

Discussions flushed out previous paragraph type - magichead_group that meets these requirements. I have added this paragraph block to the Vet Content Center on production.

[jv-agile6]

Error when running ddev pull va --skip-files

troubleshooting

[jilladams]

@jv-agile6 just noting that while Christian is out this week, @davidmpickett can help with any questions about the content / Drupal config side or clarify what you need to do with his feedback if you have questions, and @dsasser is your man for any Qs on the Pull request itself, CI test issues, etc.

[jilladams]

@jv-agile6 looks like this deployed today and is now live in prod.

On Centralized Content: Vet Centers
https://prod.cms.va.gov/node/16142/edit

On a Vet Center node:
e.g. https://prod.cms.va.gov/node/3788/edit

Noting: Copy in these screenshots differs from ACs on the ticket, due to feedback from Dave in the PR review. I did verify that placements in prod and copy match the PR feedback. If anyone has concerns about that, they can now make changes directly in the Production Centralized Content node. Closing!