Include banners in UX guidelines for notifications #8493

Activity

1. Nick Trogh (ntrogh)

   self-assigned this

   on Jun 18, 2025
2. Nick Trogh (ntrogh)

   added

   API documentationAPI reference issuesAPI reference issues

   on Jun 18, 2025
3. Nick Trogh (ntrogh)

   assigned

   Kaitlin Brooks (kkbrooks)

   on Jun 18, 2025
4. Joanna Oikawa (jo-oikawa)

   unassigned

   Kaitlin Brooks (kkbrooks)

   on Sep 22, 2025
5. DakotaB75 commented on Dec 20, 2025

   

   Dakota Bazan (DakotaB75)

   on Dec 20, 2025

   Contributor

   More actions

   It looks like this issue is about expanding the UX guidelines around notifications, specifically banners, but the intended scope isn’t entirely clear yet.

   To help move this forward, it might be useful to clarify:

   • whether this is meant to cover all banner types (info, warning, error, success) or only system-level notifications
   • if the guidelines should focus purely on visual/layout aspects, or also include behavior (dismissal, persistence, stacking, timing)
   • how banners differ from other notification patterns already documented (toasts, dialogs, status messages)

   Once the scope is clear, I think a structured guideline could work well, for example:

   • When to use a banner vs other notification types
   • Accessibility considerations (focus, screen readers, color contrast)
   • Interaction patterns (auto-dismiss vs persistent, user actions)
   • Do / Don’t examples

   Happy to help refine the scope further if needed.
6. cmakinet commented on Jan 27, 2026

   

   Cherehani Makigo (cmakinet)

   on Jan 27, 2026

   More actions

   Hi Open Source Maintainers on GitHub [moved] (@maintainers),

   I'mCherehani Makigo, a student contributor working on an open-source assignment. I'd like to work on this issue to include banners in UX guidelines for notifications.

   I've read the issue description and understand this involves:

   • Adding banner guidelines to UX documentation
   • Possibly creating examples or specifications
   • Ensuring consistency with existing notification patterns

   Before I start, could you please clarify:

   1. Specific location**: Where exactly should these banner guidelines be added? (e.g., src/vs/platform/notifications/ or documentation files?)
   2. Format requirements: Should this be Markdown documentation, code comments, or both?
   3. Reference examples: Are there existing notification patterns I should follow?
   4. Scope: Does this include both success/error banners or specific types only?

   I've:

   • ✅ Forked the VS Code repository
   • ✅ Set up my development environment
   • ✅ Read the CONTRIBUTING guidelines

   I'm ready to implement this documentation update once I have your guidance on the exact requirements. This aligns perfectly with my assignment requirement for a **documentation contribution.

   Please let me know if I can proceed with this issue.

   Best regards,
   Cherehani Makigo.
   cmakinet.