Additional product or business considerations from stakeholders.
Acceptance criteria
[x] Request submitted to Design Systems
[ ] Updates are reflected in the Design System
[ ] Reviewed by UX Team
[ ] Reviewed by PMs
[ ] Reviewed by CAIA (logged-out website content only)
How to configure this issue
[ ] Attached to a Milestone (when will this be completed?)
[ ] Attached to an Epic (what body of work is this a part of?)
[ ] Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
[ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
[ ] Labeled with Type (bug, request, discovery, documentation, etc.)
kdmeg-bluetiger
commented
1 month ago
Audience
Who is this content for?
CAIA / Design Systems / Internal VA teams
Purpose
What will this content help the audience do? Use verbs to explain the purpose of the content.
Used as a starting point for banner message about sign-in issues on VA.gov.
Brief description
What is the request and where will the content be published?
Update the existing language to include our 4th CSP: Login.gov. This applies to scheduled downtime notifications and unscheduled downtime notifications for the sign-in page.
Content design tasks
Documentation
Related artifacts
Chat with team in #identity-ux
Product notes
Additional product or business considerations from stakeholders.
Acceptance criteria
How to configure this issue
product support,analytics-insights,operations,service-design,Console-Services,tools-fe)backend,frontend,devops,design,research,product,ia,qa,analytics,contact center,research,accessibility,content)bug,request,discovery,documentation, etc.)