Deployment Guide

Customization Guide

Where to change branding, content, pricing, and locales without breaking upgrades.

What to change first

Most teams only need four edits before launch: brand, content, pricing, and locales. Each lives in a clearly separated place so upstream updates stay mergeable.

ChangeWhereNotes
Logo / faviconpublic/logo*.png, public/favicon*Keep the same filenames to avoid touching components
Site name / SEO defaultssrc/lib/seo.ts (SITE_NAME, default keywords)Used by every page head
Marketing copymessages/{en,zh,de}/*.jsonParaglide message catalogs; no code edits needed
Blog postscontent/english-blog/*.md + publish pipelineFrontmatter-driven; see the blog docs
Template catalogAdmin catalog (DB) or src/content/templates/*.json fallbackDB is the source of truth when present
Pricing / plansBilling catalog + /pricing page dataPrices come from Stripe, not hard-coded strings
Colors / themeCSS variables in the global stylesheetChange tokens, not individual components

Branding without forking components

  1. Replace the logo files in public/ (same names, same dimensions).
  2. Update SITE_NAME and the default OG image in src/lib/seo.ts.
  3. Edit the footer/about copy in the message catalogs.
  4. Adjust theme tokens (e.g. --coral, --sea-ink) in the global CSS.

Good to know

Keeping filenames and message keys stable means git pull from upstream rarely conflicts with your brand changes.

Content model

  • Blog: Markdown files with YAML frontmatter (title, slug, date, tags, locale). The publish pipeline validates EEAT fields before writing to the database.
  • Docs: Markdown under src/content/deploy/ and src/content/features/, loaded at build time. Add a file, add a nav entry, done.
  • Catalog: products, locales, media, and FAQ rows live in the database; the admin UI edits them. Static JSON under src/content/templates/ is only a fallback.

Locales

The site ships with en, zh, and de. To add a locale:

  1. Add the locale to the Paraglide config and create messages/<locale>/.
  2. Translate the catalogs (machine translation is fine for a first pass; review marketing copy).
  3. Add blog translations under content/i18n/<locale>/ with matching slug and group_id.
  4. Add catalog locale rows for products you sell in that market.

Pricing and billing

Prices are read from the billing catalog (Stripe-backed). To change a price:

  1. Update the Stripe product/price.
  2. Update the catalog row's billing references.
  3. Bump the catalog cache version so pages pick it up immediately.

Do not hard-code prices in components — the pricing page, template pages, and checkout all read the same source.

What not to edit

  • src/paraglide/** — generated; edit messages/ instead.
  • src/routeTree.gen.ts — generated by the router.
  • Migration files already applied to production — add a new migration instead.

Upgrading safely

See License & Updates for the recommended merge workflow and what the license covers.