How rishim9816/web-development-project works
Project type and purpose
• This is a simple full‑stack web application—a college prediction system with a login page and a predictor module.
• It uses HTML/CSS/JavaScript for the front end, PHP for server‑side logic, and MySQL as the backend database, all running on Apache via XAMPP.
File structure
• Top‑level files:
– Home.css, Login.css, practice.css: styling for each page
– Login.js: client‑side behavior for the login form
– home.php, login.php, practice.php: PHP templates that combine HTML, embedded PHP logic and include the appropriate CSS/JS
– usertable.sql: SQL script defining the MySQL user table/schema
• Single‑module monolithic layout—no separate “frontend” vs. “backend” directories, but clear functional separation (login vs. predictor).
Extract insights from the README
• Confirms tech stack: HTML, CSS, JS, PHP, MySQL, Apache (XAMPP).
• Core features: user authentication + college predictor.
a. Main components
– Client Browser (HTML, CSS, JS)
– Web Server (Apache + PHP runtime)
– Database Server (MySQL instance)
– Modules inside the server:
• Authentication Module (login.php + Login.js + Login.css)
• Prediction Module (practice.php + practice.css + Home.css)
b. Relationships and interactions
– User → HTTP(S) → Apache/PHP → MySQL
– On login: browser sends credentials → auth module validates → session created → response with Home page
– On prediction: browser inputs data → predictor module queries MySQL or applies PHP‑based logic → returns results
c. Architectural patterns/principles
– Monolithic MVC‑style separation at the code level:
• View: HTML/CSS, embedded in PHP templates
• Controller: PHP scripts handle requests, sessions, form processing
• Model: MySQL schema defined in usertable.sql, accessed via PHP’s mysqli or PDO
– Layered architecture: presentation (client), application (PHP), data (MySQL)
d. Key technologies/frameworks
– Apache HTTP Server
– PHP interpreter (v7.x+ assumed)
– MySQL database engine
– Client: modern browser (HTML5, CSS3, vanilla JS)