Create VADS draft governance content

[msbtterswrth]

User Story

As a member of the AEDP team I need to create content for the VADS page so that teams can understand the new pattern and it's guidance.

Background

Page content should follow the guidelines found at: https://github.com/department-of-veterans-affairs/vets-design-system-documentation/blob/main/src/_patterns/template.md

A good example of a more recently updated pattern is https://design.va.gov/patterns/ask-users-for/email-address, we should be sure reference this as a guide.

ACs

• [x] Determine which component or other pages need to be updated
• [x] A template has been created with formatting and an outline for the VADS page
• [x] VADS code contribution path

[beckyphung]

Ask users for… Email address is an example of one of the more updated patterns. I know it's "more updated" because it links to the web-component pattern available in the Forms library in the Code usage section. Mentioned this in our call earlier today

[msbtterswrth]

I have begun a draft guidance doc in our vagov-team repo

[msbtterswrth]

We are recommending removing the following page (to be absorbed by a new page):

• https://design.va.gov/components/form/prefill

Updating the following page (to remove prefill alert related things):

• https://design.va.gov/patterns/help-users-to/know-how-their-information-is-updated
• https://design.va.gov/components/alert#sign-in-to-start-your-application---pre-fill

And creating a new page:

• https://design.va.gov/patterns/help-users-to/know-when-their-information-is-prefilled (does not exist yet)

[beckyphung]

@msbtterswrth What are we expecting happens to Know how their information is updated? Maybe this page could be the new page for #22 Update prefilled information?

[bellepx0]

Created a Discovery doc for the Code Usage section

The doc also shows examples of how this pattern would be presented in Storybook if we choose to go that route.

[msbtterswrth]

@msbtterswrth What are we expecting happens to Know how their information is updated? Maybe this page could be the new page for #22 Update prefilled information?

Yes exactly. We'll update it for now to remove the alert directions, but will eventually replace it with "Know how to update prefilled information".

[ChristineRoseSteiffer]

Since we are working through our study synthesis next sprint, the draft content for many of these ACs will come along with that. Should we move those tasks into a story for next sprint, or carry this whole ticket over? It seems like a lot of good work has already been done here so I'd be more inclined to do the first option.

[msbtterswrth]

Agree, will split out a story for the actual content drafting for next sprint in #109. We have completed the following in this sprint:

• created a draft artifact for contributing (formatting and outline)
• created documentation for how to submit code along with our guidance
• determined which pages need to be updated, added or removed

[beckyphung]

@msbtterswrth @bellepx0 When we say Prefill pattern in this code usage GitHub doc, which pattern are we referring to?

• 17 OR

• 22

[msbtterswrth]

This task (and it's documentation) refer to #17.