[Benefits Taxonomy] UX: Explore Editor UX for building a Benefit Detail page using Benefit Taxonomy

[jilladams]

Description

User story

AS A PO/PM
I WANT to see ideas for how Editors could leverage the Benefit Taxonomy to build Benefit Detail pages
SO THAT we can share with stakeholders for feedback.

Engineering notes / background

Analytics considerations

Quality / testing notes

Acceptance criteria

• Designed one or more UI mockups in Figma for the How to Apply flavor of Benefit Detail pages

[wesrowe]

Hi @davidmpickett, I assigned this to you just so it's on your radar. I need your help figuring out how to ticket this initial step toward using the Benefit Taxonomy to harden actual pages.

[davidmpickett]

I think this might be a little bit cart before horse. We haven't really established the Content Model for how the Benefit Taxonomy will interact with Benefit Detail Pages.

Is this ask to make the Benefit Taxonomy interact with the current (blobby) Benefit Detail Page Content Type? Because my understanding is that the Benefit taxonomy would be powering new hardened Benefit Detail Content Types (i.e. Eligibility, How to Apply etc.). And the VA Benefit Taxonomy would not interact directly with the unhardened Benefit Detail Page content type.

[davidmpickett]

https://app.mural.co/t/departmentofveteransaffairs9999/m/vagov6717/1660845137501/6eadf59a3f4d8dcd29da572a68115a22d6114fe4?wid=0-1677695595748

The dotted line going from the VA Benefit Taxonomy to new hardened Benefit Detail Pages (and not to the squishy existing ones) is the key distinction here. Trying to retrofit connections from this highly structured taxonomy to a entirely unstructured content type is essentially going to be a huge pain for very little gain. We need to instead pull out the types of content most likely to be compatible with the structure and focus on standardizing those and leave the rest of the mess as is for the time being.

[davidmpickett]

Relevant point of comparison here is VAMC Top Tasks

• main epic
• sub epic just for the editorial experience

[wesrowe]

Is this ask to make the Benefit Taxonomy interact with the current (blobby) Benefit Detail Page Content Type? Because my understanding is that the Benefit taxonomy would be powering new hardened Benefit Detail Content Types (i.e. Eligibility, How to Apply etc.). And the VA Benefit Taxonomy would not interact directly with the unhardened Benefit Detail Page content type.

We're definitely aligned. If there's any wording in the issue that misled you to think I was talking about hardening Benefit Detail in situ, feel free to edit. But I'm sure it can wait till our meeting next week.

[davidmpickett]

Note for next week - this other ticket is also connected to the larger vision here: #12839

[davidmpickett]

Relevant to the discussion is this overlap analysis
Benefits-Overlap Analysis.csv

• 48 benefits currently combine About, Eligibility, & Apply into a single page (1 FE page total)
• 5 combine About & Eligibility and have a separate Apply page (2 FE page total)
• 4 have three separate pages for About, Eligibility, & Apply (3 FE page total)
• 1 is an outlier that is kinda everything in one, but not exactly