Web WorldsENGINEERING / PROOF

ENGINEERING / PROOF

Under the hood.

Measured quality, automated tests, accessibility work, performance evidence, and the delivery pipeline behind Web Worlds.

Vanilla JS Playwright GitHub Actions Cloudflare Pages Worker + D1
release://web-worlds
Releasev0.27

Production Hardening + Full-Stack Proof

Artifact QALoading…

Reading verified release snapshot.

Automated suiteLoading…

Unit, browser, accessibility, and link checks.

PerformanceNot measured

Lighthouse values stay blank until a real audit is recorded.

No decorative green lights: measured, pending, and failed states are rendered separately.

01 / ARCHITECTURE

Simple runtime.
Serious workflow.

The product remains deliberately lightweight: static HTML, CSS, and JavaScript at the edge, with an optional Worker + D1 service for persistent scores. Tooling surrounds the runtime instead of replacing it.

01 / SOURCEVanilla frontend

Route-level HTML and CSS, shared theme/state behavior, plus focused Three.js and Matter.js experiences.

02 / QUALITYAutomated checks

Linting, unit tests, browser smoke tests, accessibility scans, and internal-link validation.

03 / APIWorker + D1

Validated score submissions, persistent ranking, health checks, and failure-isolated network behavior.

04 / DELIVERYGitHub Actions

Frontend and backend checks run before a release is treated as verified.

05 / PRODUCTIONCloudflare edge

Pages serves the static product while the Worker and D1 remain optional network services.

02 / AUTOMATED TESTING

Fun is allowed.
Regression is not.

The suite focuses on behavior that matters: routes booting, themes persisting, critical controls working, reduced-motion support, and quality data staying honest.

Unit cases—

Pure utilities and configuration integrity.

E2E cases—

Critical route, theme, and interaction flows.

A11y cases—

Automated axe scans plus reduced-motion checks.

API cases—

Validation, persistence, health, ordering, CORS, and failure behavior.

Internal links—

Local href/src targets validated from source.

Quality suite

release snapshot

    Browser strategy

    outcome-based tests
    • ChromiumPrimary interaction and route coverage.critical
    • FirefoxCross-browser smoke project is configured for CI.CI
    • WebKitCross-browser smoke project is configured for CI.CI
    • Mobile viewportRepresentative touch-sized layout validation.critical

    03 / PERFORMANCE

    Measure first.
    Optimize second.

    Heavy interactive routes are judged differently from lightweight content pages. Asset size is measured directly; Lighthouse fields remain intentionally empty until a reproducible audit is recorded.

    JavaScript—

    First-party JavaScript source.

    CSS—

    All route bundles combined; one bundle loads per route.

    HTML—

    All production pages.

    Total source—

    Measured release source footprint.

    Measured source composition

    uncompressed first-party release source

    Lighthouse release metrics

    truthful nulls are better than fake 100s

    Performance history begins when reproducible Lighthouse data exists.

    04 / ACCESSIBILITY

    Playful does not
    mean careless.

    Web Worlds targets WCAG 2.2 AA where applicable. Automated scans are useful evidence, not a substitute for keyboard, focus, contrast, motion, and screen-reader review.

    Accessibility work

    v0.26 baseline
    • Keyboard + focusSkip links, semantic controls, visible focus, menu Escape handling.reviewed
    • Reduced motionShared JS avoids ambient motion; the v0.26 baseline established a global CSS reduction guard.supported
    • Theme controlsTheme switchers are exposed as labeled control groups with pressed state.semantic
    • Interactive visual worldsComplex canvas/physics experiences have fallbacks, but full non-visual equivalence is outside the current scope.documented

    Standard

    honest target

    Target: WCAG 2.2 AA where applicable. Automated axe checks are configured for major routes. This page does not claim formal compliance certification.

    The project treats accessibility findings as engineering work, not a score badge.

    05 / RELIABILITY

    Check the machine
    while it is running.

    These are live client-side checks against the site currently serving this page. They are intentionally separate from release-time CI evidence.

    Live production checks

    waiting…

      Failure isolation

      degrade, do not cascade
      • 3D dependency fallbackMissing Three.js reveals an explicit fallback instead of breaking navigation.isolated
      • Physics dependency fallbackMissing Matter.js fails the Room experience locally without taking down the site.isolated
      • Engineering data fallbackMissing metrics render unavailable states rather than fabricated success.honest

      06 / FULL-STACK PROOF

      Optional network.
      Real persistence.

      Brick Breaker can publish completed runs through a small Cloudflare Worker backed by D1. Core gameplay never depends on the network, so the leaderboard can fail without taking the playground with it.

      01BrowserCompletes a run and keeps pending scores locally until submission succeeds.
      02Worker APIValidates names, mode, score, duration, origin, body size, and submission rate.
      03D1Stores completed runs and serves deterministic score/time ordering.
      Score APIAwaiting check

      Live health uses the configured Worker endpoint.

      DatabaseAwaiting check

      D1 status comes from a real lightweight query.

      API latency—

      Browser-to-Worker health request, not synthetic uptime.

      Failure modeGameplay survives

      Network errors preserve the completed local run and expose retry feedback.

      GET /api/scoresPOST /api/scoresGET /api/health

      07 / DELIVERY PIPELINE

      From edit
      to production.

      The project keeps deployment boring on purpose. Frontend and API quality checks run first, then GitHub and Cloudflare handle the static and serverless release paths.

      01Local changeHTML, CSS, JS, tests, or docs.
      02Lint + unitSyntax, utilities, configuration.
      03Browser QARoutes, themes, critical flows.
      04Accessibilityaxe scans + motion checks.
      05API testsValidation, D1 behavior, health, CORS.
      06GitHubmain remains the production source.
      07CloudflarePages plus separately deployed Worker/D1.
      08Live checksRoutes, assets, and configured API verified in-browser.

      08 / PRODUCTION

      Small stack.
      Clean edges.

      v0.27 keeps the static frontend simple while adding an optional Cloudflare Worker + D1 score service, explicit failure isolation, API tests, and deployment-ready security controls.

      HOSTINGCloudflare Pages

      Static deployment from the GitHub production branch.

      HARDENINGSafe response headers

      nosniff, frame protection, referrer policy, and restricted browser permissions.

      DISCOVERYMetadata + sitemap

      Canonical URLs, Open Graph metadata, robots.txt, sitemap.xml, and a custom 404.

      SERVERLESSWorker + D1

      Optional score persistence with validation, prepared statements, health checks, and no production database use in tests.

      SOURCE / CASE STUDY

      Inspect the work.

      The repository documents architecture, testing strategy, performance decisions, known limitations, and the reasoning behind keeping the production runtime framework-free.

      View GitHub ↗About the builder →