Table
Responsive data table with header, body, row and cell parts.
Preview
| Name | Role | |
|---|---|---|
| Jane Doe | [email protected] | Admin |
| Alex Brown | [email protected] | Member |
Controls
Device view renders in an isolated frame so real responsive breakpoints apply. Switch to Full for overflowing popovers.
Options
Visual options rendered from the current preview target.
Variant
Density
Installation
php artisan ui:add table
Registry contract
Install confidence
php artisan ui:add table
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.1.1
- License
- open
- Stability
- stable
- Contract
- v2
- Foundation
- ≥ 1.0.0
| Type | Generated target |
|---|---|
| blade | resources/views/components/ui/table.blade.php |
| blade | resources/views/components/ui/table/header.blade.php |
| blade | resources/views/components/ui/table/body.blade.php |
| blade | resources/views/components/ui/table/row.blade.php |
| blade | resources/views/components/ui/table/head.blade.php |
| blade | resources/views/components/ui/table/cell.blade.php |
Registry dependencies
None.
Package dependencies
composer: jml/brok:^1.0
Guidance
Structured comparisonCompare structured records across consistent attributes.
Use when
- Use when users need exact comparison across rows and columns, plus sorting or filtering. Do not use a table for narrative browsing or small mobile contexts where cards or lists are easier to scan.
Avoid when
- Prefer when exact cross-item comparison is the core job, not merely browsing.
- Task length
- medium
- Interaction cost
- medium
- Interruptiveness
- none
- Input precision
- none
- Mobile / touch risk
- high
- Accessibility risk
- high
- Needs background context
- No
- Comparison needed
- Yes
Preferred alternatives
- List or cards for narrative browsing
Anti-patterns
- Using cards when exact comparison is primary
- Forcing wide tables into narrow layouts without adaptation
API
manifest knowledge + registry-derived coverageProps
| Prop | Type / values | Default | Description |
|---|---|---|---|
| variant | default|striped|borderless|vertical-lines | default | Documented catalog control used by the preview workbench. |
| density | default|dense | default | Documented catalog control used by the preview workbench. |
| sticky | bool | false | Declared by @props in the registry Blade source. |
Slots
default— Native table sections and cells, usually composed through table subcomponents.x-ui.table.header— Installed subcomponent from the registry item.x-ui.table.body— Installed subcomponent from the registry item.x-ui.table.row— Installed subcomponent from the registry item.x-ui.table.head— Installed subcomponent from the registry item.x-ui.table.cell— Installed subcomponent from the registry item.
Data slots
table
table-body
table-cell
table-head
table-header
table-row
table-wrapper
Capabilities
Behavior
- Uses server-rendered Blade and semantic HTML.
- Preserves native table semantics for assistive technology.
- Declares registry capability flags: a11y, responsive, rtl, darkMode, localized.
Usage
<x-ui.table class="w-full max-w-lg text-start">
<x-ui.table.header>
<x-ui.table.row>
<x-ui.table.head>{{ __('Name') }}</x-ui.table.head>
<x-ui.table.head>{{ __('Email') }}</x-ui.table.head>
<x-ui.table.head>{{ __('Role') }}</x-ui.table.head>
</x-ui.table.row>
</x-ui.table.header>
<x-ui.table.body>
<x-ui.table.row>
<x-ui.table.cell>{{ __('Jane Doe') }}</x-ui.table.cell>
<x-ui.table.cell>jane@example.com</x-ui.table.cell>
<x-ui.table.cell>{{ __('Admin') }}</x-ui.table.cell>
</x-ui.table.row>
<x-ui.table.row>
<x-ui.table.cell>{{ __('Alex Brown') }}</x-ui.table.cell>
<x-ui.table.cell>alex@example.com</x-ui.table.cell>
<x-ui.table.cell>{{ __('Member') }}</x-ui.table.cell>
</x-ui.table.row>
</x-ui.table.body>
</x-ui.table>
Accessibility & localization
data-slot
Keyboard focus-visible
Localized labels
- Accessibility target: wcag-2.2-aa-target.
- Uses semantic HTML and a stable
data-slotattribute for styling/scripting hooks. - Focus-visible rings use the
ringtoken so keyboard focus is always visible. - Disabled and invalid states are conveyed to assistive tech, not by color alone.
- Targets WCAG 2.2 AA; verify contrast in light, dark, admin and customer surfaces above.
- Labels go through
__()and the component uses logical properties (ms-*,text-start,start-*) so it mirrors correctly — flip the preview to RTL to confirm.
Source
The exact, editable file ui:add writes
into your app — copy it or own the whole thing. Previews
render this same code; there are no preview-only components.
Changelog
Current version: v1.1.1. See the site changelog for the full release history.