Website Stack
My Portfolio Architecture
A code-first CMS, in-process rendering & on-demand cache invalidation
- Platform
- Frontend
- Product Engineering
- Next.js
- Headless CMS
- Rendering Strategies
- PostgreSQL
- System Design
- Scalability
Overview
With my target audience and the problem to solve defined, the next question was how this solution would be implemented. Given the solution implied a robust Information Architecture (IA), content cross referencing and personalised [company] routes, i knew i'd need a flexible CMS, one that played well into my stack's core: React / Next.
Content lives code-first in Payload collections. Pages render through an in-process Local API. A GraphQL endpoint stays exposed but off the render path. A single revalidateSite() makes a publish go live in seconds. The stack splits across Vercel (app), Railway (Postgres), and Vercel Blob (media).
