Skip to main content
ambooka
Back to case studies
Case studyCompleted

ambooka.dev Portfolio Platform

Built a full-stack Next.js portfolio platform with Supabase backend, admin CMS, GitHub sync, resume variants and Playwright e2e tests.

Next.js 16TypeScriptReactSupabasePostgreSQLPlaywrightTailwind CSS

Project summary

Full-stack Next.js portfolio platform with Supabase content, admin CMS, resume variants, GitHub sync and Playwright e2e tests.

Source code Live project

Status

Live portfolio platform

Problem

  • A static portfolio could not present real project evidence, resume variants, case studies and evolving technical positioning.

Architecture

  • Problem-first presentation: the case study opens with the operational or engineering pain point, not a UI effect.
  • Implementation details are summarized through stack, workflow, integrations, data handling and deployment context.
  • Sensitive client/company details are sanitized while preserving real business value and technical credibility.
  • Every project record links stack, proof, engineering evidence and measurable impact where available.

Key Decisions

  • Use real resume evidence only: client work, company work, academic research and completed portfolio platform work.
  • Keep private learning plans out of the public portfolio.
  • Avoid overclaiming: status, proof and metrics must reflect actual evidence.
  • Prioritize readable business value and implementation decisions over decorative presentation.

Implementation

  • Built a database-backed Next.js portfolio platform with admin-managed content, structured project data, resume views, GitHub sync and tests.
  • Stack used: Next.js 16, TypeScript, React, Supabase, PostgreSQL, Playwright, Tailwind CSS.
  • Documented the project with a recruiter summary, business value and engineering evidence.
  • Prepared the project for public case-study presentation with safe disclosure boundaries.

Quality Gates

  • Testing evidence is expected or present.
  • CI/CD evidence is expected or present.
  • Deployment or real operational use is part of the proof.
  • Public wording avoids private planning language and keeps the portfolio professional.

Results

  • Turns professional evidence into a structured proof system instead of a flat resume page.
  • Strengthens the portfolio through real-world experience instead of tutorial-style claims.
  • Supports positioning across software engineering, IT systems, business automation and applied AI/ML engineering.

Future Improvements

  • Add screenshots or diagrams where safe to publish.
  • Add demo videos for public-facing work.
  • Attach more measurable performance, reliability or business impact metrics when available.
  • Keep client/company-sensitive details sanitized.

Public Evidence

  • Tests
  • Ci
  • Database Migrations
  • Docs
  • Deployed