How datthodai/11tyjamstackcmsproject works
Project Type & Purpose
• Project Type: JAMStack static site
• Purpose: A fast, responsive hamster-care blog built with Eleventy (11ty) and Nunjucks templates, deployed via Netlify, with content stored as Markdown and managed optionally through Netlify CMS.
Main Components
a. Content Source
– Markdown posts under src/blog (e.g., 2025-xx-xx.md)
– Static assets (images, CSS) under src/assets & public/assets
– Nunjucks templates in src/_includes
– Netlify CMS configuration (src/admin/config.yml)
b. Build Engine
– Eleventy CLI (.eleventy.js + package.json)
c. Repository & CI/CD
– Git repository (GitHub, GitLab, etc.)
– Netlify build hook (connected to repo)
d. Hosting & Delivery
– Netlify CDN and DNS
– Public URL / Live Demo endpoint
e. End Users
– Browsers on mobile/desktop.
Relationships & Data Flow
1. Developer writes or edits content (Markdown) and templates locally
2. Commits pushed to Git repository
3. Netlify CI pipeline triggers on each push
4. Eleventy reads Markdown + Nunjucks templates + assets → generates static HTML/CSS/JS in public/
5. Netlify deploys the generated static site to its CDN edge network
6. End user requests content; CDN serves prebuilt pages instantly
7. (Optional) Content editors use Netlify CMS admin UI to propose new posts—commits stored back to Git.
Architectural Patterns & Design Principles
• JAMStack separation: Content + Markup + Delivery are decoupled
• Static-first approach for speed and security
• Git-backed headless CMS for content management
• CI/CD pipeline enforces build consistency and atomic deployments
Technologies & Frameworks to Call Out
– Eleventy (11ty) static site generator
– Nunjucks for templating
– Netlify for hosting, CDN, and CMS integration
– Custom CSS variables and responsive design
– Markdown for content authoring