Skip to content

Entries

An infolist entry is text on a surface, so the type scale is most of the mapping. Nothing here is a theme method, except the badge variants an entry shares with a table column.

PartWhat it takes
Entry labelBody-small on the variant ink
Entry contentBody-medium on the plain ink
Text entryBody-medium on the plain ink; an affix or a limited-list message body-small on the variant ink
PlaceholderBody-medium in the outline color
Code entrySurface-container-highest, rounded 4dp
Image entryRounded 8dp
Color entryA circle behind a hairline
Repeatable entry itemA 1dp outline-variant border, rounded 12dp
php
use Filament\Infolists\Components\TextEntry;

TextEntry::make('status')->badge();
TextEntry::make('summary');

Badges

An entry renders a badge as a Material chip, and takes the same three container variants a table column does:

php
use Saade\FilamentMaterialTheme\Enums\ChipVariant;

TextEntry::make('status')->badge()->outlinedBadge();
TextEntry::make('status')->badge()->elevatedBadge();
TextEntry::make('status')->badge()->variant(ChipVariant::Filled);

See badges for the variants and their API.

Why the names end in Badge

An Entry descends from the schema component that carries the card variants, so a bare outlined() on one would give an outlined card.

Prose

Long-form content rendered through Filament's prose class takes the type scale: headings from the headline and title styles, body-large text, links in primary, inline code on surface-container-high, and quotes behind a 2dp rule in the outline-variant color.