Rebuilding my portfolio: Next.js, Payload CMS and a database I control
My old portfolio was a static page I had outgrown — every new project meant editing markup by hand. I rebuilt it as a real product: Next.js and Payload CMS on my own Postgres, with projects, posts and socials managed from an admin panel. What the rebuild involved, and the two failures that taught me the most.

The old site did its job for a while. It was also a ceiling: adding a project meant editing HTML, wiring an image by hand and redeploying, and the case studies I wanted to write had nowhere to live. I did not need a prettier page — I needed the portfolio to work like the products I build for other people.
A CMS, but on my own database
The stack is Next.js with Payload CMS running inside the same application, backed by PostgreSQL on Supabase, with media in S3-compatible storage. Payload mattered for one reason above the rest: the content lives in a database I control, in tables I can inspect, instead of inside a hosted page-builder I would have to trust and rent forever. Projects, blog posts and even my social links are rows I can edit from an admin panel — publishing a case study no longer touches code.
Two homes for content, on purpose
Not everything belongs in a CMS. The copy that almost never changes — my bio, the skills grid, the words on the home page — lives in JSON files in the repository, validated when the site builds, so a missing field fails the build instead of quietly shipping a blank section. The catalog that changes — projects, posts, links — lives in the database. One rule keeps it sane: a piece of text lives in exactly one of the two homes, never both.
What fought back
Two failures are worth writing down. The first: the admin panel passed every functional check I threw at it — register, login, upload, all green — while rendering completely unstyled, because one stylesheet import was missing. It taught me to verify the rendered page, not just the endpoints; users never see your API responses. The second: on mobile, the page scrolled sideways. The culprit was my own scroll animations, whose elements rest off-canvas until they enter view — at rest, every measurement passed, and only measuring during the scroll caught it. That check is now a script that sweeps every route at phone widths before anything ships.
Where it stands
The home page now counts its own statistics from the database — projects and technologies are live numbers, not claims I typed once and forgot. The contact form runs end to end with spam protection, and the whole site ships in light and dark themes. The portfolio stopped being a page about my work and became part of it — it is, fittingly, one of the case studies on it.