Skip to content

[Discussion] Button > Append an ellipsis (…) to the button label text

Context

Context: Slack Discussion, !2615 (merged)

Pajamas guidance for Buttons states:

Append an ellipsis (…) to the button label text when the action will require additional input from the user before final completion. Does not apply to danger actions.

As GitLab is a complex tool, many buttons trigger workflows that require additional action from users, such as:

  • Projects > New project
  • Group > New group
  • Code > Repository > + > New file
  • Code > Repository > + > Upload file
  • Code > Repository > + > New directory
  • Code > Repository > + > New branch
  • Code > Repository > + > New tag
  • Code > Repository > Edit > Edit single file > Commit
  • Code > Branches > New branch
  • Issues > New issue
  • Issues > Add > New task / Existing task
  • Merge requests > New merge request
  • Build > Pipelines > New pipeline
  • Build > Pipeline Schedules > New schedule
  • Build > Test cases > New test case
  • Secure > On-demand scans > New scan
  • Deploy > Releases > New release
  • Deploy > Feature flags > New feature flag
  • Deploy > Model registry > Create model
  • Operate > Environments > New environment
  • Analyze > Analytics dashboards > New dashboard

Problem

There are many buttons across the site that require additional information from users.

The current guidance in Pajamas does not provide enough clear information to determine which buttons would benefit from the use of (...) in the button text, and which would not.

Should we:

  • Remove this guidance
  • Edit the guidelines to make it more clear when to use the (...) in the button text, and when to not
Edited by Alyssa Trinh