Clarify empty states on security dashboards
Problems
Based on the issue about day 1 experiences: #34369 (comment 279699498) Certain copies need to improve in the following situations:
-
Instance level dashboard:
- Title/Explanation copy: Tells the user exactly why the dashboard is empty: no scans enabled / no vulnerabilities found/ no projects added?
- CTA: Should it lead to the docs pages? If so, should it be a high level page or a sublinked section of that page? Or it should it link to the configuration page?
- Title/Explanation copy: Tells the user exactly why the dashboard is empty: no scans enabled / no vulnerabilities found/ no projects added?
-
Group level dashboard:
- Title/Explanation copy: Tells the user exactly why the dashboard is empty: no scans enabled / no vulnerabilities found/ no projects added?
- CTA: Should it lead to the docs pages? If so, should it be a high level page or a sublinked section of that page? Or it should it link to the configuration page?
- Title/Explanation copy: Tells the user exactly why the dashboard is empty: no scans enabled / no vulnerabilities found/ no projects added?
-
Project level dashboard:
- Title/Explanation copy: Tells the user exactly why the dashboard is empty: no scans enabled / no vulnerabilities found?
- CTA: Should it lead to the docs pages? If so, should it be a high level page or a sublinked section of that page? Or it should it link to the configuration page?
- Title/Explanation copy: Tells the user exactly why the dashboard is empty: no scans enabled / no vulnerabilities found?
Note: the following has been moved to #215504 (closed)
* Dependency page:
* Title/Explanation copy: Tells the user exactly why the dashboard is empty because no scans setup or because nothing has been scanned yet?
* CTA: it should be documentation of dashboard in general? or it should be documentation of how to setup? or it should be linked to configuration page?
Edited by Becka Lippert