- What does the rdp77/laravel-stisla package actually include?
- It is a Laravel integration for the Stisla Bootstrap admin template, so expect publishable Blade layouts, partials and front-end assets rather than application logic. The release notes do not specify what ships, and the repo only mentions basic features, so publish it in a throwaway branch and list the views, config keys and assets before relying on it. It does not appear to include CRUD generators or a documented component API.
- Which Laravel and PHP versions does laravel-stisla support?
- Version 1.0.1's only manifest change is a composer.json update, and the supported Laravel and PHP range is not documented in the repository or release notes. Check the composer.json constraints against your target app and test the install on your exact Laravel version before merging. Pin 1.0.1 exactly instead of using a caret range until a support matrix exists.
- How do I install laravel-stisla with Composer?
- Run composer require rdp77/laravel-stisla, then publish the package views, config and assets with vendor:publish. Point a route group at the provided layout and confirm the views render. Because the publish tags and service provider registration are not documented, inspect the package source to confirm the exact publish tags.
- Is laravel-stisla compatible with Laravel 10 and Laravel 11?
- There is no published support matrix, so compatibility with Laravel 10 or 11 has to be verified by installing it in a branch against your target version. The package is a Blade presentation layer, so the main risks are autoloading, service provider registration and asset pipeline expectations rather than deep framework coupling. Run the install and a smoke test of every published view before deciding.
- Does laravel-stisla use Vite or Laravel Mix for assets?
- The repository does not state whether assets are bundled locally or referenced from a CDN, or whether it assumes Laravel Mix or Vite. Stisla is a Bootstrap 4-era template, so check whether the published assets are precompiled or expect a build step. Confirm the asset path matches your app's pipeline before adopting it, especially in a Vite-based Laravel app.
- Is laravel-stisla safe to use in production?
- Treat it as unproven: version 1.0.1 has three commits, a single maintainer, and no visible CI, tests or documentation. Admin shells touch login screens, layouts and asset pipelines, so coupling those surfaces to an unvetted dependency is asymmetric risk. If you use it, copy the views and assets into your own codebase and drop the Composer requirement.
- Should I keep laravel-stisla in require or publish the views?
- Publish the views and assets into resources/views/vendor and public, verify rendering, then remove the Composer dependency and own the copied files. This turns an unvetted third-party package into internal code with a known upgrade cost, which is the right trade for a UI shell you adopt once. Keeping it in require long term leaves your layout API exposed to churn from an early-stage package.
- What are good alternatives to laravel-stisla for a Laravel admin panel?
- If your team already standardizes on Tailwind, Laravel Breeze, Jetstream or Filament are more actively maintained and better documented. For Bootstrap-based dashboards, look at AdminLTE integrations or maintain the Stisla template directly without a wrapper. Choose based on your front-end stack, not just the theme's look.
- Does laravel-stisla include authentication scaffolding?
- The overview mentions auth-ready scaffolding, but the repository does not specify which auth screens or routes are included. Verify whether it ships login, register and password reset views, and whether they conflict with existing Breeze, Jetstream or Fortify scaffolding. Test coexistence before installing it into an app that already registers auth routes or layout namespaces.
- Is laravel-stisla maintained, and what license does it use?
- The package has a single maintainer, three commits and no visible tests or CI, so ongoing maintenance and Bootstrap security updates are not guaranteed. Stisla itself is MIT-licensed, but confirm both the package license and the bundled template assets before redistributing them in a commercial product. Also ask whether the maintainer intends to track upstream Stisla and Bootstrap upgrades.