Next.js Experience
App Router, SSR, and production deployments — this site is the case study.
Overview
How I've used Next.js
Next.js is my framework of choice for any project that needs to be fast, SEO-friendly, and genuinely production-grade rather than a single-page app bolted onto a CMS.
This portfolio is built end-to-end in Next.js 14 with the App Router — static generation for marketing pages, dynamic routes for case studies and blog posts, a server-rendered API route handling contact form submissions into a Postgres database, dynamically generated Open Graph images, and a sitemap that regenerates itself from the underlying data instead of going stale. It's deployed via a CI/CD pipeline (GitHub Actions → VPS, PM2 process management) rather than a one-click host, which means handling real production concerns: environment variables, build steps, and zero-downtime restarts.
What I can do
Specific Next.js capabilities
- ✓App Router architecture — layouts, nested routes, server/client components
- ✓Static generation (SSG) and server-side rendering (SSR) where each is appropriate
- ✓API routes for backend logic (form handling, database writes, third-party integrations)
- ✓Dynamic metadata, sitemaps, and Open Graph image generation
- ✓Production deployment — CI/CD pipelines, environment configuration, process management
FAQ
Common questions about my Next.js work
What parts of this site demonstrate real Next.js production experience?+
The contact form (API route → Postgres → branded email sends), the dynamically generated sitemap and OG images, and the CI/CD deploy pipeline to a self-managed VPS — all things a marketing-only site wouldn't need, which is exactly why they're useful proof points.
Related skills