How noor-ahmed-12/blood-donation-bank-management-system works
Project type and purpose
• This is a monolithic, full-stack web application (“Blood Donation Bank Management System”) built on the LAMP stack (Apache + PHP + MySQL).
• It provides a public-facing portal (donor search, registration, requests) and an admin dashboard for managing users, donors, blood groups, donations, and requests.
File structure
• Top level:
• index.php, login.php, sign-up.php, search-donor.php, profile.php, contact.php – public-facing PHP pages
• request-received.php, donor-list.php, etc. – public user workflows
• css/, js/, images/, webfonts/ – static assets for the public site
• includes/config.php, includes/header.php, includes/footer.php, includes/slider.php – shared layout & configuration
• admin/ – entire admin module
· admin/index.php, dashboard.php, add-donor.php, manage-pages.php, request-received.php, etc.
· admin/includes/ – admin-specific config, header, left sidebar
· admin/css/, admin/js/, admin/img/, admin/fonts/ – admin assets
• Database script: bbdms.sql (defines MySQL schema for users, donors, recipients, blood groups, requests)
README for additional insights
• Confirms features: user registration/login, donor & recipient management, donation & request workflows, admin dashboard.
• Technical stack: PHP 7.4+, MySQL 5.7+, HTML/CSS/JS (Bootstrap, jQuery).
a. Main components
1. Client (Browser)
– Renders HTML/CSS/JS; interacts via HTTP(S).
2. Web Server
– Apache/PHP engine hosting:
• Public module (index.php, sign-up.php, includes/*, css/, js/, images/)
• Admin module (/admin/*)
– Shared PHP libraries/config under includes/config.php
3. Database
– MySQL instance storing:
• users table (donors, recipients, admins)
• blood_groups table
• donation_records
• blood_requests
• etc.
4. External services (optional)
– phpMyAdmin (for DB import)
– Email SMTP (if notifications implemented)
b. Relationships and interactions
– Browser ↔ Web Server: HTTP requests for pages, form submissions.
– Web Server ↔ Database: Server-side PHP issues SQL queries (CRUD) via mysqli/PDO.
– Admin module ↔ Public module: share config and DB but kept in separate URL space (/admin).
– Static assets served directly by web server (CSS, JS, fonts, images).
c. Architectural patterns/design principles
– Modular PHP includes for reuse (header, footer, config).
– Thin server-side presentation: server-rendered pages, minimal JS for interactivity.
– Role separation: public vs. admin modules.
– Single database backing entire application.
d. Key technologies/frameworks
– PHP 7.4+, MySQL 5.7+
– Bootstrap 4 (CSS/JS), jQuery, custom JS (medic.js, main.js)
– Apache (via XAMPP)
– Optional: Node/npm for front-end tooling (package.json present)
Detail
• Drill down into important pages (e.g., admin/dashboard.php calling chartData.js, admin/includes/config.php) if necessary.
• CRUD workflows: user management, donor records, blood requests, donations.