Weave Code
Wind Laravel Package
lara-zeus/wind
Lara Zeus Wind is a Laravel package in the Zeus ecosystem that helps you build dynamic, configurable interfaces with minimal boilerplate. Install it via Composer, define your settings in clean PHP, and ship admin panels and forms faster. Open source and MIT licensed.
Lara Zeus Wind is a Laravel package that provides a collection of Tailwind CSS-powered UI components and layouts for building clean, responsive admin interfaces. It streamlines common dashboard patterns so you can focus on application logic instead of repetitive markup.
- Prebuilt Blade components styled with Tailwind CSS
- Responsive layouts and navigation for admin panels
- Built-in dark mode and RTL support
- Works smoothly with Livewire and standard Laravel views
- Customizable components for your own design system
Frequently asked questions about Wind
- What is lara-zeus/wind used for in a Laravel app?
- Lara Zeus Wind is a Filament plugin for capturing inbound contact messages. It adds a public contact form, stores submissions, and gives you a Livewire-backed review table inside the Filament admin panel. It is not a general-purpose Tailwind Blade component library, so it fits best when Filament is already your admin system of record.
- How do I install lara-zeus/wind?
- Install it with Composer using composer require lara-zeus/wind. Then publish the package resources and register WindPlugin::make() in your Filament panel provider. The typical publish tags are wind-config, wind-migrations, wind-views, and wind-translations, though tag names can drift between majors. If a tag reports no publishable resources, run the interactive vendor:publish and select the provider.
- Does lara-zeus/wind require Filament and Livewire?
- Yes. The package is built for Laravel applications that already use Livewire and Filament, because the admin review screen and submissions resource live inside a Filament panel. If your app has no Filament panel, Wind is the wrong shape and configuration will not fix that. Check your installed filament/filament and livewire/livewire versions before adopting it.
- Which Filament versions does lara-zeus/wind support?
- Wind tracks Filament majors, so version compatibility is the first thing to verify. Run composer show filament/filament livewire/livewire laravel/framework on the target app and compare that with the require block in the package's composer.json for the exact tag you plan to install. A v4-era release will not install into a v3 panel, and PHP constraints are the usual silent blocker on older CI images.
- Why does my Wind contact form submit but no message is saved?
- A form that renders but silently does nothing is usually a stale asset or migration issue, not a package bug. Run filament:assets and livewire:assets after install and confirm cache-busting per release. Also verify that the Wind migrations were published and migrated and that the submission route is reachable.
- Why is lara-zeus/wind not showing in my Filament admin navigation?
- The most common cause is forgetting to register WindPlugin::make() in the panel provider that serves your admin panel. Confirm the plugin is added to the correct panel, then clear cached config and assets. If the form works but the review screen is missing, check panel access and resource discovery.
- How do I publish Wind's config, migrations, views, and translations?
- Use Laravel's vendor:publish command with the package's publish tags: wind-config, wind-migrations, wind-views, and wind-translations. Publish tag names drift between Filament majors, so if a tag returns no publishable resources, run the interactive publish and select the Wind service provider. After publishing, review the config and run migrations before testing the form.
- Is lara-zeus/wind safe to use in production?
- The code risk is low because the artifact is small: a table, a route, a Livewire component, and a Filament resource. The real risk is continuity: roughly 35 stars, zero dependents, a single maintainer, and maintenance-mode stewardship. Pin the exact version, wrap it in one swap point, and avoid standardizing on it across multiple products.
- Can lara-zeus/wind replace a CRM or helpdesk?
- No. Wind is a capture-and-review layer, not a CRM or helpdesk. It is suitable when the Filament panel is the accepted home for inbound messages or when you adopt it temporarily with an explicit migration plan to a CRM. If messages have an SLA or a sales owner, silent lead loss is a product failure that Wind cannot prevent.
- Should I use lara-zeus/wind or build my own contact form?
- Use Wind when you already run Filament, need a quick public form plus admin review, and want to skip a day or two of boilerplate. Build your own when you need routing, assignment, SLA tracking, custom PII handling, or a design that is not Filament-shaped. A competent Laravel developer can rebuild the equivalent in one to two days, so the decision is low-stakes either way.
Weaver
How can I help you explore Laravel packages today?