Empty hiring-style layout with a swipeable card deck above primary actions
Empty hiring-style layout with a swipeable card deck above primary actions
Centered empty state with stacked photo frames and gentle motion
Soft panel empty state with overlapping template previews and doc link
An example of Empty: call log.
An example of Empty: client search.
Full empty state with icon, message, and action buttons. Use when a search returns no results, a filter clears all items, or a list has been emptied. The buttons give the user a way forward: go back, clear filters, or try a different query.
Smaller empty state with reduced spacing for constrained areas. Use inside sidebar panels, card widgets, or notification drawers where a full-size empty state would overwhelm the layout.
Empty state wrapped in a Card for first-time setup or onboarding. Use when the user has not created any items yet, like a project list, team roster, or dashboard widget that will fill with data once they take action.
App shell with a pinned staging environment banner, a switch action, a topbar, and a deployments page with an environment facts panel.
500 page with a retry action, home link, collapsible technical details (request id, timestamp, copy button) and a system status line. Ships composable parts.
Error 1 variant for block.
Error 2 variant for block.
A blueprint 404 with search and escape routes.
A full incident page for a 500 during maintenance: live status, rollback progress, request trace, incident timeline and email updates.
In-place panel fallback showing a mono error reference, a section-scoped retry button, and confirmation that the rest of the page is unaffected.
An SLO panel with a header badge, a four stat budget and burn rate row, and a line chart tracking remaining budget against ideal burn.
A master list of grouped exceptions with event counts and sparkline bars beside a detail pane showing the selected issue and its stack trace.
Application error tracking feed with severity indicators, occurrence counts, and source locations. Summary pills show error distribution.
A 404, 500 or maintenance page: status code, headline, explanation and two ways out.
A 404, 500 or offline screen with honest wording and a way out that can work: one sentence, beside places that still work, or a plain readout for developer tools.
A centred 404 page with an illustration, a home link and a contact action
A split 404 page with the brand mark, an illustration and a single home action
Interactive 404 page with search and help options
Maintenance page with countdown and progress tracking
Showing 361–384 of 1,149