Details

MVP ForSale — a Server-Rendered Promo Storefront for Your Marketplace Catalog

A themed, read-only listing storefront built on Next.js 16 (App Router) and React 19. Point it at an MVP Hub-style public API and it becomes a second, fully crawlable surface for the same catalog — with its own domain, its own look, and every buy action deep-linking back to your marketplace with UTM attribution.

Why you need this MVP

A marketplace lives or dies on discovery. Your main product handles accounts, checkout, and seller tooling — but a promo storefront is a different job: a lightweight, SEO-first catalog surface you can put on a memorable domain, re-skin per audience, and iterate on without touching the core platform.

The hard part of that job is invisible: server rendering so crawlers see real HTML, per-listing structured data so Google shows price and stars, a sitemap that tracks the live catalog, canonical URLs, honest fallbacks when data is missing, and an image pipeline that doesn't break when a CDN host changes. This storefront ships all of it as a finished baseline.

Key benefits

• Server-rendered catalog. Every page fetches the catalog server-side — full HTML for crawlers and link previews, no loading-spinner shell. API responses are cached for 60 seconds, including the POST detail endpoint.
• The SEO layer is done. Per-listing metadata + Open Graph, schema.org Product JSON-LD (offer price, aggregate rating — emitted only when real data exists), canonical URLs, catalog-driven sitemap.xml, robots.txt, noindexed search results.
• Honest by construction. No fabricated reviews, no $0 prices for unpriced listings, demo buttons only when a real demo link exists, sold-out and coming-soon statuses respected. Trust is the product; the storefront never lies about the catalog.
• Real catalog UX. Faceted search (category, tech stack, capability, price slider), category landing pages with subcategory chips derived from live data, sortable browse grid, listing detail with gallery, seller markdown body (raw HTML stripped), readiness badges, and multi-variant "from" pricing.
• Re-skinnable theme. The hand-drawn wireframe aesthetic (Kalam handwriting font, sketch browser chrome) lives in one CSS file with design tokens at the top. Swap the tokens, keep the machinery.
• Ops baseline included. Dockerfile.deploy builds a Next.js standalone node:24-alpine image (non-root) with a /api/health liveness route for blue/green swaps; build-time env arrives as a BuildKit secret so nothing lands in a layer. The image-optimizer allowlist is derived from env, with a safe per-image unoptimized fallback for unknown hosts.
• Fails loudly, degrades gracefully. Production refuses to run with an unset API origin; if the API goes down at runtime, cached pages keep serving and cold requests show a clear source-connection error instead of a blank page.

How you can use it

• Marketplace operators — run a promo domain for the same catalog your main product serves
• Agencies — white-label a listing storefront per client or per niche
• Founders — validate a vertical (e.g. "booking apps only") with a themed slice of an existing catalog
• Developers — a clean, dependency-light reference for App Router catalog SEO done right

What is included

• Next.js 16 App Router + React 19, plain JavaScript, zero UI-framework dependencies
• Home, browse, faceted search, category landing pages, listing detail
• Per-listing metadata, OG tags, Product JSON-LD, canonicals, sitemap, robots
• Sanitised seller-markdown rendering (react-markdown, raw HTML stripped)
• Env-driven config: API origin, public marketplace origin, canonical site origin, optional image CDN allowlist
• Dockerfile.deploy (standalone output, BuildKit env secret, non-root, health route)
• Hand-drawn wireframe theme in a single tokenised CSS file

Tech stack at a glance

• Frontend: Next.js 16 (App Router) + React 19, JavaScript
• Rendering: dynamic server rendering with 60s API response caching
• SEO: schema.org Product JSON-LD, OG, sitemap, robots, canonicals
• Markdown: react-markdown (raw HTML stripped)
• Ops: Docker standalone image, BuildKit secret env, liveness probe

Pluggable against any backend exposing the /api/mvps list + detail contract — MVP Hub out of the box.