How drsatvir/webapp works
Project type & purpose (from file tree + README)
This is a teaching/demo web application for a Web Application Development (WAD) course. The repository is very small and mostly static:
• Static UI pages: index.html, landingPage.html, layout.html, newPage.html
• Styling: btsp.css, myStyle.css
• One dynamic/server-side page: dbasePage.php (likely demonstrates PHP + database concepts, given the filename)
There’s no explicit build system, package manager, or frameworks indicated. So the “architecture” is a classic server-hosted website with optional database access through PHP.
Static Files group
• index.html, landingPage.html, layout.html, newPage.html
• btsp.css, myStyle.css
Dynamic Endpoint
• dbasePage.php
Static page flow
• Browser → Web Server: GET /index.html
• Web Server → Browser: HTML response
• Browser → Web Server: GET /myStyle.css, GET /btsp.css
• Web Server → Browser: CSS responses
Dynamic PHP flow
• Browser → Web Server: GET /dbasePage.php
• Web Server → PHP Runtime: execute dbasePage.php
• (Optional) PHP Runtime → Database: SQL queries
• Database → PHP Runtime: result sets
• PHP Runtime → Web Server: generated HTML
• Web Server → Browser: HTML response
Architectural pattern to highlight
This is effectively a server-rendered web app with:
• Static content delivery (HTML/CSS)
• Server-side rendering via PHP for dynamic content
• (Optional) 3-tier structure: Presentation (Browser) → Application (PHP) → Data (DB)
Relevant technologies to label
Based on files:
• HTML, CSS
• PHP (for dbasePage.php)
• Apache/Nginx
• MySQL/MariaDB (only if dbasePage.php uses DB)
Start with runtime nodes (not code files)
• User, Browser, Web Server, PHP runtime, Database (optional)
Annotate responsibilities
• Static: “Serve files as-is”
• PHP: “Execute script, render HTML”
• DB: “Persist/query records” (only if applicable)
What “as many components as possible” means here (without inventing structure)
Since the repo is small, “more components” should come from:
• Splitting static vs dynamic
• Splitting server vs runtime
• Splitting asset types (HTML vs CSS)
• Splitting request types (GET static, GET dynamic)
Not from imaginary microservices or extra layers that aren’t present.