How azaou123/cms works
Project type and purpose
• This is a full-stack web application (“CMS Club Management System”) built on Laravel (PHP) with Blade templates, some client-side JS (Vite, Node/NPM), and a relational database (MySQL/PostgreSQL).
• It manages club data: members, cells, projects, events, meetings, conversations, notifications, and settings.
File structure
• Top-level directories:
• app/ (Models, Controllers, Notifications, Providers) → MVC central
• resources/ (views, CSS/SCSS, JS) → front-end assets & templates
• public/ (entry point, built assets) → static assets served by webserver
• config/, bootstrap/, routes/ → framework configuration & route definitions
• database/ (migrations, factories, seeders) → schema and test data
• tests/ → automated tests
• Build / deployment files: composer.json, package.json, vite.config.js, .env / .env.example, GitHub Actions workflow (.github/workflows/deploy.yml)
• Architectural patterns: MVC via Controllers → Models → Views, Service Providers bootstrapping, event/notification system, Eloquent ORM, RESTful resource routes.
README for additional insights
• Core features: CRUD on cells, events, meetings, conversations, projects; user auth/roles; club settings; notifications via Laravel’s Notification/Queue system.
• Technical stack: PHP 8.x, Laravel, MySQL/PostgreSQL, Node.js & NPM for front-end build, optional XAMPP, GitHub Actions for CI/CD.
• No SPA framework—server-side rendered with some JS enhancements.
Capturing essential details
– Include each sub-system (Auth, Cells, Events, Conversations, Meetings, Projects, Settings) as grouped modules under Controllers/Models
– Show Eloquent relationship flows (e.g., User ↔ Project via pivot table)