Design an MVP foundation for migrating content for "Pilot Offices"

Background

3-4 Pilot Offices will be used to guide the Offices MVP design.

User Story or Problem Statement

Design should include content strategy/types and UX design.

Affected users and stakeholders

No existing users affected

Hypothesis

Assumptions

(How will these assumptions be validated?)

Acceptance Criteria

[ ] Testable_Outcome_X
[ ] Testable_Outcome_Y
[ ] Testable_Outcome_Z
[ ] Requires KB article update

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.
[x] Content lifecycle governance: Produce tools, processes and policies to maintain content quality throughout its lifecycle.

Editor-centered

[x] 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.
[x] 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

## Labels (You can delete this section once it's complete) - [ ] Issue type (red) (defaults to "Epic") - [ ] CMS subsystem (green) - [ ] CMS practice area (blue) - [ ] CMS workstream (orange) - [x] CMS-supported product (black) ### CMS Team Please leave only the team that will do this work selected. - [ ] `Platform CMS Team` - [x] `Sitewide CMS Team` - [ ] `⭐️ Content ops` - [ ] `⭐️ CMS experience` - [x] `⭐️ Offices` - [ ] `⭐️ Product support` - [ ] `⭐️ User support`

department-of-veterans-affairs / va.gov-cms