add subtitle to a resource page?

[wivaku]

It's my understanding it is currently not possible to add a subtitle to a resource page.

Sometimes it helps to add some clarification.

Example:

E.g.

// CustomerResource

class CustomerResource extends Resource
{

  //protected static ?string $title = 'Custom Page Title';
  protected static ?string $subtitle = 'example of subtitle';

[danharrin]

$subheading

[arthurnmachado]

Is there any way to modify the subheading, such as its size or color?

[danharrin]

Using CSS in your theme file, yes

[wivaku]

Nice!

Could not find this in the documentation, right?
Looked here:
https://filamentphp.com/docs/2.x/admin/pages/getting-started#customization

Having trouble to get it to work though (strange: same for title btw).

[danharrin]

You need to put the properties on a page class, not a resource class

[wivaku]

That makes sense. To be sure, my question was about a resource.
$navigationLabel, $slug do work there. But $title and $subheading don't.
Is it possible (or: can it be added in the future) to customize $title and add $subheading to a resource?

[danharrin]

the resource is to define stuff that is used across multiple pages. any page-specific things like heading are overridden per-page. resource labels are used across all pages so they belong in the resource

[wivaku]

Ah, lightbulb moment 💡 !
I was focused on Resources\Shop\ProductResource.php
and I should have looked at Resources\Shop\ProductResource\ListProducts.php.

I have added to Resources\Shop\ProductResource\ListProducts.php:

    protected ?string $subheading = 'Custom subheading';

And it works. 👍

Note that if I add static (like the navigationLabel and slug for a resource) I get an error message:
Cannot redeclare non static Filament\Pages\Page::$subheading as static

Thanks Dan!

[bilogic]

Can subheadings be translated?

[bilogic]

LOL, ok, in that case, may I propose something that will fit all our needs. It will still be opt in, but getSubheading does not need to be overridden in every class.

public function getSubheading(): string | Htmlable | null
{
    if (config("filament.always_translate"))
    {
        return __($this->subheading);
    }
    
    return $this->subheading;
}

This proposal would not be needed if I could write protected ?string $subheading = __("translate this");, unfortunately it is illegal syntax.

[danharrin]

I think that would add too much maintenance burden ensuring that the setting is added in every place, I don't think I would accept that.

[bilogic]

What is your scope for "every place"?

For a start, I think getTitle() and getSubHeading() will do, the rest can be added progressively.
I'm willing to do the PRs for any reported translation issues for this mechanism.

To keep it maintainable, perhaps we can have this in trait to make it easy to remove (if there is ever a need). "Perhaps" because I have not looked at the consistency and location of the method names yet, but I think a trait would be very clean.

What kind of maintenance concerns do you have?

[danharrin]

Look, I'm not interested in the feature. Eventually every string will need to be added, it's just too much extra code. I'm happy with the current system of defining methods to pass translation strings.

[bilogic]

ok thanks

[BrilianPP]

Hello, please help me,
in my program, i have error "Missing required parameter for [Route: filament.admin.resources.periodes.rakers.index] [URI: admin/periodes/{parent}/rakers] [Missing parameter: parent]."
please help me for solve this problem
big thanks