Update 6102 notifications email based on research findings and feedback

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

Editor-centered management for Veteran-centered content.

https://prod.cms.va.gov

GNU General Public License v2.0

98 stars 68 forks source link

Update 6102 notifications email based on research findings and feedback #12391

Closed EWashb closed 1 year ago

EWashb commented 1 year ago

Background

Based on feedback received during 6102 notifications research, areas of opportunity were identified for updating the notifications email.

Acceptance Criteria

[x] Remove 30/60/90 day outdated differential on the email
[x] Combine outdated content into one section
[x] Provide a link to the CMS where editors will see their outdated content list
[x] Add "Action Required" to subject line
[x] Accessibility review
[x] Create tech implementation ticket for dev build

BlakeOrgan commented 1 year ago

I've made updates and added a couple questions to the Figma file.

laflannery commented 1 year ago

Based on some technical updates for MVP @laflannery and possibly @EWashb will be updating designs for V4

@EWashb will also add some more detailed notes regarding MVP

laflannery commented 1 year ago

@EWashb Can you take a look at V4 when you get a chance? https://www.figma.com/file/fQl2Y2k9MDA2dc0xViC645/6102-Notification-Email?node-id=0%3A1&t=RbphvYJX8mwKTfUd-0

There were only a couple updates to make this generic - so I may have missed something. Also I have a couple questions in there

EWashb commented 1 year ago

After speaking with devs, it was determined that the outdated content view within the email would be very heavy lift that would require dymanic coding for each permission level. Also, showing the outdated content directly in the email would not be the source of truth. We should always lean into the current outdated content view to be the source of truth. However, we can update the outdated content report to show only 25 at a time. Those 25 (due to pagination) will, by default, always be the most outdated and what editors should focus on.

We can iterate on the email as needed, but to ensure that all appropriate editors are notified AND we aren't overcomplicating the design, we have landed on this design below. I need to determine if two links are really needed because they essentially take you to the same place.

EWashb commented 1 year ago

Email design

EWashb commented 1 year ago

shared final design with Dave via Slack and Email on 2/23