How to organize sections of similar nature in Laravel? - laravel

Question

The Summary
Consider a Laravel project having, among all other things, the following sections: Files, Documents, Images, Videos, Tests.
Each of these sections stores some sort of data:
Documents contain various text documents.
Images contain image files of different extensions.
Videos contain video files of different extensions.
Files contain the rest of the files, not fitting into any of the sections above.
Tests contain sets of series of questions with an ability to respond.
Despite the diverse nature of their content, these sections are organized in the same fashion: each of them has data split by categories (which, by using the nested set model, may or may not include subcategories), and each item inside of them can be viewed individually on its full page.
So, each of these sections has the following route organization:
/{section} // The homepage of a section
/{section}/{category} // The page of a section's top-level category
/{section}/{parent_category}/{child_category} // The page of a section's subcategory
/{section}/{item_category}/{item} // The page of a section's specific item
Inside routes/web.php, I have made use of route groups from Laravel to achieve this:
Route::prefix('documents')->name('documents.')->controller(DocumentsController::class)->group(function () {
Route::get('/{category_slug}/{entry_slug}', 'entry')->name('entry');
Route::get('/{category_slug}', 'category')->name('category');
Route::get('', 'all')->name('all');
});
Route::prefix('images')->name('images.')->controller(ImagesController::class)->group(function () {
Route::get('/{category_slug}/{entry_slug}', 'entry')->name('entry');
Route::get('/{category_slug}', 'category')->name('category');
Route::get('', 'all')->name('all');
});
Route::prefix('videos')->name('videos.')->controller(VideosController::class)->group(function () {
Route::get('/{category_slug}/{entry_slug}', 'entry')->name('entry');
Route::get('/{category_slug}', 'category')->name('category');
Route::get('', 'all')->name('all');
});
Route::prefix('files')->name('files.')->controller(FilesController::class)->group(function () {
Route::get('/{category_slug}/{entry_slug}', 'entry')->name('entry');
Route::get('/{category_slug}', 'category')->name('category');
Route::get('', 'all')->name('all');
});
Route::prefix('tests')->name('tests.')->controller(TestsController::class)->group(function () {
Route::get('/{category_slug}/{entry_slug}', 'entry')->name('entry');
Route::get('/{category_slug}', 'category')->name('category');
Route::get('', 'all')->name('all');
});
This way I can attach different views and different data to different sections, but, as you can see, it becomes clumsier and clumsier if I'll add more sections, which is clearly a sign that what I am trying to do is not done right.
The Question
Simple and clean, how do I get rid of this duplicated code without opening new issues with the implementation? Most importantly, how do I organize such sections for getting a centralized control over their abstraction?
They are not similar to any data structure or database design model of which I know. I suspect that polymorphic relationships should be useful somehow, but even if I choose to use a polymorphic relationship, creating some sort of datastorable, I don't know how do I make routes of these abstractions which won't involve a lot of duplicate code.
Please do not respond the typical workaround by creating an array of titles and controllers and iterating over them in order to remove the duplicate code. Not only it forces to either typecast associative arrays to objects (which is considered a bad practice) in order to access values by -> object operator to keep it in line with Laravel's approach, but also it's adding its own layer of unnecessarity by redundant declarations.