bruno.exePROJECTScontact.exe
BR95

</br95>

BR95

This website: a Win95 desktop where every window is a real, crawlable URL.

1-bit

original icon suite · every glyph generated, zero colour

byte-level

SEO parity gate on every route

Bayer 4×4

ordered-dither asset pipeline

zero JS

needed to read any public case study on this site

SPECIFICATIONS

ROLESOLO BUILD
DATEJul 2026
TYPEWEBSITE / OS SHELL
STATUSLIVE
STACKnext.js 16 · react 19 · typescript · zustand 5 · tailwind 4 · three.js / r3f · canvas · webaudio +3 more
LINKS[live ↗]
AVAILABILITYbrunojaamaa.dev

Every developer portfolio looks the same, and the usual fix is a heavy visual gimmick that destroys crawlability and accessibility · exactly the things a portfolio exists for.

== WHAT IS THIS ==

This portfolio itself: a Windows-95-style desktop operating system that is simultaneously a fully server-rendered website. Every window is a real URL, all case-study text lives in the HTML, and a byte-level SEO parity gate guards every release. On a wide screen the home page opens on a desk in a dark void, and you scroll or click your way to its CRT, where the live desktop is on the screen. The home window is BRpedia, a Wikipedia-style article about me. Underneath: a zustand window manager, a terminal with a virtual file system, an original 1-bit icon suite, a Bayer-dithered asset pipeline, and a resident desktop cat.

== </stack and architecture> ==

next.js 16 · react 19 · typescript · zustand 5 · tailwind 4 · three.js / r3f · canvas · webaudio · sharp · playwright · claude code

The shell reads the route. DesktopShell mounts once in the root layout and holds the wallpaper, taskbar, Start menu, and desktop icons; a registry maps every pathname to window metadata, and the App Router's children render inside the matched window. Routed windows (real URLs) and client-only app windows (terminal, games, dialogs) share one zustand window manager · selector-based re-renders for components, getState() for the imperative modules that run outline-drag and the wireframe minimize/restore animations, no provider.

The desk is one react-three-fiber scene built by a Blender pipeline: an ordinary desk dressed with CC0 photoscanned props, baked in Cycles and exported as one Draco-compressed GLB with three pairs of lightmaps (lamp on and lamp off), about 850 KB in all, fetched only on screens wide enough for it and only after the page itself has loaded, with a fallback to the plain desktop if it fails or is late. Nothing on the desk is lit at runtime: unlit materials mix the two bakes in the shader. Around it is a void in three layers: haze and dust in the lamp's beam, a floor of ASCII glyphs under the desk, and a far ring of dashed lines. One GSAP ScrollTrigger timeline scrubs the camera over a pinned canvas. At the computer the real desktop DOM lies under the canvas, placed on the tube with a CSS 3D transform recomputed every frame from the screen mesh, and the canvas is see-through only where the glass is, so the desktop stays fully interactive and its text stays in the HTML. On a first visit the tube shows a POST screen with the build's hash for about two seconds as the desk comes up, before the desktop appears on it. The older way out is still in the code for the screensaver: the desktop shrinks into the tube and is sampled as a 1-bit grid of roughly 96 by 60 cells. The home route renders BRpedia, an article styled with Wikipedia's own night-mode colour tokens and layout, server-rendered inside the same window frame as every other route. The terminal is a pure-logic command registry over a virtual file system built from the same grouping module that drives the desktop folders, so C:\PROJECTS always mirrors what the folder windows show.

