Create a Status Page
Draft and publish a new status page, from basic layout to public launch.
Steps
- Choose a descriptive internal name (not always public facing).
- Select visibility: Public (indexed) or Private (auth / secret link depending on future features).
- (Optional) Toggle Active; keep disabled if drafting.
- Add blocks (status bars, graphs) selecting monitors and time windows.
- Configure branding (logo, theme, custom CSS) if plan allows.
- Save & (optional) attach a custom domain.
Fields
| Field | Description | Notes |
|---|---|---|
| name | Display / internal identifier | Shown in dashboard & page header. |
| public | Boolean for visibility | Switch to private for internal use. |
| active | Operational toggle | Inactive pages hidden from listings. |
| blocks | Array of layout components | Define requirements (status, uptime, ping). |
| customDomain | (Plan) Custom FQDN | Requires DNS configuration (CNAME / A). |
| customCss | (Plan) Style overrides | Sanitized & injected server-side. |
Custom Domain Setup (High Level)
- Enter domain (e.g.,
status.example.com). - Verify ownership (DNS validation approach may vary—future docs).
- Point DNS to provided target (CNAME recommended).
- Await certificate provisioning (usually minutes).
Draft Workflow
- Build page in private mode.
- Verify data & theming.
- Flip to public once approved.
Versioning (Recommended Practice)
Clone existing page (future feature) before large structural changes to reduce risk.
Incident & Maintenance Integration
Incidents and maintenances linked to monitors automatically appear; no manual embedding required if the corresponding blocks reference those monitors.
Accessibility Tips
- Ensure sufficient color contrast in custom themes.
- Provide alternative text for custom logos.
Next Steps
- Learn about Filters for managing many pages.
- Configure integration alerts to drive proactive communication.