Most developer portfolios are static.

Most developer portfolios are static.

A hero section. A few projects. A contact form that goes nowhere.

That’s not how I build products — so it’s not how I built my portfolio.

I work on editorial platforms and CMS-driven systems used under real traffic.
My portfolio needed to reflect that.

So I built it like a production system, not a showcase.

Here’s what I did:

• Built with Next.js 15 + Payload CMS (runs inside the same app)
• CMS-first architecture — content updates without redeploy
• Graceful fallback — site works even if the database is down
• Client-side S3 uploads — avoids serverless limits on Vercel
• Structured SEO + JSON-LD from day one
• Performance-focused (image optimization, font preload, minimal JS)

One decision I’m really happy with:

→ Payload runs inside Next.js at /admin
→ One repo. One deploy. No separate CMS

The goal wasn’t just design.

It was to build something that behaves like the systems I actually ship —
structured, resilient, and built for real content.

Your portfolio isn’t just a page.

It’s a system.

If you’re building CMS platforms, your portfolio should behave like one.

Open to freelance / contract work in:

• Editorial platforms
• CMS architecture
• Full-stack systems

Let’s connect.