How estraviz/blog works
Project type and purpose
• This is a static website and personal blog built with the Hugo static‐site generator, using Markdown content, Hugo layouts, SCSS assets, and a Cactus theme. It is deployed automatically via Netlify (and has a GitHub Actions workflow defined).
File structure
• Top‐level:
• content/ ← Markdown source for pages and blog posts
• layouts/ ← Hugo templates & shortcodes
• themes/cactus/ ← Theme files (partials, templates, assets)
• resources/_gen/ ← Auto‐generated assets (compiled SCSS→CSS)
• static/ ← Static assets (images, fonts) copied verbatim
• config.toml ← Site configuration (params, menu, theme)
• data/projects.json ← Data file for use in templates
• .github/workflows/hugo.yml ← CI pipeline to build site
• netlify.toml ← Netlify build & deploy settings
• Patterns:
• Static‐site generator pipeline
• Template‐content separation (MVC/L → V → C)
• Asset pipeline for SCSS compilation
README for additional insights
• Confirms use of Hugo and Netlify
• No additional architectural sections, so we infer from build files
a. Main components:
1. Developer’s local environment (writes Markdown, templates, SCSS)
2. GitHub repository (source code, config, content, CI workflow)
3. CI/CD:
• GitHub Actions (optional)
• Netlify Build (runs hugo)
4. Hugo engine (core static‐site generator):
• Reads config.toml
• Loads content/* and data/*
• Applies layouts from layouts/ and themes/cactus/
• Runs resource pipeline (SCSS→CSS)
• Writes final HTML/CSS/JS to public/
5. CDN / Static hosting (Netlify’s CDN)
6. End users (browsers requesting static files)
b. Relationships and interactions:
• Developer pushes to GitHub → triggers CI (GitHub Actions or Netlify)
• CI invokes Hugo build → processes content+layouts+assets → outputs public/
• Netlify publishes public/ to global CDN
• Browser requests static files from CDN → site is rendered to visitor
c. Architectural patterns / design principles:
• Static‐site generator model (write → generate → serve)
• Separation of concerns: Markdown content vs. HTML templates vs. styles
• Asset pipeline for on‐the‐fly SCSS compilation
• GitOps / CI‐driven deployment
d. Key technologies/frameworks/libraries:
• Hugo (Go-based SSG)
• Go templates + shortcodes
• SCSS → rendered via Hugo Pipes
• Netlify build/deploy
• GitHub Actions (hugo.yml workflow)
• Cactus Hugo theme