Front end
Astro ships the reading pages as static HTML first, then wakes the heavier pieces only where interactivity actually adds value.
Colophon / build rationale
Why this site tries to feel like a room instead of a dashboard.
I like personal sites that feel closer to rooms than control panels, so this page explains how that preference shows up in the stack, the visuals, and the performance rules underneath.
Edge shape
Cloudflare Pages Functions and a Durable Object handle the visitor signal, so the globe can feel alive without turning the whole site into a permanently running app.
Static by default, interactive by choice.
The writing, archive, and evergreen pages stay server-rendered and cache-friendly. React is used where the experience would be weaker without it: search, reading continuity, and the globe.
The globe is poster-first on purpose.
A calm poster loads first. The WebGL scene then upgrades on idle or on demand, which protects slower devices and keeps the homepage from feeling blocked by a hero effect.
Approximate signals, short memory.
The visitor view keeps only a short rolling window of approximate locations. It is meant to show ambient presence, not build a dossier on readers.
Readable before clever.
Every new effect has to justify its payload. If a feature is not helping orientation, reading, or delight, it does not stay.
Read the thinkingSoft midnight over dashboard chrome.
The look aims for a warmer, more personal kind of dark mode: still technical, but less like a control panel and more like a space someone actually inhabits.
See the labProvider-aware, not provider-locked.
The current deployment path is Cloudflare-first, but the content model and static build stay portable enough to move toward Alibaba Cloud or another edge runtime later.
Open the repository