How florishafkenscheid/portfolio works
Main Components
A. Client Layer
• Web Browser
• Static Assets (CSS/JS)
B. Server Layer
• Apache Web Server (.htaccess present)
• PHP Application
• MVC Components:
• Controllers
• Views
• Route System
C. Data Layer
• MySQL/MariaDB Database (indicated by database.sql)
Component Relationships and Structure
• [Client Layer]
• ↕
• [Server Layer]
• ↕
• [Data Layer]
Break down each layer in detail
Client Layer:
• [Browser] ←→ [Static Assets]
• CSS (views/css)
• JavaScript (views/js)
Server Layer:
• [Route System] → [Controllers] → [Views]
• Route.php - BaseController - layout/
• BlogController - *.view.php
• HomeController
• etc.
Data Layer:
• [Database]
• (Defined in database.sql)
Specific Implementation Details
[BaseController]
• ↓
[Specific Controllers]
• BlogController
• ContactController
• ProjectsController
• HomeController
• InfoController
View Structure
[Views]
• Layout Templates
• Page Views
• Asset Management
Important Considerations:
Request Flow
• How controllers interact with views
• Database interactions where applicable
MVC Pattern
• Clearly separate the three main components
• Relationships between them
• Where the Route system fits in
Special Attention
• Routing system as it's a crucial component
• How .htaccess fits into the request handling
• Where static assets are served from
Additional Elements
• Component types
• Request/Response flow
• The MVC architecture
• Request handling flow
• Database interactions
• Static asset serving
• Template system structure
Remember to include notes about potential scaling points and areas where the architecture might evolve, as indicated by the README's mention of this being an "ever evolving portfolio project."