- What is wg-vn/spatie-laravel-settings-ui?
- It is a Composer package that adds a plain Blade admin interface on top of Spatie's Laravel Settings package. Instead of building your own settings screens, you get a ready-made Blade panel for viewing and editing your application's settings. It deliberately avoids Filament, Livewire, and any front-end build step, so it drops into an existing Laravel app without new tooling.
- Does this package require Livewire or Filament?
- No. The package is built with plain Blade views only, so you do not need Livewire, Filament, or any other admin framework installed. That makes it a good fit for applications that want a lightweight settings screen without pulling in a full admin panel stack.
- Do I need npm or a Vite build step to use it?
- No build step is required. The UI ships as Blade templates, so you do not need to run npm install or compile assets with Vite to get the settings screen working. This keeps deployment simple, especially for small internal apps or legacy projects without a front-end pipeline.
- How do I install spatie-laravel-settings-ui?
- Install it with Composer using composer require wg-vn/spatie-laravel-settings-ui. After that, follow the README for any publishing and route registration steps, since setup details such as config, views, and route prefixes live there. You should already have Spatie's Laravel Settings package installed and configured before adding this UI.
- How do I protect the settings admin UI from unauthorized users?
- Because the UI is served through Laravel routes, you control access with standard route middleware. Apply your existing auth and authorization middleware so only intended administrators can reach the settings screen. Wrap it in a gate or policy if different roles should see different settings groups.
- Can I customize the look and feel of the settings UI?
- Yes. Since the interface is plain Blade, you can override or publish the views and adjust markup and classes to match your application's styling. There is no compiled asset pipeline to fight with, so template edits take effect directly. This is one of the main trade-offs of a Blade-only UI compared with a heavier admin framework.
- Which Laravel and PHP versions are supported?
- Version constraints are defined in the package's composer.json and reflected in the README. Check those constraints before installing to confirm compatibility with your Laravel and PHP versions. Because the package depends on Spatie's Laravel Settings, its supported Laravel range matters as well.
- Does it work with all Spatie Laravel Settings types, like arrays and encrypted settings?
- The UI renders editors on top of the settings classes registered with Spatie's Laravel Settings package, so it works with the settings you have defined. Complex types such as arrays or custom casts may render as simpler form inputs, so verify how your specific setting types appear. Highly custom casts are worth testing in a staging environment before relying on the UI in production.
- Can I use this instead of a Filament settings plugin?
- Yes, if you want a minimal admin screen without adopting Filament as a dependency. A Filament plugin makes sense when you already run Filament and want a consistent admin experience, while this package suits apps that only need a small Blade-based settings page. The trade-off is fewer built-in UI features in exchange for zero extra framework overhead.
- Is it safe to use in production and is it maintained?
- The package is a thin Blade layer over Spatie's Laravel Settings, so the underlying storage, caching, and repository behavior come from that well-established package. Before deploying, check the repository for recent commits, open issues, and tagged releases to judge maintenance activity. As with any third-party admin route, make sure it is behind authentication in production.