rparvz700/admin360

1. This is a single Laravel 11 monolith: HTTP requests enter through routes/web.php and routes/auth.php, are handled by feature controllers in app/Http/Controllers, persisted through Eloquent models in app/Models, and rendered as Blade views in resources/views.

2. The application is organized by business domain rather than by technical layer. Major subsystems include Admin, Facilities Management, Vehicle Management, Ticket Management, Invoice Management, Generic Document Management, and Vehicle Maintenance Management. Each domain has its own controller folder, model set, and view subtree.

3. Authentication and user lifecycle are a first-class subsystem. The repo includes the standard Laravel auth flow plus custom controllers for login, registration, password reset, email verification, profile editing, and session confirmation. These screens live under resources/views/auth and resources/views/profile, with request validation in app/Http/Requests/Auth and ProfileUpdateRequest.

4. Authorization is built around Spatie Roles & Permissions. The config/permission.php config, the create_permission_tables migration, and the RoleSeeder, PermissionSeeder, and SuperAdminSeeder indicate a database-backed RBAC layer that gates access across admin and module controllers.

5. The Admin subsystem manages core master data: users, roles, departments, and subcenters. Its controllers and request classes follow a standard CRUD pattern with dedicated create/edit/index/show views and validation requests for store/update operations.

6. Facilities Management is a large domain covering buildings, floors, agreements, rent, security deposits, assets, asset categories, and asset attributes. The domain uses separate models for property and rental entities, suggesting a relational model where buildings contain floors, agreements drive rent and deposits, and assets have extensible attributes/values.

7. Vehicle Management is another major domain with vehicles, drivers, vehicle types, document categories, document attributes, and document records. The presence of document attribute/value models shows a configurable metadata pattern similar to the generic document and asset modules.

8. Vehicle Maintenance Management expands the vehicle domain with maintenance records, operational logs, parts, vendors, and reports. The views include reporting screens such as service due, vendor cost, vehicle cost, monthly expenses, and parts history, so this subsystem is not just CRUD; it also produces operational analytics.

9. Ticket Management provides a workflow around tickets, ticket updates, attachments, and vehicle assignment. Separate admin ticket controllers and admin-specific views suggest role-based triage or oversight distinct from regular ticket submission and viewing.

10. Generic Document Management is a reusable document metadata system. It has categories, attributes, documents, and attribute values, plus a client-side field generator in public/js/generic-document-attribute-fields.js, indicating dynamic forms that adapt to selected document schema.

11. The UI is server-rendered Blade with reusable layouts and components. Shared structure lives in resources/views/layouts, resources/views/Partials, and resources/views/components, while domain pages are composed from those common building blocks. Front-end behavior is added with static assets in public/js and compiled assets in resources/js / resources/css via Vite.

12. Persistence is conventional relational MySQL/PostgreSQL-style Laravel storage: feature-specific migrations define tables for each module, factories and seeders populate baseline data, and the storage directory handles cached views, sessions, logs, and public/private file storage. There is no separate service layer or external API architecture visible in the tree.

13. The test suite is focused on framework and auth behavior rather than domain logic. Feature tests cover registration, authentication, password reset/update, email verification, and profile flows, which matches the repo’s emphasis on secure access control and CRUD-driven internal workflows.