Marketing Pages
The public site: landing page, FAQ and legal pages, served from the edge cache to first-time visitors.
The kit ships a public site in apps/web/pages/(marketing)/: a landing page (/), an FAQ (/faq), pricing (/pricing), a blog (/blog), a changelog (/changelog), a help center (/docs) and three legal pages (/privacy-policy, /terms-of-service, /cookie-policy). They share a header and footer, render only content from the repository (or a sanitized content source), never the request, and are served from Void's edge cache to visitors without cookies.
What's Where
| Part | Location | Page |
|---|---|---|
| Pages | apps/web/pages/(marketing)/ | Adding a Page |
| Search and link previews | apps/web/lib/seo.server.ts, apps/web/config/seo.config.ts | SEO |
| Header and footer | apps/web/pages/(marketing)/layout.tsx | Rebranding |
| Header, footer and legal links | apps/web/config/marketing-navigation.config.ts | Rebranding, Navigation |
| Copy | apps/web/messages/<locale>/marketing.json | Rebranding |
| FAQ order | apps/web/config/faq.config.ts | Rebranding |
Pricing plans, card order and buttons (ctaHref / ctaLabel) | apps/web/config/billing.config.ts | /pricing buttons go to sign-up by default |
| Legal text | apps/web/content/legal/*.md | Rebranding |
| Blog posts and changelog entries | apps/web/content/blog/, apps/web/content/changelog/, apps/web/config/content.config.ts | Blog and Changelog |
| Help docs and their order | apps/web/content/docs/ (meta.json per folder) | Help Docs |
| Content from a CMS or API | apps/web/config/content.server.ts | Content Sources |
| Components | @kit/ui/marketing (packages/ui/src/makerkit/marketing/) | Rebranding |
| Caching rules | apps/web/lib/cacheable-routes.server.ts | Caching |
The Rules in Short
- The folder decides. A page in
pages/(marketing)/is public and cacheable; nothing is listed by hand. - Repository content only. Marketing pages never read query parameters, request headers or user input: first-time visitors get them without a CSP, so injected content would run. Pages that take input go elsewhere.
- Content changes on deploy. Cached pages last until the next deploy, except a blog, changelog or docs read from a CMS, which refreshes after its
maxAge. See Caching.
Next: Rebranding →