Problem
A technical portfolio should help reviewers understand the strongest project quickly without vague marketing or entry-level positioning.
Case study
Portfolio — developer site for business web apps
Personal portfolio focused on technical evidence, project context, case studies and protected contact reveal.
Goal
Build a fast portfolio that presents projects by problem, real features, stack, status and case study links.
Status
Active development
Stack
Next.jsReactTypeScriptTailwind CSSFramer MotionTurnstileCal.com APIVercelVitest
Key features
- B-CRM-first project order.
- Technical reviewer section for companies and recruiters.
- Localized project cards and case studies.
- Custom booking calendar using Cal.com through server routes.
- Protected contact reveal for email and phone.
- SEO, OpenGraph, sitemap, robots and optional GTM.
Technical decisions
- The site focuses on business web apps instead of broad freelancing copy.
- Email and phone details are revealed through a server route instead of rendered in the initial HTML.
- Booking uses a custom UI and server-side Cal.com API calls instead of an external embed.
What I learned
- Positioning projects through concrete technical evidence.
- Building localized content structures for portfolio pages.
- Keeping contact and booking flows practical without exposing API keys.
Next improvements
- Expand project screenshots into a fuller gallery where it helps technical review.
- Add browser smoke tests for navigation, booking and contact reveal.
- Add analytics events through GTM after final container configuration.
- Review Core Web Vitals after design changes.
Limitations
The portfolio is an active project. Screenshots, browser smoke tests and analytics events still need more coverage.