Launch content, homepage, public experience, and mobile parity

Purpose

The public experience is CMS-driven where possible and protected by fallback navigation. Visitors should always be able to understand what the marketplace offers, browse products, find Help/Support/Trust links, and reach legal/contact pages even when dynamic content is unavailable.

Homepage and public pages

1. 1Use /admin/pages to manage homepage sections and public CMS pages such as About, How it works, FAQ, Contact, Trust/Safety, Terms, and Privacy.
2. 2Ensure the homepage includes required section types before launch: hero, marquee, rich text, feature grid, steps, pricing, and CTA.
3. 3Use /admin/navigation to add only live routes to the header, footer, and legal link groups.
4. 4Use /admin/theme to keep brand name, logo, colors, and tagline consistent across public pages.
5. 5Verify fallback navigation still exposes Marketplace, Help Center, Support, Trust Center, FAQ, Contact, Terms, and Privacy when CMS navigation fails.

Launch content checklist

• ✦ Homepage explains the marketplace value proposition for buyers, creators, and influencers.
• ✦ Marketplace has approved, safe, complete product listings with categories and prices.
• ✦ Creator storefronts have profile copy, featured products, and unavailable-state messaging.
• ✦ Help Center includes buyer, creator, influencer, admin, mobile, support, provider, payments, security, and runbook guidance.
• ✦ Trust Center explains public-safe protections without revealing bypasses or private controls.
• ✦ Contact and Support routes accept safe customer context and warn against sharing secrets.
• ✦ SEO metadata, canonical paths, robots settings, redirects, and structured data are reviewed before launch.

Premium public experience expectations

Keep public pages polished, responsive, and consistent with the marketplace design system. Avoid replacing dynamic storefront, marketplace, or support experiences with plain static text. Use screenshot-ready documentation areas for future validated screenshots and include accessible alt text for every visual asset.

Mobile parity checklist

• ✦ Marketplace, product detail, checkout-complete deep link, Library downloads, notifications, Trust, Support, Creator, Influencer, and Admin tabs are represented in mobile navigation according to role.
• ✦ Mobile Trust Center content loads from public-safe settings and falls back to offline-safe copy.
• ✦ Mobile Support is available to signed-in users for ticket creation, replies, AI-safe drafts, and close/reopen actions; guest contact remains web-first.
• ✦ Push notification preferences and device registration require provider readiness before they are promised as production push delivery.
• ✦ Deep links should be tested for marketplace, product, order completion, order detail, Library, notifications, support, trust, creator, influencer, and admin paths.

Security and trust content rules

Public trust documentation may describe entitlement checks, signed links, moderation, rate limits, public-safe APIs, auditability, support safety, and privacy expectations. It must not expose secret names/values, webhook bypass details, fraud-scoring internals, private incident timelines, admin credentials, raw provider payloads, or customer-sensitive data.