How tri1-sudo/webdemo works
Project type and purpose
• From the file tree and README (“Web Demo”), this is a purely static web site: a set of HTML pages, CSS styling, and images. There is no backend code or database—just client-side files to be served by a web server (or CDN).
File structure
• Top-level files and directories:
• index.html (landing page)
• html/ (about.html, blog.html, login.html, product.html)
• css/style.css
• img/ (all image assets)
• No server-side code, build scripts, or configuration files.
• The organization reflects a simple separation of concerns: HTML content, styling, and images.
README
• Minimal content (just “# Web Demo”), confirming that no special services, APIs, or frameworks are involved beyond delivering static files.
Main components
a. User’s Web Browser (Client)
b. Static File Host (Web Server or CDN)
c. File Store (the project’s directory structure: HTML pages, CSS, images)
Relationships and data flow
• The browser issues HTTP(S) requests for URLs ("/", "/about.html", "/css/style.css", "/img/...").
• The static file host / CDN resolves the request (DNS → Load Balancer if present) and serves the appropriate file from the file store.
• The browser renders HTML, fetches CSS and images, and displays the page to the user.
Architectural patterns and design principles
• This is the simplest “static site” architecture.
• Separation of concerns: content (HTML) lives separately from styling (CSS) and assets (images).
• Cache-friendly delivery: static files can be cached at multiple layers (browser, CDN).
Technologies, frameworks, or libraries
• No frameworks.
• Underlying hosting could be any static file server: Nginx, Apache, Amazon S3 + CloudFront, GitHub Pages, etc.