Runway
HomeComponentsPricingDev Tools

Start Here

  • Overview
  • Installation
  • Project Structure

Customize

  • Customization
  • Runtime Configuration
  • Site Content

Build

  • Components
  • Layout
  • Brand

Product Systems

  • Auth, Billing, Email, SEO, Security
Loading docs page
Built withRunway
  1. Customize
  2. Site Content

Site Content

How homepage messaging and public-site structure are driven from config.

Update homepage copy

In this baseline, src/config/landing-page.js owns the post-hero narrative and src/config/foundation.js owns the foundation feature inventory. Change section content, proof points, and CTA support there before you reach for layout code.

js
1export const launchStorySteps = [{ title: "Acquire and activate", description: "..." }];
2export const foundationFeatures = [{ title: "Billing", bullets: ["..."] }];

Navigation and CTA links

Shared site nav and footer links live in src/config/navigation.js. Keep CTA destinations real and current so the public site does not point at missing sections or dead routes.

Baseline rules

  • Sell outcomes, not internal architecture
  • Keep the homepage concrete and commercial
  • Prefer deleting weak sections over preserving filler
  • Let the docs explain implementation details when they are actually useful

Related

  • Customization
  • Brand
  • Layout

On This Page

  • Update homepage copy
  • Navigation and CTA links
  • Baseline rules

Related

  • Customization
  • Brand
  • Layout