Typed content architecture
Profile data, navigation, skills, experience, and project narratives are centralised so the site behaves more like a maintainable product than a hard-coded landing page.
Back to projects
Case study / Ongoing personal product
Portfolio Platform Redesign
A rebuild of my personal site into an employer-focused portfolio platform with dedicated case studies, typed content, and a cleaner conversion path.
A portfolio rebuild focused on clearer storytelling, stronger hierarchy, and a more maintainable content structure.
[ Problem ]
The older portfolio looked dated, concentrated too much information into a single scrolling page, and did not communicate technical judgement or delivery quality clearly enough for engineering roles.
[ Approach ]
01. Reframed the site around employer-first storytelling: stronger hierarchy, fewer generic components, clearer project narratives, and dedicated detail pages for selected work.
02. Moved the site content into a typed local model so profile copy, navigation, case studies, metadata, and contact details all stay consistent.
03. Used the rebuild to improve both presentation and implementation quality, including route-level metadata, structured data, and a more deliberate contact flow.
[ Technical decisions ]
Hybrid App Router structure
The homepage works as a high-level editorial overview, while dedicated `/projects/[slug]` routes carry deeper case-study detail for the strongest work.
Inline contact feedback with server action delivery
The contact form uses a server action, React Email, and Resend with clearer validation, honeypot spam friction, and env-backed runtime configuration.
[ Outcome ]
- > Turned the portfolio into a clearer representation of how I think, build, and communicate as an engineer.
- > Improved both the visual quality and the underlying implementation model instead of treating design and engineering as separate concerns.
- > Created a reusable foundation for future case studies without adding CMS overhead.