Colophon

How this site is built

It's held to the same standard as Falkor: static, fast, private, accessible, and honest about every number. The site has its own pipeline and its own gates.

The pipeline

  1. 01RecordsFalkor's capability audit and git history
  2. 02Allowlist exporterPrivate. Copies aggregate numbers field by field; never raw records
  3. 03Static buildAstro renders every page to plain HTML at build time
  4. 04Leak gate21 rules, each proven by a negative control; binaries approved by hash
  5. 05PublishOnly the built folder ever leaves the machine

Details you might not notice

  • No cookies, trackers or third-party requests

    Every byte comes from this site. Fonts are the system's own, so nothing is fetched from a font service either.

  • Served exactly as built

    The site is static files on Cloudflare Pages, behind a strict content security policy that allows nothing from any other origin and runs only the inline scripts it names by their hash, computed at build time. Two hosting features that rewrite pages on the fly, an injected analytics beacon and email-address scrambling, are switched off, and a check confirms the live pages match the build byte for byte.

  • A themed backdrop that stays out of the way

    The circuit traces, network lines and dot grids are CSS, a few small SVG masks and some inline SVG in the heroes, all drawn in the page's own colors so they follow light and dark mode. They keep out of the reading column, disappear for print and high-contrast modes, and the packets travelling along the hero's traces stop when your system asks for reduced motion.

  • A home page that routes

    The home page is about the person and the work, in under 2,500 words. The full Falkor tour has its own page, and old links into the former single long page are forwarded, before the first paint, to wherever each section lives now.

  • Contact without a form service

    “Discuss a role” and “Discuss a project” each open your own mail app with a subject and a few short prompts already filled in. There is no form service or third party, and nothing is stored.

  • Ready to be shared and found

    Every page names its canonical address and carries a 1,200 by 630 link preview and structured data: a profile, breadcrumbs, and articles for approved case studies. Case studies join the sitemap only once they're approved.

  • Accessibility as a release gate

    Before every release, an axe-core scan covers every page and its interactive states, alongside checks of contrast, target size, reflow at 320 pixels and keyboard use. The deploy command runs them itself and publishes nothing unless all of them pass. The accessibility statement lists what they cover and what still falls short.

  • An instrument panel instead of a stock hero

    The Falkor page opens on its flight recorder: a hand-built SVG map of the real request path and five scenarios replayed from recorded behaviour. A small animation engine moves each request hop by hop, types the log as it goes, and cancels cleanly when you switch scenarios. It pauses when the panel is offscreen or the tab is hidden, steps aside entirely for reduced motion, and without JavaScript it shows a complete transcript.

  • A film that waits its turn

    The film on the home page's Falkor card shows its first frame as a small still (19 to 40 KB, sized to the screen) that loads as it nears the screen. The video itself (839 KB of AV1, with H.264 for browsers that can't decode AV1) is requested only after the page has finished loading, plays only while it's on screen, and never autoplays when your system asks for reduced motion or less data. It always has a pause button, the audio track was removed, and the white end card was trimmed so the loop never flashes.

  • A long page you can steer

    The Falkor page is long, so its section tabs stay pinned to the top and highlight where you are. The header tucks away while you read and returns when you scroll up. Any long jump offers a one-click “Back to …”, a back-to-top button fills in as you read, and the [ and ] keys step through the sections.

  • Real screens, reviewed one by one

    The screenshots come from the running system through a small pipeline. A headless browser captures each page cropped to its content, every capture is reviewed at full size (several were rejected for showing personal or location details), and only approved captures become WebP images at two widths, with metadata stripped. The build refuses to publish any image whose hash hasn't been approved.

  • Demos, not videos

    Six showcase items are small working demos that run in your browser on sample data: a claim guard, a memory inbox, GPU sharing, a crash-and-resume collector, Game Mode and a process census. Each starts only when opened, stops its timers when you move on, and shows a meaningful static state without JavaScript.

  • Annotated screenshots

    Numbered pins mark what each screenshot proves. Hovering a pin or its line in the legend lights up both, and the legend carries every word, so nothing depends on hovering. Screens open in a native-dialog lightbox that pages with the arrow keys or a swipe.

  • Charts built for everyone

    The palette is checked for color-vision deficiency, and dark mode has its own selected steps rather than an inversion. The heatmap is drawn at its true scale and answers to the keyboard (arrow keys move by day and week). Every chart has a text or table equivalent.

  • Motion that asks first

    The hero settles in once on load, the theme switch is a circular reveal (View Transitions API), and pages load as plain documents with no client router. Nothing waits on scrolling to appear, and all of it is skipped when your system asks for reduced motion.

  • Reading progress without JavaScript

    The bar at the top of each case study is a CSS scroll-driven animation. Browsers without support simply don't show it.

  • A command palette on a native dialog

    Press Ctrl/⌘ K or / to jump anywhere. The native <dialog> element provides the focus trap, Esc to close and an inert background, with combobox and listbox semantics for screen readers.

  • Keyboard-first components

    The showcase explorer and the lifecycle tabs follow the ARIA tabs pattern (arrow keys, Home, End), every filter announces its result count, [ and ] move between the Falkor page's sections, and focus is always visible. The header never tucks away while it holds keyboard focus.

  • Progressive enhancement throughout

    With JavaScript off, every page still renders, every link works and every panel is readable. The script only adds conveniences on top.

  • One source for the resume

    The PDF is generated from the web resume's own print stylesheet in a headless browser, so the page and the PDF can't drift apart.

  • Numbers with receipts

    Every figure on the site carries its source and date, and the site changes only when a new snapshot is published. It never talks to the live system.

Measured

Lighthouse 12 against the live home page, on a simulated slow 4G phone (three runs: 99 each for performance). Desktop scored 100 in all four, and the Falkor page 99 on the phone in all five runs and 100 on desktop. Zero layout shift and zero blocking time throughout. Measured · 30 Sep 2026

99

Performance

100

Accessibility

100

Best practices

100

SEO

Home page, transferred (compressed)Size
HTML of the home page19.9 KB
CSS, the themed backdrop included13.4 KB
JavaScript (all of it on this page: the demos, film, navigation and lightbox)8.7 KB
Code total, in 7 requests42.1 KB
The film's first frame, loaded as its card nears the screen19–40 KB
The film itself, fetched only once it's on screen (AV1)839 KB
Everything a first visit loads on a phone before the film plays (over HTTP/2; HTTP/3 adds about 5 KB of headers)91 KB
The Falkor page's code, with the flight recorder's map and the showcase61.0 KB

What you can check yourself

On this site, without taking my word for it

  • No cookies or trackers: your browser's storage and network panels show none, and every request stays on this site.
  • The security policy: the response headers name it, and your browser's console reports anything it blocks.
  • Accessibility and speed: run axe or Lighthouse on any page and compare with the numbers above.
  • The structured data: Google's Rich Results Test reads the same profile, articles and breadcrumbs search engines do.
  • The link previews: paste any page into LinkedIn, Slack or a message and see its card.

From Falkor's private records

  • Falkor's figures (the capability audit, commit counts, certification runs and recovery times) come from Falkor's own dated records. Each carries its source and date, but the records stay private because they describe a household.
  • The screens are real captures, reviewed one by one; several were rejected for showing personal or location details.

Stack

Astro (static output) · TypeScript · hand-written CSS with design tokens · hand-built SVG with a small animation engine · system fonts · a headless browser for the PDF resume · a private Node exporter and leak gate

Esc