# riccardofus/cavi-website architecture

> Architecture diagram of the GitHub repository riccardofus/cavi-website, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-06-24). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/riccardofus/cavi-website
- Repository: https://github.com/riccardofus/cavi-website

## Overview

##### Project type and purpose
- This is a static, front-end-only website (single HTML page plus CSS, plus miscellaneous downloadable CVs).
- Purpose: serve an index.html page styled by style/styleNew.css, and host several PDF/LaTeX files under misc/ for download.

##### File structure
- index.html at root: the entry point, delivers the page markup.
- style/styleNew.css: the styling sheet loaded by index.html.
- misc/: a directory of static assets (PDFs, TeX sources) that the user can download.
- No server-side code, no databases, no build scripts.

##### Extract insights from the README
- README.md is minimal (just “# Cavi Website”), confirming this is a static site without complex internal architecture.

##### Main components
a. User Web Browser (Client)
b. DNS / Domain Name
c. CDN / Static Web Host (e.g., S3 + CloudFront, Netlify, GitHub Pages)
d. Storage of static assets
– index.html
– styleNew.css
– misc/*.pdf, *.tex, etc.
e. Optional: Local Development Environment (e.g., file:// or local HTTP server)

##### Relationships and interactions
- User → DNS: resolves the domain name to the CDN endpoint
- User → CDN: HTTP GET index.html
- CDN → Storage: fetch index.html, CSS, PDF assets on cache miss
- CDN → User: serve cached or origin-fetched assets
- index.html → style/styleNew.css: the browser issues an HTTP request for the CSS file
- index.html → misc/*.pdf links: the browser downloads PDFs on click

##### Architectural patterns & design principles
- Static-site architecture: “Everything is a static file.”
- CDN-backed delivery for low latency and high availability.
- Separation of concerns: HTML (structure), CSS (presentation), and assets (documents) are in distinct folders.

##### Technologies / frameworks
- HTML5 (index.html)
- CSS3 (style/styleNew.css)
- Static-file hosting (e.g., AWS S3 + CloudFront, Netlify, GitHub Pages)
- DNS provider

##### Detail without over-thinking
- Even though the project is simple, capture:
– The flow of requests (Browser → DNS → CDN → Origin).
– The separation of assets (HTML vs. CSS vs. downloadable PDFs).

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% Client
    subgraph "Client Side"
        Browser["User Web Browser"]:::client
    end

    %% Network services
    DNS["DNS / Domain Name"]:::network
    CDN["CDN / Static Host"]:::network

    %% Storage origin
    subgraph "Origin Storage"
        HTML["index.html"]:::storage
        CSS["style/styleNew.css"]:::storage
        Misc["misc/ (PDFs, TeX sources, DOCX)"]:::storage
        Docs["README.md"]:::storage
    end

    %% Request flow
    Browser -->|"DNS Lookup"| DNS
    DNS -->|"Returns CDN Endpoint"| CDN
    Browser -->|"HTTP GET index.html"| CDN
    CDN -->|"Fetch index.html on cache miss"| HTML
    Browser -->|"HTTP GET style/styleNew.css"| CDN
    CDN -->|"Fetch CSS on cache miss"| CSS
    Browser -->|"Download misc assets"| CDN
    CDN -->|"Fetch assets on cache miss"| Misc
    %% Documentation retrieval (optional)
    Browser -.->|"View docs"| Docs

    %% CDN serves to browser
    CDN -->|"Serves cached assets"| Browser

    %% Click Events
    click HTML "https://github.com/riccardofus/cavi-website/blob/main/index.html"
    click CSS "https://github.com/riccardofus/cavi-website/blob/main/style/styleNew.css"
    click Misc "https://github.com/riccardofus/cavi-website/tree/main/misc/"
    click Docs "https://github.com/riccardofus/cavi-website/blob/main/README.md"

    %% Styles
    classDef client fill:#ADD8E6,stroke:#000,stroke-width:1px
    classDef network fill:#FFA500,stroke:#000,stroke-width:1px
    classDef storage fill:#90EE90,stroke:#000,stroke-width:1px
```
