Three distinct landing page variants served from a single NextJS repository using route-based versioning (/v2, /v3). Each version uses a different design system, font stack, and hero copy while sharing the same underlying infrastructure.
The Problem
Security founders testing positioning and messaging typically spin up separate repos or duplicate entire sites. This creates maintenance overhead, inconsistent deployments, and no clean way to share the same tooling across variants.
The Solution
Route-based versioning in a single NextJS repo:
/serves the default dark/teal variant/v2and/v2/*serve a white editorial variant with different fonts and hero copy/v3and/v3/*serve a luxury dark variant with a different accent palette- All inner pages (Solutions, ROI Calculator, Blog, etc.) inherit their version's theme via a shared layout wrapper
- Zero duplication of inner page logic; only hero copy and theme tokens change per version
Use Cases
- A/B testing hero messaging with security decision-makers (CISOs, SOC managers, founders)
- Testing dark vs. light vs. editorial aesthetics on the same domain without separate deploys
- Validating which positioning resonates before committing to a full redesign
Impact
- Single deployment for 3 audience experiments
- All inner pages automatically themed via layout wrapper; no per-page changes required
- Version-aware routing keeps URLs clean and shareable for stakeholder review
.png)
.png)
