How european-summer-of-code/esoc2026 works
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.