All posts

[ Personal Build · Portfolio ]

How I came up with this website and built it

Illustration of a portfolio homepage layout with a dark interface, headline, cards, and a highlighted call-to-action.

I wanted one place on the internet that felt more like me than a CV, a GitHub profile, or a LinkedIn page on its own. Those platforms are useful, but they flatten everything into the same template. I wanted a small site that could show not just what I have worked on, but also how I think: structured, practical, and a little opinionated about building things well.

How the idea started

The starting point was simple: I needed a portfolio that could introduce me quickly to someone landing on it for the first time. That meant a clear homepage, a focused about page, selected work instead of a giant dump of projects, and a writing section where I could leave traces of what I am learning. I did not want something bloated. I wanted something direct.

I also wanted the site to reflect the kind of engineer I am trying to become. Most of my background is in AI and end-to-end engineering, so the portfolio had to feel intentional rather than decorative. The design leans clean and minimal, but the real goal was clarity: make it easy to understand who I am, what I build, and what I care about.

How I wrote it

I kept the stack deliberately simple and wrote the site as a static project: separate HTML pages, one shared stylesheet, and a small JavaScript file for the interactive touches. No framework, no CMS, no unnecessary complexity. That gave me full control over the structure, performance, and visual details without fighting tooling I did not need.

I built the pages section by section. First the overall structure and navigation, then the homepage hero and project highlights, then the supporting pages like About, Work, Writing, and Contact. After that, I tightened the layout, typography, spacing, and transitions so the site felt consistent instead of like isolated pages stitched together.

What mattered while building it

The most important decision was restraint. I did not want to hide weak content behind heavy effects. So I treated the site the same way I try to treat engineering work: start with strong structure, keep the moving parts understandable, and only add polish where it actually improves the experience. The animations, styling, and assistant layer are there to support the content, not distract from it.

In the end, this website became more than a portfolio piece. It is also a small expression of how I like to build: clearly, from scratch when that makes sense, and with enough care that the final result feels deliberate.