Larastarters Laravel Package

Getting Started

1. Start fresh: Create a new Laravel 11+ project — this package is strictly for new apps; existing code will be overwritten.
2. Install:

   composer require laraveldaily/larastarters --dev
   php artisan larastarters:install
   

3. Choose your stack: The interactive command prompts you to select between Laravel Breeze (Tailwind) or Laravel UI (Bootstrap), then pick one of 7 themes (e.g., Windmill, CoreUI, Volt, Plainadmin).
4. Run migrations & seed:

   php artisan migrate:fresh --seed
   

   This sets up auth tables and creates a demo user (admin@example.com / password: password).

👉 First use case: Instantly bootstrap a functional admin dashboard with login, registration, profile editing, a users list, and a static "About" page — ready for prototyping or MVP validation.

Implementation Patterns

• Theme customization: All themes are scaffolded into resources/views and resources/css. Modify layouts (e.g., resources/views/layouts/app.blade.php) or extend Blade components — no package-specific APIs needed post-install.
• Extend starter features:
  • Add new routes/controller methods under routes/web.php using the provided middleware (auth, verified).
  • Enhance the demo Users table by extending app/Http/Livewire/UsersTable.php (or equivalent) and connecting to your models.
  • Personalize the profile form (app/Http/Controllers/ProfileController.php) — it’s standard Laravel code, not abstracted.
• Workflow:
  1. Install Larastarters → test theme appearance.
  2. Replace demo UI elements (e.g., @section('content') in resources/views/home.blade.php) with your real pages.
  3. Use the two-level sidebar menu structure as a reference for building dynamic menus via policies/roles.
• Vite integration: Themes use Vite by default — run npm run dev or npm run build after install. Ensure vite.config.js exists at project root.

Gotchas and Tips

• ⚠️ No partial installs: Running larastarters:install more than once will overwrite files. Backup custom views before re-running.
• Container caveats: If using Docker/Sail, use --php_version=./vendor/bin/sail flag to avoid php binary path mismatches during asset compilation steps.
• Translation ready: All static strings (e.g., menu items) use __() — publish translations via php artisan vendor:publish --tag=laravel-translations if localizing.
• Theme quirks:
  • Some themes (e.g., Notus JS) require Tailwind JIT — confirm vite.config.js includes tailwindcss and purge configs.
  • Bootstrap themes (like CoreUI) often need jQuery — ensure resources/js/bootstrap.js loads it if using legacy plugins.
• Debugging tip: If auth routes break, verify routes/auth.php is included in routes/web.php and check for middleware conflicts in app/Http/Kernel.php.
• Extension points: To swap themes after install, manually replace resources/views/, public/css/, and public/js/, plus update vite.config.js imports — the package doesn’t support runtime theme switching.