How enactusftuhanoi/yearbook works
Project type and purpose
• This is a static web-based “yearbook” site (an open-source, content-driven project).
• Purpose: serve HTML pages (index.html, yearbook.html) enriched with images, audio, and video to showcase the Enactus FTU Hanoi community.
File structure
• Top-level assets:
• index.html, yearbook.html – main entry points
• media files (audio.mp3, video.mp4)
• (README points to assets/ for logos, though your provided tree is flattened)
• No backend code or server components—purely static.
README for additional insights
• Deployment likely via GitHub Pages or any static-site host.
• Contributors update content by forking, branching, and pull-request, implying a simple CI/CD pipeline (optional).
a. Main components
1. Developer Workstation (contributors)
2. Version Control (GitHub repo)
3. CI/CD Pipeline (optional: GitHub Actions or another)
4. Static Site Host (e.g., GitHub Pages, Netlify, Vercel)
5. End-User Browser
6. External Services (optional analytics, CDN for assets/media)
b. Relationships & data flow
• Developers → push code/content → GitHub
• GitHub triggers CI/CD → builds/deploys static assets → Host
• End-User Browser ↔ Host (HTTP GET index.html, yearbook.html, fetch assets & media)
• Browser may pull assets/media from CDN (if configured)
c. Architectural patterns/design principles
• Static site architecture (no server-side logic)
• Content-driven, declarative HTML pages
• Git-centric collaboration & deployment
d. Key technologies/frameworks
• HTML/CSS (no JS frameworks shown)
• Static hosting (GitHub Pages, Netlify, etc.)
• GitHub for version control and CI (GitHub Actions)
• Optional CDN for media
Detail and granularity
• How new media files flow through the pipeline (developer adds to media/ → GitHub → deploy → CDN).