Error Pages

Open source

Full-screen error pages — 404 and 500 status screens in masked-numeral, oversized, and helpful-links layouts.

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

@props([])

{{-- 500 server-error page — built inline from primitives. --}}
<div class="min-h-screen bg-background text-foreground">
    <main class="mx-auto flex min-h-screen max-w-xl flex-col items-center justify-center px-6 py-16 text-center">
        {{-- Icon chip --}}
        <div class="flex size-16 items-center justify-center rounded-full bg-destructive/10 text-destructive">
            <svg class="size-8" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true">
                <path d="M10.29 3.86 1.82 18a2 2 0 0 0 1.71 3h16.94a2 2 0 0 0 1.71-3L13.71 3.86a2 2 0 0 0-3.42 0Z" />
                <line x1="12" x2="12" y1="9" y2="13" />
                <line x1="12" x2="12.01" y1="17" y2="17" />
            </svg>
        </div>

        {{-- Status badge --}}
        <div class="mt-6">
            <x-ui.badge variant="destructive">{{ __('Error 500') }}</x-ui.badge>
        </div>

        {{-- Oversized status code --}}
        <p class="mt-4 text-2xl font-bold tracking-tight text-foreground tabular-nums sm:text-3xl">500</p>

        {{-- Headline --}}
        <h1 class="mt-2 text-2xl font-semibold tracking-tight text-foreground sm:text-3xl">
            {{ __('Something went wrong') }}
        </h1>

        {{-- Explanation --}}
        <p class="mt-4 max-w-md text-base text-muted-foreground">
            {{ __('Our server hit an unexpected error and could not complete your request. The team has been notified — please try again in a moment.') }}
        </p>

        {{-- Actions --}}
        <div class="mt-8 flex w-full flex-col items-center justify-center gap-4 sm:w-auto sm:flex-row">
            <x-ui.button href="javascript:window.location.reload()" class="w-full sm:w-auto">
                {{ __('Try again') }}
            </x-ui.button>
            <x-ui.button href="/" variant="outline" class="w-full sm:w-auto">
                {{ __('Back to home') }}
            </x-ui.button>
        </div>

        {{-- Status page link --}}
        <p class="mt-6 text-sm text-muted-foreground">
            {{ __('Still not working?') }}
            <a href="/status" class="font-medium text-foreground underline-offset-4 hover:underline">
                {{ __('Check our status page') }}
            </a>
        </p>
    </main>
</div>

Installation

terminal

php artisan ui:add pages/error-page-500-status

Installs these dependencies automatically:

button badge

Registry contract

Install confidence

php artisan ui:add pages/error-page-500-status 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.4
License: open
Stability: stable
Contract: v1
Foundation: ≥ 1.0.0

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

Registry dependencies

button badge

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.

error-page-500-status.md

# Brok UI page: Error 500 Page (`error-page-500-status`)

A centered full-screen 500 server-error page with a destructive icon chip, status badge, headline, explanation and try-again / back-home actions.

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/error-page-500-status
```

## Render it

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

## Use when

- A centered full-screen 500 server-error page with a destructive icon chip, a status badge, a headline, an explanation and try-again/back-home actions.
- It is built inline from primitives (button, badge) rather than composed marketing blocks.

## Avoid when

- Wanting a helpful-links layout or a masked numeral instead of a plain centered notice; use error-page-500-links or error-page-500-oversized instead.

## Rules

- Render the installed page with `<x-pages.error-page-500-status />` 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/error-page-500-status
- Registry JSON (files, props, contract): https://brokui.dev/r/open/pages/error-page-500-status.json

Ask about Error 500 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 centered full-screen 500 server-error page with a destructive icon chip, a status badge, a headline, an explanation and try-again/back-home actions.
It is built inline from primitives (button, badge) rather than composed marketing blocks.

Avoid when

Wanting a helpful-links layout or a masked numeral instead of a plain centered notice; use error-page-500-links or error-page-500-oversized instead.

Anti-patterns

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

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.error-page-500-status />

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.