The Project

Problem: I needed a single place that represents me well, without forcing recruiters to piece together context from scattered repos. I also wanted the site to reflect how I actually work, clear structure, good defaults, and a focus on maintainability. What I built: I developed a portfolio site that presents my work, background, and contact details in a clean layout. The key requirement was to keep the content easy to update, so I structured projects as data objects that the UI can render consistently. This avoids rewriting UI code every time a project changes. How I built it: I used Next.js and TypeScript to keep routing, rendering, and component boundaries predictable. I used SCSS for styling so I could maintain a consistent design system without relying on heavy UI frameworks. I also added small details that improve usability, such as clear navigation and direct links to source repositories. How it ties back to my backend focus: Even though this is a front-end artefact, I treated it like a software system. I paid attention to structure, separation of concerns, and how future changes will be made. The site also acts as a hub for my Java work, so the presentation stays simple and the technical depth lives in the projects themselves. Outcome: The portfolio gives a quick, accurate snapshot of my work and makes it easier for someone to review my repositories with the right context.