Weave Code
Filament Clusters Laravel Package
asignua/filament-clusters
Organize your Filament admin panel into logical clusters. This package lets you group related resources and pages into cohesive modules, keeping navigation clean and making large applications easier to manage for developers and end users.
Group several Filament 5 fields into one input row with a shared label, joined borders and one focus ring: name parts, date ranges, amount + currency, address lines. Per-field validation keeps working. Successor of guava/filament-clusters.
Frequently asked questions about Filament Clusters
- What can I use asignua/filament-clusters for?
- It groups several Filament 5 fields into a single input row with one shared label, joined borders and a single focus ring. Typical uses are split name fields, date ranges, an amount next to its currency, and multi-line address input. Validation stays per field, so you keep your existing Laravel rules for each underlying input.
- How do I install asignua/filament-clusters?
- Install it with composer require asignua/filament-clusters in a Laravel app that already runs Filament 5. Because it is a form layout layer rather than a panel plugin, most projects need no extra provider registration; check the README for a view-publishing step if you intend to customize the markup. Pin the constraint to ^1.0 while the 1.x line is still maturing.
- Which Filament and Laravel versions does asignua/filament-clusters support?
- The package is built for Filament 5 fields, so your panel must be on Filament 5. The 1.x line is early, with v1.0.1 as a patch release, so verify the exact PHP and Laravel constraints in composer.json against your current LTS target before adopting. Treat that constraint as authoritative and re-check it at each minor release rather than assuming broad Laravel compatibility.
- How do I group fields into one row with a shared label?
- You declare the fields in PHP with the package layout API, for example columns(2) plus a per-field span, and give the cluster one label. The package renders the row through Blade with joined borders and a single focus ring so the group reads as one control. Column and span settings control how inputs distribute across the row and wrap onto additional rows.
- Does per-field validation still work when fields are grouped?
- Yes. The package does not own validation: you keep standard Laravel rules or FormRequest rules per field, and it surfaces each field error message in place. Message text stays under your control, for example 'The end date field must be a date after or equal to start date.' Adoption is form-by-form, so your existing validation contracts do not change.
- Is asignua/filament-clusters the successor of guava/filament-clusters?
- Yes, asignua/filament-clusters is the successor of guava/filament-clusters. Plan the switch as a namespace and Composer package swap, then re-check your field and layout calls against the current API. Diff the rendered output of one representative form so any change in border, span or label behavior is caught before you migrate the rest.
- Can I publish and override the Blade views without forking the package?
- The package renders through Blade, so the normal Laravel path applies: publish the views and own them inside your app instead of forking the repository. If the override surface proves insufficient, wrap the fields in your own Blade components so call sites stay insulated from upstream changes. Confirm the published view set in the README before committing to that route.
- Will dynamic column and span classes be purged from my production CSS?
- Dynamically generated utility classes for column and span settings are a real risk if your CSS build purges unused selectors. Layout can look perfect in the demo and silently collapse in production, so safelist the generated classes or ship precompiled output. Add a build check against a multi-column, multi-row form to catch regressions.
- How should I evaluate or test it before rolling out?
- Start with the bundled workbench demo: a half-day spike with screenshots of one, two and three-column layouts with spans at your breakpoints. Then rebuild a single internal admin form and diff the rendered HTML and validation messages against the current version. Because the v1.0.1 fix was a visual border defect in spanned multi-row grids, add a lightweight screenshot-diff test on that form partial.
- Is asignua/filament-clusters production-ready and actively maintained?
- It is an early 1.x package with a recent patch release and active documentation work, which are positive signals, but expect API movement before 2.0. The main risk is maturity rather than capability: border and edge logic across column counts, spans and wrapping is the class of bug most likely to recur. Pin to ^1.0, review each minor, keep a thin wrapper, and compare against plain Filament Grid or Section layouts for simpler forms.
Weaver
How can I help you explore Laravel packages today?