Midpoint Review - IA Feedback - Public Websites, Resources and Support, Search experience enhancements, Phase 1

[erinrwhite]

Next Steps for the VFS team

• Assign this ticket to the team member(s) responsible for addressing feedback provided by Platform.
• Comment on this ticket:
  • If the Platform reviewer has any Thoughts/Questions that require responses.
  • When Must feedback has been incorporated. As appropriate, link to any other GitHub issues or PRs related to this feedback.
  • When Should/Consider feedback has been incorporated, or if any feedback will not be addressed. As appropriate, link to any other GitHub issues or PRs related to this feedback.
• Questions? For the most timely response, comment on Slack in your team channel tagging @platform-governance-team-members.
• Close the ticket when all feedback has been addressed.

Thoughts/questions

• Thanks for bringing this through the Collab Cycle! I am excited to see some work being done on the search/filter pattern.

Feedback

Practice areas will document their feedback on the VFS-provided artifacts following the Must, Should, and Consider Framework. Platform Governance reviewers may also provide additional notes that don’t comment on the artifacts themselves but are important for implementation (eg. engineering/coding notes).

• Should: study labels for "topic" and how it relates to "benefit" As folks with knowledge about how these tags are configured in Drupal, we know what the differences between these groups of filters are, but do these two labels make sense to Veterans and match their mental models? What language might be used to more clearly convey what the "topics" filter covers? I am excited to hear about your research on this!

• Should: on details page, display accurate filter type labels for chips Right now, the details page lists all relevant tags/chips as "Topics", but if we want to maintain consistency/clarity, those tags should be listed as belonging to their their filter group, i.e. audience, topic, or benefit.
  

• Consider: on search page, list filter type label on each chip (This might also be related to the "should" feedback bullet immediately before this one.) The search results page is displaying applied filters as chips. It could help a lot with clarity/cognitive load for these chips to include the type of filter they are in the text of the chip. So for example, instead of "Veterans", the chip could read "Audience: Veterans".
  

Governance team actions

• Format feedback as individual tasks (check boxes)
• Assign this ticket to the VFS team member that opened the Slack request
• Add the VFS team product label
• Add the VFS team the feature label (if applicable)
• Add the touchpoint labels
• Add the practice area labels
• Add the Collaboration Cycle initiative milestone