How fronteers/website works
Project Type and Purpose
• This is a Jamstack‐style static site built with Eleventy (11ty).
• It generates a content‐driven website (Fronteers.nl) by converting Markdown, JSON, and Liquid templates into static HTML, CSS, and JS.
• Deployed on Netlify and served via CDN with CI provided by GitHub Actions.
High‐Level Architecture Components
a. Developer Environment
• Local file system: src/ (Markdown, templates, assets), utils/, package.json, Eleventy config .eleventy.js.
• Node.js/Elevnty CLI that reads content, data, and templates.
b. Version Control & Collaboration
• Git repository hosted on GitHub (.github/ workflows, issue templates).
• Contributors push feature branches, open PRs.
c. Continuous Integration
• GitHub Actions (.github/workflows/) runs linting, formatting (Prettier), link checks, and Eleventy builds.
d. Build Process
• Eleventy reads:
– src/_data/ JSON/JS data
– src/_includes/ Liquid layout & partials
– src/_components/ paired JavaScript/CSS components
– src/_assets/ CSS/JS/images/fonts
– Markdown under src/en/, src/nl/, etc.
• Applies transforms (utils/transforms.js) and filters (utils/filters.js)
• Outputs to _site/ (static HTML/CSS/JS)
e. Deployment & Hosting
• Netlify (netlify.toml) picks up the build, runs npm run build (Eleventy), and deploys output.
• Static assets served from CDN with instant cache invalidation.
f. External Services
• GitHub (source, PRs, actions)
• Netlify (build, deploy, hosting)
• Slack (community link)
Relationships & Data Flow
1. Developer edits source files → commits to GitHub.
2. Push/PR triggers GitHub Actions workflow → runs lint/build tasks.
3. Eleventy build → transforms content + templates + assets → produces static site.
4. Netlify receives built artifacts → deploys to CDN.
5. End users request pages → served from CDN.
Architectural Patterns & Principles
• Jamstack: Pre‐built markup, decoupled frontend, CDN delivery.
• Content‐as‐Code: Markdown/JSON under version control.
• Modular components: CSS/JS under src/_components/ for reusability.
• Separation of concerns: Data (src/_data), templates (src/_includes), assets (src/_assets).