Adminlte Templates Laravel Package

Getting Started

This release is the scaffolding path for AdminLTE on modern Laravel. Install with Composer (composer require acacha/laravel-ui-adminlte), then run the UI preset:

php artisan ui adminlte
# or with auth scaffolding
php artisan ui adminlte --auth
npm install
npm run dev

Look first at config/adminlte.php (menu, layout, auth routes), resources/js/app.js (Vite entry), and the published views under resources/views/vendor/adminlte/. The first practical use case is bootstrapping an authenticated admin area in a new Laravel 10 app: run the preset, register the auth guard if needed, run migrations, and load /admin to confirm the layout renders through Vite.

Implementation Patterns

Auth + layout scaffolding. Use php artisan ui adminlte --auth for a quick auth flow, then customize the guard and route prefix in config/adminlte.php. For existing apps, run the preset without --auth and wire the AdminLTE layout into your own controllers via @extends('adminlte::page').

Vite asset loading. Define resources/js/app.js and resources/css/app.css as Vite entries, import AdminLTE CSS/JS and plugins there, then reference them in your layout with @vite(['resources/js/app.js']). In production use npm run build; keep npm run dev for hot reload during development.

View extension. Publish views (php artisan vendor:publish --tag=adminlte_views) and extend them per module:

@extends('adminlte::page')
@section('title', 'Dashboard')
@section('content')
  @include('admin.partials.stats')
@stop
@section('plugins.Select2', true)

Menu-driven navigation. Register items in the menu array of config/adminlte.php with 'route', 'icon', and 'active' => ['admin/*'] for active-state highlighting. This keeps navigation out of blade templates and lets you gate items by role in a service provider.

Localization. Set APP_LOCALE, publish lang files where needed, and use translation keys in menu labels. The v6 localization fixes mean per-locale admin labels render correctly — verify with php artisan optimize:clear after changing locale files.

Gotchas and Tips

• Publishing overwrites your views. Always run vendor:publish with the specific tag and back up custom views; --force will replace your edits.
• Vite base path matters. If hosting the admin area under a subpath, set base in vite.config.js and rebuild; otherwise @vite emits broken asset URLs.
• jQuery/plugin order. AdminLTE plugins depend on jQuery and must be loaded before plugin scripts in the Vite entry — import order in app.js is load order.
• Laravel 10 upgrade. After upgrading, run composer update, republish stubs if the preset changed, and clear cached views (php artisan view:clear). Check for removed helpers if you customized the stubs.
• Localization caching. Translation and config caching can mask locale changes; run php artisan optimize:clear when debugging missing or mislabeled strings.
• Debugging menus and routes. If menu items don't highlight, dump the resolved route name and compare against the active array; use php artisan route:list to confirm the route exists under the expected prefix.
• Extension points. Favor config/adminlte.php menu arrays, published blade partials, and view composers in a service provider over editing vendor files — those survive minor upgrades.