Experience Studio

Build customer-facing B2B commerce storefronts and themes on revenexx Revenue Cloud — the theme, the blocks, the data, the deploy, and running it in production.

Start here

Getting started

A themed, block-composable storefront running locally in minutes, then live on a preview URL.

Build your first theme

The hands-on tutorial track — scaffold, customize blocks, brand it, ship it.

The five parts of a storefront project

Build the theme

The Nuxt layer chain, the manifest, local development, and overriding anything the base layer ships.

Compose pages with Blökkli

Blocks as Vue components, the options an editor turns, and the ninety bundles you inherit.

Connect commerce data

The BFF pattern, authentication, multi-tenant themes, catalog, cart, checkout, search, media and forms.

Build and deploy

Build configuration, compute, environment variables, and the four ways to create a deployment.

Run it in production

Deployments, previews, rollbacks, domains, logs, and publishing a theme to the marketplace.

This section is for frontend developers building a storefront for a B2B commerce customer. In Cockpit, customers manage their sites, domains, pages, media, and themes in Experience Studio; this section is the developer's side — how you build the storefronts and themes they run.

That usually means you're at a partner agency or on a customer's own product team, and you're shipping the website that the customer's buyers will use to log in, browse catalogs, place orders, and manage their accounts.

What you're actually building

A storefront on revenexx is a Nuxt 4 application running as the customer-facing shopfront. You don't fork it: your theme extends the published base layer @revenexx/cover, which brings the components, composables, and server routes for a working storefront. The platform gives you a substantial head start — multi-tenant data, identity, catalog, checkout primitives, search — and your job is to wrap that in a brand experience that fits the customer's business.

The single most useful thing to know on day one: it runs locally with no credentials at all. Every commerce domain resolves through a service key that defaults to mock, so npm install && npm run dev gives you a working shop with a catalog, a cart, and a checkout before you have an API key. See Service modes.

In practice, a storefront project involves four kinds of work:

  1. Composition — laying out pages the customer's content team can edit themselves. That's Blökkli, the block-based page builder: the reference theme ships around ninety block bundles, and you add your own as Vue components.
  2. Customization — tailoring the checkout to the customer's order process. Most B2B checkouts need things a B2C template doesn't have: cost centers, approval flows, ERP-validated SKUs, contract-priced line items. Schema-driven FormKit forms make this configurable per customer without a rebuild.
  3. Identity — wiring up login, registration, and password recovery. Buyers authenticate through Customers, the platform's buyer identity, which is separate from the admin/Cockpit identity (signed in through ID).
  4. Branding — applying the customer's visual identity with design tokens, so the same codebase serves many tenants without rebuilds.

What you don't have to build: multi-tenancy plumbing, the catalog data model, the order system, payment integrations, the search infrastructure, user roles. Those come from the platform.

What you should not build here either: business logic. Pricing, stock rules, validation and approvals live in an App, and the storefront reaches them through the App's API capabilities. Apps and Sites draws the line and shows a Theme consuming an App from end to end.

What you'd typically build with this

Three realistic project types:

A wholesaler webshop for a Mittelstand distributor. Buyers log in, see their contract pricing, browse SKUs, place orders that flow into the customer's ERP. You extend the reference theme, customize the checkout for net-30 payment terms and cost-center routing, and theme it to the customer's brand. Most of the work is in the integration between the storefront and the ERP — which is itself usually built in Integration Studio, not in the storefront.

A spare-parts portal for a manufacturer. Each registered workshop sees parts compatible with their installed equipment. You wire identity to a customer database, customize the catalog views to show compatibility data, and add a quick-reorder workflow on the account page.

A configurator-driven storefront for industrial supplies. Buyers configure complex products before adding them to the cart. You build custom Vue components for the configurator, and the rest — catalog, cart, checkout, account — comes from the base layer.

In all three, the unique work is in the customization and integration. The boilerplate is solved by the platform.

The five groups

The section is organised the way a project runs.

  • Build the theme — the layer chain you extend, the theme.json manifest, file-path shadowing, the mock-to-live service modes, design tokens, local development, the supported frameworks, and rendering strategies.
  • Compose pages with Blökkli — defineBlokkli, the option types, shells and fields, registering a block in the manifest, inline editing, reading published pages, and the full bundle catalog.
  • Connect commerce data — why components call /api/* and never the gateway, the auth headers, running one deployment for many tenants, and the catalog, cart, checkout, search, media and forms surfaces.
  • Build and deploy — build configuration, compute specifications, environment variables, and deploying from Git, from the CLI, or by upload.
  • Run it in production — deployment statuses, preview hosts, instant rollbacks, custom domains and TLS, request logs, and publishing a theme.

Where to go next

New to the platform as a whole? Start with Platform overview. Ready to build? Getting started has a themed storefront on a preview URL in eight steps. Prefer a guided tutorial? Build a storefront theme walks the same ground at a slower pace.