- What is mortalkiller/filament-page-header used for?
- It adds a reusable, customizable header component for Laravel Filament admin pages, so resource pages and custom screens can show page titles, actions, and contextual details consistently. It is a presentation-layer UI extension, not a domain, persistence, or service-layer package. Use it when you want to reduce repeated Blade header markup across a Filament panel.
- How do I install mortalkiller/filament-page-header in a Laravel app?
- Install it with Composer using the package name mortalkiller/filament-page-header, then follow the package setup instructions for your Filament version. The technical evaluation notes optional plugin registration in a Filament PanelProvider and possible view or config publishing. Verify the exact commands and published files against the package README before rolling it out.
- Does this package require registering a Filament plugin?
- The technical assessment describes optional plugin registration in a Filament PanelProvider, so registration may depend on how the header component is packaged for your Filament version. Check whether the release includes a plugin class or only Blade views and configuration. In a pilot, register it only in one panel first and confirm the header renders as expected.
- Which Laravel, PHP, Livewire, and Filament versions are supported?
- The available context does not document explicit version constraints, so you must confirm supported Laravel, PHP, Livewire, and Filament versions from the package metadata and README. Filament major versions can change Blade override and asset publishing behavior. Run a short proof of concept against your exact stack before accepting the dependency.
- Can I customize the page header actions, slots, or breadcrumbs?
- The package is described as customizable for page titles, actions, and contextual details, but the exact API for slots, actions, breadcrumbs, badges, and responsive layout is not documented in the provided context. Review the published views and configuration to see what can be overridden safely. Test customization against your existing resource page conventions.
- Is mortalkiller/filament-page-header safe for production?
- The runtime complexity appears low because it is a narrow Filament UI extension, but maturity and supply chain risk are the main concerns. The assessment cites thirteen stars, an unknown repository location, and a future-dated release, so verify the Packagist vendor, public repository, signed tags, release notes, and maintainer identity. Pin the version, commit the lockfile, and keep a fallback header component until an upgrade cycle has passed.
- How does it handle dark mode, RTL, localization, and accessibility?
- These areas are listed as risks in the technical evaluation, not confirmed features. The package may inherit Filament and Blade behavior, but header contrast, responsive layout, right-to-left rendering, translations, and focus or landmark semantics need explicit testing. Do not assume accessibility or RTL support without checking rendered output in your panel.
- Should I use this package or build an internal Blade header component?
- Because the scope is narrow, a small internal Blade component may achieve the same result with fewer supply chain and upgrade concerns. The package is justified if its header API already matches your Filament resource and page conventions and saves repeated markup. Compare maintenance ownership, customization needs, and Filament version churn before choosing the dependency.
- How do I migrate existing Filament pages to this header component?
- Start with a bounded pilot in one non-critical Filament panel or staging copy, and inventory existing custom header partials, resource page classes, and vendor view overrides. Install with an exact version constraint, apply the header to selected pages, and compare layout, breadcrumbs, actions, responsiveness, and accessibility against current headers. Migrate panel by panel behind a configuration toggle, and avoid global view overrides until the rendering contract is understood.
- Who maintains mortalkiller/filament-page-header and what happens if it is abandoned?
- The provided context does not identify a verifiable repository or maintainer, so provenance verification is required before adoption. The MIT license permits forking, but it does not guarantee support or upgrades. Decide internally who owns Filament upgrades and keep the previous header implementation or an internal Blade fallback available.