relay
From prompt to page.
Let the good work flow. An independent static interpretation of the archived GetLayers brief.
01 / Read the brief
The text source is 10-RELAY-WORKFLOW-AUTOMATION.md. Reference media could not be inspected in this environment. This is not a pixel-identical reconstruction.
02 / Establish a visual system
Background #0c100b, foreground #f5f7ec, accent #c7f76d, surface #171f13. Local fonts, a responsive 1320 px maximum grid, and a site-specific hero composition establish the hierarchy.
03 / Build the signature mechanism
A perspective CSS workflow window connects four semantic DOM nodes. A guarded async sequence lights each node in order, announces completion once, and re-enables the run button. A 10k–10M range meter computes the published linear event-price formula.
04 / Make it interactive
- Run the workflow twice and verify all four completion states
- Set event volume to 10,000 and 10,000,000; expect $19 and $8,011
- Check keyboard focus and mobile node labels
05 / Record the adaptations
Native DOM/CSS light connections replace a continuous WebGL beam and blocking preloader. No actual Stripe, Slack, webhook, ledger, or billing integration. Motion does not obscure readability.
Shared architecture: local Three.js, native scrolling, a single frame scheduler, capped pixel density, offscreen/hidden-tab suspension, reduced-motion support, CSS fallback, and no backend.
06 / Validate honestly
See the actual validation record for test results. Automated checks do not replace manual screen-reader testing or reference-image comparison. All readouts and submissions are illustrative and local.
07 / Reproduce the build
python3 -m http.server 8080 --bind 0.0.0.0 # Open /getlayersai/sites/relay/ cd getlayersai python3 tools/build.py python3 tools/verify.py npm ci npm test
Edit this site's record in tools/catalog.py before rebuilding. Shared rendering and interactions are in shared/scenes.js and shared/interactions.js. Generated HTML and documentation will be overwritten on regeneration.