← Back to blogעברית

Adding a blog to my personal site (without starting over)

Why I migrated yonatanhanan.com to Astro and what the first bilingual, content-rich blog setup includes.

For a while, yonatanhanan.com did one job well: it introduced me and my work. But when I wanted to start writing, the site had nowhere for writing to live.

The portfolio was a single-page React + Vite app, with content stored in YAML translation files. That was a solid setup for a fast landing page, but a poor fit for a blog: no per-post URLs, no article-friendly content model, and no easy way to mix text with richer building blocks.

What I wanted from a blog

I wasn’t trying to rebuild everything. I wanted a setup that could:

  • Stay fast and simple to deploy
  • Support real articles in English and Hebrew
  • Let posts include more than plain Markdown when needed
  • Keep the door open for interactive components without turning every page into a full app

Why Astro fit

Astro gave me that middle ground: static-first by default, with flexibility where it matters.

  • Static-first output that deploys cleanly to Cloudflare
  • Content Collections for typed, organized posts and metadata
  • MDX so a post can include components alongside prose
  • React islands for interactive pieces only where they add value

In other words, I could keep the site lightweight while giving the writing side a proper foundation.

What the first version includes

This first pass focuses on the essentials instead of trying to ship every idea at once:

  • Bilingual posts with English and Hebrew versions
  • Rich article content, including images
  • Mermaid diagrams with zoom and pan for larger charts
  • Embedded HTML/components for cases where a post needs something custom
  • A foundation for future authoring improvements and per-post view analytics

How the pieces fit together

The migration keeps the existing portfolio and adds a content layer for the blog:

Loading diagram…

What’s next

From here, I want to improve the writing workflow (possibly with an optional WYSIWYG flow), add per-post analytics, and expand the kinds of media posts can include, including video where it actually helps.

But the important milestone is already in place: I now have a home for writing on the same site I build, maintain, and deploy, in both languages.