Landing page and marketing pages

Comprehensive documentation for KilatKoding landing pages and public marketing pages.

This feature is the public entry layer of your product. It is where potential users first understand the value proposition, use cases, pricing, CTA structure, legal pages, and entry points to other features such as waitlist, contact, or checkout.

What this feature includes

This area covers the main landing page and public marketing pages such as:

• /
• /about
• /compare
• /affiliates
• /privacy
• /terms
• /roadmap
• /status
• /open
• /use-cases
• /docs/components

Other public-facing pages such as /contact, /waitlist, /checkout, and /blog are also visible to end users, but they have their own feature docs because their dependencies are different.

Related routes

Route	Type	Purpose
/	Public page	Main landing page
/about	Public page	Explains the product or team
/compare	Public page	Compares the offer or alternatives
/affiliates	Public page	Affiliate or partner page
/privacy	Public page	Privacy policy
/terms	Public page	Terms of service
/roadmap	Public page	Public roadmap
/status	Public page	Service status
/open	Public page	Open startup metrics
/use-cases	Public page	Use case gallery
/docs/components	Public page	Public UI component showcase

Public routes such as /contact, /waitlist, /checkout, /order/[id], /blog, and /changelog are also closely related to the marketing layer, but they are documented in their own feature pages so the explanation can stay more focused.

Who uses it

• potential users,
• active users who still read public pricing or updates,
• partners or clients evaluating the product,
• internal teams validating copy and funnel quality.

Main dependencies

Area	Required?	Notes
Page copy and content	Yes	This is the core of the marketing layer
config/site.ts	Strongly recommended	Product name, description, and base URL affect metadata
config/navigation.ts	Strongly recommended	Controls public navigation paths
config/marketing-designs.ts	Optional but important	Controls marketing visual presets
Legal pages	Required for public launch	Privacy and terms should match the live brand and operations

Main files and areas

Area	Most common files
Product identity	config/site.ts
Marketing navigation	config/navigation.ts
Marketing visual presets	config/marketing-designs.ts
Landing page sections	components/sections/*
Global marketing styling	app/globals.css, app/marketing.css, tailwind.config.ts
Legal pages	app/(marketing)/privacy/page.tsx, app/(marketing)/terms/page.tsx
Roadmap	config/roadmap.ts
Status page	config/status-page.ts
Open startup metrics	config/open-startup.ts

What teams usually customize

• hero headline, subheadline, and CTA,
• feature sections, FAQ, testimonials, and pricing summary,
• positioning copy for the target audience,
• legal page content,
• roadmap, status, and open startup visibility,
• visual theme, preset, and brand feel.

When this feature should be simplified

This area usually needs to be reduced when:

• you only need a simple waitlist funnel,
• the product does not need pages such as roadmap, status, or open,
• too many CTA links still point to disabled features,
• the copy still feels like a boilerplate instead of a real product.

Verification checklist

1. Product name, description, and CTA copy match the live brand.
2. Public navigation only shows pages you actually use.
3. No CTA points to a disabled feature.
4. Privacy and terms contain final content.
5. Roadmap, status, and open pages do not contain confusing placeholders.
6. Meta title, description, and preview images are ready for launch.

If you want to review public-facing features that often connect directly from the marketing layer, continue to Contact form, Waitlist, and Blog and MDX content.