The homepage globe stays as the fast first impression.
This is the part of the site meant to be touched.
Home keeps one globe near the front so the site has a pulse immediately. This page is where the interactive side gets more breathing room: live visitor presence, recent hotspot memory, and the experiments that make more sense in motion than in a paragraph.
Here the globe gets context, space, and a more focused atmosphere.
No splash screen, no waiting ritual, just a smoother entrance into the scene.
A public visitor map that feels more like ambient presence than surveillance.
The globe shows approximate visits in a short rolling window, collected at the edge and rendered as a lightweight visual signal. Live mode shows fresh arrivals. History mode turns recent traffic into softer hotspots, so the scene has both pulse and memory.
Privacy shape
Approximate locations, short retention, and no attempt to turn every reader into a profile.
Performance shape
The poster paints first, the heavier 3D scene wakes later, and the page still works if WebGL never does.
Curiosity shape
It gives non-technical visitors something immediate to play with while still pointing technical readers back toward the build notes.
Tip: drag the globe to pause the drift and inspect a region.
The code stays public.
If you want the implementation details immediately, the repository is the shortest path.
Open GitHubThe reasoning has a home too.
The technical explanations and trade-offs live in the blog, not only inside the source tree.
Read the blogThe person should stay visible.
If you arrived from a profile link and just want context, the About page is the fastest orientation.
Open aboutThe lab's written trail.
These entries explain how the experiments are built, where they fit, and what trade-offs were made to keep the site fast and readable.
Launching a static-first engineering blog with one living island
Why this blog starts with Astro, a deliberate WebGL island, and a bias toward edge-readable systems.
Astro islands are a product choice, not just a framework feature
Treating hydration as a design constraint leads to cleaner reading experiences and a healthier performance budget.