User Story: create temporary 'informative status' for site content changes

[dmvancura]

As a [current partner who uses notify.gov],

I want [to be informed on notify.gov of structural and content changes],

So that [i know what content (therefore information) is different and that these changes are on purpose].

Detailed condition or criteria that must be met for the user story to be considered complete.

Implement an 'informative status' component on the dashboard that has a label and descriptive sentence

List of specific tasks or sub-tasks that need to be done to implement the user story.

• review informative status message copy
• receive approval of copy for the informative status
• use USWDS informative status 'standard alerts' component

List any dependencies that need to be resolved before starting or completing this user story.

Dependencies – the using notify and best practices content needs to go live with or just before this informative message status component

Any additional information or context that might be useful for the team.

See message copy for review in site messages copy doc

[dmvancura]

mornining @CathyBeil, this ticket is to create an informative status component to place verbiage letting the users know that the content behind the login is changing. it should go out sometime before all of the Using Notify and Pricing related information goes out. I wanted to make sure you agree with this. thanks!

[CathyBeil]

This is fine, I'm neutral about its importance for content like this. We know partners want advance notice if dashboard/activity/send report pages change, but these I figure they'd discover on their own regardless and shouldn't impact any of their automations. Fine to let them know though!

[dmvancura]

i wondered similar, i.e., whether this content change would confuse or disorient their use of the product. knowing the workflow did receive a11y compliant updates, this is in response to that. we could have the informative status set up in staging so we are able to use it in the future, if not for this update. note: content hasn't been finalized/reviewed for this, but it has been written for consideration