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.
| Change | Where | Notes |
|---|---|---|
| Logo / favicon | public/logo*.png, public/favicon* | Keep the same filenames to avoid touching components |
| Site name / SEO defaults | src/lib/seo.ts (SITE_NAME, default keywords) | Used by every page head |
| Marketing copy | messages/{en,zh,de}/*.json | Paraglide message catalogs; no code edits needed |
| Blog posts | content/english-blog/*.md + publish pipeline | Frontmatter-driven; see the blog docs |
| Template catalog | Admin catalog (DB) or src/content/templates/*.json fallback | DB is the source of truth when present |
| Pricing / plans | Billing catalog + /pricing page data | Prices come from Stripe, not hard-coded strings |
| Colors / theme | CSS variables in the global stylesheet | Change tokens, not individual components |
Branding without forking components
- Replace the logo files in
public/(same names, same dimensions). - Update
SITE_NAMEand the default OG image insrc/lib/seo.ts. - Edit the footer/about copy in the message catalogs.
- Adjust theme tokens (e.g.
--coral,--sea-ink) in the global CSS.
Good to know
Keeping filenames and message keys stable means
git pullfrom 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/andsrc/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:
- Add the locale to the Paraglide config and create
messages/<locale>/. - Translate the catalogs (machine translation is fine for a first pass; review marketing copy).
- Add blog translations under
content/i18n/<locale>/with matchingslugandgroup_id. - 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:
- Update the Stripe product/price.
- Update the catalog row's billing references.
- 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; editmessages/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.