Investigate prefillMessage component

[msbtterswrth]

Background

There exists a prefillMessage component that is considered a 'content component'. Currently this is meant to be used to pull in standardized static alert content for prefill alerts, though few forms are using it correctly (or at all).

We want to investigate it's usage and propose a path forward for it and it's VADS page. Those forms that are using this component often do so incorrectly and overwrite the default content anyways, so it may benefit us to remove the option for overwriting that, if the desire is to have consistent messaging across all form contexts.

We know that the prefillMessage component does NOT currently use the correct alert component, it's using a plain div with a blue background.

ACs

• We have documented all the forms using this component
• We have documented it's variations
• We have determined if we should keep the component as is or update it
• We have created follow up tasks to adjust our VADS guidance if necessary

[adamwhitlock1]

I have created a markdown file for my findings and suggested steps for standardizing the component.

https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/authenticated-patterns/engineering/169-PrefillMessage-platform-usage.md

[msbtterswrth]

Excellent work! Let's chat about this during refinement today and what our next steps are!

[beckyphung]

@msbtterswrth Given the findings, what is our recommendation for the prefill component page? Sounds like majority of teams are using this component.

[msbtterswrth]

I believe we decided to leave as is @adamwhitlock1 @bellepx0 can check me on that though