Building My Personal Site kazasiki.jp with AI
This article was automatically translated from Japanese by AI. Read the original Japanese version →
Table of Contents
I have finally moved on from Hatena Blog, which I had been using for years, and launched my own personal website at kazasiki.jp.
I originally started writing on Hatena Blog around 2013, posting casually for over a decade about VR games, gadgets, programming, and everyday life. Over time, my output also spread across various platforms—Steam, Eiga.com, Bookmeter, and more—so I had been using Linktree as a hub to tie everything together.
For a while, though, I had been wanting a proper personal site of my own. With the help of an AI agent (Antigravity), I decided to migrate everything and build it out in one go.
In this post, I want to share the stack I chose and the key things I specifically wanted to achieve with this site.
Services and Tech Stack
Here is an overview of the services and technologies behind the site. My core goal was to keep things simple, lightweight, and inexpensive to run as static files, while retaining full control over everything.
- Static Site Generator (SSG): Astro
- All content is managed as Markdown files and compiled into pure static HTML at build time. I left the tool selection up to Gemini.
- Hosting: Firebase Hosting (GCP)
- Since I have Google Cloud credits through Google AI Pro, I chose Firebase Hosting for easy static hosting on GCP.
- Custom Domain:
kazasiki.jp(Xserver Domain)- Registered through Xserver Domain and pointed to Firebase Hosting using its free DNS service.
- Repository & Automated Builds: GitHub (Private Repository) + GitHub Actions
- Pushing to
mainautomatically generates any new OGP images, builds the Astro site, and deploys it live.
- Pushing to
- Migrated & Aggregated Content:
- Hatena Blog (
kazasikipg.hatenablog.com): Migrated all 134 published posts and 119 images from the export file - Linktree (
linktr.ee/kazasiki): Consolidated my profile, review platforms, and social links onto the home page - Corporate Tech Blogs: Listed 10 technical articles I authored for company engineering blogs (
techtektandKAYAC Engineers' Blog) on a dedicated page
- Hatena Blog (
- Development, Migration & Translation: Antigravity
- Used interactively throughout the entire process—from site design and migration scripts to translating all 134 posts into English, reorganizing categories, and generating OGP images and favicons.
In the end, I now have a snappy static site with 275 pages (home, blog archive, external articles, and 134 posts in both Japanese and English) plus 270 per-post OGP images that builds in just a few seconds.
What I Wanted to Achieve
1. Owning the kazasiki.jp Domain
The simplest—and longest-standing—goal was simply owning a domain with my own handle.
kazasiki is a handle I have used across the internet for a very long time—on my blog, X, GitHub, Steam, Bluesky, and almost everywhere else.
Looking back over the past decade or more, the landscape of web platforms and social networks has shifted dramatically. Twitter became X, newer networks like Bluesky emerged, and where developers publish technical notes keeps changing. Individual platforms are convenient, but they are ultimately rented spaces subject to policy changes and shifting trends.
Having kazasiki.jp under my own control gives me a permanent home base on the internet. It works like a digital business card, and no matter which social platform comes or goes, pointing people to kazasiki.jp gives them the full picture of what I do.
2. Graduating from Linktree to a Hub-Style Home Page
Previously, I put linktr.ee/kazasiki in my X and Bluesky bios to gather links to my blog, Steam reviews, Eiga.com, Bookmeter, and X search links for my Playdate and indie game mini reviews.
To be honest, though, I never really liked Linktree’s layout.
While Linktree is convenient for tapping buttons vertically on a phone, it basically just stacks identical wide buttons in a single column. On a desktop screen it feels awkward, it is hard to establish visual hierarchy between my main blog and secondary mini-review links, and visitors cannot even see my latest blog posts from the top page.
So I designed the home page as a hub combining my profile, links, and latest posts:
- Top (Profile): My profile icon (a favorite of mine drawn by calvet, with a subtle credit right beside it), a short bio, and my main social accounts (X, GitHub, Bluesky)
- Middle (Contents): Two prominent side-by-side cards for the site’s core sections—my Blog and External Articles
- Lower Middle (Reviews & Mini Reviews): A compact list of five external links (Steam, Eiga.com, Bookmeter, and my X mini-review searches)
- Bottom (Latest Posts): The five most recent blog posts so visitors can jump straight into reading
Visually, I made dark mode the default (with a toggle for light mode) and turned my profile icon into a circular favicon. Being able to iron out all the tiny annoyances you normally have to live with on hosted profile services felt great.
3. Full Japanese & English Support (For Both Search and AI)
One thing I (or rather, the AI) put a lot of effort into was making the entire site bilingual—Japanese (/) and English (/en/). Not just the UI, either: all 134 existing posts migrated from Hatena Blog were translated into English.
Of course, these translations are generated by AI. To be transparent with readers, every English post displays a clear notice at the top stating that it was automatically translated from Japanese by AI, along with a direct link to the original Japanese article.
I had two main reasons for doing this:
First, I wanted English-speaking readers to be able to find my posts via search. Much of my writing covers topics with large international communities—VR games, Steam Deck, Playdate, and gadgets—so keeping everything locked strictly in Japanese felt like a missed opportunity.
Second, I wanted a site that AI systems can easily read and reference. More and more people now discover information not just through traditional Google search, but through LLMs and AI search agents. Having clean, structured static HTML in both Japanese and English, backed by a hreflang-annotated sitemap and bilingual RSS feeds, makes the content far more accessible across language boundaries.
Not long ago, translating 134 back-catalog posts into English would have been completely out of the question for a solo side project. Using AI, all 134 posts were translated in just a few minutes while preserving HTML structure, code blocks, and internal links.
4. Making My Site and Posts Freely Accessible to AI
From a technical standpoint, this might be the single biggest advantage of the migration: keeping my entire site and every article as plain Markdown files in a local Git repository so I can let AI inspect, refactor, and operate on them freely.
When your posts live inside a hosted blogging SaaS, editing one post at a time in a browser is easy, but doing cross-cutting structural cleanups across a hundred old articles is painful.
Once all 134 posts were sitting locally as Markdown, I could have an AI agent read the entire archive and maintain it holistically. The clearest example of this was overhauling my categories.
After more than ten years of tagging posts on a whim, I had ended up with 23 fragmented categories plus a bunch of uncategorized posts. I had the AI review the titles and contents of all 134 posts and consolidate them cleanly into 5 categories:
- Life (生活)
- Gadgets (ガジェット)
- Games (ゲーム)
- Tech (テック)
- VR (VR)
Posts can belong to multiple categories where appropriate, and zero posts are left uncategorized. Doing that manually across 134 articles would have taken hours; with AI, it was done in moments.
5. Collecting My Corporate Tech Blog Articles in One Place
Finally, I had long wanted a single place to list the technical articles I wrote for company engineering blogs.
As a software engineer, writing for your employer’s tech blog is a great experience—I have published articles on Persol Career’s official tech blog (techtekt) as well as KAYAC Engineers’ Blog from my previous company.
The downside is that over time and across job changes, those articles end up scattered across different domains, leaving no easy way to view all of your public technical writing in one place.
To solve that, I created a dedicated /articles/ page separate from my personal blog (/blog/). It lists the 10 technical articles I authored myself (8 on techtekt and 2 on KAYAC Engineers’ Blog), complete with OGP thumbnails and publisher filters, along with English titles and summaries on the /en/articles/ page.
Separating personal/hobby writing (VR, games, gadgets, daily life) from work-related technical articles—while still keeping both under kazasiki.jp—makes the entire site feel much cleaner and better organized.
Wrapping Up
Building a personal site with a static site generator is nothing new for engineers. Historically, though, all the tedious migration work—moving old posts, saving images, fixing broken markup, and polishing the design—made it hard to actually follow through.
Pairing static site generation with an AI agent lowered that barrier dramatically. I was finally able to build the exact personal site I had pictured in my head.
Going forward, kazasiki.jp will be my home base on the web, and I look forward to writing new posts and continuing to evolve the site alongside AI.