How sonukr822800/blood-donation-management works
Project type and purpose
• This is a full-stack PHP web application called “Blood-Bank & Donation Management System.”
• It provides two layouts:
• User-facing pages (home, about us, why donate, become donor, search, contact)
• Admin panel (authentication, donor management, page content management, contact queries).
File structure
• Top-level files: home.php, about_us.php, need_blood.php, donate_blood.php, contact_us.php, etc.
• Shared includes: head.php, footer.php, slider.php, ticker.php, conn.php (database connection).
• “admin” directory: all admin PHP scripts (login, dashboard, add/update/delete donor, manage pages, queries), plus nicedit.js.
• “sql” directory: blood_bank_database.sql for MySQL schema.
• “image” and “admin/admin_image” folders: static assets for user and admin pages.
README for additional insights
• Technology stack: Apache + PHP + MySQL (XAMPP/WAMP).
• Database schema imported from sql/blood_bank_database.sql.
• Two logical modules: public website and protected admin panel.
Main components
a. Client (Web Browser)
• Interacts via HTTP/HTTPS
• Requests user pages or admin pages
b. Web Server Layer
• Apache HTTP Server running PHP
• Hosts all .php files and static assets (images, JS, CSS)
• Contains routing through individual PHP scripts
c. Application Layer (PHP Scripts)
• Public controllers: home.php, about_us.php, need_blood.php, donate_blood.php, contact_us.php, savedata.php, search_blood_group.php
• Admin controllers: admin/login.php, admin/dashboard.php, admin/add_donor.php, admin/delete.php, etc.
• Shared modules: conn.php, session.php, header.php, sidebar.php
d. Persistence Layer
• MySQL database “blood_bank_database” (hosted on local MySQL instance)
• Tables for donors, pages, contact queries, admins, sessions, etc.
e. Static File Storage
• Public images (slider, ticker) under /image
• Admin-uploaded images under /admin/admin_image
f. (Optional) External Services
• Email SMTP for contact us form notifications (if implemented)
Relationships and data flows
• Browser → Apache HTTP Server: HTTP Request → routes to specific PHP script
• PHP script → includes conn.php → opens MySQL connection
• PHP script ↔ MySQL: CRUD operations on relevant tables
• PHP script → reads/writes files in /image or /admin/admin_image
• Admin session control: login → session.php sets session cookies → guarded access to admin pages
Architectural patterns and design principles
• Layered architecture: Presentation (HTML/PHP templates), Application (business logic in PHP controllers), Data (MySQL)
• Modularization by directory: “admin” vs “public” modules
• Shared include files for cross-cutting concerns (DB connection, header/footer, session management)
a. Start by placing the Client (Browser) at the left or top.
– Public controllers (home.php, about_us.php, etc.)
– Admin controllers (/admin/*.php)
h. Optionally, show “Session Store” if sessions are persisted.
Clarity and detail
• Notes about key frameworks/libraries (e.g., nicedit.js for rich text editing in admin).