As we roll out CMS notifications, we should investigate all the possible triggers that prompt notifications can be put in place for iteration of the product. There are various ways that editors can be notified about tasks to be done.
As we think through these triggers, a path for remediation and clearing those triggers/flags/notifications is determined to reduce false positives and notification fatigue.
If you need to create a ticket for an existing trigger or proposed trigger for CMS notifications, use the template.
User Story or Problem Statement
As a CMS editor, I need to be notified about specific tasks to be done so I can complete an action so that I can be compliant with various VA standards for positive veteran outcomes.
As a Sitewide Crew member, I need a way to reach editors about tasks that should be completed or content to be corrected so that I can ensure a positive veteran experience.
Problem Description
How might we create specific triggers in the CMS for specific email notifications?
Affected users and stakeholders
CMS editors of all products
Helpdesk Support Team
Hypothesis
We believe that CMS notifications about editor actions will achieve broader compliance. We'll know this to be true when there are less 508 errors and higher rates of acceptance for the various Sitewide Crew products.
Assumptions
There will be ways to create triggers in the CMS for various editorial tasks
(How will these assumptions be validated?)
Acceptance Criteria
[ ] Triggers are identified
[ ] Process for requesting a new trigger is created
[ ] Path to clear each trigger is determined
[ ] Path to editor remediation is considered
[ ] Change management consulted
[ ] 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”)
[x] Require action by some or all users by a specific deadline
[ ] Change the front end and be highly visible to the public
EWashb
commented
8 months ago
Background
As we roll out CMS notifications, we should investigate all the possible triggers that prompt notifications can be put in place for iteration of the product. There are various ways that editors can be notified about tasks to be done.
As we think through these triggers, a path for remediation and clearing those triggers/flags/notifications is determined to reduce false positives and notification fatigue.
If you need to create a ticket for an existing trigger or proposed trigger for CMS notifications, use the template.
User Story or Problem Statement
As a CMS editor, I need to be notified about specific tasks to be done so I can complete an action so that I can be compliant with various VA standards for positive veteran outcomes.
As a Sitewide Crew member, I need a way to reach editors about tasks that should be completed or content to be corrected so that I can ensure a positive veteran experience.
Problem Description
How might we create specific triggers in the CMS for specific email notifications?
Affected users and stakeholders
Hypothesis
We believe that CMS notifications about editor actions will achieve broader compliance. We'll know this to be true when there are less 508 errors and higher rates of acceptance for the various Sitewide Crew products.
Assumptions
(How will these assumptions be validated?)
Acceptance Criteria
Change management triage
The change represented by this user story will:
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.Labels
(You can delete this section once it's complete)
CMS Team
Please check the team(s) that will do this work.
ProgramPlatform CMS TeamSitewide Crew⭐️ Sitewide CMS⭐️ Public Websites⭐️ Facilities⭐️ User support