John Anderson — Portfolio Website
This multi-page portfolio: metadata-first, accessible, fast by default and built with a small static toolchain.
01 — Context
The challenge
The site you are reading is itself a case study. It is a static, multi-page portfolio with shared components, data-driven content, generated metadata, dark mode and a deliberately small JavaScript footprint.
A portfolio needs to be easy to update, quick to load and useful to both people and search engines. It also needs to feel like a designed object rather than a collection of disconnected pages.
02 — Approach
The solution
Each page is a standalone HTML document. Content lives in JSON, shared components live in partials, and a Node build script assembles the pages, injects SEO metadata and creates a sitemap and RSS feed. Runtime JavaScript only handles behaviour: navigation, theme, animation, filtering and form feedback.
03 — Build
What I built
Static by design
Every route is a real HTML file that can be served from any static host.
Metadata pipeline
SEO, Open Graph, Twitter cards and JSON-LD are generated from one JSON file.
Theme system
A light and dark theme driven by CSS custom properties and a saved preference.
Small runtime
Vanilla JavaScript modules for navigation, animation and form validation.
04 — Result
What the build demonstrates
- Fully rendered pages with metadata in the initial HTML response.
- A single source of truth for navigation, content and SEO.
- Accessible navigation, forms and reduced-motion support.
- No frontend framework or runtime CSS dependency.
“The useful constraint was to keep the build simple enough to understand in an afternoon. A portfolio should demonstrate judgement, and the architecture is part of the argument.”
Project reflection
Next step
Have a project like this in mind?
Tell me what you're trying to make. I'll reply with an honest view of the work and the next useful step.