How eavesofit/eavesofit-blog works
Project type and purpose
• This is a static blog built with Jekyll (a Ruby-based static site generator).
• README confirms it’s the main repo for a personal blog (“eavesofit-blog”).
File structure
• Top-level files:
– Gemfile/Gemfile.lock: Ruby dependencies (Jekyll + plugins)
– _config.yml: Jekyll configuration (site metadata, permalink style, plugins)
– .gitignore: files excluded from VCS
– index.html / index.markdown: homepage templates or content
• Posts directory: _posts/ contains Markdown or HTML files for each blog post.
• 404.html: custom 404 page.
• No “src” or “backend” folders—everything is static.
Key insights from README
• Confirms it’s a blog repo—no runtime server or API layer; all pages are pre-rendered.
Main components
a. Content source
– Markdown files in _posts/, index.markdown, custom pages (404.html)
– Static assets (CSS, JS, images) if present
b. Configuration & templates
– _config.yml (sitewide settings)
– Layouts and includes (not shown in file tree, typically in _layouts/ or _includes/)
c. Build engine
– Jekyll (Ruby gem invoked via jekyll build or jekyll serve)
d. Output artifact
– Generated static files (HTML, CSS, JS) in _site/ (not checked into Git)
e. Hosting platform
– GitHub Pages (or any static-site host)
f. End user
– Browser receiving rendered pages
Relationships and data flow
• Author commits Markdown + config → Git repository
• CI or local build invokes Jekyll engine with templates + content + config
• Jekyll processes Liquid tags and Markdown → generates static HTML/CSS/JS in _site/
• Host (e.g., GitHub Pages) deploys contents of _site/ to a CDN or web server
• End user’s browser requests pages → served by static host
Important architectural patterns
• Static Site Generation (SSG)
• Template-driven rendering (Liquid templates)
• Git-based deployment (push to main branch triggers rebuild on GitHub Pages)