Why I rebuilt my portfolio from scratch

I build software for a living, but my portfolio wasn't showing that well. So I rebuilt it from scratch, with one goal: make it easy for you to see what I've built and how it works.

Designed like the products I build

My first design for this version was loud: bright blue, yellow, and a line that drew itself as you scrolled. It looked different, but it got in the way of the work, so I threw it out.

The site you're reading now works more like an app. There's a sidebar, and the home page has a project explorer where you can filter by field, click through screenshots, and see how each project fits together, all without leaving the page.

Real products, not just screenshots

The projects are the centre of the site, including three I care a lot about:

• DigCare, a digital healthcare platform for Ghana, with a mobile app and separate web portals for clinics, labs, pharmacies and insurers.
• TechTitan, an e-commerce platform for gadgets and toners in Accra, with WhatsApp ordering, MoMo and Paystack payments, and tracked delivery.

Each project page shows what it does, what it's built with, and an architecture diagram where I've added one.

Publishing without a redeploy

I wanted updating my portfolio to be as easy as writing a note. Content lives in Supabase, and I manage it through a private Studio that only exists on my own computer. When I press Publish, the live site updates in seconds, with no deploy.

The diagrams work the same way. I write a few lines of text:

Next.js storefront -> Django REST API -> [PostgreSQL, Paystack, Redis]
Redis -> Celery workers -> [WhatsApp Cloud API, Brevo email]

The site turns that into a drawn diagram.

Secure by design

The public site has no login, and it can't write to the database. Studio code never reaches the production build, and the build fails on purpose if it finds Studio code or a secret key.

What's next

I'll keep adding projects and writing here about what I learn along the way. If you're working on something and need a developer who cares about both the backend and the screen, let's talk.