Finally building the personal site I've been procrastinating on

I’ve wanted a personal site for a long time. Not a portfolio with fancy animations, not a blog with a newsletter funnel — just a small place where I could present the projects I work on and gather the random stuff I build for fun. A simple showcase.

The problem is I never did it. For years.

Why it took so long

It’s not like I couldn’t build a website. I do that for a living. But there was always something more interesting to work on, and the thought of picking a framework, choosing a design, setting up hosting, writing content… it just never made it to the top of the list.

The real blocker was the design part. I genuinely dislike thinking about design. I can spend hours on a backend architecture, but ask me to pick between two shades of gray and I’ll close the laptop.

What finally made it happen

I’ve been using Claude Code for a while now, and at some point I just thought — why not use it for this? The requirements are clear, the scope is small, and most of the work is execution rather than creative problem-solving. Exactly the kind of thing where it shines.

So I sat down one evening and just… did it. The whole thing took about 4 hours from first command to deployed site.

Claude Code did the heavy lifting. I described what I wanted, reviewed what it produced, course-corrected when needed, and kept going. It wasn’t about generating code I couldn’t write myself — it was about removing the friction that had kept me from doing it for years.

The stack

Astro was the obvious choice. The site is content-driven — project pages, blog posts, all written in MDX. Astro is built for exactly this. No client-side JavaScript framework needed, just static pages generated at build time.

The other big reason: hosting. Astro sites deploy to Cloudflare Pages effortlessly. Push to main, site is live. No servers, no bills, no maintenance.

The design is deliberately Notion-like. Clean, minimal, content-focused. I didn’t want to spend time on custom design systems or pixel-perfect layouts. A simple sidebar, some tags, good typography — done. Markdown files look natural in this kind of layout, which matters when that’s what you’re writing all day.

Tailwind for styling because I didn’t want to think about CSS architecture for a personal site.

What’s on here

The site is mostly a place for my projects. Some are serious — ODashboard, PassPass — and some are just things I built to scratch an itch or learn something new.

Having them all in one place is the whole point. Before this, these projects just lived in GitHub repos or in my head. Now they have a proper page with context, tech stack, and the story behind them.

The blog is secondary. I’ll write something when I have something worth sharing. No schedule, no pressure.

Was it worth it?

Absolutely. Four hours for something I’d been procrastinating on for years. The site isn’t groundbreaking, but it doesn’t need to be. It’s a simple place that does its job — and it actually exists now, which is more than I could say last week.

If you’ve been putting off building your own site, my advice is simple: lower your standards, pick a boring stack, and let the tools do the boring work. You’ll be surprised how fast it goes.