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

PartLocationPage
Pagesapps/web/pages/(marketing)/Adding a Page
Search and link previewsapps/web/lib/seo.server.ts, apps/web/config/seo.config.tsSEO
Header and footerapps/web/pages/(marketing)/layout.tsxRebranding
Header, footer and legal linksapps/web/config/marketing-navigation.config.tsRebranding, Navigation
Copyapps/web/messages/<locale>/marketing.jsonRebranding
FAQ orderapps/web/config/faq.config.tsRebranding
Pricing plans, card order and buttons (ctaHref / ctaLabel)apps/web/config/billing.config.ts/pricing buttons go to sign-up by default
Legal textapps/web/content/legal/*.mdRebranding
Blog posts and changelog entriesapps/web/content/blog/, apps/web/content/changelog/, apps/web/config/content.config.tsBlog and Changelog
Help docs and their orderapps/web/content/docs/ (meta.json per folder)Help Docs
Content from a CMS or APIapps/web/config/content.server.tsContent Sources
Components@kit/ui/marketing (packages/ui/src/makerkit/marketing/)Rebranding
Caching rulesapps/web/lib/cacheable-routes.server.tsCaching

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 →