Content review of Benefit Taxonomy MVP

[strelichl]

Issue Description

Content review and testing of Benefit Taxonomy MVP in Drupal, to gather feedback for Public Websites team:

• populating content
• adding and editing terms
• feedback on model and on editor experience
• think about what we will use this for

From the team: The tool is in prod now, they've updated it so we can make terms ourselves.

Tool: https://prod.cms.va.gov/admin/structure/taxonomy/manage/va_benefits_taxonomy/overview

Video of Laura's overview of the tool

---

Tasks

• [ ] CAIA content workshop to test drive the tool (Lily)
• [ ] Feedback and questions compiled (Lily)
• [ ] Review shared with stakeholders (Lily)

Acceptance Criteria

• [ ] Tool tested and feedback provided

---

[strelichl]

Capturing questions from the team's first working session:

• Can we watch an end-to-end example of someone filling out a structured content node, and then using it?
• What are the best use cases? What are cases when we shouldn't be using it?
• Is it possible to add in a structured content node and then tweak it for that local specific case? Or is the content fixed?
• Will this work only in Drupal? (not Chatbot, Voicebot, or other comms things?)
• Do we have to maintain 2 separate nodes — one for the structured benefit content, and one for the main benefit detail page?
• is the idea that we would migrate content from our current Drupal pages to these pages, eventually?
• Could it ever be used for authenticated content?
• For Danielle: how does this fit in to big picture Public Websites changes?

[strelichl]

@laurwill do you think we can close this

[laurwill]

I think OCTO was working on this before bringing us in, but I honestly can't remember — maybe check with Danielle and Randi whether there's still work for us to do here