Developer tools template

Steadyline Status

For a hosted product that owes its customers a clear answer when something breaks. A strict grid in black and white, with one red signal kept for outages.

Opens the prompt in Crisp so you can change it before the build starts.

The look: Swiss Grid.

Precise and graphic: white, black and one signal red, on a strict grid. Headings in Archivo, text in Archivo.

  • background
  • surface
  • foreground
  • primary
  • accent
Opening
editorial: the name or promise in oversized type spanning the full grid, a small lede and an index of sections in columns under it
Sections
numbered sections on a 12-column grid, hairline rules between them, project rows with year and discipline in columns, no rounded cards
Motion
reveal on sections only
Texture
a faint grid faintly in the hero, hairline rules everywhere else

The screens.

  1. 01Status
  2. 02Incident
  3. 03History
  4. 04Subscribe
  5. 05Admin
  6. 06New incident
  7. 07Components
  8. 08Maintenance
The prompt Crisp receives
Build a status page for our hosted product, Steadyline. Customers visit it to see if something is broken; our on-call engineers post incidents and planned maintenance. Data: components (name, group: API, Dashboard, Webhooks or Storage, current status: operational, degraded, partial outage, major outage), incidents (title, impact, affected components, status: investigating, identified, monitoring, resolved, started at, resolved at), incident updates (incident, status, message, posted at, posted by), maintenance windows (title, components, start, end, message) and subscribers (email, confirmed). Public screens in order. The status page: a large one-line verdict across the top (all systems working, or what is not), each component as a row with its status and a 90-day bar of daily uptime, then active incidents with their updates newest first, and upcoming maintenance. An incident page with its full timeline. The history page, incidents grouped by month. A subscribe form for email updates. Admin, behind sign-in: a page header with a one-line summary, stat cards for open incidents, uptime this month and subscribers, then the incident list; a new incident form that sets the status of the affected components at once; a post-update form; components; maintenance; and settings. Emails to subscribers are stored until an email key is added. Seed four groups, eleven components, 90 days of history with five past incidents, and one planned maintenance window.
Use this template

What Crisp builds from it

  • A public status page with 90-day uptime bars
  • Incidents with a timeline of updates
  • Planned maintenance and a monthly history
  • Email subscribers, stored until a key is added
  • An admin for incidents and components

Change the name, the town and the details to yours before you start. How a build works.

More developer tools templates.

  • Ferrule Docs

    Developer docs that read like a book and search as you type

  • Hookcatch

    See exactly what a webhook sends before you write the handler

  • Patternbox

    Test a pattern or tidy some JSON, then share it with one link

Every template