Why I Built My Portfolio
I built my portfolio to have a place that genuinely reflects how I design and build things, instead of relying on a standard template. I wanted to bring my web, mobile, and UI/UX work together in one experience, while experimenting with interactions, case studies, and a few features I don't usually get to build for client projects. It also gave me a chance to create something that feels personal and evolves with my work.
How I Built My Portfolio
I built the portfolio with Next.js, TypeScript, and Tailwind CSS, using Framer Motion for interactions and animations. Supabase powers the community wall, authentication, and user submissions, while Resend handles contact form emails. I designed the project structure around dynamic pages for different types of work, with galleries and case-study content for individual projects. I also focused on responsive layouts so the experience works smoothly across desktop and mobile.
Challenges in Creating My Portfolio
One of the biggest challenges was balancing visual design with a smooth, practical user experience. I wanted the portfolio to feel interactive without making it slow or difficult to navigate. Building features like the community wall, authentication, moderation, editable submissions, project galleries, and contact form also required more work than a typical portfolio. Making everything responsive across different screen sizes was another challenge, especially for the more interactive parts of the site.
How I Overcame Those Challenges
I tackled each challenge by breaking the project into smaller features and solving them one at a time. I kept the UI focused on usability while using Framer Motion selectively for interaction and animation. For the community features, I used Supabase Auth and database functionality with a private moderation flow. I also tested the layouts across different screen sizes and adjusted the more complex interactions for mobile so the experience stayed consistent and easy to use.
Inspiration
I took inspiration from modern digital portfolios and interactive websites that make the work feel like part of the experience. Adham Dannaway’s portfolio was one of the references that influenced me, especially the way it combines personality, visual interaction, and clear presentation of work. I also looked at modern web design trends and experimented with different layouts, typography, motion, and interactions until the site felt personal rather than like a typical portfolio template.
Lessons
Building the portfolio taught me that a good portfolio is more than just presenting projects. I learned a lot about balancing design, performance, responsiveness, and usability while working with Next.js, Supabase, and Framer Motion. I also gained experience building features like authentication, moderation, dynamic pages, and form handling. Most importantly, I learned how much better the final result becomes when I treat the portfolio itself as a real product rather than just a collection of my work.
Future Plans for My Portfolio
Definitely. I plan to keep the portfolio evolving as I take on new projects and learn new things. I’d like to add more case studies, improve existing interactions, and continue refining the overall design and performance. I also want to expand the community section and experiment with new ideas that make the portfolio feel more personal and useful rather than just being a static showcase.