Every visual asset in the shell is generated by repo scripts on a 1-bit budget: icon glyphs rasterized on an integer pixel grid and serialized to rect-only SVGs, window thumbnails run through an ordered Bayer 4×4 dither (chosen over Floyd-Steinberg to match the wallpaper's dither signature), and custom cursors. The Windows-style chimes are original WebAudio synths; key presses, mouse clicks and the desk's tone, CRT, lamp and disk-drive sounds are recorded CC0 samples; the smaller desk sounds are synthesised by a script. A phone mode swaps the window manager for a full-screen sheet UI under 768px.

== </how it works> ==

Shell-reads-route window manager

A zustand store drives draggable, resizable, minimizable windows · and the routed ones are real URLs with full server-rendered content. Closing a window is navigation.

Byte-level SEO parity gate

A script compares every route against committed baselines: head fields byte-identical, visible text containment-checked, links superset, one h1. Releases fail on unwaived diffs.

The desk and the CRT

On a wide screen the home page opens on a desk in a dark void. A first visit scrolls it apart with numbered labels; after that, buttons sit you down to look around and click things, or lean in until the live desktop is on the CRT, in use. Reduced motion gets the same story as stills.

BRpedia

The home window is a Wikipedia-style biography in night mode, with an infobox, a contents list, figures and numbered references, server-rendered like every other route.

Terminal over a virtual file system

A pure-logic command registry (ls, cd, open, cat, hire, and some gags) over a virtual C:\ built from the same grouping module as the desktop folders.

1-bit generated asset pipeline

Icons, dithered thumbnails, and cursors are all generated by repo scripts · rect-only SVGs on an integer grid, ordered Bayer 4×4 dithers, zero colour.

== </key decisions> ==

DECISION 01

Shell-reads-route over SPA-with-fake-URLs was the foundational call. The parity is enforced, not aspirational: a gate script compares every route against committed baselines · title, meta description, canonical, Open Graph, and JSON-LD must be byte-identical; visible text is containment-checked; internal links must be a superset; exactly one h1 per route. The build fails on any unwaived diff.

DECISION 02

Long prose stays in the server HTML. A case study is a help-viewer document with a CONTENTS rail of anchor links rather than a spawned client window, so the full text is in the DOM, crawled, and readable with JavaScript off · the rail is real <a href="#…"> anchors and the headings are real <h2> ids, so navigation needs no JavaScript either.

DECISION 03

The 1-bit law and the text diet are constraints that do design work: no accent colour in the desktop shell, ≤80-character one-liners, and a six-window cap that doubles as a period-correct out-of-memory gag when you open a seventh. The law has three deliberate exceptions, none of them in the shell's chrome: the orange shutdown screen, the BRpedia article, which keeps Wikipedia's night palette and its blue links, and the 3D desk, which is lit in colour inside a black and white void.

DECISION 04

The blog was killed rather than left to rot · its routes redirect permanently to /about instead of 404ing indexed URLs. And accessibility rules are hard laws, not nice-to-haves: nothing flashes more than 3×/s, prefers-reduced-motion gets a static everything, and body text is always real DOM.

br95 desktop: BRpedia open in the home window, taskbar, 1-bit icon suite
a project window: every window is a real crawlable url
terminal.exe: real command registry over a virtual file system
start menu: programs, documents, settings, shut down (it works)
the room, October 2026: a baked 3D desk at night, seen from the seat
monitor view in the room: the live desktop inside the tube, the room still around it
act 2, outside the box (retired in October 2026): every project as a cube on a timeline

== </versions> ==

01

The first site

Mar to Jun 2026

My first portfolio was a dark one-page site with project panels. Over three months it picked up a small 3D intro, a dithered hero and some ASCII details. It worked, but most of the home page only appeared after JavaScript ran, so a search engine saw very little of it.

the home page as it stood in June 2026
02

SIGNAL

Jul 2026, never shipped

Next I built a full redesign called SIGNAL: amber on warm black, like an old instrument panel, with my name in chrome letters over a field of amber pixels. I finished it, then changed direction before it went live. It is still in the repo as a checkpoint dated 3 July 2026.

SIGNAL, built in early July 2026 and never deployed
03

BR95, the desktop

Jul to Oct 2026

The Windows 95 style desktop went live on 4 July 2026. Every window is a real page with its text in the HTML. Through July and August it went from v1.1 to v1.11: a terminal, a guestbook, a few small games, and case studies that read like documents.

the desktop in July 2026, around v1.3
04

The room

3 to 15 Oct 2026

Then the desktop moved into a 3D room at night, baked in Blender, that you looked around from the seat. You could lean into the monitor and use the desktop inside it, and a headset on the desk led out to Act 2, a black space where every project was a cube on a timeline. The home window became BRpedia in this version.

the room, seen from the seat
act 2, outside the box
05

The quiet desk

15 Oct 2026 to now · NOW

In October I cut the room down to just the desk. It stands in a dark void over a floor of ASCII glyphs, and since 26 October the home page on a wide screen opens straight on it. Since 1 November every visit opens on a wide shot of the desk that slowly sways; until then a first visit scrolled through an opening that took the desk apart with numbered labels. From there SIT DOWN lets you look around and click things, and USE THE COMPUTER leans in until the desktop is live on the CRT. The power-off screen, black with the red light of a power strip, now only comes up after Start, Shut Down.

the power-off screen, after Shut Down
the desk at rest
the exploded view, from the opening scroll (until 1 Nov)
at the computer, the desktop live on the CRT

== </the problem> ==

Every developer portfolio looks the same, and the usual fix is a heavy visual gimmick that destroys crawlability and accessibility · exactly the things a portfolio exists for. The challenge: build something a visitor screenshots and remembers, that is simultaneously a fast, fully server-rendered, parity-gated website a search engine reads as plain HTML.

== </the approach> ==

Make the gimmick the shell and the content the OS. The desktop mounts once; every meaningful surface is a real URL rendered into a window frame; all long-form text lives in server HTML, visible, indexed by a CONTENTS rail. Guard the whole thing with scripts: a byte-level SEO parity gate, tsc, and a Playwright E2E pass on every release. Built solo, first through sprints D1 to D6 and then in versioned releases, with Claude Code doing the implementation and the diffs reviewed by hand.

role & context

Solo build · design, engineering, asset pipeline, and content. The site is its own case study.

== </the story> ==

BR95 is the website this page is part of: my portfolio, built as a Windows 95 style desktop. The desktop went live in July 2026, replacing an earlier design of the same site, and has been extended since.

The brief I set myself was that every portfolio looks the same, and that the usual fix, a heavy visual gimmick, destroys the two things a portfolio needs most: crawlability and accessibility. So instead of putting a gimmick on top of the content, I made the gimmick the shell and the content the operating system's real file system.

The site boots like a machine, runs a desktop with draggable windows, a taskbar, a Start menu, a terminal and three small games. But underneath, it is a boring-on-purpose Next.js site: the desktop shell mounts once and never remounts, and the App Router renders each route's fully server-rendered content into a window frame. Opening a project window IS navigating to its URL. Closing it navigates back. View source on any project page and the entire case study is sitting there in the HTML.

From 3 to 15 October 2026 a first visit opened on a 3D room at night, and a headset on the desk led out to a black space where every project was a cube. In October 2026 both gave way to a quieter scene: one desk standing in a dark void. Since 26 October a load of the home page on a wide screen opens on that desk, and since 1 November every load opens on a wide shot of it that slowly sways, with the buttons. Until then a first visit scrolled through an opening that took the desk apart with numbered labels. From there SIT DOWN goes to the seat, to look around and click things (the lamp, the fan, the speakers, the notebook, the floppies), and USE THE COMPUTER leans in until you are at the computer, where the live desktop is on the CRT and in use. The power-off screen (black, the red light of a power strip and PRESS ANY KEY) was the front door for a while; it now only comes up after Start, Shut Down. Phones keep the plain desktop. The home window changed with the room: since October 2026 it has been BRpedia, a Wikipedia-style article about me in Wikipedia's night palette. None of it gates the content: reduced motion gets the same story as stills with a Next button, deep links land straight at the computer with their window open, and every route still renders on the server.

The whole thing was built solo with Claude Code as the primary dev environment, against an implementation-grade sprint plan (D1 through D6) that ran to well over a thousand lines before the first line of code. It was planned in place of an amber-on-black redesign called "SIGNAL", which was finished but never went live · the plan for that one is still in the repo too.

== </what was learned> ==

>

A parity gate changes how you build: when every release must produce byte-identical head fields, you structure components so chrome and content never mix.

>

Constraints are a design system. The 1-bit law and the text diet made a thousand small decisions automatic and gave the whole shell one voice.

>

The gimmick and the fundamentals are not in tension if the gimmick is the architecture. The Win95 shell is why the SEO is good, not what the SEO survives.

>

An implementation-grade plan before code · sprints, file-level tasks, locked amendments · is what lets an AI-augmented workflow ship a project this size solo without drift.

next:

Keep treating the site as a product: more desk toys, and whatever the next hardware generation of BR95 turns out to be.

== HOW IT WAS BUILT ==

Built solo in Claude Code against an implementation-grade sprint plan (D1 to D6), diffs reviewed by hand, byte-level SEO parity gated on every release.

== </the plan> ==

Nothing here was improvised. The repo carries a masterplan with sprint sections that specify the work down to file-level tasks · window store interfaces, drag algorithms, boot state machines · plus "final locked amendments" from hardening rounds that override anything they conflict with. The BR95 desktop took the place of a finished amber-on-black design ("SIGNAL") before that one ever went live; both plans are still in the tree.

Each sprint ends the same way: tsc clean, next build clean, and the SEO parity gate green before the sprint is marked done.

== </the loop> ==

Every task runs the same five steps: scope it in the ticket system with acceptance criteria; hand it to Claude Code to architect and implement in the terminal; manually review the diff · read the logic, check the edge cases; test on a real device or browser against the spec; commit with a clean message and move on.

The manual review step is the contract. AI writes most of the code here; a human who understands the system reviews it before it is committed.

== </ai workflow> ==

Claude Code is the primary dev environment for implementation. Claude handles reasoning and design review before code exists · the sprint plans themselves are drafted, argued with, and hardened in conversation. Perplexity covers research. The division of labor is deliberate: the machine does volume, the human does judgment, and the gates catch what both miss.

== </guardrails> ==

Four gates run before anything ships: TypeScript strict compilation, a production build, a byte-level SEO parity script that diffs every route against committed baselines, and a Playwright end-to-end pass over the desktop's critical flows. Content has its own law: never invent facts · anything unverified ships as an explicit placeholder or not at all.

== toolchain ==

EDITORVS Code
AI TOOLSClaude Code (implementation) · Claude (reasoning + review) · Perplexity (research)
PROCESSTicketing + sprint planning · manual code review · on-device testing · clean commit history
GATEStsc · next build · SEO parity script · Playwright E2E
INFRAGitHub · Vercel, deployed from the CLI