How ictinnovations/ictschool works
Main components
• Web Frontend: Represented by the “resources/views” directory (Blade templates) and assets (CSS/JS in public and assets folders). This is the user-facing UI for various panels like the admin dashboard and teacher panels.
• Backend (Laravel Application): The core application is organized into MVC layers:
• Routes (defined in routes/web.php and routes/api.php) control incoming HTTP requests.
• Controllers (in app/Http/Controllers, including a dedicated Auth folder) implement business logic for various modules such as student, teacher, exam, fee management, etc.
• Models (in app/Models) map to database tables created via migrations (in the database/migrations folder) and represent entities like Student, Teacher, Class, Exam, etc.
• Console Commands (in app/Console/Commands) handle scheduled jobs and automated notifications (e.g., attendance notifications, fee notifications, etc.).
• Database: Use a MySQL (or other relational) database and highlight that migrations manage schema versions. Connect Models to database tables.
• External Services and Notifications: Indicate integration with SMS and voice notification services, as these features are explicitly mentioned in the README.
• Scheduled Jobs / Cron: The artisan scheduling system and defined cron jobs trigger background tasks via Laravel’s scheduler.
• API/Authentication: Note that Laravel Passport is installed to enable RESTful API interactions if needed.
• Users (e.g., admin, teacher, student, and parents) interacting with the Frontend/UI.
• That all requests first hit the Route layer; then controllers process them.
• For scheduled tasks (via Cron), illustrate a separate component that invokes Laravel console commands which, in turn, might trigger notifications or update records.
• If applicable, include an API layer (via routes/api.php) with Passport-based authentication for mobile or external integrations.
Architectural Patterns
• MVC Pattern: Clearly separate the views (Blade templates and public assets), the controllers (request handling and business logic), and models (data management).
• Dependency Injection and Service Providers: Since the project utilizes Laravel’s providers (see app/Providers), they can be shown as a layer that bootstraps application-level services.
• Cron and Scheduling: Illustrate how the Artisan scheduler (triggered externally by a system crontab) periodically executes various commands to keep processes like attendance and fee notifications automated.
Technologies and Frameworks
• Laravel Framework as the backbone.
• Composer for PHP package management.
• PHP 8.2 and MySQL (or another supported database system).
• Frontend assets include HTML/CSS/JS frameworks and additional libraries such as Bootstrap, jQuery, and Font Awesome.
• Laravel Passport for API authentication.
• Additional third-party packages (e.g., DataTables, Flot, etc.) as seen in public/bower_components.