Weave Code
Black Dashboard Laravel Package
laravel-frontend-presets/black-dashboard
Laravel frontend preset that scaffolds a Black Dashboard admin UI with Bootstrap layouts, authentication views, and ready-made dashboard pages. Install via Composer to quickly generate routes, controllers, and a sleek dark admin theme.
Laravel 11.x Front-end preset for black dashboard
Frequently asked questions about Black Dashboard
- What is laravel-frontend-presets/black-dashboard used for?
- It is a Laravel 11.x frontend preset that scaffolds the Black Dashboard admin theme into a Blade and Bootstrap application. Running it generates dashboard routes, controllers, authentication views, and dark-themed layouts. It is intended as a scaffolding accelerator for admin panels, internal dashboards, and prototypes rather than a long-term UI platform.
- How do I install the Black Dashboard preset in Laravel 11?
- Install the package with Composer, then run the preset command it provides to publish views, assets, routes, and controllers. Because the exact Artisan command is not broadly documented and adoption is low, confirm the command in the package README and test it in a disposable Laravel 11 app first. After publishing, build your frontend assets with your configured Node tooling.
- Does this preset support Vite or does it require Laravel Mix?
- This is the main compatibility question to resolve before committing to delivery work. The template lineage may carry legacy Laravel Mix and laravel/ui assumptions, while Laravel 11 defaults to Vite. Verify in a throwaway app whether the published Sass and JavaScript compile under your Vite setup and whether any Mix scripts are still referenced.
- Which Laravel versions are supported?
- The package targets Laravel 11.x and was released in November 2024. Laravel 12 support is not explicitly confirmed, so treat any "11.x and up" claim as unverified. Pin the Composer version, commit your lockfile, and validate against your exact Laravel minor before relying on it.
- Will the preset overwrite my existing views, routes, or config files?
- Presets commonly overwrite application files such as app.blade.php, authentication views, route files, and build configuration. Before running it, inventory every file it creates or replaces, and run it on a branch with a rollback point. In existing applications, prefer manually extracting the assets and Blade patterns you want instead of running the preset against the codebase.
- Does it include authentication scaffolding and which guard does it use?
- The preset scaffolds authentication views as part of the admin UI, but the exact guard and controller assumptions depend on Laravel UI-style scaffolding. Check the generated auth controllers and routes in your spike to confirm they use the default web guard and match your application's user model. If you already use Breeze, Jetstream, or Fortify, do not layer this on top.
- Can I use this preset with Tailwind, Livewire, Inertia, or Vue and React?
- It is not a good fit for those stacks. Black Dashboard is Bootstrap-based, so mixing it with Tailwind, Breeze, Jetstream, or an Inertia single-page app creates conflicting styling and build pipelines. Isolate it to a separate admin surface or a prototype rather than forcing it into a customer-facing application.
- What license and attribution does Black Dashboard require?
- The Composer package is MIT licensed, but the underlying Black Dashboard theme comes from Creative Tim, which may have its own attribution or licensing terms. Review the upstream Creative Tim license before shipping, and keep any required credits in the layout. Confirm this early because removing attribution later can affect your release.
- Can I remove the package after generating the dashboard files?
- Yes, and that is usually the recommended path. The preset mostly produces static Blade views and frontend assets, so once generated you can commit those files as owned application code and drop the Composer dependency. Ejecting means your team owns normal Blade, SCSS, and JavaScript maintenance, but avoids tracking an unproven package.
- Is this package safe and maintained for production use?
- It has low ecosystem adoption, around 87 stars and no dependents, with community-only support and no vendor SLA. Runtime risk is limited because the output is largely static views and assets, but change risk is higher since the preset touches routes, views, and build configuration. Timebox a compatibility spike, run license and dependency security checks, and eject to owned files before production.
Weaver
How can I help you explore Laravel packages today?