# frontman-git/dev-event architecture

> Architecture diagram of the GitHub repository frontman-git/dev-event, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-08-13). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/frontman-git/dev-event
- Repository: https://github.com/frontman-git/dev-event

## Overview

##### Project Type and Purpose
- This is a JAMstack-style, markdown-driven events listing website (“Dev-Event”) that aggregates developer events by month/year.
- All content lives as Markdown files (under `end_event/`, `replay_event/`, `review/`), and images/assets live under `static/`.
- The site is built and deployed as a static site (likely using a Static Site Generator such as Next.js or similar) and hosted on a CDN (Vercel).

##### File Structure Analysis
- Top-level:
- `.gitignore`, `.all-contributorsrc`, `README.md` – project metadata and contributor configuration.
- `end_event/` – past event data, one Markdown file per month.
- `replay_event/` & `review/` – special pages for replays and reviews.
- `static/` – banners, images, PPTX files used in content.
- No “src/” or “frontend/” directories because the generator is concealed; it’s purely content + config.
- Deployment probably orchestrated via Vercel’s Git integration (build hooks).

##### README Insights
- Shows badges linking to web app (`https://dev-event.vercel.app/events`) and mobile apps (Android/iOS) – the mobile apps are separate clients that consume the same underlying content or an API.
- Mentions Vercel, social links, sponsor banners: all static content.

##### Main Components
a. Content Repository (GitHub)
- Stores markdown (event data), static assets (`/static`), README, config.
b. CI/CD / Build Pipeline (Vercel)
- On push to `main`, triggers SSG build.
- Reads Markdown + assets, generates HTML/CSS/JS.
- Outputs published static files.
c. CDN / Static Hosting
- Serves static assets (HTML, images, CSS, JS) globally.
d. Web Client (Browser)
- User visits `dev-event.vercel.app` → static pages are delivered via CDN.
e. Mobile Clients (Android / iOS Apps)
- Could pull from the same static JSON or API endpoints hosted as serverless functions (if any), or directly scrape/consume a JSON data feed.
f. External Services
- GitHub for version control, Vercel for builds and hosting, any analytics or badge services.

##### Relationships & Data Flows
1. Developer pushes Markdown/asset change → GitHub repo.
2. Vercel webhook fires → CI/CD build → SSG reads content → outputs static files.
3. Generated static site is deployed to CDN.
4. Browser or Mobile App requests content → CDN returns static HTML/JSON/assets.

##### Architectural Patterns & Principles
- JAMstack (pre-build, serve via CDN)
- Content-as-Code (Markdown drives UI)
- CDN distribution for low latency and high availability
- CI/CD (push-to-deploy) via Vercel

## Diagram (Mermaid)

```mermaid
flowchart TB
    %% Source Layer
    subgraph "Source Layer"
        direction TB
        Repo["Content Repository (GitHub)"]:::content
        Past["Past Event Content\n(Markdown)"]:::content
        Replay["Replay Event Pages\n(Markdown)"]:::content
        Review["Review Pages\n(Markdown)"]:::content
        Assets["Static Assets\n(images, banners, PPTX)"]:::content
        Meta["Project Metadata & Config"]:::content
    end

    %% Build & CI/CD Layer
    subgraph "Build & CI/CD"
        direction TB
        Vercel["Vercel CI/CD & SSG"]:::build
        API["Serverless API Endpoints"]:::build
    end

    %% Delivery Layer
    subgraph "Delivery Layer"
        direction TB
        CDN["CDN / Static Hosting"]:::delivery
    end

    %% Client Layer
    subgraph "Client Layer"
        direction TB
        Browser["Web Browser"]:::client
        Android["Android App"]:::client
        iOS["iOS App"]:::client
    end

    %% External Services
    subgraph "External Services"
        direction TB
        GitHubExt["GitHub (Version Control)"]:::external
        Badge["Badge & Analytics Services"]:::external
    end

    %% Connections
    Repo -->|git push| Vercel
    Past --> Vercel
    Replay --> Vercel
    Review --> Vercel
    Assets --> Vercel
    Meta --> Vercel
    Vercel -->|build & generate| CDN
    Vercel -->|deploy JSON| API
    CDN -->|GET /events| Browser
    CDN -->|GET /events| Android
    CDN -->|GET /events| iOS
    Android -->|fetch JSON| API
    iOS -->|fetch JSON| API
    GitHubExt -->|webhook| Vercel
    Badge -->|embed badges| Meta

    %% Click Events
    click Repo "https://github.com/frontman-git/dev-event/tree/master//"
    click Past "https://github.com/frontman-git/dev-event/tree/master/end_event/"
    click Replay "https://github.com/frontman-git/dev-event/tree/master/replay_event/"
    click Review "https://github.com/frontman-git/dev-event/tree/master/review/"
    click Assets "https://github.com/frontman-git/dev-event/tree/master/static/"
    click Meta "https://github.com/frontman-git/dev-event/blob/master/README.md, .gitignore, .all-contributorsrc"

    %% Styles
    classDef content fill:#e0ffe0,stroke:#2d662d;
    classDef build fill:#e0f0ff,stroke:#2a4a73;
    classDef delivery fill:#fff4e6,stroke:#c46a00;
    classDef client fill:#f5e0ff,stroke:#7d3e7d;
    classDef external fill:#f0f0f0,stroke:#888888;
```
