Back to projects
Portfolio · 2026 // Ongoing · Shipped work

Personal Portfolio

Personal Portfolio hero

Summary

Personal Portfolio is a live professional showcase platform built to present my projects, product thinking, and technical learning journey in a more engaging format than a traditional CV alone. It combines project case studies, contact functionality, and structured portfolio content while laying the groundwork for future expansion into richer CV storytelling, interactive dashboards, and public-facing workflow documentation.

The Challenge

The challenge was to create a portfolio that goes beyond simply listing experience, instead demonstrating practical product thinking, prioritisation, and technical curiosity through the portfolio itself. It needed to balance personal branding, usability, and maintainability while also acting as a sandbox for learning modern deployment workflows, API integrations, and AI-assisted development practices.

Product Rationale

Search

Portfolio as product

Designed the site as a genuine product experience rather than a static resume replacement, using the platform itself to demonstrate product, UX, and prioritisation thinking.

LayoutDashboard

Expandable content model

Structured the portfolio architecture to support future additions such as interactive CV views, dashboards, and deeper project documentation without requiring significant redesign.

ListToDo

Transparent workflow showcase

Planned future public backlog and kanban functionality to demonstrate how work is prioritised, refined, and delivered in a realistic product environment.

Tech Stack

Next.jsTypeScriptTailwindResendVercelJSONSQLite

Key Decisions

  • Case-study led structure: Prioritised project storytelling and rationale over generic portfolio templates to better communicate strategic thinking and delivery approach.

  • API-driven contact workflow: Integrated Resend and DNS configuration to implement a functioning production-ready contact pipeline rather than relying on placeholder forms.

  • Flexible content storage planning: Current project content is JSON-driven for simplicity and speed, with architecture left open for lightweight database adoption such as SQLite if dynamic task/backlog functionality becomes beneficial later.

Project Notes

No two projects solve the same problem, so each case study emphasises different aspects of delivery depending on what was most relevant to the challenge. Supporting visuals and implementation details are included here to provide additional context behind the final outcome.

Visuals

Portfolio homepage timeline and project overview layout
Portfolio detailed case study and project showcase view