Status Page

Open source

A public system-status screen: an overall operational banner, a per-service status list composing the status component, and a past-incident history, above a pinned minimal footer.

Responsive Dark mode RTL Localized SEO

resources/views/pages/status-page.blade.php Blade

@props([])

{{-- Status Page 01 — a public system-status screen: an overall banner, a
     per-service status list (composing <x-ui.status>), and a past-incident
     history, above a pinned minimal footer. Wire the states to real monitoring. --}}
<div data-slot="page-status" class="flex min-h-screen flex-col bg-background text-foreground">
    <main class="mx-auto w-full max-w-3xl flex-1 px-4 py-12 sm:px-6">
        <header class="mb-8 flex flex-wrap items-end justify-between gap-4">
            <div>
                <h1 class="text-2xl font-semibold tracking-tight text-foreground">{{ __('System status') }}</h1>
                <p class="mt-2 text-sm text-muted-foreground">{{ __('Current status of our services and recent incidents.') }}</p>
            </div>
            <x-ui.button href="#subscribe" variant="outline">{{ __('Subscribe to updates') }}</x-ui.button>
        </header>

        {{-- Overall status banner. --}}
        <x-ui.alert variant="success" role="status" class="mb-8">
            <x-ui.alert.title>{{ __('All systems operational') }}</x-ui.alert.title>
            <x-ui.alert.description>{{ __('Updated just now') }}</x-ui.alert.description>
        </x-ui.alert>

        {{-- Per-service status. --}}
        <h2 class="mb-4 text-sm font-medium text-muted-foreground">{{ __('Services') }}</h2>
        <div class="divide-y divide-border overflow-hidden rounded-lg border border-border bg-card">
            @foreach (['API', 'Dashboard', 'Webhooks', 'Background jobs', 'Email delivery'] as $service)
                <div class="flex items-center justify-between gap-4 px-4 py-4">
                    <span class="text-sm font-medium text-foreground">{{ __($service) }}</span>
                    <x-ui.status variant="online" :label="__('Operational')" />
                </div>
            @endforeach
        </div>

        {{-- Past incidents. --}}
        <section class="mt-10">
            <h2 class="mb-4 text-lg font-semibold text-foreground">{{ __('Past incidents') }}</h2>
            <ol class="space-y-6">
                <li class="border-s-2 border-border ps-4">
                    <p class="text-sm font-medium text-foreground">{{ __('Elevated API latency') }}</p>
                    <p class="text-sm text-muted-foreground">{{ __('Resolved, 3 days ago, 42 min') }}</p>
                    <p class="mt-2 text-sm text-muted-foreground">{{ __('A database failover caused brief latency. Fully resolved after promoting a replica.') }}</p>
                </li>
                <li class="border-s-2 border-border ps-4">
                    <p class="text-sm font-medium text-foreground">{{ __('Scheduled maintenance') }}</p>
                    <p class="text-sm text-muted-foreground">{{ __('Completed, 2 weeks ago') }}</p>
                    <p class="mt-2 text-sm text-muted-foreground">{{ __('A planned database upgrade completed with no downtime.') }}</p>
                </li>
            </ol>
        </section>
    </main>

    <x-blocks.footer-minimal brand="Acme" brandHref="/" />
</div>

Installation

terminal

php artisan ui:add pages/status-page

Installs these dependencies automatically:

button status blocks/footer-minimal alert

Registry contract

Install confidence

php artisan ui:add pages/status-page writes only the generated targets below. The CLI validates each file hash before writing and prompts before replacing local changes unless --force is used.

Version: 1.0.5
License: open
Stability: stable
Contract: v1
Foundation: ≥ 1.0.0

Type	Generated target
blade	resources/views/pages/status-page.blade.php

Registry dependencies

button status blocks/footer-minimal alert

Package dependencies

composer: jml/brok:^0.2

Use with AI

A brief for your coding agent: what the page is, the install command, how to render it, its props and the rules. Copy it, or open a prompt about this page in an assistant.

status-page.md

# Brok UI page: Status Page (`status-page`)

A public system-status screen: an overall operational banner, a per-service status list composing the status component, and a past-incident history, above a pinned minimal footer.

Brok UI is a Laravel Blade registry. `ui:add` copies this page into the app as plain Blade the app owns; it composes installed `<brok:*>` primitives and semantic design tokens.

## Install

```bash
php artisan ui:add pages/status-page
```

## Render it

```blade
<x-pages.status-page />
```

## Use when

- A public system-status screen: an overall operational banner, a per-service status list composing the status component, and a past-incident history, above a pinned minimal footer.
- It composes the button, status and alert primitives plus blocks/footer-minimal.

## Avoid when

- Needing a pre-launch or maintenance notice instead of live service status; use maintenance-page instead.

## Rules

- Render the installed page with `<x-pages.status-page />` and pass data through its props; edit the copied file only for structural changes.
- Keep the semantic design tokens (`bg-background`, `text-muted-foreground`); never swap in raw colour utilities.
- Keep the `data-slot` attributes and the logical (start/end) spacing so the markup still mirrors under `dir="rtl"`.

## Links

- Docs: https://brokui.dev/pages/status-page
- Registry JSON (files, props, contract): https://brokui.dev/r/open/pages/status-page.json

Ask about Status Page in

Working in Claude Code, Cursor or Codex? Give the agent the whole registry through the MCP server or the Brok UI skill.

Guidance

Use when

A public system-status screen: an overall operational banner, a per-service status list composing the status component, and a past-incident history, above a pinned minimal footer.
It composes the button, status and alert primitives plus blocks/footer-minimal.

Avoid when

Needing a pre-launch or maintenance notice instead of live service status; use maintenance-page instead.

Anti-patterns

Do not replace semantic props with conflicting utility classes.
Do not remove labels, focus styles, or state attributes.

Anatomy: root page-status

Usage

Render the page as a component, or wire it to a route. Pass data where useful:

resources/views/welcome.blade.php Blade

<x-pages.status-page />

Built from blocks & primitives

This page composes installed <brok:*> primitives and semantic design tokens only — it does not reimplement any primitive. Re-theme it (light, dark, admin, customer) by editing CSS variables; flip the preview to RTL to confirm it mirrors.

Source

The exact, editable file ui:add writes into your app. The preview above renders this same source — there are no preview-only pages.