Skip to content

[BLOCKED] BE: Benefit Hub teaser / label: document or resolve dual source of truth for copy #14027

Open
@jilladams

Description

@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:
#13955 (comment)

  • 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:
image

  • 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
  • [ ]

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Benefit hubsCMS managed product, Public Websites teamBlockedIssues that are blocked on factors other than blocking issues.CMS designDesignCMS team practice areaDrupal engineeringCMS team practice areaNeeds refiningIssue statusPublic WebsitesScrum team in the Sitewide crewUXVA.gov homepageCMS managed product owned by Public Websites teambackendsitewide

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions