Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design: create page-specific banners for manage.get.gov #2495

Open
3 tasks
vickyszuchin opened this issue Jul 24, 2024 · 0 comments
Open
3 tasks

Design: create page-specific banners for manage.get.gov #2495

vickyszuchin opened this issue Jul 24, 2024 · 0 comments
Labels
content issue is just content changes, generally no code design issue is for the design team refinement

Comments

@vickyszuchin
Copy link

vickyszuchin commented Jul 24, 2024

Issue description

If the registrar is unavailable, we should inform users on manage.get.gov. A banner to communicate the situation on affected pages will be helpful. Currently, we do not have a page-specific banners for manage.get.gov. We should create page-specific banners that to communicate any production issues (for errors and down for maintenance ) that may result in registrar being unavailable.

Acceptance criteria

  • Determine the pages that need a page-specific banner
  • Define sample content for boilerplate page-specific banner for re-use (eg., date/time placeholder, create one for maintenance, degraded performance, outage, etc.)
  • Create dev ticket for implementation, if needed

Additional context

No response

Links to other issues

Related to:

@vickyszuchin vickyszuchin added design issue is for the design team content issue is just content changes, generally no code labels Jul 24, 2024
@PaulKuykendall PaulKuykendall moved this from 👶 New to 🍦 Backlog in .gov Product Board Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content issue is just content changes, generally no code design issue is for the design team refinement
Projects
Status: 🍦 Backlog
Development

No branches or pull requests

2 participants