Build the accessible RelayView marketing page #4

New Issue

2026-10-08T17:28:19-04:00

anodyine commented

2026-10-08 17:28:19 -04:00

Problem

Recruiters and prospective customers need a concise, usable public explanation of RelayView.

Scope

Implement the approved claims brief in the separate relayview-site repository. Include the hero, problem, supervised workflow, Community/Teams distinction, trust direction, and calls to action. Use original or properly licensed assets and keep private product code out of the site.

Acceptance Criteria

Content follows the approved claim classification without implying planned features are available.
Mobile, tablet, and desktop layouts are readable without horizontal overflow.
Navigation, headings, controls, keyboard use, focus, contrast, and reduced motion are verified.
Calls to action work or explain their pre-release state honestly.
A production build and focused checks pass; visual review evidence is attached.
Documentation disposition is recorded.

Ablation decision

not_required: marketing interface only.

## Problem Recruiters and prospective customers need a concise, usable public explanation of RelayView. ## Scope Implement the approved claims brief in the separate relayview-site repository. Include the hero, problem, supervised workflow, Community/Teams distinction, trust direction, and calls to action. Use original or properly licensed assets and keep private product code out of the site. ## Acceptance Criteria - Content follows the approved claim classification without implying planned features are available. - Mobile, tablet, and desktop layouts are readable without horizontal overflow. - Navigation, headings, controls, keyboard use, focus, contrast, and reduced motion are verified. - Calls to action work or explain their pre-release state honestly. - A production build and focused checks pass; visual review evidence is attached. - Documentation disposition is recorded. ## Ablation decision `not_required`: marketing interface only.