Customization

First edits

Most teams should make these changes first:

1. Replace homepage messaging in src/config/landing-page.js and src/config/foundation.js.
2. Update shared nav and footer links in src/config/navigation.js.
3. Rename the brand surfaces and public copy that still refer to Runway.
4. Review src/config/runtime.js before enabling providers or shipping flows.

Content and brand

Keep content changes in the content and config layers whenever possible:

• Homepage messaging: src/config/landing-page.js and src/config/foundation.js
• Shared navigation: src/config/navigation.js
• Docs content: src/docs/content/*
• Brand components: src/components/brand/*

That keeps copy edits and structural edits reviewable without mixing them into unrelated UI logic.

Product-specific systems

Once the public shell is aligned, move into the systems you actually need:

• Auth and billing if the product has accounts and payments
• Email if you need transactional lifecycle messages
• SEO if you are changing public metadata, canonical routes, or social previews
• Security if you are turning on providers, secrets, or protected flows

Read Auth, Billing, Email, SEO, Security before turning those pieces on.