# european-summer-of-code/esoc2026 architecture

> Architecture diagram of the GitHub repository european-summer-of-code/esoc2026, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-02-13). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/european-summer-of-code/esoc2026
- Repository: https://github.com/european-summer-of-code/esoc2026

## Overview

##### What this project is (type + purpose)
This repository is **not an application runtime** (no `src/`, no code, no services). It’s a **content/documentation repository** used to publish and maintain:

- The **European Summer of Code (ESoC) 2026 program information** (root `README.md`)
- An **archive of prior year project listings/cards** (e.g., `esoc2025/` with `cards/*.md`)
- A set of **external entry points** (ESoC website, LinkedIn, Discord, Office forms, GitHub Discussions) referenced from the docs

##### What the file tree tells you (structure → architecture)
Top level:
- `README.md`: the main “landing page” for 2026 information, timelines, guides, and pointers.
- `esoc2025/README.md`: previous-year (2025) page.
- `esoc2025/cards/*.md`: individual **project cards** (examples: `PTF.md`, `aptamer.md`, `prefix-dev.md`, etc.)

This strongly suggests a **content model**:
- “Program Guide” content (central index/landing pages)
- “Project Cards” content (many small, repeatable docs)
- “Year-based namespaces” (e.g., `esoc2025/`), implying `esoc2026/` may appear later.

##### What the README implies (runtime interactions are external)
The README includes multiple external integrations that matter architecturally:

**External systems**
- **Public website**: https://www.esoc.dev (likely the canonical public-facing surface)
- **Office forms** (applicant registration, sponsor onboarding, OSS onboarding)
- **GitHub Discussions** (Q&A forum)
- **Discord** (events)
- **LinkedIn** (communications)

These are “dependencies” of the documentation system because the docs drive traffic to them and define process.

##### Main components to include (separate into as many components as reasonable)
For this repo, “components” are largely **content + channels + intake**:

##### Content source of truth
- GitHub repo
- Year folders (e.g., `esoc2025/`)
- Project cards

##### Publishing / distribution
- GitHub Markdown rendering
- esoc.dev (public website)

##### Application/intake
- Office Forms: applicant registration form
- Office Forms: sponsor form
- Office Forms: open source onboarding form

##### Community & comms
- GitHub Discussions (Q&A)
- Discord (events)
- LinkedIn (announcements)

##### Operational org structure
- Hubs (France/probabl, Germany/GCOS-AI, Italy/FBK) as organizational nodes influencing processes and timelines

