-
Notifications
You must be signed in to change notification settings - Fork 70
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into VACMS-9919-fixes-visual-focus-on-node-edit-u…
…nlock-button
- Loading branch information
Showing
4 changed files
with
119 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,110 @@ | ||
--- | ||
name: Public Websites Epic | ||
about: A epic for the Public Websites team. | ||
title: "" | ||
labels: Epic, Public Websites | ||
assignees: '' | ||
|
||
--- | ||
|
||
## Top-line Description / Goal(s) | ||
|
||
|
||
|
||
#### Monthly project updates: | ||
|
||
--- | ||
|
||
## Headlines | ||
**VA stakeholders** - | ||
|
||
**OCTO lead** - Dave Conlon | ||
|
||
**Is this project tracked to an upcoming event or congressional deadline?** - | ||
|
||
## Details | ||
|
||
**Which OCTO team should do this and what is currently on their roadmap?** - Sitewide | ||
|
||
**Which OCTO priority does this work support?** - | ||
|
||
**What is the user impact and scale of impact?** - | ||
|
||
**Who would manage this product long term?** - Public Websites | ||
|
||
**How much leverage will this create to solve more problems in the future?** - | ||
|
||
**How great is the cost of inaction? (e.g., Can it wait? Must it be done by us?)** - | ||
|
||
--- | ||
## Business Case | ||
|
||
### 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 | ||
|
||
<link to any existing research or data supporting this> | ||
|
||
|
||
### 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](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/facilities/change-management) 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 | ||
<optional> | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters