How syntaxmo/itcs333-project-g6 works
Project type and purpose
• This repository is a monolithic multi‐module web application (“ITCS333‐Project‐G6”) that bundles six independent full‐stack sub-apps (Campus News, Events Calendar, Course Reviews, Course Notes, Club Activities, Student Marketplace).
• Each sub-app consists of:
• Static frontend files (HTML, CSS, JS)
• A PHP “API” layer (api.php, DatabaseHelper.php, config.php)
• An initialization script (init_db.php) for MySQL
• A filesystem area for uploads/images
• All sub-apps share the same CSS framework (Bootstrap) and are likely served from a single web server (Apache or Nginx+PHP-FPM) on the same domain.
File structure
• Top-level modules:
• Campus News/
• Events-Calendar/
• Phase1-ClubActivity/
• Phase1_Course-Notes/
• course-review2/
• student-Marketplace/
• Each module has:
• A client folder (HTML, CSS, JS)
• A server/API folder (PHP files, config.js)
• init_db.php to bootstrap its own schema
• An uploads or Pics/Images folder for attachments
• There’s a root index.html (likely landing page) and shared style.css.
Key insights from README
• Six student-owned modules, each with a dedicated author.
• Uses Bootstrap for responsive styling across all modules.
a. Main components (per module, repeated six times):
• Web Browser (Client-side)
• Static File Server (HTML/CSS/JS, served by Web Server)
• PHP Application Layer (api.php, DatabaseHelper.php)
• MySQL Database (initialized by init_db.php)
• File Storage (uploads/images directory)
b. Relationships & interactions:
1. User →
HTTP GET/POST → Web Server
2. Web Server serves HTML/CSS/JS to Browser
3. Browser JS calls AJAX → PHP API endpoints
4. PHP API → MySQL (CRUD) → returns JSON
5. For uploads, PHP → File Storage → returns URL
c. Architectural patterns & principles:
• Simple two-tier MVC-like pattern per module:
• View: static HTML + JS
• Controller: api.php endpoints
• Model: MySQL + DatabaseHelper.php
• Separation of concerns:
• Presentation, business logic, persistence are in separate layers
• Potential micro-service boundary: each module can be containerized independently
d. Key technologies:
• Frontend: HTML5, CSS3, JavaScript, Bootstrap
• Backend: PHP 7+, Apache/Nginx+PHP-FPM
• Database: MySQL
• Storage: Local filesystem for images