{{-- The layout every error page extends: this package's 403, 404, 419, 429, 500 and 503, and the framework's own 401 and 402, which extend `errors::minimal` and find this file before the framework's (the provider appends this folder's parent to `view.paths`). Sections — the framework layout's `title`, `code` and `message`, plus three of its own, so either layout renders the other's pages: `title` the browser tab, followed by the app name; `code` the status, drawn in display type over the shape; `headline` what happened, in a few words (without it, `message` is the headline); `message` one sentence on what to do about it; `shape` an M3 Expressive shape name (`cookie-7` by default), in primary-container; `actions` the buttons; by default a filled Home and, when the visitor came from a page on the way here, a text Back. The app's own Vite entries (`livewire-material.showcase.vite`) bring its scheme, font and the package's stylesheets, including this layout's own, resources/css/components/error-page.css. But an error page is also what shows while a deploy has no build yet, so when those tags cannot be made the page brings a small stylesheet of its own instead: the app's scheme from its scheme data, drawn onto the same `data-md-error-*` hooks (`src/Support/ErrorPage.php::fallbackStyles()`). Keep the hooks in step across both when changing the markup. The shape turns once a minute, unless the visitor asks for reduced motion. --}} @php $assets = \NoNameWeb\LivewireMaterial\Support\ErrorPage::assets(); $back = \NoNameWeb\LivewireMaterial\Support\ErrorPage::backUrl(); @endphp @yield('title') · {{ config('app.name') }}

@if ($assets !== null) {{ $assets }} @else @endif

@yield('code')

@hasSection('headline') @yield('headline') @else @yield('message') @endif

@hasSection('headline')

@yield('message')

@endif

@hasSection('actions') @yield('actions') @else @if ($back !== null) @endif @endif