All case studies

A portfolio the owner can edit himself, without touching code

Sanjay B

sanjay-b/overview.md
Role
Frontend engineer, CMS integration
Timeline
6 weeks
Team
1 designer, 1 developer
Category
Next.js
Sanjay B website

The challenge

The owner wanted a fast, polished site he could update on his own, plus a contact flow that filters spam while still reaching real clients.

How I solved it

  1. 1. WordPress as a headless CMS

    Content is edited in WordPress and delivered through the REST API, so the owner keeps a familiar editor and the site keeps modern performance.

  2. 2. Incremental regeneration

    Pages are rebuilt in the background when content changes, so edits go live quickly with no full redeploy.

  3. 3. Email OTP verification

    Enquiries are confirmed with a one-time code before they are sent, which blocks bots without a CAPTCHA.

architecture.txt
WordPress → REST API
Next.js → ISR pages
Contact form → OTP email → verified enquiry

What I learned

Splitting content from presentation worked well here. The owner edits in WordPress, Next.js handles delivery, and regeneration puts changes live without a redeploy.