- What is the White Dashboard Laravel frontend preset?
- White Dashboard is a Laravel frontend preset that scaffolds a clean, light admin dashboard with Blade layouts, authentication views, and UI components. It is a scaffolding generator rather than a runtime library, so once installed you own every generated file. It fits best in a greenfield, server-rendered Blade application whose design direction matches the White Dashboard visual style.
- How do I install laravel-frontend-presets/white-dashboard?
- Install the package with Composer, then run the Artisan preset command it provides to copy views, layouts, and compiled CSS and JavaScript assets into your app. Run it on a fresh Laravel application or commit your work first, because preset commands can overwrite same-named files in resources/views and public. Check the composer.json version constraints before installing.
- Does this preset support Laravel 11?
- It is described as a Laravel 11.x frontend preset, so that is the target to verify first. However, the core preset command was removed from the Laravel skeleton in Laravel 7 in favor of laravel/ui, Breeze, and Jetstream, so confirm the package actually installs and runs on your exact Laravel 11 version. A short test in a throwaway application is the reliable check.
- Is White Dashboard compatible with Laravel 10 or Laravel 12?
- The package context only claims Laravel 11.x, and there is no verified compatibility matrix for Laravel 10 or 12. The laravel-frontend-presets family originally grew up around much older Laravel versions, and a recent release may be only a metadata or dependency bump. Test any target version in an isolated app before relying on it.
- Is laravel-frontend-presets/white-dashboard maintained?
- Maintenance signals are weak: the repository has low stars, zero dependents, and a single-purpose scope. There is little production evidence in the wild and no real bus factor beyond the maintainer. Treat it as a one-time scaffold source rather than a long-term maintained dependency.
- What UI stack and assets does White Dashboard include?
- It provides a Blade and Bootstrap-era admin theme with its own jQuery-driven JavaScript, charts, icons, and font assets. Creative Tim themes of this vintage often bundle Bootstrap 4, jQuery, Chart.js, and CDN-hosted resources, which can surface in security and GDPR reviews. Confirm the exact bundled versions and whether assets are served locally or from third-party CDNs.
- Can I use White Dashboard with Inertia, Vue, React, or Livewire?
- It is a poor fit for Inertia or SPA frontends because it assumes server-rendered Blade views and the theme's own JavaScript behavior. It can be a workable starting point for a Blade or Livewire application if the visual style matches your product. Otherwise, use the repository as a design and asset source and port the views into your existing component system.
- Does the White Dashboard preset overwrite existing views?
- Preset commands typically copy files into resources/views and public and may overwrite same-named files. Run the command on a clean application or commit and stash your work first so you can review and revert the generated changes. There is no guaranteed merge strategy or update channel for copied-in files.
- How should I evaluate White Dashboard before using it in production?
- Time-box a short spike in a throwaway Laravel app pinned to the highest version the package claims to support. Inspect the copied views and assets, check bundled Bootstrap, jQuery, and Chart.js versions for known CVEs, and verify the theme license fits your internal or resale distribution model. For a current Laravel application, installing Breeze and hand-porting the White Dashboard views is often the safer path.
- What are alternatives to the White Dashboard Laravel frontend preset?
- Laravel Breeze is the current standard for simple Blade authentication scaffolding, while Jetstream and Volt cover more opinionated stacks. If you only want the White Dashboard look, treat the repository as a design and asset source and port the layouts into your own Blade components. That avoids committing your team to a deprecated preset mechanism with no upgrade story.