Header, actions and widgets
Above the relation, a relation page can show part of the record's view, header actions and widgets. Define them on the resource for every relation page, or on a relation manager for its own page:

php
public static function relationPageHeader(Schema $schema): Schema
{
// The whole infolist (static::infolist($schema)) or a piece of it.
return $schema->components([
CustomerCard::make(),
]);
}
public static function getRelationPageHeaderActions(): array
{
return [
Action::make('email')
->url(fn (Customer $record): string => "mailto:{$record->email}"),
];
}
public static function getRelationPageHeaderWidgets(): array
{
return [CustomerStats::class]; // receives the record as $record
}
public static function getRelationPageFooterWidgets(): array
{
return [];
}- The header of a relation manager replaces the resource's one; actions and widgets of both are shown, the resource's first.
- Header actions act on the record the relation belongs to.
- With a header, the record's name is not repeated under the title.
- Pieces that only exist inside the view page class (its own methods and modals) are not reachable from here: move them to the resource, to an action class or to a trait.