[Aging Content] Launch Plan

[jilladams]

We can merge MVP without it being launched. The configurations can merge, disabled. Would then need to enable the configuration for notifications to go out in prod.

Automated testing

• [ ] [Aging Content] Write unit tests for the notifications framework (& full-width alert/banner if applicable) #18005

Developer-facing Configuration Fields Text Updated

• [ ] #18019

User Testing

Needs a high level product review of user stories, to confirm paths. Requires an environment from which to configure / send mail. Tugboat sends mail to a dashboard. Staging may or may not send mail, we need to verify.

• [ ] PM to draft QA plan for documentation (Configuring, and verifying emails are sent / received)
• [x] QA is performed & PM has signed off

Documentation

We need instructions for how to use.

• [ ] [Aging Content] Create an editor-facing KB article for Aging Content Notifications #18006
• [ ] [Aging Content] Draft or edit existing Architectural document #18007 -- CMS and Sitewide contributor engineer / Product facing

[FranECross]

@dsasser I've created three tickets and added links to this ticket: KB article, architectural document (product-facing), and unit tests. I'll work on the QA tests / ticket today or tomorrow as well. Thanks! cc @jilladams