[EPIC] [Discharge Upgrade Wizard] Phase 2 Content updates

[FranECross]

Background

Ticket stubbed; need to flesh out. This is for Discharge Upgrade Wizard Phase 2 content changes.

Staging Review Issues

The child issues were noted by the Governance Team during the Staging Review and need CAIA / Design review. They are non-launch blocking, so I'm adding here as part of Phase 2.

User Story or Problem Statement

<As a _____, I need _____ so I can _____.>

or

<Problem description. How might we _____________ ?>

Affected users and stakeholders

• CMS_editors_of_X_product
• Developers of Y teams

Hypothesis

A hypothesis may depend on a spike ticket to be completed.

We believe that this_solution will achieve this_outcome. We'll know that to be true when this measurable outcome occurs.

Assumptions

• Tk
• Tk

(How will these assumptions be validated?)

Acceptance Criteria

• Testable_Outcome_X
• Testable_Outcome_Y
• Testable_Outcome_Z
• Requires KB article update

Change management triage

The change represented by this user story will:

• Be a site-wide change to appearance or key functionality (such as log-in process)
• Be a specific change that requires more than 30 minutes of work by a user to meet a publishing requirement
• Remove a piece of functionality (such as restricting editing functions, or “hardening”)
• Require action by some or all users by a specific deadline
• Change the front end and be highly visible to the public
• Noticeable performance improvements (publishing speed, predictability)

If you selected an item above, use the Change Management Runbook to create a CM epic and associated tickets.

If you did not select an item above, update issues/PRs in GitHub but don’t plan for change management.

Design principles

Veteran-centered

• 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.
• 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.

Runbook