Weave Code
Delia Laravel Package
lara-zeus/delia
Delia is a Laravel menu builder from Lara Zeus that makes it easy to define, store, and render navigation menus. Configure menus in code or the database, then output them in Blade with a clean, simple API for fast, maintainable site navigation.
Delia is a Laravel package from the Lara Zeus family that adds a complete FAQ module to your application. It plugs into the Sky admin panel, providing a Filament-powered interface to create, reorder, and publish questions and answers without boilerplate CRUD code.
Everything stays Laravel-native: Eloquent models, publishable config and views, and restylable Blade components. A practical fit for support centers, product pages, and marketing sites where non-developers manage content.
- Filament-powered CRUD for questions and answers
- Sortable entries with publish/unpublish controls
- Translatable, localization-ready fields
- Publishable migrations, config, and views
- Drops into any Sky-powered admin panel
Frequently asked questions about Delia
- What does the lara-zeus/delia package do?
- Delia adds a complete FAQ module to a Laravel application, with questions and answers managed through a Filament-powered CRUD interface. It ships sortable entries, publish and unpublish controls, translatable fields, and publishable migrations, config, and Blade views. It is built to drop into a Sky-powered admin panel so you do not have to write boilerplate CRUD code for support centers, product pages, or marketing sites.
- How do I install lara-zeus/delia in a Laravel app?
- Run composer require lara-zeus/delia, then publish the config, migrations, and views and run php artisan migrate. Register the plugin in your Filament panel provider, republish the panel assets, and clear the config and view caches. Because the package is tightly paired to a Filament major version, do a dry-run install first to confirm the PHP, Laravel, Livewire, and filament/filament constraints resolve cleanly.
- Which Laravel and Filament versions does Delia support?
- Delia 3.x exists specifically to support Filament 5, while the 2.x line covers Filament 3 and 4. Your Laravel and Livewire versions must meet the floors declared in the package composer.json. Check that constraint before planning anything, because Delia is a rider on a Filament major upgrade rather than a reason to perform one.
- Is Delia a standalone Laravel package or a Filament plugin?
- Delia is a Filament panel plugin and should be evaluated in the admin-panel layer, not as application infrastructure. It registers through a standard panel provider, adds migration-backed storage plus panel affordances, and does not touch your domain models, routing, or request lifecycle. That keeps its footprint small and well bounded inside one panel.
- Can I customize the FAQ views, styling, and translations?
- Yes. Migrations, config, and Blade views are all publishable, so you can restyle the components to match your application's design system. The question and answer fields are translatable and localization-ready for multi-language sites. Publish only the assets you actually intend to change so future package updates stay straightforward.
- Is Delia safe to use in production?
- It is MIT licensed with a small, well-bounded footprint, but it has a single maintainer and very low adoption, so treat it as a bounded experiment inside an internal panel rather than a platform building block. The mitigation is structural: the feature surface is small enough to fork or reimplement in roughly one to two days of engineering. Name and own that fallback before adoption, and keep customer-facing surfaces out of scope.
- The Delia docs describe something different from the code, so should I read the source?
- Repository descriptions for this package have drifted between releases, so budget an hour to read the plugin class, the migrations, and the config before committing. That review tells you what is actually persisted, which extension points are used, and what the upgrade path looks like. If that hour is not available, the package is not ready to evaluate yet.
- Does Delia handle authorization, multi-tenancy, and cascade deletes?
- These behaviors are not documented, so verify them in staging against your own panel. Check whether queries respect Filament's canAccess() for records a user can no longer reach, whether the migration carries a tenant or panel discriminator, and what happens to rows when a user or resource is deleted. Each of these is verifiable in under an hour and should be covered before rollout.
- How should I test a Delia integration in my Laravel app?
- Install into a staging panel first and exercise the create, reorder, publish, and unpublish flows the way a non-developer editor would. Add feature tests using Filament's testing helpers to cover access control, sort order persistence, and translated fields. Also watch query counts on pages with many entries to catch N+1 patterns early.
- What are the alternatives to Delia?
- The most predictable alternative is building it yourself: a small persistence table plus a Filament resource and a render or navigation hook, typically one to two days of engineering. You can also evaluate other Filament FAQ or content plugins, or simply own a plain Filament resource outright. If a Filament 5 upgrade is not already planned, Delia should not be the driver for it.
Weaver
How can I help you explore Laravel packages today?