"New features" page Release 2

[sastels]

Description

As a service owner, I need to know what changes to Notify have been made or are upcoming so that I can plan my use of Notify accordingly.

WHY are we building?

• We have a mvp experience released and we want to improve... visibility | findability | interaction | process | scope for upcoming features?

WHAT are we building?

• [x] Link "new features" page from footer, or other relevant places
• [x] Have a way to find and manage older updates
• [x] Link the other new features on the dashboard banner, once we have other new features
• [ ] Build a sign-up form for our clients if they want to receive updates by email
• [ ] Improve on the bilingual content creation experience
• [ ] Criteria to determine when we post a product update

VALUE created by our solution

• Increased transparency, without annoying users with communications they did not sign up for

Acceptance Criteria** (Definition of done)

We have and maintain a "New and upcoming features" page

• [ ] Generate appropriate log messages so that executions of this feature can be tracked
• [ ] Can misuse of this feature cause harm? If yes, create an alert

QA Steps

• [ ] Tested in a realistic production scenario
• [ ] user from https://cds-snc.freshdesk.com/a/tickets/9632 notified

Note: asked for in ticket https://cds-snc.freshdesk.com/a/tickets/9632

[foudamo]

Adding on behalf of @YedidaZalik: The pop up for the recent policy change of Lastpass (first image) seems like a good inspiration for how to communicate a policy change to users / customers. Adding here as inspo. I like two things about it:

• the simple language of the pop up when you first sign in, with the option to link to the policy.
• another note, good to have the pop up at least 2 times or on a second day for folks who opt out the first time

Link to the policy itself: https://www.lastpass.com/legal-center/privacy-policy?utm_source=pendo&utm_medium=ipm&utm_campaign=2023-07-01-multi-multi-global-en-global-privacy-policy+updates&utm_content=privacy-policy-update

[yaelberger-commits]

@adriannelee should we turn this card into Product Updates v2?

[yaelberger-commits]

@amazingphilippe and @yaelberger-commits will meet to further refine this card with new scope given decision was made not to proceed with CMS and banner

[YedidaZalik]

When we start work on this, this document, linked to the story refinement invite, may help us to develop criteria for when to post https://docs.google.com/document/d/150owimsQk5xy-AEwqLRu1GmVUcl3YK1Ns0YltWUIxWE/edit#heading=h.vyfm13e2g6ov (edited)

[yaelberger-commits]

Drafted some new content for New Features here for recent features we've released or are preparing to release. Keenan and I will work together on these moving forward with some reviews from content designers https://docs.google.com/document/d/167NQm_13ctA-2AqThtsp7o8NI8lU1hpANnMZY6uoxks/edit

[yaelberger-commits]

Keenan reviewed. Yedida also suggested edits. I accepted changes. Drafts are now ready for FR content review/translations when @mariesophiebezert has capacity

[yaelberger-commits]

3 new features to post about

1. Changes to the System Status page and component checker
2. New Register for a demo flow
3. Self-Serve Branding

[YedidaZalik]

French content is ready https://docs.google.com/document/d/1wjxZ5sumkgDNxQzbUIfPccbZEVUjNFxXoKGQ_FVfeEk/edit#heading=h.gjdgxs

[yaelberger-commits]

First publishing only for System Status and Register for a Demo

[yaelberger-commits]

We will bring this back into the backlog to complete the rest of the tasks