PublishedFull-Stack Developer

Nilay Naha Portfolio (Next.js + Headless CMS)

January 19, 2026
https://nilay-naha-portfolio.vercel.app
Nilay Naha Portfolio (Next.js + Headless CMS)
Position / Role

Full-Stack Developer

Deployment

Published

Timeline

Jan 2026

Primary Artifact

My portfolio is a full-stack Next.js web app with its own headless CMS, a free AI assistant and recruiter tools. I built it so I can update everything from my phone, and it costs ₹0 a month to run.

₹0Monthly running cost
0Paid AI API keys
7Shared content topics
The home page
The home page

The problem

Template portfolios are static: every content change means editing code and redeploying. I wanted a site I could keep up to date without touching code, that helps recruiters quickly, and that stays completely free to host.

How it works

  • Headless CMS behind /admin: projects (with case-study fields), blog posts, About, testimonials, the home hero and chatbot answers. Drafts stay private until published, and every save updates the live site immediately.
  • Free AI assistant: a small answer engine over my live content, using BM25 search and intent detection. No paid LLM, and it never invents facts.
  • Recruiter tools: job-description match (/match), a tailored one-page résumé, and a Ctrl + K command palette.
  • Discoverable: JSON-LD, sitemap, llms.txt, a public read-only MCP server and OpenAPI docs at /api-docs.
  • Fast: public data served from a server cache, cleared on every CMS save, with heavy effects loaded only after the page is ready.
The projects page with topic filters
The projects page with topic filters
Job-description match for recruiters (/match)
Job-description match for recruiters (/match)

Tech stack

Next.js 14 TypeScript Tailwind CSS Framer Motion MongoDB Atlas Mongoose Vercel PWA

Challenges & solutions

  • Slow first loads: every visit queried the database. I moved public API reads to a tagged server cache that each CMS save clears.
  • 3D mascot hurting performance: a three.js model loaded on every page, and mobile browsers dropped its WebGL contexts. I replaced it with a single small image.
  • Security for a personal admin panel: signed expiring sessions, login throttling, rate limits, a Content Security Policy and an audit log.
A blog article with a sticky table of contents
A blog article with a sticky table of contents
Interactive API docs (/api-docs) with the public MCP server
Interactive API docs (/api-docs) with the public MCP server

What's next

More write-ups and more curated chatbot answers.

Live site → Source code →

Case Study

Monthly cost

₹0

Free tiers only

Paid AI keys

0

Answer engine runs on site content

  1. Problem

    Template portfolios are static: every content change means editing code and redeploying. I wanted a site I could update without code, that helps recruiters fast, and that is free to run.

  2. Approach

    • Built a headless CMS behind /admin for all content
    • Added a free answer engine (BM25 + intents) over live content instead of a paid LLM
    • Added recruiter tools: job match, tailored résumé, command palette
    • Cached public data on the server, cleared on every CMS save
  3. Results

    • Runs at ₹0/month on free tiers
    • Content updates go live instantly without redeploying