Include a fallback for help links in empty state call to action design specifications
Problem
Previously added empty states contained duplicate primary call to action buttons (see https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22745, https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21975) but empty states are still being added with duplicate primary call to action buttons (see https://gitlab.com/gitlab-org/gitlab-ee/issues/9233, https://gitlab.com/gitlab-org/gitlab-ee/issues/9230).
Proposal
Include a fallback for help links in empty state call to action design specifications (see helping users).
CURRENT
- The call to action button in the empty state should be a primary button.
- There is only one primary button since there can only be one primary button per form. If there is a need for more than one button, the other should be a secondary button.
PROPOSED
- The call to action button in the empty state should be a primary button.
- There is only one primary button since there can only be one primary button per form. If there is a need for more than one button, the other should be a secondary button.
- If there is no need for a primary button or the primary button has already been added in the near components (see tabs), there can be one or more help links within the description text (see helping users)