Align content on VADS for experimental design with new user flow

[allison0034]

User Story

As a VFS team member, I want to have up to date documentation to reference, so that I know how to follow the experimental design process.

Assignee: @briandeconinck
Peer Reviewer: @allison0034

Description

Governance team has recently published a new flow to the VADS that steps through the experimental design process. The new flow is up to date and accurate, however the content supporting these pages does not align.

The purpose of this ticket is to update the content on all live pages shared below, if necessary, to reflect the updated Experimental Design flow.

Once all content is up to date, @naomimarcussen has recommended that Governance announce these changes at the Design sync meeting on Mondays.

Impacted Artifacts

Live pages

• Contributing to the design system
• Experimental components and patterns
• Suggest an addition or update
• Add a component or pattern once approved

Drafted pages

• Draft - Contributing to the design system
• Draft - Experimental components and patterns
• Draft - Suggest an addition or update
• Draft - Add a component or pattern once approved

Tasks

• Review all live pages to determine where content is out of sync.
• Make updates to the content to align with the Experimental Design flow
  • Note: if you are uncertain on any preferred wording, please connect with Matt Dingee for his input.
• Peer review changes
• Once content is aligned, submit pull request to DST for approval/merge
  • PR 3616

Peer Review

To be completed by peer reviewer

• User story and acceptance criteria are met

Acceptance Criteria

• Governance has updated the experimental design pages on VA Design System to align with the Experimental Design flow.

Team Notification

• Slack post on #platform-governance-team
• Presentation at Weekly Initiative Meeting
• No notification needed (for Governance, however notification for design community would be preferred)

How to prepare this issue

Refinement

• Ticket has user story, description, tasks, and acceptance criteria
• Ticket has been sized
• Once all above items are checked, add the 'Ready' label.

Planning

If this ticket is picked up from the Backlog mid-sprint, connect with Shira to ensure the below items are completed correctly

• Ticket has been discussed as a team at Planning
• Ticket has been assigned to appropriate initiative or quarterly epic
• Ticket has been assigned to a Sprint
• Ticket has been moved to the Planned pipeline in the Governance team board
• Ticket as an assignee and peer reviewer

[shiragoodman]

Brian was out sick Nov 13-15. Since Collab Cycle reviews are the priority, I have directed him to work on catching up with Collab Cycle work. This ticket will not be picked up this sprint and will be moved into the next sprint.

[shiragoodman]

reassigned this to the appropriate tech debt initiative.

[shiragoodman]

@briandeconinck is this work in progress? We're 3 days into the sprint and I would've expected this work to have started by now. Please lmk.

[briandeconinck]

Yes! Sorry, updating the ticket status and updating with progress made so far right now.

[briandeconinck]

Commenting with an end-of-sprint update: Drafts in progress, almost done; work will carry over into next sprint but should be wrapped up pretty soon after.

[briandeconinck]

@allison0034 Draft content changes are ready for review!

• Draft - Contributing to the design system
• Draft - Experimental components and patterns
• Draft - Suggest an addition or update
• Draft - Add a component or pattern once approved

Note that I've made no changes to the Experimental components and patterns page --- but please let me know if I missed something in there that needs updating. (I may include updates to the heading structure in my PR, but that's just me playing accessibility specialist.)

On the other three pages, I've included comments describing the changes I made (eg. new section here, existing content with minor revisions there, etc) plus a question or two for you.

Thank you!

[allison0034]

@briandeconinck I made some comments. Let me know if you want to chat.

[briandeconinck]

@allison0034 I think I've addressed all of your comments. Would you give them another look?

• Draft - Contributing to the design system
• Draft - Experimental components and patterns
• Draft - Suggest an addition or update
• Draft - Add a component or pattern once approved

[allison0034]

I think this looks good, should you run it by Matt?

[briandeconinck]

Per @shiragoodman, created PR 3616

[shiragoodman]

@briandeconinck looks like Matt left a couple comments in the PR. I approved, however please still address his comments. I will check in on this tomorrow during standup.

[briandeconinck]

Matt's comments have been addressed and @allison0034 has given her 👍 for those edits. Waiting on Matt to approve then changes will be merged in.

Per @shiragoodman in Slack, closing this ticket as complete.