Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D design
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Primer
  • design
  • Issues
  • #295
Closed
Open
Issue created Sep 15, 2022 by Josep Martins@josepmartinsContributor

Alert dialog guidelines

Problem

Now that we have the wonderful Dialog documentation out, we might want to expand the documentation around dialog when used for alerts, warnings, or destructive purposes.

As @edokoa pointed out here, this sort of dialog doesn't follow a clear set of patterns, therefore we end up with different variations often used for similar use cases.

Figma file screenshot from @dylanatsmith to showcase different unpublish GitHub page dialog actions

Proposal

Add a new Dialog usage section (similar to the Button usage), or a subsection inside the Messaging guidelines. This documentation could cover:

  • Alert/flash banner usage (including best practices of danger and warning variants, positioning, tone and voice, etc)
  • Heading content, so we don't vary from "Are you sure...?" to "Doing this..."
  • Guidelines to display output or consequences on important actions (where and how to them, tone and voice, etc)
  • Consistency around buttons (when to require or not a confirmation input, using danger or secondary buttons, etc)

Slack thread reference (internal)

Figma file screenshot from @edokoa gathering all the different dialogs in GitHub

Assignee
Assign to
Time tracking