Weave Code
Filament Header Schema Laravel Package
vitisstudio/filament-header-schema
Build Filament page headers with a schema-based API. Compose titles, actions, breadcrumbs, and custom header content consistently across resources and custom pages, cutting boilerplate and keeping headers clean, reusable, and easy to maintain.
Build rich Filament page headers with a schema instead of a Blade view.
Frequently asked questions about Filament Header Schema
- What does vitisstudio/filament-header-schema do?
- It adds a schema-based API for Filament page headers, so you declare titles, actions, breadcrumbs and custom header content in PHP with headerSchema() instead of overriding renderHeader() or shipping a custom Blade view. Headers become declarative and reusable across resources and custom pages, matching the schema idiom Filament already uses for forms, tables and infolists. It is an alternative to Blade-based header overrides and getHeaderWidgets() when you want consistent headers without per-page boilerplate.
- How do I install filament-header-schema in a Laravel app?
- Install it with Composer as vitisstudio/filament-header-schema, then add a headerSchema() method to the resource or page whose header you want to control. There are no migrations, no data layer and no background work, so nothing else in the application needs to change beyond registration. Keep the first change scoped to one page, validate it on staging, and compare screenshots at several container widths before rolling it out.
- Which Filament and Laravel versions does filament-header-schema support?
- The package is on a 1.x line and targets Filament's schema-based header surface, so check the Filament constraint declared in its composer.json rather than assuming compatibility with your installed minor. Because it hooks into header rendering and relies on Filament's .fi-* markup, verify support against the exact Filament major and minor you run and pin it in your lock file. Test any Filament upgrade on staging before adopting it.
- How do I build a page header with headerSchema() instead of a custom Blade view?
- Add a headerSchema() method that returns schema components, including a HeaderSection that holds your title, actions, breadcrumbs and any custom content. The package renders the header from that schema, so you can delete the renderHeader() override or Blade partial that previously assembled it. Everything stays in PHP, which means the header is reviewable in the same diff and idiom as the rest of the page schema.
- What is HeaderSection and how do the leading, main, and trailing slots work?
- HeaderSection is the header primitive, with leading, main and trailing slots so you can place content left, centre and right without writing layout CSS. The leading slot typically holds breadcrumbs or back navigation, main holds the page title, and trailing holds actions or status content. It also exposes from() breakpoints for controlling the split layout, though those breakpoints still respond to window width rather than container width.
- Does filament-header-schema work with existing getHeaderActions() and Filament breadcrumbs?
- Yes. The public API is a superset of behaviour Filament already exposes, so existing getHeaderActions() definitions continue to work unchanged and you can migrate headers one at a time. Breadcrumbs are supported as part of the schema, and since v1.1.0 the package resets Filament's breadcrumb offset and positions header siblings itself. That does couple it to Filament's undocumented markup, which is worth noting when planning upgrades.
- Can I reuse one header schema across multiple resources and custom pages?
- Yes, that is the main point of the package. Because the header is just a schema, you can extract it into a reusable method or class and apply it to multiple resources and custom pages across panels instead of duplicating Blade. This keeps headers consistent as teams add pages and reduces the drift that comes from everyone copying a header partial.
- What browser support do the container queries in filament-header-schema require?
- Version 1.1.0 replaced media queries in the actions row with @container queries against a named fi-hs-header inline-size container, which sets a browser floor of roughly Chrome 105, Safari 16 and Firefox 110. That is fine for internal admin tooling but should be stated explicitly if any kiosk or locked-down browser audience exists. Note that HeaderSection's from() breakpoints still use window-based media queries, so the header mixes two layout models.
- Does the package ship precompiled CSS or rely on my app's Tailwind build?
- This is one of the first things to confirm before committing: check whether the package ships precompiled CSS or expects your application's Tailwind build to scan its Blade views. If your app is planning a Tailwind v3 to v4 migration, that answer decides whether the package survives the upgrade unchanged. Inspect the package's distributed assets and its Tailwind configuration rather than assuming either way.
- Is filament-header-schema safe to depend on in production?
- Treat it as low-risk engineering and non-trivial supply chain risk: it is a 1.x package with a single maintainer, few stars and no dependents, so nobody else absorbs breakage when a Filament minor reshuffles header markup or spacing. Pin the version, plan to own it as vendored code with an upstream, and budget a visual QA pass on each upgrade. There is no auth surface, data layer or migration risk, and the failure domain is a single rendered region on a page.
Weaver
How can I help you explore Laravel packages today?