Clarity before growth hacks
Build a landing page system that can survive the product getting real.
Kevly is positioned as a disciplined marketing surface: clear offer, reusable sections, and a stack that stays fast on Vercel without overbuilding on day one.
- Sharper headline and positioning decisions
- Reusable sections for launch, waitlist, and pricing pages
- A codebase that scales without turning into CMS theater
Launch Narrative
The default homepage should explain the offer in under 15 seconds.
Value proposition
Turn scattered product thinking into a convincing landing page system.
Why this architecture
Thin routes, composable sections, and shadcn primitives keep the marketing layer readable while the product is still moving.
What gets added later
Waitlist forms, analytics, and more static pages only when the MVP needs them.
Foundation
A simple architecture that makes future static pages cheaper to build.
This repo is scaffolded for a landing page first, with a direct path to about, privacy, legal, and other static pages without inventing a fake content platform around them.
Message discipline
Capture value proposition, positioning, proof, and CTA structure in one place so the page does not drift into generic copy.
Reusable page sections
Compose the marketing surface from focused sections and shadcn primitives instead of one oversized homepage file.
Fast iteration on Vercel
Lean into static defaults, preview deployments, and a file structure that stays simple while the product evolves.
App Router for route ownership
Route files stay thin. Marketing composition lives in components, while metadata and routing remain at the app boundary.
shadcn for primitives, not templates
Use shadcn for buttons, cards, inputs, and future form primitives. Keep brand expression inside page-specific components.
Implementation path
Start with a few explicit static routes, then add complexity only when repetition makes it necessary.
For an MVP with a landing page, about page, privacy policy, and a few more static pages, the right bias is straightforward route files plus shared UI. Not a CMS, not MDX, and not a site builder abstraction.
01
Define the offer
Keep the actual product promise, proof points, and CTA explicit before creating more pages.
02
Ship the static surface
Add the homepage, about page, privacy policy, and any other static legal or company pages as direct routes.
03
Expand only when needed
Introduce forms, analytics, and any richer content system only after the static marketing surface is working.
Next step
Use this scaffold as the default shape for the first real Kevly launch page.
The current homepage is intentionally thin on product specifics. The architecture is ready for real content, proof, waitlist capture, and future pages without rewriting the stack.