Scaffolding Sections

The adminlte:scaffold command publishes complete, working sections into your Laravel app — migrations, Eloquent models, controllers, seeders, Blade views, and routes — driven by a declarative manifest baked into ScaffoldCommand.

Usage

adminlte:scaffold [section] [--all] [--force] [--seed]

Behavior:

• Passing an unknown section aborts with an error listing the valid names.
• With no section and no --all, you get a multi-select picker.
• Files that already exist are skipped (printed as exists) unless --force is used.
• Route registration is idempotent — a section's routes are added once and skipped on re-runs.

Available sections

Where files are published

Section manifest

The following tables list exactly what each section publishes, per the manifest in ScaffoldCommand.

mailbox

Routes (adminlte. prefix):

chat

Routes:

kanban

Routes:

calendar

Routes:

projects

Routes:

file-manager

No database. Browses files via Laravel's Storage.

Routes:

profile

No database (operates on the authenticated user).

Routes:

settings

No database.

Routes:

invoice

No database.

Routes:

pricing

View-only (no controller, no DB). Uses Route::view.

Routes:

faq

View-only (no controller, no DB). Uses Route::view.

Routes:

Database tables

The five DB-backed sections create the following tables.

Mailbox — adminlte_messages

Chat — three tables

adminlte_conversations

adminlte_conversation_user (pivot)

adminlte_chat_messages

Kanban — four tables

adminlte_kanban_boards

adminlte_kanban_lanes

adminlte_kanban_cards

adminlte_kanban_card_user (pivot)

Calendar — adminlte_events

Projects — adminlte_projects

Route group injected into routes/web.php

The scaffolder appends section routes into a managed block in routes/web.php. The block is created once and reused for subsequent sections.

The generated group:

// AdminLTE scaffold routes
Route::middleware(['web', 'auth'])->prefix('admin')->name('adminlte.')->group(function () {
    // [adminlte:mailbox]
    // ... the section's route lines ...
});

Key points:

• Middleware: web + auth — all scaffolded pages require authentication.
• URI prefix: /admin.
• Route-name prefix: adminlte. (so a section route mailbox.index becomes adminlte.mailbox.index).
• Each section is wrapped behind a // [adminlte:{section}] marker. If that marker is already present, the section's routes are not added again (idempotent).
• New sections are inserted right after the opening of the managed group; if the managed group doesn't exist yet, it's created at the end of the file.

If routes/web.php is missing, route registration is skipped with a warning.

Seeders and --seed

Each DB-backed section ships a demo-data seeder:

When --seed is passed, for each scaffolded section that defines a seeder the command runs:

php artisan migrate --force
php artisan db:seed --class={Seeder} --force

(View-only sections — file-manager, profile, settings, invoice, pricing, faq — have no seeder and are skipped by --seed.)

Getting started example

Scaffold the mailbox, create its table, seed demo data, and view it:

# 1. Scaffold the mailbox section (publishes migration, model, controller,
#    seeder, views, and routes) and run migrate + seed in one shot.
php artisan adminlte:scaffold mailbox --seed

# If you prefer to do it in steps:
php artisan adminlte:scaffold mailbox
php artisan migrate
php artisan db:seed --class=AdminLteMailboxSeeder

Then:

1. Add a sidebar menu item in config/adminlte.php pointing at the new route:

   ['text' => 'Mailbox', 'route' => 'adminlte.mailbox.index', 'icon' => 'bi bi-envelope'],
   

2. Log in (the /admin group is auth-protected — scaffold auth first with php artisan adminlte:make-auth if needed; see authentication.md).

3. Visit /admin/mailbox.