Building My Portfolio Website: A Journey in Next.js

January 13, 2026 (7mo ago)

Building My Portfolio Website: A Journey in Next.js

Hey there! Welcome to my first blog post on this newly minted portfolio website. Today, I want to share the story behind how this site came to be, the technologies I chose, and some of the challenges I faced along the way.

Why Next.js?

When I started planning this portfolio, I knew I wanted something that could handle both static content (like this blog) and dynamic interactions. Next.js 14 with the App Router was the perfect choice because:

The Tech Stack

Here's what powers this website:

Frontend Framework

Styling & UI

Content & Blog

Development Tools

Key Features Implemented

1. Responsive Design

The site works beautifully on all devices, from mobile phones to desktop screens. Tailwind's responsive utilities made this a breeze.

2. Dark Mode Toggle

A seamless dark/light mode switch that respects user preferences and persists across sessions.

3. Interactive Components

4. Blog System

This very blog you're reading! Built with MDX for easy content creation and a clean reading experience.

Challenges & Learnings

Tooltip Z-Index Issues

One of the first challenges I faced was tooltips getting hidden behind other content. The solution was carefully managing z-index values and using CSS specificity when needed.

Animation Timing

Getting the BlurFade animations to feel natural took some experimentation with delays and easing functions. The key was using consistent timing across all components.

MDX Processing

Setting up the MDX pipeline with syntax highlighting and GitHub Flavored Markdown support required understanding unified.js and its ecosystem.

Performance Optimizations

Future Plans

This is just the beginning! I plan to add:

Conclusion

Building this portfolio has been an incredible learning experience. It combines everything I love about modern web development: performance, accessibility, and great user experience.

If you're reading this, thanks for stopping by! Feel free to explore the code on GitHub and reach out if you have any questions or feedback.

Happy coding! 🚀


This post was written on January 13, 2026, using the very blog system described herein.