README

A Tailwind CSS / Flowbite backend shell for Laravel — sidebar, header, breadcrumb layout.

This package provides the structural layout (sidebar, top navigation, main content wrapper) for a Laravel admin panel. It is designed to work alongside laravel-cube for UI components, but the core layout works independently.

Requirements

• PHP ^8.2
• Laravel 11 / 12 / 13
• Tailwind CSS v4 + Flowbite (compiled via Vite in the host application)

Installation

composer require nasirkhan/laravel-admin

The service provider is auto-discovered.

Publish assets

Publish the config file:

php artisan vendor:publish --tag=admin-config

Publish the views (only if you need to customise them):

php artisan vendor:publish --tag=admin-views

Configuration

After publishing, edit config/admin.php:

return [
    // Brand name shown in the sidebar and browser tab
    'name' => env('APP_NAME', 'Admin'),

    // Optional logo path relative to public/ (null = text brand)
    'logo' => null,

    // Default theme: 'system' | 'light' | 'dark'
    'theme' => 'system',

    // Fallback navigation when no dynamic menu (module-manager) is available
    'nav' => [
        [
            'label'    => 'Dashboard',
            'route'    => 'backend.dashboard',
            'icon'     => 'home',
            'children' => [],
        ],
        [
            'label'    => 'Users',
            'route'    => 'backend.users.index',
            'icon'     => 'users',
            'children' => [],
        ],
        [
            'label'    => 'Roles',
            'route'    => 'backend.roles.index',
            'icon'     => 'shield',
            'children' => [],
        ],
        [
            'label'    => 'Notifications',
            'route'    => 'backend.notifications.index',
            'icon'     => 'bell',
            'children' => [],
        ],
    ],
];

Supported icon values: home, users, shield, bell, cog.

What's included

Beyond the layout shell, the package ships a complete backend for the three core resources:

All routes are named under the backend. prefix (e.g. backend.users.index) and protected by the auth and can:view_backend middleware.

Four Livewire components are registered by the package:

Controllers intentionally keep use App\Models\User and use App\Models\Role — models stay in the host application.

Customising views

Published views in the host application always take precedence over the package defaults. You can override any view without touching the package.

Publish all views at once

php artisan vendor:publish --tag=admin-views

Files land in resources/views/vendor/admin/ with the same structure as the package:

resources/views/vendor/admin/
├── users/
│   ├── index.blade.php
│   ├── create.blade.php
│   ├── edit.blade.php
│   ├── show.blade.php
│   ├── changePassword.blade.php
│   └── trash.blade.php
├── roles/
│   ├── index.blade.php
│   ├── create.blade.php
│   ├── edit.blade.php
│   └── show.blade.php
├── notifications/
│   ├── index.blade.php
│   └── show.blade.php
├── includes/
│   ├── action_column.blade.php
│   ├── errors.blade.php
│   ├── show.blade.php
│   ├── user_actions.blade.php
│   └── user_roles.blade.php
└── livewire/
    ├── dashboard.blade.php
    ├── notifications.blade.php
    ├── users-index.blade.php
    └── roles-index.blade.php

Publish selectively

Copy only the files you need to override. For example, to override just the user edit form:

mkdir -p resources/views/vendor/admin/users
cp vendor/nasirkhan/laravel-admin/resources/views/users/edit.blade.php \
   resources/views/vendor/admin/users/edit.blade.php

Laravel resolves admin::users.edit by looking in resources/views/vendor/admin/ first, then falling back to the package.

Publish everything (views + config + routes)

php artisan vendor:publish --provider="Nasirkhan\Admin\AdminServiceProvider"

Adding columns to the users table

To add a new field (e.g. phone) to user management:

1. Create and run a migration

php artisan make:migration add_phone_to_users_table --table=users
php artisan migrate

2. Add the column to $fillable in App\Models\User

protected $fillable = ['name', 'email', 'phone', ...];

3. Publish the views you need to change (if not already published)

php artisan vendor:publish --tag=admin-views

4. Edit the published views

• resources/views/vendor/admin/users/create.blade.php — add the form field
• resources/views/vendor/admin/users/edit.blade.php — add the field with its old/current value
• resources/views/vendor/admin/users/show.blade.php — add a display row

5. Optional — make the column visible in the listing

Publish and edit resources/views/vendor/admin/livewire/users-index.blade.php to add a column to the table. If the column also needs to be searchable or sortable, publish the Livewire component class by copying it into your app and re-registering it in a service provider:

// In your AppServiceProvider::boot()
\Livewire\Livewire::component('backend.users-index', \App\Livewire\Admin\UsersIndex::class);

Overriding the Dashboard and Notifications components

The Dashboard and Notifications Livewire components are intentionally minimal — they ship as empty shells so you can fill them with your own widgets and reactive features.

Override the view only

Place a file at the corresponding vendor path and Laravel will use it instead of the package default:

resources/views/vendor/admin/livewire/dashboard.blade.php
resources/views/vendor/admin/livewire/notifications.blade.php

Or publish all views at once and edit from there:

php artisan vendor:publish --tag=admin-views

Override the component class

If you need to add properties, computed data, or new actions (e.g. loading stats for dashboard widgets), extend the package class and re-register the alias in your AppServiceProvider:

// app/Livewire/Admin/Dashboard.php
namespace App\Livewire\Admin;

use Nasirkhan\Admin\Livewire\Dashboard as BaseDashboard;

class Dashboard extends BaseDashboard
{
    public int $userCount;

    public function mount(): void
    {
        $this->userCount = \App\Models\User::count();
    }
}

// app/Providers/AppServiceProvider.php
use Livewire\Livewire;

public function boot(): void
{
    Livewire::component('backend.dashboard', \App\Livewire\Admin\Dashboard::class);
}

Because AppServiceProvider boots after AdminServiceProvider, the re-registration replaces the package's class for that alias. The blade view can be overridden independently via the vendor path above.

Usage

Extend the admin layout in your backend Blade views:

@extends('admin::layouts.admin')

@section('title', 'Dashboard')

@section('breadcrumbs')
    {{-- optional breadcrumb markup --}}
@endsection

@section('content')
    <p>Your page content goes here.</p>
@endsection

Layout slots

Vite setup

The layout expects two Vite entry points compiled in the host application:

// vite.config.js
export default defineConfig({
    plugins: [
        laravel({
            input: [
                'resources/css/app-backend.css',
                'resources/js/app-backend.js',
            ],
        }),
    ],
});

app-backend.css should import Tailwind CSS v4 and Flowbite:

@import 'tailwindcss';
@import 'flowbite/src/flowbite.css';

@source '../views/backend/**/*.blade.php';
@source '../../vendor/nasirkhan/laravel-admin/resources/views/**/*.blade.php';

Optional integrations

These integrations are detected at runtime — the layout degrades gracefully without them.

Dark mode

Dark mode is toggled via a button in the top navbar and persisted in localStorage under the key color-theme. The <html> tag receives the dark class (Tailwind class-based dark mode).

License

GPL-3.0-or-later — see LICENSE.