Portfolio + Blog Website

A personal portfolio and blog built with Next.js 16 and TypeScript.
It showcases my work, writing, and experience while also functioning as a reusable template that other developers can adapt by updating a few configuration values.

Overview

The site is designed to be clean, fast, and easy to customize.
It presents my projects and background in a structured way, while the underlying architecture keeps content manageable and scalable.

Tech Stack

Core Technologies

This project is powered by Next.js 16 and TypeScript, chosen for their reliability, modern features, and strong ecosystem.

Content System

I use Content Collections to manage Markdown/MDX content.
It replaced my initial plan to use Contentlayer, which is no longer maintained and currently incompatible with Next.js 16.

Design & Interaction

  • Tailwind CSS for styling
  • GSAP for animations
  • Lenis for smooth scrolling
    Together, these create a consistent and polished visual experience.

Design & Credits

The visual design is inspired by the portfolio created by Saurabh Chandre.
I came across his site — schar.dev — and admired its simplicity and interaction quality. Rebuilding it became a personal challenge to study its structure and polish.

I contacted Saurabh during development, and he was incredibly open and helpful, offering clarity on a few design choices. I genuinely appreciate his support.

Development Notes

While building the site, I focused on keeping things modular and easy to extend. Some highlights:

  1. Template-first structure driven by metadata
  2. Clean code organization across components, hooks, and UI utilities
  3. Smooth scroll behaviour and focused animation performance
  4. MDX-powered blog with custom components and syntax highlighting

I’m continuing to refine transitions, layout spacing, and smaller UI details to make everything feel cohesive.

Repository Availability

The source code will be published soon.
Before releasing it, I’m finalizing:

  • minor design and animation refinements
  • cleanup and optimization
  • documentation improvements
  • a more polished project structure

Once everything is ready, I’ll make the GitHub repository public.