How benlf1/littlelink works
Project type and purpose
• LittleLink is a minimalist, self-hosted, static “link tree” site generator. It comprises only HTML, CSS, fonts, and images—no build step or front-end framework. It can be served directly via any static-site host or via a simple container.
File structure
• Top-level assets:
• index.html, privacy.html – the two pages served
• css/ – style.css (theme logic), reset.css, brands.css (100+ branded button styles)
• fonts/, images/ – static resources
• Config and infra:
• docker/ – Dockerfile, compose.yaml, .dockerignore for containerized hosting
• .github/workflows/contrast-check.yml – CI job for accessibility checks on brand CSS
• No JS source code—pure vanilla HTML/CSS.
README insights
• Describes theming (auto/light/dark via CSS variables), accessibility (contrast checks), performance (100/100 metrics), and multiple deploy targets: Vercel, Netlify, Amplify, GitHub Pages, Docker.
• Points out an optional “LittleLink-Server” project for dynamic back-ends, but core is static.
Main components & relationships
a. Components
1. Developer Workstation (dev tools, git CLI)
2. GitHub Repository (source: HTML/CSS/fonts/images + Docker assets + CI workflows)
3. Continuous Integration (GitHub Actions: contrast-check.yml)
4. Build/Package Artifact (in this case, just source files; optionally built Docker image)
5. Hosting Environment(s):
– Static-site hosts (Vercel/Netlify/Amplify/GitHub Pages)
– Docker Container (built from docker/Dockerfile, served on localhost:8080 or any container host)
6. CDN/Edge Cache (e.g., automatically provided by Vercel/Netlify)
7. End User Browser (mobile/desktop)
8. External Service: Fathom Analytics (privacy-focused analytics insert)
b. Relationships & Data Flows
– Developer pushes to GitHub → triggers GitHub Actions → runs contrast/accessibility checks → on success, artifacts deployed
– CI (or manual Docker build) → produces Docker image → pushed to container registry (optional) or deployed directly
– Hosting Environment pulls static assets (or container) → serves via CDN
– End User Browser sends HTTP(S) requests → CDN/Host returns HTML/CSS/fonts/images
– Browser executes Fathom Analytics snippet → analytics data sent to Fathom
c. Architectural patterns & principles
– Static-first: no server-side logic, minimal attack surface, excellent performance & caching
– Theming via CSS variables, no JavaScript dependency
– Accessibility as a first-class citizen: CI checks for contrast ratios
– Deploy-anywhere: Git-driven, zero config required beyond dropping files
d. Key technologies
– HTML5, CSS3 (variables, resets)
– Docker (Dockerfile, docker-compose)
– GitHub Actions for CI
– Static-site hosts (Vercel, Netlify, Amplify, GitHub Pages)
– Fathom Analytics
Detail without over-splitting
• Every folder’s purpose under “source” (css/, fonts/, images/, pages)
• Docker folder as its own sub-component in the builder step
• Contrast-check CI job as part of quality gates
• Identifies static assets and their flow from dev to end-user
• Shows the CI/CD pipeline and quality checks
• Illustrates multiple hosting options and runtime environments
• Highlights external analytics integration