Weave Code
Accordion Laravel Package
lara-zeus/accordion
Lara Zeus Accordion adds a simple accordion component to Laravel and Filament forms, letting you group fields into collapsible sections for cleaner, more organized layouts.
Zeus Accordion is filamentphp layout component to group components
Frequently asked questions about Accordion
- How do I install lara-zeus/accordion in a Laravel Filament project?
- Install it with Composer using an exact version pin, for example composer require lara-zeus/accordion:3.0.2. Before wiring anything into a panel, confirm whether the package is a registered Filament plugin or a pure schema component by checking vendor/lara-zeus/accordion/composer.json and grepping src/ for a Filament\Contracts\Plugin implementation. Layout components usually need no registration, and registering a non-plugin is a self-inflicted panel provider bug. There are no migrations, routes, or config files to publish.
- Which Filament version does lara-zeus/accordion 3.x support?
- The package's major versions track Filament's major versions, so 3.x targets Filament 3. Verify this against your installed Filament major before committing, because a mismatch invalidates the rest of the evaluation. You cannot adopt this package independently of your Filament version, and staying behind on Filament means staying behind here too.
- Is lara-zeus/accordion a Filament plugin that must be registered in the panel provider?
- Most likely not. It is a narrow schema layout component, and that class of package typically ships no Filament\Contracts\Plugin implementation and requires no panel registration. Confirm with a quick grep of src/ before adding anything to your PanelProvider. Assuming it is a plugin when it is not will break your panel boot.
- How do I use the accordion to group fields in a Filament Resource form?
- Drop the component into your schema like any other layout element and place form fields inside each collapsible section. A common pattern is daily-use fields above and metadata such as SEO, publishing state, and internal notes tucked into collapsed panels below. It composes with Section, Grid, Tabs, and Fieldset, so it fits existing schema conventions instead of introducing a parallel layout idiom.
- How do I make an accordion section collapsed or open by default?
- The package supports sensible default open states through a fluent API, but the exact method names are not enumerated in the release notes. Check the source for whether it is collapsed(), open(false), or something similar, and note what the canonical make() signature accepts. Do not assume the API from a previous major version, since the package has churned across three major lines.
- Can I nest Grid, Tabs, or other form fields inside an accordion section?
- Yes. The component is designed as a composable layout wrapper, so standard Filament form fields and layout components can live inside a panel. That includes Grid, Section, Tabs, and Fieldset. Keep the nesting sensible, since collapsed panels hide validation messages for any field inside them.
- Does the accordion's open state survive a Livewire re-render from a live() field?
- This is undocumented and must be tested in your own panel. Put a reactive or live() field inside a collapsed panel, trigger an update, and watch whether the panel stays closed. If state resets on every re-render, the component becomes unusable for reactive forms and should be evaluated accordingly before rollout.
- Is the accordion accessible, with aria-expanded, aria-controls, and keyboard support?
- Accessibility ownership is not documented. Nothing in the release notes claims aria-expanded, aria-controls, or Enter and Space keyboard activation, so assume the responsibility is yours until you inspect the rendered DOM. If those attributes and handlers are missing, either add them through a custom view or treat accessibility work as part of the integration cost.
- How do I customize the accordion's styling, and what CSS classes does it render?
- It uses Filament's styling and theme integration, so it inherits your panel's look out of the box. Modifier classes follow zeus-accordion-btn-* and zeus-accordion-container-* naming, but the specific suffixes are not enumerated in the release notes and remain an unconfirmed contract. Inspect the rendered DOM before writing CSS against them, and prefer the two base classes if you need stability.
- Is lara-zeus/accordion risky to depend on, and what about just using native details and summary?
- The risk is dependency durability rather than code quality: a small star count, few dependents, a single maintainer, and a single-vendor ecosystem, with majors that follow Filament's majors. The exit cost is genuinely low, which is the real mitigation, so wrap it in a single component rather than scattering it across the codebase. Outside a Filament schema, such as a marketing FAQ block, a native details and summary element is zero-dependency, keyboard-accessible, and strictly better, so do not let this package drift into general front-end usage.
Weaver
How can I help you explore Laravel packages today?