Summary
The SO1 marketing landing page (so1.io) reached build-verified state — production build passing, dynamic social sharing images working, Vercel deployment configured. A full monorepo audit produced 15 new issues and a prioritized execution plan across 8 future taskset blocks.
What this means for the business
Landing page is deployment-ready
The page atplatform-tools/so1-landing/ builds cleanly and has all infrastructure in place for a Vercel deployment: OG images render the brand identity automatically for social shares (Mars planet, tagline, telemetry bar at 1200x630), the favicon is generated dynamically, and a vercel.json wires the build command. To go live, create a second Vercel project pointing at Root Directory platform-tools/so1-landing and assign the so1.io domain.
Design system is aligned across products
The “Hab Visor” design system tokens on the landing page now match the Rover’s token values exactly — same surface opacities, blur levels, border colors, status colors (success/warning/danger/info), and background gradients. When the Rover is rebranded from “Glass” to “Visor” naming (issue #50, ~174 references), both products will share one visual language without a shared CSS package.Accessibility gaps identified before launch
The audit found 3 WCAG compliance issues that should be fixed before public launch: no skip-to-content link (required for keyboard navigation), a duplicate heading structure, and 5 text styles that fail minimum contrast requirements on the dark background. These are scoped as the first taskset to execute (TASKSET 9), roughly one session of work.Roadmap is now visible
The 37 open issues across the monorepo are organized into 8 taskset blocks with a recommended execution order:| Block | Focus | Effort |
|---|---|---|
| T9 | Landing launch readiness (a11y, error handling) | ~1 session |
| T10 | Animation expansion + constants cleanup | ~1 session |
| T11 | CI pipeline for landing + shared package | ~1 session |
| T12 | Shared types unification (3 diverged copies) | ~1 session |
| T13 | Vercel deployment + security headers | ~1-2 sessions |
| T14 | Rover Hab Visor rebrand (~174 refs) | ~1 session |
| T15 | BFF test coverage + Docker CI | ~2 sessions |
| T16 | Monorepo hygiene (CODEOWNERS, Dependabot) | ~1 session |
Action items
- Vercel: Create second project for landing, set Root Directory to
platform-tools/so1-landing, assignso1.iodomain - Pre-launch: Execute TASKSET 9 (issues #51-#55, #57) to fix a11y and error handling before going public
- CI: Landing has no CI coverage yet — execute TASKSET 11 (issue #60) before merging further PRs
- Shared types: Three diverged copies of the type package will cause drift bugs — prioritize TASKSET 12 (issue #61) after CI is in place