Home

Behind the build

How this site works

A small website with a few moving parts. The interesting work is deciding how those parts should behave when something goes wrong.

From a file to a page

Astro turns the written content, shared layouts and design tokens into HTML at build time. The fonts and artwork are served with the site. Navigation uses ordinary links, with browser page transitions where supported.

Read the page

HTML carries the project stories, notes and links. If JavaScript is disabled, these remain readable. Interactive pages include instructions or worked examples.

Add the interaction

A small shared script connects preferences and navigation. The hero, simulations and games load their own code only on pages that use them. Controls appear once their handlers are ready.

Remember a little

Preferences and game progress can stay in local browser storage. Unreadable saves fall back to a fresh state. If storage is unavailable, the current tab can still work.

Room for motion

The drawings, small red car and connected hero share the same colours and motion preferences. Appearance and visual emphasis are independent, so a different accent does not change your light or dark setting.

Reduced motion follows your device preference and the site's own control. It stops decorative movement and reveals content immediately. Page-exit handlers also cancel active motion. A failed animation download leaves a still drawing.

See the connected hero

A shared daily puzzle

Each game turns its name, rules version and today's UTC date into a deterministic seed. With the same game version and a correct device clock, visitors receive the same daily challenge.

  1. IdentityGame + version + UTC date
  2. SeedA repeatable number, computed in the browser
  3. ChallengeA generated route or race schedule, with its defined rules

Relay Route generates 7,382 distinct route shapes, then places checkpoints and scrambles the tiles. Pit Window generates 2,592 distinct eight-lap schedules with changing conditions and pit opportunities. The versioned daily sequence visits every candidate before repeating. Practice advances through the same finite collection.

A new UTC day offers a new dated challenge without replacing an unfinished game. Original v1 saves still replay their original rules and layouts; new runs use v2. First Daily results stay separate by date and version. No server reset or daily content upload is needed, and these local results are not a competitive leaderboard.

The scoring rules are separate from the animation. Saved moves are replayed through the model when restored; a stored score alone is never enough. This helps reject broken saves, while results remain local and editable by the browser's owner.

Try the daily games

A boundary between private and public

Preferences and game progress stay in your browser. The separate Advice demo also runs locally with fictional questions. The real Questions and resources page checks whether its submission service is available and never shows a successful send when it cannot reach storage.

When enabled, questions go through a same-origin API into private database storage. I sign in to a separate review page, edit a public version, and explicitly publish that saved revision. An edited draft does not silently replace a published answer. A deletion receipt lets a visitor remove their question without creating an account.

Database policies enforce who can see private questions. Verification and durable rate limits protect intake, while local screening only suggests topics and flags. Nothing publishes automatically. A scheduled cleanup removes old private data; activation requires checking the hosted database, sign-in, verification and cleanup together.

Visit Questions and resources ยท Read the privacy details

Checking the boundaries

The project checks authored content, generated links, contrast pairs and script policy during builds. Behaviour tests exercise game rules, saved-state recovery, motion preferences and private review permissions, submission retries and exact-revision publication.

Browser checks also cover narrow layouts and missing scripts. Those checks support the implemented behaviour; they do not prove every device works perfectly or make browser-only scores trustworthy. Hosted sign-in and storage, real devices and accessibility tools need their own verification.

I write about related decisions in Engineering notes. The next questions I want to work through are on Currently exploring.