The Problem With Developer Portfolios
Most developer portfolios look the same: a hero section, a grid of project cards, a contact form. They optimise for showing what you built, not how you think.
I wanted something different — a space that felt more like a magazine than a résumé.
The Approach
Inspired by Medium, Substack, and long-form journalism sites, I designed the portfolio around reading experience:
- Centered column layout — max-width 680px, generous whitespace
- Editorial typography — Merriweather for headings, Inter for body
- Minimal chrome — no sidebars, no widgets, no distractions
- Content-first — articles and case studies as the primary content
Technical Decisions
- Next.js 16 with App Router for static generation
- Tailwind CSS for design tokens and utility-first styling
- Framer Motion for subtle scroll animations
- JSON-based CMS for articles and work items — no external dependencies
Impact
The editorial approach attracted a different calibre of visitors. Instead of recruiters scanning for tech stacks, I started getting messages from founders who resonated with how I think about products.
Lessons Learned
Your portfolio is a product. Treat the visitor as a user. What experience do you want them to have? For me, the answer was: thoughtful, unhurried, and clear.