Blog⁽¹⁴⁾

The Work section reproduces a reference that ships a megabyte of Three.js and GSAP. Ours runs on a hand-rolled WebGL2 renderer, a 140-line tween engine and a router that swaps the main element, in under 20 kB gzipped.

• WebGL
• Performance
• Vanilla TypeScript

We used to cap our JavaScript at 15 kB and fail the build over it. A cap is the wrong question for a site worth looking at. Now the build keeps a ledger of what every file weighs, and nothing gets heavier without someone deciding it should.

• Performance
• Tooling
• Bun

Utilities are scanned from the templates and compiled into one stylesheet per section. The browser never sees a class it does not use, and it never runs a line of styling JavaScript.

• Tailwind CSS
• Performance
• Design

Two WOFF2 files cover Latin and Latin Extended, each declared with its own unicode-range, so a page that only uses ASCII downloads one of them. How the split is chosen and what it does to the first paint.

• Performance
• Design

The build writes one HTML file per route from the same templates the client router renders. Deep links work without JavaScript, and an in-app navigation produces the exact DOM a cold load would.

• Vanilla TypeScript
• Performance
• Infrastructure

The development server is a single TypeScript file: it serves the repo, bundles entry points on request, spawns a Tailwind CSS watcher per stylesheet and renders the generated routes. No framework, no config directory.

• Bun
• Tooling

With no CDN fonts, no analytics and no embeds, the policy collapses to default-src self. What that rules out, the one inline exception for noscript styles, and why the rest of the headers file is short.

• Security
• Infrastructure

The landing page hero types a command, streams output a line at a time and pauses on a choice. The scenarios live in template elements in the markup, and a run token keeps fast tab clicks from interleaving.

• Vanilla TypeScript
• Design

The utilities we publish are native. No bundled browser, no telemetry, no update daemon. Why a small studio takes the slower road and what it gets back.

• macOS
• Studio

Every animated component on the site has a reduced-motion path that is designed, not just disabled. Typing becomes a print, reveals become visible, waveforms stand still, and the page loses nothing.

• Accessibility
• Design
• Vanilla TypeScript

The demo player draws its bars from the narration's real frequency data through an AnalyserNode. When the file cannot play, the same bars fall back to a CSS keyframe so the component never looks broken.

• Vanilla TypeScript
• Design

The front end is vanilla TypeScript by design. Behind it, Go handles services and tooling that need to run for years, and Rust takes the pieces where a runtime would cost too much. A short field guide to the split.

• Go
• Rust
• Infrastructure
• Studio

Performance, accessibility, best practices and SEO are what we aim at for every page, not a report to admire. How the checks run, which numbers we treat as real, and why an estimate never counts as a measurement.

• Performance
• Tooling
• Accessibility

Black Bao Studio is a two-desk studio on the Spanish coast that builds websites the way infrastructure is built: measured, budgeted and boring where boring is a virtue. This is the first post.

• Studio