BE: Benefit Hub teaser / label: document or resolve dual source of truth for copy

[jilladams]

Description

User story

AS A Content team editor I WANT to clearly understand where edited content appears in VA.gov SO THAT I know what I'm modifying.

Text entered in Benefit Hub Landing Pages UI in Drupal was originally used on old homepage. However, since then these same fields were added to other products. And now, with the changes to the homepage (2023), they are no longer used on the homepage Benefit Hub list (now built from a menu). Other places they're used are detailed here: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/13955#issuecomment-1574385183

• E.g., they're used to populate a list of links on a PACT Act page - on the FE under VA Benefits heading, at the bottom of the main content section, right above "Need more help".

Screen shot

Drupal edit screen for the Education and Training landing page:

• The text entered here is still used, but not on the home page.

Suggested approach

seems like what we have here is design debt – the fields are not being used how they're labeled in the CMS UI. Solution might be to rename the field set?

Proposed change:

Field set heading Old: Home page listing New: Brief listing? Brief summary?

Help text below heading Old: Add information for the Benefit Hub's listing on the VA.gov home page New: Add information for this hub to be displayed when it's included in a list.

@DanielleThierryUSDSVA, do you have an opinion about what these blurbs could be called without referencing the Homepage? (See image in ticket description for context.) The comment above this one has examples of where else these short names and descriptions are used.

Engineering notes / background

Analytics considerations

Quality / testing notes

Acceptance criteria

Consider

• Design / Accessibility reviews
• Collab cycle requirements
• Device sizes (mobile first)
• Documentation updates / Change management < - Content model documentation
• Testing notes

• [ ]

[wesrowe]

@DanielleThierryUSDSVA, note that there is a question for you in the description of the ticket. The question we're trying to answer: "What should the Benefit Hub Landing Page fields currently called 'Home page listing' actually be called?" See ticket description for full version and context.

[FranECross]

@DanielleThierryUSDSVA Just pinging you regarding the question above and in the description. Thank in advance! cc @jilladams

[jilladams]

Blocked on CAIA input. If we want to get this moving, we likely need to schedule time to meet synchronously to discuss.

[DanielleThierryUSDSVA]

Hi there! Sorry for delay in answering this. If I'm understanding the issue correctly, I think we'll likely want to do the following:

• Rename these to "Brief benefit hub landing page description"
• Have a single source of truth for the description to make it consistent wherever it appears

[jilladams]

We could go ahead and rename the field from "Home page listing" to "Brief benefit hub landing page description", but Danielle is also flagging a deeper problem: we don't want dual sources of truth. CAIA would prefer a one-stop to update Benefit description, everywhere it appears. (Reasonable.)

So to recap for @FranECross 's sake:

• Benefit hubs have 2 fields: Hub Label and Hub Description. Those fields are used to describe benefits on multiple templates throughout the site. They appear in the Front-end in the "Related Benefit Hubs" section of each /resources/ article type, e.g. under the VA Benefit section at the foot of content here
• Homepage These fields also used to power the "Explore VA benefits and health care" section of the homepage.
  • Last year when we rebuilt the homepage, we stopped using these fields and converted that section to be powered by a Drupal menu.
  • This was done primarily because of the addition of the "VA department information" item there, which is not a Benefit Hub. We opted to convert to a menu, rather than trying to wedge that new item into the Hub content type or hacking it onto the end of the list powered by Hub fields.

So: in order to resolve multiple sources of truth, we will need to figure out what to do about that current conundrum. (Danielle, holler if you have additional questions/notes based on that summary.)