Skip to content
Neon Coast
Open menu

Directory

Search the curated set. Filters stay in the URL, so a shared link opens the same slice.

17 of 47 resources

A short fork in the docs. Business Manager can create the storefront in a GitHub repository, or create the resources and leave code generation to your machine. A third path generates code against the demo instance from the terminal.

Salesforce Developers

Generates a project with pnpm dlx @salesforce/storefront-next-dev create-storefront and tells you to accept the demo defaults for the SLAS client, organization, short code, and site. The guide says this procedure is for exploring the code, not for creating your own storefront. The dev server example is http://localhost:5173.

Salesforce Developers

Business Manager creates the storefront plus API and Managed Runtime resources, and you generate the code locally with the CLI. The guide limits setup to one storefront per site and says a failed setup has to be deleted and recreated. Download env.txt from the completion page; the client secrets are not offered again.

Salesforce Developers

Business Manager connects to GitHub, creates a repository for the generated storefront, and sets up the API and Managed Runtime resources. You pick an organization or a personal account, grant the integration access, and download env.txt once for the local credentials.

Salesforce Developers

Reference for the sfnext CLI shipped in @salesforce/storefront-next-dev. Documented commands include create-storefront, dev, preview, push, create-bundle, and extensions. The page says not to install the package globally.

Salesforce Developers

Describes config.server.ts as the type-checked place for project settings, with environment overrides and a split between public and server-only values. getConfig() is the API for loaders, actions, and utilities. The page groups commerce, hybrid, auth, sites, images, and related options.

Salesforce Developers

Public fashion and retail starting point, CLI identifier fashion. The README describes a React Router 7 and React 19 storefront and tells you to copy .env.default, then run pnpm install and pnpm dev. The package name on branch latest is template-retail-rsc-app. Official architecture docs describe React Router 7 server rendering. This repository is not a Next.js application.

Salesforce Commerce Cloud

Public beauty and cosmetic vertical, CLI identifier cosmetic, package name storefront-cosmetic. It is a separate mirror from the retail template, with its own demo data. The template-features guide describes shade, ingredient, and how-to-use attributes for Beauty Next.

Salesforce Commerce Cloud

Public footwear vertical, CLI identifier footwear, package name storefront-footwear. Release notes for B2C Commerce 26.10 introduce Footwear Next for fit, size guides, and activity browsing. The template-features page lists the size, width, cushioning, and terrain attributes.

Salesforce Commerce Cloud

Public furniture vertical, CLI identifier furniture, package name storefront-furniture. Release notes for B2C Commerce 26.10 introduce Furniture Next for dimensions, materials, and delivery options. The features guide lists width, depth, height, and assembly attributes.

Salesforce Commerce Cloud

Public unthemed vertical, CLI identifier foundations, package name storefront-foundations. The features guide says Foundations keeps the commerce toolkit without an industry theme and omits several retail-only category fields. Its README is also the table of the other public vertical repositories.

Salesforce Commerce Cloud

Public repository listed by the foundations template as the luxury vertical, CLI identifier luxury, package name storefront-luxury. The same October 2026 stamp and SDK 1.4.0 pin were in package.json on branch latest. The Business Manager feature comparison does not document a luxury layout.

Salesforce Commerce Cloud

Instruction files a coding agent can load while you work in a Storefront Next project. The README groups them from sfnext-overview and project setup through routing, SCAPI, Page Designer, deployment, and tests. The skills directory contained 24 sfnext-* folders on 8 Nov 2026. Two sibling plugins target Figma and need a Figma connection this directory does not set up.

Salesforce Commerce Cloud

A symptom-by-symptom article for Page Designer on Storefront Next: a missing Storefronts menu, a missing local-preview module, Shopper Experience API 403s and 404s, manifest sync, and a crash the author ties to cloning branch latest during one week in September 2026.

Rhino Inquisitor

SFCC Learning's product page for a free PDF study guide covering architecture, setup, configuration, routing, data fetching, caching, and deployment, with a stated length of 573 pages. Only the product page was read.

SFCC Learning

64labs' accelerator for Storefront Next and Next.js: prebuilt UX patterns, state management, CMS, search, and payment connectors, and infrastructure templates. 64labs says it shortens a typical 9-month launch to 4-5 months. That timeline is the publisher's.

64labs · Access unknown

A build log of Après Studio, an AI-written Storefront Next storefront on a sandbox, covering OCAPI, SCAPI, WebDAV, and Managed Runtime, including failures and interventions. No public storefront URL is given.

Studio Science (Aaron Hutten, personal site)