That combination will be “most accurate” for this project because it reflects what actually exists: a documentation-driven process hub with external operational dependencies.

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% =======================
    %% System Context (Top)
    %% =======================
    subgraph "System Context (People + External Channels)"
        direction TB

        A1["Applicants"]:::actor
        A2["Sponsors / Organizations"]:::actor
        A3["Open-source Maintainers"]:::actor
        A4["ESoC Coordinators / Repo Maintainers"]:::actor

        E1(["ESoC Website (esoc.dev)"]):::surface
        E2(["GitHub Repository UI (Markdown Viewer)"]):::surface

        X1(["Applicant Registration (Office Form)"]):::intake
        X2(["Sponsor Onboarding (Office Form)"]):::intake
        X3(["OSS Onboarding (Office Form)"]):::intake

        C1(["GitHub Discussions (Q&A)"]):::community
        C2(["Discord (Events)"]):::community
        C3(["LinkedIn (Announcements)"]):::community

        O1["Hub: France (probabl)"]:::org
        O2["Hub: Germany (GCOS-AI)"]:::org
        O3["Hub: Italy (FBK)"]:::org
    end

    %% =======================
    %% Publishing / Distribution (Middle)
    %% =======================
    subgraph "Documentation Publishing / Distribution"
        direction TB

        P0["ESoC Content Repository (Markdown)"]:::repo
        P1["Static Site Build / Publishing Mechanism (TBD)"]:::pipeline
        P2["Public Consumption Surfaces"]:::group

        P2a(["esoc.dev Pages"]):::surface
        P2b(["GitHub Markdown Rendering"]):::surface
    end

    %% =======================
    %% Repo Information Architecture (Bottom)
    %% =======================
    subgraph "Repo Information Architecture (Content Model)"
        direction TB

        R0["2026 Program Information (Main Landing Page)"]:::content
        R1["2025 Archive (Year Namespace)"]:::content
        R2["2025 Archive Index Page"]:::content
        R3["Project Cards (Markdown Content Type)"]:::content

        subgraph "Example Project Cards (esoc2025/cards/*.md)"
            direction TB
            C_01["Project Card: PTF"]:::card
            C_02["Project Card: aptamer"]:::card
            C_03["Project Card: ecospecs"]:::card
            C_04["Project Card: electrolux"]:::card
            C_05["Project Card: gcos-esoc2025-batches"]:::card
            C_06["Project Card: gcos-esoc2025"]:::card
            C_07["Project Card: hyperactive"]:::card
            C_08["Project Card: prefix-dev"]:::card
        end
    end

    %% =======================
    %% Connections (Typed Flows)
    %% =======================

    %% People consume published content
    A1 -->|"Read/View"| E1
    A1 -->|"Read/View"| E2
    A2 -->|"Read/View"| E1
    A3 -->|"Read/View"| E1
    A3 -->|"Read/View"| E2

    %% Maintain / edit content
    A4 -->|"Edit/Commit"| P0

    %% Publish / deploy (mechanism intentionally TBD)
    P0 -->|"Publish/Deploy"| P1
    P1 -->|"Publish/Deploy"| P2
    P2 -->|"Serve"| P2a
    P2 -->|"Serve"| P2b

    %% Public surfaces correspond to external viewing systems
    P2a -->|"Public Portal"| E1
    P2b -->|"Repo Viewer"| E2

    %% Docs link users to intake/community channels
    E1 -->|"Link-out"| X1
    E1 -->|"Link-out"| X2
    E1 -->|"Link-out"| X3
    E1 -->|"Link-out"| C1
    E1 -->|"Link-out"| C2
    E1 -->|"Link-out"| C3

    E2 -->|"Link-out"| X1
    E2 -->|"Link-out"| X2
    E2 -->|"Link-out"| X3
    E2 -->|"Link-out"| C1
    E2 -->|"Link-out"| C2
    E2 -->|"Link-out"| C3

    %% Submissions / participation
    A1 -->|"Submit"| X1
    A2 -->|"Submit"| X2
    A3 -->|"Submit"| X3

    %% Discuss / attend / follow
    A1 -->|"Discuss"| C1
    A2 -->|"Discuss"| C1
    A3 -->|"Discuss"| C1

    A1 -->|"Join/Attend"| C2
    A3 -->|"Join/Attend"| C2

    A1 -->|"Follow"| C3
    A2 -->|"Follow"| C3
    A3 -->|"Follow"| C3

    %% Hubs influence coordination and program operations
    O1 -->|"Coordinate"| A4
    O2 -->|"Coordinate"| A4
    O3 -->|"Coordinate"| A4

    %% Repo content mapping into source-of-truth box
    P0 -->|"Contains"| R0
    P0 -->|"Contains"| R1

    %% Year namespace structure
    R1 -->|"Includes"| R2
    R1 -->|"Includes"| R3
    R3 -->|"Instances"| C_01
    R3 -->|"Instances"| C_02
    R3 -->|"Instances"| C_03
    R3 -->|"Instances"| C_04
    R3 -->|"Instances"| C_05
    R3 -->|"Instances"| C_06
    R3 -->|"Instances"| C_07
    R3 -->|"Instances"| C_08

    %% =======================
    %% Click Events (from component_mapping)
    %% =======================
    click R0 "https://github.com/european-summer-of-code/esoc2026/blob/main/README.md"
    click R1 "https://github.com/european-summer-of-code/esoc2026/tree/main/esoc2025/"
    click R2 "https://github.com/european-summer-of-code/esoc2026/blob/main/esoc2025/README.md"
    click R3 "https://github.com/european-summer-of-code/esoc2026/tree/main/esoc2025/cards/"
    click C_01 "https://github.com/european-summer-of-code/esoc2026/blob/main/esoc2025/cards/PTF.md"
    click C_02 "https://github.com/european-summer-of-code/esoc2026/blob/main/esoc2025/cards/aptamer.md"
    click C_03 "https://github.com/european-summer-of-code/esoc2026/blob/main/esoc2025/cards/ecospecs.md"
    click C_04 "https://github.com/european-summer-of-code/esoc2026/blob/main/esoc2025/cards/electrolux.md"
    click C_05 "https://github.com/european-summer-of-code/esoc2026/blob/main/esoc2025/cards/gcos-esoc2025-batches.md"
    click C_06 "https://github.com/european-summer-of-code/esoc2026/blob/main/esoc2025/cards/gcos-esoc2025.md"
    click C_07 "https://github.com/european-summer-of-code/esoc2026/blob/main/esoc2025/cards/hyperactive.md"
    click C_08 "https://github.com/european-summer-of-code/esoc2026/blob/main/esoc2025/cards/prefix-dev.md"

    %% =======================
    %% Styles (Color + Shapes)
    %% =======================
    classDef actor fill:#ffffff,stroke:#374151,stroke-width:1.5px,color:#111827
    classDef repo fill:#dbeafe,stroke:#1d4ed8,stroke-width:2px,color:#0b1220
    classDef content fill:#bfdbfe,stroke:#2563eb,stroke-width:1.5px,color:#0b1220
    classDef card fill:#93c5fd,stroke:#1d4ed8,stroke-width:1.5px,color:#0b1220
    classDef pipeline fill:#e0f2fe,stroke:#0284c7,stroke-width:2px,color:#0b1220
    classDef surface fill:#dcfce7,stroke:#16a34a,stroke-width:2px,color:#052e16
    classDef intake fill:#ffedd5,stroke:#f97316,stroke-width:2px,color:#3b1d00
    classDef community fill:#e5e7eb,stroke:#6b7280,stroke-width:2px,color:#111827
    classDef org fill:#f3e8ff,stroke:#7c3aed,stroke-width:2px,color:#1f1147
    classDef group fill:#f0fdf4,stroke:#22c55e,stroke-width:1.5px,color:#052e16,stroke-dasharray: 4 3
```
