Removing Covid status and associated messaging and content modifications

[dsinla]

Background

After research and readout, it has been decided that Covid status will be removed. We will want to

• modify the editor UI to remove current Covid status option
• work with Content team to develop nationalized text for Covid status from which editors can select
• determine how best to present the Covid text in the UI (with an eye towards making it generic, what about Monkeypox? What about hurricanes?),
• train/document best practices for editors on the new UI
• remove Covid status from the CDW Database (send null?, adjustments to operating status more_info 300 )
• remove Covid status from the Facility API

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 _thissolution will achieve _thisoutcome. 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:

• [x] 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
• [x] Change the front end and be highly visible to the public
• [ ] Noticeable performance improvements (publishing speed, predictability)

If you selected an item above, open a new issue using the change management template.

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

## Labels (You can delete this section once it's complete) - [x] Issue type (red) (defaults to "Epic") - [ ] CMS subsystem (green) - [ ] CMS practice area (blue) - [x] CMS workstream (orange) - [ ] CMS-supported product (black) ### CMS Team Please check the team(s) that will do this work. - [ ] `Program` - [ ] `Platform CMS Team` - [ ] `Sitewide Crew` - [ ] `⭐️ Sitewide CMS` - [ ] `⭐️ Public Websites` - [x] `⭐️ Facilities` - [ ] `⭐️ User support`

[ContentBrewmaster]

@dsinla wondering how this epic overlaps with 9096?

[dsinla]

Good point @ContentBrewmaster. I had assumed a narrower scope for 9096, but it looks like it encompasses what I was trying to represent here. I will close as dupe.