## Overview
Same AInstein visual identity as v1 — default shadcn theme, brand-blue primary, system sans, no custom CSS variables — but rearranged rhetorically. Where v1 leads with the product, v2 leads with **the problem**: the search landscape has changed, and most teams aren't equipped for it. The page reads like a technical argument that builds toward AInstein as the inevitable answer. More editorial than v1 — larger headlines, longer leads, dense structured information before any product surface appears.
## Colors
Identical to v1 — inherits the default shadcn theme. See `apps/shots/projects/ainstein/templates/v1/DESIGN.md` for the token list. No overrides.
## Typography
Identical to v1 — system sans at every level, tight tracking on headlines, semibold/medium weights. No custom font wrapper.
## Elevation
Identical to v1 — inherited from the shadcn theme.
## Components
Composed entirely from `@repo/design-system/blocks` — no custom section components.
1. **Hero1** — centered, copy-only hero with fade-in-blur reveal. No image. Lets the headline land alone.
2. **Layout1** — "The new search reality" with badge, large heading, supporting paragraph, and four bullet points covering the shift to AI answer engines.
3. **Feature24** — "The bottleneck most teams face" with a checked grid of the five real production failures.
4. **Feature24** (second instance) — "Who this is for" with the four canonical audience segments.
5. **Process1** — same six-step Discover → Measure workflow as v1.
6. **Cta1** — closing centered card CTA.
## Do's and Don'ts
- Do reach the workflow section having already convinced the reader they need it.
- Do keep all variation purely structural — different blocks in a different order.
- Do compose from `@repo/design-system/blocks` only.
- Don't override the shadcn theme to differentiate from v1.
- Don't introduce a product image before the problem has landed.