<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=425861) </details> <!--IssueSummary end--> ## Objective We mostly come across projects that have considerable amount of resources hosted into them already and hence don't get a complete picture of what new users see. Hence, we lack visibility into what the various empty states in CI/CD look like, and there have been some changes that were not ran through the design DRIs of the stage groups. Example: this shows when no pipeline is added to a project and the concerned team has no knowledge of this addition. {width=401 height=134} This highlight the need to pro-actively track these empty states to understand which frameworks we can employ next to make them more helpful for our users while aligning the actions with our business direction. ## Who will participate? <table> <tr> <th>DRI</th> <th>Pages/Area</th> <th>Stage-group</th> </tr> <tr> <td>Sunjung</td> <td>Pipeline editor, CI Catalog, Pipeline graph, tabs in the pipeline detail page</td> <td>Pipeline Authoring</td> </tr> <tr> <td>Gina</td> <td>Runner(at all levels), Runner settings, Runner management area</td> <td>Runner management</td> </tr> <tr> <td>Veethika</td> <td>Pipeline list view, Jobs list view, merge status widget(CI/CD related, pipeline tab in MRs, Job logs</td> <td> Pipeline Execution Pipeline Security </td> </tr> </table> | Activity | Goal | Issue | |----------|------|-------| | Audit | Understand where we're at with the current empty states and which components and pages lack an empty state | :star:️ Here️ | | Map empty states | Align the empty states in CI/CD with documented JTBDs and create a logical map on how they'd relate and connect | https://gitlab.com/gitlab-org/gitlab/-/issues/425860 | | Create issues | Identify the changes we need to make to all empty states and discuss with leadership to develop a plan of action | https://gitlab.com/groups/gitlab-org/-/epics/11532 | ## [FigJam Board](https://www.figma.com/file/gTY1rWyl0RlKGmK9obnszu/Build-empty-states?type=whiteboard&node-id=0-1&t=qsszexYudqJUd0hc-0) You may reference [this old issue](https://gitlab.com/gitlab-org/gitlab/-/issues/340407 "Design: Audit CI/CD page states"). ## Instructions (pending)