How we built Status Page

This post details the technical implementation of GitLab's Status Page, a new tool for communicating incident status and maintenance times. It addresses requirements for no tool switching during incidents, controlled visibility of updates, and display of rich data from GitLab incident descriptions. The implementation involved a Spike exercise, evaluation of open-source solutions, and a decision to build a custom implementation. The backend approach involves a background job converting incident issues to JSON and publishing to the Status Page. The frontend is built with VueJS and GitLab UI, and is a stand-alone application published to cloud storage (S3). The Status Page solution ensures that incident issues are converted to JSON and mirrored on the Status Page by a background job.