# 06samuel/simulation_app architecture

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

- Interactive diagram: https://gitdiagram.com/06samuel/simulation_app
- Repository: https://github.com/06samuel/simulation_app

## Overview

##### Project type and purpose
- This is a static, multi-page front-end web application (“Rent Apart” simulation) composed entirely of HTML, CSS, and JavaScript prototypes.
- It uses GitHub Actions and Jekyll to deploy to GitHub Pages as a static site.

a. Developer’s GitHub Repository
– Contains all source files: HTML pages (index.html, apartments.html, etc.), CSS (styles.css), JS (main.js), and configuration (.github/workflows/jekyll-gh-pages.yml).
b. Continuous Integration / Continuous Deployment (CI/CD) Pipeline
– GitHub Actions workflow triggered on pushes to the repo.
– Jekyll build step (optional, if markdown or templating is used), then deploy to GitHub Pages.
c. Static Hosting / Content Delivery Network
– GitHub Pages serves the built site via a global CDN.
d. End-User’s Web Browser
– Fetches HTML, CSS, JS assets from the CDN.
– Renders the various pages (dashboard, galeri, kalender, landing pages, profile, etc.).
e. (Optional) External API Integration
– For example, kalender_google.html hints at Google Calendar integration via client-side API calls.

##### Architectural patterns and design principles
- Static site architecture: separation of build/deploy pipeline and runtime delivery
- Client-side rendering: HTML templates + JS for interactivity (main.js)
- Folder structure reflects multiple UI prototypes, each page is standalone
- Single Responsibility: each component (repo, CI/CD, hosting, client) has a clear role

##### Key technologies and frameworks
- HTML5 – page layout, multiple prototypes (apartments, details, reports, etc.)
- CSS – styles.css for theming across pages
- JavaScript – main.js for UI behavior
- GitHub Actions – .github/workflows/jekyll-gh-pages.yml for CI/CD
- Jekyll (via GitHub Pages) – optional static generator
- GitHub Pages / CDN – global static asset hosting
- Potential External APIs – e.g., Google Calendar

## Diagram (Mermaid)

```mermaid
flowchart TB
    Developer["Developer"]:::actor
    subgraph "Code Repository"
        Repo["GitHub Repository"]:::repo
        Workflow["CI/CD Workflow (.github/workflows/jekyll-gh-pages.yml)"]:::ci
    end
    subgraph "Front-end Static Assets"
        HTML["HTML Pages (*.html)"]:::repo
        CSS["CSS Stylesheet (styles.css)"]:::repo
        JS["JavaScript Behavior (main.js)"]:::repo
    end
    CDN["GitHub Pages / CDN"]:::cdn
    Browser["End-User Browser"]:::client
    External["Google Calendar API"]:::external

    Developer -->|"push code"| Repo
    Repo -->|"triggers workflow"| Workflow
    Workflow -->|"Jekyll build & deploy"| CDN
    Browser -->|"fetch assets"| CDN
    Browser -->|"load pages & scripts"| CDN
    Browser -->|"call API"| External

    click Repo "https://github.com/06samuel/simulation_app/tree/main//"
    click Workflow "https://github.com/06samuel/simulation_app/blob/main//.github/workflows/jekyll-gh-pages.yml"
    click HTML "https://github.com/06samuel/simulation_app/blob/main//*.html"
    click CSS "https://github.com/06samuel/simulation_app/blob/main//Proyek1/styles.css"
    click JS "https://github.com/06samuel/simulation_app/blob/main//Proyek1/main.js"
    click External "https://github.com/06samuel/simulation_app/blob/main//kalender_google.html"

    classDef repo fill:#D6EAF8,stroke:#21618C,color:#1B4F72
    classDef ci fill:#FDEBD0,stroke:#D68910,color:#A04000
    classDef cdn fill:#D5F5E3,stroke:#27AE60,color:#1E8449
    classDef client fill:#FCF3CF,stroke:#B7950B,color:#7D6608
    classDef actor fill:#FCF3CF,stroke:#B7950B,color:#7D6608
    classDef external fill:#EBEDEF,stroke:#839192,color:#566573
```
