# kookmin-sw/capstone-2025-05 architecture

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

- Interactive diagram: https://gitdiagram.com/kookmin-sw/capstone-2025-05
- Repository: https://github.com/kookmin-sw/capstone-2025-05

## Overview

##### Project type and purpose
- This is a static website (GitHub Pages) powered by Jekyll (or another Markdown‐to‐HTML generator).
- Its purpose is to host a “capstone team” landing page: project intro, team member profiles, usage instructions, and media.

##### File structure
- Top‐level files:
- _config.yml   → Jekyll/GitHub Pages configuration
- index.md      → the home page content in Markdown
- README.md     → project README (not part of the published site, but for repo instructions)
- There are no backend, API, build scripts, or tests: it’s purely a static content pipeline.

##### README for additional insights
- The README guides contributors on:
- Editing index.md for project intro
- Customizing the theme via GitHub Pages settings
- Using Markdown (headings, lists, images, links)
- It references GitHub Pages “Source = master” and theme chooser, implying the site build and serve pipeline is handled by GitHub.

a. Developer workstation
– Edits .md and _config.yml locally
– Commits & pushes to GitHub repo
b. GitHub Repository
– Hosts the source files
– Triggers GitHub Pages build
c. Jekyll / Pages Build Engine (on GitHub infra)
– Reads _config.yml + Markdown (.md)
– Applies theme/layouts → generates static HTML/CSS/JS
d. GitHub Pages CDN/Server
– Serves the generated static site at https://<org>.github.io/<repo>
e. End‐user’s Browser
– Requests pages, loads HTML/CSS/JS, renders site

##### Relationships and data flow
- Developer → (git push) → GitHub Repo
- GitHub Repo → (build trigger) → Pages Build Engine
- Build Engine → (artifact publish) → CDN
- Browser ↔ CDN (HTTP GET/response)

##### Architectural patterns/design principles
- Static Site Generation (SSG): separation between content (Markdown) and presentation (HTML templates/themes)
- Continuous Deployment: every git push auto‐triggers build & deploy
- CDN distribution for global performance

##### Relevant technologies/frameworks
- Git & GitHub
- Jekyll (or whichever static site generator GitHub Pages uses)
- Markdown
- GitHub Pages hosting & CDN

## Diagram (Mermaid)

```mermaid
flowchart TD
    subgraph "Developer Workstation"
        direction TB
        Content["Project Content (index.md)"]:::local
        Config["Site Configuration (_config.yml)"]:::local
    end
    Dev["Developer Workstation"]:::local
    Dev -->|"git push"| Repo[(GitHub Repo)]:::infra
    Content --> Dev
    Config --> Dev

    subgraph "GitHub Infrastructure"
        direction TB
        Repo[(GitHub Repo)]:::infra
        Document["Repository Documentation (README.md)"]:::infra
        Repo -.contains.-> Document
        Repo -->|"build trigger"| Build["Pages Build Engine (⚙️)"]:::infra
        Build -->|"publish artifacts"| CDN["GitHub Pages CDN (☁️)"]:::infra
    end

    Browser["End-user Browser"]:::user
    Browser -->|"HTTP GET"| CDN
    CDN -->|"HTTP response"| Browser

    click Content "https://github.com/kookmin-sw/capstone-2025-05/blob/master/index.md"
    click Config "https://github.com/kookmin-sw/capstone-2025-05/blob/master/_config.yml"
    click Document "https://github.com/kookmin-sw/capstone-2025-05/blob/master/README.md"

    classDef local fill:#cce5ff,stroke:#3399ff;
    classDef infra fill:#d4edda,stroke:#28a745;
    classDef user fill:#ffe5cc,stroke:#ff9900;
```
