feat(marketing): redesign the site around product core values

[shivamhwp]

What changed

• redesign the marketing experience around T3 Code's product promises
• add five distinct hero directions with channel-specific visual worlds
• showcase the web, desktop, and mobile experiences with realistic demo states
• improve responsive behavior, downloads, release metadata, and supporting marketing pages

Why

The marketing site should make T3 Code's core value obvious before asking visitors to understand the implementation. This draft puts the product experience first and keeps multiple hero directions available for review before choosing the final presentation.

Impact

Visitors get a clearer, more visual explanation of how T3 Code works across surfaces. Maintainers can review the complete redesign and compare the hero directions in one branch.

Validation

• formatting check for all changed text files
• marketing, web, and client-runtime type checks
• 56 focused marketing, web demo, and client-runtime tests
• git diff --check

Generated with GPT-5.6 using the Codex harness in T3 Code.

Note

Redesign marketing site with stage-aware downloads, interactive demo, and mobile app support

• Rewrites the marketing homepage hero with an embedded interactive iframe demo, concept selector, mobile screenshot carousel, and Latest/Nightly/Dev channel picker that updates download links and CTA art live.
• Adds an in-browser demo backend (server.ts) serving real RPC contracts over in-memory WebSocket pairs, enabling the embedded demo to run without a real backend.
• Adds a release channel picker to the download page that shows platform-appropriate binaries for Latest/Nightly or source build instructions for Dev.
• Updates Layout.astro with Open Graph/Twitter meta tags, a dynamic favicon per stage, a multi-column footer, and a nav-level stage toggle; removes the live GitHub star count.
• Adds a CI workflow step (mobile-showcase-screenshots.yml) that commits updated iOS/Android screenshots to marketing assets after successful screenshot generation.
• Adds a 'Mobile apps' section to the Connections settings panel linking to the App Store and Google Play.
• Risk: the demo build (VITE_T3CODE_DEMO=true) disables client tracing entirely and uses hash-based routing, which differs from production behavior.

📊 Macroscope summarized cc45c83. 34 files reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted

🗂️ Filtered Issues

No issues evaluated.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: db5a445a-7587-45e1-8ea4-144e1aa8d66f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

🟠 High state/server.ts:430

resolveServerConfigValue now accepts a live projection from the previous session when its serverVersion differs from the new session's initialConfig only by a nightly/dev suffix. During a real reconnect or channel switch (e.g. cached/live 1.0.0 followed by a bootstrap 1.0.0-nightly.20260701.1), this causes the old session's providers, settings, and config to override the new session's bootstrap configuration — the prior exact-equality comparison intentionally rejected stale cross-session projections. Consider restoring the exact comparison for production state, or gating the nightly/dev equivalence to demo-only contexts.

🤖 Copy this AI Prompt to have your agent fix this:

In file @packages/client-runtime/src/state/server.ts around line 430:

`resolveServerConfigValue` now accepts a live projection from the previous session when its `serverVersion` differs from the new session's `initialConfig` only by a nightly/dev suffix. During a real reconnect or channel switch (e.g. cached/live `1.0.0` followed by a bootstrap `1.0.0-nightly.20260701.1`), this causes the old session's providers, settings, and config to override the new session's bootstrap configuration — the prior exact-equality comparison intentionally rejected stale cross-session projections. Consider restoring the exact comparison for production state, or gating the nightly/dev equivalence to demo-only contexts.