love-ecommerce-template 1.0.0 · SDK 1.2.0

Getting started

The Template SDK is a complete, standalone kit for building templates for the storefront: a launcher, a CLI, a visual Studio, a preview with demo data, a validator built from the store's rules, a test runner, and packaging that produces folders the store installs as they are. It needs only Node.js — no store, no database, no npm packages.

The template rules in this documentation come from love-ecommerce-template 1.0.0 (fingerprint 7075c14c24bbaf06), built into the SDK on 2026-10-01. Statements about the template system cite the store's source as file:line — hover to see the line.

Who does what

Template developerStore owner
Hasthis SDK and their template filesthe store application
Doescreates, edits, previews, validates, tests and packages templatesinstalls the template packages developers send
Commandsthe launcher, or create, dev, validate, test, packageverify --app, install --app, runtime update --app

Requirements

Start

Nothing is installed. Unzip the SDK, then:

From a terminal instead: in the SDK folder use node bin/template-sdk <command>; inside a template folder use node sdk <command> (every template made by the SDK has a small sdk.js that finds the SDK). On Windows sdk <command> works too (.\sdk in PowerShell), and npm run dev / validate / test / package if npm is present.

For the store owner

node bin/template-sdk verify my-template-1.0.0.zip --app /path/to/frontend    # check a package against the live store
node bin/template-sdk install my-template-1.0.0.zip --app /path/to/frontend   # copy it into <frontend>/templates
node bin/template-sdk runtime update --app /path/to/frontend                  # after a store update: refresh the SDK's built-in rules and renderer

Your first template

# in the SDK folder
node bin/template-sdk create my-template                 # → projects/my-template ("storefront" starter: every engine feature wired)
node bin/template-sdk create my-blank --from blank       # minimal starting point
node bin/template-sdk create my-copy --from organic      # copy of one of the store's templates

cd projects/my-template
node sdk dev          # Studio: visual + code editor with live preview (Ctrl+C to stop)
node sdk validate
node sdk test
node sdk package      # dist/my-template-<version>.zip, verified → send it to the store owner

A template folder you already have: node bin/template-sdk import <folder or zip> (copies it into a project), or node bin/template-sdk init <folder> to add sdk.js to it in place.

Project layout

PathPart of the template?Purpose
index.htmlyesMarkup rendered by the application (see HTML).
styles.css / style.cssyesStylesheet (see CSS).
script.jsyesTheme script (see JavaScript).
template.jsonyes (required)Configuration (see Configuration).
theme.jsonyes (optional)Installation metadata.
image/yesImages served at /image/… (see Assets).
template-sdk.jsonnoSDK project settings (normally empty).
sdk.js, sdk.cmd, package.jsonnoLaunchers: node sdk <command>, sdk <command> (Windows), npm run <command>.
tests/noYour tests (see Testing).
sample-data/noYour preview datasets (see Sample data).
dist/noBuild output and packages.
.template-sdk/noCaches, the staged preview, test results. Safe to delete.

Only the template files are copied into builds and packages; the others never reach the application.

Starters

Generated 2026-10-01 11:59 UTC from the application source (contract 7075c14c24bbaf06).