DEV: System status page is linked in EN and FR from other Notify pages identified as relevant

YedidaZalik commented 1 year ago

Description

As a user, I need to be able to able to easily move between the system status page and other relevant pages so that I'm aware of incidents impacting security and service interruptions and can link them to Notify's practice of continuous security and our SLO's.

WHY are we building? Users reading the security statement should be able to review current and previous incidents. Users reading the SLA should be able to easily find the system status page. Users on the SLO and Contact us page should be able to link to the system status page to determine whether to ask for support.

WHAT are we building? Content to link the following pages to the status page:

Security statement
SLA
SLOs
Contact us

VALUE created by our solution Notify users can easily link between the pages that have content related to the system status page.

Documentation and Artifacts

System status page - possible links from other pages including policy doc review Good docs, figma mockups, ADRs, screenshots etc.

Acceptance Criteria

Given I'm reading about Notify's security and status, when I want to review the history of security related incidents and service interruptions, then I can easily find that information. Given I'm on the SLO or contact us page and deciding whether to request support, I can easily link to the status page to know whether Notify is already aware of/ working on my issue.

[x] Create content to link the relevant pages to the system status page
[x] Content localized to FR
[x] Content and menus updated in GC Articles. Using publication checklist
[x] Content updated in notification-admin (footer)
[x] Content updated in Security Statement EN/FR and last updated is updated
[x] Content updated in SLA EN/FR and last updated is updated
[x] Content updated in SLO EN/FR and last updated is updated
[x] Content updated in notification-admin (Contact Us page EN/FR) ~~- [ ] New feature update for status page (maybe)~~

Related Research Airtable records

(Ping Adrianne to add stuff here or find stuff yourself)

QA Steps

[ ] Tested in a realistic production scenario

YedidaZalik commented 9 months ago

Reviewed pages including policy docs to assess where to link to status page: https://docs.google.com/document/d/1Bl_I5bmDX9nVscP5IleOMzk66hMBXczGGYkkUuIb75Y/edit

yaelberger-commits commented 9 months ago

Hey team! Please add your planning poker estimate with Zenhub @YedidaZalik @adriannelee @amazingphilippe

YedidaZalik commented 9 months ago

Discussed accessibility recommendations for hyperlinks during design sync. Prepared link content (in purpled) for Melissa's review: https://docs.google.com/document/d/1Bl_I5bmDX9nVscP5IleOMzk66hMBXczGGYkkUuIb75Y/edit

YedidaZalik commented 9 months ago

@mtoutloff reviewed and have now sent to @mariesophiebezert for localization review After that will share with team

amazingphilippe commented 9 months ago

From the contact page, content will be added above the form. In the footer, the link will go under the contact form link, in the "support" section.

Figma prototype, but I don't think we'll need a dev-design review for this. Its pretty simple.

YedidaZalik commented 9 months ago

Marie-Sophie made some suggestions which I incorporated. Yael reviewed and said it could go to translation. Marie Sophie can use this page: https://docs.google.com/document/d/1FBBMq5F88tqlZuVCsSb0JFPpdW-tTbqJWcTOJ-4bwFc/edit

yaelberger-commits commented 9 months ago

Linked from footer

yaelberger-commits commented 8 months ago

yaelberger-commits commented 8 months ago

Updates with links to System Status page made to Security page, Service Level Agreement, and SLO page in both EN and FR and _last _updated__ date has been changed. Contact Us page still needs new content with link, and this card will need QA by someone other than me next

amazingphilippe commented 8 months ago

Looked at all the pages and made tiny changes

A leading space was hyperlinked in French links.
Fixed the list numbering on the SLA pages.

Otherwise looks good on the GCA pages.

For the contact us page, the translated screens are in Figma

We can tag the dev team to continue this story.

amazingphilippe commented 8 months ago

In staging, waiting for release, andrew QA'd

yaelberger-commits commented 8 months ago

Released this morning Yael QA'd in production

cds-snc / notification-planning