A Salesive theme is a Vite and React project, and you build it with salesive-dev-tools. The CLI scaffolds the project, runs it locally with live config watching, and publishes it with salesive cook. Before any of that, you need a Themes API key from Developers then API keys in the dashboard.

What do you need before you start?

You need a Salesive account with access to the developer settings, a Themes API key, and a working Node environment for Vite and React. The API key is created under Developers then API keys. Treat it like a password: it authorises publishing, so it does not belong in a public repository.

You also need a store to develop against. A theme renders a real storefront, so the useful development loop points at a store with products, categories and at least one order. An empty store hides most of the layout problems you are trying to catch.

Decide which store mode you are targeting before you scaffold. Salesive supports ecommerce, restaurant and business storefronts, and the mode changes what the theme is expected to render.

How do you scaffold a theme?

Start by storing the token with salesive auth set-token, then confirm it with salesive auth verify. Running verify before you scaffold saves you from debugging a build that was never going to publish.

Then run salesive init. The command scaffolds a Vite and React project with the structure the platform expects. You get a working theme rather than an empty folder, which is the fastest way to learn the conventions.

Read the generated files before you change them. The scaffold encodes the route structure, the config shape and the build expectations. A theme that fights the scaffold will fight the publish step too.

How does local development work?

salesive-dev-tools runs the project locally with live config watching. When you change the theme configuration, the running storefront picks it up without a full restart. That short loop is the point of the CLI: you see the merchant-facing result while you edit.

Develop against real content. A theme that looks right with placeholder text can fall apart with a long product name, a missing image or a category with one item. The live config watching makes it cheap to test those cases as you go.

Keep the browser console open. React warnings and failed asset requests are easier to fix while the change is small. A clean console at the end of a session is a better signal than a screenshot that happens to look right.

Run the theme against a store in each mode you support before you publish. A restaurant menu and an ecommerce grid stress different parts of the layout, and the config that works for one can leave the other with empty sections.

How do you configure a theme?

Themes use salesive.config.json for configuration. That file is how the theme declares what it needs and how the platform passes store data into it. Keep it explicit and keep it in version control.

Merchant-facing settings live in salesive.form.json, which works with the Form Builder. This is the difference between a theme you can only configure in code and a theme a merchant can adjust from the dashboard. A colour, a layout choice or a section toggle can become a form field instead of a support ticket.

Design the form for the merchant, not for yourself. Every field you expose is a decision someone has to make. Expose the ones that change the storefront in a useful way, and keep the rest in the config.

Keep secrets out of salesive.config.json. The file is part of the theme, and a theme is published. If a value is private, it does not belong in a file that ships with the storefront.

What can a theme override?

Themes support automatic route overrides. That means the theme can take control of a route without you rebuilding the router by hand. The /library route is supported too, so a digital store can present its buyer library inside the custom theme.

Multi-mode storefronts are supported. A theme can serve an ecommerce store, a restaurant store or a business store, with the mode deciding which pieces are relevant. If you only need one mode, say so in the config and keep the theme narrow.

Test every route you override with a real store in that mode. A route that works in ecommerce can behave differently when the store sells menus or services.

A theme is a contract with the platform. The more you work with the scaffold, the less you have to maintain against it.

How do you publish?

Publishing is salesive cook. The command builds the theme and sends it to Salesive, where it becomes available to the store. Run it from the project root, with the same token you verified at the start.

Publish to a test store first. A theme that works locally can still fail on a real storefront because of a missing config value or a route that expected data the test store does not have. The publish step is not the place to discover that.

Keep a version you can go back to. A theme is production code for someone's shop, and a publish that breaks checkout is urgent in a way that a broken landing page is not.

What are the limits?

A Salesive theme runs on Salesive. It is not a general React app you can deploy to another platform, and the CLI publishes to the Salesive theme system rather than a generic host. Build for the platform you are actually on.

The theme also depends on the platform's data and routes. When you override a route, you are still working within the storefront model, not replacing it. That constraint is what keeps payments, accounts and the chat widget working.

Frequently asked questions

What is a Salesive theme built with?

A Vite and React project, scaffolded and published with salesive-dev-tools.

Where do I get the Themes API key?

From Developers then API keys in the Salesive dashboard.

What does salesive init do?

It scaffolds a Vite and React theme project with the structure the platform expects.

What is salesive.form.json for?

It defines merchant-facing settings that work with the Form Builder, so a merchant can configure the theme from the dashboard.

Can I publish a Salesive theme to another platform?

No. Themes run on Salesive and are published with salesive cook.

The shortest path is the scaffold: verify the token, run init, develop with live config watching, put merchant settings in the form, and publish with cook to a test store first. The features page covers the storefront, integrations covers the services a theme can surface, and pricing shows the plans. For the widget your theme will host, read what the Salesive chat widget gives your storefront, and for the currency a theme has to display, see selling in USD and GBP from Nigeria.