Skip to main content
ambooka
Back to case studies
Case studyCompleted

ambooka.dev Portfolio Platform

Built ambooka.dev as a full-stack Next.js 16 portfolio platform with Supabase backend, admin CMS, GitHub activity sync and Playwright e2e testing.

Next.js 16TypeScriptSupabaseGitHub Activity SyncPlaywright

Project summary

Full-stack portfolio platform with Supabase backend and admin CMS.

Source code Live project

Type

portfolio-platform

Status

live

Problem

  • A static resume could not represent evolving project evidence, portfolio content and GitHub activity.

Architecture

  • Problem-first framing so reviewers understand the operating context before implementation.
  • Implementation details are tied to the stack and workflows in the project record.
  • Sensitive client and company details are sanitized while preserving technical credibility.
  • Business value and measurable outcomes are highlighted where evidence exists.

Key Decisions

  • Use only completed work supported by the résumé or public repository evidence.
  • Keep project claims specific, factual, and proportionate to available proof.
  • Separate confidential client or company information from public technical summaries.
  • Prioritize implementation decisions and outcomes over decorative presentation.

Implementation

  • Built a database-backed portfolio platform with admin-managed content, a single canonical resume, GitHub sync and e2e tests.
  • Documented the stack, business context, and relevant operational outcomes.
  • Prepared a concise recruiter summary and safe public case-study presentation.

Quality Gates

  • Public records include the problem, solution, stack, business value, and evidence status.
  • Sensitive details remain intentionally summarized.
  • No unsupported performance, certification, or capability claim is included.

Results

  • Turns professional evidence into a structured software product rather than a static page.
  • Demonstrates completed work rather than tutorial or study-plan output.
  • Supports software, backend, payments, business-systems, infrastructure, or computer-vision roles.

Future Improvements

  • Add screenshots or architecture diagrams where safe to publish.
  • Add demo videos for public-facing work.
  • Attach additional verified performance or business-impact metrics when available.

Public Evidence

  • Tests
  • Ci
  • Database Migrations
  • Docs
  • Deployed