How ab9mamun/emil-website works
Main Components
a. Content Layer
• “content/”, “data/”, “static/”: Markdown, TOML, media, front‑matter templates.
• Forestry CMS (optional) for editing front matter (shown as an external CMS service).
b. Presentation Layer
• Hugo engine + Academic theme (“layouts/”, “assets/”, “config.toml”, “go.mod”).
• Custom SCSS/JS under “assets/” and “layouts/partials/”.
c. Build & CI/CD
• Git repository (GitHub/GitLab).
• Netlify Build (hooks into repo, runs hugo, runs scripts like utils/parse_talks.py, update_academic.sh).
d. Hosting & Delivery
• Netlify CDN serving the generated static HTML, CSS, JS.
• Optional viewer tooling (view.sh, local hugo server) for previews.
Relationships & Data Flow
• Developer edits content or code → commits to Git.
• Netlify notices push → runs the build pipeline:
• Clones repo → installs dependencies (go.mod & Hugo modules) → runs pre‑build scripts → hugo generates public/ folder.
• Deploys public/ to Netlify CDN.
• End‑user browser fetches assets from Netlify CDN.
• Forestry CMS (if enabled) updates content via Git commits.
Architectural Patterns & Principles
• Static Site Generation (SSG): separation of content, templates, and build.
• Theming & Extendability: Academic theme modules plus local overrides in “layouts/”.
• CI/CD pipeline: automated, Git‑driven continuous deployment.
• Modular configuration: top‑level config.toml plus environment overrides in config/_default/.
• Asset Pipeline: SCSS compilation, JS bundling via Hugo Pipes.
Technologies, Frameworks & Tools
• Hugo (Go-based SSG)
• Academic (Hugo) theme
• SCSS (via Hugo Pipes)
• Netlify (CI/CD, hosting, CDN)
• Git (version control)
• Forestry CMS (Git-based content editor)
• Python scripts for content preprocessing (utils/parse_talks.py)
• Shell scripts for init/setup (scripts/init_kickstart.sh)