How iamabdo/tecweb works
Main System Components
a) Client-Side Layer:
• Public Frontend (HTML/CSS pages)
• Admin Frontend (admin directory)
• JavaScript Components (*.js files)
b) Server-Side Layer:
• PHP Backend Components
• Authentication System
• Admin Modules
• File Management System
c) Data Layer:
• Database (indicated by sql.sql)
• File Storage (uploads directory)
Component Relationships
A. Frontend Components (Top Layer):
┌─ Public Area ─────────────┐ ┌─ Admin Area ──────────┐
• Specialty Pages │ │ - Dashboard │
• Degree Information │ │ - User Management │
• Contact System │ │ - Certificate Management│
• ┘ └────────────────────────┘
B. Middleware Layer (Center):
┌─ Authentication ─┐ ┌─ Core Logic ──────┐
• Login/Logout │ │ - Message Handling│
• Session Mgmt │ │ - Module System │
• ┘ └──────────────────┘
C. Data Layer (Bottom):
┌─ Database ─────┐ ┌─ File Storage ───┐
• User Data │ │ - Certificates │
• Course Info │ │ - Images │
• ┘ └─────────────────┘
Key Interactions to Highlight
• User authentication flow
• Admin access control
• File upload/download paths
• Database interactions
Technical Stack Indicators
• Frontend: HTML5, CSS3, JavaScript
• Backend: PHP
• Storage: MySQL (assumed from sql.sql)
• Static Assets: Images and Certificates
[Client Layer]
• ↕
[Application Layer]
• ↕
[Data Layer]
Document the message system integration
This educational platform architecture requires special attention to:
• User role separation (public/admin)
• Content management workflows
• File handling security
• Educational content organization
• Administrative controls