Organizing web routes

Since it's php you can separate them to your hearts content.

I created a helper for it.

function routesForModel($model)
{
    return require base_path("routes/Models/{$model}.php");
}

function authRoutes()
{
    return require base_path('routes/auth.php');
}

So I can just do it like this.

routesForModel('books');
routesForModel('games');
routesForModel('movies');
routesForModel('records');
routesForModel('profiles');
authRoutes();

And then in each "model route" file add the routes needed.

Route::get('/books', BooksIndexController::class)->name('books.index');
Route::get('/books/create', BooksCreateController::class)->name('books.create');
Route::get('/books/{bookShowView}', BooksShowController::class)->name('books.show');
Route::post('/books/store', BooksStoreController::class)->name('books.store');
Route::get('/books/edit/{bookShowView}', BooksEditController::class)->name('books.edit');
Route::put('/books/{book}', BooksUpdateController::class)->name('books.update');
Route::delete('/books/{book}', BooksDeleteController::class)->name('books.delete');

If you are concerned about convenience - you are free to organize routes as you like. Just try this, try that - and you will know what fits. Extracting your admin routes to a separate file sounds good.

If you are concerned about performance - php artisan route:cache caches all routes in effective way no matter how you organize them.

@developer654079525 As others have said, you can organise routes how you wish.

For completely separate “sections” of applications, such as an admin panel, I extract those routes into their own routes file. I tend to name them something like routes/web.admin.php so it’s clear that it’s part of the “web” stack, but specifically the admin web routes.