How I built this portfolio

I wanted a personal site that felt less like a resume and more like a home for my work, thinking, mentorship, and experiments.

The goal

The first version of this site started as a portfolio. The better version became a point of view.

I did not want the homepage to read like a career timeline. I wanted it to answer a more useful question: what do I care about, how do I think, and what kinds of problems keep showing up in my work?

The structure

I organized the site around a few reusable sections: why I build, selected work, evolution, thinking and exploring, building in public, mentorship, speaking, published work, and contact.

That structure lets the site grow without becoming cluttered. Work can live in case studies. Ideas can live as essays. Speaking and mentorship can grow over time.

The stack

I kept the stack intentionally simple: GitHub Pages, a custom domain, plain HTML, and CSS. No CMS, no hosting bill, no heavy framework.

The tradeoff is that updates require a little discipline. Each new post is a new HTML file. Each homepage card links to that file. The simplicity is worth it because the site stays fast, portable, and easy to control.

What I learned

• A personal site should lead with philosophy before chronology.
• Depth belongs on separate pages, not crowded onto the homepage.
• Visual restraint matters. A few strong surfaces are better than too many decorative elements.
• Writing the site forced me to clarify what connects my work: trust, decision systems, and making complexity easier to navigate.

The reusable pattern

The pattern I would reuse is simple: start with why, show evidence through selected work, create space for ideas, then add modular sections for the parts of your professional identity that are still growing.

A good personal site should not feel finished. It should feel alive.