2026-08-10 · site / architecture / release

From landing page to public platform.

The v8 redesign is an information-architecture change first and a visual change second.

The problem

The previous home accumulated identity, portfolio, lore, terminal simulation, stack, releases and contact into one page. It was visually coherent, but the structure made every future improvement compete for the same first document.

The v8 decision

The home becomes a hub. Projects move into case studies. Lilith moves into an identity artbook. Yggdrasil gets a public architecture explorer. Releases render from the existing RSS feed. Status shows only intentionally public services.

Why the stack stays static

There is no current requirement that justifies moving the site to a larger application framework. Semantic HTML, shared CSS, modern JavaScript and Cloudflare remain sufficient while preserving a small attack and maintenance surface.

Release safety

The v8 line is built behind a branch, pull-request checks and a Cloudflare preview workflow. Production remains a separate gate after automated and visual QA.