About This Portfolio

This portfolio didn’t start as a “personal brand” project.

It started as a simple question:

“Can I build something clean, scalable, and actually mine — while I’m still learning?”

Most developer portfolios are static.
A few screenshots, some links, maybe a fancy animation — and that’s it.

I didn’t want that.

I wanted this portfolio to be a living system — something I can break, improve, refactor, and grow as my skills grow.

Why I Built It This Way

I’m a BCA student learning web development seriously.
Not a 10+ years experience dev. Not pretending either.

So instead of copying layouts or trends blindly, I focused on:

• Understanding structure over aesthetics
• Building reusable UI patterns
• Keeping everything simple but intentional
• Learning by actually shipping

This site is not meant to impress with buzzwords.
It’s meant to show how I think as a developer.

Design Philosophy (No Overkill)

I kept the design minimal on purpose.

Flashy UI can hide weak structure.
Clean UI exposes mistakes — which is perfect for learning.

The layout relies heavily on:

• spacing
• contrast
• consistent borders
• typography hierarchy

Instead of random colors, I use design tokens so themes can change without rewriting components.

:root {
  --bg: 248 248 248;
  --card: 255 255 255;
  --text: 15 23 42;
  --accent: 64 64 64;
  --border: 226 232 240;
}

.dark {
  --bg: 0 0 0;
  --card: 18 18 18;
  --text: 235 235 235;
  --accent: 180 180 180;
  --border: 45 45 45;
}

No unnecessary gradients. No fake depth.

Just clarity.

Tech Stack (What I Actually Use)

This portfolio is built using tools I’m actively learning and improving with:

• Next.js (App Router) — routing, layouts, performance
• React — component-based UI
• Tailwind CSS — fast, consistent styling
• Framer Motion — subtle animations, not distractions

MDX — content + components in one place

If something didn’t add value, I didn’t add it.

Why There’s a Blog Here

• I added a blog section for one reason:
• Writing forces clarity.
• Using MDX lets me mix:
• explanations
• code snippets
• visuals
• custom components

This blog isn’t about teaching experts. It’s about documenting my learning in public — mistakes included.

What This Portfolio Represents

This site is not a final product.

It’s:

• a playground
• a learning log
• a proof of consistency
• a system I’ll keep improving

I’m building. I’m learning. I’m shipping.

And this portfolio grows with me.