Skip to content

docs: describe v3 status pages in the anatomy-of-a-status-page article (DOC-214) #740

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hlenke merged 1 commit into from
Oct 28, 2026
Merged

docs: describe v3 status pages in the anatomy-of-a-status-page article (DOC-214) #740

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion learn/incidents/anatomy-of-a-status-page.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ The basic technical requirements (fast loading pages, manual edits permitted, et

**3. Clear infographics** - a status page should be able to take complex historical data and turn it into a clear history for the viewer. Some kind of graphing library should represent high level status data visually.

**4. Incidents should be organized into services** - for Checkly’s Status Pages, all alerts are [classified ahead of time into services](/communicate/status-pages/overview#services). We don’t want to present our product as a monolith, nor should we print inscrutable internal labels. With this organization, we can present sections on a single status page, or multiple separate status pages with groupings of services.
**4. Incidents should be organized into services** - for Checkly’s Status Pages, you organize each page into [components](/communicate/status-pages/overview#components) ahead of time, and on Team and Enterprise plans, [automation rules](/communicate/status-pages/overview#automatically-creating-incidents) match failing checks by tag and open an incident on the components you choose. We don’t want to present our product as a monolith, nor should we print inscrutable internal labels. With this organization, we can present sections on a single status page, or multiple separate status pages with groupings of services.

**5. Subscription service** - Users should subscribe to only the pages they care about.

Expand Down
Loading