A production-grade React storefront for headless WordPress and WooCommerce.
Live flagship · Documentation · Shortcode library · Report an issue
Every managed headless environment runs the same storefront release with a capability-aware backend profile. The native WordPress development backend is listed separately for setup visibility. These badges are live HTTP status checks, not manually maintained labels.
| Environment | Profile | Status |
|---|---|---|
| superfunky.pro | Flagship Pro commerce |  |
| developer.superfunky.pro | Developer example |  |
| free-blog.superfunky.pro | Free CMS/blog |  |
| free-shop.superfunky.pro | Free commerce |  |
| pro-shop.superfunky.pro | Pro commerce |  |
| dev.superfunky.pro | Default WordPress backend |  |
The workspace is split into deliberate public package boundaries:
Public npm-version badges will replace the workspace badges as each package is published.
git clone https://github.com/coded-letter/superfunky-storefront.git
cd superfunky-storefront
corepack enable
pnpm install
pnpm devThe development fallback uses the public dev.superfunky.pro WPGraphQL backend, so the
storefront starts without requiring a local WordPress installation. To use your own backend:
cp apps/storefront/.env.example apps/storefront/.envVITE_GRAPHQL_ENDPOINT=https://wordpress.example/graphql
VITE_SITE_URL=http://localhost:4173Never commit private WordPress, commerce, payment, or deployment credentials.
- Static route generation and complete CMS route discovery.
- React 18, Vite, TypeScript and route-level code splitting.
- Pages, posts, taxonomies, authors, navigation and SEO.
- WooCommerce catalog, cart, checkout, account and order flows.
- Community profiles, posts, media, comments and marketplace presentation.
- Capability-aware free, blog, shop and Pro backend profiles.
- Stable WordPress content styling, Layout Studio and shortcode rendering.
- Sitemaps, feeds, structured data, AI discovery files and production headers.
- Provider-neutral static output, with a Netlify deployment adapter and static failover.
apps/storefront Routes, feature composition and remaining domain presentation
packages/cms Extracted CMS normalization primitives
packages/commerce Extracted commerce normalization primitives
packages/sdk Backend transport, environment, cache and React data hooks
packages/ui Reusable presentation and current shared application primitives
packages/shared Framework-independent schemas, validators and route contracts
Backend transport and incremental caching are private to the SDK. CMS and commerce package roots contain the first extracted domain primitives; the storefront app still owns feature composition while those public boundaries expand without duplicating implementations.
pnpm dev # start the storefront
pnpm test # run the complete test suite
pnpm build # create the production storefront and static route inventoryThe default development backend is intended for exploration and local setup. Production projects should supply their own WPGraphQL endpoint and capability profile. WooCommerce, Polylang and SEO integrations are detected and gated instead of being unconditional.
The WordPress backend theme is distributed separately after its release and security validation. The storefront remains independently forkable under the MIT licence.
MIT. Commercial hosting, migrations, updates and support are available from Superfunky.