Building My Portfolio with Next.js, GSAP & Motion
This portfolio is not just a collection of projects — it’s an experiment in interaction, motion, and performance. I built it to reflect how I think about frontend engineering: clean logic, subtle motion, and zero unnecessary noise.
1. Why I Needed a Custom Portfolio
- Most portfolios felt static and forgettable
- I wanted motion to feel intentional, not decorative
- Performance and smoothness mattered more than visuals alone
- I needed full control over routing and transitions
2. Key Technologies Used
3. Architecture Decisions
- App Router with nested layouts
- GSAP-driven global page transitions
- Client components only where interaction is required
- Reusable UI primitives instead of heavy components
4. Motion Philosophy
Motion is used only when it improves clarity or flow. Page transitions hide layout shifts, micro-animations guide attention, and nothing runs without purpose.
MALAY
Crafted at 2AM by MalayPatel
“Powered by creativity, fueled by caffeine and created in dark mode.”
. All rights reserved.