1
Campaign-specific composition
This route can have different sections, ordering, messaging, and visuals without touching the main homepage.
Landing 1 Demo
Performance landing architecture for fast campaign launches.
This demo variant has its own shell and page composition, while still reusing shared CTA routing, topic validation, and legal pages. Perfect for testing ad traffic without coupling everything to the main homepage.
- Fast launch quiz flow
- Different visual language
- Same CTA routing
- Shared legal foundation
Variant Capabilities
Own header and footer
Route-local shell per landing
Own sections
Swap storytelling and order freely
Shared app logic
Buttons keep consistent behavior
Shared legal routes
One source of truth for policy pages
How It Works
Separate route, separate shell, same conversion engine.
2
Shared conversion logic
All sign-in and action buttons still point to the same app entry and quiz flow.
3
Safer iteration
You can run experiments for paid traffic or seasonal campaigns without destabilizing the default landing.
Demo Outcome
New landing variants become additive, not destructive.
The main homepage keeps its own implementation under one route group, while campaign pages can diverge visually and structurally without branching business logic everywhere.
Shared Logic
- All `Log In` buttons route to `app.draftout.ai`.
- Hero form still validates before redirecting to quiz.
- Legal links stay centralized.
- New landing routes can reuse common primitives only where needed.
FAQ
Demo answers for the architecture
Can landing-1 have a different header and footer?
Yes. In this architecture, each landing route owns its local shell, so branding and navigation can differ completely.
Do legal pages stay shared?
Yes. Privacy, Terms, Subprocessors, Data Processing, and Refund Policy stay global and can be linked from every landing variant.
Can CTA logic stay the same?
Yes. The shared HeroTopicCta and CTA URLs keep redirect behavior consistent across all landing variants.