White Dashboard Laravel Package

Product Decisions This Supports

• Build vs. buy for admin chrome. This package is an "adopt" decision rather than a build: it ships a Bootstrap 4 dashboard shell (Creative Tim's White Dashboard) plus Laravel auth views and asset scaffolding. If your MVP's blocking work is "we need login, register, and a dashboard layout," this is a candidate to skip 1–2 weeks of design and wiring.
• Feature scoping and demo velocity. Use it to put a clickable admin surface in front of stakeholders early — useful for validating information architecture, navigation, and CRUD flows before committing to a design system.
• Roadmap and tech-debt triage. Adopt only as throwaway scaffolding. The package relies on the php artisan preset workflow, which Laravel removed in v8. That makes it a one-shot generator, not a maintained dependency — a decision you should make explicitly, not discover later.
• Vendor/theme shortlisting. A useful benchmark against Breeze/Jetstream + Tailwind, Filament, or a paid theme with a support SLA. It sets the floor for "free and fast."
• Signal check — do not over-read it. 50 stars, 0 dependents, opportunity score 2.07. This is not ecosystem direction and should not influence platform strategy. Treat it as a tactical utility, not a trend.

When to Consider This Package

Consider adopting when:

• The surface is internal-facing or a disposable prototype, the team is small, and there's no designer in the loop.
• You're willing to run it once and then delete it: composer require --dev, publish views/assets into your repo, uninstall the package. This is the only pattern I'd endorse.
• Bootstrap 4 is acceptable — the team already knows it, there's no Bootstrap 5 mandate, and no strict accessibility or design-system requirement.
• You need auth views and a dashboard layout now, and branding requirements stop at swapping a logo and color palette.
• MIT terms fit: no attribution burden beyond the license notice, no redistribution constraints.

Look elsewhere when:

• You're on Laravel 8+ and want supported first-party scaffolding → Breeze, Jetstream, or Filament.
• The real need is an admin panel with CRUD generation, tables, and filters → Filament or Backpack. This package gives you chrome, not capability.
• The product is customer-facing or long-lived → Tailwind plus a real design system, or a paid theme with a support contract.
• You need ongoing security patching of the theme, accessibility compliance, or a maintenance guarantee. One maintainer, zero dependents, and no community pressure to fix issues means bus factor ≈ 1.
• Bootstrap 4's jQuery-era dependency is a liability on your platform roadmap.

How to Pitch It (Stakeholders)

For executives: A free, MIT-licensed admin dashboard starter for Laravel. It compresses "we need a login screen and an admin shell" from roughly two weeks to roughly two days for internal tools and prototypes. It is scaffolding, not a platform bet — we extract the views we want into our own repo and can walk away at any time. The risk is contained: no license cost, no lock-in, no production runtime dependency.

For engineering: A Bootstrap 4 admin theme packaged as a laravel-frontend-presets preset — layouts, auth views, and asset config. Three caveats to plan around: the artisan preset install path was removed in Laravel 8, the theme is Bootstrap 4/jQuery-era, and the package is ~50 stars with zero dependents and a single maintainer. Recommended usage is a one-shot scaffold in a sandbox: publish views and assets into our codebase, then uninstall. Do not add it as a runtime dependency.

Recommendation: Conditional approve for internal tools and time-boxed prototypes; reject as a foundation for customer-facing or long-lived products. If the underlying need is truly an admin panel rather than an admin look, evaluate Filament first — it likely collapses both the scaffolding and the CRUD work into one decision.