How jannikmenzel/ifsr-website works
Project Type and Purpose
• This is a static website generated with the Hugo SSG framework.
• It serves as the official information portal for TU Dresden’s iFSR, using Markdown content, templates, and assets to produce a fully static site.
Main Components
a. Content Layer
• content/ (Markdown pages)
• data/navigation.toml (menu structure)
• archetypes/ (front‐matter templates)
b. Presentation Layer
• layouts/ (Hugo templates: base, section, single, partials, shortcodes)
c. Build Engine
• Hugo CLI / Server
• hugo.toml (site config)
• GitHub Actions (.github/workflows/hugo.yaml) for CI/CD
d. Hosting & Delivery
• Static host (e.g., Netlify, GitHub Pages) serving the generated public/ output
• Browser clients requesting HTML/CSS/JS
Relationships & Data Flow
1. Developer Workflow
• Developer pushes content/layout changes → GitHub repo
• CI Workflow triggers Hugo build
2. Build Process
• Hugo reads content/, data/, archetypes/
• Hugo applies layouts/ and processes assets/
• Generates final static files in public/
3. Deployment
• CI pushes public/ to hosting provider
• Hosting serves assets to end users’ browsers
4. Runtime
• Browser requests HTML/JS/CSS
• Assets loaded from CDN or static host
Architectural Patterns & Design Principles
• Static Site Generation: pre-rendering all content at build time
• Separation of Concerns:
• Content vs. Layout/Template vs. Assets vs. Data
• Template Inheritance: base templates + partials + shortcodes
• Continuous Deployment: Git → CI → Hugo → Hosting