Laravel how best to organize the structure when for an Enterprise project?

Question

Software design

Good afternoon.
Interested in the question about writing an Enterprise portal on Laravel.
What's the best method for structuring files so they can be used later on in other projects? According to the standard file structure, it is not very convenient that all files are scattered throughout the project, if you want to edit something, you fly through all the folders looking for routes, views, controllers, etc.
For example, I want everything related to the blog to be in the App\Modules\Blog folder. The entire admin panel was in App\Modules\Admin, and everything needed for other modules to work was in App\Modules\Base, for example, User, Translation, Menu, Roles.
As I understand it, the option of wrapping the code in plugins is not entirely reasonable and resource-intensive.
Questions:
1. How to implement such a code structure?
2. Maybe someone has already encountered this, what are the pitfalls of such a structure? After all, if such a structure were super convenient, then Tyler would immediately think it over in the default Laravel structure.

Answer 1

laravel-modules
How to stumble on modular structure and areas from...
well, or go to symfony with its bundles