How mahm0udrabie/schoolsystem works
Project type and purpose
• This is a modular Laravel‐based monolithic web application (“SchoolSystem”) that manages school data: configurations (grades, divisions, sections, subjects, teachers), student records, teacher agendas, and online classes (with Zoom integration). It exposes both web and API endpoints, handles authentication/authorization (Laratrust, Passport), event broadcasting, and notifications.
File structure
• Top‐level “Modules” directory: each subfolder (ConfigModule, OnlineClasses, Student, Teacher) is a self‐contained module with its own:
• Config (config.php, module.json)
• Database (migrations, seeders, factories)
• Entities (Eloquent models)
• Repositories (Interface + implementation)
• HTTP layer (Controllers, Requests, Routes, Middleware)
• Providers (ServiceProvider, RouteServiceProvider)
• Resources (views, JS, SCSS, language files)
• Transformers (API Resources)
• Tests
• Core Laravel app folders (app/, config/, routes/, database/, resources/, public/, storage/) host shared services: user auth, permissions, global configuration, queues, caching, event broadcasting.
• Key config files: config/modules.php wires modules; webpack.mix.js for asset compilation; composer.json for autoloading; modules_statuses.json for enabling/disabling modules.