### Background The main status page Epic https://gitlab.com/groups/gitlab-org/-/epics/208 captures details on the audience and problem to be solved. #### Problem Summary 1. Stakeholders need access to the incident issue description and important comments that share information about what is happening, changes in progress/status. The description includes all written detail, embedded metrics charts, and embedded images/screenshots. 2. Responders (users who are working incidents and updating the status page) need a way to publish information to the status page from within GitLab 3. Customers need a way to engage GitLab with inquiries. They will no longer be able to comment on the GitLab incident issue directly, so they must be provided a communication channel. ### Further Details This epic captures work directly aimed at enabling the internal GitLab Infrastructure team to use ops.gitlab.net to manage incidents. This domain is private to protect critical systems and data. This set of functionality will also serve all customers who use their GitLab instances for Incident Management and need to manage stakeholders that do not have access to GitLab. This applies to most customers. ### Who does this serve? * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) ### Objective Here is a prioritized list to complete the MVC. This is what we consider necessary for Dogfooding (SRE team as a customer, deliverable) 1. Settings page for configuring where to upload status page JSON file 2. Ability to publish issue to a stand-alone site that includes: 1. Issue title 2. Issue description (JUST text) 3. Updates to title, description in GitLab automatically push to new site 4. Publish to CDN 5. Contact support button ### Design Proposal **MVC Designs:** | Landing page | Incident detail page | | ------ | ------ | |  | | **Longer-term vision for landing page (when we deprecate status.io):** | Landing page | Landing page, active incident | Incident detail page | | ------ | ------ | ------ | |  |  |  | ### References & Artifacts [Sketch cloud](https://sketch.cloud/s/z3yZb) [Balsamiq competitor analysis and wires](https://balsamiq.cloud/saotw6e/pofyliq) [User flow](https://app.mural.co/t/gitlab2474/m/gitlab2474/1580410553179/f5d39aff6b11055ffbe968da4094e21c6710741f) ### Documentation Documentation required.