Configuration

Almost everything a buyer can change lives in a single file. Edit src/config/site.ts and the rest of the app reads from it through src/lib/content.ts.

One file to rule them all

The siteConfig object is the single source of truth for brand, copy, navigation, pricing, FAQ, testimonials, docs, and more. You should rarely need to touch component code to rebrand Loop.

// src/config/site.ts
export const siteConfig = {
  name: "Loop",
  tagline: "Async standups for distributed engineering teams",
  email: "hello@loop.example",
  url: "https://loop.example",
  // ...
};

Brand and contact

Start at the top of the file. Change name, tagline, headline, and sub to your product, then update the contact block:

• email — shown in the footer and contact form
• phone — optional, hidden if left blank
• supportUrl — links out to your helpdesk
• url — production URL used for metadata, sitemap, and OG tags

Localized fields

Most strings carry optional *Es, *Fr, and *Pt siblings. When a translation is missing, Loop falls back to the English value, so you can translate incrementally.

{
  title: "Pricing",
  titleEs: "Precios",
  titleFr: "Tarifs",
  titlePt: "Preços",
}

Structured content

Arrays drive whole sections of the site:

• nav — top navigation items
• features6 / features3 / featureTabs — feature layouts
• pricing and pricingMatrix — plans and the comparison table
• testimonials, faqCategories, docs, competitors

Add, remove, or reorder entries and the pages update on the next build.

Where to go next

Once the copy is yours, move on to Themes and Fonts to dial in the look.