Astro 5: Why Zero-JavaScript Architecture Became the Sensible Default
Why Astro 5 became our default for content-heavy sites — server islands, content layer, view transitions, and what’s actually changed.
Engineering noteEtherlabz Journal 32 entries · 06 Aug 2026
Field notes on design and engineering: brand, product, SaaS, ecom, and the work in between.
Why Astro 5 became our default for content-heavy sites — server islands, content layer, view transitions, and what’s actually changed.
Engineering noteWhy ecommerce conversion is mostly a friction problem, not a copy problem — and the structural changes that actually move the metric.
Fifty-two technical, design, SEO, and legal checks we actually run before pushing an ecommerce store live. The boring stuff that quietly tan…
A practitioner’s guide to GDPR for websites, ecommerce stores, and SaaS products in 2026 — with the technical implementation detail and the…
Real pricing for custom marketing sites, ecommerce stores, and SaaS applications in 2026 — across all three build categories, with honest co…
When behavior data justifies a SaaS redesign, what to audit before wireframing, and how to roll out without spiking churn.
Engineering noteResidency vs sovereignty, the 2026 EU regulatory stack (NIS2, DORA, EU Data Act), real EU-native provider trade-offs, and when the US hypers…
What actually matters when picking a web design agency for a tech startup — the criteria that predict outcomes vs the marketing fluff.
Why WordPress + Astro is the rare headless stack that actually works — the architecture, the integration details, and the hard parts.
Engineering note