Consider: Harden "Featured Content" field on Benefit Detail Pages to match Summary Box component

[davidmpickett]

Status

[2024-08-09] [Fran] Currently on hold/blocked. More info for this ticket will shake out in the content modeling effort; not ready for refinement yet; possibly a Q4 endeavor.

Background

Currently the "Featured Content" field on Benefit Details Pages nodes allows for a wide variety of input. It allows two paragraph types: Rich Text, and Page-specific Q&A. Since the Rich Text paragraph doesn't use the Rich Text Limited formatter, editors are able to enter headings throughout. The Page-specific Q&A allows for even more wild cards with tables and process lists and React widgets

This means the data being passed to the Front End is not going to be reliably parsable. Which means we can't adopt a standard DST component (summary box) and are instead stuck in Imposter land.

Originally raised in #17187

Drupal Config

Editor UX

Examples

• https://www.va.gov/health-care/about-va-health-benefits/dental-care/
• https://www.va.gov/pension/how-to-apply/
• https://www.va.gov/health-care/health-needs-conditions/health-issues-related-to-service-era/gulf-war/

[davidmpickett]

Exploring this problem space may also help give clarity on this question #18322

[FranECross]

@davidmpickett Is this a UX or a Drupal engineering ticket? I was going to move it to Next refinement, but I'm not sure who will be working on it or what the ask it. 😁 Thanks!

[davidmpickett]

@FranECross This is a pretty loose ticket stub. Probably need more dedicated prefinement/discovery from Content Modeling before it'd be ready for group refinement.

This probably should be discussed in the larger context of Benefit Detail page hardening when that gets prioritized. Maybe a Q4 consideration.