Developer Portfolio Website
April 2026
A personal portfolio website for showcasing projects, blogs, services, and professional experience.
Overview
This portfolio website is my proof-of-work hub. It brings together my projects, case studies, blog posts, services, contact form, and professional positioning in one place.
I built it because a resume alone does not show enough context. The site gives recruiters and collaborators a clearer way to see what I am building, what I am learning, and how I explain technical decisions.
The portfolio is also a living project. As my backend and full-stack projects mature, the site can grow with better case studies, writing, and project evidence.
Problem
A resume is useful, but it compresses too much context into bullet points. I wanted a recruiter-friendly structure where someone can quickly understand my backend focus, inspect real projects, read technical writing, and contact me without searching through disconnected links.
My Role / Contribution
I built the website structure, homepage sections, project showcase, project detail pages, blog timeline, blog detail pages, services page, contact page, and contact form integration. I also deployed it with Vercel and connected it to a custom domain.
Key Features
- Homepage with hero, about, skills, featured projects, services, and contact sections.
- Projects page with category filters and detailed project cards.
- Blog and project pages powered by shared structured TypeScript content data.
- Services and contact pages for professional positioning.
- Contact form integration using Resend.
- Project detail pages for recruiter-friendly case studies.
- Blog timeline with individual readable articles.
- Custom domain and production deployment.
- Dark, minimal visual style focused on backend-heavy engineering work.
Challenges
- Presenting technical depth without turning the site into a keyword-stuffed resume.
- Keeping project descriptions specific while leaving room for future case study expansion.
- Maintaining consistency across homepage cards, project listings, and detail pages.
- Balancing visual polish with the practical feel of a backend-focused portfolio.
- Making the content honest and defensible instead of inflated.
Learnings
- A portfolio is strongest when it explains decisions, not only lists technologies.
- Shared data structures prevent homepage and project pages from drifting apart.
- Small design constraints make a personal site feel more focused and professional.
- A portfolio becomes more useful when it is treated as a product, not a static profile.
Architecture / Flow
- Next.js App Router organizes public pages such as home, projects, blog, services, and contact.
- Reusable section and layout primitives keep spacing, typography, and cards consistent.
- Shared project data feeds the homepage, project listing, and detail pages.
- Shared blog data feeds the blog timeline and dynamic article pages.
- The contact form posts to an API route and uses Resend for email delivery.
- Vercel hosts the app and connects it to the custom domain.
Tech Stack
Frontend
Content & Forms
Deployment
Next Improvements
- Add richer visuals or diagrams to selected case studies.
- Improve blog article depth as more projects mature.
- Add stronger accessibility and metadata checks.
- Keep project content current as live apps and repositories evolve.
Links