Custom Landing Page

MuseMVP landing pages are composed in the route file, in render order. Keep src/config/index.ts for brand, auth, billing, and contact delivery. There is no systemShowConfig, useSystemComponent, or landing-page PLACEHOLDER block.

Config Directory Structure

Home Page

src/app/(landing-page)/[locale]/(home)/page.tsx renders sections sequentially and keeps force-static:

export const dynamic = "force-static";

export default async function Home({ params }) {
  const { locale } = await params;
  setRequestLocale(locale);
  return (
    <>
      <Hero />
      <Features />
      <CTASection />
      <PricingSection />
      <FaqSection />
      <Newsletter />
    </>
  );
}

To hide a section, remove its JSX. To replace a section, change the import. To reorder, move the JSX.

Header and Footer

Edit the components. Do not add a switch matrix to config.ui.

Hide a public page by deleting its link in header/footer. Delete the route file only if the URL should not stay reachable. Pricing links still follow config.payments.enableBilling.

Pricing Page

The pricing page at src/app/(landing-page)/[locale]/pricing/page.tsx is controlled by config.payments.enableBilling. When false, the pricing route redirects to home. Homepage pricing hides itself inside PricingSection instead of using a route-level flag.

Pricing copy and plan display come from src/config/saas/pricing-desc-usage.ts and pricing-desc.ts.

• pricing-desc.ts: plan titles, descriptions, and feature lists
• pricing-desc-usage.ts: actual purchasable price items, stable app productId values, and billing behavior. Provider product IDs live in Admin → Runtime settings.

If you want to show a compare-at/original price such as $249 and charge $199, configure it in pricing-desc-usage.ts:

{
  type: "one-time",
  productId: billingProductCatalog.lifetime.productId,
  originalAmount: 249,
  amount: 199,
  currency: "USD",
}

Field semantics:

• amount: the actual checkout amount sent to the billing gateway
• originalAmount: optional UI-only compare-at price rendered as a strikethrough price in the pricing card

originalAmount is displayed only when it is greater than amount. If omitted, the pricing UI falls back to showing only the current price.

FAQ

FAQ data is defined in src/modules/landing-page/home/components/FaqSection.tsx via two hooks:

• useFaqData(): FAQ list (question, answer) — sourced from i18n translations
• useFaqSectionData(): FAQ section title, description — also from i18n

To customize FAQ content in this template, edit faq.json in src/i18n/translations/en/ and src/i18n/translations/zh/. Derivative products should put replacement copy in mvp.json instead of overwriting those files.

Changelog

/changelog renders a three-column sticky timeline in src/modules/landing-page/changelog/changelog-page-content.tsx. Entry bodies come from content/changelog/ MDX. UI strings, including the expand-full-notes label, live in changelog.json.

Legal Pages

Legal pages are independent MDX files. Edit them directly:

Keep frontmatter title. Do not add another # H1 in the body; the route already renders the title. Footer labels live in home.json.

Quick Customization Flow

Related Docs