[EPIC] [Find a Form] Find-a-form support

[wesrowe]

Background

User Story or Problem Statement

As a Veteran, I need the Find-a-form search to work for all forms so that I can interact with my VA benefits as efficiently and accessibly as possible.

Affected users and stakeholders

• Veterans
• Editors/maintainers of Forms

Collateral

• VA Forms flow topic dive - Youtube video
• Modern epic: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/3232 for improvements to the system
• "Find a form" labeled issues
• Test cases to test against whenever code is altered

Notes / History

• Marci McGuire - former PM on Forms, now Platform Crew/HMI Spike Team [Ad Hoc]
• Label: va-forms or "Find a form"
• Additions will be per-audience/product – e.g., maybe specific tools for VAMC editors
• Topic dive describes cases where Editors may upload new versions of a form rather than editing existing versions, leading to duplicates, version issues

Design principles

Veteran-centered

• [x] Single source of truth: Increase reliability and consistency of content on VA.gov by providing a single source of truth.
• [ ] Accessible, plain language: Provide guardrails and guidelines to ensure content quality.
• [ ] Purposely structured content: Ensure Content API can deliver content whose meaning matches its structure.
• [ ] Content lifecycle governance: Produce tools, processes and policies to maintain content quality throughout its lifecycle.

Editor-centered

• [ ] Purpose-driven: Create an opportunity to involve the editor community in VA’s mission and content strategy goals.
• [x] Efficient: Remove distractions and create clear, straightforward paths to get the job done.
• [ ] Approachable: Offer friendly guidance over authoritative instruction.
• [ ] Consistent: Reduce user’s mental load by allowing them to fall back on pattern recognition to complete tasks.
• [ ] Empowering: Provide clear information to help editors make decisions about their work.

Labels

(You can delete this section once it's complete)

• [x] Issue type (red) (defaults to "Epic")
• [ ] CMS subsystem (green)
• [ ] CMS practice area (blue)
• [x] CMS workstream (orange)
• [ ] CMS-supported product (black)

CMS Team

Please check the team(s) that will do this work.

• [ ] Platform CMS Team
• [ ] Sitewide program
• [ ] ⭐️ Sitewide CMS
• [x] ⭐️ Public websites
• [ ] ⭐️ Facilities
• [ ] ⭐️ User support

[FranECross]

Added associated tickets as sub-issues so they'll display on the epic on the new board.