# santimvillarreal/f1-cuyana architecture

> Architecture diagram of the GitHub repository santimvillarreal/f1-cuyana, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-09-17). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/santimvillarreal/f1-cuyana
- Repository: https://github.com/santimvillarreal/f1-cuyana

## Overview

##### Project type and purpose
- This is a static, frontend-only website (“F1 Cuyana”) built as the final project for a frontend programming course.
- Its purpose is to present Formula 1 information: news, race calendar, regulations, and history to new fans in an easy, practical, and engaging way.

##### File structure
- Top-level files:
- index.html – the entry point/homepage
- README.md – project description
- Public directory:
- css/styles.css – global stylesheet
- img/… – organized asset directories (calendario, historia, reglamento, contacto)
- pages/… – secondary HTML pages (calendario.html, historia.html, noticias.html, reglamento.html, contacto.html)
- No backend code, APIs, server logic, or database layers—this is purely static content.

##### README for additional insights
- Confirms it’s a static site for F1 content, aimed at new fans.
- No mention of build tools (webpack, rollup), frameworks (React, Vue), or server-side rendering.

##### Main components
a. End-user’s Web Browser
b. CDN or Web Server (e.g., GitHub Pages, Netlify, AWS S3 + CloudFront)
c. Static Assets:
- HTML files (index.html, pages/*.html)
- CSS (styles.css)
- Images (Public/img/…)
d. (Optional) DNS / Custom Domain and SSL certificate
e. (Optional) Version Control System (e.g., GitHub) as the source repository

##### Relationships and interactions
- The user’s browser sends an HTTP(S) request to the DNS-resolved domain.
- The request hits the CDN/Web Server.
- The server returns the requested static HTML page.
- The HTML references CSS (styles.css) and image assets, prompting additional HTTP requests.
- The CDN/Web Server serves those assets back to the browser.
- The browser renders the page and applies styles and images.

##### Architectural patterns and principles
- Single Page Entry with multiple static page routes.
- Content Delivery Network for performance and global distribution.
- Separation of concerns:
- HTML for structure & content
- CSS for styling
- Image assets for media
- Cache-first strategy (set appropriate cache headers on the CDN).

##### Relevant technologies
- HTML5, CSS3
- Static hosting (GitHub Pages / Netlify / AWS S3 + CloudFront)
- Optional DNS (Route 53, Cloudflare) & SSL/TLS
- Version control (Git)

## Diagram (Mermaid)

```mermaid
flowchart TB
    %% User Layer
    browser["User Browser"]:::user

    %% Hosting Layer
    dns["DNS / Load Balancer"]:::hosting
    cdn["CDN / Web Server"]:::hosting

    %% Assets Layer
    subgraph "Static Assets"
        subgraph "HTML Files"
            index["index.html"]:::asset
            calendario["calendario.html"]:::asset
            historia["historia.html"]:::asset
            noticias["noticias.html"]:::asset
            reglamento["reglamento.html"]:::asset
            contacto["contacto.html"]:::asset
        end
        subgraph "CSS"
            css["styles.css"]:::asset
        end
        subgraph "Images"
            img_calendario["/img/calendario"]:::asset
            img_historia["/img/historia"]:::asset
            img_reglamento["/img/reglamento"]:::asset
            img_contacto["/img/contacto"]:::asset
        end
    end

    %% Version Control
    git["Git Repository (README.md)"]:::repo

    %% Connections
    browser --> dns
    dns --> cdn
    cdn --> index
    cdn --> calendario
    cdn --> historia
    cdn --> noticias
    cdn --> reglamento
    cdn --> contacto
    cdn --> css
    cdn --> img_calendario
    cdn --> img_historia
    cdn --> img_reglamento
    cdn --> img_contacto
    index --> browser
    calendario --> browser
    historia --> browser
    noticias --> browser
    reglamento --> browser
    contacto --> browser
    css --> browser
    img_calendario --> browser
    img_historia --> browser
    img_reglamento --> browser
    img_contacto --> browser
    git -->|"Deployment Pipeline"| cdn

    %% Click Events
    click index "https://github.com/santimvillarreal/f1-cuyana/blob/main/index.html"
    click calendario "https://github.com/santimvillarreal/f1-cuyana/blob/main/Public/pages/calendario.html"
    click historia "https://github.com/santimvillarreal/f1-cuyana/blob/main/Public/pages/historia.html"
    click noticias "https://github.com/santimvillarreal/f1-cuyana/blob/main/Public/pages/noticias.html"
    click reglamento "https://github.com/santimvillarreal/f1-cuyana/blob/main/Public/pages/reglamento.html"
    click contacto "https://github.com/santimvillarreal/f1-cuyana/blob/main/Public/pages/contacto.html"
    click css "https://github.com/santimvillarreal/f1-cuyana/blob/main/Public/css/styles.css"
    click img_calendario "https://github.com/santimvillarreal/f1-cuyana/tree/main/Public/img/calendario/"
    click img_historia "https://github.com/santimvillarreal/f1-cuyana/tree/main/Public/img/historia/"
    click img_reglamento "https://github.com/santimvillarreal/f1-cuyana/tree/main/Public/img/reglamento/"
    click img_contacto "https://github.com/santimvillarreal/f1-cuyana/tree/main/Public/img/contacto/"
    click git "https://github.com/santimvillarreal/f1-cuyana/blob/main/README.md"

    %% Styles
    classDef user fill:#cce5ff,stroke:#004085,color:#004085
    classDef hosting fill:#d4edda,stroke:#155724,color:#155724
    classDef asset fill:#fff3cd,stroke:#856404,color:#856404
    classDef repo fill:#e2e3e5,stroke:#b8b9ba,color:#383d41
```
