Starting points

Where to start a new storefront or theme — the reference theme, the theme marketplace, and the framework quick-starts.

There is no public template-listing API. The site-template endpoints are not exposed on the public gateway at https://api.revenexx.com, so don't design a workflow around fetching a catalogue of templates — there is nothing partner-callable to fetch.

What does exist are three real starting points, and which one you want depends on what you're building.

Start from the reference theme

For a commerce storefront, this is the answer. A theme is a Nuxt 4 app that extends the published base layer:

nuxt.config.ts
export default defineNuxtConfig({
  extends: ['@revenexx/cover'],
})

@revenexx/cover is on public npm. Extending it gives you the components, composables, and server routes for a working storefront — catalog, cart, checkout, account — and overriding any part of it is plain Nuxt layer shadowing: put a file at the same path in your project and yours wins.

If you also want the full Blökkli block library, extend @revenexx/cover-theme instead, which extends @revenexx/cover itself.

The decisive advantage: a storefront built this way runs locally with no credentials at all, because every commerce and content domain defaults to mocked data in development. See Architecture.

The tutorial is Build your first theme.

Install a theme from the marketplace

If the customer doesn't need a bespoke storefront, an existing theme may do. In Cockpit, Experience Studio → Marketplace lists installable storefront themes; installing one makes it available to activate on a domain under Installed Themes.

This is a themes marketplace, not a scaffold generator — you install a whole theme and configure it, rather than copying a starter into your own repository. Getting your own theme listed there is covered in Publishing a theme.

Start from a framework quick-start

If you're deploying something that isn't a commerce storefront — a documentation site, a landing page, an app shell — start from the framework quick-starts. They cover creating the site, the build settings for that framework, and the first deployment, without any assumption that you're building a storefront.

Related

Was this page helpful?